6-5-1 Webmethods Error Message Reference PDF

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

Contents

About This Guide
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

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.

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

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

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.

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.

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.

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

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

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.
1033 Error: "<switchString>" unknown switch.

Cause: The option specified in the command line is unknown.
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.
1034 Error: Unexpected arg "<argString>".

Cause: The argument is not valid.

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.
1037 Error: "<parameter>" is specified but not required.

Cause: Extra storage parameters are specified but not required.
1038 Broker Server Monitor starting Broker Server executable <executableName> in directory <dataDirectory>.
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.

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.

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.

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.
1055 Error: The specified license key is incorrect. Please specify a valid license key.
Cause: The Broker Server license key is invalid.
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.

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

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.

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.

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

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.
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
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
1089 Cannot register service <serviceName>: <errorMessage>.

Cause: The Broker Server encountered an internal error on the Windows platform.
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>.

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

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

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


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.
1098 Cannot open service <serviceName>: <errorMessage>.

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

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

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


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

Broker
1105 Broker initialization failed, network manager did not start -- [EXITING].
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>.

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

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.

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.

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.
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.
1119 Could not accept SSL connection, error code <errorCode> (<errorMessage>).
1120 Could not accept SSL connection, bad handshake from <ipAddrss>: <portNum>.

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

1122 Could not find DN <distinguishedName> in key file "<keyFile>". SSL disabled.
Cause: The certificate file supplied does not contain the specified Distinguished Name.
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.
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.

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.

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.

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.

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

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.
problem.
1158 Broker "<brokerName>": Error: Could not prepare lookup document to send to access label adapter process. Access
label lookup not available.
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.
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.
problem.
1160 Broker "<brokerName>": Error: Could not allocate memory to send lookup to access label adapter process. Access
label lookup not available.

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

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

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.

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.

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.
Reason: Permission denied.
Cause: The local Broker Server failed to establish a connection with a remote Broker 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

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.
Reason: An internal error occured (error code <errorCode>).
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.

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.
1182 Error: Cannot add QS log file "<fileName>": <errorMessage>.

Cause: The Broker Server failed to add a QS log file.
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.
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.
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.

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:
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.
1187 Broker "<brokerName>": A broker connection to "<brokerName>"@<portNum> was successfully established.

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

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

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.

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.

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

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.

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

Broker successfully recreated the storage required files.
Response: No action required.

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

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

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.

BRM (JMS Provider)
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.

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.
BRM.10.1009 Message data field is missing in serialized message.

Cause: The serialized Message object does not contain the required data field.
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.

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.

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.

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

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

Cause: An unsupported object type was passed to the method.
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.

BRM (JMS Provider)
BRM.10.1061 Map Message field "<name>" cannot have type "<type>".

BRM.10.1062 Map Message field name cannot be null.

Cause: The passed field name was null.
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>".
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.

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.

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.

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.

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

BRM.10.1224 Transaction rolled back due to lost connection.

Cause: The client reconnected to the Broker resulting in any open transactions being aborted.
BRM.10.1225 Asynchronous message listener has thrown an exception.

Cause: The client's message listener code has thrown a RuntimeException.
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.

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.

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.

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.

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.

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.

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.

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.
BRM.10.4004 Broker protocol error.

Cause: An internal error indicating that the Broker sent an invalid reply.
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.

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.

BRM (JMS Provider)
BRM.10.4028 Invalid license.

Cause: The Broker's license is invalid.
BRM.10.4029 Multiple event requests.

Cause: An internal error indicating that the Broker has received multiple event requests for the same consumer.
BRM.10.4030 Operation interrupted.

Cause: An internal error indicating that client's current operation on the Broker has been interrupted.
BRM.10.4031 Client has been deleted.

Cause: The client has been administratively deleted.
BRM.10.4032 Queue cursor is out of bounds.

Cause: An internal error indicating that the Broker queue's cursor is out of bounds.
BRM.10.4033 Acknowledgement is out of order.

Cause: An internal error indicating that message acknowledgement arrived out of order.
BRM.10.4034 Duplicate sequence number.

Cause: An internal error indicating that the Broker received a duplicate sequence number.
BRM.10.4035 Bad sequence number.

Cause: An internal error indicating that the Broker received an invalid sequence number.

BRM.10.4036 Client has been destroyed.

Cause: The client has been administratively destroyed.
BRM.10.4037 Broker has run out of storage.

Cause: The Broker to which the client is connected has run out of storage.
BRM.10.4038 Protocol is missing arguments.

Cause: An internal error indicating that the command sent to the Broker is incorrect.
BRM.10.4039 Broker strorage is corrupt.

Cause: The Broker's storage has become corrupted.
BRM.10.4040 Broker storage error.

Cause: The Broker reported a storage error.
BRM.10.4041 Command not recognized by Broker.

Cause: An internal error indicating that the command sent to the Broker is not recognized.
BRM.10.4042 Broker protocol error: <error>

Cause: An internal error indicating a Broker protocol error.
BRM.10.4043 Connection is closed.

Cause: An internal error indicating that the Broker session has been disconnected.

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.
BRM.10.4046 Connection to Broker "<broker>" has been reconnected.

Cause: The current operation failed because of reconnection to the Broker.
BRM.10.4100 Reconnecting to "<broker>" in <number> seconds.

Cause: The client has lost its connection to the Broker and will be reconnecting.
BRM.10.4101 Reconnected successfully to "<broker>".

Cause: The client has successfully reconnected to the Broker.
BRM.10.4236 Transaction unknown.

Cause: An internal error indicating that the transaction is unknown.
BRM.10.4237 Transaction mismatch.

Cause: An internal error indicating that there is a transaction mismatch.
BRM.10.4238 Transaction closed.

Cause: An internal error indicating that an operation was attempted on a closed transaction.
BRM.10.4239 Transaction invalid state.

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

BRM.10.4240 Transaction already open.

Cause: An internal error indicating that an open transaction was attempted to be opened.
BRM.10.4241 Transaction cannot be reopened.

Cause: An internal error indicating that a closed transaction was attempted to be reopened.
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.
BRM.10.4244 Transaction has been heuristically rolled-back.

Cause: The client attempted to use a transaction that has been heuristically rolled-back.
BRM.10.4245 Transaction has been heuristically committed.

Cause: The client attempted to use a transaction that has been heuristically committed.
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.

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.

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

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.

distinguished name.
Response: Specify a distinguished name.
BRM.10.5102 Cannot make SSL connection to Broker: password is missing.

password.
Response: Specify the keystore's password.

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

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.

Broker Failure (100-1011): A failure occurred on the Broker. An uninterpretable reply was sent back.
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.

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

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

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.

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.

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.

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.

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.

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

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.

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

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

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

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.

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.
Response: Make sure that the bin string is valid and was obtained from a valid BrokerEvent.

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.

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.

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.
Incompatible Version (106-1208): The Broker does not support changelocks.

Cause: This version of the Broker does not support the change locks feature.
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.
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.
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.
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.
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.

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.
Incompatible Version (106-3796): Transactions not supported in this version.

Cause: This version of webMethods Broker does not support transactions.
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.
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
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.

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

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

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
Response: Make sure that the document name is valid and contains only supported characters.

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

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

Broker C API
Invalid Field Name (214-1286): The field name <fieldName> is invalid. Field names must be between 1 and 255 ANSI
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
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.

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.

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

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.
Response: Check the ClientQueueLock. Make sure that its parameters correspond to a valid client and the
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.

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

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

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.

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.

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.

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.

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

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.
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.
the document type's time-to-live is different.
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.
the document type's description is different.
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.
the document type's infosets are different.
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.
the document type's validation is different.
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.

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

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

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.

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.

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

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

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

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.

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

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.

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.

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.
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.
Protocol Error (111-1433): A protocol failure occurred.

Cause: An unknown error in the protocol request caused the operation to fail.
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.
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.

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

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

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

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

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.

Broker Java API
Bad State (200-1000): Cannot register callback for a sub ID before registering a general callback.
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.
Response: Register a general callback before registering any specific callbacks for a BrokerClient.
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.

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

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

Broker Failure (100-1011): A failure occurred on the Broker. An uninterpretable reply was sent back.
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-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.
necessary.

Broker Java 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.
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.

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

Broker Java 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.

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

Broker Java API
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: 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.
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.
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 matches 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 matches 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.
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.

Broker Java API
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.
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 passed in.
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.
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.
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.
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.

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. Check the error message <parseMsg> for more details.
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.

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

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

Broker Java API
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.
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 all specified regular expressions are correct.
Filter Runtime Error (206-1167): A filter stack overflow has occurred.

Filter Runtime Error (206-1168): A filter stack underflow has occurred.

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.

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.
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.
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.
Format Error (207-1180): Error in parsing document bin string body header.
Cause: The bin string might be invalid.
Format Error (207-1181): Error in parsing document bin string data.

Format Error (207-1182): Error in parsing document bin string envelope header.

Broker Java API
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 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.
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.
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 Broker does not support setting subscription filters for territory gateways.
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.
Incompatible Version (106-1208): The Broker does not support change locks.
Cause: This version of the Broker does not support the change locks feature.
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.

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

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.
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.
Interrupted (107-1210): The operation was interrupted by request.

Cause: The operation was interrupted by user request.
Response: None.
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 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 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
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
Response: Make sure that the broker name is valid and contains only supported characters.

Broker Java API
Invalid Client (209-1230): The client pointer is NULL or is not a client. Perhaps the variable is uninitialized or the client has
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.
Invalid Client Group Name (237-1600): The client group name <group> is not valid. Client group names cannot contain
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
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 occurred while accessing the ClientQueueLock of <clientID>. The
ClientQueueLock is 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
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 BrokerClient 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 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
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
Response: Make sure that the document name is valid and contains only supported characters.
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.

Broker Java API
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.
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.
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
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.
Invalid Field Name (214-1286): The field name <fieldName> is invalid. Field names must be between 1 and 255 ANSI
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.

Broker Java API
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 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.
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.
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.

Invalid Filter (282-2310): The filter is invalid. The hint at position <char_pos> is missing the "hint:" prefix.
Invalid Filter (282-2311): The filter is invalid. The hint at position <char_pos> is missing a comma delimiter.
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 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-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.

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.
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.
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
Response: Check the Broker for the specified client ID. Make sure that the client ID exists on the 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 occurred while accessing the ClientQueueLock of <clientID>. The ClientQueueLock
is 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
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
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.

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

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

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.

Broker Java API
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-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.

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

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

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-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.
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.
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 to 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. 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-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 BrokerClient.
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-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-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.
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.
the document type's definition contains different fields.
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.

Broker Java API
the document type's description is different.
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.
the document type's validation is different.
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.
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>.
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>.
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
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.
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
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 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 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

Broker Java API
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.
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-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.

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: Make sure the encryption levels are matching.

Broker Java 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: 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.
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.
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.
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.

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-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-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-1412): The value of 'flag' is not a legal value.

Cause: The Broker encountered a serious internal error.
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).
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).

Broker Java API
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.
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.
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.
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-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-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.
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.

Broker Java API
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.
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.
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-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-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-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.

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-1430): Client creation failed due to missing platform information.
Cause: The client could not be created because information on the client platform is missing.
Protocol Error (111-1433): A protocol failure occurred.

Cause: An unknown error in the protocol request caused the operation to fail.
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.

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.

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

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 <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-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: Make sure that the certificate is specified explicitly when using a certificate file with more than one
certificate.

Broker Java API
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.
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.
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
Response: Make sure that the specified Broker exists on the Broker Server.

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
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
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 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.
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
Response: Make sure that the specified client group exists on the broker.

Broker Java API
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.
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
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
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.
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.

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.

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.
ETD.0002.0008 Error closing build file: <buildFile>

Cause: An error occurred when attempting to close the build file.
ETD.0002.0009 Error creating build report: <buildReportFile>

Cause: An error occurred when attempting to create the build report file.
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.
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.

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

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

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
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
Response: Either remove the profile field group from the project or add it to the source Trading Networks
system.

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

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


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

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

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

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.
ETD.0004.0021 Could not load deployment map <deploymentMapName> from project <projectName>.
Cause: The deployment map file is corrupted.
<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>.

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

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

again. If saving again is not successful, restarting the server might help, or recreate the deployment candidate.
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.
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.

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.

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.

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

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.

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.

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, if it is available.
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>.

again. If saving again is not successful, restarting the server might help, or recreate the variable substitution
information and retry the action.
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.

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.

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.

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.

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

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 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.
Server.
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:

Server.
allowable field groups.
ETD.0006.0266 An error occurred while attempting to import field definitions; error information from Trading Networks
Cause: An error occurred when attempting to import field definitions into Trading Networks. Possible causes
include:
Server.
allowable field definitions.
ETD.0006.0270 An error occurred while attempting to import partner profiles; error information from Trading Networks
Cause: An error occurred when attempting to import partner profiles into Trading Networks. Possible causes
include:

Server.
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:
Server.
allowable trading partner agreements (TPAs).

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:
Server.
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.

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

Server.
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:
Server.
allowable Trading Networks Security Data.

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:
Server.
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:

Server.
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."

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

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.

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.

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.

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

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

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

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

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:
<targetFileName>
- 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>.
<errorMessageReturnedFromIS>
- 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.

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

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

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.

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>
ETD.0007.0008 Call to getConnectionInfo for system <serverName> returned the following missing data: <errorMsg>

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.

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.

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.

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

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

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,"
- 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,"
- 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

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

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

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


CHAPTER 3
webMethods EDI Module
EDICOR (WmEDI Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
EDIFTN (WmEDIforTN Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

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.

EDICOR.000010.000108 Unsupported encoding specified - <encodingName>

Cause: When reading data from InputStream and converting it to String, the encoding specified is not
supported.
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>'

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

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

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.

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.
supported encoding.

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.

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
EDIFTN.000010.000007 Unable to install doc type: 'version' not supplied

EDIFTN.000010.000008 Unable to install doc type: 'transaction' not supplied

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.

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

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

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.
supported encoding.

EDIFTN.000010.000116 Failed to update EDI Tracking status: Original Doc ID: {<documentID>}, related Doc ID:
{<documentID>}, new status {FAStatus>}
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

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
EDIFTN.000010.000204 Failed creating EDI envelope doc type. Cannot handle object of type: {<objectClassName>}

EDIFTN.000010.000206 Failed creating EDI envelope doc type. Service wm.b2b.editn.getAllDetails returned null or empty
details
EDIFTN.000010.000208 An error occurred during document processing. The service wm.b2b.editn:getICDetail failed

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.
supported encoding.
EDIFTN.000010.000216 {<exceptionShortDescription>}
Cause: Internal Error in EDIEnvelopeDocType.createEnvelope().
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>}


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

EDIFTN.000010.000242 TPA Store Exception

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.

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

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.
EDIFTN.000010.000258 Cannot reprocess document <TN internal document id>.\n<detailed error message>.
Cause: There is a database error.
EDIFTN.000010.000260 Failed to create EDI Status entry.

Cause: There is a database error.
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.

EDIFTN.000010.000263 Cannot reprocess a Duplicate Control Number or Out of Sequence Control Number group document
with generateFA option set to be true.
been updated.
control number.
EDIFTN.000010.000264 Cannot reprocess an Auto FA rejected envelope document with generateFA and/or
updateControlNumber option set to be true.
been updated.
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).
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.
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.

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).
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).
associated with this document, and then contact webMethods Customer Care. Please have the following
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.

EDIFTN.000010.000290 Rejected a document that failed FA validation/compliance check.

Cause: The document contains an error.
EDIFTN.000010.000291 Received a document that failed FA validation/compliance check.

Cause: The EDI document contains an error.
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.
associated with this document, and then contact webMethods Customer Care. Please have the following
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.
EDIFTN.000010.000294 Forced reprocessing of document.

Cause: User forced reprocessing of the document.
EDIFTN.000010.000295 Reset control number.

Cause: The control number has been set/updated.
EDIFTN.000010.000296 Status returned by wm.b2b.edi.util:generateFA.

Cause: The FA status is displayed.

EDIFTN.000010.000297 Envelope Validation Error.

Cause: The wm.b2b.edi:envelopeProcess service failed. Envelope is not valid.
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.
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.

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

supported encoding.

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

EDIFTN.000010.000711 {<IOExceptionShortDescription>}
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>}
supported encoding.
EDIFTN.000010.000720 Invoking validation service error: {<ExceptionShortDescription>}

EDIFTN.000010.000750 {<ExceptionShortDescription>}
EDIFTN.000010.000752 Exception from EDItx module

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.

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.
packages\WmEDIforTN\config directory.
EDIFTN.000010.000768 TPA Store Exception

Cause: There is an error while creating and/or updating a TPA.
EDIFTN.000010.000770 Error: <detailed TPA Store exception message>

Cause: There is an error while creating and/or updating a TPA.

EDIFTN.000010.000772 Failed to get control number

Cause: Error occurred while trying to retrieve the control number.
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.
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.

EDIFTN.000010.000786 Please check console and error log

Cause: There is an error in the delivery job entry.
associated with this document and the Integration Server error log.
EDIFTN.000010.000818 Failed to create EDI Tracking entry

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

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.

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.
EDIFTN.000040.000022 Fail to lock - it is already locked (TN document id: <document id>)
Cause: The row is locked.


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


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>

EDIINT.000002.000004 Could not register EDIINT MDN Attribute - <attributeName>

EDIINT.000002.000011 Error in creating EDIINT BizDocEnvelope, <errorMessage>


EDIINT.000002.000012 Error in creating EDIINT MDN BizDocEnvelope, <errorMessage>
EDIINT.000002.000013 Could not register EDIINT Processing services, <serviceName>

EDIINT.000002.000014 Could not register EDIINT Processing services, <serviceName>

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.

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

Response: See the server log and activity log for more information.

EDIINT.000002.000033 Could not retreive docId from envelopeDocuments
The EDIINT Module located the envelopeDocuments variable in the pipeline; however, it does not contain
Trading Networks internal IDs.
available.
EDIINT.000002.000034 Could not retreive EDI BizDocEnvelope [<TN_internalDocID>]

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.
available.
EDIINT.000002.000035 EDI BizDocEnvelope [<TN_internalDocID>] has not been persisted

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

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.

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>

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


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


CHAPTER 5
webMethods Flat File Package
FFP (Flat File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
FPL (File Polling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

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.

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>

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

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.
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.
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.
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 (`]`).
FFP.0000.0018 Found unmatched `]`

Cause: Character `]` occurred in SEF file without a starting `]` character.

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.
FFP.0000.0020 Unexpected `{` character. Loop occurring in segment definition

Cause: The character '{' occurs in an unexpected location in a segment definition.
FFP.0000.0021 Loop Contains no segments

Cause: The SEF file contains a loop definition that is empty; that is, it contains no segments.
FFP.0000.0022 Found loop close `}` in segment definition. Expecting `]`

Cause: The character '}' occurs in an unexpected location in a segment definition.
FFP.0000.0023 Unable to parse number [<unparsableNumber>]

Cause: The <unparsableNumber> value specified in the message is not a valid number.
FFP.0000.0024 No sets defined in SEF file

Cause: The SEF file has no transaction set definitions.
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.

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


FFP (Flat File)
FFP.0001.9002 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


FFP.0001.9008 Cannot add record to a composite

FFP.0001.9009 Cannot add unknown type to a composite


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>


FFP (Flat File)
FFP.0001.9014 The first child of the Record Usage must be the Record Definition
packages\WmFlatFile/\config directory.
FFP.0001.9015 Cannot set the children of a usage node. The only child is the used node definition
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

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.

FFP (Flat File)
FFP.0005.0003 Unknown type <typeName>

Cause: A Node Definition with an unknown type was encountered.
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."

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.
FFP.0011.0008 Invalid date

Cause: The input data in a date field does not meet the format specified by a format service.

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.
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.
FFP.0011.0011 Unrecognized element

Cause: A record appeared in the document that is not defined in the flat file schema.
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.
FFP.0011.0014 Maximum occurs exceeded

Cause: A record appeared in the document more times than allowed by the flat file schema.

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.
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.
FFP.0011.0018 String could not be formatted properly.

Cause: A formatting service has been invoked on a given field and determined that the value of the field cannot
be formatted properly.
FFP.0011.0099 Other error

Cause: Attempted to validate a field that does not contain a String value.
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.

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.
FFP.0013.0002 Missing envelope start for standard: <standardName>

Cause: The configuration file used for parsing SEF files contains errors.
FFP.0013.0003 Missing envelope end for standard: <standardName>

FFP.0013.0004 Missing document start for standard: <standardName>


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

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.

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

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.

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.

FFP (Flat File)
FFP.0100.0005 Unable to handle recordIdentifier of type: <invalid type>.

Cause: Internal error
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.

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.

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.

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.

FPL (File Polling)
FPL.0001.0013 Error processing monitoring file. <errorReason>.

Cause: An error occurred during the execution of the user-specified processing service.
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
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>


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

FPL (File Polling)
FPL.0002.0004 Server Error: <errorDetails>

FPL.0002.0005 Invalid Cleanup service: <serviceName>

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>


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.

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.

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

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

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.

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.

-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

-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


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


-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


-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


-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


-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


-SSLcert option used without a certificate, ignored
-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.

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

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

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.

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.
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
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.
argument or see the “webMethods Installation Guide.”

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.

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.

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.

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

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.
ART.0114.0004E Adapter Runtime: Error getting available packages.

Cause: An error occurred while retrieving a list of packages available for node creation.
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.
ART.0114.0006E Adapter Runtime: Unable to initialize transaction manager. Transaction manager already initialized.
Cause: WmART has attempted to initialize the Transaction Manager twice.
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.

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.
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.
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.
ART.0114.0013E Adapter Runtime: Error occurred while Adapter Runtime was loading adapter type "<adapterName>".

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.
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.
ART.0114.0016E Adapter Runtime: Error occurred while Adapter Runtime was unloading adapter type "<adapterName>".
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.
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.
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.

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.

ART.0114.0032E Adapter Runtime: Unable to update resource <namespace>.

Cause: An error occurred when updating a value in the specified namespace.
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.
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.
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.

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

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.
long data type.
ART.0114.0058E Adapter Runtime: Unable to convert string array to primitive float array.
float type.

ART.0114.0059E Adapter Runtime: Unable to convert string array to primitive double array.
double type.
ART.0114.0060E Adapter Runtime: Unable to convert string array to primitive boolean array.
Boolean type.
ART.0114.0061E Adapter Runtime: Unable to convert string array to primitive short array.
short type.
ART.0114.0062E Adapter Runtime: Unable to convert string array to primitive char array.
char type.
ART.0114.0063E Adapter Runtime: Unable to convert string array to Integer array.

integer instance.
ART.0114.0064E Adapter Runtime: Unable to convert string array to Long array.

long instance.

ART.0114.0065E Adapter Runtime: Unable to convert string array to Float array.

float instance.
ART.0114.0066E Adapter Runtime: Unable to convert string array to Double array.

double instance.
ART.0114.0067E Adapter Runtime: Unable to convert string array to Boolean array.

Boolean instance.
ART.0114.0068E Adapter Runtime: Unable to convert string array to Short array.

short instance.
ART.0114.0069E Adapter Runtime: Unable to convert string array to Character array.

character instance.
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.

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:
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.
ART.0114.0075U Adapter Runtime: Unable to set property descriptor.

Cause: WmART failed to introspect an unspecified bean.
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.
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.

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

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

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

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

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

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

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

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.
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.
ART.0114.0306E Adapter Runtime (Transaction): Unable to rollback 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
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
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
ART.0114.0351E Adapter Runtime (Transaction): Unable to create Transaction Manager.

Cause: WmTransactionManagerFactory failed to create a TransactionManager.

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

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

ART.0114.0517E Unable to get Adapter Description. Adapter Resource Bundle not found.
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
ART.0114.0518E Unable to get Adapter Description.

Cause: WmAdapter failed to retrieve the adapter's description string for the server's locale.
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.
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.
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.
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,

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

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.
that adapter.

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

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.

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
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.
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.
that adapter.

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.
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.
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.
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.
ART.0114.0701E Adapter Runtime: Unable to retrieve ART instance/session ID.

Cause: The Adapter Runtime (ART) session ID failed to initialize.
ART.0114.0702E Adapter Runtime: Errors occurred attempting to stop <notificationName>. See error log for details.
Cause: An exception was caught stopping the notification.
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.

ART.0114.0704E Adapter Runtime: Internal Error-assert failed - node: <notificationName>, detail:<errorDetail>. Contact
technical support.
Cause: An unexpected exception occurred during processing.
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.
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.

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.

Cause: WmART failed to encrypt a string value.

Cause: WmART failed to decrypt a string value.
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.

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.
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.
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.
ART.0114.1012D Adapter Runtime: No updates found for adapter: <adapterName>.

Cause: No installed updates were found for the adapter.
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.

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.
ART.0114.1018E Adapter Runtime: Error loading update information. The '<tagName>' tag is missing.
Cause: The fix name is missing.
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.
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.
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.
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

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

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

ART.0115.3207E Adapter Runtime (Listener): Illegal event type received: <eventNumber>.

Cause: The method WmNotificationListener.doNotify was passed the specified invalid event ID.
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.
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
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.
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.
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.

ART.0115.3214E Adapter Runtime (Listener): Listener <listenerNode> not Found.

Cause: WmART failed to lookup the specified listener.
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.
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.
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.
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.

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

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

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

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

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.
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.
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
ART.0115.3251E Adapter Runtime (Listener): Invalid listener node name: <listenerNode>.

Cause: The specified listener name is missing or invalid.
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.
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.

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

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

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.

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.
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
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.
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.
ART.0116.3005E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. Publishable
Document name not set.
publishable document node name for the specified notification.

ART.0116.3006E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. UUID not set.
specified notification's universal unique identifier (UUID) from the NotificationNode object.
ART.0116.3007E Adapter Runtime (Notification): Illegal event type received: <eventNumber>.

Cause: The method WmNotification.notifyEvent was passed the specified invalid event ID.
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.
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.
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.
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.

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.
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.
ART.0116.3014E Adapter Runtime (Notification): Notification <notificationNode> not Found.

Cause: WmART failed to locate the specified notification.
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.
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.
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.

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

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

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

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.
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.
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.
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.
ART.0116.3043E Adapter Runtime (Notification): Error deleting notification object. Invalid node name: <notificationNode>.
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.

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

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.
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.
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.
ART.0116.3053E Adapter Runtime (Notification): Unable to update notification <notificationNode>. Invalid node name.
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.
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.

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

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

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

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

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

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

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

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

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

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

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.
ART.0117.4038E Adapter Runtime (Adapter Service): Unable to delete adapter service <adapterServiceNode>.
Cause: An unexpected exception occurred trying to delete the adapter service.
ART.0117.4039E Adapter Runtime (Adapter Service): Unable to update adapter service <adapterServiceNode>.
Cause: An unexpected exception occurred trying to update the adapter service.
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.
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.
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.

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

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.
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.
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.
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.
ART.0118.5012E Adapter Runtime (Connection): Unable to update connection <aliasName>.

Cause: An error occurred while editing the connection type.

ART.0118.5013E Adapter Runtime (Connection): Unable to find connection <aliasName>.

Cause: WmART was unable to locate the specified connection while deleting it.
ART.0118.5014E Adapter Runtime (Connection): Unable to delete connection <aliasName>.

Cause: An error occurred while deleting a connection.
ART.0118.5015E Adapter Runtime (Connection): Unable to get connection manager properties.

Cause: An error occurred while getting a list of Connection Manager properties.
ART.0118.5016E Adapter Runtime (Connection): Unable to get configured values for connection manager.
Cause: An error occurred while processing Connection Manager property values.
ART.0118.5017E Adapter Runtime (Connection): Error occurred while getting connection manager properties.
ART.0118.5018E Adapter Runtime (Connection): Error getting connection properties.

Cause: An error occurred while fetching connection property values.
ART.0118.5019E Adapter Runtime (Connection): Error getting connection metadata. Missing required parameter:
adapterTypeName.
Cause: WmART was unable to determine the adapter type name while processing a connection's metadata.

ART.0118.5020E Adapter Runtime (Connection): Unable to process connection properties. Internal error.
Cause: WmART failed to set properties for a connection node. The expected connection form fields were not
found in the pipeline.
ART.0118.5021E Adapter Runtime (Connection): Unable to process connection properties. Internal error.
Cause: WmART failed to get properties for a connection node. The expected connection form fields were not
found in the pipeline.
ART.0118.5022E Adapter Runtime (Connection): Cannot create connection <aliasName>. Adapter type <adapterName> does
not exist.
Cause: WmART failed to start the specified connection because it was unable to locate the specified adapter
type.
ART.0118.5023E Adapter Runtime (Connection): Unable to configure connection manager. No connection manager
properties provided.
Cause: WmART was unable to validate Connection Manager properties because they were null.
ART.0118.5024E Adapter Runtime (Connection): Unable set connection <aliasName> state to <stateName>. Invalid state
specified.
Cause: WmART was unable to modify the connection's state because the intended state is missing or invalid.
ART.0118.5025E Adapter Runtime (Connection): Unable to enable connection <aliasName>.


ART.0118.5026E Adapter Runtime (Connection): Unable to stop connection <aliasName>.

ART.0118.5027E Adapter Runtime (Connection): Unable to enable connection <aliasName>. Connection is already enabled or
is being shutdown.
Cause: WmART is enabling a connection that is not currently in a disabled state.
ART.0118.5028E Adapter Runtime (Connection): Unable to shutdown connection <aliasName>. Connection is already
disabled or in the process of being shutdown.
Cause: WmART is attempting to shut down a connection that is not currently in an enabled state.
ART.0118.5029E Adapter Runtime (Connection): Unable to disable connection <aliasName>. Connection is already disabled.
Cause: WmART is attempting to disable a connection that is already disabled.
ART.0118.5030E Adapter Runtime (Connection): Unable to create connection <aliasName>. Package <packageName> does
not exist.
Cause: WmART was unable to create the connection node because it could not locate the specified package.
ART.0118.5031E Adapter Runtime (Connection): Unable to delete connection <aliasName>. Internal error.
Cause: An error occurred while deleting the specified connection.

ART.0118.5032E Adapter Runtime (Connection): Unable to set connection resource properties. Internal error:
ConnectionPropertiesBridge not found.
Cause: WmART failed to create a configured managed connection factory because it could not locate the
WmConnectionPropertiesBridge instance needed to set its properties.
ART.0118.5033E Adapter Runtime (Connection): Error disabling connection resources.

Cause: An error occurred while stopping the connection resources. See adjacent log messages for more details.
ART.0118.5034E Adapter Runtime (Connection): Connection type <factoryType> does not exist in adapter <adapterName>.
Cause: WmART was unable to locate the specified connection factory in the specified adapter.
ART.0118.5035E Adapter Runtime (Connection): Unable to create connection <aliasName>. Internal error occurred while
creating connection factory of type <factoryType>.
Cause: WmART was unable to create the specified connection factory for the connection. See adjacent log
messages for more details.
ART.0118.5036E Adapter Runtime (Connection): Unable to configure connection manager.

Cause: WmART was unable to create a Connection Manager. See adjacent log messages for more details.
ART.0118.5037E Adapter Runtime (Connection): Cannot create ResourceAdapterMetaData object. CCI Connection Factory is
not an instance of WmConnectionFactory.
Cause: The method ConnectionDataNodeManager.createCCIConnectionFactory could not get the
ResourceAdapterMetaData object for a connection factory.

ART.0118.5040E Adapter Runtime (Connection): Unable to get adapter service templates for connection <aliasName>.
Cause: WmART failed to locate any adapter service templates for the specified connection.
Response: Do not configure an adapter service with a connection for which no adapter service templates exist.
Try another connection.
ART.0118.5041E Adapter Runtime (Connection): Unable to get connection status for connection resource <resourceName>.
Cause: WmART was unable to obtain connection state information for the specified connection.
ART.0118.5042E Adapter Runtime (Connection): Unable to enable connection resource <resourceName>.

ART.0118.5043E Adapter Runtime (Connection): Unable to disable connection resource <resourceName>.

ART.0118.5044E Adapter Runtime (Connection): Unable to shutdown connection resource <resourceName>.

ART.0118.5046E Adapter Runtime (Connection): Unable to get a connection to resource <resourceName>. Resource not
available.
Cause: WmART could not locate a connection factory for the specified connection.
ART.0118.5047E Adapter Runtime (Connection): Unable to get a connection to resource <resourceName>. Internal error
occurred while restarting connection.
Cause: An error occurred while creating the connection.

ART.0118.5048E Adapter Runtime (Connection): Unable to get adapter service templates for connection resource
<resourceName>.
Cause: WmART failed to locate any adapter service templates for the connection.
Response: Do not configure an adapter service with a connection for which no adapter service templates exist.
Try another connection.
ART.0118.5049E Adapter Runtime (Connection): Unable to reset adapter connection <connectionNode>. Connection
<className> is not supported.
Cause: The method ConnectionResource.handleAdapterConnectionException reports that the specified
connection class is not derived from WmConnection.
ART.0118.5050E Adapter Runtime (Connection): Unable to reset adapter connection <connectionNode>. Unable to configure
connection manager.
Cause: The method ConnectionResource.handleAdapterConnectionException was unable to locate the
ConnectionManager or ConnectionManagerPropertiesBridge for this connection.
ART.0118.5051E Adapter Runtime (Connection): Unable to reset adapter connection <connectionNode>. Adapter type
<adapterName> does not exist.
Cause: The method ConnectionResource.handleAdapterConnectionException was unable to determine the
adapter type for this connection.
ART.0118.5052E Adapter Runtime (Connection): Unable to create connection. Connection resource <connectionNode> is
restarting.
Cause: The method ConnectionResource.createConnection has been called against a connection resource in the
restarting state.

ART.0118.5053E Adapter Runtime (Connection): Unable to get a connection to resource <resourceName>.

Cause: WmART failed to create a connection because it could not communicate with the back-end connection
resource.
Response: Check independently that the target resource is communicating and that it can be reached from the
connection. If the condition persists, contact webMethods Customer Care. Please have the following
ART.0118.5054E Adapter Runtime (Connection): Unable to reset adapter connection <connectionNode>.

Cause: An error occurred while trying to restart the specified connection. Additional details may appear in
adjacent log messages.
ART.0118.5055E Adapter Runtime (Connection): Unable to get adapter service templates for connection resource
<connectionNode>.
Cause: The method ConnectionResourceState.getInteractionSpecsSupported failed to locate the
ResourceAdapterMetaData associated with specified connection.
ART.0118.5056E Adapter Runtime (Connection): Unable to create connection for connection resource <connectionNode>,
connection type <connectionType>.
Cause: The method ConnectionResourceState.createConnection failed to get the Connection object for the
specified connection.
ART.0118.5057E Adapter Runtime (Connection): Adapter Runtime was unable to initialize <quantity> connection resources
for the adapter "<adapterName>".
Cause: com.wm.pkg.art.ns.ConnectionDataNodeManager.startConnectionResources detected failures in
starting connection nodes for the specified adapter.

ART.0118.5058E Adapter Runtime (Connection): Adapter Runtime was unable to stop <quantity> connection resources for
the adapter "<adapterName>".
Cause: com.wm.pkg.art.ns.ConnectionDataNodeManager.stopConnectionResources detected failures in
shutting down connection nodes for the specified adapter.
ART.0118.5059E Adapter Runtime (Connection): Adapter Runtime was unable to stop connection resources for the
<quantity> adapter types.
Cause: com.wm.pkg.art.ns.ConnectionDataNodeManager.stopAllConnectionResources detected failures in
shutting down connection nodes.
ART.0118.5060E Adapter Runtime (Connection): Unable get properties for connection resource <connectionNode>.
Cause: An error occurred while fetching the specified connection's properties.
ART.0118.5061E Adapter Runtime (Connection): Unable to configure Connection Manager: Poolable property not set.
Cause: WmART failed to determine whether a connection should be pooled.
ART.0118.5062E Adapter Runtime (Connection): Unable to find connection <connectionNode>: error <errorText>.
Cause: An error was encountered while validating the specified connection.
ART.0118.5063E Adapter Runtime (Connection): Unable to start connection <connectionNode>: after <numberOfRetries>
attempt(s).
Cause: The startup of a connection pool has exceeded the maximum number of retires.
Response: Check the Integration Server error log for details on the retryable exception.

ART.0118.5064E Adapter Runtime (Connection): Cannot reconfigure connection <connectionNode>: it must be disabled first.
Cause: To update a connection, it must be disabled.
Response: Disable the connection and retry the update operation.
ART.0118.5065E Adapter Runtime (Connection): Cannot delete connection <connectionNode>: it must be disabled first.
Cause: To delete a connection, it must be disabled.
Response: Disable the connection and retry the delete operation.
ART.0118.5066E Adapter Runtime (Connection): Exception encountered processing <methodName> connection callback
method. The <operationName> operation will proceed.
Cause: An exception was encountered while executing the specified connection callback method.
Response: Look in the error log for details on the original exception. The callback processing did proceed even
though the error was encountered.
ART.0118.5067E Adapter Runtime (Connection): Unknown callback event type received on connection node:
<connectionNodeName>
Cause: An unknown connection callback was made.
ART.0118.5068E Adapter Runtime (Connection): Exception encountered processing <methodName> connection callback
method.
Cause: An exception was encountered while executing the specified connection callback method.
Response: Look in the error log for details on the original exception. When this error is received, the callback
processing did not continue.
ART.0118.5069E Adapter Runtime (Connection): Cannot create connection factory for connection <connectionName>.
Adapter type <adapterTypeName> does not exist.
Cause: The adapter associated with this connection is not registered.
Response: Verify the package dependencies are set correctly. Reload the adapter package, and retry the
operation.
ART.0118.5070E Adapter Runtime (Connection): Exception encountered creating the connection factory for connection
<connectionName>.
Cause: An exception was encountered creating the connection factory.

ART.0118.5071W Adapter Runtime (Connection): A non-fatal exception was encountered attempting to unregister
<connectionName>. The operation will proceed. See the error log for more details.
Cause: An exception was encountered trying to unregister the connection node.
Response: Look in the error log for details on the original exception. The unregister processing continued.
ART.0118.5072E Adapter Runtime (Connection): Adapter service <adapterServiceName> cannot use connection
<connectionName>. The adapter service and connection are from different adapters.
Cause: The user attempted to set the connection associated with a an adapter service; however, the adapter
service and connection were not from the same adapter.
Response: Retry the operation using a connection from the same adapter.
<connectionName>. The connection is already being used by a listener.
Cause: The user attempted to use a connection in an adapter service; however, the connection is already being
used by a listener.
Response: Retry the operation using a connection that is not already being used by a listener.
ART.0118.5074E Adapter Runtime (Connection): "<connectionName>" is not a valid connection name for adapter
<adapterName>
Cause: The user attempted to use a connection in a polling notification or listener; however, the connection was
not part of the same adapter.
Response: Retry the operation using a connection from the same adapter.
ART.0118.5075E Adapter Runtime (Connection): Listener <listenerName> cannot use connection <connectionName>. The
connection is already being used by and adapter service or polling notification.
Cause: The user attempted to use a connection in a listener; however, the connection is already being used by a
polling notification or an adapter service.
Response: Retry the operation using a connection that is not already being used by a polling notification or
adapter service.
ART.0118.5076E Adapter Runtime (Connection): Polling notification <notificationName> cannot use connection
<connectionName>. The connection is already being used by a listener.
Cause: The user attempted to use a connection in a polling notification; however, the connection is already
being used by a listener.
Response: Retry the operation using a connection that is not already being used by a listener.

<connectionName>. The connection does not support this adapter service template.
Cause: The user attempted to use a connection for an adapter service; however, the connection does not
support the adapter service.
Response: Retry the operation using a connection that supports the adapter service.
ART.0118.5078E Adapter Runtime (Connection): Minimum pool size must not be greater than maximum pool size.
Cause: The user attempted to set the minimum pool size to a value that is greater than the maximum pool size.
Response: Retry the operation specifying a minimum pool size that is lower than the maximum pool size.

BAA (Auditing)
BAA.0000.0046E could not get a JDBC connection from the pool.

Cause: The Integration Server could not obtain a connection to the database.
Response: Check that the database is running. Also check the Settings>JDBC Pool page of the Server
Administrator to make sure the connection pool has a sufficient number of connections.
BAA.0000.0047I Warning: Pending audit events <eventNumber> is <percentage>% of threshold <threshold>.

Cause: The Integration Server is approaching the threshold for pending audit events. This threshold, and the
point at which the Integration Server should start issuing warnings about it, are configured on the
watt.server.auditDBSize and watt.server.auditThreshold configuration properties.

BAF (File System Persistence)
BAF (File System Persistence)
BAF.0003.0072E Warning: Pending audit events <eventNumber> is <percentage>% of threshold <threshold>.

Cause: The Integration Server tried to start a transaction, but couldn't because the fsdata.allowtxnwait property
is not set to "true".
Response: Contact webMethods Customer Care. Be prepared to provide logs and the version number and
patch level for the Integration Server and your operating system.

BAP (Master Password)
BAP.0004.0001E Encryptor: HARD-CODED encryptor code is invalid: <code>.

Cause: As part of outbound password processing, the Integration Server tried to register a user-written
encryptor, but the encryptor returned a null or empty string for the encryptor code.
Response: Correct the problem with the encryptor.
BAP.0100.0002E Can not use null <element>.

Cause: While processing outbound passwords, the Integration Server found an unexpected null value. The
element might be one of the following: master password, logger, data store, encryptor, handle, secure string,
default encryptor, sanity encryptor. In any case, this error reflects a problem with how outbound password
handling has been configured.
Response: Make sure that the following outbound password configuration files reside on the Integration
Server:
config/txnPassStore.dat
config/empw.dat
config/configPassman.cnf
config/passman.cnf
See the "Outbound Passwords" section of the "Managing Server Security" chapter of the "webMethods
Integration Server Administrator's Guide" for information about these files. If you cannot determine the source
of the problem, contact webMethods Customer Care.
BAP.0100.0004E Verification of current master password failed.

Cause: When trying to update the master password, an administrator entered the wrong value for the existing
master password.
Response: Enter the existing master password correctly.
BAP.0100.0005E Invalid master password expiration interval: <interval>.

Cause: An administrator entered an invalid expiration interval for the master password.
Response: Enter a non-negative integer that is no greater than 366. Refer to the "Outbound Passwords" section
of the "Managing Server Security" chapter of the "webMethods Integration Server Administrator's Guide" for
information about the expiration interval.
BAP.0100.0008E Cannot store password after failed sanity check.

Cause: A user or Integration Server subsystem tried to update a stored outbound password but could not
because the Integration Server is in safe mode. The Integration Server enters safe mode when it detects a
problem with the master password or outbound passwords at start up. When in safe mode, the Integration

Server is not connected to any external resources, except the server's own external repository. To prevent
further problems with the passwords, the Integration Server rejects any requests to update the outbound
passwords while in safe mode.
Response: Check the following possible causes:
- The master password file, outbound password file, or both are corrupted or out of sync with each other.
- An administrator entered the wrong master password when prompted.
- OS locale or default encoding has changed.
Refer to the "Outbound Passwords" section of the "Managing Server Security" chapter of the "webMethods
Integration Server Administrator's Guide" for more information.
BAP.0100.0009E Cannot retrieve password after failed sanity check.

Cause: A user or an Integration Server subsystem tried to update a stored outbound password but could not
BAP.0100.0011E Cannot remove password after failed sanity check.


BAP.0100.0012E Cannot verify master password after failed sanity check.

- You entered the wrong master password when prompted.
BAP.0100.0013E Cannot update master password after failed sanity check.

Cause: An administrator tried to change the master password but could not because the Integration Server is in
safe mode. The Integration Server enters safe mode when it detects a problem with the master password or
outbound passwords at start up. When in safe mode, the Integration Server is not connected to any external
resources, except the server's own external repository. To prevent further problems with the passwords, the
Integration Server rejects any requests to update the outbound passwords while in safe mode.
BAP.0100.0014E Cannot set master password expiration interval after failed sanity check.
Cause: An administrator tried to change the expiration interval for the master password but could not because
the Integration Server is in safe mode. The Integration Server enters safe mode when it detects a problem with
the master password or outbound passwords at start up. When in safe mode, the Integration Server is not
connected to any external resources, except the server's own external repository. To prevent further problems
with the passwords, the Integration Server rejects any requests to update the outbound passwords while in
safe mode.

BAP.0103.0001E Invalid file name: <fileName>.

Cause: The Integration Server detected a problem with the outbound password store. This file is specified on
the outbound.password.field.fileName= property in the passman.cnf file. Possible causes are that the
operating system cannot find the file or that another process already has it open.
Response: Check to see if the name is specified correctly in the passman.cnf file and that it exists in the specified
location. If another process has the file open, terminate that process and try again.
BAP.0103.0006E Problem opening FileInputStream from <fileName>.

Cause: The Integration Server detected a problem with the outbound password store. The name of this file is
specified on the outbound.password.field.fileName= property in the passman.cnf file. Possible causes are that
the operating system cannot find the file or that another process already has it open.
location. Check the server.log for other messages that indicate the nature of the problem. If another process has
the file open, terminate that process and try again.
BAP.0103.0008E Problem reading data from <fileName>.

Cause: The Integration Server detected a problem with the file specified as the outbound password store. The
name of this file is specified on the outbound.password.field.fileName= property in the passman.cnf file.
Possible causes are that the operating system cannot find the file or that another process already has it open.
BAP.0103.0009E Problem opening FileOutputStream to <fileName>.

Cause: The Integration Server detected a problem with the file specified as the outbound password store. The

BAP.0103.0011E Problem writing data to <fileName>.

Cause: The Integration Server detected a problem while trying to write to the outbound password store. The
BAP.0103.0012E Cannot begin a new transaction, already in progress.

Cause: The Integration Server encountered an error when a user-written program tried to use the Integration
Server code that handles outbound passwords. Specifically, the code attempted to begin a new transaction
while a previous transaction was still in progress.
Response: Refactor the user-written code to avoid nested and overlapping transactions.
BAP.0103.0013E Cannot commit a new transaction, already in progress.

Server code that handles outbound passwords. Specifically, the program is attempting to commit a transaction
while a previous transaction is still in progress.
BAP.0103.0014E Cannot rollback a new transaction, already in progress.

Server code that handles outbound passwords. Specifically, the program attempted to rollback a transaction
while a previous transaction was still in progress.
BAP.0104.0001E New master password can not be null or empty.

Cause: An administrator entered a blank value when trying to change the master password for outbound
passwords.
Response: Specify a valid password.
BAP.0104.0002E New master password must be different from the current master.
Cause: An administrator tried to change the master password, but specified a value that is the same as the
current password.
Response: Enter the master password again, this time specifying a different value.

BAP.0104.0003E New master password must be different from the previous saved masters.
Cause: The Integration Server keeps track of recent master passwords and does not let you reuse one until a
specified number of different passwords have been used in the interim.
Response: Specify a password that has not been recently used.
If you want to reuse a previously used master password sooner, you can change the repeatLimit value in the
configPassman.cnf file. See the "Outbound Passwords" section of the "Managing Server Security" chapter in
the "webMethods Integration Server Administrator's Guide" for instructions.
BAP.0104.0007E Retrieved null /empty master file: <fileName>.

Cause: The Integration Server detected a problem with the outbound password store. The name of this file is
specified on the outbound.password.field.fileName= property in the passman.cnf file.
location.
BAP.0104.0009E Retrieved null /empty master array.

Cause: To prevent you from reusing old master passwords too soon, the Integration Server keeps track of them
in the config/empw.dat file. The Integration Server issues this error when it cannot find the old passwords
because this file is missing or corrupted or because the configuration is pointing to the wrong file.
Response: Check the master.password.field.fileName= record in the config/configPassman.cnf file. By default,
this record points to config/empw.dat. Verify that the file specified on this record exists and is not corrupted. If
the file is missing, you can restore it from a backup.
Important: If you restore a file, it is important to restore other configuration files at the same time, so that they
stay in synch. Before restoring any files, see the "Outbound Passwords" section of the "Managing Server
Security" chapter of the "webMethods Integration Server Administrator User's Guide" for instructions.
If the record is pointing to the wrong file, you can update the record. See the "Outbound Passwords" section of
the "Managing Server Security" chapter of the "webMethods Integration Server Administrator User's Guide"
for instructions on updating the config/configPassman.cnf file.
Note: You can change how soon the Integration Server will let you reuse a previously used master password
by changing the repeatLimit value in the configPassman.cnf file. See the "Outbound Passwords" section of the
"Managing Server Security" chapter of the "webMethods Integration Server Administrator User's Guide" for
instructions.
BAP.0105.0001E Invalid encryption code: <code>.

Cause: One of the following problems occurred with an outbound password:
- The Integration Server tried to decrypt an outbound password, but the encryptor used to encrypt the
password no longer exists in the configuration file.

- User-written code tried to store a password to the outbound password store, but the encryption code it
specified is not registered with the Integration Server.
Response: Correct the program that submitted the indicated encryption code, or correct the configuration to
register the encryptor.
BAP.0105.0002E Cannot use a null key for encryption.

Cause: A program or application called a password management routine but passed a null value for the
encryption key. This is an internal error.
BAP.0105.0003E Cannot encrypt a null string.

BAP.0105.0004E Cannot use a null key for decryption.

Contact webMethods Customer Care.

ISC (IS Core)
ISC (IS Core)
ISC.0006.0013E Peer certificate is not present.

Cause: The Integration Server cannot retrieve the peer certificate chain from a client.
Response: Update your client program so that it provides a valid peer certificate to the Integration Server.
ISC.0006.0014E SSL handshake failed on port <portNumber> because peer certificate is not in IS Certificate Map, transfer is
terminated
Cause: While trying to connect to the Integration Server, a client presented a certificate that is not contained in
the store of client certificates that are mapped to Integration Server users.
Response: To import the client certificate to the Integration Server and map it to a valid user, go to the Server
Administrator and click Security>Certificates>Configure Client Certificates. For additional information about
certificate mapping, refer to the "Managing Server Security" chapter of the "webMethods Integration Server
Administrator's Guide."
ISC.0006.0015E Peer certificate chain is not trusted

Cause: While trying to connect to the Integration Server, a client presented a certificate that is not trusted by the
Integration Server.
Response: Add the certificate to the trusted certificates directory for the Integration Server. The name of this
directory is specified on the Server Administrator under Security>Certificates. For more information about
trusted certificates, refer to the "Managing Server Security" chapter of the "webMethods Integration Server
Administrator's Guide."
ISC.0006.0016E SSL handshake failed on port <portNumber>, transfer is terminated

Cause: An IOException occurred during the SSL handshake portion of a client's attempt to connect to the
Integration Server at the indicated port.
Response: Check the server log and error log for possible causes for the error.
ISC.0009.0012E Failed to create certificate: <certificateName>.

Cause: The certificate specified in the Configure Client Certificates settings has a bad X509Certificate format.
Response: Make sure that the .der file specified in Configure Client Certificates settings is valid.
ISC.0009.9001U Certificate chain broken: not linked properly.

Cause: The certificate chain is out of order.
Response: Obtain a valid certificate chain.

ISC.0009.9002E Error in certificate chain.

Cause: The certificate chain is invalid.
Response: Obtain a valid certificate chain.
ISC.0009.9003U Certificate contains an unsupported critical extension.

Cause: The Integration Server does not support the critical extension contained in the certificate.
Response: Provide a feature request to webMethods Client Services.
ISC.0018.0001U Unable to read MIME types file.

Cause: During startup, the Integration Server was unable to read the MIME types from the file "mime.types",
which is located on the <IntegrationServer_dir>\lib directory. The most likely reason is that this file is
corrupted.
Response: Contact webMethods Customer Care for a copy of this file.
ISC.0018.9101U returning unused object!

Cause: The Integration Server encountered an internal error.
ISC.0018.9102U runnable target is null.

ISC.0018.9201U index <position> out of range of table <numberOfRows>.

Cause: The Table class issued an error because the index number exceeded the size of the table.
Response: Examine the use of the Table class in your application and make sure that the index number passed
to the API does not exceed the size of the table.
ISC.0018.9301U Unlocking thread is not owner.

ISC.0018.9501E Failed to complete transaction: <errorMessage>.


ISC (IS Core)
ISC.0018.9502U Unable to read item from disk: <errorMessage>.

ISC.0018.9503U Checkpoint: <errorMessage>.

ISC.0042.0002E Unsupported Encoding: <encodingName>.

Cause: The Integration Server did not recognize the encoding of the document. Therefore, the default encoding
will be used.
Response: If the Integration Server successfully uses the default encoding, no action is necessary. Otherwise,
change the supplied document so that it has a valid encoding.
ISC.0042.9005U URI <uri> not declared at node <nodeName>.

Cause: The webMethods Integration Server encountered an internal error.
ISC.0042.9006U Node reference is null.

ISC.0042.9007U Node is not XML.

Cause: The pub.xml:getXMLNodeIterator service failed to execute because the node object supplied was not an
XML node.
Response: Examine the service input and make sure the "node" parameter represents an XML node, not an
HTML node.
ISC.0042.9008U Moving window mode is only available when iterating over XML nodes.
Cause: The pub.xml:getXMLNodeIterator service failed to execute because the XML node supplied did not
represent a whole XML document.
Response: Examine the service input and make sure the "node" parameter represents an entire XML document,
not an element of an XML document.

ISC.0042.9009U Moving window mode is not available with SAX parsers.

Cause: The pub.xml:getXMLNodeIterator service failed to execute because the moving window mode is not
available with SAX parsers.
Response: Switch to the webMethods parser instead of the SAX parser.
ISC.0042.9011U SAX parsers do not expose enough DTD info; try selecting the expandDTD option.
Cause: The pub.xml:loadXMLNode service failed to execute because it used a SAX parser. The Integration
Server does not support SAX parsers because they do not expose enough DTD information.
Response: Switch to the webMethods parser instead of the SAX parser.
ISC.0042.9012U First node of region not found in node parameter.

Cause: The pub.web:createRegions service failed to execute because the "regions" parameter did not correctly
specify the first node of the region.
Response: Examine the service input for the "regions" parameter and check the query specified for identifying
the first node. Make sure the query specified will correctly identify the first node.
ISC.0042.9013U Last node of region not found in node parameter.

Cause: The pub.web:createRegions service failed to execute because the "regions" parameter did not correctly
specify the last node of the region.
Response: Examine the service input for the "regions" parameter and check the query specified for identifying
the ending node. Make sure the query specified will correctly identify the ending node.
ISC.0042.9101E Parser Interrupted.

ISC.0042.9201U Incorrect character encoding (<java CharConversionException error message>).

Cause: An incorrect encoding was specified to interpret the characters.
Response: Use the correct encoding to read the characters.
ISC.0042.9301E References to external entities from within internal entities are not supported, as with the present reference
to external entity <entity name>.
Cause: The parser does not support external general entity references.
Response: Define an internal entity instead of a external entity.

ISC (IS Core)
ISC.0042.9302E External general references are not supported, as with the present reference to external entity <entity name>.
Cause: The parser does not support external general entity references.
Response: Define an internal entity instead of a external entity.
ISC.0042.9303E Can't configure SAX for HTML.

Cause: SAX parser can only handle XML files and should not be used to parse HTML files.E126
Cause:
Cause: The SAX parser can only accept XML files; it should not be used to parse HTML files.
Response: Use the default parser to parse HTML files.
ISC.0042.9304E Can't resolve reference <delimiter><refNameStr>;

Cause: Cannot resolve the reference. The entity reference ( e.g. &a;) is not defined in the XML files.
Response: Define the entity reference in the XML file.
ISC.0042.9305E Invalid GE reference in entity text.

Cause: The syntax of the Entity Reference is wrong.
Response: Correct the syntax. Use either &a; or %a; if it's inside a DTD.
ISC.0042.9306U <entity type><entity name> recursively includes itself via <child entity type><child entity name>.
ISC.0042.9307U A name token must follow <![.

Cause: The XML or DTD document contains the characters "<![" that are not followed by a name token.
Response: Provide a name token after "<![".
ISC.0042.9308U Missing '[' at start of conditional section.

Cause: The beginning of the conditional section of the XML or DTD document is missing the character "[".
Response: Add "[" at the start of the conditional section.
ISC.0042.9309U XML document terminated in middle of CDATA section.

Cause: The XML document contains a syntax error in the CDATA section.
Response: Make sure the CDATA section is closed with the characters "]]>".

ISC.0042.9310U DTD INCLUDE/IGNORE section found in XML or DTD document content.

ISC.0042.9311U Unrecognized construct <![<construct>.

Cause: The XML or DTD document contains a syntax error following the characters "<![". Only IGNORE or
INCLUDE can follow "<![".
Response: Replace the invalid construct with IGNORE or INCLUDE.
ISC.0042.9312U DTD include section not properly terminated.

Cause: The DTD document contains an error in the INCLUDE section. It is not terminated properly.
Response: Make sure the INCLUDE section is closed with the characters "]]>".
ISC.0042.9313U DTD conditional section terminated but never started.

Cause: The DTD document contains an error in the conditional section. It is terminated but never started.
Response: Make sure the conditional section starts correctly.
ISC.0042.9314U DTD not properly terminated.

Cause: The DTD document is not terminated properly.
Response: Make sure the DTD is terminated properly.
ISC.0042.9315U Entity declaration is missing entity name.

Cause: The entity name was missing from an entity declaration in an XML or DTD document.
Response: Provide the entity name in the entity declaration.
ISC.0042.9316U Expecting literal or external ID in entity declaration.

Cause: The literal or external ID was missing from an entity declaration in an XML or DTD document.
Response: Provide the literal or external ID in the entity declaration.
ISC.0042.9317U XML or DTD document terminates in middle of element declaration.

Cause: The XML or DTD document terminates in the middle of an element declaration.
Response: Make sure that the XML or DTD document terminates correctly.

ISC (IS Core)
ISC.0042.9318U ATTLIST element name not found.

Cause: The XML or DTD document is missing the ATTLIST element name.
Response: Provide a name for the ATTLIST element.
ISC.0042.9319U ATTLIST attribute name not found.

Cause: The XML or DTD document is missing the ATTLIST attribute name.
Response: Provide a name for the ATTLIST attribute.
ISC.0042.9320U Enumeration attribute is missing enumeration values in ATTLIST declaration.

Cause: The XML or DTD document contains an error in an enumeration attribute. The ATTLIST declaration is
missing enumeration values.
Response: Provide the enumeration values for the ATTLIST declaration.
ISC.0042.9321U Missing ')' in ATTLIST declaration for an enumeration attribute.

Cause: The XML or DTD document contains an error in an enumeration attribute. The ATTLIST declaration is
missing the character ")".
Response: Add the character ")" to the ATTLIST declaration.
ISC.0042.9322U External ID is missing the system ID.

Cause: The XML or DTD document is missing the system ID. For example, "<!DOCTYPE a SYSTEM>".
Response: Provide the system ID. For example, "<!DOCTYPE a SYSTEM http://www.test.com/a.dtd>".
ISC.0042.9323U PE ref missing terminating ';'.

Cause: The XML or DTD document contains an error in the parameter entity reference. It is missing the
terminating character ";".
Response: Add the character ";" to the parameter entity. For example, "%a;".
ISC.0042.9324U Attempted to parse HTML with a 3rd party XML parser.

Cause: The HTML files are being parsed with third-party XML parsers.
Response: Only use webMethods' parser to parse HTML files.
ISC.0042.9325U Element <element name> is missing end tag.

Cause: The XML or DTD document contains an incomplete element structure. For example, "<a></a>".
Response: Add an end tag to the XML or DTD document. For example, "<a></a>".

ISC.0042.9326E Error in tree structure.

ISC.0042.9327U Expecting </<expected name>> got </<actual name>>.

Cause: The XML or DTD document contains an end tag that does not match the start tag. For example,
"<a>".
Response: Make sure that the start and end tag names match.
ISC.0042.9328E Error: namespace prefix <namespace prefix> not defined for element <element localName>.
Cause: The XML or DTD document contains an element that has an undefined namespace prefix.
Response: Define the namespace prefix for the element. For example, 'xmlns:a="http://test.com"'.
ISC.0042.9329U No namespace declaration defined for attribute <namespace prefix>:<attribute localName> in element
<namespace prefix>:<element localName>.
Cause: The XML or DTD document contains an attribute that has an undefined namespace prefix.
Response: Define the namespace prefix for the attribute.
ISC.0042.9330U Malformed start tag: duplicate '<'

Cause: The XML or DTD document contains a start tag that has the duplicate character "<". For example, "<<a>".
Response: Remove the duplicate character "<".
ISC.0042.9331U Malformed end tag <tag name>: missing ''>''.

Cause: The XML or DTD document contains an end tag that is missing the character ">". For example,
"<a:b>sth.</a:b".
Response: Add the character ">" to the end tag.
ISC.0042.9332E Malformed entity reference: &<illegal text>

Cause: The Integration Server encountered a malformed entry while parsing an XML document. One service
that might throw this error is the pub.xml:xmlNodeToDocument service.
Response: Resend the XML document with legal XML syntax, that is, with the malformed entity corrected. For
customers who prefer to allow the malformed entries (pre 6.5 behavior), the watt.server.xml.enforceEntityRef
configuration has been added. Set this property to false to prevent the Integration Server from throwing an
exception when the XML parser detects a malformed entity.

ISC (IS Core)
ISC.0049.0013E Set: <errorMessage>.

Cause: While saving or loading a flow service, the Integration Server encountered a problem with the base64
encoding of a Map operation.
ISC.0049.9001E FlowExit ''<label>'' -- no valid ancestor to exit from $loop.

Cause: In a flow service, the Exit operation failed because an ancestor loop was not found.
Response: Move the Exit operation to a Loop/Repeat step or set the exit-on property to a value other than
$loop.
ISC.0049.9002E get: complex path is not supported.

Cause: A Flow service tried to perform a get operation on a complex path, but the Integration Server does not
support complex path types. This is an internal error.
Response: Call webMethods Customer Care.
ISC.0049.9003E put: complex path is not supported.

Cause: A Flow service tried to perform a put operation on a complex path type, but the Integration Server does
not support complex path types. This is an internal error.
ISC.0049.9004E delete: complex path is not supported.

Cause: A Flow service tried to perform a delete operation on a complex path, but the Integration Server does
not support complex path types. This is an internal error.
ISC.0049.9005E Input validation for service "<serviceName>" failed: "<errorMessage>".

Cause: During service execution, the Integration Server detected that the contents of the pipeline did not
conform to the specified input schema. (The input schema is specified on the Input tab of the Flow service in
the Developer. )
Response: Ensure that the inputs in the pipeline match the schema specified on the input tab of the Flow
service, or disable pipeline validation for this service.

ISC.0049.9006E Output validation for service "<serviceName>" failed: "<errorMessage>".

Cause: Upon completion of a service, the Integration Server detected that the contents of the pipeline did not
conform to the specified output schema. (The output schema is specified on the Output tab of the Flow service
in the Developer. )
Response: Ensure that the outputs in the pipeline match the schema specified on the output tab of the Flow
service, or disable pipeline validation for this service.
ISC.0049.9007E Failure creating input validator for "<serviceName>".

Cause: During execution of a Flow service, the Integration Server determined that it could not create an input
Validator from the parameters provided.
ISC.0049.9008E Failure creating output validator for "<serviceName>".

Cause: During execution of a Flow service, the Integration Server determined that it could not create an output
Validator from the parameters provided. This is an internal error.
ISC.0049.9012E Cannot define 'switch' and use label conditions at "<flowElementName>".

Cause: The Integration Server tried to perform a Branch operation, but the Flow Branch properties were
specified incorrectly. Specifically, the "evaluate labels" property was set to "true" while the "switch" property
specified an expression. This is not a valid combination.
Response: On the Flow Branch properties screen, either specify a switch with "evaluate-labels" set to false, or
do not specify a switch and set "evaluate-labels" to true.
ISC.0049.9013E Timeout at ''<Flowstep_label || type>''.

Cause: A step in a flow service exceeded its timeout value before returning.
Response: This is desired behavior. Examine the underlying services that did not return in time.
ISC.0049.9014E Scope ''<scope>'' not found or invalid .

Cause: At runtime, the Integration Server could not resolve a flow step. The scope resolved to a non-IData
object.
Response: Make sure that the path in the scope resolves to an IData object at runtime.
ISC.0049.9015E FlowExit ''<label>'' - label not found: ''<fromLabel>''.

Cause: In a flow service, the Exit operation failed because it could not locate the label in a previous flow step.
Response: Make sure that an ancestor flow step has a label that matches the one in the Exit step.

ISC (IS Core)
ISC.0049.9016E Invalid scope path.

Cause: At runtime, the Integration Server could not resolve a flow step. The scope resolved to a non-IData
object.
Response: Make sure that the path in the scope resolves to an IData object at runtime.
ISC.0049.9019I More than one copy into the path with different common parents(s).
Cause: From the Developer, under a single map step, you tried to make maps to two different document fields
under a common parent, but the source documents have different dimensions.
Response: Separate the maps into two different steps.
ISC.0049.9024E Cannot make the copy from: <elementName1> to: <elementName2>.

Cause: While executing a flow mapping operation, the Integration Server determined that it could not copy one
element to another because the elements were of incompatible types.
Response: Make sure that the types are compatible and have the same dimensions.
ISC.0049.9025E Invalid source path.

Cause: While trying to perform a Flow Map copy, the Integration Server determined that no source path was
specified.
Response: In the Developer, make sure that a source path is specified.
ISC.0049.9026E Invalid target path.

Cause: While trying to perform a Flow Map copy, the Integration Server determined that no target path was
specified.
Response: In the Developer, make sure that a target path is specified.
ISC.0049.9027E Error at <serviceName> - Transformers cannot loop over list elements.

Cause: A service tried to map a list of elements to a single element in a Flow Map step.
Response: Do not map a list of elements to a single element in a Flow Map step.
ISC.0049.9100U No closing delimiter found.

Cause: While executing a flow service, the Integration Server detected an expression that was missing a closing
delimiter. Many expressions expect certain delimiters to appear in pairs, such as quotes, parentheses, etc.
Response: Make sure that for each open delimiter there is a properly nested closing delimiter.

ISC.0049.9102U Unexpected end of expression.

Cause: The expression specified for a Flow step or a trigger has a syntax error and does not represent a valid
expression.
Response: Examine the expression specified for the Flow step or the trigger. Refer to Appendix D in the
"webMethods Developer User's Guide" for the correct syntax usage, and correct the error.
ISC.0049.9103U Too many parts to the expression.

Cause: The expression specified for a Flow step or a trigger has a syntax error and does not represent a valid
expression.
ISC.0049.9104E Not an expression.

Cause: While executing a Flow service, the Integration Server detected that a trigger or flow condition contains
an invalid expression.
Response: Check the syntax of the expression.
ISC.0049.9105U Unmatched parentheses.

Cause: The expression specified for a flow step or a trigger has a left parenthesis "(", but doesn't have a
matching right parenthesis ")".
ISC.0049.9106U Expected an expression.

Cause: The expression specified for a flow step or a trigger has a syntax error and does not represent a valid
expression.
ISC.0050.0017E Error encoding schema in FlowMap <exception>.

Cause: While saving a flow service, the Integration Server encountered an error trying to encode the input or
output of a Map operation.

ISC (IS Core)
ISC.0050.0018E Error decoding schema in FlowMap <exception>.

Cause: While loading a flow service, the Integration Server encountered an error trying to decode the input or
output of a Map operation.
ISC.0062.0002E CreateRegions createRegions type not supported.

Cause: The pub.web:createRegions service failed to execute because the input provided for the "regions"
parameter was not an instance of IData[ ].
Response: Examine the service input make sure the "regions" parameter specifies an instance of IData[ ]. See the
"webMethods Integration Server Built-In Services Reference" for descriptions of the input parameters.
ISC.0062.0003U GenerateQueryString <errorMessage> setValues <nodeID>.

ISC.0062.0004E GenerateQueryStrings createFields type not supported.

ISC.0062.0005E GenerateQueryStrings createNodeIDs type not supported.

ISC.0062.0006E GenerateQueryStrings the bind failed.

ISC.0062.0007U GetDocAsTable nodeTypeToString: <typeName> unknown type.

ISC.0062.0011E MakeRules.makeRecord ERROR ConnectParticleName:<name>.


ISC.0062.0014E QueryDocWithIdentity createFields type not supported:<objectName>.

ISC.0062.0016E queryXMLNode createFields type not supported:<objectName>.

ISC.0062.0018U DocumentToXMLString boundNode argument is null.

Cause: The pub.xml:documentToXMLString service failed to execute because the required "document"
parameter was missing. This parameter specifies the name of the document to be converted to XML.
Response: Examine the service input and make sure it specifies a value for the "document" parameter.
ISC.0062.9001U boundNode parameter is null.

Cause: The pub.xml:documentToXMLString service failed to execute because the required "document"
parameter was missing.
Response: Examine the service input and make sure it contains the document to be converted in an Idata object.
ISC.0062.9002U Namespace prefix name '<prefixName>' for uri <uri> is not legal XML name <streamName>.
Cause: The pub.xml:documentToXMLString service failed to execute because it detected illegal characters in
the namespace prefix of the document to be converted. The Integration Server flags invalid characters in the
namespace prefix only if the value for the "enforceLegalXML" parameter is set to "true".
Response: To resolve this error, do one of the following:
(1) Set the input for the "enforceLegalXML" parameter to "false". This causes the service to produce an XML
fragment.
(2) Make sure the input for the "nsDecls" parameter specifies a namespace prefix that starts with a letter or the
underscore "_" character. In addition, it can only contain letters, digits, and the period ".", hyphen "-", and
underscore "_" characters.

ISC (IS Core)
ISC.0062.9003U Illegal parameter value. <numberString> is too many root elements in boundNode. Number
attributes:<numberString>.
Cause: The pub.xml:documentToXMLString service failed to execute because the document to be converted
contains multiple root elements. The Integration Server flags this condition only if the input for the
"enforceLegalXML" parameter is set to true.
Response: Examine the service input and make sure the "enforceLegalXML" parameter is set to "false". This will
cause the service to produce an XML fragment composed of the multiple elements that were not enclosed
within a root element.
ISC.0062.9004U Attribute name '<attrName>' is not legal XML name.

Cause: The pub.xml:documentToXMLString service failed to execute because the prefix that designates the
keys that contain attributes contains illegal characters. The Integration Server flags this condition only if the
input for the "enforceLegalXML" parameter is set to true.
(1) Set the input for the "enforceLegalXML" parameter to "false" . This will cause the service to produce an
XML fragment.
(2) Make sure the input for the "attrPrefix" parameter starts with a letter or underscore "_" character. In
addition, it can only contain letters, digits, and the period ".", hyphen "-", and underscore "_" characters.
ISC.0062.9005U Element name '<elementName>' is not legal XML name.

Cause: The pub.xml:documentToXMLString service failed to execute because the document being converted
contains illegal XML tag names. The Integration Server flags this condition only if the input for the
"enforceLegalXML" parameter is set to true.
(1) Set the input for the "enforceLegalXML" parameter to "false". This causes the service to produce an XML
fragment.
(2) Make sure the input for the "'document" parameter starts with a letter or underscore "_" character. In
addition, it can only contain letters, digits, and the period ".", hyphen "-", and underscore "_" characters.
ISC.0062.9006U Illegal parameter value. Document Type '<documentTypeName>' not found.

Cause: The pub.xml:xmlNodeToDocument service failed to execute because the "documentTypeName" was
specified, but the document it represents does not exist on the Integration Server's namespace.
Response: Examine the service input and make sure the "documentTypeName" parameter specifies the fully
qualified name of the document type. Remember that namespace element names are case-sensitive.

ISC.0062.9021U object' is null

Cause: The object to be validated does not exist in the pipeline.
Response: Link an XML node or document variable to the object variable in Service In.
ISC.0062.9022U <objectName>' - object does not exist.

Cause: The IS document type or IS schema specified for the conformsTo variable does not exist in the IS
Namespace.
Response: Change the value of conformsTo to be an IS document type or IS schema that exists in the IS
namespace.
ISC.0062.9023U conformsTo parameter is null.

Cause: While executing the pub.schema:validatePipeline service, the Integration Server determined that no
value was specified for the "conformsTo" property, which is a required parameter. This parameter specifies the
IS document or IS schema against which the Integration Server performs validation.
Response: Specify a value for the "conformsTo" parameter that is an IS document type or schema type that
exists in the IS namespace.
ISC.0062.9024U Integration Server does not support this type of object in validation <objectName>.
Cause: The object to be validated is not one of the types supported by validation.
Response: Currently, only XML, pipeline, and document (IData object) validation are supported.
ISC.0062.9101U start query type of field <regionName> is null.

Cause: The pub.web:createRegions service failed to execute because the value for "queryType" was not
supplied for the "start" field inside the "regions" parameter.
Response: Examine the service input and make sure that the input value passed for the "queryType" field for
the "start" field inside the "regions" parameter is either "XQL" or "WQL".
ISC.0062.9102U start query string of field <regionName> is null.

Cause: The pub.web:createRegions service failed to execute because the value for "query" was not supplied for
the "start" field inside the "regions" parameter.
Response: Examine the service input and make sure that the input value passed for the "query" field for the
"start" field inside the "regions" parameter is not empty.

ISC (IS Core)
ISC.0062.9103U end query type of field <regionName> is null.

Cause: The pub.web:createRegions service failed to execute because the value for "queryType" was not
supplied for the "end" field inside the "regions" parameter.
Response: Examine the service input and make sure that the input value passed for the "queryType" field for
the "end" field inside the "regions" parameter is either "XQL" or "WQL".
ISC.0062.9104U end query string of field <regionName> is null.

Cause: The pub.web:createRegions service failed to execute because the value for "query" was not supplied for
the "end" field in the "regions" parameter.
Response: Examine the service input and make sure that the input value passed for the "query" field for the
"end" field in the "regions" parameter is not empty.
ISC.0062.9105U node parameter is null.

ISC.0062.9106U illegal null result of start query for region <regionName>.

Cause: The pub.web:createRegions service failed to execute because it detected a null region when looking for
the beginning of the region to create. The server flagged this error because the "nullok" parameter was set to
"false" for the start query.
Response: Examine the service input for the "nullok" parameter. If you want the service to execute even if the
start query returns a null region, change the value of the "nullok" parameter from "false" to "true" .
ISC.0062.9107U illegal null result of end query for region <regionName>.

the end of the region to create. The server flagged this error because the "nullok" parameter was set to "false"
for the end query.
end query returns a null region, set the value of the "nullok" parameter to "true".
ISC.0062.9108U illegal null result for field <regionName>.

the start and end of the region to be created. The server flagged this error because the "nullok" parameter was
set to "false" for the start and end queries.
resulting regions are null, set the values of the "nullok" parameters for the start and end queries to "true".

ISC.0062.9109U illegal non-null result for field <regionName>.

ISC.0062.9110U bindRegionsFromPipe pipe is null.

Cause: The pub.web:createRegions service failed to execute because no inputs were specified for the service.
Response: Examine the service input. Make sure it specifies the correct values for the input parameters and that
the input pipeline is not empty.
ISC.0062.9112U name of region <index> is null.

Cause: The pub.web:createRegions service failed to execute because the name to be assigned to the resulting
region was not specified.
Response: Examine the service input for the "name" field in the "regions" parameter and make sure it is not
null.
ISC.0062.9113U CreateRegions node parameter of <regionName> is null.

Cause: The pub.web:createRegions service failed to execute because the XML node from which you want to
create regions was missing.
Response: Examine the service input for "node" parameter and make sure it is not null.
ISC.0062.9114U CreateRegions node parameter of incorrect type.

Cause: The pub.web:createRegions service failed to execute because the node object from which you want to
create regions was not an XML node.
Response: Examine the service input for "node" parameter and make sure it specifies an instance of the
com.wm.lang.xml.Node class. Typically, you use the pub.xml:loadXMLNode service to produce an XML node
object.
ISC.0062.9115U node parameter null when processing field <fieldName>.

Cause: The pub.xml:queryXMLNode service failed to execute because the XML node to be queried was
missing.
Response: Examine the service input and ensure that the "node" parameter contains the name of the XML node
you want to query. You can obtain an XML node object by using the pub.xml:loadXMLNode or
pub.xml:xmlStringToXMLNode service or an XML content handler.

ISC (IS Core)
ISC.0062.9118U result type of field <fieldName> is null.

Cause: The pub.xml:queryXMLNode service failed to execute because the result type was not specified.
Response: Examine the service input for "ResultType" field in the "fields" parameter and make sure it is not
null.
ISC.0062.9120U GenerateQueryStrings String queryType parameter must not be null.

ISC.0062.9121U GenerateQueryStrings Node node parameter must not be null.

ISC.0062.9122U GenerateQueryStrings String[] identities parameter must not be null.

ISC.0062.9123E GenerateQueryStrings bind failed.

ISC.0062.9124E GenerateQueryStrings IData node type not supported.

ISC.0062.9125U identities unknown type: <objectName>.

ISC.0062.9126U GenerateQueryStrings nodeID: <nodeID> is not in the document subtree defined by the result set of the
parent field's query.

ISC.0062.9127U bindFieldsFromPipe pipe is null.

ISC.0062.9128U bindFieldsFromPipe <index> of <size> is null.

ISC.0062.9130U reference node of <nodeName> is null.

ISC.0062.9131U node parameter of incorrect type.

ISC.0062.9132U query type of field <fieldName> is null.

ISC.0062.9133U identities unknown type for field.

ISC.0064.0001E HttpContext cannot clone self.

ISC.0064.0012U Class not found: <className>.

Cause: The Integration Server encountered an internal error because it could not find a class in the namespace.

ISC (IS Core)
ISC.0064.0018U Unable to instantiate class: <className>.

Cause: The Integration Server encountered an internal error because it could not instantiate a class in the
namespace.
ISC.0064.9015E FTP AUTH command failed with error code <ftpReturnCode>

Cause: An FTP client sent an AUTH command to establish an FTPS connection with the Integration Server, but
the command failed with the indicated return code.
Response: Check your FTP documentation for the possible causes of the FTP return code. In addition, check the
server log and error log for possible causes for the error.
ISC.0064.9016E FTP AUTH command failed with error <errorMessage>

Cause: An FTP client sent an AUTH command to establish an FTPS connection with the Integration Server, but
the command failed.
Response: Check your FTP documentation for the possible causes of the FTP error message. In addition, check
the server log and error log for possible causes for the error.
ISC.0064.9017E FTP PBSZ command failed with error code <ftpReturnCode>

Cause: An FTP client sent a PBSZ command to establish a secure connection between the client and Integration
Server, but the command failed with the indicated return code.
ISC.0064.9018E FTP PROT command failed with error code <ftpReturnCode>

Cause: An FTP client sent a PROT command to establish a secure connection between the client and Integration
Server, but the command failed with the indicated return code.
ISC.0064.9101E Bad Request.

Cause: The Integration Server failed to execute the HTTP proxy request because the required Host field was
not supplied.
Response: In the client application, examine the logic that builds the HTTP request to ensure that it produces a
valid proxy request and specifies HOST in its Host request-header field.

ISC.0064.9102U Not Implemented.

Cause: The Integration Server failed to execute the HTTP proxy request because the method supplied is not
implemented by the Integration Server.
Response: In the client application, examine the logic that builds the HTTP request and make sure that it only
uses HTTP GET and POST to submit the request to the server.
ISC.0064.9103E Bad Gateway.

Cause: The Integration Server, while acting as a gateway or proxy, could not connect to the internal Integration
Server to fulfill the request. Possible causes are that the internal server was unavailable or that connections
were interrupted by a temporary network outage.
Response: Examine the status of the internal Integration Server. Verify that it is up and running and try the
request again.
ISC.0064.9306U Connection was closed during read.

Cause: The Integration Server failed to read the HTTP request from a client application or the HTTP response
from another web server because the other side closed the connection.
Response: Make sure that the connection between the client and the server is available.
ISC.0064.9313E Cannot write to output after opening input.

Cause: The data is being posted again to the site after already being posted.
Response: Only post the data once.
ISC.0064.9321U expected a header name.

Cause: The header name is empty. For example, ": value". Since there is nothing before ":", there is no header
name (i.e. it is empty).
Response: Make sure to provide a valid header name.
ISC.0064.9322E expecting <character string1> (<integer value of the char>) got <character string2> (<integer value of the
char>) context: <the header>.
Cause: There is no ":" character in a header name value pair. For example, if an entire header line is "Content-
Type text/xml", there should be a ":" character in it. It should be "Content-Type: text/xml".
Response: Make sure that the ":" character exists in the header name value pair.

ISC (IS Core)
ISC.0064.9324E Server Error: <error message>.

Cause: The remote HTTP site returned an HTTP code between 500 and 599, inclusive. This indicates that the
remote site encountered an internal error.
Response: Check the remote HTTP site to see what is wrong.
ISC.0064.9401U Content does not match the content type: <mimeType>.

ISC.0064.9402E Invalid input stream.

Cause: A pub.mime service tried to create a MIME data object, but it encountered an I/O error when trying to
read the input stream. A likely cause is that the input stream is closed.
Response: Make sure the input stream is not closed.
ISC.0064.9403E Could not parse input stream.

Cause: A pub.mime service tried to create a MIME data object, but the input stream or string was empty or in a
format other than stream or string.
Response: Make sure the input is in stream or string format.
ISC.0064.9405E Bad Stream.

Cause: A pub.mime service encountered an error while trying to create a MIME data object using an
unsupported stream type.
Response: Do not use unsupported stream types.
ISC.0064.9406E Invalid Content-Type header.

Cause: During execution of the pub.mime:createMimeData service, the Integration Server detected an invalid
content type in the "mime header" parameter. The server issues this message only if the resulting data is a
multi-part message.
Response: Refer to RFC 2045 at http://www.ietf.org/rfc/rfc2045.txt for the syntax and descriptions of the content
type header field.
ISC.0064.9407U Data key is null.


ISC.0064.9408E Content Type is invalid or missing.

Cause: A service tried to add an element to the body of a message. As part of this process, the pub.mime service
tried to add an element to the MIME object, but no content was provided or the content-type is either invalid
or missing from the message header.
Response: Check the headers of the message and ensure that a valid content type is specified.
ISC.0064.9409E Invalid body part.

Cause: A service tried to add an element to the body of a message. As part of this process, the pub.mime service
tried to add an element to a MIME object, but the content type specified in the message header was invalid. A
possible reason is that it does not conform to the MIME header standard.
Response: Make sure that a valid content type is specified in the message header.
ISC.0064.9410E Invalid Object: <objectName>.

Cause: A pub.mime service tried to add an invalid element to the body of a message. The element must be an
InputStream or MimeData object.
Response: Make sure to use only an InputStream or MimeData object when adding body parts to a message.
ISC.0064.9413U Null mime object received.

Cause: The MIME service failed to execute because the input supplied is a null MIME object.
Response: Examine the service input and make sure it specifies a MIME object that is not null. For example, you
can use the pub.mime:createMimeData service to produce an IData object before performing other operations.
ISC.0064.9414U No data in buffer!

ISC.0064.9415U Encoding <encoding> is not supported

Cause: A client used the pub.client.ftp service to retrieve data from a remote FTP(S) server, but the encoding
specified by the service is not supported by the Integration Server.
Response: Correct the client program so that it specifies a supported encoding method.
ISC.0066.9101E Invalid Key or key length.

Cause: The Repository Server of the Integration Server encountered an internal error.

ISC (IS Core)
ISC.0066.9102U Duplicate key.

ISC.0066.9103U No ValuesHash found for this key.

ISC.0066.9104U DirValuesHash corrupted, missing file <fileName> for key <key>.

ISC.0066.9105U No ValuesHash object.

ISC.0066.9106U ValuesHash has been deleted.

ISC.0066.9107U Key already exists in container.

ISC.0066.9108E Put failed.

ISC.0066.9109E Could not obtain pooled connection for RDBValuesHash operation.


ISC.0066.9110E Invalid table name for RDBValuesHash.

ISC.0066.9111U The table name must not be null.

ISC.0066.9112U Database <dbUrl> has been disabled.

Cause: The database used to store the data is disabled.
Response: Enable the database.
ISC.0066.9201E Could not acquire lock for key: <key>.

Cause: The Repository Server of the Integration Server failed to get a lock for the key. Another user may be
working on the entry.
Response: Perform the operation again.
ISC.0066.9202U No Share or Exclusive lock for key: <key>.

Cause: The application does not have the proper lock to perform this operation.
Response: In the client application, examine the logic to make sure that it has the correct lock to perform the
operation.
ISC.0066.9203U Entry not locked.

Cause: A user tried to update or remove an entry from the repository, but the entry was not locked. This is an
internal error.
ISC.0066.9204U Data for update is stale.

Cause: The data entry was removed from the storage system by the database administrator or the application.
The user is not able to update that entry.
Response: No action can be taken, since the data entry is not in the storage system.

ISC (IS Core)
ISC.0067.0003U findPrimaryServer() exception: <errorMessage>.

Response: Make sure that you have followed the steps mentioned in the "webMethods Integration Server
Clustering Guide" to configure Integration Server clustering. If the configurations seem correct and the servers
have the same environments and the issue still occurs, contact webMethods Customer Care.
ISC.0067.0006U refreshClusterInfo() exception: <errorMessage>.

ISC.0067.0009U isPrimaryServer(); negotiatePrimaryServer() exception: <errorMessage>.

Response: Make sure that you have followed the steps mentioned in "webMethods Integration Server
Clustering Guide" to configure the clustering. If the configurations seem correct and the servers have the same
environments and the issue still occurs, contact webMethods Customer Care.
ISC.0067.0010U isPrimaryServer() exception: <errorMessage>

Response: Make sure that you have followed the steps described in the "webMethods Integration Server
Clustering Guide" to configure clustering. If you cannot identify the cause of the problem, contact
ISC.0067.0013E initRemoteRepositoryServer() exception: Could not create registry.

ISC.0067.0014U initRemoteRepositoryServer() exception: <errorMessage>.

Cause: The Integration Server failed to bind to the RMI server running on the host where the Repository Server
is located.
Response: Restart the Repository Server. If the problem persists, contact webMethods Customer Care.
ISC.0067.0017U registerWithCluster() negoiation exception: <errorMessage>.

Cause: An internal error occurred while the Repository Server negotiated to be the primary server in a cluster
of Repository Servers.
Response: Check the Repository Server configuration and restart the server. If the problem persists, contact

ISC.0067.0018U registerWithCluster() exception: <errorMessage>.

Cause: An internal error occurred while the Repository Server added itself to a cluster of Repository Servers.
Response: Check the Repository Server configuration and restart the server. If the problem persists, contact
ISC.0067.0023U getClusterInfo() exception: <errorMessage>.

ISC.0067.0027U findPrimaryServer() exception: <errorMessage>.

Response: Make sure that you have followed the steps mentioned in "webMethods Integration Server
ISC.0067.0028U unlockEntry() exception: <errorMessage>.

ISC.0067.0031U registerSecondaryServer() servers=<exception message>.

Cause: The Repository Server configuration may be incorrect.
Response: Make sure that the server is configured properly.
ISC.0067.0032U registerSecondaryServer() exception: <exception message>.

ISC.0067.0035U registerPrimaryServer() exception: <exception message>.

ISC.0067.0038U negoiatePrimaryServer() exception: <exception message>.

Cause: The Repository Server configuration is incorrect.

ISC (IS Core)
ISC.0067.0042U notifySecondaryServers() exception: <errorMessage>.

ISC.0067.0045U lookupServer() exception: <errorMessage>.

Response: Make sure that you have followed the steps mentioned in the "webMethods Integration Server
ISC.0067.0068U RC.get() Exception: <errorMessage>.

Cause: The Repository Server is down.
Response: Make sure the Repository Server is up and running.
ISC.0067.0069U RC.add() Exception: <exception message>.

ISC.0067.0070U RC.put() Exception: <exception message>.

ISC.0067.0071U RC.remove() Exception: <exception message>.

ISC.0067.0072U RC.containsKey() Exception: <exception message>.

ISC.0067.0073U RC.keys() Exception: <exception message>


ISC.0067.0075U RC.unlockEntry() Exception: <exception message>.

ISC.0067.0076U RC.getKey() Exception: <exception message>.

ISC.0067.0099E Repository Server initialization failed: <errorMessage>.

Cause: The Integration Server failed to start the Repository Server because it is not configured correctly or the
<IntegrationServer_dir>/config/repository2.cnf file is missing or corrupt.
Response: Make sure that you are following the instructions in the "webMethods Clustering Guide" to set up
the Repository Server. Also check the content of the repository2.cnf file to make sure that it is not missing or
corrupt. If the file is corrupt, repeat the steps to configure the Repository Server.
ISC.0067.0101E Repository Server shutdown failed: <errorMessage>.

ISC.0067.0102U RC.isEntryLocked() Exception: <exception message>.

ISC.0067.0104E RMI Exception: Could not find registry.

ISC.0067.0105U shutdowmRepositoryServer() exception: <errorMessage>.

ISC.0067.0108U initRemoteRepositoryClient() exception: <errorMessage>.


ISC (IS Core)
ISC.0067.0114E Failed to create/obtain the repository context : <errorMessage>.

Cause: The Integration Server was unable to create or obtain the Repository context. This is an internal error.
ISC.0072.9001U Unknown service: <serviceName>.

Cause: The Integration Server encountered an internal error because it could not find a requested service in the
namespace.
ISC.0072.9002U Reporter died from IOException: <errorMessage>.

Cause: The Reporter.createTemplateFromFile() class issued an error because it could not read the template
from the supplied file.
Response: Examine the use of the Reporter class in your application and make sure that the application has
proper Read access to the template file.
ISC.0076.0005E BinCoder decode error creating Java serialized object. Excpt:<exception>.

Cause: The java.io.ObjectInputStream.readObject() service encountered an error while trying to decode a Java
serialized object.
For a ClassNotFoundException, the most likely cause is that a client performing a remote invoke placed a class
definition into the pipeline, but the class definition does not exist on the receiving Integration Server.
For an InvalidClassException, the most likely cause is that the class definition on the Integration Server does
not match the class definition placed in the pipeline by the client.
Response: Make sure that the originating client and the receiving Integration Server have the same class
definitions.
For other I/O exceptions, there might be corruption in the input stream; therefore, you should try the request
again.
ISC.0076.0008E XMLCoder decode exception: <exception>.

Cause: The Integration Server threw an exception while decoding an IDataXML encoded document.
Response: The document is corrupt. Contact webMethods Customer Care.

ISC.0076.0009E RPCBinCoder2 decode error for array class: <classname>.

Cause: The Integration Server encountered an error while trying to decode an array of remote objects. Class
definitions might be out of synch.
ISC.0076.0010E RPCBinCoder2 decode error for Codable class: <classname>.

Cause: The Integration Server encountered an error while trying to decode a codable class. Class definitions
might be out of synch.
ISC.0076.0011E RPCBinCoder2 decode error for as_String class: <classname>.

Cause: The Integration Server encountered an error while trying to decode an object that was encoded as a
String.
ISC.0076.0012E SOAP Encoding Registrar cannot register schema type <typeName>; schema type already exists.
Cause: The SOAP Encoding Registrar could not register the indicated schema type. This is a serious internal
error.
ISC.0076.0013E SOAP Message Coder cannot encode output data; pipeline does not match output signature.
Cause: The SOAP message coder could not XML-encode the results of a SOAP remote procedure call because a
variable appeared in the pipeline more than once.
Response: On the Integration Server, examine the target service to determine why it is not producing output
values that match the output signature. Correct the service's signature and/or logic after identifying the source
of the problem.
ISC.0076.0017E SOAP Message Coder error; no coder is registered for encoding style <styleName>.
Cause: The message coder encountered a serious internal error.
ISC.0076.0019E SOAP Message Coder cannot decode message; encoding style <styleName> is not a registered style.
Cause: The message coder could not decode the submitted XML because it does not support the specified
encoding style.
Response: Check the incoming XML and verify that the encodingStyle attribute is specified correctly and that it
specifies a style that the Integration Server supports.

ISC (IS Core)
ISC.0076.0020E Soap Message Coder warning; invalid HREF found <reference>.

Cause: The message coder could not resolve the href pointing to reference. A null value was produced instead.
Response: Examine the incoming XML and make sure that the specified reference points to an element that
exists in the body of the message.
ISC.0076.0030E Broker Coder warning; cannot parse value <dataValue>; using <objectString> instead
Cause: The Integration Server was not able to parse the document. There are two possible reasons: (1) the
document might be corrupted (2) the document is out of sync with the corresponding documents on the
Broker.
Response: Examine the document and make sure that it is not corrupted. Also, use Developer to synchronize
the document with the corresponding document on the Broker.
ISC.0076.0031E Broker Coder warning; cannot create an instance of <className>.

Cause: The Integration Server could not create an instance of the indicated class. This is an internal error.
ISC.0076.9002U incorrect IDataXMLCoder file format: no element 'IDataXMLCoder' found.

ISC.0076.9003U encoding <className>.

ISC.0076.9004U decoding: <typeName> ex:<exceptionMessage>.

ISC.0076.9005U decoding: boolean ex:<exceptionMessage>.


ISC.0076.9006U decoding: <className>.

ISC.0076.9007U decoding: No null-arg create method in class: <className>.

ISC.0076.9008U Unsupported RPC type: <versionNumber>.

Cause: The Integration Server RPC Bin Coder does not support the version specified in the input stream to be
decoded. This is an internal error.
ISC.0076.9009U Root element is null.

Cause: The flow.xml or node.ndf file is corrupt.
ISC.0076.9010U Sibling root element is null rootTag:<string> localName:<string> root:<string>.

Cause: The XMLCoder class issued an error because the supplied XML input stream cannot be decoded.
Response: Examine the use of the XMLCoder class in your application and make sure that the XML input
stream has the correct format and it only contains supported object types. If the error still occurs, use the
setIgnoreInvalid() class to set the flag to false so that XMLCoder ignores the unsupported object type that it
decodes.
ISC.0076.9011U illegal file format.

Cause: The service pub.flow:restorePipelineFromFile failed to execute because the file containing the saved
pipeline was not encoded with XMLCoder or IDataXMLCoder.
Response: Examine the file containing the saved pipeline and make sure it is not corrupt. If the file was saved
using the pub.flow:savePipelineToFile service, and it is not corrupt, contact webMethods Customer Care.
ISC.0076.9101E SOAP Encoding Registrar cannot register encoding style <styleName>; encoding style already exists.
Cause: The encoding registrar encountered a serious internal error.

ISC (IS Core)
ISC.0076.9102E SOAP Encoding Registrar cannot register Java type <typeName>; Java type already exists.
Cause: The encoding registrar encountered a serious internal error.
ISC.0076.9103E SOAP Encoding Registrar cannot register Schema type <typeName>; Schema type already exists.
Cause: The message code encountered a serious internal error.
ISC.0076.9104E SOAP Encoding Registrar cannot unregister Java type <typeName>; doesn't exist in the registry
Cause: The SOAP encoding registrar encountered a serious internal error.
ISC.0076.9105E SOAP Encoding Registrar cannot unregister Schema type <typeName>; doesn't exist in the registry.
Cause: The pub.xml:queryXMLNode service failed to execute because the SOAP encoding registrar
encountered a serious internal error while trying to unregister a Schema type.
ISC.0076.9201E SOAP Message Coder cannot decode message; no encoding style is specified.
Cause: The message coder could not decode the parameters in the SOAP message because the message does
not specify an encoding style.
Response: This error usually occurs because the SOAP "encodingStyle" attribute is missing, misplaced or
misspelled. Examine the RPC request that was submitted to the Integration Server and ensure that the SOAP
Envelope includes the "encodingStyle" attribute. Also check that the "encodingStyle" attribute has the proper
syntax and namespace.
ISC.0076.9202U SOAP Message Coder failure; a RuntimeException was thrown in the SOAP Coder.
ISC.0076.9203E SOAP Message Coder cannot decode message; Invalid number <value>.
Cause: The message coder could not decode an XML-encoded array because one of its dimensions is set to a
nonnumeric value.
Response: Check the incoming XML and make sure that the "arrayType" attribute specifies a positive integer.
For example, make sure it has not been inadvertently set to a nonnumeric value such as "A".

ISC.0076.9204E SOAP Message Coder cannot encode output data; pipeline does not match output signature, duplicate
variable <varName> in pipeline.
Cause: The message coder could not XML-encode the results of a SOAP remote procedure call because the
variable <varName> appeared in the pipeline more than once.
Response: On the Integration Server, examine the target service to determine why it is not producing output
values that match the output signature for <varName>. Correct the service's signature and/or logic after
identifying the source of the problem.
ISC.0076.9205E SOAP Message Coder cannot encode variable <varName>; variable does not have a valid XML name.
Cause: The message coder could not XML-encode the SOAP RPC request or response because the pipeline
contained the variable <varName>, whose name is not a valid name for an XML element.
Response: This error often occurs because the variable name contains a colon (:). Change the name of
<varName> to one that is also valid as an XML element name (or map <varName> to a new variable, and use
that variable as your SOAP RPC input or output parameter).
ISC.0076.9206E SOAP Message Coder error; no coder is registered for encoding style <styleName>.
ISC.0076.9208E SOAP Message Coder cannot decode message; cannot determine type of element <elementName>.
Cause: The message coder could not decode the XML-encoded parameters it has received, because the simple
element <elementName> has an unknown data type (for example, xsi:type="myDataType").
Response: Check the incoming XML and make sure the data type has been specified correctly. Also make sure
that it is using the correct namespace.
ISC.0076.9209E SOAP Message Coder cannot decode message; unable to create array for arrayType attribute value
<attValue>.
Cause: The message coder could not decode an XML-encoded array because it could not allocate an array of
the specified dimensions.
Response: Check the incoming XML and make sure that the arrayType attribute is specified correctly. For
example, make sure that it does not specify a negative dimension or an invalid array size (e.g., too many
dimensions or dimensions that are unrealistically large). If the array is unusually large or the server is
extremely very low on memory, the possibility also exists that this error was the result of an out-of-memory
condition.

ISC (IS Core)
ISC.0076.9210E SOAP Message Coder cannot decode message; arrayType attribute value <attValue> is malformed.
Cause: The message coder could not decode an XML-encoded array because it cannot understand the value of
the "arrayType" attribute.
Response: Check the incoming XML and make sure that the "arrayType" attribute is using the correct syntax.
For example, make sure that it is not missing a "[" symbol.
ISC.0076.9211E SOAP Message Coder cannot encode output data; pipeline does not match output signature, required
variable <varName> is missing.
Cause: The message coder could not transform the results of a SOAP remote procedure call because the
required variable <varName> was not in the pipeline.
Response: On the Integration Server, examine the target service to determine why it is not producing the
required output variables. Correct the service's signature and/or logic after identifying the source of the
problem.
ISC.0076.9212E SOAP Message Coder cannot encode output data; pipeline does not match output signature, extra variable
<varName> in pipeline.
ISC.0076.9301E Broker Coder does not support wire format version <versionNumber>. Latest supported format version is
<versionNumber>.
Cause: While attempting to process a document from the Broker, the Integration Server encountered an
internal error.
ISC.0076.9302E Broker Coder Encoding Registrar cannot register type coder for Java type <typeName>; this type coder
already exists.
internal error.
ISC.0076.9303E Broker Coder Encoding Registrar cannot register type coder for Schema type <typeName>; this type coder
already exists
internal error.

ISC.0076.9304E Broker Coder Encoding Registrar cannot unregister type coder for Java type <typeName>; this type coder
does not exist in the registry.
internal error.
ISC.0076.9305E Broker Coder Encoding Registrar cannot unregister type coder for Schema type <typeName>; this type
coder does not exist in the registry
internal error.
ISC.0076.9401E Broker Coder cannot encode document; the document, document type or both are null values.
Cause: While attempting to encode a document to be published, the Integration Server determined that the
document, the document type, or both are null values. This is an internal error.
ISC.0076.9402E Broker Coder cannot encode document; Broker document type name is missing
Cause: The subscribing Integration Server received a document from the Broker or a publishing Integration
Server, but was unable to encode the document because the document type name was missing from the event
subscription. There are three possible reasons: (1) the document to be encoded is corrupted (2) the document is
out of sync with the corresponding documents on the Broker (3) an internal error occurred.
Response: Examine the document to be encoded and use Developer to manually synchronize the document
with the Broker. Refer to "webMethods Building Integration Solutions Using Publication" for instructions. If
the error persists after the synchronization, contact webMethods Customer Care.
ISC.0076.9403E Broker Coder cannot decode document; byte[] is in wire format version <versionNumber>. Latest supported
format is version <versionNumber>.
Cause: The subscribing Integration Server was not able to decode an incoming document from the Broker or
the publishing Integration Server because the version of the Broker or publishing server is incompatible with
the version of the subscribing server.
Response: See the "webMethods Installation Guide" for supported configurations.
ISC.0076.9404E Broker Coder cannot encode document; the document, document type or both are null values
Cause: While attempting to process a document from the Broker, the Integration Server determined that the
document, the document type, or both are null values. This is an internal error.

ISC (IS Core)
ISC.0076.9405E Broker Coder cannot decode document; the document does not conform to the document type,
<documentTypeName>.
Cause: The subscribing Integration Server was not able to decode the incoming document from either the
Broker or the publishing Integration Server because the document type on the local Integration Server is out of
sync with the corresponding document types on the publishing Integration Server and the Broker.
Response: Use webMethods Developer to manually synchronize the publishable document type with the
Broker.
ISC.0077.0001E Config set local host error. Excpt:<errorMessage>.

Cause: During startup, the Integration Server was not able to set local host information from the values
specified on the "watt.net.localhost" property.
Response: Examine the value specified for property "watt.net.localhost". The value can either be a machine host
name or a string representing the machine's IP address, such as "localhost" or "127.0.0.1".
ISC.0077.0003S Cannot initialize password store with a null manager

Cause: Initialization of the code that manages outbound passwords failed. The most likely cause is a problem
with the outbound password configuration files.
Response: Make sure that the following outbound password configuration files reside on the Integration
Server:
config/empw.dat
config/passman.cnf
See the "Outbound Passwords" section of the "Managing Server Security" chapter of the "webMethods
Integration Server Administrator User's Guide" for information about these files and to determine whether
you can restore them. If you cannot determine the source of the problem, contact webMethods Customer Care.
ISC.0077.0004S Exception during <operation>, type<exceptionClass>, msg<exceptionMessage>

Cause: A problem occurred when the Integration Server tried to store or retrieve an outbound password or
retrieve an encryption code from the outbound password store.
Response: The outbound password data store, config/txnPassStore.dat, is probably corrupted. See the
"Outbound Passwords" section of the "Managing Server Security" chapter of the "webMethods Integration
Server Administrator User's Guide" for information about this file and how to restore it and other outbound
password configuration files. If you cannot determine the source of the problem, contact webMethods
Customer Care.

ISC.0077.0006E System property "<propertyName>" equals "<propertyValue>". This value is not valid. The property will now
be reset to its default value of "<defaultValue>".
Cause: The Integration Server detected an invalid value on the indicated configuration file property.
Response: Refer to the configuration properties appendix in the "webMethods Integration Server
Administrator's Guide" for a description of the property and its required values.
ISC.0077.9006E Could not determine encoding of file <fileName>.

ISC.0077.9007E Invalid encoding, <encoding>, specified for file <fileName>.

ISC.0077.9013U Document to XSD error: Field <fieldName> cannot be represented in XML Schema. The field name contains a
prefix but an XML Namespace property is not assigned to the field.
Cause: The Developer determined that the IS document type you are using to generate a WSDL document
contains a top-level variable whose name includes a prefix (that is, the name is in the format prefix:local
name). This variable is not associated with an XML namespace.
Response: Do one of the following:
(1) Associate the variable with an XML namespace by selecting the variable in Developer, selecting
Edit>Properties, and then typing the namespace for the variable in the XML Namespace field on the General
tab.
(2) Remove the prefix. Note that some protocols require the use of a prefix. Before removing the prefix, check
the service signature's input and output requirements as documented for each protocol in the "webMethods
Web Services Developer's Guide."
ISC.0077.9014U Document to XSD error: Field <fieldName> cannot be represented in XML Schema. The field name does not
conform to the XML NCName definition.
Cause: The Developer determined that the IS document type you are using to generate a WSDL document
contains field names that do not conform to the XML NCName definition.
Response: To resolve this error, rename the fields to conform to the Qname lexical rules specified in
http://www.w3.org/TR/REC-xml-names/#NT-QName and the XML namespace and local naming conventions
specified in http://www.w3.org/TR/REC-xml-names/#NT-NCName.

ISC (IS Core)
ISC.0077.9015E The amount of data needed is greater than the amount of data reserved.
Cause: A service needed to write a large amount of data to tspace, but the space the service reserved is not large
enough to hold the data.
Response: Update your program to reserve more tspace. If your program does not reserve tspace directly,
ISC.0081.0005E Could not create a unique ID for the trigger from the trigger's name.
Cause: The Integration Server was unable to create a unique identifier for the Trigger. This is an internal error.
Response: Try to recreate the trigger. If that fails, contact webMethods Customer Care. Be prepared to provide
logs and the version number and patch level for the Integration Server and your operating system.
ISC.0081.9003E Illegal argument: not a signature.

Cause: The specified path item is not a signature type in the service path information.
ISC.0082.9002I Unable to retrieve root element.

Cause: XML document is empty.
Response: Check that the document is being submitted properly.
ISC.0082.9003I Unable to locate a matching element declaration.

Cause: An undeclared element node is found in the instance document.
Response: Check to make sure that the document uses only declared elements.
ISC.0082.9004I [attributes] property must be empty.

Cause: This element carries attributes that are not expected.
Response: Check to make sure that the document only uses element attributes that are declared in the schema.
ISC.0082.9005I Eiement Information items are not allowed in [children] property.

Cause: This element contains child elements; however, the element declaration in the IS schema indicates that
the element does not contain any child elements.
Response: Check to make sure that the document properly conforms to the schema.

ISC.0082.9006I Unable to locate a matching attribute declaration.

Cause: This element carries an attribute that is not declared in the element declaration in the IS schema.
Response: Check to make sure that the document only uses element attributes that are declared in the schema.
ISC.0082.9007I Missing Attribute Information Item.

Cause: A required attribute is not found in this element node.
Response: Check to make sure that the document conforms to the schema.
ISC.0082.9008E Invalid value - does not match fixed value.

Cause: The instance document contains an invalid element body or attribute value. Specifically, the element
body or attribute value does not match a fixed value found in the declaration.
ISC.0082.9009I Child element <elementName> at position <location> is unexpected.

Cause: The element is not a valid child element or the sequence of child elements does not satisfy the order
specified in the corresponding element declaration or complex type definition.
ISC.0082.9010I Incomplete content - one or more child elements are expected.

Cause: The element is not a valid child element or the sequence of child elements does not satisfy the order
specified in the definition.
ISC.0082.9011I Unable to locate attribute declaration.

Cause: An attribute declaration is not found. It is possible that a dependent IS schema that contains this
attribute declaration was removed from the IS Namespace. For example, IS schema pub.schema.w3c:datatypes
references an attribute declaration (xml:lang) in pub.schema.w3c:xml . If you receive this error, it is possible
that pub.schema.w3c:xml was removed.
Response: Check to make sure that all of the attribute declarations referenced by the schema are present.
ISC.0082.9012I Unable to locate type definition.

Cause: A simple or complex type definition is not found. It is possible that a dependent IS schema that contains
this type definition was removed from the IS Namespace. For example, IS schema pub.schema.w3c:structures
references a type definition in pub.schema.w3c:datatypes. If you receive this error, it is possible that
pub.schema.w3c:datatypes was removed.
Response: Check to make sure that all of the type definitions referenced by the schema are present.

ISC (IS Core)
ISC.0082.9013I Unable to locate type definition <typeName>.

Cause: During execution of a Flow service, the Integration Server could not find a type definition that was
referenced by a schema. A possible cause is that the schema that contains the type definition was removed
from the Integration Server's namespace.
Response: Make sure that all of the type definitions referenced by the schema are present in the namespace
ISC.0082.9014I Unable to locate element declaration.

Cause: An element declaration is not found. It is possible that a dependent IS schema that contains the element
declaration was removed from the IS Namespace.
Response: Check to make sure that all the element declarations referenced by the schema are present.
ISC.0082.9015I Ambiguous content model in schema - not LL(1).

Cause: The schema content model is ambiguous. To resolve it, the processor must look ahead at least twice.
According to the XML specification, the processor should look ahead no more than once.
Response: Clean up the ambiguous content model.
ISC.0082.9016I unable to resolve QName: <localName:uri>.

Cause: The schema processor uses the namespaces declared in the instance document to resolve a QName to:
{Namespace URI} Local Name. However, the schema processor is unable to resolve the QName using the
namespace declarations in the instance document.
ISC.0082.9017I <typeName> is not validly derived from <declaredTypeName>.

Cause: This error occurs when the first type is used in a context where the second type is expected, and either
the first type is not the same as the second type or the first type is not validly derived from the second type.
Response: Check to make sure that the correct types are specified in the schema and that the correct
corresponding types are used in the document.
ISC.0082.9018E <typeName> is an abstract type and cannot be used directly to validate content.
Cause: The specified type is an abstract type that has been either declared or nominated. Abstract types cannot
be used to validate element content.
Response: Make sure to use only concrete types when validating element content.

ISC.0082.9019E <elementName> is an abstract element and cannot appear in an instance.

Cause: The element declaration identifies the element as an abstract element. Abstract elements cannot appear
in instance documents.
Response: Make sure to only use concrete elements in instance documents.
ISC.0082.9020I <QName> - xsi:type is used incorrectly (declared type is anonymous).

Cause: A type is nominated using xsi:type for an element whose declaration contains an anonymous type. A
new type cannot be derived from an anonymous type because new types can be derived only from named
types.
Response: Be sure to use only named types when declaring new types.
ISC.0082.9021E Contains invalid text.

Cause: The schema processor encountered an invalid piece of text. It is possible that the instance document
contains a simple type where element declarations are interspersed with text. Simple types cannot contain
element declarations.
ISC.0082.9022E The nillable value of <element name> is false, hence xsi:nil cannot appear in an instance.
Cause: The schema element cannot have an xsi:nil attribute when the nillable value of the element is set to
"false".
Response: Remove the xsi:nil attribute from the instance.
ISC.0082.9023E The value of xsi:nil is invalid.

Cause: The value specified for xsi:nil is not a valid value. Valid values are 0, 1, "true", and "false".
Response: Replace the invalid value with 0, 1, "true" or "false".
ISC.0082.9024E <Name of the Schema Element> cannot have content or child elements since xsi:nil is true.
Cause: The schema element cannot have content or child elements when the xsi:nil attribute is set to be "true".
Response: Remove the content or child elements from this element.
ISC.0082.9025I Missing Object.

Cause: A required document (IData object) or variable is missing from the input.
Response: Be sure that the arguments are being passed properly to the validator.

ISC (IS Core)
ISC.0082.9026I Undefined Object found.

Cause: A document (IData object) contains an orphan variable. (This message only appears if you cleared the
Allow unspecified fields check box on the Constraints tab of the Variable Properties dialog box.)
Response: Make sure that all variables are defined, or check the box to allow unspecified fields on the
constraints tab of the Variable Properties dialog box.
ISC.0082.9027I Dimension mismatch, List expected.

Cause: The value being validated is a scalar value or a multi-dimensional array (String table), however the
variable it is being validated against is a list (one-dimensional array).
ISC.0082.9028I Dimension mismatch, Single item expected.

Cause: The value being validated is an array value (a list or a table). The variable it is being validated against is
scalar.
ISC.0082.9029I Dimension mismatch, Table expected.

Cause: The value being validated is a scalar value or a one-dimensional array (list). The variable it is being
validated against is a two-dimensional array (table).
ISC.0082.9030I Type mismatch, String expected.

Cause: The value is being validated against a String variable, but the IS data type of the value is not a String.
ISC.0082.9031I Type mismatch, Document expected.

Cause: The value is being validated against an IS document type variable, but the IS data type of the value is
not an IS document type.
ISC.0082.9032I Type mismatch, Object expected.

Cause: The value is being validated against an Object variable, but the IS data type of the value is not an Object.

ISC.0082.9033I Java type mismatch; expected <JavaType1>, got <JavaType2>.

Cause: During execution of a Flow service, the validator expected an Object of the first Java type, but the
document contained an Object of the second Java type.
ISC.0082.9034I Field is absent, field must exist.

Cause: While processing a document, the validator expected an Object of the first Java type, but the document
contained an Object of the second Java type.
Response: Make sure the document conforms to the schema.
ISC.0082.9035E Value cannot be null, allow null value is false

Cause: During execution of a Flow service, the Integration Server determined that the document received is
null, but the setting to allow null values is disabled.
Response: Make sure that the document does not contain null values, or select the option to allow null values.
ISC.0082.9101E Document Type generation error: <errorNumber>.

Cause: The schema processor encountered an error in the XML Schema definition used to create an IS
document type.
ISC.0082.9106U Complex type <typeName> is recursive. webMethods Integration Server does not support creating a
document type from an XSD with a recursive complex type.
Cause: The XML Schema contains a recursive complex type definition. The Integration Server does not support
generating a document type from an IS schema containing a recursive complex type. This error only occurs
when you generate an IS document type from an XML Schema.
Response: Do not try to generate a document type from a schema containing a recursive complex type.
ISC.0082.9111E Element must be a document type, service or specification

Cause: While processing an input schema file, the Integration Server detected an element that was not defined
as a document type, service, or specification.
Response: Correct the XML schema input file.
ISC.0082.9112E The service does not have a valid signature

Cause: While processing an input schema file, the Integration Server determined that the service does not have
a valid signature.
Response: Add a valid signature to the service.

ISC (IS Core)
ISC.0082.9501I DTD is empty.

Cause: The DTD does not contain any information.
Response: Make sure that the DTD is valid.
ISC.0082.9502I NS Declaration is missing for prefix '<prefixName>'.

Cause: Warns that an XML Namespace prefix is used without declaring it.
Response: Declare the XML Namespace prefix before using it.
ISC.0082.9505I Name collision <detailedWarningMessage>.

Cause: Warns that an element type declaration is found in another schema with the same XML Namespace.
Response: Use a different XML Namespace.
ISC.0082.9701I Duplicate declaration found in this schema <folderName:schemaName> with the same target namespace.
Cause: Warns that an identical attribute declaration or element declaration is found in the specified schema
with the same target namespace. The schema processor creates the schema but does not include the duplicate
declaration. Instead, the schema contains a pointer to the first (original) declaration.
Response: None required.
ISC.0082.9702I Duplicate definition found in this schema <folderName:schemaName> with the same target namespace.
Cause: Warns that an identical simple type or complex type definition is found in the specified schema with the
same target namespace. The schema processor creates the schema but does not include the duplicate type
definition. Instead, the schema contains a pointer to the first (original) type definition.
Response: None required.
ISC.0082.9703I Duplicate declaration found in this schema definition.

Cause: A duplicate attribute or element declaration is found in the XML Schema definition.
Response: Make sure the XML Schema definition is valid.
ISC.0082.9704I Duplicate definition found in this schema definition.

Cause: A duplicate simple type or complex type definition is found in the XML Schema definition.
Response: Make sure the XML Schema definition is valid.

ISC.0082.9705I Definition not found.

Cause: A simple type or complex type definition is missing from the XML Schema definition.
Response: Make sure the data type definition is present in the XML Schema definition.
ISC.0082.9707I Base type definition not found.

Cause: A base type definition that is used to derive either a simple type or complex type is missing from the
XML Schema definition.
Response: Make sure the base type definition is present in the XML Schema definition.
ISC.0082.9709I Type derivation not OK: attribute declaration to be restricted is not found in the base type definition.
Cause: In a complex type derivation, an attribute declaration restricts the use of an attribute. However, this
attribute declaration is not found in the base type definition.
Response: Make sure that the attribute declaration is present in the base type definition.
ISC.0082.9710I Type derivation not OK: attribute declaration to be prohibited is not found in the base type definition.
Cause: In a complex type derivation, an attribute declaration prohibits the use of an attribute. However, this
attribute declaration is not found in the base type definition.
Response: Make sure that the attribute declaration is present in the base type definition.
ISC.0082.9712I Incorrect facet (s) specified: <typeName> throws <errorMessage>.

Cause: Constraining facets applied to the data type are incorrect or cannot be used with the data type.
Response: Use the error messages to determine which constraining facets to remove from the type definition.
ISC.0082.9713I Unable to resolve Qname.

Cause: Incorrect QName.
Response: Check the value of the QName.
ISC.0083.9001U Requested type not available.

Cause: The pub.xml:queryXMLNode service failed to execute because the Integration Server XQL query engine
encountered an internal error.

ISC (IS Core)
ISC.0083.9002E Tree type not supported.

Cause: The pub.xml:queryXMLNode service failed to execute because the supplied query object supplied was
not a valid XML Node object.
Response: Examine the service input and ensure it is a valid XML node object. You can invoke the
pub.xml:xmlStringToXMLNode or pub.xml:loadXMLNode service to obtain the document and transform it to
an XML node object before performing the query.
ISC.0083.9003U Expression is empty.

Cause: The pub.xml:queryXMLNode service failed to execute because no query expression was specified.
Response: Examine the logic and make sure that the query expression is not empty.
ISC.0083.9004U Node parameter is null.

Cause: The pub.xml:queryXMLNode service failed to execute because the XML Node to be queried was empty
or missing.
Response: Examine the XML node object submitted for query and make sure it is not null.
ISC.0083.9005U "<objectType>" object type not currently supported.

Cause: The pub.xml:queryXMLNode service failed to execute because the document submitted was not an
instance of an XML Node object. This service can obtain information from XML nodes only.
Note: An XML node is a special representation of an XML document that can be consumed by the Integration
Server. Most webMethods services that operate on XML documents require an XML node as input.
Response: Examine the document submitted and make sure that you have used
pub.xml:xmlStringToXMLNode or pub.xml:loadXMLNode service to convert the document to an XML Node
object before performing the query.
ISC.0083.9006E Regions are not supported on IData objects.

Cause: The pub.xml:queryXMLNode service failed to execute because it tried to perform a region query on an
IData object; the Integration Server does not support this type of query. Currently only XML node objects are
supported for region queries.
Response: Do not attempt to query regions on IData objects.
ISC.0083.9007U Source not available for IData objects.

Cause: The pub.xml:queryXMLNode service failed to execute because it tried to obtain information from a
Document (an IData object) instead of an XML Node. This service can obtain information from XML Nodes

only.
Response: Do not attempt to query the source from Documents (IData objects).
ISC.0083.9008U Recursion detected in IData at <queryString>; can't have recursion when query contains | or //.
Cause: The pub.xml:queryXMLNode service failed to execute because it tried to perform a query on a recursive
IData object, but the query contained "|" (a union operator) or "//" (a path operator). These operators are not
allowed when querying a recursive IData object.
Response: Do not attempt to query a recursive IData object when the query contains "|" or "//".
ISC.0083.9012U (' expected.

Cause: The pub.xml:queryXMLNode service failed to execute because it specified an incorrect syntax.
Specifically, the left-hand parenthesis "(" was missing after the "true" or "false" Boolean function.
Response: Examine the query expression and make sure it uses the correct syntax. There must be matching
parentheses after any "true" or "false" functions, e.g., true(), false().
ISC.0083.9013U )' expected.

Cause: The pub.xml:queryXMLNode service failed to execute because the right-hand parenthesis ")" was
missing after the "true" or "false" Boolean function.
Response: Examine the query expression and make sure it uses the correct syntax. There must be matching
parentheses after any "true" or "false" functions, e.g., true(), false().
ISC.0083.9014E Invalid boolean method: <methodName>.

ISC.0083.9015U Comparison requires an rvalue.

Cause: The pub.xml:queryXMLNode service failed to execute because the right-hand operand was not present
in the query. Left- and right-hand operands are required for a comparison query .
Response: Examine the query expression and make sure that both the left- and right-hand operands are
supplied.

ISC (IS Core)
ISC.0083.9016U Comparison righthand operand evaluates to more than one value.

Cause: The pub.xml:queryXMLNode service failed to execute a comparison query because the value of the
right-hand operand was not a scalar.
Response: Examine the query expression and make sure the value of the right-hand operand is a scalar or a
value that can be cast at runtime to a scalar.
ISC.0083.9017U Comparison operator is missing.

Cause: The pub.xml:queryXMLNode service failed to execute a comparison query because the expression
contained $any$ or $all$, but no comparison operator. A comparison operator must be specified in an
expression that contains $any$ or $all$.
Response: Examine the query expression and make sure it contains a comparison operator.
ISC.0083.9018U Only relative queries allowed inside filters.

Cause: The XQL query expression contains an absolute path inside a filter. For example, "book[/author]".
Response: Make sure that the XQL query expression contains a relative path inside the filter. For example,
"book[author]".
ISC.0083.9019U [' is not matched by ']'.

Cause: The pub.xml:queryXMLNode service failed to execute because the left-hand square bracket "[" was
specified but the right-hand square "]" bracket was missing. An expression that uses a filter operator or a
subscript operator must contain matching parentheses.
Response: Examine the query expression and make sure it contains matching brackets "[ ]" .
ISC.0083.9020U Filter brackets may only select nodes or attributes.

Cause: The pub.xml:queryXMLNode service failed to execute because a subquery within the "[ ]" was not a
node or attribute. A subquery must be a node or an attribute when a filter operation is used.
Response: Examine the query expression and make sure that the subquery contained within the "[ ]" is a node
or attribute.
ISC.0083.9021E Invalid or missing term.

Cause: The pub.xml:queryXMLNode service failed to execute because a query expression using a filter
operator specified an invalid term or no terms at all.
Response: Examine the query expression and make sure it specifies a valid term. Valid terms are: dot('.'), left
parenthesis('('), at('@'), and wildcard('*').

ISC.0083.9022U (' is not matched by ')'. Token '<token>' found.

Cause: The pub.xml:queryXMLNode service failed to execute because the query expression contained a left
parenthesis "(" that was not matched by a right parenthesis ")", but rather by another character. The query
expression must specify matching parentheses when a filter operator is used.
Response: Examine the query expression and make sure it contains matching parentheses "()".
ISC.0083.9023U (' is not matched by ')'. End of query found.

Cause: The pub.xml:queryXMLNode service failed to execute because the query expression contained a left
parenthesis "(" but no right parenthesis ")". A query expression must specify matching parentheses when a
filter operator is used.
Response: Examine the query expression and make sure it contains matching parentheses "()".
ISC.0083.9024E Invalid or misplaced term "<token>".

Cause: The pub.xml:queryXMLNode service failed to execute because an invalid character was specified in a
query expression that contains a filter operator. Valid characters are dot ".", left and right parentheses ''(" and
")", at "@", and wildcard "*".
Response: Examine the query expression and ensure that only valid characters are specified.
ISC.0083.9025E Invalid attribute name "<prefixName>".

Cause: The XQL query expression contains an invalid attribute name. This attribute belongs to a namespace.
For example, "//@prefix:123".
Response: Make sure that the XQL query expression contains a valid attribute name. For example,
"//@prefix:a123".
ISC.0083.9026E Invalid or missing attribute name.

Cause: The XQL query expression contains an invalid or undefined attribute name. For example, "//@123" or
"//@".
Response: Make sure that the XQL query expression contains a valid attribute name. For example, "//@a123".
ISC.0083.9027U attribute() takes a quoted string.

Cause: The pub.xml:queryXMLNode service failed to execute because the optional parameter passed to
attribute() function was not a quoted string.
Response: Examine the query expression and make sure that it uses the correct syntax and passes a quoted
string to the attribute() function.

ISC (IS Core)
ISC.0083.9028U attribute() incorrect attribute name "<attributeName>".

Cause: The XQL query expression contains an invalid attribute name inside the attribute(). For example,
"//book/attribute('123')".
Response: Make sure that the XQL query expression contains a valid attribute name inside the attribute(). For
example, "//book/attribute('a')".
ISC.0083.9030U count() takes a query parameter.

Cause: The XQL query expression contains a parameter in the count(), which is not allowed. For example,
"//book/count(1)".
Response: Make sure that the XQL query expression does not contain a parameter in the count(). For example,
"//book/count()".
ISC.0083.9031E Type <resultType> can't be cast to Date.

Cause: The pub.xml:queryXMLNode service failed to execute because the query engine returned a value that
could not be cast as a date.
Response: Examine the query expression and make sure it uses the correct syntax and specifies the correct
query.
ISC.0083.9032E date(<dateString>)<errorMessage>.
Cause: The pub.xml:queryXMLNode service failed to execute because the parameter passed to the XQL date()
function was not in a format that could be converted to a date.
Response: Examine the detailed error message and make sure that the string parameter passed to the XQL
date() function can be converted to a date.
ISC.0083.9033E date()<errorMessage> Error offset:<position>.

Cause: The pub.xml:queryXMLNode service failed to execute because the parameter passed to the XQL date()
function could not be parsed.
Response: Examine the detailed error message and the position provided in it and make sure that the string
parameter passed to the date() function in the query expression can be parsed to a date.
ISC.0083.9034E Invalid element name "<prefixName>".

Cause: The XQL query expression contains an invalid element name. This element belongs to a namespace. For
example, "//a:1".
Response: Make sure that the XQL query expression contains a valid element name. For example, "//a:b".

ISC.0083.9036U element() takes a quoted string.

Cause: The pub.xml:queryXMLNode service failed to execute because the optional parameter passed to XQL
element() function was not a quoted string.
Response: Examine the query expression and make sure it uses the correct syntax and passes a quoted string to
the element() function.
ISC.0083.9037U element() incorrect attribute name <parameterName>.

Cause: The XQL query expression contains an invalid parameter in element(). For example,
"/book/element("1")".
Response: Make sure that the XQL query expression contains a valid parameter name in element(). For
example, "/book/element("a")".
ISC.0083.9039E Type <resultType> can't be cast to Float.

Cause: The pub.xml:queryXMLNode service failed to execute because it expected a float, but the value it
received was not a float.
Response: Examine the query expression. Make sure it uses the correct syntax and specifies the query you
intended.
ISC.0083.9040U id() takes a quoted string.

id() function was not a quoted string.
the XQL id() function.
ISC.0083.9041E Type <resultType> can't be cast to Integer.

Cause: The pub.xml:queryXMLNode service failed to execute because it expected an integer, but the value it
received could not be cast as an integer.
Response: Examine the query expression. Make sure it uses the correct syntax and specifies the query you
intended.
ISC.0083.9042U name() takes a quoted string.

name() function was not a quoted string.
the XQL name() function.

ISC (IS Core)
ISC.0083.9043U name() requires a non-empty string.

Cause: The pub.xml:queryXMLNode service failed to execute because the parameter passed to the XQL name()
function was empty.
Response: Examine the query expression and make sure it uses the correct syntax and passes a non-empty
quoted string to the name() function.
ISC.0083.9044U node() must be used relative to a node.

Cause: The pub.xml:queryXMLNode service failed to execute because it specified an incorrect syntax for the
XQL node() function or tried to execute the function against a non-node object.
Response: Examine the query expression and make sure it uses the correct syntax for the node() function and
executes the function against a node.
ISC.0083.9045U region() must be used relative to a node.

XQL region() function or tried to execute the function against a non-node object.
Response: Examine the query expression and make sure it uses the correct syntax for the region() function and
executes the function against a node.
ISC.0083.9049U textnode() must be used relative to a node.

XQL textnode() function or tried to execute the function against a non-node object.
Response: Examine the query expression and make sure it uses the correct syntax for the textnode() function
and executes the function against a node.
ISC.0083.9051U (' missing after function or method name.

Cause: The pub.xml:queryXMLNode service failed to execute because a left-hand parenthesis "(" was missing
after the function or method name. The correct syntax is functionname() or methodname() .
Response: Examine the query expression and make sure that it uses the correct syntax for the function or
method.
ISC.0083.9052U Query contains truncated invocation.

Cause: The pub.xml:queryXMLNode service failed to execute because an incomplete expression was provided
for a function call. Specifically, the expression contained a left parenthesis "(" but the invocation parameter or
right parenthesis ")" was missing.
Examples:

function()
function(parameter
Response: Examine the query expression and make sure it uses the correct syntax.
ISC.0083.9053U )' must terminate parameter list.

Cause: The pub.xml:queryXMLNode service failed to execute because the right parenthesis ")" was missing
from the parameter list that was passed to the XQL function.
Response: Examine the query expression and make sure it uses the correct syntax and includes the right
parenthesis to terminate the parameter/parameter list.
ISC.0083.9054E missing function parameter.

Cause: The pub.xml:queryXMLNode service failed to execute because the parameter required by the XQL
function was not provided.
Response: Examine the query expression and make sure it uses the correct syntax and includes the required
parameter.
ISC.0083.9055E Invalid number of parameters in function or method "<name>".

Cause: The pub.xml:queryXMLNode service failed to execute because an invalid number of parameters were
passed to the XQL function or method.
Response: Examine the query expression and make sure it uses the correct syntax and passes the correct
number of parameters to the XQL function. See XQL Query Language at
http://www.w3.org/TandS/QL/QL98/pp/xql.html for method or function reference.
ISC.0083.9056U "<functionName> is not a recognized function name.

Cause: The pub.xml:queryXMLNode service failed to execute because an invalid XQL function name was
provided.
Response: Examine the query expression and make sure that it only uses the valid XQL functions. Integration
Server currently supports the following pre-defined functions: attribute(), Boolean(), comment(), count(),
date(), element(), float(), id(), integer(), name(), node(), not(), pi(), region(), textnode(), true(), false().
ISC.0083.9057U <methodName> is not a recognized method name.

Cause: The pub.xml:queryXMLNode service failed to execute because an invalid XQL method name was
provided.
Response: Examine the query expression and make sure that it only uses the valid XQL methods. Integration
Server currently supports the following pre-defined methods: basename(), count(), end(), index(),
namespace(), nodename(), nodetype(), nodetypestring(), prefix(), regex(), regexinsensitive(),
regexinsensitivematch(), regexmatch(), rawtext(), stringmatch(), source(), text(), value().

ISC (IS Core)
ISC.0083.9058U Methods may only be applied to nodes and attributes.

ISC.0083.9064U Query contains extraneous terms.

Cause: The pub.xml:queryXMLNode service failed to execute because there was a syntax error in the
expression. Specifically, there were extraneous terms in the expression.
Response: Examine the query expression and make sure it uses the correct syntax.
ISC.0083.9065E Cannot parse queries of type <queryType>.

Cause: The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an
internal error.
ISC.0083.9066U Left operand of / must be either a node or an attribute.

Cause: The pub.xml:queryXMLNode service failed to execute because the query expression specified the unary
child operator "/" but the value specified by the left-hand operand was not a node type or an attribute type.
Response: Examine the query expression and make sure the left-hand operand is a node or attribute.
ISC.0083.9067U Only relative queries allowed in relative paths.

Cause: The XQL query expression contains an absolute path inside another absolute path. For example,
"/x/(/y)".
Response: Make sure that the XQL query expression does not contain an absolute path embedded inside
another absolute path.
ISC.0083.9068U Left operand of // must be a node.

Cause: The pub.xml:queryXMLNode service failed to execute because the query expression specified the unary
child descendant operator "//" but the value specified by the left-hand operand was not a node.
Response: Examine the query expression and make sure the left-hand operand is a node.
ISC.0083.9069E Invalid subscript argument.

Cause: The pub.xml:queryXMLNode service failed to execute because no argument was supplied for the
subscript operator or the argument supplied was not an integer.
Response: Examine the query expression and make sure that a valid integer is provided for the subscript
operator.

ISC.0083.9070U Only values of the same type may be unioned.

Cause: The pub.xml:queryXMLNode service failed to execute a union operation because the left-hand operand
is not the same type as the right-hand operand.
Response: Examine the query expression and make sure that both operands are of the same type. Valid types
are node, attribute, string, integer, float, and Boolean.
ISC.0083.9071U <leftType> and <rightType> types are not comparable.

Cause: The pub.xml:queryXMLNode service failed to execute a comparison operation because the left-hand
operand is not the same type as the right-hand operand.
Response: Examine the query expression and make sure that the left-hand operand and right-hand operand are
of the same type. Valid types are node, attribute, string, integer, float, and Boolean.
ISC.0083.9072U The <relationType> relation is not defined on <resultType> types.

ISC.0083.9073U Unrecognized expression type "<expressionType>".

internal error.
ISC.0083.9076U generateQueryString only supports WQL, XQLVALUES and XQL types. Unsupported type "<queryType>".
Cause: The pub.xml:queryXMLNode service failed to execute because an expression attempted to evaluate an
unsupported type. The Integration Server currently only supports WQL,XQLVALUES and XQL.
ISC.0083.9077U Unknown TreeExpression type.

Cause: The Integration Server tried to process an unsupported type. This is an internal error. Currently only
the WQL, XQLVALUES and XQL types are supported.

ISC (IS Core)
ISC.0083.9078E Cannot cast "<stringValue>" to boolean.

Cause: The pub.xml:queryXMLNode service failed to execute because it attempted to cast a string value to a
Boolean type. The possible causes are: (1) the left-hand and right-hand operands specified with a comparison
operator were not of the same type (2) the value returned by the query was of an unexpected type.
Response: Examine the query expression and make sure it specifies the correct syntax and performs the query
you expected.
ISC.0083.9079E Cannot cast "<stringValue>" to a float.

float. The possible causes are: (1) the left-hand and right-hand operands specified with a comparison operator
were not of the same type (2) the value returned by the query was of an unexpected type.
you expected.
ISC.0083.9080E Cannot cast "<stringValue>" to an integer.

Cause: The pub.xml:queryXMLNode service failed to execute because it attempted to cast a string value to an
integer. The possible causes are: (1) the left-hand and right-hand operands specified with a comparison
you expected.
ISC.0083.9081E Cannot cast "<stringValue>" to a long.

long type. The possible causes are: (1) the left-hand and right-hand operands specified with a comparison
you expected.
ISC.0083.9083U XqlQuery.getStringWithIdentities: Query "<queryExpression>" does not yield strings:<stringValue>.

internal error.
ISC.0083.9084U XqlQuery.getString: Query "<queryExpression>" does not yield strings:<stringValue>

internal error.

ISC.0083.9085U XqlQuery: Query yields unknown type.

internal error.
ISC.0083.9086U XqlQuery.getNodeWithIdentities: Query "<queryExpression>" does not yield nodes.

internal error.
ISC.0083.9087U XqlQuery.getNode: Query "<queryExpression>" does not yield nodes.

internal error.
ISC.0083.9088U XqlQuery.getNodeArrayWithIdentities: Query "<queryExpression>" does not yield nodes.

internal error.
ISC.0083.9089U XqlQuery.getNodeArray: Query "<queryExpression>" does not yield nodes

internal error.
ISC.0083.9090U XqlQuery.getIData: Query "<queryExpression>" does not yield nodes.

internal error.
ISC.0083.9091U Query does not yield an IData instance as expected.

internal error.

ISC (IS Core)
ISC.0083.9092U XqlQuery.getIDataArray: Query "<queryExpression>" does not yield nodes.

internal error.
ISC.0083.9093U Query ''<queryExpression>"' does not yield only IData instances as expected.
internal error.
ISC.0083.9094E Floating point numbers must begin with a digit.

Cause: The pub.xml:queryXMLNode service failed to execute because an invalid query expression was
provided. Specifically, a floating point number was provided in an incorrect format. A digit must immediately
precede and follow the dot "." term. Examples of the correct format are "1.23" and "-0.99.". Examples of
incorrect formats are ".99" and "1.".
Response: Examine the query expression and make sure that it uses the correct format for floating point
numbers.
ISC.0083.9095U Unrecognized operator '$<operatorString>'.

Cause: The pub.xml:queryXMLNode service failed to execute because an expression contained an
unrecognized operator.
Response: Examine the query expression and make sure it only uses the valid operators specified in the XQL
specification. See XQL Query Language at http://www.w3.org/TandS/QL/QL98/pp/xql.html for more
information.
ISC.0083.9096E Invalid number: "<numberString>".

Cause: The pub.xml:queryXMLNode service failed to execute because the XQL query engine could not parse a
numberString to an integer or a float because the string does not represent an integer or float number.
Response: Examine the query expression and make sure that it uses the correct syntax. See XQL Query
Language at http://www.w3.org/TandS/QL/QL98/pp/xql.html for more information.
ISC.0083.9098U "<name>" is not a recognized function or method name.

Cause: The pub.xml:queryXMLNode service failed to execute because an invalid XQL function or method was
specified in the query expression.
Response: Examine the query expression and make sure that you only use a set of pre-defined XQL function
names or method names in the query. For a list of pre-defined functions and methods in XQL, see The XML
Query Language (XQL) at http://www.w3.org/TandS/QL/QL98/pp/xql.html.

ISC.0083.9099U Method requires Node tree for query "<queryExpression>".

internal error.
ISC.0084.9002E Resubmit data array cannot be null.

Cause: webMethods Monitor failed to resubmit the rejected document because the data array for resubmission
was not supplied.
Response: Examine the document to be resubmitted and make sure that it is valid and not empty.
ISC.0084.9003E Resubmit data cannot be null.

Cause: webMethods Monitor failed to resubmit the rejected document because the data for resubmission was
not supplied.
Response: Examine the document to be resubmitted and make sure that it is valid and not empty.
ISC.0084.9004E Auditcontexts cannot be null or empty.

Cause: webMethods Monitor failed to resubmit the rejected document because the "auditContext" field in the
data was either null or empty.
Response: Examine the document to be resubmitted and make sure that it is valid and that the "auditContext"
field is not missing.
ISC.0084.9004E Cannot obtain a connection: out of connection or invalid in pool configuration.

Cause: The Integration Server could not connect to the JDBC database that contains the server's cross-reference
keys and echo suppression data. Possible reasons are that the pool is configured incorrectly or that not enough
connections are available. Connection information for this database is specified on the Settings>JDBC Pools
page of the Server Administrator.
Response: From the Settings>JDBC Pools page of the Server Administrator, examine the pool alias properties
for the Xref and Echo Suppression database. If the configuration appears to be correct, consider increasing the
number of connections.
ISC.0084.9005E Error Message: <errorMessage>; Error Code: <errorCode>; SQLState: <stateString>.

Cause: A "pub.synchronization.*" service encountered a SQLException.
Response: Examine the error stack trace to determine which SQL exception was thrown. Check the
"webMethods Integration Server Administrator's Guide" to make sure you have set up the database correctly.
If you cannot determine the cause of the problem, contact the Database Vendor.

ISC (IS Core)
ISC.0084.9005E Service name cannot be null or empty.

Cause: webMethods Monitor failed to resubmit the rejected document because the "serviceName" field in the
data was either null or empty.
Response: Examine the document to be resubmitted and make sure that it is valid and that the "serviceName"
ISC.0084.9006U Service for resubmission does not exist on the server.

Cause: webMethods Monitor failed to resubmit the rejected document because the service for resubmission
does not exist on the Integration Server.
Response: Examine the document to be resubmitted and make sure that the name specified in the
"serviceName" field is a valid service and exists on the Integration Server.
ISC.0084.9007E Cannot insert a duplicated record.

Cause: The pub.synchronization.xref:createXReference service or pub.synchronization.xref:insertXReference
service threw a RepositoryNoLockException when the Integration Server tried to insert to or create a cross-
reference record in the Repository.
Response: From the Settings>Repository page of the Server Administrator, examine the Maximum Lock Wait
setting and consider increasing this value. Doing so will cause the Integration Server to wait longer for a lock
to be set, thereby reducing the chance of a timeout condition. If increasing the wait time does not correct the
problem, contact webMethods Customer Care.
ISC.0084.9007E Input pipeline cannot be null.

Cause: webMethods Monitor failed to resubmit the rejected document because the "pipeline" field in the data
was either null or empty.
Response: Examine the document to be resubmitted and make sure that it is valid and that the "pipeline" field
is not missing.
ISC.0086.9204E `<variableName>` is required.

Cause: A required input value is missing.
Response: If you are working with the webMethods Developer, enter an appropriate value in this field. For
information about this field, see the "webMethods Developer User's Guide."
If you are invoking a user-written service, check the required input to that service. If the service calls a
webMethods built-in service, refer to the "webMethods Integration Server Built-In Services Reference" for
information about required input for the built-in service.

ISC.0086.9205E If `<variableName>` is supplied, it must be zero (0) or greater.

Cause: The indicated input value is a negative number, but it must be zero or a positive number.
ISC.0086.9206E `offset` + `length` cannot exceed the size of `buffer`.

Cause: The values specified for offset and length are invalid because they will cause the Integration Server to
write data from the stream past the end of the supplied buffer.
ISC.0086.9207E The mark method is not supported by the supplied InputStream.

Cause: A service invoked the pub.io:mark service to mark a location on a stream, but the supplied stream does
not implement the mark and reset methods.
Response: If you are working with the webMethods Developer, contact webMethods Customer Care.
If you are invoking a user-written service, either use a different kind of InputStream that implements the mark
and reset methods, or do not invoke the pub.io:mark service.
ISC.0086.9208E The reset method is not supported by the supplied InputStream.

Cause: A service invoked the pub.io:reset service to reset to a location on a stream, but the supplied stream
does not implement the mark and reset methods.
Response: If you are invoking a user-written service, either use a different kind of InputStream that implements
the mark and reset methods, or do not invoke the pub.io:reset service.
ISC.0086.9209E `<variableName>` must be greater than zero (0).

Cause: The input variable specified is negative or zero, but the value must be a positive number.

ISC (IS Core)
ISC.0088.0001U SOAPException: <faultString>.

Cause: The SOAP message handler could not process the message because an error occurred.
Response: Examine the detailed element in the SOAP exception message for information about the specific
failure that occurred.
ISC.0088.0002E Failed registering SOAP Processor, missing parameter: <svcName>.

Cause: The Integration Server failed to add the specified SOAP processor to the processor registry using the
pub.processor:registerProcessor service.
Response: Examine the service input and make sure that the fully-qualified service name is specified correctly
for input parameter "svcName". Usually, this error occurs because the service name was not specified.
ISC.0088.0003E Failed registering SOAP Processor <processorName> as directive <directiveName>; directive already
registered.
Response: Make sure that the "directive" parameter specifies the correct directive. (Remember that directive
names are case-sensitive.) In addition, make sure that the specified directive is not already registered in the
SOAP Processor registry. Usually, this error occurs because the registry already contains a processor
registered to the specified directive.
ISC.0088.0004E Failed registering SOAP Processor <processorName> as directive <directiveName>; unknown service
<serviceName>.
Response: Examine the service input and make sure that the fully-qualified service name is specified correctly
for input parameter "svcName". Usually, this error occurs because the service does not exist on the Integration
Server. (Remember that service names are case-sensitive.)
ISC.0088.0005E Failed unregistering SOAP Processor, missing parameter: <directive>.

Cause: The pub.processor:unregisterProcessor service failed to execute because the "directive" parameter was
not supplied.
Response: Examine the service input and make sure that the "directive" parameter specifies the correct
directive. (Remember that directive names are case-sensitive.) Usually, this error occurs because the directive
is not specified.

ISC.0088.0006E Failed unregistering SOAP Processor <processorName>; no such directive registered.

Cause: The Integration Server failed to remove the specified processor from the SOAP Processor registry using
the pub.processor:unregisterProcessor service.
Response: Make sure that the "processorName" parameter specifies the correct directive. (Remember that
directive names are case-sensitive.) In addition, make sure that the specified directive is currently registered in
the SOAP Processor registry. It may have already been removed. Usually, this error occurs because the
registry does not contain a processor registered to the specified directive.
ISC.0088.0007E Failed registering SOAP Processor <processorName> as directive <directive>; invalid character(s) in
directive.
Cause: The Integration Server failed to add the specified processor to the SOAP Processor registry using the
Response: Examine the service input and make sure that the value for the "directive" parameter only contains
characters that are part of a Unicode identifier. See the Java Specification for the full range of Unicode values.
Usually, this error occurs because the specified directive contains characters that are not part of a Unicode
identifier.
ISC.0088.9102U ASSERTION: The directive <directiveName> in the URL <urlName> should be <directiveName>.
Cause: The SOAP message handler encountered a serious internal error.
ISC.0088.9103E Error reading SOAP Message from HTTP stream -- appears to be empty.
ISC.0088.9105E Failed to register SOAP Handler <directiveName>.

Cause: The Integration Server was not able to successfully add the specified SOAP processor to the SOAP
Processor registry.
Response: Verify that the SOAP processor directive and fully qualified service name have been specified
correctly. This error usually occurs because the directive name or the service name has not been specified.
ISC.0088.9107E Failed to unregister SOAP Handler <directiveName>.

Cause: The Integration Server was not able to successfully remove the specified SOAP processor from the
SOAP Processor registry.
Response: This error generally occurs because the registry does not contain a processor registered to the
specified directive. Verify that the process directive was specified correctly. (Remember that directive names

ISC (IS Core)
are case-sensitive.) Also verify that the specified directive is currently registered in the SOAP Processor
registry. It may have already been removed.
ISC.0088.9108U SOAP Handler <directiveName> already registered.

Cause: The Integration Server was not able to successfully register the SOAP processor, because the registry
already has a processor registered under the specified directive.
Response: Register the SOAP processor under a different directive. Or unregister the processor that is currently
registered to <directiveName>, and then register this SOAP Processor.
ISC.0088.9109U SOAP is only supported using HTTP POST protocol.

Cause: The SOAP message handler was not able to accept the request because the SOAP message was
submitted to the Integration Server using the HTTP GET method. The SOAP message handler only accepts
requests via the POST method (per W3C specification).
Response: Modify the client to use HTTP POST to submit SOAP messages to the Integration Server.
ISC.0088.9110E Invalid BOOLEAN value <value> for variable <varName>; must be 0 or 1.

Cause: The addHeaderEntry utility failed because the "mustUnderstand" attribute was not set correctly.
Response: Check the logic in the process that failed to make sure that it sets the value of <varName> to either 0
or 1. No other values are permitted when setting the "mustUnderstand" attribute.
ISC.0088.9111E Cannot load or execute the SOAP processor <directiveName>.

Cause: The SOAP message handler cannot process the SOAP message because the requested SOAP processor
is non-operational.
Response: On the Server, check the status of the service that is registered to <directiveName>. Make sure this
service is loaded and operating successfully. (Frequently this error occurs because the processor was modified
and then did not recompile successfully.)
ISC.0088.9112E An Exception was thrown in the server.

Cause: The Integration Server, the SOAP processor, or one of the services processing the message has thrown
an exception.
Response: See the detail element in the SOAP fault to determine the exception that was thrown and which
process it was thrown by.
ISC.0088.9113U The SOAP Envelope does not have a Body block.

Cause: The SOAP client was given a soapRequestData that did not contain a body element.
Response: Examine the logic in the client to see whether it uses the stringToSoapData or streamToSoapData
service to generate their SOAP objects. If so, determine whether the String or stream from which the SOAP
object was generated represented a valid SOAP message. Also check whether the SOAP processor or client

used any of the data removal utilities (such as removeHeaderEntry or removeBodyEntry) and might have
inadvertently removed the entire Body element.
ISC.0088.9114U Missing SOAP directive in the URL <urlName>.

ISC.0088.9116E The server cannot execute the requested SOAP utility; required parameter <paramName> is missing or
invalid.
Cause: The requested SOAP utility failed to execute because a required parameter was not supplied.
Response: Check the logic in the SOAP processor or client to make sure that it passes the correct parameters to
each SOAP utility service that it invokes.
ISC.0088.9118I Parameter <paramName> must be a valid soapData.

Cause: The requested SOAP utility failed to execute because parameter <paramName> is not a SOAP object.
Response: Examine the logic in the SOAP processor or client and make sure that it passes a SOAP object in
parameter <paramName>.
ISC.0088.9119U SOAP Processor did NOT return a valid SOAP Response

Cause: The message handler did not a receive a valid SOAP message from the SOAP processor.
Response: Examine the logic in the SOAP processor to make sure that it composes the SOAP response message
correctly. For example, check to see whether it the processor uses the stringToSoapData or streamToSoapData
services to generate soapResponseData. If so, determine whether the original String or stream represents a
valid SOAP message. If the SOAP processor logic seems correct, contact webMethods Customer Care. This
would indicate a serious internal error.
ISC.0088.9120U Parameter <paramName> is not one of the valid data types: <dataType>.
Cause: The requested SOAP utility failed to execute because parameter <paramName> did not have the correct
data type. The type in <dataType> is the data type that is expected.
Response: Examine the logic in the SOAP processor or client and make sure that it passes to <paramName> an
object of the data type specified in <dataType>.

ISC (IS Core)
ISC.0088.9122U Service <serviceName> does not exist.

Cause: The SOAP facility could not complete the requested operation because it could not find the specified
service. This error is issued by various SOAP processes (e.g., registering a SOAP processor, invoking a SOAP
processor, invoking a target service).
Response: Examine the process that failed and make sure that it specifies the name of the requested service
correctly. For example, if you receive this error when registering a SOAP processor, check that you have
specified the svcName parameter correctly. Remember that service names are case-sensitive.
ISC.0088.9123U Requested SOAP processor <directiveName> is not registered on this server.

Cause: The Integration Server could not process the SOAP message because it does not have the SOAP
processor requested by the client.
Response: On the client side, verify that the correct process directive is specified in the URL (remember that the
directive is case-sensitive). If the client has specified the process directive correctly, then use
pub.soap.processor:list to verify that the requested processor is registered on the Integration Server.
ISC.0088.9124U SOAP Message does not conform to the SOAP message model.
Cause: The SOAP message passed to the validateSoapData utility failed validation (for example, it is missing
the Body element or the Header element follows the body).
Response: Examine the logic that produced the message and see whether it uses the stringToSoapData or
streamToSoapData service to manually generate a SOAP object instead of using the message composition
services (e.g., createSoapData , addHeaderEntry , addBodyEntry ). If so, determine whether the String or
stream from which the SOAP object is generated represents a valid SOAP message.
Also check whether the SOAP processor or client used any of the data removal utilities (such as
removeHeaderEntry or removeBodyEntry ) and might have inadvertently removed required portions of the
SOAP object (for example, the entire Body element).
ISC.0088.9125U SOAP request does not conform to the SOAP message model.
Cause: The SOAP message handler could not process the SOAP request because it violates the SOAP message
schema (for example, it is missing the Body element or the Header element follows the body).
Response: On the client side, correct the logic that builds the message to ensure that it produces a valid SOAP
message.
ISC.0088.9126U SOAP response does not conform to the SOAP message model.
Cause: The SOAP message handler could not return the SOAP response generated by a SOAP processor on the
Integration Server because the message violates the SOAP message schema.
Response: Examine the logic in the SOAP processor and see whether it uses the stringToSoapData or
streamToSoapData service to generate a SOAP object. If so, determine whether the String or stream from
which the SOAP object is generated represents a valid SOAP message. Examine the logic that produced the

message and see whether it uses the stringToSoapData or streamToSoapData service to manually generate a
SOAP object instead of using the message composition services (e.g., createSoapData, addHeaderEntry,
addBodyEntry). If so, determine whether the String or stream from which the SOAP object is generated
represents a valid SOAP message. Also check whether the SOAP processor or client used any of the data
removal utilities (such as removeHeaderEntry or removeBodyEntry) and might have inadvertently removed
required portions of the SOAP object (for example, the entire Body element).
ISC.0088.9127U The server could not load the SOAP XML Validator.
ISC.0088.9128U Request is from namespace <msgNamespace>, server requires namespace <svrNamespace>.

Cause: The SOAP message handler could not process the message because the message is not from a version of
SOAP that the Integration Server supports. The Integration Server supports the version indicated in
<svrNamespace> .
Response: From the client side, resubmit the message using a version of SOAP that the Integration Server
supports.
ISC.0088.9129E Invalid node: XML blocks must be in a container

Cause: The requested SOAP utility (e.g., addHeaderEntry , addBodyEntry ) failed to execute because it
received a node that does not represent an enclosed XML element.
Response: This error can occur if the node is missing opening and closing tags (e.g., the node contains " hello "
instead of " <a>hello</a> "). Examine the process that called the failing utility and make sure that it passes a
valid node object to the SOAP utility.
ISC.0088.9130E Invalid node: XML blocks can only have a single root container
Cause: The requested SOAP utility (e.g., addHeaderEntry , addBodyEntry ) failed to execute because it
received a node that does not have a root element.
Response: This error can occur if the node contains an XML fragment that represents uncontained elements
(e.g., the node contains " hello <c>world</c> " instead of " <a> hello <c>world</c> </a> ").
Examine the logic that called the failing utility and make sure that it passes a node containing only one top-
level XML element.
ISC.0088.9131E Invalid node: must be well-formed XML

Cause: The requested SOAP utility (e.g., addHeaderEntry, addBodyEntry) failed to execute because it received
a node that does not represent a well-formed XML document.
Response: This error can occur if the node contains overlapping or missing tags (e.g., a node that contains "
hello " or " <a> hello <c>world</c> </a> "). Examine the logic that called the failing utility and make
sure that it passes a node containing well-formed XML.

ISC (IS Core)
ISC.0088.9132E Failed to register SOAP Handler <directiveName>, illegal characters in directive name.
Cause: The Integration Server was not able to successfully register the SOAP processor, because
<directiveName> contains characters that are not allowed in a directive name.
Response: Register the SOAP processor under a name that is composed only of letters, digits, or the characters
-_.!~*'( ) .
ISC.0088.9133E Error while encoding RPC output.

Cause: The message coder could not XML-encode the parameters associated with a SOAP remote procedure
call.
Response: See the detail element in the SOAP fault for information about the specific failure that occurred.
ISC.0088.9134U Exception occurred while processing the body of the message.

Cause: The Integration Server, the SOAP processor, or one of the services processing the SOAP message has
thrown an exception.
Response: See the detail element in the SOAP fault to determine which exception was thrown and which
process it was thrown by.
ISC.0088.9135U A WMDocument Exception was thrown in the server, usually because an XML block was not well-formed.
Cause: The SOAP message handler, the soapHTTP service, or the soapRPC service has received a SOAP
message that contains invalid XML.
Response: Check the process that submitted the SOAP message to the Integration Server and make sure that it
is producing valid XML. This error usually occurs because of a basic error in the XML document, such as
missing tags or overlapping elements.
ISC.0088.9136U A WattEvaluationException was thrown by the XQL Query engine.

Cause: The XQL query processor encountered a serious internal error.
ISC.0088.9137E Invalid input parameter; <paramName> must be a Document (IData).

Cause: The requested SOAP utility failed to execute because the object passed in <paramName> is not an IData
object.
Response: Check the logic in the SOAP processor or client to make sure that it passes an IData in paramName .
ISC.0088.9138U Input parameters do not conform to targetInputSignature: <validationDetails>.

Cause: The pub.client:soapRPC service could not submit the remote procedure call because the input
parameters did not pass the data-validation process.

This error is thrown when a client supplies an invalid set of input parameters for a SOAP remote procedure
call. Specifically, it indicates that the parameters submitted to pub.client:soapRPC in reqParms do not match
the structure and constraints of the document type specified in targetInputSignature .
Response: Generally, you will want to code your client to detect this kind of error and take some type of
corrective action when it occurs.
ISC.0088.9139U Output parameters do not conform to targetOutputSignature: <validationDetails>.

Cause: The SOAP RPC client could not submit the remote procedure call because the output parameters
returned by the remote server did not pass the data-validation process.
This error is thrown when a client receives an invalid set of output parameters (results) from a SOAP remote
procedure call. Specifically, it indicates that the parameters returned to pub.client:soapRPC in respParms do
not match the structure and constraints of the document type specified in targetOutputSignature .
Response: Generally, you will want to code your client to detect this kind of error and take some type of
corrective action when it occurs.
ISC.0088.9140E Invalid target signature <docTypeName>, must be a Document Type.

Cause: The SOAP RPC client could not process the remote procedure call because it was not able to validate the
input or output parameters associated with the request. The signature it was given for validation is not a
document type.
Response: Examine the logic in the SOAP RPC client and make sure that the object it specifies in
targetInputSignature and/or targetOutputSignature is a document type. That is, these parameters, if used,
specify the fully qualified name of a document type that exists on the Integration Server.
ISC.0088.9141E Invalid target signature <docTypeName>, Document Type does not exist.
Cause: The SOAP RPC client could not process the remote procedure call because it was not able to validate the
input or output parameters associated with the request. The specified document type does not exist on the
Integration Server.
Response: Examine the logic in the SOAP RPC client and make sure that targetOutputSignature and/or
targetOutputSignature are correctly specified. (Remember that the names of document types are case
sensitive.). Also verify that the specified document type exists on the server and the package in which it
resides is loaded and enabled.
ISC.0088.9142U Invalid Body Entry. SOAP Body Entries must have a namespace name.
Cause: The pub.soap.util:addBodyEntry service failed because it was given an XML node that was not
namespace qualified.
Response: Examine the logic in the SOAP client or target service (depending on which entity issued the error)
and verify that the XML node that the addBodyEntry service is attempting to add is namespace qualified (i.e.,
that it includes the "xmlns" attribute and that the element name has the proper namespace prefix). Note: This

ISC (IS Core)
error occurs only if namespace checking is enabled on the Integration Server. See
watt.server.SOAP.enforceMsgPartNS in the "webMethods Integration Server Built-In Services Reference."
ISC.0088.9143U Invalid Header Entry. SOAP Header Entries must have a namespace name.
Cause: The pub.soap.util:addHeaderEntry service failed because it was given an XML node that was not
namespace qualified.
Response: Examine the logic in the SOAP client or target service (depending on which entity issued the error)
and verify that the XML node that the addHeaderEntry service is attempting to add is namespace qualified
(i.e., that it includes the "xmlns" attribute and that the element name has the proper namespace prefix). Note:
This error occurs only if namespace checking is enabled on the Integration Server. See
watt.server.SOAP.enforceMsgPartNS in the "webMethods Integration Server Built-In Services Reference."
ISC.0107.9001E Cannot create element ''<elementName>''; a document type or schema with this name already exists on the
Integration Server.
Cause: While trying to pull a document from the Broker, the Integration Server determined that a record being
referenced already existed on the Integration Server. As a result, synchronization could not continue.
From the Developer, check the "Overwrite existing elements when importing referenced elements" box on the
Document Synchronize dialog.

ISE (Internal Errors)
ISE.0093.9902E Error occurred while invoking a service : <errorMessage>.

Cause: The Integration Server encountered an internal error while invoking a service. The <errorMessage>
should include more specifics about the actual error.
ISE.0093.9903U Not implemented.

ISE.0093.9904U Unknown session: <sessionID>.

ISE.0093.9952U Access was denied to resource <resourceName>.

Cause: The Integration Server encountered an internal error due to resource access.
ISE.0093.9954U Resource <userName> doesn't exist or was removed.

Cause: The Integration Server encountered an internal error due to resource access.

ISP (Package Management)
ISP.0046.0001E Could not initialize HTTP Listener. Invalid port specified: <portNumber>.
Cause: While attempting to initialize a port, the Integration Server detected that the port was improperly
configured. Specifically, an invalid port number was specified for the port in the server.cnf, ports.cnf, or
listeners.cnf file.
Response: Edit the appropriate configuration file and specify a port number from 1 through 65534 that is not
already in use.
ISP.0046.0006E Cannot initialize HTTP Listener on port <portNumber>. No socket available.

Cause: While trying to initialize an HTTP listener, the Integration Server determined that the socket associated
with the requested port is already in use by another application, therefore the requested port is unavailable.
Response: Specify a port that is not already in use, or disable the application that is using the desired port.
ISP.0047.0001E Could not initialize HTTPS Listener. Invalid port specified: <portNumber>.
Cause: While attempting to initialize a port, the server detected that the port was improperly configured.
Specifically, an invalid port number was specified for the port in the server.cnf, ports.cnf, or listeners.cnf file.
Response: Edit the appropriate configuration file and specify a port number from 1 through 65534 that is not
already in use.
ISP.0047.0018E Aborting connection from <address>: <message>.

Cause: The Integration Server encountered a problem while trying to establish a secure connection with the
client at the indicated address.
Response: Make sure the client properly supports SSL connections.
ISP.0047.0019E SSL listener restricted to 128 bit or better encryption:

Cause: The Integration Server configuration property watt.net.ssl.server.strongcipheronly is set to "true", but
the list of ciphers includes weak ciphers. The Integration Server displays these weak ciphers in subsequent
messages.
Response: Either use only strong ciphers, or set watt.net.ssl.server.strongcipheronly to "false".
ISP.0047.0020E cipher <number> = <cipher> (<number> bit).

Cause: The Integration Server configuration property watt.net.ssl.server.strongcipheronly is set to "true", but
the list of ciphers includes the weak ciphers displayed by this message.
Response: Either use only strong ciphers, or set watt.net.ssl.server.strongcipheronly to "false".

ISP.0047.0021E Aborting connection request on <protocol> port <port>, a certificate map does not exist for <user>.
Cause: A client presented a certificate to the Integration Server, but the certificate has not been mapped to a
user on the Integration Server. For a certificate to be mapped to a user, the certificate must have been
previously stored on the Integration Server and associated with that user.
Response: Use the Server Administrator interface to import the certificate to the Integration Server and map it
to the appropriate user.
ISP.0047.9998U Exception --> <error message>.

Cause: The Integration Server encountered an error. This message contains the exception produced by the
server.
ISP.0068.9003E Invalid service: <serviceName>.

Cause: A message was received at the Integration Server's e-mail listener, but the service that is supposed to
perform the message processing is invalid for some reason. Which service the Integration Server selects to
execute message processing depends on how the server is configured. The server selects a service in the
following order:
- Use the service specified in the Global Service field on the Email Client Configuration screen on the Server
Administrator.
- If the Global Service field is not specified, use the service specified in the e-mail message from the e-mail
client.
- If a Global Service is not specified and no service is specified in the e-mail message, use the service specified
in the Default Service field on the Email Client Configuration screen on the Server Administrator UI.
The problem is often that the service name is specified in the wrong case (service names are case sensitive).
Other causes are that no service was specified at all (not in the Global Service or Default Service fields, or in the
e-mail message itself) or that a service was specified, but does not exist on the Integration Server in the
specified location.
Response: Make sure that the service you want to perform message processing is correctly specified either in
the email or in the appropriate field on the Email Client Configuration screen on the Server Administrator.
ISP.0071.9001E Cannot build data connection: use PORT or PASV first.

Cause: The Integration Server failed to connect to a port on the FTP client because the FTP client did not
provide valid port information.
Response: Check the Integration Server configuration and restart the server. If the problem persists, contact

ISP.0071.9002E <directoryName>: cannot create.

Cause: An FTP client application connected to an FTP port on the Integration Server and tried to create a
remote directory on the FTP server, but the "mkdir" command failed.
Response: Make sure the directory name was specified correctly. Also examine the remote file system and
make sure that you have permission to create the directory there.
ISP.0071.9003E <fileName>: cannot delete.

Cause: An FTP client application connected to an FTP port on the Integration Server and tried to delete a file on
the FTP server, but the "delete" command failed.
Response: Make sure the file name was specified correctly and that the file exists on the remote server. Also
examine the remote file system and make sure that you have permission to delete the file from the remote file
system.
ISP.0071.9004E Cannot rename File to <fileName>.

Cause: An FTP client application connected to an FTP port on the Integration Server and tried to rename a file
on the FTP server, but the "rename" command failed.
Response: Make sure the old and new file names were specified correctly. Also examine the remote file system
and make sure that you have write permission to both the old and new file names.
ISP.0071.9005U Unable to make dir <directoryName>.

Cause: An FTP client application connected to an FTP port on the Integration Server and tried to create a
remote directory on the FTP server, but the "mkdir" command failed.
Response: Make sure the directory name was specified correctly. Also examine the remote file system and
make sure that you have the permission to create the directory there.
ISP.0071.9006U Unable to delete <fileName>.

Cause: An FTP client application connected to an FTP port on the Integration Server and tried to delete a file on
the FTP server, but the "delete" command failed.
Response: Make sure the file name was specified correctly and that the file exists. Also examine the remote file
system and make sure that you have permission to delete the file.
ISP.0071.9007U Unable to rename to <fileName>.

Cause: An FTP client application connected to an FTP port on the Integration Server and tried to rename a file
on the FTP server, but the "rename" command failed.
Response: Make sure the old and new file names were specified correctly. Also examine the remote file system
and make sure that you have write permission to both the old and new file names.

ISP.0071.9008E Cannot write.

Cause: The Integration Server failed to put the file in the folder directory. The file must be in the service
directory for processing.
Response: Put the file in the service directory.
ISP.0071.9009E Invalid transaction name. Not in the form 'tid[;mime.type][;encoding]'.

Cause: The MIME type specified in the FTP request is incorrect. It should be in the form of
'tid[;mime.type][;encoding]'."
Response: Make sure to provide the name in the correct form.
ISP.0071.9010U Unable to determine mime type.

Cause: The Integration Server does not support the MIME type specified.
Response: Only use the MIME types supported by the Integration Server.
ISP.0071.9012U No such service: <serviceName>.

Cause: The Integration Server FTP listener encountered an internal error.
ISP.0071.9013U Unknown content type: <mime type name>.

Cause: The Integration Server does not support the MIME type specified.
Response: Only use the MIME types supported by the Integration Server.
ISP.0071.9014U Server Error: <error message>.

ISP.0071.9015E Cannot publish STOR complete event

ISP.0085.9053E invalid package.

Cause: An application tried to delete a service, but the package specified does not exist on the Integration
Server.
Response: Examine the service input and verify that a valid package name is specified.

ISP.0085.9062E Package name was not provided.

Cause: An application tried to export a package, but the package name was not provided.
Response: Examine the service input make sure it provides a valid package name.
ISP.0085.9078E node belongs to invalid package.

Cause: An application tried to create a service, but the package name specified to contain the service was
missing or invalid.
Response: Examine the service input and make sure a valid package name is provided.
ISP.0085.9079E not a valid interface name.

Cause: An application tried to create a new service, but the folder name was missing or invalid.
Response: Examine the service input and verify that a valid folder name is provided.
ISP.0085.9088E Invalid package version <versionNum>, the accepted format is #.#.

Cause: Using the Developer, you tried to edit the package version, but specified an invalid version number.
The correct format is "x.y" or "x.y.z" (x, y, z all must be digits from 0-9, e.g. 2.0, 4.0.1 etc.).
Response: Examine the service input and make sure a valid package version is provided.
ISP.0085.9089E Not allowed to add unknown package(s) <packageName> to dependency list.

Cause: While using the Developer, you tried to edit a package's dependency list, but the package name you
tried to add to the list does not exist on the Integration Server.
Response: Specify the package name again, this time specifying a package that exists on the Integration Server
and is enabled.
ISP.0085.9094E Invalid Folder/Service Name.

Cause: Using the Server Administrator, you tried to add a service or folder to a port's access list, but the service
or folder specified does not exist on the Integration Server.
Response: Enter the folder or service name again, this time specifying one that exists on the Integration Server.
ISP.0085.9100E No password specified.

Cause: Using the Server Administrator, you tried to create an alias for a remote server, but omitted the remote
server's password.
Response: Enter a valid password in the password field.

ISP.0085.9101E Missing one or more required parameters: $alias, $service.

Cause: The pub.remote:invoke service failed to execute because one or both of the required "$alias" or
"$service" parameters were not supplied.
Response: Examine the service input and ensure that both the parameters are specified.
ISP.0085.9102E No such remote server: <serverAliasName>.

Cause: The pub.remote:invoke service failed to execute because an invalid server alias was provided.
Response: From the Settings>Remote Servers page of the Server Administrator examine the Remote Servers
List and make sure an alias exists for the remote server. If not, create one before invoking the
pub.remote:invoke service again.
ISP.0085.9103E User session required to invoke a protected remote server.

Cause: The Integration Server encountered a serious internal error because the user session object that invokes
the service on the remote server is null.
ISP.0085.9104E Access denied to invoke on remote server <serverAliasName>.

Cause: The pub.remote:invoke service failed to invoke the service on the remote server because the current
user does not have the proper ACL.
Response: Using the Integration Server Administrator, examine the remote server alias properties as well as the
service's Execute ACL setting on the remote server. Make sure that the current user has the proper ACL to
invoke the service.
ISP.0085.9105E User session required to invoke a remote server with SESSION scope.
Cause: The Integration Server encountered a serious internal error because the user session object that invokes
the service on the remote server is null.
ISP.0085.9113E Date/time format is invalid. Date must be in YYYY/MM/DD format and time in HH:MM:SS format.
Cause: From the Server Administrator, you tried to schedule a one- time task, but specified an invalid date or
time format.
Response: Enter the date and/or time again, this time specifying the correct format.

ISP.0085.9116E Interval must be a positive integer <intervalValue>.

Cause: Using the Server Administrator, you tried to schedule a repeating task, but the interval you specified is
not valid.
Response: Specify the interval again, this time specifying a positive integer.
ISP.0085.9117E Invalid task type: <taskType>.

Cause: The WmRoot service wm.server.schedule:createUserTask failed to execute because an invalid task type
was supplied. Valid task types are: "once", "repeat", and "complex".
Response: Examine the service input and ensure that the "type" parameter specifies a valid task type.
ISP.0085.9123U nobody to send message to.

Cause: The Integration Server failed to invoke a service on the remote server using the e-mail port because the
"to" parameter was not supplied.
Response: Examine the logic to make sure that it passes the correct input to the "to" parameter when invoking
services remotely using the e-mail listener.
ISP.0085.9124U no attachment.
"attachments" parameter was not supplied.
Response: Examine the logic to make sure that it passes the correct input to the "attachments" parameter when
invoking services remotely using the e-mail listener.
ISP.0085.9125U attachments must be of type Values[].

input for the "attachments" parameter was not of Values[] type.
Response: Examine the logic to make sure that it passes the correct Values[] input to the "attachments"
parameter when invoking services remotely using the e-mail listener.
ISP.0085.9126E Invalid attachment file <fileName>.

file attachment specified in the "filename" parameter does not exist in the system.
Response: Examine the logic to make sure that it passes a valid file to the "filename" parameter and make sure
that it exists in the file system.

ISP.0085.9131E Not allowed to add empty package version, the accepted format is *.*.
Cause: While using the Developer, you tried to edit a package's dependency list, but did not specify the
package version.
Response: Enter a valid package version in the format "x.y" or "x.y.z" (x, y, z all must be digits from 0-9, e.g. 2.0,
4.0.1 etc.).
ISP.0085.9139E Cannot <compile> changes because the file(s) representing <serviceName> may have been changed to
'Read-Only'. To <compile> changes, change the following file(s) from 'Read-Only' to 'Read/Write' either manually or through a
source control system: <fileCanonicalPath>.
Cause: The Integration Server could not compile the java or C service, possibly because the files have changed
to Read-Only.
Response: Examine the file permissions and change the file permission from Read-Only to Read/Write, either
manually or through a source control system.
ISP.0085.9141E The Universal Name <universalName> contains an invalid character.

Cause: This is an internal error.
ISP.0085.9145E Invalid input.

Cause: A WmRoot service failed to execute because the service input is not of the type required by the service.
Response: Examine the error stack trace to determine the exception that was thrown and the service that threw
it. For example, the service may require an IData object, but the supplied input was not an instance of IData.
ISP.0085.9147E Missing required parameter: 'header'.

ISP.0085.9148E header' must be of type Idata.

ISP.0085.9156E Cannot perform operation without List ACL privileges on <nsNodeName>.

Cause: From the Developer, you tried to lock a namespace element for editing or tried to view a service, but
you do not have List access to the resource.
Response: Contact the Administrator of the Integration Server to request List ACL permission for the service or
NS node.

ISP.0085.9166E Not a valid condition type.

Cause: The Integration Server determined that an invalid condition type was provided. The condition type
must be "simple" or "join."
Response: Examine the service input and ensure that the condition type provided is "simple" or "join."
ISP.0085.9167E Not a valid trigger name. Trigger name must be of type String.
Cause: The Integration Server determined that an invalid trigger name was provided. The trigger name must
be of type String.
Response: Examine the service input and ensure that the trigger name is of type String.
ISP.0085.9171E Not a valid condition name. Condition name must be of type String.
Cause: During a trigger test, the Integration Server encountered an invalid condition name. The condition
name must be of type String.
Response: Examine the service input and ensure that the condition name is of type String.
ISP.0087.0001E Initialization failed: (exceptionMessage)

Cause: During Integration Server initialization, the native startup code for NTLM authentication failed.
Response: Check the exception message text and the server log for information about why the NTLM
authentication failed.
ISP.0087.0003E failed to load native libraries, NT Challenge Response cannot be used!

Cause: During initialization, the Integration Server could not find the ntlm.dll library. This library is required
for NTLM authentication.
ISP.0087.0004E Could not properly acquire state information for NT challenge response
Cause: While trying to execute a request, the Integration Server could not find the state information for the
current NTLM handshake. The most likely cause is that the state identifier from the client is bad or the state
information collection is bad.
Response: Try obtaining a fresh client session. If the client is a browser, restart the browser.
ISP.0087.0006E Could not properly acquire state information for NT challenge response
Cause: While trying to execute a request, the Integration Server could not find the state information for the
current NTLM handshake. The most likely cause is that the state identifier from the client is bad or the state
information collection is bad.
Response: Try obtaining a fresh client session. If the client is a browser, restart the browser.

ISP.0087.0009E Authorization failed NT Challenge Response negotiation.

Cause: When the Integration Server tried to execute a request, the NTLM handshake failed to authorize the
current user.
Verify that the current user is authorized in the NT domain.

ISS (IS Server)
ISS (IS Server)
ISS.0001.0011U All licenses have been consumed.

Cause: The Integration Server has reached its client limit. Your license for the Integration Server allows only a
certain number of sessions to be used at a time. The Integration Server issues this message when the number of
users trying to use the server exceeds the number specified in the license.
Response: Check the number of licensed sessions specified in your Integration Server's license. Consider
upgrading the license to obtain more user "seats" if the number of users requiring access to your Integration
Server has increased.
ISS.0002.0002E Error loading LDAP settings: <errorMessage>

Cause: The Integration Server encountered an IOException while reading the ldap.cnf file.
Response: Check to make sure that the operating system user that is running the Integration Server has
permission to read and write to the ldap.cnf file. In addition, make sure that the ldap.cnf file is a valid XML file
and has not been corrupted in some way. As a last resort, delete the ldap.cnf file and reconfigure the LDAP
settings from the Server Administrator.
ISS.0002.0003E Error saving LDAP settings: <errorMessage>

Cause: An IOException occurred while the Integration Server was writing the ldap.cnf file.
Response: Check to make sure that the operating system user that is running the Integration Server has
permission to read and write to the ldap.cnf file and to the server config directory. In addition, make sure that
there is sufficient disk space and quota space for creating and writing a new file.
ISS.0002.0005W LDAP User Manager enabled, but no LDAP directories are configured
Cause: The Integration Server is attempting to perform operations that require a connection to an LDAP server,
but the Integration Server is only partially configured to use LDAP. Specifically, the configuration does not
include a list of LDAP directories to which the Integration Server can connect.
Response: Use the Integration Server Administrator to configure the Integration Server to connect to one or
more LDAP directories. For more information about working with LDAP, refer to the "Working with External
Directories (LDAP or NIS)" chapter of the "webMethods Integration Server Administrator's Guide."
ISS.0002.0007W Query returned multiple DNs for a single user with filter (<uidproperty> =<value>)
Cause: The values specified in the Query DN field on the LDAP directory settings screen are not sufficient to
uniquely identify a user. The Integration Server uses this field to build a query to send to the LDAP server so
that the LDAP server can authenticate the user.
Response: Make sure that the user root, user property, and user names specified on the Query DN field are not
ambiguous.

ISS.0002.0008E Could not get a connection from the pool in the time allowed
Cause: The Integration Server was unable to connect to the LDAP server because the request to obtain a
connection timed out. This error can occur if the LDAP directory server is slow, is under high load, or is
experiencing high latency, and there are insufficient connections in the connection pool to meet demand.
Response: This error is probably transient. It is usually sufficient to wait a few seconds and try the operation
again (for example logging in, executing a service) when the load has decreased and resources have become
available. If the problem persists, then from the LDAP Directory Settings page of the Server Administrator, try
increasing the size of the LDAP connection pool. Also check to make sure the LDAP directory server is
properly configured and that the network is able to handle the load being placed on it by the application.
ISS.0002.0009E Unable to open a connection to <server>

Cause: The Integration Server was unable to open a connection to the indicated LDAP directory server.
Response: Check the following:
- Make sure the LDAP server is running and that the Integration Server has permission to connect to it.
- Make sure that the connection parameters specified on the LDAP Settings screen of the Server Administrator
are properly configured.
- If you are using SSL, make sure that the directory URL specified on the LDAP Settings screen specifies an SSL
port on the LDAP server and that both the Integration Server and LDAP server support SSL.
- If you are specifying credentials, make sure the principal specified on the LDAP Settings screen of the Server
Administrator is correct and that the password matches.
This error can also occur if the Integration Server cannot establish a connection to the LDAP server within the
configured time limit because of a problem such as network latency.
For more information about connecting the Integration Server to an LDAP server, see the "Working with
External Directories (LDAP or NIS)" chapter in the "webMethods Integration Server Administrator's Guide."
ISS.0002.0010E Error quering for user <user>: <message>

Cause: During a user log in, the Integration Server encountered an error while performing a query to obtain the
user's Distinguished Name.
Response: In the Server Administrator, on the LDAP Settings screen for the LDAP directory in question, check
to see if user root and user properties have been set correctly.

ISS (IS Server)
ISS.0002.0013W Found group <group>, but it contained no attribute <attribute>

Cause: During ACL mapping, the Integration Server determined that the value specified in the group attribute
field does match the attribute values of the group that the Integration Server found.
Response: Make sure the group name attribute field contains a valid group name attribute.
ISS.0002.0014E Error quering for groups on <server> with root <dn> and filter <filter>: <error message>
Cause: The Integration Server encountered an error when looking for LDAP groups to map to an Integration
Server ACL.
Response: If the text of the exception indicates a connection issue, try performing the mapping later. Otherwise,
check the values specified for group name, filter, and group name attribute on the Map Groups to ACLs
screen.
ISS.0002.0015E Unable to create ACL mapping: LDAP User Manager not initialized
Cause: An attempt to map an LDAP group to an ACL failed because the LDAP User Manager function of the
Integration Server is not running. This error occurs when one user disables LDAP while another user is trying
to perform ACL mapping.
Response: Use the Integration Server Administrator to check the External User Management Configuration
screens for possible configuration problems. In addition, try checking the server and error logs for messages
about problems with the LDAP manager.
For information about using the Integration Server with an external directory, refer to the "Using an External
Directory (LDAP or NIS)" chapter in the "webMethods Integration Server Administrator's Guide."
ISS.0002.0016E Unable to create ACL mapping: ACL group <group> not found
Cause: An attempt to map an LDAP group to an ACL failed because the ACL specified on the Map Groups to
ACLs screen does not exist. This error occurs if one user deletes the ACL in question when another user is
trying to map an LDAP group to it.
Response: Determine why the other user changed the Integration Server configuration then reconfigure the
Integration Server to use LDAP, if appropriate. For information about using the Integration Server with an
external directory, refer to the "Using an External Directory (LDAP or NIS)" chapter in the "webMethods
Integration Server Administrator's Guide."
ISS.0002.0017E Unable to retrieve password for handle <handle>: <errorMessage>

Cause: The Integration Server is trying to connect to an LDAP server. As part of connecting, the Integration
Server needs to send a password to the LDAP server. This error occurs when the Integration Server cannot
find the password it stored for this purpose. A likely cause is that the ldap.cnf file was moved from one system
to another, but the stored outbound passwords were not.
Response: Check to make sure the Outbound Password Manager is properly configured, and that its files are
readable by the Integration Server process. If the Outbound Password Manager is set up correctly, and the

error still occurs, go to the LDAP Configuration screen of the Server Administrator and reenter the existing
password.
ISS.0002.0018E Unable to store password for handle <handle>: <errorMessage>

Cause: The Integration Server was unable to store the password needed to connect to an LDAP server.
The Integration Server must supply passwords to many of the applications it connects to. It stores these
outbound passwords in encrypted form on the Integration Server. This error occurs when an administrator
enters or changes the password, but the Integration Server cannot subsequently store it.
Response: Check to see if the Integration Server is properly configured to handle outbound passwords.
Make sure that the following outbound password configuration files reside on the Integration Server and are
readable and writable:
config/empw.dat
config/passman.cnf
Integration Server Administrator User's Guide" for more information.
ISS.0002.0019E Unable to delete password for handle <handle>: <errorMessage>

Cause: An administrator updated the Integration Server configuration so that it no longer connects to an LDAP
server. As part of this process, the Integration Server tried to delete the password it uses to connect to the
LDAP server, but was unable to. The Integration Serve deletes the LDAP server from the configuration, but the
password remains, in encrypted form, on the Integration Server.
The most likely cause is that the files used to store outbound passwords on the Integration Server are read-
only.
Response: Refer to the "Outbound Passwords" section of the "Managing Server Security" chapter of the
"webMethods Integration Server Administrator User's Guide" for more information about outbound
passwords and the files used to store them. Then try to determine why the files are in read-only mode.
ISS.0002.0020E Unable to check password: LDAP User Manager not initialized

Cause: The Integration Server tried to check the password of an LDAP user but could not because the LDAP
user manager is not running. This error occurs when one user updates the Integration Server configuration to
disable LDAP directory use while another user is trying to perform an LDAP operation.
Response: Determine why the other user changed the Integration Server configuration. Then, reconfigure the
external directory, refer to the Using an "Using an External Directory (LDAP or NIS)" chapter in the
"webMethods Integration Server Administrator's Guide."

ISS (IS Server)
ISS.0002.0021E Unable to check group membership: LDAP User Manager not initialized
Cause: The Integration Server tried to find members of an LDAP group but could not because the LDAP user
manager is not running. This error occurs when one user updates the Integration Server configuration to
disable LDAP directory use while another user is trying to perform an LDAP operation.
Response: Determine why the other user changed the Integration Server configuration. Then, reconfigure the
external directory, refer to the "Using an External Directory (LDAP or NIS)" chapter in the "webMethods
ISS.0002.0023E Error initializing a connection to <server>: <errorMessage>

Cause: The Integration Server encountered an exception while trying to connect to the indicated LDAP server.
Response: Check the following:
- Make sure the LDAP directory server is running and that the Integration Server has permission to access it.
- Make sure the parameters on the External User Management Configuration screens of the Server
Administrator have been properly set.
ISS.0002.0024W Error closing connection to <server>: <errorMessage>

Cause: The Integration Server encountered an exception while trying to connect to the indicated LDAP server.
The Integration Server will clean up the connection.
ISS.0002.0025E No ACL Group specified.

Cause: An administrator did not select an ACL from the drop down box when trying to map LDAP groups to
an Integration Server ACL.
Response: Try performing the mapping again, this time specifying an ACL.
ISS.0002.0026E No LDAP groups were selected.

Cause: An administrator did not select the check box next to any of the LDAP groups listed when trying to map
LDAP groups to an Integration Server ACL.
Response: Try performing the mapping again, this time specifying at least one LDAP group.

ISS.0002.0027E No filter specified.

Cause: An administrator did not specify a filter while trying to map LDAP groups to an Integration Server
ACL. A filter narrows the selection of groups within Group Root.
Response: On the Map Groups to ACLs screen in the Server Administrator, specify an LDAP filter that starts
and ends with parentheses, for example, (objectClass= groupOfUniqueNames). For more information about
what to specify in this field, refer to the "Working with External Directories (LDAP or NIS)" chapter in the
"webMethods Integration Server Administrator's Guide" and the documentation for your LDAP server.
ISS.0002.0028E No group name attribute specified.

Cause: An administrator did not specify a group name attribute while trying to map LDAP groups to an
Integration Server ACL. LDAP uses the group name attribute to identify the name of the group to which a user
belongs, for example "cn". The Integration Server will use this attribute to search for group names in the LDAP
server.
Response: On the Map Groups to ACLs screen of the Server Administrator, specify a group name attribute. For
more information about what to specify in this field, refer to the "Working with External Directories (LDAP or
NIS)" chapter in the "webMethods Integration Server Administrator's Guide" and the documentation for your
LDAP server.
ISS.0002.0030E While attempting automatic LDAP configuration, some invalid settings were found. It is necessary to
complete the configuration manually.
Cause: When you upgrade from Integration Server release 6.1 or earlier to Integration Server release 6.5 or
later, the upgrade process tries to automatically configure the external user management facilities in your new
Integration Server based on these settings in your old Integration Server. To determine the old configuration
settings, the upgrade process looks for the following properties:
watt.server.ldap.server
watt.server.ldap.attr.userId
watt.server.ldap.attr.member
This error indicates that the upgrade process was unable to find one of these properties. The automatic
configuration does not continue.
Response: Go to the Security > Users and Groups > External User Management Configuration screen of the
Server Administrator and configure the Integration Server to use an external LDAP directory. For additional
information, refer to the "Using an External Directory (LDAP or NIS)" chapter in the "webMethods Integration
Server Administrator's Guide."

ISS (IS Server)
ISS.0002.0034E Invalid credentials connecting to <server> as <user>

Cause: The Integration Server encountered an Authentication Exception because the indicated user could not
log in to the indicated LDAP server.
Response: This error can occur for a number of reasons. Check to make sure that the DN of the user is valid,
that the credentials (i.e. password) specified are valid, and that the user account is enabled.
ISS.0002.0035E Invalid credentials connecting to <server> as <user>: <errorMessage>

Cause: The Integration Server encountered an Authentication Exception because the indicated user could not
log in to the indicated LDAP server. The last part of the message <errorMessage> includes extra information
provided by the LDAP server about the error. You can use this data to audit authentication errors when the
Integration Server connects to Microsoft Active Directory.
Response: This error can occur for a number of reasons. Check to make sure that the DN of the user is valid,
that the credentials (i.e. password) specified are valid, and that the user account is enabled.
Note: The errorMessage portion of this error displays only if the watt.server.ldap.extendedMessages property
in the server.cnf file is set to true. If you do not find the extended message useful, you can disable extended
messaging by setting this property to false.
ISS.0002.0037E LDAP Directory configuration failed: <errorMessage>

Cause: The Integration Server could not update its configuration to add an LDAP directory.
Response: Check to see if the disk to which the Integration Server is trying to write the configuration data is full
or write protected.
ISS.0002.9001E LDAP User Manager not initialized

Cause: The Integration Server detected a problem with its configuration settings for connecting to LDAP
servers. As a result, the Integration Server cannot connect to any LDAP servers.
Response: Check the settings on the External User Management Configuration screens of the Server
Administrator for possible problems.
ISS.0002.9002E Error saving new ACL Mappings: <errorMessage>

Cause: The Integration Server encountered an error while trying to map LDAP groups to an Integration Server
ACL.
Response: Check to see if the disk to which the Integration Server writes ACL data (for example
IntegrationServer/config/acl*.cnf) is full or write protected.

ISS.0005.9001U The Invoke State doesn't exist.

ISS.0011.0008U <fileName> is a File, not Directory!

Cause: During initialization, the Integration Server determined that the value specified on the watt.proxy.cache
property was not a directory. This parameter must specify the directory where the server cache will be stored.
Response: Examine the watt.proxy.cache property and make sure it specifies a valid directory. The Integration
Server will store all server cache files in this directory. You can view this property through the
Settings>Extended Settings page of the Server Administrator.
ISS.0014.0001E Encountered fatal errors while starting License Manager. Shutting down server.
Cause: The Integration Server encountered a serious internal error while validating the webMethods license.
ISS.0014.0021E Failed to invoke notification callback <service>: <exception>.

Cause: The Integration Server encountered an error while updating ACLs. Specifically, an error occurred when
the Integration Server invoked a service that is registered as a notification callback.
Response: Make sure that the service being invoked exists and can be executed.
ISS.0014.0022E Retrying service <service>. Retry count is <number>.

Cause: The Integration Server is retrying a service that was previously unsuccessful.
ISS.0014.0023E Available Thread Pool Threshold No Longer Exceeded: <number>% available.

Cause: The Integration Server is no longer exceeding the specified threshold for thread pool usage.
ISS.0014.0024E Server Initialization Aborted. See log messages.

Cause: During start up, the Integration Server encountered a serious internal error that caused it to shut down
immediately.
Response: Make sure that the machine on which the Integration Server runs has sufficient disk space. In
addition, make sure the operating system user that is trying to start the Integration Server has a sufficient
space allowance and has read/write permission to the directory on which the Integration Server resides.

ISS (IS Server)
ISS.0014.0029S Master password failed a sanity check.

Cause: During Integration Server initialization, the sanity check of the master password for outbound
passwords failed.
The Integration Server uses the master password to encrypt outbound passwords, which the Integration
Server uses to connect to applications or systems such as remote Integration Servers, proxy servers, or
databases. The outbound passwords are stored in files on the Integration Server and encrypted for security
purposes.
During initialization, the Integration Server performs a sanity check of the master password by attempting to
use it to decrypt a special, internal string that it previously encrypted using the master password. If the
decrypted internal string matches the clear text version of the string, the Integration Server knows the correct
master password was provided. This error is issued when the decrypted and clear text versions of the string
do not match.
Response: The sanity check of the master password can fail for a number of reasons:
- The outbound password file is corrupted.

- The master password file is corrupted.
- You mistyped the master password when you were prompted for it.
If you suspect you have mistyped the password, shut down the server and restart it, this time entering the
correct password. If this does not correct the problem, refer to the "When There Are Problems with the Master
Password or Outbound Passwords at Startup" section in the "Managing Server Security" chapter in the
"webMethods Server Administrator's Guide."
ISS.0014.0030S Master password updated.

Cause: The master password, which the Integration Server uses to encrypt outbound passwords, has been
successfully updated.
ISS.0014.0032E Could not connect to configured Repository Server. Shutting down server.
Cause: The Integration Server could not connect to a configured Repository Server. The Integration Server
shuts down. The Repository Server is the mechanism the Integration Server uses to store data in and retrieve
data from the repository.
Response: Before restarting the Integration Server, use the following command to start repository server:
webMethods6\IntegrationServer\reposerver\bin\repoui.bat (or bin/repoui.sh on UNIX)
Refer to the "webMethods Integration Server Clustering Guide" for information about working with
Repository Servers.

ISS.0014.0035S OutboundPasswordManager configuration directory cannot be null.

Cause: The Integration Server cannot locate the configuration directory it uses for managing outbound
passwords.
ISS.0014.0039S OutboundPasswordManager, (operation) caught this: type(exceptionClass), msg(exceptionMessage).

Cause: The code that the Integration Server uses to manage outbound passwords encountered a problem while
trying to perform the indicated operation.
Response: If the exception message text does not suggest a solution, contact webMethods Customer Care.
ISS.0014.9118U ServerReferenceManager can't get session to access object cache.

Cause: The Integration Server encountered an internal error with the object cache.
ISS.0014.9119U Unable to allocate a new thread in the
time specified.
Cause: The Integration Server has reached the configured limit for the number of new threads it can create.
After waiting unsuccessfully for resources to become available, the Integration Server issued this ISRuntime
exception.
This exception usually indicates a transient condition in which resources are temporarily unavailable. If this
error occurs during execution of a trigger, and retry is enabled, the Integration Server will automatically retry
the service. If, after a configured amount of time, the resources are still unavailable, the Integration Server
throws this exception.
Response: If the problem persists, use the Resource Settings page of the Server Administrator to specify thread
pool settings that are more appropriate for your environment.
ISS.0015.0002E Error <errorMessage> initializing Invoke Manager class <className> from <fileName>.
Cause: The Integration Server failed to initialize InvokeManager from the configuration file located at
<IntegrationServer_dir>/config/invokemanager.cnf file at startup.

ISS (IS Server)
ISS.0015.0003E Error <errorMessage> initializing Invoke Manager with <fileName>.

Cause: The Integration Server failed to initialize InvokeManager from the configuration file located at
<IntegrationServer_dir>/config/invokemanager.cnf file at startup.
Response: Using a text editor, open the <IntegrationServer_dir>/config/invokemanager.cnf file and make sure
that the content is not corrupt. If the error still occurs, consider removing the invokemanager.cnf file and
restarting the Server.
ISS.0015.0004E Service <serviceName> failed ACL access checking for user <userName>.
Cause: The client application failed to invoke the service because the current user did not have the Execute
ACL privileges to execute the service.
Response: Using the Integration Server Administrator, examine the ACL settings of the service as well as the
ACL group to which the current user belongs. Make sure that the user has the proper ACL settings.
ISS.0024.0005E Could not read users.cnf (the file may be corrupt).

Cause: The Integration Server could not read user and group configuration information from the users.cnf file.
The file might be corrupt.
Response: Examine this file in the Integration Server /config directory. Ensure that the server has read access to
it. If the file is corrupted, you might need to set up the users and/or groups again through the Administrator
UI.
ISS.0024.0006E Could not write users.cnf (the file may be corrupt).

Cause: The Integration Server could not write user and group configuration information to the users.cnf file.
The file might be corrupt.
Response: Examine this file in the Integration Server /config directory. Ensure that the server has write access
to it. If the file is corrupted, you might need to set up the users and/or groups again through the Administrator
UI.
ISS.0025.0034U Dispatcher could not be shutdown: <errorMessage>.

Cause: The Integration Server encountered a serious internal error while shutting down.
ISS.0025.0037U Audit Log Manager invalid value for auditGuaranteed found <stringValue>, config =<booleanValue>.
Cause: The Integration Server failed to start because the Audit Log Manager did not have valid configuration
value for the "watt.server.auditGuarantee" property.
Response: Open the <IntegrationServer_dir>\config\server.cnf file with a text editor, examine the property
"watt.server.auditGuarantee" and make sure that its value is either "true" or "false".

ISS.0025.0040I FIPS mode initialized.

Cause: The Integration Server is operating under Federal Information Processing Standards.
ISS.0025.0041I FIPS mode not initialized.

Cause: The Integration Server is not operating under Federal Information Processing Standards.
ISS.0025.0042S FIPS mode could not be initialized. Shutting down server: <exception msg>.
Cause: An error was encountered during initialization of FIPS mode operation.
Response: Contact webMethods Customer Care. Be prepared to provide configuration information related to
security provider and FIPS mode.
ISS.0025.0043S Integration server started in Safe Mode

Cause: The Integration Server is operating in safe mode either because it was started using the safeboot switch
or because there were problems with the master password. When in safe mode, the Integration Server is not
connected to any external resources, except the server’s own external repository, and you cannot update any
passwords.
If it is a master password problem, there will be other messages logged that indicate that there was a master
password problem.
Response: If you intended to start the Integration Server in safe mode, then no action is required. If the
Integration Server automatically started in safe mode due to a master password problem, see the "When There
Are Problems with the Master Password or Outbound Passwords at Startup" section of the "webMethods
Integration Server Administrator Guide."
ISS.0026.0002E Failure while loading service <serviceName>: <errorMessage>.

Cause: The Integration Server failed to install, enable, or reload the package because it could not load a service
in the package into its namespace.
Response: Examine the error message to determine the problem service. Usually this error occurs when a Java
service was not compiled before loading the package.
ISS.0026.0008E Error: Exception serializing Flow Service <errorMessage>.

Cause: The Integration Server encountered an internal error with a flow service.

ISS (IS Server)
ISS.0026.0009E Error: unknown flow operation type for node:<localName> in file:<fileName>.

Cause: The Integration Server encountered an internal error with a flow service.
ISS.0026.9101U Missing invoke attributes: <string>.

Cause: The Integration Server encountered an internal error while invoking a service.
ISS.0026.9106U Service Entry is NULL.

ISS.0028.0026E Invalid or corrupt namespace plug-in configuration found in <packageName> package.

Cause: The Integration Server could not read plug-in configuration information from the nsplugins.cnf file
associated with the indicated package.
ISS.0028.0039E Failure while loading document type <documentName>: <errorMessage>.

Cause: The Integration Server failed to load the document type into the namespace because another document
type with the same name was already being loaded into the Server's namespace.
Response: Examine the error message to determine the problem document types. Check both document types
to make sure they have different names. If both need to be loaded into the namespace, rename one and try
again.
ISS.0028.0040E Failure while loading schema <schemaName>: <errorMessage>.

Cause: The Integration Server failed to load the schema into the namespace because another schema with the
same name was already being loaded into the Server's namespace.
Response: Examine the error message to determine the problem schemas. Check both schemas to make sure
they have different names. If both need to be loaded into the namespace, rename one and try again.
ISS.0028.0041E Failure while loading element <elementName>: <errorMessage>.

Cause: The Integration Server failed to load the element into the namespace because another element with the
same name was already being loaded into the Server's namespace.
Response: Examine the error message to determine the problem elements. Check both elements to make sure
they have different names. If both need to be loaded into the namespace, rename one and try again.

ISS.0028.0044W Invalid classpath entry: <entry>.

Cause: An I/O error occurred when the Integration Server tried to access the file system to resolve the canonical
name of the directory in which the file exists.
Response: Check the file system for errors, such as problems with permissions and cyclical links.
ISS.0028.0045E Failed to install package <package>. Another package exists with the name <name>.
Cause: The Integration Server was unable to install a package because a package with the same name already
exists on the Integration Server.
Response: Rename the existing package or the one you are trying to install. Note that case does not matter; the
Integration Server considers "ABC" the same name as "abc".
ISS.0028.0046E Failed to read class <class> from input stream.

Cause: The Integration Server encountered an error while loading the indicated class.
Response: Check the audit log for messages about the underlying cause of the exception.
ISS.0028.0047E Unable to locate resource <bundle>.

Cause: The Integration Server encountered an error while loading the indicated resource.
Response: Check the Audit log for messages about the underlying cause of the exception.
ISS.0028.0051E Task scheduler startup service exited with the following error: (errorMessage)
Cause: The Integration Server encountered an error while executing the scheduler startup service task.
ISS.0028.0052E Task scheduler startup service (serviceName) was not found in (packageName) package
Cause: The package startup process could not locate the service named in the message.
ISS.0033.0103E Could not open the Repository. <errorMessage>.

ISS.0033.0104E Could not add server to the cluster. <errorMessage>.

Cause: The Integration Server failed to add a server to the cluster.
Response: Make sure that the server repository is running and that the connection to other servers is valid.

ISS (IS Server)
ISS.0033.0114E Failed to add server statistics to the Repository. <errorMessage>.

ISS.0033.0124E Failed to remove the expired sessions from the Repository. <errorMessage>.
Cause: The Integration Server failed to remove expired sessions from the Repository. This is an internal error.
ISS.0033.0151U The cluster is now not operational.

Cause: During server startup, the server detected a problem with its configuration that will prevent it from
being part of a cluster.
Response: Check the Clustering and Repository settings for your Integration Server. Refer to the "webMethods
Integration Server Clustering Guide." If you cannot determine the cause of the problem, contact webMethods
Customer Care.
ISS.0033.0153E Could not obtain a handle to ConnectionManager.

ISS.0033.0154E Could not persist session <sessionID> to Repository. <errorMessage>.

Cause: The Integration Server failed to persist the indicated session to the Repository. This is an internal error.
ISS.0033.0155E Could not query session <sessionID> from Repository. <errorMessage>.

Cause: An Integration Server in a cluster tried to update a session object, but was unable to find it. This in an
internal error.
ISS.0033.0156E Cluster Invoke did not complete successfully. Cluster Synchronization feature is not configured.
Cause: After a trigger configuration update, the Integration Server attempted to apply the change to other
Integration Servers in the cluster, but was unable to. The most likely reason is that the Cluster Synchronization
feature has not been properly configured.
Response: Review the "Cluster Synchronization for Trigger Management" section in the "webMethods Server
Administrator User's Guide" for instructions on configuring your cluster to propagate trigger changes to other
Integration Servers in the cluster.

ISS.0036.0002E Errors occurred invoking URL <errorMessage>.

Cause: A client application using the Java API did one of the following:
1) Tried to invoke the indicated folder or service name, but specified the wrong folder/service name.
2) Specified invalid certificates when setting up the SSL connection to the Integration Server.
Response: Examine the error stack trace to determine which exception was thrown. If it is a
MalformedURLException, check the folder/service name provided in the API call and make sure that you
specified the fully qualified service name. If it is a CertificateException, an IOException, or an
InvalidKeyException, check the certificates provided and make sure that they are valid.
ISS.0036.0009E Ping Failed.

Cause: A client application performed a periodic ping of a remote Integration Server. The ping resulted in an
exception.
Response: Verify that the remote Integration Server is up and running. In addition, verify that there is network
connectivity between the two servers.
ISS.0036.9103E Failed to invoke service.

Cause: The client application failed to invoke the specified service on the Integration Server via the
Context.invoke() method. There are several possible reasons: 1) the supplied service does not exist on the
server; 2) the server is temporarily unavailable; or 3) the client application does not have the proper ACL to
invoke the service.
Response: In the client application, examine the logic of the service being invoked and make sure that it
specifies the correct service name. Keep in mind that service names are case-sensitive. If the server is
temporarily down, wait until it is up again before you re-invoke.
ISS.0036.9104E Failed to invoke service on any server in cluster.

Cause: The client application failed to invoke the specified service on any server in the cluster via the
Context.invoke() method. There are several possible reasons: 1) the supplied service does not exist on the
server; 2) none of the servers are available; or 3) the client application does not have the proper ACL to invoke
the service.
Response: In the client application, examine the logic of the service being invoked and make sure that it
specifies the correct service name. Keep in mind that service names are case-sensitive. If the server is
temporarily down, wait until it is up again before you re-invoke.
ISS.0036.9107E Transport error encountered.


ISS (IS Server)
ISS.0036.9108U Specified server is not our partner.

Cause: The client application could not connect to the specified server via the Context.invoke() method because
the server is not a partner server.
ISS.0036.9110U Server Unreachable or Session Expired.

Cause: The client failed to connect to the Integration Server. The server is unavailable or the session expired.
Response: Make sure the server is up and running and then try reconnecting to it.
ISS.0036.9112U Unable to reset job manager - enabled.

Cause: The Integration Server failed to reset the job manager using Tcontext.resetJobManager because the it is
already enabled.
Response: In the client application, examine the logic and make sure that the job manager is not already
enabled when calling the API to reset it. If the logic seems correct, it is an internal error. Contact webMethods
Customer Care.
ISS.0051.0002E Error: <errorMessage>.

Cause: The Integration Server failed to add a port, remove a port, or edit an existing port because it could not
save ports properties to <IntegrationServer_dir>/config/port.cnf.
Response: Examine the port.cnf file to make sure that it is not corrupt and not Read-Only. If the file is corrupt,
you may need to remove the file and restart the Integration Server. After you do this, you can re-add ports to
the Server.
ISS.0055.0001E Critical Java Service error.

Cause: The Integration Server encountered a serious internal error.
ISS.0059.0001U Interrupted <service name>.

ISS.0070.0027U An I/O or Socket exception has occurred on <port number>.

Cause: The port is not available.
Response: Make sure that the specified port is available.

ISS.0070.9001E Invalid global service <serviceName>.

Cause: Invalid global service name provided for message processing.
An e-mail listener was started. When the Integration Server tried to determine which service to use for
message processing for this listener, the Integration Server detected a problem with the name of the service
specified as the Global Service. The Global Service overrides the setting for the Default Service or the service
specified in the e-mail message from the e-mail client.
The problem could be that the service name is specified in the wrong case (service names are case sensitive) or
that the specified service does not exist in the Integration Service's namespace.
Response: Examine the Global Service name provided. Make sure the name is in the correct case and that the
service exists in the Integration Server's namespace.
ISS.0070.9002E Invalid default service <serviceName>.

Cause: An e-mail listener was started. When the Integration Server tried to determine which service to use for
message processing for this listener, the Integration Server detected a problem with the name of the service
specified as the Default Service. The Integration Server executes the Default Service if no service is specified in
the e-mail message and no service is specified for the Global Service in the Email Client Configuration screen
on the Server Administrator.
The problem could be that the service name is specified in the wrong case (service names are case-sensitive) or
that the specified service does not exist in the Integration Server's namespace.
Response: Examine the Default Service name provided. Make sure the name is in the correct case and that the
service exists in the Integration Server's namespace.
ISS.0070.9011E An invalid port number was provided.

Cause: An administrator entered an invalid port number on a port configuration screen in the Server
Administrator.
Response: Specify a positive integer from 1 through 65534 for the port number.
ISS.0078.0103E Error while doing local invoke: <errorMessage>.

Cause: In a reverse invoke environment, the reverse invoke Integration Server was not able to invoke the
filtering service successfully. There are several possible reasons:
1) The name of the filtering service was not specified correctly on the "watt.server.revInvoke.filterSvcName"
parameter.
2) The service was associated with the wrong ACL. The proxy port should always be assigned to the
Anonymous ACL.

ISS (IS Server)
3) The proxy port's Access Mode was configured incorrectly. As a result, the service was not available for
execution from the port.
Response: Examine the value specified for property "watt.server.revInvoke.filterSvcName" and make sure the
fully qualified service name was provided. Remember that service names are case-sensitive.
Check the access mode of the proxy port and make sure it is set to Deny by Default and that the allow list for
the port includes the filtering service. To check the Access Mode, use the Server Administrator for the reverse
invoke server and go the Security>Ports page. For more information, see the "Managing Server Security"
chapter of the "webMethods Integration Server Administrator's Guide."
Check the ACL assignment for the service and make sure it is set to Anonymous. To check the ACL
assignment, use the Server Administrator for the Reverse Invoke server and go to the
Packages>Management>Browse Folder page. For more information, see the "Managing Server Security"
chapter of the "webMethods Integration Server Administrator's Guide."
ISS.0084.9001E Invalid credentials.

Cause: The user name or password is invalid, or the client did not present a certificate to the Integration Server
for the HTTPS request.
Response: In the client application, examine the logic and make sure that: (1) the correct username and
password is provided for the HTTP request, and (2) a valid client certificate is provided for the HTTPS request
when the "Client Authentication" setting is "Require Client Certificates".
ISS.0084.9002E Invalid SSL credentials.

Cause: The client certificate is not valid. The Integration Server requires client certificates for all HTTPS
requests.
Response: In the client application, examine the logic and make sure that a valid client certificate is provided
for the HTTPS request.
ISS.0084.9003U Certificate not signed by trusted Certificate Authority.

Cause: The client certificate was not signed by a trusted certificate authority. The Integration Server requires
client certificates for all HTTPS requests.
Response: In the client application, examine the logic and make sure that a valid trusted client certificate is
provided for the HTTPS request.
ISS.0084.9005E Invalid Session ID or Session Expired.

Cause: The session associated with the client is invalid or expired due to a long period of idle time.
Response: Re-login to the Integration Server. If this error frequently occurs, you can increase the Session
Timeout setting to an appropriate value on the Resources screen in the Integration Server.

ISS.0084.9006U Server is not accepting new requests at this time.

Cause: If it was a normal invoke environment, the Integration Server was temporarily unable to fulfill the
request because it was in a shutdown-restart process. If it was a Reverse Invoke environment, the internal
server could not serve the request because it was temporarily unavailable due to a transient network outage.
Response: For a normal invoke, check the Integration Server's status and resubmit the request until the
Integration Server is up. For a reverse invoke, check the network connection and the internal server's status.
Resubmit the request when the connection returns or when the server is up.
ISS.0084.9007U Server has reached client limit.

Cause: The Integration Server could not fulfill the client's request because it reached its client limit.
Response: In the Integration Server's license, check the number of licensed sessions. If the number of users who
access the Integration Server is more than that specified in the license, consider upgrading your license to
obtain more user seats.
ISS.0084.9008E User name cannot be empty or null.

Cause: webMethods Monitor failed to resubmit the rejected document because the "userName" field in the data
was either null or empty.
Response: Examine the document to be resubmitted and make sure that it is valid and that the "userName"
ISS.0084.9009U Access is denied to the user.

Cause: webMethods Monitor failed to resubmit the rejected document because the current user does not have
access privileges to invoke the service specified in the "serviceName" field in the data.
Response: Examine the document to be resubmitted and the Execute ACL setting for the service. Make sure
that the current user has the correct ACL.
ISS.0084.9101U Access Denied.

Cause: The Integration Server could not execute the requested service request because the service was not
available from the specified port.
Response: Log on to Server Administrator. From the Settings>Ports page, examine the "Port Service Access
Settings" and "Deny List" for the port. Make sure the service to be invoked is NOT included in the port's Deny
List.
ISS.0084.9301U Not Authorized to use Server.

Cause: The Integration Server encountered an internal error because it could not authorize the user.

ISS (IS Server)
ISS.0085.9203E Errors occurred while updating remote aliases (<numberOfErrors> of <numberOfUpdates> updates failed).
See server logs for more details.
Cause: The Integration Server encountered an error while trying to update remote aliases as part of the Cluster
Synchronization process. Cluster Synchronization makes sure that changes made to a trigger's configuration
on one Integration Server are propagated to other servers in the cluster. If an Integration Server is configured
for Cluster Synchronization, this process runs when an administrator makes a trigger configuration change
through the Server Administrator or when a user-written service calls one of the pub.trigger: services.
Response: Check the server logs on the local server and remote servers for errors related to the Cluster
Synchronization process. After correcting the problem, retry the task you were performing when the error
occurred.
ISS.0085.9204E Local update failed: <errorMessage> (Note: The cluster synchronization will not run until all local errors are
resolved.)
Cause: The Integration Server encountered an error while trying to perform the Cluster Synchronization
process. Cluster Synchronization makes sure that changes made to a trigger's configuration on one Integration
Server are propagated to other servers in the cluster. If an Integration Server is configured for Cluster
Synchronization, this process runs when an administrator makes a trigger configuration change through the
Server Administrator or when a user-written service calls one of the pub.trigger: services.
In this case, the Cluster Synchronization process failed on the local server. As a result, it was not attempted on
any of the external nodes in the cluster.
Response: Check the server log on the local server for errors related to the Cluster Synchronization process.
After correcting the problem, retry the task you were performing when the error occurred.
ISS.0086.8117U Task being updated is not a one-time task.

Cause: The pub.scheduler:updateOneTimeTask service failed to execute because an invalid task ID was
supplied. The task was not a one-time task.
Response: Examine the server input and make sure the "taskID" parameter specifies the correct task ID. This
error usually occurs when you supply the task ID of a repeating task or a complex task, instead of a one-time
task.
ISS.0086.9000E Recipient certificate at index <location> not in recognizable format.

Cause: The pub.smime:createEncryptedData or pub.smime:createSignedAndEncryptedData service failed to
execute because the Integration Server could not recognize the certificate of one of the message recipients.
Response: Examine the error message to determine which recipient certificate was not in the correct format.
Then, check the "recipientCerts" parameter and make sure it specifies a valid X.509 certificate.

ISS.0086.9001U bytes must be byte[].

Cause: The pub.string:bytesToString service failed to execute because the value supplied for the "bytes"
parameter is not an instance of bytes[].
Response: Examine the service input and make sure it specifies the correct value for the "bytes" parameter.
ISS.0086.9004U URL is null.

Cause: The Integration Server could not successfully invoke the pub.client:http service because the required
parameter "url" was not supplied.
Response: Examine the input for this service to make sure it sets the value for "url."
ISS.0086.9005U URL must begin with 'http:' or 'https:'.

Cause: The Integration Server could not successfully invoke the pub.client:http service because the value
specified for "url" was not correct. This error occurs if the value passed to "url" does not start with "http" or
"https."
Response: Examine the value for "url" and make sure it passes the correct value. (e.g.,
http://www.webMethods.com instead of www.webMethods.com.
ISS.0086.9006U HTTP method is null.

Cause: The Integration Server could not successfully invoke the pub.client:http service because the required
parameter "method" is not supplied.
Response: Examine the input for this service to make sure it sets the value for "method".
ISS.0086.9007U only use one of: data.stream, data.bytes or data.mimeStream on a POST.

Cause: The "pub.client:http" service failed to execute because the input passed to the service included more
than one parameter. Only one parameter ("bytes", "stream", "mimeStream") is allowed when the parameter
method is "post."
Response: Examine the input passed to the pub.client:http service and make sure it specifies only one
parameter.
ISS.0086.9008U do not use: data.stream, data.bytes or data.mimeStream on a GET.

Cause: The pub.client:http service failed to execute because the "bytes", "stream", or "mimeStream" parameter
was passed to the service, but these parameters are unnecessary when the "method" parameter is "get".
Response: Do not pass "bytes", "stream", or "mimeStream" parameter to the pub.client:http service the
"method" parameter is "get".

ISS (IS Server)
ISS.0086.9010E invalid HTTP method: <methodName>.

Cause: The pub.client:http service specified an invalid method.
Response: Provide a valid method. Valid methods are: "get", "post", "head", "put", "delete", "options", "trace".
ISS.0086.9015E files must be of type Values[].

Cause: The pub.client:http service specified an invalid value for the "attachments" input field.
Response: Examine the value for input parameter "attachments" and ensure that it is of type IData[].
ISS.0086.9018U pattern' is a required input.

Cause: The pub.date:getCurrentDateString service failed to execute because the required "pattern" parameter
was not supplied.
Response:
Response: Examine the service input and make sure it specifies the correct value for the "pattern" parameter.
ISS.0086.9019U No filename supplied.

Cause: The "pub.file:getFile" service failed to execute because the required "filename" parameter was not
supplied.
Response: Examine the service input and make sure it specifies the correct value for the "filename" parameter.
ISS.0086.9020U <fileName> does not exist.

Cause: The pub.file:getFile service failed to execute because the file specified by the "filename" parameter does
not exist.
Response: Examine the service input and make sure that the file specified for the "filename" parameter exists in
the file system.
ISS.0086.9021E <fileName> cannot be read.

Cause: During execution of the pub.file:getFile service, the Integration Server detected that it could not read the
file specified by the "filename" property because the user running the job does not have access to the file.
Response: Make sure the correct file name was entered for the "filename" property. If it was, check the file
properties and make sure the correct permissions have been set.

ISS.0086.9022U <fileName> is a directory.

Cause: The pub.file:getFile service failed to execute because the file specified by the "filename" parameter is a
directory, not a file.
Response: Examine the service input and make sure the file specified by the "filename" parameter is indeed a
file, not a directory. This error usually occurs if you do not specify the whole path of the file.
ISS.0086.9025U Saved pipeline <pipelineName> does not exist.

Cause: The pub.flow:restorePipeline service failed to execute because the pipeline specified by the "$name"
parameter does not exist in the Integration Server.
Response: Examine the service input and make sure the pipeline specified for the "$name" parameter is exactly
the same for both pub.flow:savePipeline and pub.flow:restorePipeline services. Remember that "$name" is
case-sensitive.
ISS.0086.9027U InvokeState not available.

ISS.0086.9028E getLastError invoked outside of a Flow.

Cause: A service that is not a Flow service attempted to invoke the "pub.flow:getLastError" service. The
"pub.flow:getLastError" service must be invoked from a Flow service; it cannot be invoked from a Java Service
or a C service.
Response: Do not invoke the "pub.flow:getLastError" service from a Java service or a C service. Invoke it from a
Flow service instead.
ISS.0086.9029U parameter 'key' is required when fromList is not null.

Cause: The pub.list:stringListToDocumentList service failed to execute because the required "key" parameter
was not supplied. This parameter must be supplied when the value for the "fromList" parameter is not null.
Response: Examine the service input and make sure it specifies a value for the "key" parameter when the
"fromList" value is not null.
ISS.0086.9030U input must be an InputStream.

Cause: The pub.mime:createMimeData service failed to execute because the value provided for the "input"
parameter was not an instance of "java.io.InputStream".
Response: Examine the service input and make sure it specifies the correct value for the "input" parameter.

ISS (IS Server)
ISS.0086.9031U index must be a non-negative integer.

Cause: The pub.mime:getEnvelopStream, pub.mime:getBodyPartHeader, or pub.mime:getBodyPartContent
service failed to execute because an incorrect value was supplied for the "index" parameter. The value for
"index" must be a non-negative integer.
Response: Examine the service input and make sure it specifies the correct value for the "index" parameter. This
parameter identifies the body part. The first body part is index number 0.
ISS.0086.9032U <mimeData> input parameter required.

Cause: The pub.mime:addBodyPart service failed to execute because the required "mimeData" parameter was
not supplied.
Response: Examine the service input and make sure it specifies a valid value for the "mimeData" parameter.
This IData object is usually produced by the pub.mime:createMimeData service.
ISS.0086.9033U content input parameter required.

Cause: The pub.mime:addBodyPart service failed to execute because the required "content" parameter was not
supplied.
Response: Examine the service input and make sure it specifies a valid value for the "content" parameter. You
can use an InputStream or a MIME object for this parameter.
ISS.0086.9034U Message content is not empty.

Cause: The pub.mime:addBodyPart service failed to execute because the "replace" parameter was set to "no"
and there was already a payload in the mimeData. When the "replace" parameter (used only when the
"multipart" parameter is used) is set to "no," the Integration Server throws this exception to notify you that the
mimeData already contains data.
Response: Examine the service input for the "multipart" and "replace" parameters. If "multipart" is set to "no",
use the default value "yes" for "replace". Or, set the value for "multipart" to "yes" and the service will append
the payload to the mimeData.
ISS.0086.9035U Missing required value: {xmlvalues}.

Cause: The pub.document:XMLValuesToDocument service failed to execute because the required "(No
Suggestions)" parameter was not supplied.
Response: Examine the service input and make sure it specifies the correct value for the "xmlvalues" parameter.
Note: This String must contain a webMethods XMLValues encoding of a document. No other encoding format
is accepted.

ISS.0086.9036U Missing required value: {record}.

Cause: The pub.record:recordToRecordList service failed to execute because the required "record" parameter
was not supplied.
Response: Examine the service input and make sure it specifies the correct value for the "record" parameter .
ISS.0086.9037U Missing one or more required values: {recordList,name}.

Cause: The pub.record:recordListToRecord service failed to execute because the required "recordList" and
"name" parameters were not supplied.
Response: Examine the service input and make sure that it specifies the correct values for the "recordList" and
"name" parameters. Neither one should be empty.
ISS.0086.9038E Invalid certificate input.

Cause: The pub.smime:createCertsOnlyData service failed to execute because an invalid value was supplied
for the "certificates" parameter.
Response: Examine the service input and make sure that it specifies the correct byte[][] for the "certificates"
parameter. Each byte[] should represent a single certificate. See the "webMethods Integration Server Built-In
Services Reference" for more information.
ISS.0086.9039U Certificate not in recognizable format.

Cause: The pub.smime:createCertsOnlyData service failed to execute because the Integration Server did not
recognize the certificate supplied.
Response: Examine the service input and make sure the "certificates" parameter specifies a valid X.509
certificate.
ISS.0086.9040U Certificate at index <location> not in recognizable format.

Cause: The pub.smime:createCertsOnlyData service failed to execute because the Integration Server did not
recognize one of the certificates supplied.
Response: Examine the service input and make sure that all the certificates specified by the "certificates"
parameter are valid X.509 certificates.
ISS.0086.9041E Invalid certificate input at index <location>.

Cause: The pub.smime:createCertsOnlyData, pub.smime:createSignedData, or
pub.smime:createSignedAndEncryptedData service detected an invalid certificate at the specified location.
The location is specified by an index number.
Response: Examine the service input and make sure that the certificate at the specified location is a valid X.509
Certificate.

ISS (IS Server)
ISS.0086.9042E Could not create certs only SMIME object <errorMessage>.

ISS.0086.9043E Not a valid InputStream.

Cause: A pub.smime service failed to execute because the "envStream" or "SMimeEnvStream" parameter
contains an invalid value.
Response: Examine the service input and make sure the "envStream" or "SMimeEnvStream" parameter
specifies a valid value. The value must be an instance of java.io.InputStream.
ISS.0086.9044U InputData not in recognizable format.

Cause: A pub.smime service failed to execute because the Integration Server could not recognize the input
stream that contained the MIME message to be processed.
Response: Examine the service input for the "envStream" or "SMimeEnvStream" parameter. Generally, the
input for "envStream" is produced by the pub.mime:getEnvelopeStream service and "SMimeEnvStream" is
produced by either the pub.smime:createSignedData or pub.smime:createEncryptedData service. The input
must be a Java InputStream object.
ISS.0086.9045E Invalid recipient certificates information.

Cause: A pub.smime service failed to execute because the "recipientCerts" parameter contains an invalid value.
Response: Examine the service input and make sure that you have specified byte[][] for the "recipientCerts"
parameter correctly. Each byte[] should represent a certificate for a single recipient. See the "webMethods
Integration Server Built-In Services Reference" for more information.
ISS.0086.9046E Invalid recipient certificate input at index <location>.

execute because an incorrect value was supplied for an e-mail recipient's certificate.
Response: Examine the service input and make sure it specifies the correct input byte[] for the recipient's
certificate. See the "webMethods Integration Server Built-In Services Reference" for more information.
ISS.0086.9047U Incorrect keylength specified: <keyLength>.

execute because keyLength parameter contains an invalid key length.
Response: Examine the service input and make sure that the length of the encryption key for RC2 encryption is
40, 64, or 128. The "keyLength" parameter is ignored if the encryption algorithm is not RC2.

ISS.0086.9048U Unsupported encryption algorithm specified: <algorithmName>.

execute because an encryption algorithm that is not supported by the Integration Server was supplied.
Response: Examine the service input make sure that it specifies TripleDES, DES, or RC2 for the encryption
algorithm.
ISS.0086.9049E Could not create SMIME Enveloped object <errorMessage>.

ISS.0086.9050E Invalid private key information.

Cause: A pub.smime service failed to execute because the private key supplied was not in the correct format.
Response: Examine the service input and make sure the "privKey" parameter specifies an instance of byte[ ]
and that it is an RSA private key.
ISS.0086.9051E Invalid certificates information.

Cause: The pub.smime:createSignedData or pub.smime:createSignedAndEncryptedData service failed to
execute because the certificate chain of the party signing the message was not an instance of byte[ ][ ].
Response: Examine the service input and make sure the certificates parameter is a byte[ ][ ] and that each byte[
] represents a single certificate in the chain.
ISS.0086.9052E Invalid signer certificate file information.

execute because the digital certificate of the party signing the supplied message was not an instance of byte[ ].
Response: Examine the service input and make sure the "signerCert" parameter specifies a byte[ ][ ] and that
each byte[ ] represents a single certificate in the chain.
ISS.0086.9053U Certificate file not in any recognizable format.

execute because the digital certificate of the party signing the supplied message was not in a recognizable
format.
Response: Examine the service input and make sure the "signerCert" parameter specifies a valid X.509
certificate.

ISS (IS Server)
ISS.0086.9054E Could not create signed SMIME object <errorMessage>.

ISS.0086.9055E Could not retrieve content from input.

ISS.0086.9056U Encrypted Content not in recognizable format.

Cause: The MIME message supplied is not encrypted.
Response: Make sure that the MIME message is encrypted
ISS.0086.9057U Recipient certificate not in any recognizable format.

Cause: The "pub.smime:processEncryptedData" service failed to execute because the digital certificate of the
party receiving the message was not in a recognizable format.
Response: Examine the service input and make sure the "recipientCert" parameter specifies a valid X.509
certificate.
ISS.0086.9058E Supplied certificate cannot decrypt content.

Cause: The certificate and private key supplied are unable to decrypt the content.
Response: Make sure that the correct certificate and private key pair are supplied to decrypt the content.
ISS.0086.9059E Not a valid privateKey.

Cause: The pub.smime:processEncryptedData service failed to execute because the private key supplied was
not valid. It might have the wrong encoding or key length.
Response: Examine the service input and make sure that the private key supplied for decrypting the encrypted
message is valid. Also make sure that you use the party's public key to encrypt the message and supply its
private key here to decrypt the message.
ISS.0086.9060U Unable to decrypt symmetric key.

Cause: The private key supplied is unable to decrypt the message.
Response: Make sure that the correct private key is supplied.

ISS.0086.9061U Certs-Only data not in recognizable format.

Cause: The pub.smime:processCertsOnlyData service failed to execute because the SMIME entity supplied was
not in the correct format.
Response: Examine the service input and make sure that the supplied SMIME entity is a PKCS7 certs-only
SMIME entity.
ISS.0086.9062U Signed Content not in recognizable format.

Cause: The pub.smime:processSignedData service failed to execute because the Integration Server could not
recognize the signed SMIME entity that was supplied.
Response: Examine the service input and make sure the supplied SMIME entity was successfully signed and in
the correct format.
ISS.0086.9063U Missing required value: string.

Cause: The pub.string:base64Decode service failed to execute because the required "string" parameter was not
supplied.
Response: Examine the service input and make sure that it specifies the correct value for the "string" parameter.
ISS.0086.9064U bytes must be type byte[].

Cause: The pub.string:base64Encode service failed to execute because the "bytes" parameter contained an
invalid value.
Response: Examine the service input and make sure it specifies the correct byte[] to the "bytes" parameter. See
the "webMethods Integration Server Built-In Services Reference" for more information.
ISS.0086.9074E Cannot process null input.

Cause: The pub.security.util:getCertificateInfo service failed to execute because the required "certificate"
parameter was not supplied.
Response: Examine the service input and make sure it specifies the correct byte[] for the "certificate" parameter.
Note the byte[] should represent a valid X.509 certificate.
ISS.0086.9075U Input not a byte array.

Cause: The pub.security.util:createMessageDigest service failed to execute because the value supplied for the
"input" parameter was not the correct type. Or, the pub.security.util:loadPKCS7CertChain service failed to
execute because the value supplied for the "CertificateChain" parameter was not correct. Input for these
parameters must be byte type array or an instance of a byte array object.
Response: Examine the service input and make sure it specifies the correct byte[] for these parameters. See the
"webMethods Integration Server Built-In Services Reference" for more information.

ISS (IS Server)
ISS.0086.9076E Input in incorrect format, certificate cannot be loaded.

Cause: The pub.security.util:loadPKCS7CertChain service failed to execute because the certificate chain
supplied was not in PKCS7 format.
Response: Examine the service input and make sure the supplied certificate chain is in PKCS7 format.
ISS.0086.9077U No algorithm has been specified.

Cause: The service pub.security.util:createMessageDigest failed to execute because the required "algorithm"
Response: Examine the service input and make sure it specifies a valid value for the "algorithm" parameter. The
service uses this algorithm to compute the message digest. The algorithm must be either MD5 or SHA-1.
ISS.0086.9078U Unsupported algorithm specified.

Cause: The pub.security.util:createMessageDigest service failed to execute because the value supplied for the
"algorithm" parameter is not a supported algorithm.
Response: Examine the service input and make sure that it passes a supported algorithm to the "algorithm"
parameter. Only MD5 or SHA-1 can be used to compute the message digest.
ISS.0086.9079U No keys provided to sign the provided data.

Cause: The service pub.security.pkcs7:sign failed to execute because the required "signerInfo" parameter was
not supplied.
Response:
Response: Examine the service input and make sure it specifies a valid value for the "signerInfo" parameter.
ISS.0086.9080U Data to sign not in the expected format (byte[]).

Cause: The pub.security.pkcs7:sign service failed to execute because the value supplied for the "data"
parameter was not the correct data type.
Response: Examine the service input and make sure that it specifies the correct byte[] for the "data" parameter.
See the "webMethods Integration Server Built-In Services References" for more information.
ISS.0086.9081E An error occurred processing the signer information for <location>, <errorMessage>.
Cause: The pub.security.pkcs7:sign service failed to execute because one part of the signer's information was
invalid. This may be because the certificate chain of the signer was invalid or the private key used to sign the
data was invalid.
Response: Examine the error message to determine which signer was invalid. Make sure that the certificate
chain and the private key supplied are supported by the webMethods Integration Server.

ISS.0086.9082E An error occurred creating the signature for the data: <errorMessage>.
Cause: The pub.security.pkcs7:sign service failed to execute because a general exception occurred.
Response: Examine the error message and make sure that valid signer information is supplied. If all are correct,
then contact webMethods Customer Care.
ISS.0086.9083U No signature provided to verify.

Cause: The pub.security.pkcs7:verify service failed to execute because the required "signature" parameter was
not supplied.
Response: Examine the service input and make sure it specifies the correct value for the "signature" parameter.
ISS.0086.9084U No data provided to verify detached signature.

Cause: The pub.security.pkcs7:verify service failed to execute because the required "data" parameter was not
supplied.
Response: Examine the service input and make sure it specifies the correct byte[] input for the "data"
parameter. See the "webMethods Integration Server Built-In Services Reference" for more information.
ISS.0086.9085E An error occurred attempting to reconstruct the signature: <errorMessage>.

Cause: The pub.security.pkcs7:verify service failed to execute because a general exception occurred while
reconstructing the signature.
Response: Examine the error message and make sure that valid input to the service is supplied. If all are
correct, then contact webMethods Customer Care.
ISS.0086.9086U Signature provided is not PKCS#7 SignedData.

Cause: The pub.security.pkcs7:verify service failed to execute because the signed data supplied was not a DER
encoding of the PKCS#7 SignedData object.
Response: Examine the service input. If you are processing a detached signature, examine the value passed to
both the "signature" and "data" parameters. If you are processing an implicit signature, check the value passed
to the "signature" parameter.
ISS.0086.9087E Invalid data encountered when building the certificate chain, either an instance of a certificate or a byte[]
expected
Cause: The pub.security.pkcs7:verify service failed to execute because the input supplied for the certificate in
the certificate chain is not an instance of byte[ ].
Response: Examine the input for the "certChain" parameter. Make sure that each certificate in the certificate
chain is an instance of byte[ ].

ISS (IS Server)
ISS.0086.9088E Invalid data provided for certificate entry <location>, expecting a byte[].
Cause: The pub.security.pkcs7:sign service failed to execute because one of the certificates in the signer's
certificate chain was not in the correct format.
Response: Examine the service input and make sure the "certChain" field of the "signerInfo" parameter is
specified as byte[ ].
ISS.0086.9089U Parameter <paramName> is missing.

Cause: A WmPublic service failed to execute because a required parameter was not supplied.
Response: Examine the service input and the error message and make sure it specifies a value for this
parameter.
ISS.0086.9090U Parameter <paramName> is of incorrect type.

Cause: A WmPublic (pub.xml and pub.web) service failed to execute because the data supplied for the
indicated parameter was of the wrong data type.
Response: Examine the service input and make sure it specifies an object of the correct data type for the
parameter. See the "webMethods Integration Server Built-In Services Reference" for service input details.
ISS.0086.9091U Parameters <xmldata>, '$filestream' and '$filedata' are all missing. One of these must not be null.
Cause: The pub.xml:xmlStringToXMLNode or pub.web:stringToDocument service failed to execute because
none of the required parameters (xmldata, $filestream, $filedata) was supplied.
Response: Examine the service input and make sure it specifies a value for one of the indicated parameters
(xmldata, $filestream, $filedata).
ISS.0086.9092E Http Error: <statusCode>.

Cause: The pub.xml:loadXMLNode service failed to retrieve a document from the URL specified in the "url"
parameter because the web server returns a HTTP status code between 400 and 599. This indicates that an
error occurred during the request. This exception occurs only when the "failOnHTTPError" parameter is set to
"true".
1) Ignore the HTTP errors by setting the "failOnHTTPError" parameter to "false".
2) Examine the HTTP status code and message and refer to RFC 2068 on the HTTP protocol to identify the
reason and correct the problem.
ISS.0086.9093E Http Error: <statusCode> - <statusMessage>.

Cause: The pub.xml:loadXMLNode service failed to retrieve a document from the URL specified in the "url"
parameter because the web server returns an HTTP status code between 400 and 599. This indicates that an

error occurred during the request. This exception occurs only when the "failOnHTTPError" parameter is set to
"true".
1) Ignore the HTTP errors by setting the "failOnHTTPError" parameter to "false".
2) Examine the HTTP status code and message and refer to RFC 2068 on the HTTP protocol to identify the
reason and correct the problem.
ISS.0086.9094U No LDAP URL specified

Cause: The pub.ldap:connect service failed to execute because the required "ldapUrl" parameter was not
supplied.
Response: Examine the service input and make sure the value of the "ldapUrl" parameter is the URL of the
directory server.
ISS.0086.9095E No connection key provided.

Cause: A pub.ldap service failed to execute because the required "ldapConnectionKey parameter was not
supplied.
Response: Examine the service input and make sure the "ldapConnectionKey" parameter specifies the LDAP
server. You can obtain this key by executing the pub.ldap:connect service.
ISS.0086.9096E Bad connection key: <ldapConnectionKey>.

Cause: A pub.ldap service failed to execute because an invalid connection key was supplied.
Response: Examine the service input and make sure it correctly specifies the LDAP connection key. You can
obtain this key by executing the pub.ldap:connect service.
ISS.0086.9097U No lookup name provided.

Cause: The pub.ldap:lookup, pub.ldap:update, or pub.ldap:delete service failed to execute because the
required "ldapLookupName" parameter was not supplied.
Response: Examine the service input and make sure it correctly specifies the name you want to modify, delete,
or look up in the LDAP directory.
ISS.0086.9098U No search filter provided.

Cause: The pub.ldap:search service failed to execute because the required "ldapSearchFilter" parameter was
not supplied.
Response: Examine the service input and make sure it specifies a value for the "ldapSearchFilter" parameter.
This parameter specifies the filter that describes which entries to return.

ISS (IS Server)
ISS.0086.9099U No target name provided.

Cause: The pub.ldap:bind service failed to execute because the required ldapTargetName parameter was not
supplied.
Response: Examine the service input and make sure it specifies an "ldapTargetName" parameter. This
parameter specifies the name of the entry you want to add into the LDAP server.
ISS.0086.9100U No modifications specified.

Cause: The pub.ldap:update service failed to execute because the required parameter "ldapAttributeMods"
Response: Examine the service input and make sure it specifies the appropriate value for the
"ldapAttributeMods" parameter. This parameter contains the modifications to make to an entry in the LDAP
directory.
ISS.0086.9101U No objectclass provided.

Cause: The pub.ldap:getClassDef service failed to execute because the required "ldapObjectClass" parameter
was not supplied.
Response: Examine the service input and make sure it specifies an appropriate value for "ldapObjectClass"
parameter. This parameter contains the name of the object class for which you want to retrieve the definition.
ISS.0086.9102U No schema information available.

ISS.0086.9110U No service specified.

Cause: A pub.scheduler service failed to execute because the required "service" parameter was not supplied.
Response: Examine the service input and make sure the "service" parameter specifies the fully qualified name
of the service you want to schedule for execution on the Integration Server. Remember that service names are
case-sensitive.
ISS.0086.9111U No taskID specified.

Cause: A pub.scheduler service failed to execute because the required "taskID" parameter was not supplied.
Response: Examine the service input and make sure the "taskID" parameter specifies a valid task identification
number. You can retrieve a list of identification numbers for of all tasks currently in the Scheduler by invoking
the pub.scheduler:getTaskIDs service.

ISS.0086.9112E Invalid taskID specified.

Cause: A pub.scheduler service failed to execute because an invalid task identification number was supplied.
Response: Examine the service input and make sure the ''taskID" parameter specifies a valid task identification
number. You can retrieve a list of identification numbers for of all tasks currently in the Scheduler by invoking
the pub.scheduler:getTaskIDs service.
ISS.0086.9113U No such user present: <userName>.

Cause: A pub.scheduler service failed to execute because an invalid user ID was supplied.
Response: Examine the service input and make sure that it specifies a valid user ID under which the service is
to be executed.
ISS.0086.9114U No time specified.

Cause: The pub.scheduler:addOneTimeTask service failed to execute because the required "time" parameter
was not supplied.
Response: Examine the service input and make sure the "time" parameter specifies the time at which to run the
service, in HH:mm:ss format.
ISS.0086.9115U No date specified.

Cause: The pub.scheduler:addOneTimeTask service failed to execute because the required "date" parameter
was not supplied.
Response: Examine the service input and make sure the "date" parameter specifies the date on which to run the
service, in yyyy/MM/dd format.
ISS.0086.9116U No interval specified.

Cause: The pub.scheduler:addRepeatingTask service failed to execute because the required "interval"
Response: Examine the service input and make sure the "interval" parameter specifies the time interval
(measured in seconds) between executions of the task.
ISS.0086.9118U Task being updated is not a repeating task.

Cause: The pub.scheduler:updateRepeatingTask service failed to execute because an invalid task ID was
supplied. The task was not a repeating task.
error usually occurs when you supply a one-time task or complex task instead of a repeating task.

ISS (IS Server)
ISS.0086.9119U Task being updated is not a complex task.

Cause: The pub.scheduler:updateComplexTask service failed to execute because an invalid task ID was
supplied. The task was not a complex task.
error usually occurs when you supply the task ID of a one-time task or repeating task, instead of a complex
task.
ISS.0086.9120E Inputs cannot be null.

Cause: The pub.security:setKeyAndChain service failed to execute because one or both of the required
"privKeyFile" and "certFiles" parameters were not supplied.
Response: Examine the service input and make sure that values are specified for both the "privKeyFile" and
"certFiles" parameters.
ISS.0086.9121E Certificate file not found: <fileName>.

Cause: The pub.security:setKeyAndChain service failed to execute because the certificate files supplied do not
exist in the system.
Response: Examine the service input and verify that the "certFiles" parameter specifies the correct names of
certificate files. These files contain the certificates that comprise the certificate chain.
ISS.0086.9122U Certificate file <fileName> not in any recognizable format.

Cause: The pub.security:setKeyAndChain service failed to execute because the Integration Server does not
recognize the certificate file(s) provided.
Response: Examine the server input and make sure the certificates specified by the "certFiles" parameter are
valid X.509 certificates.
ISS.0086.9123E IO Exception encountered while reading file: <fileName>.

Cause: The pub.security:setKeyAndChain service failed to execute because an I/O exception occurred when the
Integration Server tried to read either the private key or the certificates.
Response: Examine the error message provided to determine which file encountered the I/O exception, then
check the file properties and make sure the Integration Server has read access to the file.
ISS.0086.9124E Invalid datastore name or datastore is not registered.

Cause: A pub.storage service failed to execute because the supplied datastore is empty or unregistered. Before
using the repository, you must use the pub.store:registerStore to create the repository and register it with the
Integration Server.
Response: Examine the service input and make sure the "storeName" parameter specifies the name of the store
to be used for various operations. Also, verify that the repository store has been created and registered.

ISS.0086.9125E Invalid datastore name.

Cause: The pub.storage:registerStore service failed to execute because the required "storeName" parameter was
not supplied.
Response: Examine the service input and make sure the "storeName" parameter specifies the name of the store
to register.
ISS.0086.9127E key of value to add can not be null.

Cause: The pub.storage:add service failed to execute because the required "key" parameter was not supplied.
Response: Examine the service input and make sure the "key" parameter specifies the key under which the
entry is to be inserted in the data store.
ISS.0086.9128E key of entry to insert or update can not be null.

Cause: The pub.storage:put service failed to execute because the required "key" parameter was not supplied.
Response: Examine the service input and make sure the "key" parameter specifies the key where you want to
insert or update the entry .
ISS.0086.9129E key of entry to get can not be null.

Cause: The pub.storage:get service failed to execute because the required "key" parameter was not supplied.
Response: Examine the service input and make sure the "key" parameter specifies the key of the entry whose
value you want to retrieve.
ISS.0086.9130E value to add can not be null.

Cause: The pub.storage:add service failed to execute because the required "value" parameter was not supplied.
Response: Examine the service input and make sure the "value" parameter specifies a value to be inserted in the
store.
ISS.0086.9131E key of entry to remove can not be null.

Cause: The pub.storage:remove service failed to execute because the required "key" parameter was not
supplied.
Response: Examine the service input and make sure the "key" parameter specifies the key of the entry you want
to remove.

ISS (IS Server)
ISS.0086.9132E value to insert or update can not be null.

Cause: The pub.storage:put service failed to execute because the required "value" parameter was not supplied.
Response: Examine the service input and make sure the "value" parameter specifies a value to be put into the
store. If the key does not exist in the data store, then the entry is inserted. If the key already exists in the store,
then its value is updated and the associated entry is unlocked.
ISS.0086.9133E Cannot obtain entry lock for key.

Cause: A pub.storage service failed to execute because:
(1) A repository lock was not obtained before an update

(2) A lock was requested and denied due to a timeout condition.
Response: (1) Make sure you have obtained the lock by using the pub.storage:lock service before performing
other operations.
(2) Consider increasing the value (in milliseconds) for the "waitLength" parameter. This will cause the
Integration Server to wait for this entry to become available if it is already locked by another thread.
ISS.0086.9138E Not allowed to activate package "<packageName>".

Cause: An attempt was made to activate the WmRoot package by using the pub.packages:*Package built-in
service. You cannot activate the WmRoot package this way. This package contains important administrative
services used by the Integration Server and can only be activated by webMethods installation, maintenance, or
administrative functions.
Response: Do not use the pub.packages:*Package built-in service to activate the WmRoot package.
ISS.0086.9140E Not allowed to enable package "<packageName>".

Cause: An attempt was made to enable the WmRoot package by using the pub.packages:*Package built-in
service. You cannot enable the WmRoot package this way. This package contains important administrative
services used by the Integration Server and can only be enabled by webMethods installation, maintenance, or
Response: Do not use the pub.packages:*Package built-in service to enable the WmRoot package.
ISS.0086.9141E Not allowed to disable package "<packageName>".

Cause: An attempt was made to disable the WmRoot package by using the pub.packages:*Package built-in
service. You cannot disable the WmRoot package this way. This package contains important administrative
services used by the Integration Server and can only be disabled by webMethods installation, maintenance, or
Response: Do not use the pub.packages:*Package built-in service to disable the WmRoot package.

ISS.0086.9142E Not allowed to recover package "<packageName>".

Cause: An attempt was made to recover the WmRoot package by using the pub.packages:*Package built-in
service. You cannot recover the WmRoot package this way. This package contains important administrative
services used by the Integration Server and can only be recovered by webMethods installation, maintenance,
or administrative functions.
Response: Do not use the pub.packages:*Package built-in service to recover the WmRoot package.
ISS.0086.9144U Exception occurred while checking target package name.

Cause: The pub.packages:installPackage service encountered an I/O exception while trying to install a package.
One possible reason is that the package zip file was corrupted and the server could not read the package
manifest information.
Response: Examine the package zip file to see if it has been corrupted. If it has, contact the package publisher to
request a new package zip file.
ISS.0086.9145E Invalid or non-existing package name <pkgName> provided.

Cause: A pub.packages service failed to execute because the package name supplied does not exist in the
Integration Server.
Response: Examine the service input and make sure the "package" parameter specifies a valid package that
exists in the Integration Server.
ISS.0086.9146E A required parameter <localName> was not supplied.

Cause: The pub.universalName:find service failed to execute because the required "localName" parameter was
not supplied.
Response: Examine the service input and make sure it specifies the correct value for the "localName"
parameter.
ISS.0086.9152E Not allowed to reload package "<packageName>".

Cause: An attempt was made to reload the WmRoot package by using the pub.packages:*Package built-in
service. You cannot reload the WmRoot package this way. This package contains important administrative
services used by the Integration Server and can only be reloaded by webMethods installation, maintenance, or
Response: Do not use the pub.packages:*Package built-in service to reload the WmRoot package.

ISS (IS Server)
ISS.0086.9153U Unknown package name <pkgName> provided.

Cause: The pub.packages:recoverPackage service failed to execute because the name of the package to recover,
supplied by the "package" parameter, does not exist in the Integration Server's salvage directory.
Response: Examine the service input and make sure the "package" parameter correctly specifies the name of the
package to be recovered.
ISS.0086.9157E Not able to convert headerLines to byte array.

Cause: The pub.mime:mergeHeaderAndBody service failed to execute because the "headerLines" parameter
contained an invalid value.
Response: Examine the service input and make sure it specifies the correct value for the "headerLines"
parameter. You can use the IData object containing the message headers that is returned by the pub.client:http
service.
ISS.0086.9158U Missing required parameter: 'headerLines'.

Cause: The pub.mime:mergeHeaderAndBody service failed to execute because the required "headerLines"
Response: Examine the service input and make sure that it specifies the correct value for the "headerLines"
parameter. You can use the IData object containing the message headers that is returned by pub.client:http
service.
ISS.0086.9159E Invalid input. 'headerLines' must be an instance of Idata.

Cause: During execution of the pub.mime:mergeHeaderAndBody service, the Integration Server detected that
invalid input was provided for the "headLines" parameter. Input for this parameter must be of type IData.
Response: Examine the service input and ensure that the correct input type is provided.
ISS.0086.9160U Missing required paramater: 'body'.

Cause: The pub.mime:mergeHeaderAndBody service failed to execute because the required "body" parameter
was not supplied.
Response: Examine the service input and make sure it specifies the correct value for the "body" parameter. You
can pass the IData object containing the body of the message that was returned by pub.client:http service.
ISS.0086.9161E Invalid input. 'bytes' must be an instance of byte array.

invalid input was provided for the "body/bytes" parameter. Input for this parameter must be of type byte[].
Response: Examine the service input and ensure that the correct input type is provided.

ISS.0086.9162E Invalid input. 'stream' must be an instance of InputStream.

invalid input was provided for the "body" or "stream" parameter. These parameters must be of type
InputStream.
Response: Examine the service input and ensure that the "body" or "stream" parameter is of type InputStream.
ISS.0086.9163E Invalid input. 'body' must be an instance of Idata.

an invalid "body" parameter was provided. The "body" parameter must be of type IData.
Response: Examine the service input and ensure that the "body" parameter is of type Idata.
ISS.0086.9164E Error reading inputstream: 'stream'.

Cause: The "pub.mime:mergeHeaderAndBody" service failed to execute because an IOException occurred
while reading the input body stream.
Response: Contact webMethods Customer Care
ISS.0086.9165E Both 'bytes' and 'stream' cannot be absent.

Cause: The "pub.mime:mergeHeaderAndBody" service failed to execute because the Integration Server could
not obtain the value for the "body" parameter because nothing was specified for the "bytes" or "stream" keys in
the IData object.
Response: Examine the service input and make sure the IData object contains the body of the message in one of
the following keys: "bytes" or "stream". One of them must be supplied.
ISS.0086.9168E Could not retrieve raw data from implicitly signed message
Cause: The pub.security.pkcs7:verify service failed to execute because an input/output exception occurred
while retrieving the raw data from the signed message. This indicates an internal error.
ISS.0086.9179E Missing required parameter: <paramName>.

Cause: A pub.math:*Objects service failed to execute because one or both of the required "num1" and "num2"
parameters were missing.
Response: Examine the service input and make sure that both the "num1" and "num2" parameters are specified.
ISS.0086.9180E Invalid value for parameter: <paramName>. <paramName> is not a recognized numeric type.
Cause: A pub.math:*Objects service failed to execute because the "num1" or "num2" parameter that was
supplied is not an instance of java.lang.Number class.

ISS (IS Server)
The pub.math:*Objects services accept the following sub-classes of java.lang.Number: java.lang.Byte,

java.lang.Double, java.lang.Float, java.lang.Integer, java.lang.Long, java.lang.Short, java.lang.BigDecimal,
java.lang.BigInteger.
Response: Examine the service input and make sure the "num1" and "num2" parameters specify the correct
subclasses.
ISS.0086.9182U Missing required value: {document}.

Cause: The pub.document:documentToDocumentList service failed to execute because the required
"document" parameter was not supplied.
Response: Examine the service input and make sure it specifies the correct value for the "document" parameter.
ISS.0086.9183U Missing one or more required values: {documentList,name}.

Cause: The pub.document:documentListToDocument service failed to execute because the required
"documentList" and "name" parameters were not supplied.
Response: Examine the service input and make sure it specifies the correct values for the "documentList" and
"name" parameters. Neither of them should be empty.
ISS.0086.9188E Invalid Locale: <localeName>.

Cause: A "pub.date" service failed to execute because an invalid locale was supplied.
Response: Examine the service input make sure it specifies a valid value for the "locale" parameter. For
example, to specify the French language, the locale would be "fr". You can find a full list of ISO-639 language
codes at http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt.
ISS.0086.9189E Invalid date pattern or input.

Cause: The pub.date:dateTimeFormat service failed to execute because the "currentPattern," "newPattern," or
"inString" parameter contained an invalid value.
Response: Examine the service input and make sure it specifies valid values for the required parameters. For
information about valid pattern-string syntax, see "Date Folder" section of the "webMethods Integration Server
Built-In Services Reference".
ISS.0086.9194U Not logged in!

Cause: A pub.client.ftp service failed to execute because the user under which the service was to run was not
logged in when the service tried to execute.
Response: Be sure invoke the pub.client.ftp:login service to initiate an FTP session before you execute other FTP
operations.

ISS.0086.9197U Invalid transfer mode.

Cause: A pub.client.ftp service failed to execute because an invalid FTP file transfer mode was supplied in the
"transfermode" parameter.
Response: Examine the service input and make sure it specifies the correct value for "transfermode" parameter.
The FTP file transfer mode must be either "ascii" or "binary."
ISS.0086.9198U Missing content or filename.

Cause: The pub.client.ftp:put or pub.client.ftp:append service failed to execute because the data or file to be
transferred was not supplied.
Response: Examine the service input and make sure the "content" or "localfile" parameter specifies the correct
value. Either the "content" parameter or the "localfile" parameter must be specified.
ISS.0086.9199U <dirName> is not a valid directory!

Cause: The pub.client.ftp:mput or pub.client.ftp:mget service failed to execute because the "localdir" parameter
specified an invalid directory name or a directory that is not in the local file system.
Response: Examine the service input and make sure the "localdir" parameter specifies a directory in the local
file system.
ISS.0086.9200E Private key data must be in a byte array (byte[]).

Cause: A user-written service tried to supply private key data to the pub.security:setKeyAndChainFromBytes
service, but the data was not provided in byte array format.
Response: Update your program so that it supplies the private key data in byte array format.
ISS.0086.9201E Certificate chain data must be an array of byte array (byte[][]).

Cause: A user-written program passed certificate chain data to the pub.security:setKeyAndChainFromBytes
service in the wrong format.
Response: Update your program so that it supplies the certificate chain data in byte array(byte[][]) format.
ISS.0086.9202E Certificate at position <index> in array is not in any recognizable format

Cause: A user-written program passed an array of certificates to the pub.security:setKeyAndChainFromBytes
service, but the certificate in the indicated position is not a valid certificate.
Response: Provide a valid certificate in the indicated position in the certificate array.

ISS (IS Server)
ISS.0086.9203E Not a valid long number.

Cause: A user-written service tried to supply the largeFileThreshold input parameter to the pub.client.ftp:get
service but failed because the number provided is not a valid long number.
Response: Update your program to provide a valid long number for the largeFileThreshold input parameter.
ISS.0086.9210E User specified encoding `<encoding>` does not match content encoding received from remote server.
Cause: A client program used a pub.client.ftp service to connect to a remote FTP(S) server, but the encoding
provided by the client program is not supported.
Response: Update the client program so that it supplies a valid encoding value to the pub.client.ftp service.
ISS.0094.0001U Repository Exception: <errorMessage>.

Cause: During initialization, the could not initialize the Repository Manager. The most likely reason is that the
repository4.cnf file is corrupted.
Response: Check the directory that contains the repository files. By default, they are located at
<IntegrationServer_dir>\WmRepository4\ directory. Try renaming the repository4.cnf file manually (to
something like "damagedrepository4.cnf") or deleting it, then try re-initializing the Integration Server. If that
does not work, contact webMethods Customer Care.
ISS.0094.0003U RepositoryManager detected damaged data files : <errorMessage>.

Cause: During initialization, the detected that some of the data files that make up the repository were
corrupted. In a recovery attempt, the Integration Server tried to open the files, but was unable to.
Response: Check the directory that contains the data files. By default, the data files are located at
<IntegrationServer_dir>\WmRepository4\ directory. You can also look in the repository4.cnf file for the
location of the data files. Try manually renaming the files (to something like "damagedFSData00000000") or
deleting them, then try re-initializing the Integration Server. If that does not work, contact webMethods
Customer Care.
ISS.0094.0004U RepositoryManager Exception renaming damaged data files : <errorMessage>.

Cause: During initialization, the detected that some of the data files that make up the repository were
corrupted. In an attempt to correct the problem, the tried to rename the damaged files before creating new
ones, but the encountered an exception when trying to rename the damaged files.
location of the data files. Try manually renaming the files (to something like "damagedFSData00000000") or
deleting them, then try re-initializing the Integration Server. If that does not work, contact webMethods
Customer Care.

ISS.0094.0006U RepositoryManager Exception creating new data files : <errorMessage>.

Cause: During initialization, the Integration Server detected that some of the data files that make up the
repository were corrupted. In an attempt to correct the problem, the Integration Server renamed the damaged
files and tried to create new ones, but the Integration Server encountered an exception when trying to create
new files.
Possible reasons for the problem are that the file system does not have enough space for the data files or that
the Integration Server does not have write access to the directory that contains the files.
location of the data files. Make sure the file system has space for the files and that the Integration Server has
write access to the directory.
ISS.0095.0001U AuditLogManager Initialization Exception: <className>:<errorMessage>.

Cause: The Integration Server encountered an internal error while initializing the Audit Log Manager.
ISS.0095.0003U AuditLogManager Runtime Exception: <className>:<message> processing log entry <ev ent>.
Cause: The Integration Server encountered an internal error with the Audit subsystem.
ISS.0095.0004U AuditLogManager Runtime Rejected entry <event>.

Cause: The Integration Server encountered an internal error with the Audit subsystem.
ISS.0095.0006U AuditLogManager: Exception on start audit <serviceName>:<errorMessage>.

Cause: The Integration Server Audit Log Manager encountered an internal error.
ISS.0095.0007U AuditLogManager: Exception on end audit <serviceName>:<errorMessage>.

ISS.0095.0008E AuditLogManager: Exception on error audit <serviceName>:<errorMessage>.


ISS (IS Server)
ISS.0095.0009E AuditLogManager: Audit runtime interface object cannot be initialized <errorMessage>.

ISS.0097.0004E Failed to lock Repository entry <repositoryKey>

Cause: The Integration Server encountered an internal error when trying to lock the repository.
Response: If the error continues, contact webMethods Customer Care.
ISS.0098.0003U Exception occured while decoding Broker Document <brokerDocumentName> : <exceptionMessage>.

Cause: The Integration Server failed to decode the document from the Broker. The document may be corrupt.
Response: Check the publisher of the document. Consider redelivering the document from the Broker.
ISS.0098.0010U Exception initializing Dispatcher configuration from file: <errorMessage>.

Cause: The Integration Server encountered the indicated exception while trying to initialize the Dispatcher.
This is a serious internal error.
ISS.0098.0023E Document Router for Consumer Queue:<messageStoreID> encountered error: <exception>.

Cause: The Integration Server encountered an error while routing a document to a Broker.
Response: The action to take depends on the exception that occurred.
ISS.0098.0024U No Trigger available for incoming Document <documentTypeName>. Rejecting Document.

Cause: The Integration Server failed to deliver the incoming document to the triggers because no trigger
subscribed to the document. The intended trigger may be disabled or deleted.
Response: In webMethods Developer, examine the triggers in the application. If an intended trigger for the
document is disabled, enable it and ask the publisher to re-publish or deliver the document.
ISS.0098.0029U Exception while doing Request Reply: <errorMessage>.

Cause: The Integration Server encountered an internal error while executing a request reply.

ISS.0098.0030E <messageStoreId || consumerName> received duplicate document(s). Error <exception>.

Cause: The Integration Server determined that it received duplicate documents from a publishing source, that
is, another Integration Server. In some cases, the Integration Server did not really receive duplicates. For
example, two documents might use the same tracking ID but have different content.
Response: If you determine that the Integration Server did receive duplicate messages, check the publishing
source to learn the source of the problem. If the Integration Server did not receive a duplicate document, try
resubmitting the document from the webMethods Monitor.
ISS.0098.0031E Consumer:<consumerName> unable to persist Document(s) to Document Store. Error: <exception>.

Cause: The Integration Server failed to write a document to the transient store. A likely cause is that the
Integration Server JVM has run out of memory.
Response: Try increasing the heap size. The heap size indicates how much memory is allotted for server
processes. To edit the heap size, shut down the server, and open the server.bat or server.sh using a text editor.
Set JAVA_MIN_MEM to the minimum heap size and set JAVA_MAX_MEM to the maximum heap size. By
default, the minimum heap size is 128MB and the maximum heap is 256MB. Your capacity planning and
performance analysis should indicate whether you need to set higher maximum and minimum heap size
values.
ISS.0098.0033E Error while shutting down Dispatcher: <errorMessage>.

ISS.0098.0036U <threadName> encountered Transport Exception: <errorMessage>.

Cause: The Integration Server failed to publish the document because of one of the following:
1) The Broker is temporarily unavailable.
2) The client does not have the canPublish permission for its associate Broker document.
3) The document being published does not conform to the Broker document on the Broker. This may be
because the document was not synchronized with the one on the Broker.
4) An internal error occurred.
1) Check the Broker status. If the Broker or network connection is temporarily down, wait until they are up to
re-publish the document.
2) In the Broker Administrator, check the publication permissions of the client group to which the trigger client
belongs. Make sure that the client is allowed to publish the document.
3) In webMethods Developer, synchronize the document and make sure that the document being published
matches its associate Broker document type.
4) If the previous actions fail to correct the problem, contact webMethods Customer Care.

ISS (IS Server)
ISS.0098.0038E <clientID> handling invalid Document. Exception: <exception>.

Cause: The Integration Server encountered an error while processing a document. Specifically, the document
does not have a corresponding publishable Doc Type on the Integration Server or the publishable Doc Type
does not have a matching schema.
Response: Make sure that the appropriate Doc Types and Schemas for the document exist on the Integration
Server.
ISS.0098.0044U Exception while interacting with the Document Store name:<storeName> Problem:<exception>
ISS.0098.0045U Unrecoverable Exception while initializing the Dispatcher: <errorMessage>.

Cause: The Integration Server encountered the indicated exception while trying to initialize the Dispatcher.
This is a serious internal error.
ISS.0098.0048U Unable to remove subscription for Publishable Document <documentTypeName> from

transport:<brokerClientID>. \n If connected, please remove subscription from broker manually.
Cause: The Integration Server failed to remove the subscription before unregistering the trigger. The Broker
may be unavailable.
Response: In the Broker Administrator, check the status of the Broker and the network connection. If one or
both are down, then you will need to manually remove the stale subscriptions for the trigger when they are
back up.
ISS.0098.0049U Exception:<errorMessage> while executing trigger. <action> Document for TriggerStore:<storeName>.

Cause: The Integration Server failed to execute the trigger. This indicates an internal error.
ISS.0098.0055U Exception during attempt to register Trigger: <errorMessage>.

Cause: The Integration Server failed to register the trigger. This indicates an internal error.

ISS.0098.0056U Unable to acknowledge Document <documentTypeName> to transport for Trigger <triggerName>.

Exception:<errorMessage>.
Cause: The Integration Server encountered an internal error while acknowledging the document to transport
for the trigger.
ISS.0098.0057U Unable to delete Document Store for Trigger:<triggerName>. Exception:<errorMessage>.

Cause: The Integration Server encountered an internal error while deleting the document store associated with
the trigger.
ISS.0098.0059U Exception while shutting down the Document Stores:<errorMessage>.

Cause: The Integration Server encountered a serious internal error while shutting down.
ISS.0098.0060U Exception while saving Dispatcher configuration :<errorMessage>.

Cause: The Integration Server encountered an exception while trying to save Dispatcher configuration
information to the dispatch.cnf file in the <IntegrationServer_dir>/config directory.
Response: If the dispatch.cnf file is set to read-only, change it to read/write. If the file is not set to read-only, this
error indicates a serious internal error and you should contact webMethods Customer Care.
ISS.0098.0073U ControlledPublishOnSuccess max exceeded while processing <documentTypeName>.

Cause: The Integration Server failed to publish a document because the maximum concurrent publish-on-
success value was exceeded.
1) On the Integration Server, increase the "concurrent publish on success" setting by editing the
"watt.server.control.maxPublishOnSuccess" property.
2) Decrease the number of concurrent publish operations in the service.
ISS.0098.0075E Insufficient memory while decoding event:<documentName> for <clientID>.

Cause: The Integration Server does not have sufficient memory to decode the documents being retrieved from
the Broker. The Integration Server will attempt to decode this event one more time.
Response: Check the size of the documents sent by the Broker and consider increasing the heap size of the
Integration Server's JVM. You can view the heap size by editing the <IntegrationServer_dir>\bin\server.bat
file (on Windows systems) or <IntegrationServer_dir>\bin\server.sh file (on Unix systems).

ISS (IS Server)
ISS.0098.0076U Unable to decode events for <documentTypeName>. Please check JVM Heap size and/or size of Documents
on the Broker.
Cause: The Integration Server does not have sufficient memory to decode the document from the Broker.
Response: Check the size of the document sent by the Broker and consider increasing the heap size of the
Integration Server's Java Virtual Machine. You can view the heap size by editing the
<IntegrationServer_dir>\bin\server.bat file (on Windows systems) or <IntegrationServer_dir>\bin\server.sh
file (on Unix systems).
ISS.0098.0077E Dispatcher out of memory. Retrying operation.

Cause: The Integration Server does not have sufficient memory to continue its document publishing
operations. The Integration Server will attempt to process this message again.
Response: Consider increasing the heap size of the Integration Server's Java Virtual Machine. You can view the
heap size by editing the <IntegrationServer_dir>\bin\server.bat file (on Windows systems) or
<IntegrationServer_dir>\bin\server.sh file (on Unix systems).
ISS.0098.0078E Dispatcher out of memory. Operation failed. Check error log.

Cause: The Integration Server does not have sufficient memory to continue its document publishing
operations. The Integration Server has exceeded its retry count, and an exception will be thrown.
Response: Consider increasing the heap size of the Integration Server's Java Virtual Machine. You can view the
heap size by editing the <IntegrationServer_dir>\bin\server.bat file (on Windows systems) or
<IntegrationServer_dir>\bin\server.sh file (on Unix systems).
ISS.0098.0079E Dispatcher out of memory. Retry succeeded.

Cause: Integration Server successfully retried a publishing operation after an OutOfMemory error prevented
the operation from working the first time.
Response: If the Integration Server continues to issue this message, check the JVM Heap size and/or size of
Documents on the Broker.
Note: The Trigger configuration (possibly the acknowledgment queue size) may need to be adjusted.
ISS.0098.0080U Insufficient memory while peristing messages for Trigger: <triggerName>.

Cause: The Integration Server does not have sufficient memory to persist the documents to the document store
for the trigger.
Response: Check the size of the documents being persisted and consider increasing the heap size of the

ISS.0098.0081U Insufficient memory while peristing message: <documentTypeName> for Trigger: <triggerName>.
Cause: The Integration Server does not have sufficient memory to persist a single document to the document
store for the trigger.
Response: Check the size of the document being persisted and consider increasing the heap size of the
ISS.0098.0082U Unable to persist Document: <documentTYpeName> to Document Store: <storeName>. Exception:

<errorMessage>.
Cause: The Integration Server failed to persist the document to the document store. This indicates a serious
internal error.
ISS.0098.0083U Unable to acknowledge Document: <msgType> for Trigger Store: <storeID>. Insufficient memory.
Cause: The Integration Server does not have sufficient memory to acknowledge the document to the document
store.
Response: Check the size of the document being persisted and consider increasing the heap size of the
ISS.0098.0084U Exception:<errorMessage> during Trigger dispatching.

Cause: The Integration Server encountered an internal error while which processing a document destined for
an individual trigger.
ISS.0098.0085U Unable to remove all subscriptions for transport:<brokerClientID> while unregistering trigger. \n If
connected, please remove subscription from Broker manually.
Cause: The Integration Server failed to remove all stale subscriptions before unregistering the trigger. The
Broker may be unavailable.
back up.

ISS (IS Server)
ISS.0098.0086U Unable to remove all subscriptions for transport:<brokerClientID> before registering trigger. \n If connected,
please remove stale subscriptions from Broker manually.
Cause: The Integration Server failed to remove all stale subscriptions before registering the trigger. The Broker
may be unavailable.
back up.
ISS.0098.0089U Transaction size (no of documents * size of documents) is too large for Document Store: <storeName>.
Please reduce capacity of Trigger and /or increase initial size of Document Stores.
Cause: The Integration Server failed to persist documents because the document store did not contain enough
space. Documents received from the Broker are persisted in the triggers' persistent stores.
Response: In the Integration Server Administrator, click Settings>Resources>Document Stores. On this page,
consider increasing the initial size of the document store. Also, consider reducing the number of triggers that
subscribe to the document.
ISS.0098.0090U Size of Document: <documentTypeName> for Document Store: <storeName> is too large. Server is unable to
persist. Audit logging the document.
Cause: The Integration Server failed to persist a document because the document store did not contain enough
space.
Response: In the Integration Server Administrator, click Settings>Resources>Document Stores. On this page,
consider increasing the initial size of the document store.
ISS.0098.0096I Integration Server is now connected to a Broker that tracks document redelivery counts. Restart the
Integration Server to make use of redelivery counts in duplicate detection.
Cause: The Integration Server has connected to a version of the Broker that supports redelivery count.
Previously it was connected to a Broker that does not support this feature.
Response: Restart the Integration Server so that it can take advantage of the redelivery count feature supported
by the Broker.
ISS.0098.0103S <nameOfDocumentStore> not initialized. Adjust document store settings and restart server.
Cause: The Integration Server was unable to create the Document Store on disk. The Document Store is
essential for Integration Server functioning, therefore startup terminates.
Response: Check to see if there is enough disk space on the drive where the Document Store is being created
(usually under <IS_SERVER_ROOT>\DocumentStore directory). If there is sufficient disk space, then check to
see if the dispatch.cnf file under <IS_SERVER_ROOT>\config directory is corrupted. If the problem persists
despite a re-start, contact webMethods Customer Care.

ISS.0098.0104I Integration Server is now connected to a Broker that does not track document redelivery counts. Restart the
Integration Server so that duplicate detection does not expect document redelivery counts.
Cause: The Integration Server has connected to a version of the Broker that does not support the redelivery
count. Previously it was connected to a Broker that does support this feature.
Response: Restart the Integration Server so that its duplicate detection mechanism does not expect redelivery
counts to be present in documents delivered by the Broker.
ISS.0098.0105E Unable to fully build comparable trigger: <triggerName>

Cause: During Cluster Synchronization, the Integration Server was unable to compare trigger nodes across all
the nodes in the cluster. The most likely cause is that one or more triggers are not completely configured.
Cluster Synchronization makes sure that changes made to a trigger's configuration on one Integration Server
are propagated to other servers in the cluster. If an Integration Server is configured for Cluster
Response: From webMethods Developer, check the trigger configuration. After correcting the problem, retry
the task you were performing when the error occurred.
ISS.0098.0107E Error occurred during cluster invoke: Alias = <remoteAliasName>; Service = <serviceBeingInvoked>;
Exception = <exceptionMessage>.
Cause: During Cluster Synchronization, the Integration Server threw an exception while invoking a service on
a remote node in the cluster.
Cluster Synchronization makes sure that changes made to a trigger's configuration on one Integration Server
are propagated to other servers in the cluster. If an Integration Server is configured for Cluster
Response: The action you take depends on the exception issued. Look at the exceptionMessage for specific
information.
ISS.0098.9002U Required property missing for creating <Broker> transport: <brokerHost>.

Cause: The Integration Server could not read properties from the <IntegrationServer_dir>\config\dispatch.cnf
file. The file may be corrupt.
Response: Examine the dispatch.cnf file to make sure that it is not corrupt and that the "clientGroupName" and
"brokerHost" fields exist. If the file is corrupt, rename it and restart the Integration Server. After you do this,
you can re-configure the Broker Settings using the Integration Server Administrator.

ISS (IS Server)
ISS.0098.9006U No matching Document Type exists for <documentTypeName>.

Cause: A pub.publish service issued an error because the document specified in the "documentTypeName"
parameter does not exist on the Integration Server.
Response: Examine the input for the documentTypeName parameter. Make sure that the fully-qualified name
of the document being published or delivered is specified. Remember that document names are case-sensitive.
ISS.0098.9007E Data does not conform to the Publishable Document Type <documentTypeName> errors: <errorMessage>.
Cause: A pub.publish service issued an error because the IData input for the "document" parameter does not
conform to the document type specified in the "documentTypeName" parameter.
Response: Examine the validation error message and the IData object passed to the "document" parameter.
Make sure that it conforms to the document type specified in the "documentTypeName" parameter.
ISS.0098.9008U No registered Transport for the given id: <brokerClientID>

Cause: The Integration Server failed to create a subscription to the publishable document type specified in a
trigger. The transport information does not exist, which indicates an internal error.
ISS.0098.9010E No waiting thread for Document Id: <uuid>. Requestor might have timed out.
Cause: The Integration Server encountered an internal error while publishing the document and waiting for a
reply.
ISS.0098.9011U <documentTypeName> is not a Publishable Document Type.

Cause: A pub.publish service issued an error because the document specified in the "documentTypeName"
parameter was not publishable.
Response: In webMethods Developer, examine the publication properties of the document to be published or
delivered. Change the document's state to "Document Type is publishable to the Broker."
ISS.0098.9013U Dispatcher is not initialized.

Cause: The Integration Server was not able to publish, deliver, or reply to a document because the dispatcher
that is responsible for performing these operations was not initialized.
Response: Log on to the Integration Server Administrator and make sure that you have followed the steps in
Chapter 5 of "Building Integration Solutions Using Publication" to setup the configuration correctly.

ISS.0098.9014U BrokerException: <errorMessage>.

Cause: The Integration Server was unable to publish or retrieve documents from the Broker because the
operation failed on the Broker.
Response: Examine the error message provided by the Broker. Refer to the Broker Java Client API
documentation for a detailed description of the error.
ISS.0098.9016U Broker Transport unable to subscribe to Publishable Document Type:<pubDocumentTypeName>

BrokerEvent Type:<brokerEventTypeName> .
Cause: The Integration Server failed to create a subscription to the publishable document type specified in a
trigger. The client is not allowed to subscribe to its associate Broker document in the Broker.
Response: In the Broker Administrator, check the subscription permissions of the client group to which the
trigger belongs. Make sure that the client is allowed to subscribe its associate Broker document.
ISS.0098.9018E Unrecoverable Error while initializing Dispatcher: <errorMessage>.

ISS.0098.9019U Request timed out while waiting for reply.

Cause: The Integration Server encountered an internal error while publishing or delivering the document and
waiting for a reply.
ISS.0098.9021U Received incorrect document as Reply. Expecting <documentTypeName> and received

<documentTypeName>.
Cause: The Integration Server failed to receive the expected reply document while publishing or delivering the
document and waiting for a reply.
Response: Check the subscriber of the publisher document. Make sure that the subscriber delivers a correct
reply document.
ISS.0098.9022E Invalid DispatcherMessage <null>.

Cause: The Integration Server failed to deliver the document to the interested triggers. The document is null,
which indicates an internal error.

ISS (IS Server)
ISS.0098.9023U Transport Factory: <className> not found.

ISS.0098.9024U <BrokerTransportFactory> Unknown Transport Type specified. Unable to create transport.

ISS.0098.9025U <Broker> not configured. <operationName> operation can only be done after a Broker is configured.
Cause: The pub.publish:deliver or pub.publish:deliverAndWait service failed to execute because the
Integration Server is not configured to connect to the Broker. The Integration Server must be connected to a
Broker to use these two services.
Response: Log on to the Server Administrator and follow the steps in the "webMethods Integration Server
Administrator's Guide" to configure the server to connect to a Broker.
ISS.0098.9027U Unknown broker version.

Cause: The Integration Server failed to connect to the Broker because the version of the Broker is not supported.
Response: Do not attempt to set up such an environment. See the "webMethods Installation Guide" for
supported configurations.
ISS.0098.9033E Duplicate condition name <conditionName> in Trigger <triggerName>.

Cause: The Integration Server could not save the condition settings of a trigger because the trigger has
duplicate condition names.
Response: In webMethods Developer, click the Conditions tab for the trigger and make sure that each
condition has a unique name.
ISS.0098.9034E Condition name ''<conditionName>'' - Cannot have duplicate document types in AND join.
Cause: The Integration Server could not save the condition settings of a trigger because a condition has
duplicate document types in an "AND" join.
Response: In webMethods Developer, click the Conditions tab for the trigger and make sure that unique
document types are specified in the "AND" join.

ISS.0098.9035E Cannot specify different filters for document types <docTypeName> within a single trigger.
Cause: The Integration Server could not save the condition settings of a trigger because more than one filter is
specified for a document type in the trigger.
Response: In webMethods Developer, click the Conditions tab for the trigger. If multiple conditions in the
trigger specify the same document type, make sure that the filter applied to the document type is the same for
each condition.
ISS.0098.9036U Unable to ack.

Cause: The Integration Server failed to acknowledge the document to the trigger document store. This
indicates an internal error.
ISS.0098.9050U Unable to publish volatile Document: <msgType>. Broker not connected.

Cause: The Integration Server published a volatile document while the Broker was down. Therefore, a service
exception occurred for the publishing service and the volatile document was lost.
Response: Make sure the broker is up and re-publish the document.
ISS.0098.9051U No activation specified for Join Document:<documentName>.

Cause: The published message cannot be processed in a join because it is missing an activation ID.
Response: The publisher needs to set the activation ID in the document.
The publisher of the message needs to set the activation ID in the document.
ISS.0098.9056U cmd for msgs all not the same or null.

Cause: A flow service mixed the pub.publish:deliver and pub.publish:publish steps when the
delayUntilServiceSuccess parameter is set to "true".
Response: Use separate flow services to deliver and publish a message when the delayUntilServiceSuccess
parameter is set to "true".
ISS.0098.9057U destination for msgs all not the same or null.

Cause: A flow service contains multiple pub.publish:deliver steps when the delayUntilServiceSuccess
parameter is set to "true", but the destination IDs are not identical.
Response: Use separate flow services to deliver a message to different destination IDs when the
delayUntilServiceSuccess parameter is set to "true".

ISS (IS Server)
ISS.0098.9058E publish-on-success is suspended.

Cause: The publish-on-success facility has been programmatically suspended. Therefore, the publish-on-
success operation will not work.
Response: Programmatically unsuspend or restart the Integration Server. Since the suspend API is not used, a
user should not encounter this error.
ISS.0098.9059E max concurrent publish-on-success is exceeded.

Cause: The watt.server.control.maxPublishOnSuccess parameter was exceeded by a publishing flow. The
maxPublishOnSuccess parameter controls the maximum number of documents that the Integration Server
publishes on success at one time.
Response: Decrease the number of documents published by a flow service that uses publish-on-success, or
increase the value of the maxPublishOnSuccess parameter.
ISS.0098.9062U Document store is missing for <identityName>.

Cause: The Integration Server encountered an internal error in the document store.
ISS.0098.9065E Error reply <publishableDocumentName> received. adapterType:<nameOfAdapter/Package>,

errorCategory:<typeOfError>,errorText:<errorMessage>,eventId:<eventID>
Cause: A client, typically an Integration server but possibly a Broker client or Adapter, sent a request document
to an Integration Server, but received an error reply (a document of type pub.publish.notification:error ) in
response. This happens when the service executing the request document on the target server encounters an
error. Instead of sending the expected reply document type, it sends an error document indicating it could not
process the request document correctly.
Response: Check the Error log of the target Integration Server, that is, the Integration Server to which the
request document was sent. If the error occurred when a document was being published to a single subscriber,
you will know which target server issued the error reply. However, if the error occurred during a publish to
multiple Integration Servers, you will have to determine which target server issued the error.
ISS.0098.9066E Missing required parameter: <parameterName>.

Cause: A client tried to invoke a webMethods built-in service, but did not specify a required parameter.
Response: If you are working with the webMethods Server Administrator, enter the missing value in the
required field.
If you are invoking a service that calls the built-in service, refer to the "webMethods Integration Server Built-In
Services Reference" for the syntax of that service.

ISS.0098.9067E Trigger not found for triggerName: <triggerName>.

Cause: The Integration Server tried to suspend or fetch metadata for the indicated trigger, but there is no
trigger with this name enabled in the Integration Server.
Response: From webMethods Developer, check to make sure the trigger name is typed correctly and that the
trigger is enabled.
ISS.0098.9068E Unable to get status for Trigger <triggerName>: No IControlObject found.

Cause: The Integration Server encountered an error while trying to perform an action against a trigger, but the
trigger was not completely configured, and as a result, not fully initialized.
Response: From webMethods Developer, verify that the trigger is properly configured, including specifications
for conditions and document types.
ISS.0098.9069E Unable to get status for Trigger <triggerName>: <exceptionMessage>

Cause: The Integration Server encountered an error while trying to perform an action against a trigger.
- For trigger retrieval, the status indicates whether the trigger is active or suspended.
- For trigger processing, the status indicates whether the trigger is active or suspended and shows the current
threads being used, the current volatile queue size, and the current persisted queue size.
Response: The action you take depends on the exception issued. Look at the exceptionMessage and the server
log for additional details.
ISS.0098.9072E Trigger <triggerName> is locked. Change not permitted.

Cause: A user tried to modify the indicated trigger using the Trigger Management GUI or APIs, but the trigger
node is locked by the Developer.
Response: From webMethods Developer, unlock the trigger node and try again.
ISS.0098.9073E Unable to suspend document <processing | retrieval> for Trigger <triggerName>: No IControlObject found.
Cause: A request to suspend document processing failed. The most likely cause is that the trigger was not
completely configured, and as a result, not fully initialized.
Response: Use webMethods Developer to properly configure the trigger. After correcting the problem, retry
the task you were performing when the error occurred.

ISS (IS Server)
ISS.0098.9074E Unable to suspend document <processing | retrieval> for Trigger "<triggerName>": <exceptionMessage>
Cause: A request to suspend document processing failed due to the indicated exception.
Response: The action you take depends on the exception issued. Look at the exceptionMessage value in the
message for specific information.
ISS.0098.9075E Unable to resume document <retrieval | processing> for Trigger "<triggerName>": No IControlObject found.
Cause: A request to resume document processing failed. The most likely cause is that the trigger was not
completely configured, and as a result, not fully initialized.
Response: Use webMethods Developer to make sure the trigger is properly configured, including
specifications for conditions and document types.
ISS.0098.9076E Unable to resume document <processing | retrieval> for Trigger "<triggerName>": <exceptionMessage>
Cause: A request to resume document processing failed due to an exception.
ISS.0098.9077E Unable to persist the change made to Trigger "<triggerName>": <exceptionMessage>

Cause: A user tried to make a configuration change for a trigger, but the change was not saved to file. As a
result, the change will revert back to its original value after the Integration Server restarts or someone reloads
the package.
ISS.0098.9078E maxExecutionThreads cannot exceed queueCapacity

Cause: The value specified for the number of maximum execution threads exceeds the queue capacity. This is
not permitted because the number of documents the Integration Server can process concurrently
(maxExecutionThreads) cannot exceed the maximum number of documents that can be in the trigger's queue
(queueCapacity).
Response: If you are working with the webMethods Server Administrator, enter appropriate values in these
fields. For information about these fields, see the section "Modifying Trigger Properties" in the "webMethods
If you are invoking a service that calls a built-in service, refer to the "webMethods Integration Server Built-In
Services Reference" for information about the service syntax and field values.

ISS.0098.9079E queueRefillLevel cannot exceed queueCapacity

Cause: The value specified for the queue refill level exceeds the queue capacity.
The queue refill level is the number of unprocessed documents that must remain in the trigger queue before
the Integration Server retrieves more documents for the queue from the Broker. This level cannot exceed the
maximum number of documents that can be in the trigger's queue (queueCapacity).
Response: If you are working with the webMethods Server Administrator, enter appropriate values in these
fields. For information about these fields, see the section "Modifying Trigger Properties" in the "webMethods
ISS.0098.9080E <parameterName> must be a positive number.

Cause: The value specified for the indicated parameter was zero or a negative number. This value must be
positive number.
Response: If you are working with the webMethods Server Administrator, enter a positive number in the
indicated field. For information about this field, see the section "Modifying Trigger Properties" in the
"webMethods Integration Server Administrator's Guide."
ISS.0099.0001U Broker Transport:<brokerClientID> unable to subscribe to Broker Document <brokerDocTypeName>.

Exception <errorMessage>.
Cause: The Integration Server failed to create the subscription for the trigger on the Broker. The Broker may be
unavailable.
Response: In the Broker Administrator, check the status of the Broker and the network connection. If all are
correct, then this is an internal error. Contact webMethods Customer Care.
ISS.0099.0002U Broker Transport:<brokerClientID> unable to unsubscribe to Broker Document <brokerDocTypeName>.

Exception <errorMessage>.
Cause: The Integration Server failed to cancel the subscription for the trigger from the Broker after removing
the trigger from the Integration Server. The Broker may be unavailable.

ISS (IS Server)
ISS.0099.0003U Unable to create Broker Transport <brokerClientID>. Exception <errorMessage>.

Cause: The Integration Server failed to create the Broker transport for the Broker client because the client could
not reconnect to the Broker. The Broker may be temporarily unavailable.
ISS.0099.0005E Creating subscription on Broker without invalid filter: <exception>.

Cause: A trigger contains an invalid filter. The subscription was created on the Broker without the invalid filter.
Response: Change the filter in the trigger to a valid trigger.
ISS.0099.0006U Unable to disconnect Broker Transport. Exception: <errorMessage>.

Cause: The Integration Server failed to disconnect from the Broker during shutdown. This indicates an internal
error.
ISS.0099.0007U BrokerTransport:<brokerClientID> got Exception: <errorMessage>.

ISS.0099.0008U Insufficient memory while retrieving events for BrokerTransport:<clientID>.

Cause: The Integration Server does not have sufficient memory to retrieve even one document from the Broker.
Response: From the Broker, check the size of the document. Consider increasing the heap size of the Integration
Server's JVM. You can view the heap size by editing the <IntegrationServer_dir>\bin\server.bat file (on
Windows systems) or <IntegrationServer_dir>\bin\server.sh file (on Unix systems).
ISS.0099.0009U Unable to retrieve events from the Broker for BrokerTransport:<clientID>. Insufficient JVM memory. Please
check Heap size/ size of Documents on the Broker.
Cause: The Integration Server does not have sufficient memory to retrieve documents from the Broker.
Response: From the Broker, check the size of the documents. Consider increasing the heap size of the
Integration Server's JVM. You can view the heap size by editing the <IntegrationServer_dir>\bin\server.bat
file (on Windows systems) or <IntegrationServer_dir>\bin\server.sh file (on Unix systems).

ISS.0099.0010U Broker Transport:<brokerClientID> failed to unsubscribe to all Broker Documents. Exception

<errorMessage>.
Cause: The Integration Server failed to cancel the subscriptions from the Broker while removing the trigger
from the Integration Server. The Broker may be unavailable.
ISS.0100.0002S Web Container critical error: <tomcatErrorMessage>

Cause: The Integration Server encountered an internal Tomcat failure while trying to process a servlet.
ISS.0100.0003S Web Container critical error: <tomcatErrorMessage>:<parameter>

ISS.0100.0004E Web Container error: <tomcatErrorMessage>

ISS.0100.0005E Web Container error encountered: <errorMessage>:<object>.

Cause: The Apache Tomcat server encountered an error.
Response: Examine the error message provided and check Tomcat references at
http://jakarta.apache.org/tomcat/resources.html to determine the exception that was thrown.
ISS.0100.0013E Cannot call sendRedirect() after the response has been committed
Cause: A servlet or JSP tried to call the HttpServletResponse.sendRedirect() method but could not because the
output has already been committed.
Response: Correct the Servlet or JSP that caused the error.
ISS.0100.0014E Cannot call sendError() after the response has been committed
Cause: A servlet or JSP tried to call the HttpServletResponse.sendError() method but could not because the
output has already been committed.

ISS (IS Server)
ISS.0100.0015E getOutputStream() has already been called for this response

Cause: A servlet or JSP tried to call the ServletResponse.getOutputStream() method but could not because a
Printwriter has already initialized the output.
ISS.0100.0016E getWriter() has already been called for this response

Cause: A servlet or JSP tried to call the ServletResponse.getPrintWriter() method but could not because an
OutputStream had already initialized the output.
ISS.0100.0017E Cannot reset buffer after response has been committed

Cause: A servlet tried to call the ServletResponse setBufferSize() or ServletResponseReset() method but could
not because the output has already been committed.
ISS.0100.0018D The connector has already been initialized

Cause: Tomcat tried to initialize the ISConnector but the connector has already been initialized. This in an
internal error.
ISS.0100.0019E ISConnector.invoke: <stackTrace>

Cause: The Integration Server HTTP stack encountered an error while passing control to the WmTomcat
connector.
ISS.0100.0020S ISConnector.initialize: Unable to retrieve the MBean Registry

Cause: Tomcat tried to initialize the ISConnector but could not due to an internal WmTomcat JMX error.
ISS.0100.0021I ISConnector.initialize: <JMXname> was registered with the MBean Registry

Cause: The ISConnector has initialized successfully.

ISS.0100.0022I ISConnector.pause: <JMXname> was paused

Cause: The ISConnector has successfully paused the indicated JMX component.
ISS.0100.0023I ISConnector.resume: <JMX name> was resumed

Cause: The ISConnector has successfully resumed the indicated JMX component.
ISS.0100.0024D <JMXname> was registered with the MBean server

Cause: The JMX component was successfully registered with the MBean server.
ISS.0100.0025D ISConnector.destroy: <JMXname> was un-registered from the MBean Registry

Cause: The JMX name was successfully unregistered from the MBean server.
ISS.0100.0026I The connector has already been started

Cause: The Integration Server tried to start the WmTomcat package, but it has already been started.
Response: If this message persists and you are having trouble with WmTomcat, contact webMethods Customer
Care.
ISS.0100.0027E Cannot register Mapper <JMXname>:<ApacheRegistryException>

Cause: WmTomcat encountered an error while trying to register its Mapper with the Tomcat JMX registry. As a
result, Tomcat cannot initialize the ISConnector, which is a bridge between the Integration Server HTTP stack
and the Tomcat container. Without the Mapper in the registry, Tomcat cannot map and direct requests.
ISS.0100.0028E ISConnector has not been started

Cause: WmTomcat encountered an error while trying to start the ISConnector, which is a bridge between the
Integration Server HTTP stack and the Tomcat container. This is an internal error.

ISS (IS Server)
ISS.0100.0029E Cannot un-register Mapper <JMXname> : <ApacheRegistryException>

Cause: WmTomcat encountered an error while trying to un-register its Mapper from the Tomcat JMX registry.
As a result, Tomcat cannot stop the ISConnector, which is a bridge between the Integration Server HTTP stack
and the Tomcat container. This is an internal error.
Response: If restarting the Integration Server does not correct the problem, contact webMethods Customer
Care.
ISS.0100.0030E WebContainer.removePackage: <exception>

Cause: The Integration Server tried to process a request to delete a package that contains a Web application but
could not because there was an internal Tomcat error.
ISS.0100.0031E WebContainer.addPackage: <exception >

Cause: The Integration Server tried to process a request to deploy or redeploy a Web application but could not
because there was an internal Tomcat error.
ISS.0100.0032E Invalid URI: <URI >

Cause: WmTomcat tried to process a request but could not because the HTTP request passed it an invalid URI.
The Integration Server logs the HTTP request and returns, but does not invoke anything in Tomcat.
ISS.0100.0033E Cannot create a session after the response has been committed
Cause: A servlet or JSP tried to call the HttpServletRequest.getSession() method but could not because the
response has already been committed.
ISS.0100.0034E HTTP POST exceeds IS maximum buffer size set with watt.net.defaultBufferSize
Cause: An HTTP POST request exceeded the buffer size limit specified by the watt.net.defaultBufferSize
configuration property.
Response: Use the Settings > Extended screen in the Server Administrator to increase the buffer size limit on the
watt.net.defaultBufferSize parameter in the server.cnf file. See the configuration properties appendix of the
"webMethods Integration Server Administrator's Guide" for more information about this property.

ISS.0100.0035E Unable to process HTTP POST parameters <exception>

Cause: WmTomcat could not read the HTTP POST body and parameters of a request. A likely cause is that the
Integration Server buffer is not large enough to accept this request.
ISS.0100.0036E getReader() has already been called for this request

Cause: A servlet or JSP called the ServletRequest.getInputStream() method after it had already called the
ServletRequest.getReader() method. The servlet can call one method or the other, not both.
ISS.0100.0037E getInputStream() has already been called for this request

Cause: A servlet or JSP called the ServletRequest.getReader() method after already calling the
ServletRequest.getInputStream() method. The servlet can call one method or the other, not both.
Response: Correct the Servlet/JSP which caused the error
Correct the Servlet or JSP that caused the error.
ISS.0100.0038E Cannot call setAttribute with a null name

Cause: A servlet or JSP called the ServletRequest.setAttribute() method and passed a null attribute name.
ISS.0100.0040E The RequestStream has already been closed

Cause: A servlet or JSP called the ServletInputStream.close() or ServletInputStream.read() method, but the
InputStream has already been closed.
ISS.0100.0041I Deleted file <fileName>

Cause: WmTomcat unzipped a war file into its corresponding web directory, removed an Integration Server
context/package, and undeployed it from Tomcat.
ISS.0100.0042E Unable to create an IS package for URL <fullyQualifiedURL>

Cause: The WmTomcat hot deployment service could not create an Integration Server package using the war
file that was provided. The most likely cause of the error is a special character in the file name. These
characters are not valid for Integration Server packages.
Response: Check the name of the war file for special characters and rename it if necessary.

ISS (IS Server)
ISS.0100.0043E Unable to activate the IS package <fullyQualifiedURL>

Cause: The WmTomcat hot deployment service was unable to activate an Integration Server package.
Response: Check to see if the package has already been activated.
ISS.0100.0045I Unpacked file <warFileName>

Cause: WmTomcat unzipped a war file into the web directory of the corresponding Integration Server package.
ISS.0100.0046E JSP invoke <ISServiceName> returned Error message: <serviceErrorMessage >

Cause: The Invoke tag of the webM tag library received an error from the indicated service.
Response: Correct the Servlet or JSP that caused the problem.
ISS.0100.9900U The <tagName> action is not enclosed by a <tagName> action.

Cause: The Integration Server was not able to execute a web application because there are syntax errors in the
JSP file.
Response: Examine the error message to determine which tag name caused the exception to be thrown. Then
check the JSP file that contains the tags and look for syntax errors. See the "Web Applications Developer’s
Guide" for the correct usage. After you fix the problem, re-deploy the web application on the Integration
Server.
ISS.0100.9901U The <else> action is not enclosed by a <ifvar> action at <tagName>.

Cause: The Integration Server was not able to execute a web application because there was a syntax error in the
<webm:ifvar> and <webm:else> tags in the JSP file.
Response: Examine the JSP file that contains the <webm:ifvar> and <webm:else> tags. See the "webMethods
Applications Developer's Guide" for the correct usage of these tags. After you fix the problem, re-deploy the
web application on the Integration Server.
ISS.0105.0002E Cannot obtain a connection to repository: <errorMessage>.

Cause: The Integration Server was not able to perform synchronizations using key cross-referencing and echo
suppression because it could not obtain a connection to the repository where cross-reference keys are stored.
Response: From the Server Administrator, look at the Settings>Repository page and check the settings. Also
verify that the database is up and running.

ISS.0105.0003E Cannot get canonicalKey: <errorMessage>.

Cause: The pub.synchronization.xref:getCanonicalKey service failed to execute because an exception was
thrown when the Integration Server tried to retrieve the corresponding canonical key for the specified native
ID from the repository.
Response: Examine the error stack trace provided to determine which exception was thrown. If it was a
repository exception, check the "webMethods Integration Server Clustering Guide" and make sure you have
configured the Repository correctly. Also verify that you have provided correct input for the "appID",
"nativeID", and "objectID" parameters. If you cannot find the cause for the problem, contact webMethods
Customer Care.
ISS.0105.0004E Cannot insert a duplicated record, appId='<appId>', nativeId='<nativeId>', canonicalKey='<canonicalKey>',

objId='<objId>'.
service failed to execute because a RepositoryNoLockException was thrown when the Integration Server tried
to insert or create the cross-reference record in the repository.
Response: Use the Settings>Repository>Edit page of the Server Administrator to examine the Maximum Lock
Wait setting for the Repository. Consider increasing this value to prevent a timeout condition when the
application using the Repository server requests an entry lock. If the problem persists, contact webMethods
Customer Care.
ISS.0105.0005E Cannot insert into database this record, appId='<appID>', nativeId='<nativeId>',

canonicalKey='<canonicalKey>', objId='<objId>', error: <errorMessage>
service failed to execute because an exception was thrown when the Integration Server tried to insert or create
the cross-reference record in the repository.
Response: Examine the error stack trace to determine which exception was thrown. If it was a SQLException,
check the "webMethods Server Administrator's Guide" to make sure you have set up your JDBC Pool
configurations correctly. If it was a RepositoryException, check your "webMethods Integration Server
Clustering Guide" to make sure you have configured your Repository correctly. If you cannot determine the
cause of the problem, contact webMethods Customer Care.
ISS.0105.0006E Cannot close latch: <errorMessage>.

Cause: The "pub.synchronization.latch:closeLatch" service failed to execute because an exception was thrown
when the Integration Server tried to close the latch for a given application ID, canonical Key, and object ID.
check the "webMethods Server Administrator Guide" to make sure you have set up your JDBC Pool
Clustering Guide" to make sure you have set up your Repository settings correctly. If you cannot determine
the cause of the problem, contact webMethods Customer Care.

ISS (IS Server)
ISS.0105.0007E Cannot open latch: <errorMessage>.

Cause: The "pub.synchronization.latch:closeLatch" service failed to execute because an exception was thrown
when the Integration Server tried to open the latch for a given application ID, canonical Key, and object ID.
correctly. If it was a RepositoryException, check your "webMethods Integration Server Clustering Guide" to
make sure you have configured your Repository correctly. If you cannot determine the cause of the problem,
ISS.0105.0008E Cannot get nativeId: <errorMessage>.

Cause: The "pub.synchronization.xref:getNativeId" service failed to execute because an exception was thrown
when the Integration Server tried to retrieve the native ID for a given canonical key, application ID, and object
ID.
ISS.0105.0009E Cannot obtain a JDBC connection: <errorMessage>.

Cause: The Integration Server was not able to obtain a connection to the JDBC database where cross-reference
keys and echo suppression status are stored. A likely cause is that the pool alias for this database was specified
incorrectly on the Settings>JDBC Pools page of the Server Administrator.
for the Xref and make sure it specifies the correct Database URL, User Id, Password, and Database driver.
Then, restart the Integration Server.
ISS.0105.0010E No JDBC connection available.

Cause: The Integration Server was not able to obtain a connection to the JDBC database where the cross-
reference keys and echo suppression status are stored. A likely cause is that no JDBC pool connections are
available.
for the Xref and consider increasing the number of connections. Then, restart the Integration Server.
ISS.0105.0011E Release JDBC connection error: <errorMessage>.

Cause: The Integration Server tried to perform a database operation, but the "pub.synchronization*" service
failed to release its connection to the database. This indicates an internal error.

ISS.0105.0012E Get preparedStatement error: <errorMessage>.

Cause: While trying to perform a database operation, a "pub.synchronization*" service encountered an
SQLException.
Response: Examine the error stack trace to determine which SQL exception was thrown. Make sure you
followed the instructions in the "webMethods Integration Server Administrator's Guide" and setup the
Database correctly. If you cannot determine the cause of the error, contact the database vendor.
ISS.0105.0013E Check isLatchClosed error: <errorMessage>.

Cause: The pub.synchronization.latch:isLatchClosed service threw an exception when it tried to check the latch
status for a given canonical key, application ID, and object ID.
check the "webMethods Integration Server Administrator's Guide" to make sure you have set up your JDBC
Pool correctly. If it was a RepositoryException, check your "webMethods Integration Server Clustering Guide"
to make sure you have set up your Repository settings correctly. If you cannot determine the cause of the
problem, contact webMethods Customer Care.
ISS.0105.0014E Drop all records with objId='<objectId>', error: <errorMessage>.

Cause: The "pub.synchronization.xref:deleteByObjectId" service threw an exception when it tried to remove all
cross-reference records associated with a particular process or synchronization.
ISS.0105.0024E Delete xref record: appId='<appId>', canonicalKey='<canonicalKey>', objId='<onjId>', error: <errorMessage>.

Cause: The pub.synchronization.xref:deleteXReference service threw an exception when it tried to remove all
cross-reference records associated with a particular process or synchronization.
check the "webMethods Integration Server Administrator's Guide" to make sure you have set up your JDBC
Pool configurations correctly. If it was a RepositoryException, check your "webMethods Integration Server
ISS.0128.0001E Unable to get JDBC connection. Exception:<errorMessage>.

Cause: The Integration Server was unable to connect to the database defined by the DocumentHistory
functional alias. This alias defines the database that the Integration Server uses to detect duplicate documents.
Response: From the Settings>JDBC Pools> page of the Server Administrator, make sure that a Functional Alias
called DocumentHistory exists and is associated with a valid Pool Alias. Click the Test button. If the alias

ISS (IS Server)
exists, but there are errors when you hit the Test button, then there is a problem with the connection. Review
the Journal log for messages about the operation being performed. If the problem persists, contact your
Database Administrator.
ISS.0128.0002E Exception while<actionCausingError>:<errorMessage>.

Cause: An exception occurred when the Integration Server tried to perform a task using the In Doubt Resolver
component.
exists, but there are errors when you hit the Test button, then there is a problem with the connection. If the
problem persists, contact your Database Administrator.
ISS.0128.0003E SQLException:<errorMessage> while <actionPerfomredWithDocumentHistoryTable>.

Cause: An exception occurred when the Integration Server tried to perform a SQL operation using the JDBC
connection pool for the functional alias DocumentHistory.
exists, but there are errors when you hit the Test button, then there is a problem with the connection. Review
ISS.0128.0004E Exception while loading the Decision Tree: <errorMessage.

Cause: An exception occurred when the Integration Server tried to create the decision tree for resolving
duplicate documents. The decision is based on multiple criteria, but the Integration Server was not able to load
these criteria into memory.
Response: Contact webMethods Customer Care. Be prepared to provide logs and the version number and
patch level for the Integration Server and your operating system.
ISS.0128.0005E Exception:<errorMessage> while resolving Document of type: <nameOfDocument> and Id: <documentId>for
trigger: <nameOfTrigger>. Document is being deemed as In Doubt.
Cause: An exception occurred when the Integration Server tried to resolve a document it received. The
exception might be due to a problem with the database connection for the alias DocumentHistory or with the
Resolver Service associated with the trigger.
Response: Examine the Server log for error messages that indicate the cause of the problem. If the error was a
database/SQL exception, check to see if the functional alias DocumentHistory is working properly. If a
problem occurred with the Resolver Service, verify that the service is properly coded.

ISS.0128.0006E Trigger: <triggerName> encountered exception while executing resolver service: <nameOfService..
Exception: <errorMessage>.
Cause: The Integration Server received a document, but the Document Resolver Service associated with the
Trigger encountered an exception.
Response: Check the Error log to see if the Document Resolver Service associated with the Trigger has logged
any error messages. If no messages have been logged, go to the Developer and turn on Audit, Log on Error for
that service. In addition, because this is a user-written service, check it to make sure it has been coded
properly.
ISS.0128.0007E In Doubt document of type:<documentName> with Id:<documentID> received for trigger:<triggerName>.

Document is being Audit Logged.
Cause: The Integration Server received a document, but the Document Resolver Service associated with the
Trigger could not resolve the document and therefore considers it to be "In Doubt".
Response: Check the document's id to see if it is a duplicate. If there is an In Doubt Resolver Service associated
with the trigger, determine why the service was not able to resolve the document. The Integration Server
records occurrences of In Doubt Documents in the Audit log. You can view In Doubt documents through
WmMonitor.
ISS.0128.0008E Unable to Audit Log document of type:<documentName> with id:<documentId> as it can't be decoded.
Exception:<errorMessage>.
Cause: An error occurred when the Integration Server tried to resolve a document. As part of the resolution
process, a document first goes to the In Doubt Resolver component. If that component successfully resolves
the document, the Integration Server decodes the document and sends it to the trigger. However, if the In
Doubt Resolver cannot resolve the document, the Integration Server decodes the document and sends it to the
In Doubt Resolver service associated with the trigger. This error is issued if there is an error when decoding
the document before sending it to the In Doubt Resolver service associated with the trigger.
Response: Make sure the Document definition on the Integration Server matches the document definition on
the associated Broker. Re-sync the document by using the Developer tool, selecting the document and
choosing "Push to Broker". If all the Document fields and types match and the problem still persists, contact
ISS.0128.0009E Unable to get JDBC Connection to the database.

Cause: As part of storing history for the document being processed, the Integration Server's In Doubt Resolver
component add/deletes rows to a Database. While performing one of these actions, the connection to the
Database was lost.
problem persists, contact your Database Administrator. Review the Journal log for messages about the
operation being performed. If the problem persists, contact your Database Administrator.

ISS (IS Server)
ISS.0128.0014E Unable to insert UUID:<documentID>. Exception:<errorMessage>

Cause: As part of storing history for the Document being processed, the Integration Server's In Doubt Resolver
component stores the UUID (unique ID) of the Document in a Database. An exception occurred during this
process.
ISS.0128.0015E Document history initialization failed. Please verify database connection is available. Exception
<errorMessage>.
Cause: No valid JDBC connection Pool is available for the In Doubt Resolver Alias "DocumentHistory".
Detection of duplicate documents depends on the availability of a database where document history is
defined.
ISS.0128.9002E Unable to get Connection.

Cause: No valid JDBC connection Pool is available for the In Doubt Resolver Alias "DocumentHistory".
exists, but there are errors when you hit the test button, then there is a problem with the connection. Review
ISS.0128.9006E Invalid arguement supplied for:<parameterName>.

Cause: The Integration Server stores document history information in a database so that it can detect when
duplicate documents are received. This error occurs when a process tries to insert an entry that specifies an
invalid argument into the database.
Response: Check to see if the name of the Trigger and the UUID of the Document satisfy the constraints
specified on the columns of the Table WM_IDR_MSG_HST in your database. If the Trigger Name or UUID
exceeds the column length of the database column, this error can occur.

ISS.0128.9013E Exception while executing in doubt resolver service:<errorMessage>.

Cause: The Integration Server received a document, but an exception occurred during execution of the user-
written Document Resolver Service associated with the Trigger.
Response: Check the Integration Server's Error log to see if the Document Resolver Service has logged any error
messages. If no errors were logged, go to the Developer and turn on Audit, Log on Error for that service. In
addition, because this is a user-written service, verify that it has been coded properly.
ISS.0131.0001E No threads available. All diagnostic listener threads are in use.

Cause: The Integration Server has detected that all threads allocated to the diagnostic thread pool are in use.
Response: Wait for one or more of these threads to finish. If this problem persists, contact webMethods
Customer Care.

ISU (General Purpose)
ISU.0000.0000E Unable to connect to Broker. Starting to poll.

Cause: The Integration Server lost the connection to the Broker.
Response: Check the Broker to make sure that it is up and running. The Integration Server will reconnect
automatically when the Broker is up.
ISU.0000.0003U The minimum pool size must be <= the maximum pool size.
Cause: The minimum connection pool size and maximum connection pool size are not configured correctly in
the webMethods Adapter package.
Response: Refer the specific webMethods Adapter's documentation and make sure that the minimum
connection pool size is less than or equal to the maximum connection pool size.
ISU.0000.0009U Empty word in interface.

Cause: The service/document type name is missing after the interface. (e.g. "ifc:" is invalid)
Response: Define the service/doc Type name. ( e.g. ifc:name)
ISU.0000.0011U Illegal character <character> at index <index number>.

Cause: The IS namespace name has invalid characters.
Response: Remove those invalid characters.
ISU.0000.9102U transaction is not with current thread.

Cause: The webMethods Adapter that uses the IS Transaction API encountered an internal error.
ISU.0000.9103U transaction is not active.

ISU.0000.9104U current thread not with any transaction.


ISU.0000.9105U transaction not a Tran instance.

ISU.0000.9120U tran was rolled back because tran was marked for rollback.
Response: Because the transaction was rolled back, you might need to re-initiate the transaction. Check the logs
for further information about why the transaction was rolled back (for example, because of an unavailable
resource).
ISU.0000.9121E Rollback failed due to status.

ISU.0000.9124E resource can not be null.

Cause: The transaction resource was null when it was enlisted or delisted with the transaction manager. The IS
Transaction API in the webMethods Adapter was used incorrectly.
ISU.0000.9125U thread already associated with this transaction.

ISU.0000.9126U thread already associated with another transaction.

ISU.0000.9128E can not suspend due to state:

ISU.0000.9129E can not resume due to state:


ISU.0000.9130U another tran active. nested tran disabled in settings.

Cause: The Integration Server Transaction Manager throws this exception when a thread that is already
associated with one transaction attempts to start a second transaction, but the "nestedTrans" property is
disabled in the Transaction Manager properties.
Response: Refer the specific webMethods Adapter's documentation and enable the "nestedTrans" property.
ISU.0000.9131E properties can not be null.

Cause: The Integration Server encountered a serious internal error when creating the Transaction Manager.
ISU.0000.9144U runtime exception occured. see error log for details.

Cause: An Integration Server runtime exception occurred when committing the transaction.
Response: Refer the specific webMethods Adapter's documentation for details.

SCC (JCA System Contract Component Transaction Manager)
SCC.0121.0010E commit failed: <errorMessage> xid = <xidValue> rxid = <connectionName>

Cause: The Integration Server transaction manager was unable to commit a two-phase commit (2PC)
transaction to the backend XA resource.
Response: Check to see if the backend resource is connected to the Integration Server. Then, if necessary, re-
initiate the transaction.
SCC.0121.0017E rollback failed: <errorMessage> xid = <xidValue> rxid = <connectionName>

Cause: The Integration Server transaction manager was unable to roll back a two-phase commit (2PC)
transaction, most likely due to a resource issue.
Response: Check to see if the backend resource is connected to the Integration Server. Then, if necessary, re-
SCC.0121.0050U rollback-only flag is set. rolling back transaction, xid = <xid>.

Cause: The Integration Server is rolling back a transaction because a problem, such as an unavailable resource,
was encountered while processing the transaction.
Response: Check the log for other messages that indicate the cause of the problem. You might need to re-
SCC.0121.0052E Unable to persist transaction status for xid = <xidValue>: Exception: <errorMessage>
Cause: The transaction recovery manager of the Integration Server was unable to write the status of a two-
phase commit (2PC) transaction to the disk-based XA recovery store.
Response: Investigate the following possible causes for the problem:
1) The operating system userid under which the Integration Server is running does not have write privileges to
the XAStore directory.
2) There is not sufficient disk space for the directory.
3) The XA recovery store is corrupt. If this is the case, archive the files stored in the XA recovery store
directory, mail them to webMethods Customer Care, move the files in the XA recovery store to a backup
directory, and restart the Integration Server.

SCC.0121.0055E Unable to get unrecovered transactions from persistent store. Exception:<errorMessage>

Cause: The transaction recovery manager of the Integration Server was unable to obtain a list of incomplete
transactions from the XA recovery store. The Integration Server uses this store to hold two-phase commit
(2PC) transaction states for possible future recovery.
3) The XA recovery store is corrupt. If this is the case, archive the files stored in the XA recovery store
directory, mail them to webMethods Customer Care, move the files in the XA recovery store to a backup
SCC.0121.0062E Unable to rollback Xid:<xidValue> during recovery for resource:<nameOfConnection>, transaction might
been heuristically rolled back/commited by resource. Manual intervention might be required. Exception:<exceptionText>:
Error Code:<errorCodeFromException>.
Cause: The transaction recovery manager of the Integration Server detected a transaction whose status in the
Integration Server is different from the status stored in the back-end resource (for example, a database). This
situation occurs when the transaction recovery manager tries to rollback a transaction that the back-end XA
resource has already rolled back or committed.
Response: Check to see if the back-end resource administrator (for example a database administrator )
manually issued a rollback/commit for the incomplete transaction. If so, ensure that the other back-end XA
resources do the same.
SCC.0121.0067E Unable to commit Xid:<xidValue> during recovery for resource:<ConnectionName>, transaction might been
heuristically rolled back/commited by resource. Manual intervention might be required. Exception:<errorMessage>.
Cause: The transaction recovery manager of the Integration Server detected a transaction whose status in the
Integration Server is different from the status stored in the back-end resource (for example, a database). This
situation occurs when the transaction recovery manager tries to commit a transaction that the back-end XA
resource has already rolled back or committed.
Response: Check to see if the back-end resource administrator (for example a database administrator) manually
issued a rollback/commit for the incomplete transaction. If so, ensure that the other back-end XA resources do
the same.

SCC.0121.0094S Unrecoverable Exception while initializing the XA Recovery Store: <errorMessage>

Cause: The Integration Server was unable to create a persistent XA recovery store on disk. The Integration
Server uses this store to hold two-phase commit (2PC) transaction states for possible future recovery.
the XA recovery store directory.
3) The XA recovery store is corrupt. If this is the case, archive the files stored in the XAStore directory, mail
them to webMethods Customer Care, move the files in the XA recovery store to a backup directory, and restart
the Integration Server.
SCC.0121.0098E XARecoveryStore: Global xid=<xidValue> not found. Failed attempt to store status=<2PCStatus>
Cause: The Integration Server encountered an invalid or null value for the global XID value when trying to
update the XA recovery store. The Integration Server uses this store to hold two-phase commit (2PC)
transaction states for possible future recovery.
Response: This is an internal error. Examine the server log for any error messages regarding the XA recovery
store and contact webMethods Customer Care.
SCC.0121.0099E XARecoveryStore: Transaction start for xid=<xidValue> failed. Transaction for this xid has already been
started.
Cause: The Integration Server detected an XID that is already being processed elsewhere. XIDs must be
globally unique.
SCC.0121.0112E Error while shutting down XA Recovery Store:<errorMessage>.

Cause: The Integration Server XA recovery store did not shut down cleanly. The Integration Server uses this
store to hold two-phase commit (2PC) transaction states for possible future recovery.
Response: Restart the Integration Server and examine the Server log for any error messages regarding the
XARecovery Store. If the problem is a file permission or out of storage issue, correct the problem and restart
the Integration Server. If the problem is not a file permission or out of storage issue, archive the contents of the
XAStore directory and contact webMethods Customer Care.

SCC.0121.0113E Recover call on XAResource:<connectionName> failed. Exception:<errorMessage>, Error

Code:<errorCode>
Cause: The transaction recovery manager of the Integration Server encountered an error when it tried to obtain
a list of all incomplete XIDs known to the back-end resource. The error occurred because the back-end
resource threw an exception.
Response: Check to see if the back-end resource is available and connected to the Integration Server. The name
of the resource will be the name of the connection defined in the adapter for the resource.
SCC.0121.0114S Unable to get to XA Recovery Store. Transaction Manager will not be able to support Transaction Recovery
if the server crashes in the middle of a 2PC commit phase. Exception:<errorMessage>.
Cause: The Integration Server transaction manager was unable to access the XA recovery store. The Integration
Server uses this store to hold two-phase commit (2PC) transaction states for possible future recovery.
3) The XA recovery store (XAStore\XARecoveryStore) is corrupt. If this is the case, archive the files stored in
the XAStore directory, mail them to webMethods Customer Care, move the files in the XAStore to a backup
SCC.0121.0115W Unable to auto-resolve xid:<xidValue>. Manual resolution required Error:<errorMessage>

Cause: The transaction recovery manager of the Integration Server was unable to resolve the indicated XID. It
will continue trying to resolve the XID until the timeout value specified on the
watt.server.transaction.recovery.abandonTimeout property is reached.
Refer to the chapter "Using Integration Server to Manage XA Transactions" in the "webMethods Integration
Server Administrator's Guide" for instructions on manually resolving the transaction.

XSL (XSLT Service)
XSL.0003.9010E XSLT Service: No valid input provided

Cause: The Integration Server attempted to run an XSLT service, but no valid input was provided. Valid input
includes a URL to an XML file, a file name, or an XML stream.
Response: Provide a valid input parameter to the XSLT service.
XSL.0003.9011E XSLT Service: No associated .xsl file for this service.

Cause: The Integration Server attempted to run an XSLT service, but could not find the XSLT file that is
supposed to be associated with the service.
The associated .xsl file should reside in the same directory as the node.ndf file that is associated with the XSLT
service. In addition, the .xsl file should have the same basename as the directory, appended with ".xsl". For
example, for XSLT service wm.example:bar, the associated .xsl file is ns/wm/example/bar/bar.xsl.
Response: Check the file system for the appropriate file, which may need to be renamed to match the XSLT
service name.

CHAPTER 8
webMethods Logging Utility
LGU.0001.0001W Could not retrieve batch size parameter: <exceptionInfo>

Cause: The Logging Utility could not access the batch size value specified in the LoggingUtility.cnf file,
possibly for one of these reasons: (1) the file does not exist, (2) the file is not readable, or (3) the file does not
contain the proper information. The Logging Utility used the default batch size value 10 instead.
Response: Make sure the LoggingUtility.cnf file exists, is readable, and contains the proper information. Then
restart the Logging Utility to pick up the batch size value specified in the LoggingUtility.cnf file instead of the
default.
LGU.0001.0002S Error getting audit runtime: <exceptionInfo>

Cause: The Logging Utility made a call to the Integration Server audit subsystem API to retrieve a handle, but
the API call failed. The audit subsystem might be configured improperly or might be down.
Response: Make sure the audit subsystem is configured properly and is running. For information on the audit
subsystem, see the "webMethods Logging Guide."
LGU.0001.0003S Error creating broker admin client: <exceptionInfo>

Cause: The BrokerTransportFactory could not create the Broker Administrator client for the Logging Utility.
Response: Make sure the Logging-Utility equipped Integration Server is connected to a Broker and make sure
the Broker is running.Then restart the Integration Server.
LGU.0001.0004 Error connecting to repo: <exceptionInfo>

Cause: The Logging Utility cannot connect to its host Integration Server's repository.
Response: Make sure the repository is configured correctly. For instructions, see the "webMethods Integration
Server Clustering Guide." Then restart the Integration Server.

CHAPTER 8 webMethods Logging Utility
LGU.0002.0001E Error getting broker log length: <exceptionInfo>

Cause: The Logging Utility asked the Broker for the number of available log documents but the request failed,
possibly for one of these reasons: (1) the Broker is down, (2) the Broker is no longer connected to Integration
Server because the network is down, or (3) the request to the Broker timed out because the Broker host
machine is overloaded.
Response: Make sure the Broker is running. If the Broker is on a different machine than Integration Server,
make sure the network link between the two machines is up. Make sure the machine on which the Broker is
running is properly configured with enough memory and CPUs.
LGU.0002.0002E Error getting log events: <exceptionInfo>

Cause: The Logging Utility asked the Broker for available log documents but the request failed, possibly for
one of these reasons: (1) the Broker is down, (2) the Broker is no longer connected to Integration Server because
the network is down, or (3) the request to the Broker timed out because the Broker host machine is overloaded.
LGU.0002.0003E Error processing WorkflowLog document: <exceptionInfo>

Cause: An error occurred while the Logging Utility was processing the log document for a Workflow activity.
The error could have occurred for several reasons, such as a field in the log document is not set or there is as
problem with the Audit Log Manager. The message that follows displays the actual log event that caused the
error.
Response: Make sure all fields in the log document are properly set, the audit subsystem is configured
correctly, and Workflow is configured correctly for logging. For information on setting up logging, see the
"webMethods Logging Guide."
LGU.0002.0004E Error processing ProcessLog document: <exceptionInfo>

Cause: An error occurred while the Logging Utility was processing a log document for a flow step. The error
could have occurred for several reasons, such as a field in the log document is not set or there is as problem
with the Audit Log Manager. The message that follows displays the actual log event that caused the error.
correctly, and Integration Server is configured correctly for logging. For information on the audit subsystem
and setting up logging, see the "webMethods Logging Guide."

LGU.0002.0005E Error processing trigger document: <exceptionInfo>
Cause: An error occurred while the Logging Utility was processing a trigger log document. The error could
have occurred for several reasons, such as a field in the log document is not set or there is as problem with the
Audit Log Manager. The message that follows displays the actual log event that caused the error.
correctly, and Integration Server is configured correctly for logging. For information on the audit subsystem
and setting up logging, see the "webMethods Logging Guide."
LGU.0002.0007E Error deleting log events: <exceptionInfo>

Cause: The Logging Utility asked the Broker to delete processed log documents but the request failed, possibly
for one of these reasons: (1) the Broker is down, (2) the Broker is no longer connected to Integration Server
because the network is down, or (3) the request to the Broker timed out because the Broker host machine is
overloaded.
LGU.0002.0008E Error destroying broker admin client: <exceptionInfo>

Cause: The Logging Utility shut down, but the Logging Utility's Broker Administrator client could not be
destroyed.
Response: Restart and re-shut down the Logging Utility.
LGU.0002.0009S Error publishing audit data: <exceptionInfo>

Cause: The Logging Utility could not write log data to the audit subsystem. The audit subsystem might be
configured improperly or might be down.
Response: Make sure the audit subsystem is configured properly and is running. For information on the audit
subsystem, see the "webMethods Logging Guide."
LGU.0002.0010S Batch Size cannot be less than 1

Cause: The batch size value for the Logging Utility is set to less than 1, but the value must be 1 or greater.
Response: Open Integration Server Administrator and go to the Logging Utility > Settings > Configure >
Display Settings page. Set the batch size to 1 or greater. (Note: The LoggingUtility.cnf file is automatically
updated with this change.)

CHAPTER 8 webMethods Logging Utility
LGU.0002.0011S Bad processState value

Cause: The value in the processState field in the log document is of an unknown type, because a user manually
modified the value.
Response: This field should never be manually modified. Delete the log document and do not allow any future
manual modification to occur.
LGU.0002.0015S Error acquiring cluster lock: <exceptionInfo>

Cause: The Logging Utility could not acquire a lock on its host Integration Server's repository.
LGU.0002.0016S Error releasing cluster lock: <exceptionInfo>

Cause: The Logging Utility could not release its lock on its host Integration Server's repository.

CHAPTER 9
webMethods Mainframe
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 9 webMethods Mainframe
General Server Errors

The following table contains webMethods Mainframe errors between the hexadecimal values 800403EA and
800403F3.
Host
Hexadecimal Input
Value Sent Reason Action
800403EA No An internal system error has occurred. Contact Customer Care.
800403EB Yes A transaction time-out has occurred. The Increase the time-out value for this
transaction was submitted to the host transaction and try again. Verify that the
system but has not completed within the transaction has worked correctly.
configured amount of time.
800403EC No The client application has delivered a Check the format of messages from the
malformed message. client application.
800403ED No webMethods Mainframe has received an Verify the versions of the webMethods
unsupported client message. This error components.
is caused by an incompatibility between
the webMethods Integration Server-
webMethods Mainframe Package and
webMethods Mainframe Administrator.
800403EF No An internal request to webMethods Verify the versions of the webMethods
Mainframe was missing a required components and contact Customer Care.
parameter.
800403F0 No An internal request to webMethods Verify the versions of the webMethods
Mainframe contained an invalid components and contact Customer Care.
parameter.
enumeration value.
Mainframe contained an invalid node. components and contact Customer Care.
attribute.

Client Communications (TCP/IP) Errors
Client Communications (TCP/IP) Errors

The following table contains webMethods Mainframe errors between the hexadecimal values 800404B1 and
800404B6.
Host
Hexadecimal Input
800404B1 No A TCP/IP receive operation failed to Check for any network problems (for
complete while webMethods Mainframe example, caused by routers or cables)
was trying to receive a message from the between thewebMethods Integration
webMethods Integration Server- Server-webMethods Mainframe Package
webMethods Mainframe Package. and webMethods Mainframe.
800404B2 Yes A TCP/IP send operation failed to Check for any network problems (for
complete while webMethods Mainframe example, caused by routers or cables)
was trying to send a message to the between thewebMethods Integration
webMethods Integration Server- Server-webMethods Mainframe Package
webMethods Mainframe Package. and webMethods Mainframe.
Note: Data may have been sent to the Check the TxEvent.Log file for details
host system during this transaction about the state of the client transaction
request. when the failure occurred.
800404B3 No The webMethods Integration Server- Check for any network problems (for
webMethods Mainframe Package could example, caused by routers or cables)
not connect to webMethods Mainframe. between the webMethods Integration
Server-webMethods Mainframe Package
and webMethods Mainframe.
800404B4 No webMethods Mainframe has received an Verify the TN3270E server configuration.
unsupported TN3270E command code.
800404B6 No webMethods Mainframe disallowed a Check the webMethods Mainframe
request because the IP address is not configuration and verify that the IP
authorized for administrative functions. Address is allowed administrative
access.
Verify that a proxy server is not
modifying the IP Address between the
webMethods Integration Server-
webMethods Mainframe Package and

Transaction and Data Conversion Errors

The following table contains webMethods Mainframe errors between the hexadecimal values 80040515 and
80040532.
Host
Hexadecimal Input
80040515 No An internal system error has occurred. Contact Customer Care.
80040519 No An invalid mapping was detected at To determine the source of the error,
load time because a field was not check the TxEvent.Log file. In
correctly defined. webMethods Developer, determine
whether the field is mapped correctly.
8004051A No An invalid mapping was detected at To determine the source of the error,
load time because a record was not check the TxEvent.Log file. In
correctly defined. webMethods Developer, determine
whether the field is mapped correctly.
8004051B No An invalid mapping was detected at To determine the source of the error,
load time because a host transaction was check the TxEvent.Log file. In
not found or was not valid. webMethods Developer, determine if
the transaction service is validated or
missing altogether.
8004051C – Yes The transaction failed because a general To determine the source of the error,
80040523 failure occurred in mapping between check the TxEvent.Log file.
transactions.
Note: This error occurs after data has
already been sent to the mainframe.
80040527 Yes The transaction failed. A dynamic To determine the source of the error,
mapping translation error has occurred check the TxEvent.Log file.
because invalid data (or NULL data) was
received from either the host or client.
mapping translation error has occurred check the TxEvent.Log file. In
because fields with invalid data types webMethods Developer, determine if
were mapped together. the fields are mapped correctly.

Transaction and Data Conversion Errors
Host
Hexadecimal Input
because an invalid data format, such as webMethods Developer, determine if
non-numeric data in a numeric-only the field is mapped correctly.
field, was received from either the host
or client.
8004052B Yes The transaction failed. A dynamic To determine the source of the error,
because a client or host field contains no webMethods Developer, determine if
data but was not designated as optional. the field is mapped correctly.
8004052C Yes The transaction failed. A dynamic To determine the source of the error,
because a client or host field (or record webMethods Developer, determine if
count) contains more data than was the field is mapped correctly. Check the
allowed in the configuration. truncation setting in the field.
8004052D Yes The transaction failed. A dynamic To determine the source of the error,
because a field (or record count) contains webMethods Developer, determine if
less data than was allowed in the the field is mapped correctly. This error
configuration. is usually corrected by turning on field
padding, spaces, or zero fill, depending
Note: This error occurs after data has on the field type.
8004052E No The requested transaction has been In webMethods Developer, enable the
disabled. transaction service.
8004052F No The transaction already has a subscriber. Only one subscriber is allowed per
transaction. Stop and restart the
subscription.
80040530 No The requested transaction is publish Publish transactions cannot be issued in
only. request/reply mode. In webMethods
Developer, verify that this is a
publishable transaction service.

Host
Hexadecimal Input
80040531 Yes Data was received for a transaction that In webMethods Developer, determine if
had no subscribers. the transaction service is correctly
configured.
80040532 No The subscriber is attempting an In webMethods Developer, determine if
operation on a transaction that has a the transaction service is correctly
different subscriber. configured.

Host Communication System Errors

The following table contains webMethods Mainframe errors between the hexadecimal values 80040579 and
800405B0.
Host
Hexadecimal Input
80040579 – No An internal system error has occurred. Contact Customer Care.
8004058D
8004058E No The SNA communications server could On the machine where the SNA
not allocate any memory from the communications server is running,
machine on which it was running. determine if the system is running low
on memory.
8004058F No A Lock Session or SmartLock request Check your application program or
was received but the session was already webMethods services to determine why
locked. the lock request is being made multiple
times.
80040591 No A Submit request was received with a Check for the following possible causes
correlation value set, but it does not of this error:
match the current lock state of
The correlator has timed out. In
processing session.
webMethods Developer, check the Lock
time-out value for the host connection
pool.
The correlator does not match a locked
session. Make sure the correlator is not
hard coded.
The session unlocked itself due to a host
or transaction error. To determine the
source of the error, check the
TxEvent.Log file.
The configuration changed while the
session was locked and the session no
longer exists.
80040592 No An Unlock Session request was received, The session lock may have timed out. In
but the indicated session was not locked. your application program or
webMethods services, check the Lock
time-out value for the host connection
pool.
80040593 – No Internal configuration errors have Contact Customer Care.
80040596 occurred.

Host
Hexadecimal Input
80040597 Yes The transaction failed. The Ask your IT department if there have
communication system received a been any system problems.
protocol violation from a chained
Check the event logs of your SNA
receive.
communications server.
Check your application program to see if
it was properly designed chained
receives.
80040599 Yes The transaction failed because the Ask your IT department if there have
communication system failed to process been any system problems.
a send to the host system.
To determine the source of the error,
Note: Because webMethods Mainframe check the TxEvent.Log file.
can perform multiple sends for a
Check the event logs of your SNA
transaction, some data may have been
sent to the mainframe.
Check your application program to
make sure it was properly designed.
8004059A Yes The transaction failed because an LU 2 In your application program or
transaction was configured incorrectly. webMethods services, check the
The offset is not valid within the current configured offset for the field that is in
model size of this session. error.
Note: Some data may have already been To recover the state, power the session
sent to the mainframe system and the off and then on from webMethods
session is in an unknown state. Mainframe Administrator.
8004059B Yes The transaction failed because the LU 2 In your application program or
transaction was configured incorrectly. A webMethods services, check the
non-numeric value was being set in an configured offset and data type for the
LU 2 numeric field. field that is in error.
LU/Session is in an unknown state. Mainframe Administrator.
8004059C No The transaction failed. The In webMethods Mainframe
communication system could not Administrator, start sessions in the
process the transaction because the host affected host connection pool.
connection pool has no active sessions.
Ask your IT department whether there
have been system, sign-on, or host
region problems.

Host
Hexadecimal Input
8004059D Yes The transaction failed. The To determine the source of the error,
communication system could not check the TxEvent.Log file or the error
process the transaction because a description field from the Client API.
standard host error has occurred.
Ask your IT department if there have
been system, sign-on, or host region
problems.
8004059E Yes The transaction failed because the To determine the source of the error,
communication system received an check event logs of your SNA
operating system error while processing communications server.
this transaction.
Note: At the time webMethods
Mainframe processes a receive frame,
some information has already been sent
to the mainframe system.
8004059F Yes The transaction failed. The To determine the state of the transaction
communication system stopped at the time of the error, check the
processing the transaction because TxEvent.Log file.
webMethods Mainframe was shut
down.
been system, sign-on, or host region
Note: The transaction in progress could problems.
be at any state and may have sent
information to the mainframe system.
Check the TxEvent.Log for more detail.
800405A0 Yes The transaction failed. The In webMethods Developer, check the
communication system stopped configured time-out value for the
processing the transaction because a transaction service.
response was not received from the
mainframe within the configured time-
been system or host region problems.
out value for this transaction.
800405A1 Yes The transaction failed. The To determine the source of the error,
communication system stopped check event logs of your SNA
processing the transaction because communications server.
webMethods Mainframe lost contact
with the mainframe system.

Host
Hexadecimal Input
processing the transaction because an communications server.
error was returned during a receive
operation.
processing the transaction because the communications server.
session was disconnected from the host
application region (CICS or IMS).
800405A4 – No An internal lock session error occurred. Contact Customer Care.
800405A6
800405A7 Yes The transaction failed. The Check with your webMethods
communication system stopped Mainframe administrator.
processing the transaction because the
session was abnormally stopped from
800405A8 – Yes An internal output data processing error Contact Customer Care.
800405AA occurred.
800405AB Yes The transaction failed. The In your application program or
communication system stopped webMethods services, check that the
processing the transaction because the conversation transaction setting is
host request executed a conversation selected.
transaction, but the definition did not
match.
800405AD Yes An internal output data processing error Contact Customer Care.
occurred.
800405AE Yes The transaction has failed because the In webMethods Developer, check the
LU 2 transaction is configured configured definition of the transaction
incorrectly. Data was being set to a service. The host definition may have
protected field on the LU 2 screen. changed for this transaction screen.
session is in an unknown state. Mainframe Administrator.

Host
Hexadecimal Input
800405AF No The transaction failed. The In webMethods Developer, check the
communication system stopped configured definition of the transaction
processing the transaction because a service.
configured User Exit could not be loaded
or found.
800505B0 No The transaction is being canceled due to In webMethods Developer, verify that
an administrative request. this is a publishable transaction service.

APPC Errors
The following table contains webMethods Mainframe errors between the hexadecimal values 800405D3 and
800405D9.
Host
Hexadecimal Input
800405D3 No The APPC interface failed to initialize. Check APPC server availability.
800405D4 No An APPC Allocate verb failed. Check the APPC configuration in the
SNA communications server.
800405D5 No An APPC TP-Started verb failed. Check the APPC configuration in the
SNA communications server.
800405D6 Yes An APPC TP-Ended verb failed. Check the event logs of your SNA
800405D7 Yes An APPC Deallocate verb failed. Check the event logs of your SNA
800405D8 No An APPC SendData verb failed. Check the event logs of your SNA
800405D9 Yes An APPC ReceiveAndWait verb failed. Check the event logs of your SNA

CICS Sockets Errors
CICS Sockets Errors

The following table contains webMethods Mainframe errors for CICS Sockets.
Display Text Reason Action

Program <progName> is The program is either not defined to Verify that the name of the program
either not defined or is CICS or is currently disabled. is correct. If not, use webMethods
disabled Developer to change the Program
Name in transaction service
properties.
If the program name is correct, use
CEDA on the mainframe to verify
that the program is defined to CICS,
or use CEMT to enable the program.
Not authorized to use The program is not authorized for On the mainframe, grant permission
program <progName> use by the gateway transaction. to the gateway transaction to execute
the program.
Application program The program has abended. On the mainframe, if WMERRH is set
<progName> abended to produce dumps, a transaction
dump is taken with the specified
dump code. If the abend is an ASRA
abend, an SVC dump is produced by
CICS.
Program <progName> The size of the input or output It is most likely you are mapping the
Return Code: LENGERR transaction data buffers is greater wrong data buffer. In webMethods
than 32767. Developer, check that the offset plus
the length of the field does not
exceed 32767 bytes.
Program <progName> The SYNCPOINT issued by the On the mainframe, verify with CEDA
Return Code: SYNCPOINT gateway program has failed. that the gateway program is defined
failed with EXECUTIONSET FULLAPI.
Program <progName> A program error has occurred in the Contact Customer Care.
Return Code: gateway program.
ROLLEDBACK
Return Code: INVREQ gateway program.
Return Code: LINK error gateway program.


CHAPTER 10
webMethods Manager Server
Unnumbered Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Numbered Manager Server and MBean Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

CHAPTER 10 webMethods Manager Server
Unnumbered Exceptions
Manager Server
addCollectorListener: Listen Failed: <exception>

Cause: An InstanceNotFoundException has occurred.
addNotificationListener: Listen Failed: <exception>

Cause: A JMException, JMRuntimeException has occurred.
Details of the selected objects could not be created

Cause: Manager Server Administrator could not retrieve the information for the selected server-level objects in
order to generate the Technical Environment Profile.
Response: Make sure that the selected server-level objects are being managed by Manager Server
Administrator and are OPERATIONAL, then retry the operation.
dispatcher unregistered after notification failure: exception>

Cause: Integration Server cannot send notifications to Manager Server.
Response: Check the connection to Manager Server and make sure Manager Server is accepting notifications.
To trigger a notification to Manager Server, enable or disable any package on the Integration Server.
dispatcher unregistered after ping failure: <exception>

Cause: Integration Server cannot communicate with Manager Server.
Response: Check the connection to Manager Server. Make sure Manager Server is running.
dispatcher unregistered after ping "timeout”

Cause: Integration Server cannot communicate with Manager Server.
Response: Check the connection to Manager Server. Make sure Manager Server is running.

Error in deleting file. Exception : {exception}

Cause: The Send Email operation failed because a temporary file that was created for the email attachment
could be deleted.
- write permissions on the disk
- the file is used by another application
- the file is corrupted
Error occured while performing File I/O operation

Cause: Manager Server Administrator could not write the log file information to a compressed file
Response: Check the disk for write permissions and adequate storage space, then retry the log file Save or Send
operation.
Error occured while performing zip operation.

Cause: The file compression process failed.
operation.
Error occured while saving the details to a file

Cause: Manager Server Administrator could not write log file information to a compressed file.
operation.
Invalid dispatch identification: <key>

Cause: Manager Server experienced an internal error. Manager Server and Integration Server might be
disconnected or might have been disconnected earlier.
Response: If Manager Server does not correct this problem automatically, stop managing the resource, and
then start managing the resource again.
Migration complete. Manager Server shutting down

Cause: This is a status message. Data migration is complete and the Manager Server has been shutdown.
Response: Restart the Manager Server to begin managing webMethods component resources.

No log files matching the criteria were found

Cause: Manager Server Administrator could not find any log files matching the given criteria.
Response: Change the search criteria to return one or more log files. For example, broaden the search by
extending the range of dates within which to conduct the search.
No Server level managed objects retreived from Manager Server

Cause: A server-level object was not selected for generating the Technical Environment Profile.
Response: In the Technical Environment Profile list, under Available Objects, select one or more server-level
objects for which you want to gather information, then retry the operation.
Send Email failed : Attached file size more than allowed size
Cause: The Send Email operation failed because the log file information exceeded the 5MB limitation.
Response: Log files exceeding 5MB cannot be sent through email from the Supportability Administration page.
Select fewer log files and reduce the number of server-level objects, then retry the operation.
Send Email failed : No Information to be sent

Cause: The Send Email operation failed because a Technical Environment Profile or log file was not selected.
Response: Select the Technical Environment Profile or log files to send, then retry the operation.
Send Email failed due to error in generating TEP. Error Message : {errorMessage}
Cause: The Send Email operation failed because Technical Environment Profile did not get created.
Response: Refer to the Action column for the accompanying message.
Send Email failed due to error in generating zipped log files. Error Message {errorMessage}
Cause: The Send Email operation failed because there was an error in generating the compressed log files.
Response: Refer to the Action column for the accompanying message.
Send Email Failed. Exception : {exception}

Cause: The Send Email operation failed because of an exception.
Response: Make sure all email settings are configured properly, then retry the operation.
Storage Exception: Logged off

Cause: The operation cannot be completed because Manager Server is disconnected from the repository.
Response: Restart Manager Server to reconnect to the repository.

The Integration Server <serverName> cannot be managed because it is a webMethods Manager Server.
Cause: Manager Servers cannot manage other Manager Servers.
Response: Manager Servers cannot be managed. A Manager Server cannot be used as an Integration Server.
The object reference '<objectName>' is invalid.

Cause: The object name for registerNotificationInterest is not registered.
Response: Specify a registered object name.
Timeout waiting for the Integration Server to start

Cause: Manager Server cannot start managing this Integration Server because Integration Server has not
started.
Response: Wait for Integration Server to start. If Integration Server does not start, check the server and error
logs for exceptions or errors. Resolve any issues indicated in the server and error logs and then restart
Integration Server.
Zip file could not be formed

Cause: Manager Server Administrator could not create a file name for the compressed log files.
Response: Retry the log file Save or Send operation.
MBean
BpDiscovery.postRegister() Exception: <exception>

Cause: An internal error has occurred.
Response: Restart Manager Server and try to discover the business process again.
<exception>
Cause: The database profile is experiencing problems.
Response: Check the database profile and verify that the database is accessible from the Manager Server. Also
check that the Monitor tables exist in the database.
<exception>
Cause: The database profile has problems or an internal error has occurred.

<exception>
Response: Restart Manager Server and try to discover the resource or object again.
<exception>
Cause: Manager Server encountered a problem while storing the profile.
Response: Restart Manager Server and try to discover the resource or object again.
<exception>
Cause: Manager Server encountered a problem while storing the profile.
Response: Delete the resource and then start managing it again.
<exception>
Cause: Manager Server encountered a problem while creating a database profile.
Response: Rediscover the business process.
<exception>
Cause: Manager Server encountered a service exception while managing the Business Process.
Response: Verify that the Admin Server is accessible from the Manager Server.
Logged off
Cause: The operation cannot be completed because the database user is logged off.
Response: The database user should log on to the database used for Manager storage.

Numbered Manager Server and MBean Errors
ISS.0040.0001E Error getting Document Type statistics: <BrokerException>

Cause: Manager Server encountered an error while obtaining statistic values for document types using the API.
Response: Resolve the issue returned by the exception. Refer to Manager error log for detailed information
about the exception.
ISS.0040.0001E Error writing property file: enterprise.cfg

Cause: Manager Server encountered an error while creating the document type management configuration file.
ISS.0040.0001E File not found: enterprise.cfg

Cause: Manager Server could not find the property file containing the properties that enable document type
management.
Response: Create a file called enterprise.cfg in the WmOmiEnt\config directory. In this file, set the
watt.ism.docType.enabled property to false (watt.ism.docType.enabled=false).
ISS.0040.0002E Error creating Document Type Managed Object: <Broker Exception message>
Cause: Manager Server could not create the document type managed object.
ISS.0040.0002E Error initializing Document Type Mbean: <exception>

Cause: Manager Server encountered an error while initializing Document Type managed object attributes.
ISS.0040.0003E Error connecting to Broker Server

Cause: Manager Server encountered an error when connecting to the Broker while filtering document type
managed objects.
Response: Make sure the Broker is running.

ISS.0040.0003E Error deleting Document Type Managed Object: <MBeanRegistrationException>

Cause: Manager Server could not delete the document type managed object.
ISS.0040.0003E Error setting polling values in property file

Cause: Manager Server encountered an error while setting the value in the Broker polling configuration file.
ISS.0040.0004E Error connecting to Broker: <BrokerException>

Cause: Manager Server could not connect to the Broker while creating document type managed object.
ISS.0040.0004E Error creating Document Type Config File: <exception>

Cause: Manager Server encountered an error while creating the document type management configuration file.
ISS.0040.0005E Error registering Document Type Managed Object: <MBeanRegistrationException>

Cause: Manager Server could not register the document type managed object.
ISS.0040.0006E Error reading Document Type Config File: <IOException>

Cause: Manager Server encountered an input/output exception while reading the document type filtering
configuration file.
ISS.0040.0007E Encountered Document Type Config File format issue: <BrokerHostPort> <BrokerName>
Cause: Manager Server encountered a file format issue while reading the document type filtering configuration
file.
Response: Check the document type filtering configuration file for XML formatting issues, such as mismatched
brackets.

ISS.0080.0001E Failed to initialize server storage

Cause: There was an error initializing Manager Server storage.
Response: Check the error log file for details about the error.
ISS.0080.0004E Database not configured

Cause: The JDBC connection pool was not initialized.
Response: Verify that the database connection has been configured and is able to connect to the database, then
retry the operation.
ISS.0080.0017E Missing object name for managed object: {objectName}

Cause: The object name could not be found in the database.
Response: Stop and restart managing the associated server object.
ISS.0080.0018E Missing object description for managed object: {objectName}

Cause: Object description could not be found in the database
Response: Stop and restart managing the associated server object.
ISS.0080.0029E Notification Listener cannot be initialized, Server storage is not initialized

Cause: Notification listener could not be initialized because there was a problem initializing server storage.
Response: Verify that the database connection has been configured correctly and is able to connect to the
database.
ISS.0080.0030E Model Storage cannot be initialized, Server storage is not initialized

Cause: Model storage could not be initialized because there was a problem initializing server storage.
Response: Verify that the database connection has been configured correctly and is able to connect to the
database.
ISS.0080.0031E Failed to store attribute {attributeName} for object {objectName}

Cause: The attribute value could not be stored.
Response: Check the Manager Server error log for details on the exception and correct the issue.
ISS.0080.0032E Notification message text truncated for storage {text string}

Cause: A notification message could not be stored because it is too large for the field.
Response: Check the Manager Server error log to view the notification message.

ISS.0080.0033E SQL Exception occured in add notification process for Serial : {notificationSerial value}
Cause: A notification could not be added.
Response: Check the Manager Server error log for details about the exception and correct the issue.
ISS.0080.0034E SQL Exception occured for SQL : {statementLastExecuted}

Cause: An exception was encountered while executing an SQL statement.
ISS.0080.0035E SQL Exception occured while initializing Notification Listener

Cause: An exception was encountered while the notification listener was initializing.
Response: Check the Manager Server error log for details about the exception and to determine if an action is
required.
ISS.0080.0036E Error getting database connection while initializing Notification List

Cause: A connection to the database could not be made while initializing the notification list.
Response: Check the Manager Server error log for details about the exception and to determine if an action is
required.
ISS.0080.0037E Error setting notification prune length: {pruneLength value}

Cause: The notification prune length could not be set.
ISS.0080.0038E Error setting notification prune age: {pruneAge value}

Cause: The notification prune age could not be set.
ISS.0080.0039E Error setting notification prune interval: {pruneInterval value}

Cause: The notification prune interval could not be set.
ISS.0080.0040E Error storing notification: {notificationSerial value}

Cause: The notification could not be stored.

ISS.0080.0041E Error pruning notifications by length: {SQLException message}

Cause: The notifications could not be pruned by length.
ISS.0080.0042E Error pruning notifications by age: {SQLException message}

Cause: The notifications could not be pruned by age.
ISS.1000.1001E Incompatible Manager Server data.

Cause: The storage data version is incompatible with the storage version.
Response: Make sure the WmOmiServer package is the same version as Manager Server. (Use Integration
Server Administrator to check the package version number.) If necessary, reinstall Manager Server using the
ISS.1001.1001E Operation not found

Cause: Manager Server cannot find the operation being invoked.
Response: Make sure that the operation exists.
Response:
ISS.1001.1013E The object reference '<objectName>' is invalid.

Cause: The object name for registerNotificationInterest is invalid.
Response: Specify a valid object name. (For more information, see the "webMethods Manager Server
Programmer's Guide.")
ISS.1001.1015E The object reference '<objectName>' is not valid.

Cause: This parameter has an invalid object name.
Response: The object name must start with "omi."

Cause: An MBean does not exist for getMBeanInfo.
Response: Specify a valid MBean.


Cause: This object does not exist for getAttributes.
Response: Invoke this operation on a valid object.

Cause: This object does not exist for setAttributes.

Cause: This object does not exist for invokeOperation.

Cause: This object reference has an invalid object name.
Response: This object is not registered. Specify a registered MBean.
ISS.1002.1051E The operation '<operationName>' is invalid.

Cause: The operation specified is not available for this object.
Response: Invoke a valid operation. (Operations vary by MBean. For more information, see the "webMethods
Manager Server Programmer's Guide.")
ISS.1002.1055E The operation '<operationName>' is invalid.

Cause: This method does not exist for invokeOperation.
Response: Invoke a valid method on this object.
ISS.1003.1016E The parameter 'attributeName' is missing.

Cause: This parameter contains an invalid attribute name.
Response: Request a valid attribute. (Attributes vary by MBean. For more information, see the "webMethods
ISS.1003.1033E The parameter 'mode' is missing.

Cause: No notifications have been specified for getNotifications.
Response: Specify a notification.

ISS.1003.1036E The parameter 'startSerial,endSerial,startTime,endTime' is missing.

Cause: Parameters for getNotifications are missing.
Response: Specify the parameters startSerial and endSerial or startTime and endTime.
ISS.1003.1038E The parameter 'startSerial' is missing.

Cause: The parameter endSerial is specified but startSerial is not.
Response: Specify both the parameters startSerial and endSerial.
ISS.1003.1039E The parameter 'startTime' is missing.

Cause: The parameter endTime is specified but startTime is not.
Response: Specify both the parameters startTime and endTime.
ISS.1004.1020E The parameter 'mode' is invalid.

Cause: No object has been specified with exclusive mode for registerNotificationInterest.
Response: You must specify object(s) when using exclusive mode.

Cause: A wait mode is not allowed for getNotifications.
Response: Specify a poll mode (mode="poll").

Cause: The mode for getNotifications is invalid.
Response: Specify a poll mode.
ISS.1004.1037E The parameter 'mixed serial and time' is invalid.

Cause: The parameter contains mixed specifications of serial and time.
Response: Specify the parameters startSerial and endSerial or startTime and endTime.
ISS.1004.1041E The parameter 'endSerial' is invalid.

Cause: The ending serial number is invalid.
Response: Specify a value for endSerial that is greater than 0 and greater than or equal to startSerial.

ISS.1004.1050E The parameter 'invokeOperation.objectName' is invalid.

Cause: The invokeOperation must contain exactly one object.
Response: Invoke this operation with exactly one object.
ISS.1004.1052E The parameter '<paramName>' is invalid.

Cause: The supplied parameter does not match the signature of the operation.
Response: Invoke the operation with valid parameters that match the operation signature.
ISS.1004.1075E The parameter 'endTime' is invalid.

Cause: The end time is invalid.
Response: Specify a value for endTime that is greater than 0 and greater than or equal to startTime.
ISS.1006.1021E The attribute '<attribute>' is invalid.

Cause: This attribute does not exist.
Response: Request a valid attribute.
ISS.1006.1028E The attribute '<attribute>' is invalid.

Cause: This attribute is unreadable.
Response: Request a valid attribute. (Attributes vary by MBean. For more information, see the "webMethods
ISS.1007.1022E The attribute '<attribute>' is read-only.

Cause: This attribute cannot be changed.
Response: This attribute is read-only and cannot be changed.
ISS.1008.1019E There are no registered notification interests.

Cause: This notification interest does not exist.
Response: Specify a valid notification interest.

Cause: No notification interests are registered.
Response: Register a notification interest before calling getNotifications.


Cause: No notification interests are registered.
Response: Register a notification interest before calling registerNotificationListener.
ISS.1011.1012E The value '<value>' given for 'mode' is not a valid notification interest mode.
Cause: The mode for registerNotificationInterest is invalid.
Response: Specify the mode as either inclusive or exclusive.
ISS.1011.1024E The value '<value>' given for '<paramName>' is not a valid <type>.
Cause: The value of this parameter is an invalid character value.
Response: Specify a valid character string consisting of exactly one character.
Cause: The value of this parameter is an invalid date value.
Response: Specify a valid date value.
Cause: The value of this parameter is an invalid object name.
Response: Specify a valid object name.
Cause: The value of this parameter is an invalid number value.
Response: Specify a valid number value.
ISS.1011.1030E The value '<value>' given for '<param>' is not a valid <type>.
Cause: The value of this parameter is an invalid Boolean value.
Response: Specify a valid Boolean value.
ISS.1011.1041E The value '<value>' given for 'maxBatch' is not a valid batch size.
Cause: The value of the maxBatch parameter is invalid.
Response: Specify a non-negative integer value for maxBatch.

ISS.1011.1042E The value '<value>' given for 'startSerial' is not a valid serial number.
Cause: The starting serial number is invalid.
Response: Specify a value for startSerial that is greater than or equal to 0.
ISS.1011.1042E The value '<value>' given for 'startTime' is not a valid time.
Cause: The start time is invalid.
Response: Specify a value for startTime that is greater than 0.
ISS.1011.1047E The value '<value>' given for '<paramName>' is not a valid long.
Cause: This parameter has an invalid long value.
Response: Specify a valid long value.
ISS.1011.1048E The value '<value>' given for 'listener' is not a valid URL.
Cause: The notificationListener value is an invalid URL.
Response: The URL must be empty or start with "http:".
ISS.1011.1048E The value '<value>' given for 'maxBatch' is not a valid number.
Cause: The value of the maxBatch parameter is invalid because it contains characters that are not digits.
ISS.1011.1050E The value '<value>' given for 'startSerial' is not a valid serial number.
Cause: The starting serial number is invalid.
Response: Specify a value for startSerial that is greater than or equal to 0.
ISS.1011.1052E The value '<value>' given for 'maxBatch' is not a valid number.
Cause: The value of the maxBatch parameter is invalid because it contains characters that are not digits.
Cause: The invokeOperation contains an invalid parameter. There is an error in the array input value.
Response: Invoke this operation with a valid input array value parameter.

ISS.1011.1053E The value '<value>' given for 'maxBatch' is not a valid batch size.
Cause: The maxBatch parameter value is invalid.
ISS.1011.1061E The value '<value>' given for 'startSerial' is not a valid serial number within the notification range.
Cause: No notifications exist within the specified serial number range.
Response: Request notifications within a valid serial number range.
ISS.1011.1061E The value '<value>' given for 'startTime' is not a valid time within notification range.
Cause: No notifications exist within the specified time range.
Response: Request notifications within a valid time range.
ISS.1011.1077E The value '<value>' given for '<paramName>' is not a valid date.
Cause: This parameter has an invalid date value.
Response: Specify a valid date value.
ISS.1015.1060E The operation '<operationName>' is not available.

Cause: This operation does not exist on this object.
Response: Update the object so that the invoked operation exists on the object. (For more information, see the
"webMethods Manager Server Programmer's Guide.")
ISS.1100.1099E The protocol version <version> is not supported by the implementation.

Cause: The OMI version is invalid.
Response: Connect using a valid OMI version. (For Manager Server 6.0.1, the only valid OMI version is OMI
1.0.)
ISS.1100.1099E The protocol version <version> is not supported by the implementation.

Cause: The version of omiHeader.version is invalid.
Response: Specify a valid version in OmiHeader.version. For more information, see the "webMethods Manager
Server Programmer's Guide."
ISS.1102.1011E Permission is denied for the requested command '<command>'.

Cause: The command cannot be executed using the Access Control List, user name, or password provided.
Response: Make sure that the ACL and the username/password are set correctly for this service.

ISS.1102.1011E Permission is denied for the requested command '<command>'.

Cause: The command cannot be executed using the Access Control List, user name, or password provided.
Response: Make sure that the ACL and the username/password are set correctly for this service.
ISS.1104.1001E The element 'xml' has an invalid format.

Cause: The format of the parseCommand element is invalid or is missing XML.
Response: Use valid XML for the parse command.
ISS.1104.1004E The element '<element>' has an invalid format.

Cause: This element has an invalid format. The requested value in getString is not a string.
Response: Specify a valid string value.

Cause: This element has an invalid format. The requested value in getStringArray is not an array of strings.
Response: Specify a valid string array value.

Cause: This element has an invalid IData value.
Response: Specify a valid IData value.

Cause: This element has an invalid IData array value.
Response: Specify a valid IData array value.

Cause: This element has an invalid IData array value.
Response: Specify a valid IData array value.

Cause: This element has an invalid array value.
Response: Specify a valid array value.

ISS.1104.1099E The element 'omiHeader' has an invalid format.

Cause: The format of omiHeader is invalid.
Response: Specify IData for omiHeader. For more information, see the "webMethods Manager Server
Programmer's Guide."
ISS.1104.1099E The element 'omiHeader.version' has an invalid format.

Cause: The format of omiHeader.version is invalid.
Response: Specify a valid version in OmiHeader.version. For more information, see the "webMethods Manager
Server Programmer's Guide."
ISS.1105.1003E The required element '<element>' is missing from the XML request.
Cause: The XML request is missing a required element.
Response: Specify a valid element in the command.
ISS.1105.1008E The required element 'Body.[command]' is missing from the XML request.
Cause: The XML request is missing a required command.
Response: Provide a command in the OMI request.
ISS.1105.1008E The required element 'Body.[command]' is missing from the XML request.
Cause: The required element "command" is missing from the SOAP-ENV:Body section in the XML request.
Response: Specify a command within the SOAP-ENV:Body section of the request.
ISS.1105.1008E The required element 'SOAP Envelope' is missing from the XML request.
Cause: The required element "SOAP envelope" is missing (no IData representing the SOAP envelope was
found) or the element contains invalid IData.
Response: Specify a valid SOAP envelope. The envelope must contain IData.
ISS.1105.1008E The required element 'SOAP-ENV:Envelope' is missing from the XML request.
Cause: The required element "SOAP-ENV:Envelope" is missing from inside the SOAP envelope.
Response: Specify a valid SOAP envelope, which must contain the value "SOAP-ENV:Envelope".

ISS.1105.1008E The required element 'SOAP-ENV:Envelope' is missing from the XML request.
Cause: The required element "SOAP-ENV:Envelope" is missing (no IData representing the SOAP-
ENV:Envelope was found) or the element contains invalid IData.
Response: Specify a valid SOAP-ENV:Envelope, which must contain IData.
ISS.1106.1009E The request '<command>' is not a valid command.

Cause: This command does not exist.
Response: Request a valid OMI command. (For more information, see the "webMethods Manager Server
ISS.1106.1009E The request '<command>' is not a valid command.

Cause: The requested command does not exist.
Response: Request a valid OMI command. (For more information, see the "webMethods Manager Server
ISS.1113.1059U Busy Exception

Cause: An error occurred while retrieving notifications because the interest list was unavailable.
Response: Restart Manager Server. If this does not correct the error, contact webMethods Customer Care for
assistance.
ISS.2001.1101E Port out of range

Cause: The specified port is invalid.
Response: Specify a port between 0 and 65534.

ISS.2001.1102E Empty hostname

Cause: No host name is specified.
Response: Specify a host name.


ISS.2001.1107E Unknown host name

Cause: The host name cannot be found in DNS.
Response: Verify that the host name specified is recognized by the local name server.
ISS.2001.1107E Unknown hostname

ISS.2001.1112E Encryption strength out of range

Cause: The encryption strength value entered to verify SSL encryption strength is invalid.
Response: Change the encryption strength to a value greater than zero.
ISS.2001.1113E Encryption strength out of range

Cause: The encryption strength value entered is invalid.
Response: Change the encryption strength value. Valid values are 0, 40, or 128.
ISS.2001.1114E active search

Cause: A search is in progress. You cannot start another search until the current search completes.
Response: Wait until the current search is complete. Then, start another search.
ISS.2001.1116E Certificate files are not supported

Cause: Manager Server cannot verify the certificate file because SSL encryption is not enabled on the Broker.
Response: Configure the Broker for SSL encryption.
ISS.2001.1117E Certificate files are not supported

Cause: Manager Server cannot verify the certificate file because SSL encryption is not enabled on the Broker.
Response: Configure the Broker for SSL encryption.

ISS.2001.1121E Certificate file not found

Cause: The certificate file cannot be found on the file system.
Response: Re-enter the location of the certificate file.
ISS.2001.1122E Certificate file is not readable

Cause: The certificate file is not readable.
Response: Change permissions on the certificate file.
ISS.2001.1201E Empty search_name

Cause: No search name was specified.
Response: Specify a search name.

Cause: No search name is specified.
ISS.2001.1202E Empty start_address

Cause: No start address was specified.
Response: Specify a start address.

Cause: No start address is specified.
ISS.2001.1205E Invalid network address

Cause: The network address is not in the correct format.
Response: Specify an IP address in the format x.x.x.x.


ISS.2001.1206E Different class C networks

Cause: The start and end addresses must be on same subnet.
Response: Re-enter the start and end addresses.

ISS.2001.1206E end_address is less than start_address

Cause: The end address is less than the start address.

ISS.2001.1208E search_name exists

Cause: A search already exists with the specified name.
Response: Enter a different search name.

Cause: A search name already exists with the specified name.

Cause: No search name was specified.
ISS.2001.1302E Empty host_name

Cause: No host name was specified.

ISS.2001.1303E Invalid port number

Cause: An valid port number was specified.

Response: Verify the host name specified is recognized by the local name server.
ISS.2001.1305E Invalid maximum_gateway_hops number

Cause: The hop count exceeds the maximum.
Response: Specify a lower maximum hop count. The maximum number of gateway hops is determined by an
operating system setting.
ISS.2001.1401E search_name not found

Response: Delete the old search and recreate it.
ISS.2002.1001E No connection to Broker Server

Cause: A Broker Server connection is not available to set the license key.
Response: Make sure that the Broker Server is operational.

Cause: A Broker Server connection is not available to set the managed object description.

Cause: A Broker Server connection is not available to obtain Broker statistics.

Cause: A Broker Server connection is not available to obtain system statistics.


Cause: A Broker Server connection is not available to obtain SSL status.
ISS.2002.1007E No permission to access Broker Server

Cause: Manager Server was denied access to stop the Broker Server.
Response: Resolve permissions for the Broker.
ISS.2002.1009E No connection to broker server

Cause: A Broker connection is not available to stop the Broker Server.
Response: Make sure that the Broker is operational.
ISS.2003.1001E No connection to Broker

Cause: Manager Server is trying to set the object description for the Broker MBean, but there is no connection to
the Broker.
Response: Make sure that the Broker is operational before calling this operation.

Cause: Manager Server is trying to obtain Broker statistics, but there is no connection to the Broker.

Cause: Manager Server is trying to obtain territory statistics, but there is no connection to the Broker.

Cause: Manager Server is trying to obtain gateway statistics, but there is no connection to the Broker.
ISS.2003.1002E No connection to broker

Cause: A Broker connection is not available to get client statistics for custom adapter.


Cause: A Broker connection is not available to obtain client statistics for the enterprise adapter.
ISS.2003.1002E Unknown client name

Cause: Broker Server did not recognize the client name provided by Manager Server.
Response: Provide the correct client name.

Cause: Manager Server is trying to manage a custom adapter, but the client name cannot be found.
ISS.2003.1005E Client group name is empty

Cause: The client group is empty, so the custom adapter cannot be managed.
Response: Provide the correct client group name.
ISS.2003.1005E Client group name is empty

Cause: Manager Server is trying to stop managing a custom adapter, but the client group name is empty.
Response: Provide a client group name.
ISS.2003.1005E Client name is empty

Cause: Manager Server is trying to manage a custom adapter but the client name is missing.
Response: Provide a client name.
ISS.2003.1005E Client name is empty

Cause: The client name for the custom adapter is null or empty.
ISS.2003.1005E Unknown client group name

Cause: Manager Server is trying to stop managing a custom adapter, but no custom adapter is associated with
the client group.
Response: Provide the correct client group name.


Cause: No custom adapter is associated with this client name.
ISS.2003.1007E Cannot access client name

Cause: Manager Server is trying to manage a custom adapter, but the Broker does not have permissions to
access the client.
Response: Provide the Broker with the necessary permissions.
ISS.2003.1008E Cannot access client name

Cause: Manager Server was denied access to the custom adapter client while attempting to stop the custom
adapter.
Response: Resolve permissions for the client group list on the Broker for the custom adapter client.

Cause: Manager Server is trying to manage the custom adapter, but there is no connection to the Broker.

Cause: A Broker connection is not available to stop the custom adapter.
ISS.2003.1011E Custom adapter already managed

Cause: Manager Server is trying to manage a custom adapter that is being managed already.
ISS.2003.1011E Custom adapter already managed

Cause: Manager Server is trying to manage a custom adapter that is being managed already.
ISS.2003.1011E Custom adapter client group already managed

Cause: Manager Server is trying to manage the custom adapter, but the client group is being managed already.


Cause: Manager Server is trying to manage the custom adapter client group, but there is no connection to the
Broker.

Cause: A Broker connection is not available to save the infoset.



Response: Verify the host name specified is recognized by the local name server.



Cause: The address is not in the correct format.




Cause: A search name already exists with the specified name.
ISS.3002.1210E Out of range value for port

ISS.5200.1101E failed to establish db connection

Cause: Manager Server cannot connect to the log database.
Response: Check that the log server information is correct and that the database is accessible from the Manager
Server host.
ISS.5200.1101E failed to establish db connection

Cause: Manager Server cannot connect to the model database.
Response: Check that the model database information is correct and that the database is accessible from the
Manager Server host.
ISS.5200.1101E Unknown host name: <logServer>

Cause: Manager Server cannot resolve the host name for the log server.
Response: Make sure that the log server name is correct and can be resolved by DNS.
ISS.5200.1101E Unknown host name: <modelServer>

Cause: Manager Server cannot resolve the host name for the model server.
Response: Make sure that the model server name is correct and can be resolved by DNS. (For more information
about this server, see the "webMethods Manager Server Administrator's Guide.")

ISS.5200.1102E Invalid db connection parameters [<exception>]

Cause: The database profile contains invalid connection information or the database is unavailable.
ISS.5200.1103E failed to establish db connection [<exception>]

Cause: The database profile has problems or an internal error has occurred.
ISS.5200.1104E resource already managed

Cause: The resource is already being managed. Therefore, Manager Server could not delete it.
Response: Stop managing the resource and then manage the resource again. If this does not work, restart the
server and then try stopping and managing the resource again.
ISS.5200.1104E resource already managed

Cause: The resource is already being managed. Therefore, Manager Server could not delete it.
Response: Stop managing the resource and then manage the resource again. If this does not work, restart the
server and then try stopping and managing the resource again.
ISS.5200.1106E resource struct not found

Response: Delete the business process and rediscover it.



ISS.7001.1107E Unknown hostname







Cause: A search already exists with the specified name.
ISS.7001.1210E Out of range value for port


ISS.7002.1007E Servers start failed

Cause: The Workflow Servers failed to start.
Response: Check the Workflow Server Manager log for more information about what prevented the Servers
from starting, and then restart the Workflow Server Manager.
ISS.7002.1008E Servers stop failed

Cause: The Workflow Servers failed to stop.
Response: Check the Workflow Server Manager log for more information about what prevented the Servers
from stopping, and then stop the Workflow Server Manager manually.
ISS.7003.1007E Server start failed

Cause: The Workflow Server failed to start.
Response: Use the Workflow Administrator to check the Workflow Server log for more information about what
prevented the Server from starting, and then restart the Server.
ISS.7003.1008E Server stop failed

Cause: The Workflow Server failed to stop.
Response: Use the Workflow Administrator to check the Workflow Server log for more information about what
prevented the Server from stopping, and then stop the Server.

CHAPTER 11
webMethods Portal
POP.001.0002 A "<errorCode>" occurred with the Message "<messageText>".

Cause: An unexpected error occurred during deployment.
Response: Examine the logs, and optionally try again. The log file in question is the install.log. Look for the
information specific to the deployed component.
POP.002.0004 Context is in an invalid state.

Cause: The server attempted to use an invalid Portal context object. This error is the result of attempting to use
a Portal context object before it has been initialized or after it has been uninitialized.
Response: Always use the com.webmethods.portal.bizPolicy.IContextProvider (available through the
com.webemethods.portal.system.PortalSystem) to acquire a Portal context object.
POP.002.0005 Unable to locate command: <commandName>

Cause: The requested portal command is not deployed on the Portal server.
Response: Use the Install Administration portlet to deploy the portal command to the Portal server.
POP.002.0006 Unable to locate biz policy for resource: <itemName>

Cause: The server cannot resolve the business policy for the specified resource because no policy has been
registered for the resource type.
Response: Create and register a business policy for the resource type. Consult the "webMethods Portal Design
Guide" to learn more about business policies.

C H A P T E R 11 w e b M e t h o d s P o r t a l
POP.002.0007 Unknown error encountered while trying to resolve business policy for uri <uriName>
Cause: The server cannot resolve a business policy for specified resource because of an internal Portal error.
Response: Check the _problems_.log in the Portal's current logging directory for more specific error
information.
POP.002.0008 Uri is not a valid thingID: <itemName>

Cause: The server cannot the invoke RemoveAcess command on a resource that is not a metadata resource.
Response: Correct the command-invoking source code to specify a metadata resource using either the
'resourceURI' parameter or the Portal context's current resource.
POP.002.0012 Class group name is not specified

Cause: Must specify groupName parameter when invoking ReloadClasses command.
Response: Correct the command-invoking code to specify 'groupName' parameter. The parameter value
should be the name of the group's class-loader bundle.
POP.002.0014 Unable to authenticate user: <userName>

Cause: The server cannot authenticate the user either because the user does not exist or because the user's
password is incorrect.
Response: Try again with correct username and password. If necessary, use the User & Group Management
portlet to add the user to the Portal server
POP.002.0015 Error getting style for user: <userName>

Cause: An error occurred while looking up the user's Portal skin, likely because the user's Portal skin data has
become corrupted.
Response: Reset the user's Portal skin to the default value by invoking the SetPortalStyle command with the
following parameters: userURI=[userID], resourceURI=null. You can invoke a command by entering the base
Portal URL (that is, 'http://myportal/') in your browser's Address bar and appending
'?command=SetPortalStyle&userURI=[userID]&resourceURI='.

POP.002.0016 Error listing directory groups
Cause: The server cannot list the groups of a particular directory service, most likely because of a problem
connecting to the directory service.
Response: If the directory service is a freshly configured directory service, go back to the Portal Admin
Dashboard, and double-check the configuration using the Directory Service Administration portlet (in the
Portal Configuration category). If the directory service is an existing directory service for which groups could
be listed previously, validate that the LDAP or ADSI server to which the directory service is connected is up
and running properly. Also check that the machine which hosts the Portal server is able to connect to the
LDAP or ADSI server using the hostname and port specified in the directory service's configuration.
POP.002.0017 Error retrieving template list

Cause: The server cannot list directory service templates, because an error occurred loading the templates.
information.
POP.002.0018 Error listing users

Cause: The server cannot list the users of a particular directory service, most likely because of a problem
connecting to the directory service.
POP.002.0019 Error updating directory

Cause: The server cannot update the directory service configuration because an error occurred in validating or
storing the configuration settings.
information.
POP.002.0021 Cannot resolve install mechanics for: <uriName>

Cause: An error occurred during the installation of a portal component.
Response: Look in the _problems_.log file for the stack trace of the error. The stack trace may not provide
enough detail to say why the error was thrown, but it will show where the error originated.

POP.002.0025 Command name is not specified

Cause: The Ant build file does not contain the command name needed to invoke the ExecuteCommand ant
task.
Response: Correct the Ant build file to provide the command name using the 'name' attribute of the
ExecuteCommand task.
POP.002.0026 Cannot resolve command [name, type] [<commandName>, <typeName>]

Cause: The server cannot execute the command by means of an Ant task because the specified command has
not been deployed to the Portal.
Response: Deploy the command specified by the error message.
POP.002.0027 Attribute target is required

Cause: The target for invoking the ExecuteTargetLoop Ant task has not been specified.
Response: This error may occur if a developer modifies an Ant build file used to deploy comments to the
Portal. Correct the Ant build file to add a 'target' attribute to the ExecuteTargetLoop task invocation.
POP.002.0028 Cannot create IInitializableComponentData from: <configData>

Cause: The component configuration data is not one of the following types: xml (serialized XML document),
xmlLocation (url specifying XML document), properties (serialized properties map), propertiesLocation (url
specifying properties file location).
Response: Correct the component configuration in the phaseProvider.xml configuration file to specify
component configuration data as either xml, xmlLocation, properties, or propertiesLocation.
POP.002.0029 Attribute source is required

Cause: The server cannot execute an Ant task because the task requires a source attribute to be specified.
Response: Correct the Ant build file to add a 'src' attribute to RunJavaScript and RunSQLScript tasks. The 'src'
attribute should specify the file path to the script to be run.
POP.002.0030 Cannot create IInitializableComponentData from <configData> for provider <providerName>

Cause: The server cannot unregister the specified component. The component's configuration data has become
corrupted.
Response: Reinstall the component. Then try uninstalling the component.

POP.002.0032 Cannot get IComponentData for component <componentName> from provider <providerName>
Cause: An error occurred during the unregistration of a portal component.
enough detail to say why the error was thrown, but it will show where the error originated. It is likely that you
need to restart the Portal server.
POP.002.0033 Component Provider not found: <providerName>

Cause: The server cannot unregister the component because component data has become corrupted.
Response: Re-install component (using the Install Administration portlet), then try uninstalling.
POP.002.0034 Attribute descriptorSrc is required

Cause: The Ant task does not have skin descriptor content.
Response: Correct the Ant build file to provide skin descriptor content using the 'descriptorSrc' attribute to
CreateSkinInstance, GetSkinInfo, and RemoveSkinInstance Ant tasks.
POP.002.0035 Skin name is empty

Cause: The server cannot determine the skin name because the skin descriptor does not contain the skin name
or because the skin descriptor is improperly structured.
Response: Fix the skin descriptor to include the skin name in the 'name' attribute value of the 'wm_xt_skin'
element.
POP.002.0036 Portlet info is not specified

Cause: Portlet descriptor content is not included in the GetPortletInfo Ant task.
Response: Correct the Ant build file to provide portlet descriptor content using the 'descriptorSrc' attribute.
POP.002.0037 Portlet name is empty

Cause: The server cannot determine the portlet name because the portlet descriptor does not contain the portlet
name or because the portlet descriptor is improperly structured.
Response: Using the Portlet Developer, correct the portlet descriptor to include the portlet name as the content
of the 'name' element.
POP.002.0038 Portlet is not available: <portletName>

Cause: The specified portlet is not deployed on the Portal server.
Response: Use the Install Administration portlet to deploy the portlet specified by the error message.

POP.002.0040 Cannot find system folder for the portlet: <portletType>

Cause: An error occurred during installation of a portlet.
Response: Look in the _problems_.log file for the stack trace of the error. It may be necessary to reinstall the
component.
POP.002.0042 Destination container is not a valid thing: <itemName>

Cause: The server cannot clone a remote resource because the resource must be cloned to a metadata
destination container.
Response: Correct the command-invoking source code to specify a metadata destination container using the
'destContainerURI' parameter.
POP.002.0043 Source item container is not a valid thing: <itemName>

Cause: The server cannot clone the remote resource because only metadata resources can be cloned.
POP.002.0044 Invalid XType: <itemName>

Cause: The server cannot resolve the DBO type of the remote item to be cloned. The likely reason is that the
DBO type has been uninstalled from the system.
Response: Normally, a DBO type cannot be uninstalled from the system until all instances of the type have
been deleted. The remote item is in a damaged state, and you can't clone (or even recover) the item.
POP.002.0046 Item is not a valid thing: <itemName>

Cause: The server cannot invoke the metadata command because the command must be invoked against a
metadata resource.
POP.002.0048 Delete operation failed

Cause: Cannot delete container because at least one of the contained items cannot be deleted. The list of
contained items that cannot be deleted should be displayed in the UI along with this message.
Response: Attempt to delete the specified undeletable contained items individually for more detailed
information as to why the items cannot be deleted.

POP.002.0049 Error obtaining owned folder
Cause: The server cannot obtain the owned folder because of an internal Portal error.
information.
POP.002.0050 Cannot get current resource uri

Cause: Cannot invoke portlet command because the portlet against which to invoke the command is not
specified.
Response: Correct the command-invoking code to specify the portlet via either the 'resourceURI' parameter or
via the Portal context's current resource.
POP.002.0051 ResourceURI is not specifed

Cause: The server cannot invoke the portlet command because the portlet against which to invoke the
command is not specified.
Response: Correct the command-invoking source code to specify the portlet using either the 'resourceURI'
parameter or the Portal context's current resource.
POP.002.0052 PortletBean is not ICommandBean

Cause: The command cannot be invoked against the portlet, because the portlet's portlet-bean does not
implement the com.webmethods.portal.bizPolicy.command.ICommandBean interface.
Response: In the Portlet Developer, modify portlet's portlet-bean source code to make the portlet-bean
implement ICommandBean. Rebuild and redeploy the portlet.
POP.002.0053 UserID is not of type IThingID or String

Cause: The command was invoked via RMI with an inappropriate userID data type. This error is usually a
result of a bug in the command-invoking code.
Response: Correct the command-invoking code to ensure it invokes the command with a userID specified
either as a java.lang.String or a com.portal.webmethods.meta2.thing.IThingID object.
POP.002.0054 Search library not found: <libraryName>

Cause: An attempt was made to delete a search library that does not exist.
Response: Use the Search Admin portlet to check the name of the search library against the available libraries
on the Portal server.

POP.002.0056 Saved Searches folder not found

Cause: The server cannot save a search because the user's saved-searches folder does not exist.
Response: User folders such as the user's saved-searches folder are created automatically for users when they
login to the Portal. Try logging out as the user, and then logging in again.
POP.002.0057 No name parameter found

Cause: The server cannot invoke the save-search command name. Because the command does not specify a
name parameter.
Response: Correct the command-invoking source code to specify a 'name' parameter.
POP.002.0058 Not a valid skin: <itemName>

Cause: The server cannot invoke the ReloadSkin command because the specified skin identifier does not
identify a valid skin.
Response: Correct the command-invoking source code to specify a skin resource using the 'skin' parameter.
POP.002.0059 Default xmlimport requires an IThingID for the parent: <itemName>

Cause: The server cannot import a metadata resource using xmlImport unless the parent of the resource is also
a metadata resource.
Response: Correct the xmlImport file to move or remove elements contained by the element specified by the
error message.
POP.002.0061 Unable to locate acl for aclName: <aclName>

Cause: The server cannot modify the access control list (acl) for a resource specified in xmlImport because the
access control list was referenced by an alias that does not exist.
Response: Correct the xmlImport file to not use the 'aclName' attribute value specified by the error message.
POP.002.0062 Unable to find value for acl

Cause: The server cannot create an access control entry using xmlImport because the acl element requires a
value attribute.
Response: Correct the xmlImport file to add a 'value' attribute to 'acl' elements. The 'value' attribute values
should contain known Portal access right names. These values are defined in the 'rightNames.properties'
Portal configuration file.

POP.002.0063 Unable to find ace value for: <accessRightName>
Cause: The server cannot create access an control entry using xmlImport because the xmlImport entry
references an unknown right value.
Response: Correct the xmlImport 'acl' or 'ace' element 'value' attributes to use known Portal access right values.
These values are defined in the 'rightNames.properties' Portal configuration file.
POP.002.0065 Alias attribute missing on context node

Cause: The server cannot establish the resource context during xmlImport because the context element requires
an alias attribute.
Response: Correct the xmlImport file to add an 'alias' attribute to 'context' elements. The alias attribute value
should contain the name of a Portal alias; elements enclosed by the context apply to the resource identified by
this alias.
POP.002.0069 Root users folder not found

Cause: The server cannot create the user's home folder because the Portal users folder does not exist.
Response: Create a Portal folder, and set its alias to 'folder.users'.
POP.002.0076 The basic update properties requires a thingID: <itemName>

Cause: The server cannot invoke the ImportFiles command because it does not specify a folder in which to
import.
Response: Correct the command-invoking source code to specify a folder using either the 'resourceURI'
parameter or the Portal context's current resource.
POP.002.0077 Adding to version control requires a thingID: <itemName>

Cause: The server cannot invoke the version-control command without specifying a versionable resource.
Response: Correct the command-invoking source code to specify a versionable resource using either the
POP.002.0078 The resource does not support IVersionableMechanics: <itemName>

Cause: The server cannot invoke the version-control command on the resource because the resource is not
versionable.
Response: Do not invoke the AddToVersion command against resources that are not versionable. Only Portal
folders and Portal content items are versionable.

POP.002.0079 Command requires a thingID: <itemName>

Cause: The server cannot invoke the version-control command without specifying a versionable resource.
Response: Correct the command-invoking source code to specify a versionable resource using either the
POP.002.0080 Invalid version Uri: <resourceURI>

Cause: The server cannot display the Portal version information of an item because the identifier used to
specify the version is not a valid version identifier.
Response: Correct ViewVersion command-invoking source code to provide a valid version identifier.
POP.002.0081 Invalid thing ID: <itemName>

Cause: The server cannot display the Portal version information of an item because the identifier used to
specify the item does not identify a valid resource
Response: Correct the command-invoking source code to provide a valid versioned-item identifier for the
'targetURI' parameter.
POP.002.0083 Could not acquire context, principal data not found on session
Cause: The server cannot create a Portal context for the specified javax.servlet.http.HttpSession because the
HttpSession has not been initialized with the necessary Portal session data.
Response: Restart the Portal server.
POP.002.0085 Can't create subscription for non Thing: <itemName>

Cause: The server cannot create a subscription from xmlImport data because subscriptions can be created only
to metadata resources.
Response: Correct the xmlImport file to remove 'subscription' elements from non-metadata resource contexts.
The best way to figure out specifically which subscription elements in the xmlImport file that cause this error
is the trial-and-error approach: remove each subscription element in the xmlImport file one by one and try re-
importing from the xmlImport file.
POP.002.0086 Unable to import xml. No uid.

Cause: An attempt to create an access control entry or subscription using xmlimport did not specify the uid of
the Portal user or group.
Response: Correct the xmlImport file to add a 'uid' attribute to 'subscription' and 'ace' elements. The 'uid'
attribute value should contain the uid (LDAP user ID) of a valid Portal user or the cn (LDAP group ID) of a
valid Portal group.

POP.002.0087 Unable to import xml. Could not acquire uri for uid: <userName>
Cause: The user referenced in the xmlImport file does not exist on the Portal server.
Response: Use the User & Group Management portlet to add the user to the Portal server, or change the
xmlImport file.
POP.002.0089 Unable to import subscription. No value specified for 'deliveryMode'.

Cause: The server cannot create a subscription from xmlImport data because the subscription element requires
a deliveryMode attribute. This error is caused by importing from an improperly constructed xmlImport file.
Response: Correct the xmlImport file by adding a 'deliveryMode' attribute to 'subscription' elements.The
deliveryMode attribute value must be either 'portal' (Portal inbox), 'email' (email), or 'portal,email' (both Portal
inbox and email).
POP.002.0090 Unable to import subscription. No value specified for 'criteria'.

Cause: The server cannot create the subscription from xmlImport data because the subscription element
requires a criteria attribute containing the name of at least one criterion valid for the type of resource
subscribed to.
Response: Correct the 'subscription' elements in the xmlImport file so that they all contain valid 'criteria'
attribute values. Valid values are not empty; they should contain a comma-separated list of criterion names.
The criterion names for basic folders are: 'added', 'removed', 'modified', 'deleted', and 'moved'. The criterion
names for basic links, forms, portlets, and content items are 'modified', 'deleted', and 'moved'. Custom DBO
types may have additional criteria.
POP.002.0091 No matching criteria found for type: <resourceTypeName> and for criteria: <criterionName>.
Cause: The server cannot create a subscription from xmlImport data because the subscription element requires
a criteria attribute containing the name of at least one criterion valid for the type of resource subscribed to.
Response: Correct the xmlImport file so that 'subscription' elements contained by any element of the type
specified by the error message's <resource-typeName> have valid 'criteria' attribute values. Valid values are
not empty; they should contain a comma-separated list of criterion names. The criterion names for basic
folders are: 'added', 'removed', 'modified', 'deleted', and 'moved'. The criterion names for basic links, forms,
portlets, and content items are 'modified', 'deleted', and 'moved'. Custom DBO types may have additional
criteria.
POP.002.0092 Can't set ace for non Thing: <itemName>

Cause: The server cannot modify the access control entry (ace) for a resource specified in xmlImport because
the resource does not support Portal access control entries.
Response: Correct the xmlImport file to remove the 'ace' element for the resource specified by the error
message.

POP.002.0093 Unable to locate alias for: <aliasName>

Cause: The server cannot establish the resource context during xmlImport because the alias specified for the
context does not exist.
Response: Use the Alias Administration portlet to create the alias specified by the error message or fix the
xmlImport file to use an alias that does exist. To fix the xmlImport file, locate the alias attribute with the value
specified by the error message and replace that value with the name of an existing alias.
POP.002.0096 Mechanics is not an IBasicMechanics

Cause: The server cannot use xmlImport to update the properties of a resource that is not a metadata resource.
Response: Correct the xmlImport file to not update the properties of non-metadata resources. The best way to
figure out specifically which element in the xmlImport file that this error is caused by is the trial-and-error
approach: remove each element in the xmlImport file one-by-one and try re-importing from the xmlImport
file.
POP.002.0097 Unable to complete import because type: <typeName> doesn't exist.

Cause: The server cannot import a resource specified in xmlImport because the resource is an instance of a
DBO that is not currently deployed in the Portal.
Response: Deploy the DBO specified by the error message and then rerun the xmlImport.
POP.003.0003 No access model specified in property "<propertyName>".

Cause: The framework.access.model system property does not specify an access model.
Response: Update portal.properties file to specify framework.access.model property value. The choices are
'permissive' or 'restrictive.'
POP.003.0004 Unable to register principal types: "<number>".

Cause: The system directory is corrupted.
Response: Restore the underlying system user directory content from a backup or do so manually. In the case
of LDAPd, you can reinstall the LDAPd server using the webMethods Installer.
POP.003.0005 Unable to register search service: "<searchServiceName>".

Cause: An error occurred in registering a new search service.
Response: You may need to reinstall the Portal server.

POP.003.0006 Error initializing content service: "<contentServiceName>".
Cause: The content service cannot be initialized.
Response: Check the Content Service Administration portlet to verify that the content service is properly
configured.
POP.003.0007 Cannot list roles, directory service "<directoryserviceName>" not found.

Cause: The directory service cannot be found.
Response: Check the Directory Service Administration portlet to verify that the directory service is properly
configured and functional.
POP.003.0008 Could not locate system directory: "<directoryName>".

Cause: The server cannot find the 'system' user directory.
Response: Verify that the 'system' directory is present in Directory Services Administration portlet, and that it
is configured and functional.
POP.003.0009 Error setting system directory: "<directoryName>".

Cause: The command failed to change the system directory service.
Response: Do not attempt to change the system directory.
POP.003.0012 <userName> does not have permission to modify the Administrators group.
Cause: The user does not have appropriate access rights.
Response: Use item's 'Permissions' local menu item that opens up the Permissions portlet to give the user
access rights.
POP.003.0013 <userName> does not have permission to modify the directory configuration.
access rights.
POP.003.0014 Cannot update directory config, domain not found: "<domainName>".

Cause: Attempt to update the config information for a directory service using an invalid domain name
Response: Use a valid domain name.

POP.003.0015 Cannot update directory config, Administrator user not found: "<userDn>".
Cause: The system directory or the database is corrupted.
POP.003.0016 Cannot update directory config, Everyone group not found: "<groupDn>".
Cause: The system directory does not have an 'everyone' group or the directory is corrupted.
POP.003.0017 Cannot update directory config, Guest user not found: "<userDn>".
POP.003.0018 Cannot remove the system directory.

Cause: The system directory services cannot be removed.
Response: Do not try to remove the system directory.
POP.003.0021 System directory does not have Administrator user.

Cause: The LDAP user store is missing the administrator user.
Response: Add a user to the system LDAP user store whose UID matches the Portal Administrator UID. This
should only be necessary if the LDAP user store has become corrupted or the PortalAdmin user has been
removed.
POP.003.0022 System directory does not have Everyone group. Everyone group access will not be available.
Response: Restore or create the Everyone group in the underlying directory that is configured as the system
directory. Use the directory's administration UI or tools for that purpose.
POP.003.0023 System directory does not have Guest user. Guest access will not be available.
Cause: The system directory either does not have a guest user or it is corrupted.

POP.003.0024 The type "<portletType>" is 'disabled'. Please contact the Portal Administrator.
Cause: An attempt was made to view a portlet for which the status has been set to 'disabled.'
Response: Use the Manage Components portlet in the Administration Dashboard to change the status of the
portlet type.
POP.003.0025 <userName> cannot view the content of <itemName>.

Cause: User is denied access to view a portal item
Response: Use the Permissions page to set the authentication scheme for the item to one of the installed
authentication schemes.
POP.003.0026 <userName> cannot list the shortcuts to <itemName>.

access rights.
POP.003.0027 <userName> cannot list the notes for <itemName>

access rights.
POP.003.0028 <userName> cannot view the access list for <itemName>

access rights.
POP.003.0029 <userName> cannot view the authentication scheme for <itemName>

access rights.
POP.003.0030 <userName> cannot create an item of type <typeName>.

access rights.

POP.003.0031 <userName> cannot update the content of <itemName>.

access rights.
POP.003.0032 <userName> cannot add the note for <itemName>

access rights.
POP.003.0033 <userName> cannot remove the note for <itemName>

access rights.
POP.003.0034 <userName> cannot update the properties of <itemName>

access rights.
POP.003.0035 <userName> cannot delete <itemName>

access rights.
POP.003.0037 <userName> cannot destroy <itemName>.

access rights.
POP.003.0039 <folderName> cannot contain a duplicate reference to <itemName>.

Cause: You cannot create items with the same name under the same folder.
Response: When naming items in a folder, make sure each has a name that is unique within the folder.

POP.003.0040 Cannot uninstall "<componentName>" because it has "<number>" published instances. Please delete them
first and try again.
Cause: The DBO cannot be uninstalled because it has published instances.
Response: Manually delete all published instances of this DBO and try to uninstall it again. You can use Publish
History portlet to help you find all published instances.
POP.003.0044 <itemName> is checked out.

Cause: The item cannot be checked out because it is already checked out.
Response: Wait until the item is checked in and try again.
POP.003.0045 <itemName> is not versioned.

Cause: The item is not versioned.
Response: Add the item to version control using the item's local menu.
POP.003.0047 <userName> cannot list the versions of <itemName>

access rights.
POP.003.0048 <userName> cannot add to versioning <itemName>.

access rights.
POP.003.0050 <itemName> is checked out by <userName>

Cause: The item cannot be checked out because it is already checked out.
Response: Wait until the item is checked in and try again.
POP.003.0051 <userName> cannot set the current version of <itemName>

access rights.

POP.003.0052 <userName> cannot publish a version of <itemName>.

access rights.
POP.003.0053 <userName> cannot check out <itemName>

access rights.
POP.003.0054 <itemName> is not checked out.

Cause: You cannot check the item in because it is not checked out.
Response: Do not attempt to check in the item.
POP.003.0055 <userName> cannot check in <itemName>.

access rights.
POP.003.0056 <userName> cannot undo the check out of <itemName>

access rights.
POP.003.0057 Source branch is not found: "<resourceURI>".

Cause: The server cannot find a source version branch for this object.
Response: Do not try to add this object to version control.
POP.003.0059 <itemName> cannot be added to versioning because parent is null.

Cause: The item is invalid because it does not have a parent.
Response: Use the local item menu to delete the item.

POP.003.0060 Not initialized: call init(PageData) first.
Response: Try the operation again.
POP.003.0061 Column must be contained by a row.

Cause: The page data xml is not valid. The column element must be inside a row element.
Response: If you're using the Portal UI and get this message, the portal page data has been corrupted. Try to
edit and then save the page. If you cannot load the page into the page editor you will need to delete the page
and then recreate it from scratch.
POP.003.0062 Property must be contained by a portlet.

Cause: The page data xml is not valid. The property element must be inside portlet element.
POP.003.0063 Portlet must contain 'uri' attribute.

Cause: The page data xml file is not valid. The portlet definition does not have 'uri' attribute.
POP.003.0064 Property must contain 'name' attribute.

Cause: The page data xml is not valid. The property element must have 'name' attribute.
POP.003.0065 Wiring must be contained by a portlet.

Cause: The page data xml is not valid. The property element must be inside portlet element.

POP.003.0066 Wiring must contain 'name' attribute.

Cause: The page data xml is not valid. The wiring element must have 'name' attribute.
POP.003.0067 Wiring must contain 'portlet' attribute.

Cause: The page data xml file is not valid. The wiring definition does not have 'portlet' attribute.
POP.003.0069 The content service "<serviceName>" is not available. Please contact the Portal Administrator.
Cause: The server failed to update the contents of a file that was saved to the portal.
Response: Ensure that the location being used for the portal content repository exists.
POP.003.0071 Cannot lookup install service: "<installServiceName>".

Cause: The server cannot find the install service for this component.
Response: The component is not supported.
POP.003.0072 ComponentUri is not a thingID: "<resourceURI>".

Cause: The server cannot determine the location of the installed component based on the passed URI.
Response: Correct the calling code to specify a thingID as the componentUri parameter of the
uninstallComponent command.
POP.003.0073 <userName> cannot install component.

access rights.
POP.003.0074 <userName> cannot read search service.

access rights.

POP.003.0076 <userName> cannot remove access entries from <itemName>
access rights.
POP.003.0076 <userName> cannot remove access entries from <itemName>.

Cause: The specified user cannot remove entries from the access control list of the specified item.
Response: Grant the user the rights to perform the operation, or have the operation performed by a different
user who has permission to change the access control list of the target item.
POP.003.0077 <userName> cannot set the authentication scheme of <itemName>

access rights.
POP.003.0078 <userName> cannot set the owner of <itemName>

access rights.
POP.003.0079 Internal error. Access right lengths do not match.

Cause: Internal error. A database API inconsistency exists.
Response: Use the Manage Components portlet to edit permissions for this portal object.
POP.003.0080 No auth scheme for auth Level: "<authLevelName>".

Cause: The authentication scheme may not be installed yet or the specified authentication level is not valid.
Response: Install the missing authentication scheme wm_<schema>Auth.cdp component or correct the
'authLevel' attribute value of your custom xmlImport.xml file.
POP.003.0081 No implementation for auth scheme: "<authSchemeName>".

Cause: The authentication scheme for the target portal item is invalid.
Response: Use the Permissions page to set the authentication scheme for the item to one of the installed
authentication schemes.

POP.003.0082 <userName> cannot list the contents of <itemName>

access rights.
POP.003.0083 <userName> cannot add an item to <folderName>

access rights.
POP.003.0084 <userName> cannot add a shortcut to <itemName>.

Cause: Most likely User does not have appropriate access rights
Response: Give the user access rights.
POP.003.0085 <userName> cannot remove an item from <itemName>

access rights.
POP.003.0086 <userName> cannot remove a shortcut from <itemName>

access rights.
POP.003.0088 You cannot move this container into a descendant of itself.

Cause: The folder cannot be moved to one of its subfolders.
Response: If you need to move the folder, do not attempt to move it into a subfolder of itself.
POP.003.0090 <folderName> cannot contain a duplicate name.

Cause: The folder (page) cannot have items with duplicate names.
Response: When naming items in a folder, make sure each has a name that is unique within the folder.

POP.003.0091 Unable to create xtype with null name: "<xtypeID>".
Cause: The xtype id passed into the createChild command is not valid.
Response: Pass a valid xtype id parameter value. The valid values are from the tblXTypes tables.
POP.003.0092 <folderName> is a reserved folder and cannot be modified.

Cause: The folder is a system folder and cannot be modified.
Response: Do not try to modify this folder.
POP.003.0093 You cannot move a reserved item.

Cause: The item is reserved and cannot be moved.
Response: Do not attempt to move the item.
POP.003.0094 <folderName> is a reserved folder and can not be versioned.

Cause: The folder cannot be added to the version control because it is a special folder type.
Response: Do not try to add this folder to version control.
POP.003.0095 <userName> cannot change the columns of <itemName>

access rights.
POP.003.0097 <userName> cannot minimize portlet <portletName>

access rights.
POP.003.0099 <userName> cannot view this item.

Cause: The user attempted to view an item but does not have permission to see it.
Response: The portal administrator should use the Manage Components portlet to edit permissions for this
portal object.
POP.003.0102 Unable to locate: "<userDn>".

Cause: The server cannot find the user in the directory.
Response: The user may have been removed from the directory. Determine if this user belongs in the directory.

POP.003.0103 Unable to locate: "<number>" invalid type.

Cause: The directory may be corrupted or improperly configured.
POP.003.0104 <userName> cannot modify user.

access rights.
POP.003.0105 Cannot modify attribute on principal, <userDn> not found.

POP.003.0106 Cannot set email address on principal, email address attribute not configured properly.
Cause: The e-mail attribute is not configured for this user directory.
Response: Update the directory configuration in Directory Service Administration portlet to specify an 'email'
attribute name and try again.
POP.003.0107 <userName> cannot create an alias.

access rights.
POP.003.0108 Alias not found: "<alias>".

Cause: An attempt was made to remove an alias that does not exist.
Response: Make sure the remove alias call uses an existing alias name.
POP.003.0109 <userName> cannot delete this alias.

access rights.

POP.003.0110 Internal ScheduleMechanics error.
Cause: The paging cookie is invalid.
Response: Close the browser, then open it again and retry the action.
POP.003.0111 <userName> cannot view the subscription of <itemName>.

access rights.
POP.003.0112 <userName> cannot list the subscriptions to <itemName>

access rights.
POP.003.0113 <userName> cannot edit the subscription to <itemName>

access rights.
POP.003.0115 Cannot create cookie for URI: "<resourceURI>".

POP.003.0116 User page size must be >= 0 (zero indicates default).

Cause: The page size cannot be negative.
Response: Correct the calling code to pass the pageSize parameter as a positive number.
POP.003.0117 Cannot set password on user, user not found: "<userDn>".


POP.003.0118 Cannot get roles for user, user not found: "<userDn>".
POP.003.0119 Unable to locate mechanics: "<mechanicsName>".

Cause: Mechanics cannot be found for the given name or URI.
Response: If the error is related to a standard portlet, try to redeploy the portlet using the Install
Administration portlet. If you have created a custom portlet, you need to correct the calling code in the Portlet
Developer and redeploy the portlet.
POP.003.0120 <userName> cannot cut <itemName>

access rights.
POP.003.0121 <userName> cannot cut <itemName>

access rights.
POP.003.0122 A datasource named "<datasourceName>" already exists.

Cause: An attempt was made to register a SQL datasource with a datasource name that has already been used
for another datasource.
Response: Use a different name for the new datasource.
POP.003.0122 A datasource named "<datasourceName>" already exists.

Cause: An attempt was made to register a SQL datasource with a datasource name that has already been used
for another datasource.
Response: Use a different name for the new datasource.
POP.003.0123 You cannot copy a reserved item.

Cause: The item is reserved.
Response: Do not attempt to copy a reserved item.

POP.003.0126 compression not allowed.
Cause: The presentation cache content cannot be compressed.
Response: Correct the calling code to not call PresentationCacheContent.setCompressed(true).
POP.003.0129 Cannot initalize principal, invalid type: "<number>".

Cause: The directory may be corrupted or improperly configured.
POP.003.0130 Error in thread resyncing group properties [domain]: "<domainName>".

Cause: Directory access general problem
Response: Try to sync the directory again later.
POP.003.0130 Error in thread resyncing group properties [domain]: "<domainName>".

Cause: The server failed to refresh the metadata about a Group from the LDAP server.
Response: Validate connectivity to the LDAP server using an LDAP browser tool or the directory native
Administration UI or tools.
POP.003.0134 <userName>'s account has been disabled.

Cause: The user account has been disabled.
Response: Enable the user account in the underlying user directory. Use the directory Administration UI or
tools for that purpose.
POP.003.0135 Unable to find the content location for: "<resourceURI>".

Cause: The content store is corrupted.
Response: Delete the item and try again.
POP.003.0136 Cannot install component "<componentName>" because it requires "<componentName>" to be installed first.
Cause: The component being installed depends on another component that is not installed yet and not in the 'to
install' list.
Response: Install the required components before attempting to install the component that raised the error.

POP.003.0137 Unable to create with unkown type: "<xtypeName>".

Cause: Cannot create an item because the xtype is invalid.
Response: Pass a valid xtype parameter to createChild command. All valid xtypes can be found under the
XTypes system folder in the Portal UI.
POP.003.0139 Component "<componentName>" installation failed. System state is recovered by uninstalling the component.
Original error: <errorMessage>
Cause: The installation of the component failed.
Response: Uninstall the component to recover the system state. Look at the install.log file for details of why the
installation failed.
POP.003.0140 Component "<componentName>" installation failed. System state is recovered by reinstalling the previous
version of the component. Original error: <errorMessage>"
Cause: The installation of the component failed.
Response: Uninstall the component to recover the system state. Look at the install.log file for details of why the
installation failed.
POP.003.0160 Failed to resolve wiring for property <propertyName>

Cause: Wiring cannot be resolved for the <propertyName> property of a portlet instance.
Response: Open up Wiring settings for this portlet and make sure the source portlet and its property are still
available. Adjust the wiring settings if necessary.
POP.004.0001 The Resource Bundle for "<bundleName>" was not found.

Cause: The server cannot load the specified resource bundle class, likely because the bundle is a portlet class
that hasn't been deployed or is deployed in a different portlet.
Response: Use the Portlet Developer to add the resource bundle class to the invoking portlet. Redeploy the
portlet.
POP.004.0002 The Message Key "<messageKey>" was not found in the Resource Bundle "<bundleName>".
Cause: The resource bundle message key is missing.
Response: Correct the resource bundle to include a resource for the key specified by the error message.

POP.004.0004 An error occurred while formatting the Message Key "<messageKey>".
Cause: The resource bundle message key is missing or the message could not be formatted because its content
is invalid.
Response: Correct the resource bundle to include the key specified by the error message, or correct the resource
content identified by the key.
POP.004.0005 Error creating search pools "<errorMessage>".

Cause: The server cannot initialize some search service data structures because an internal portal error
occurred.
Response: Use the more specific error message quoted by this error message to diagnose the problem.
POP.004.0006 Invalid cache ID: "<cacheID>".

Cause: The server cannot initialize an invalid cache.
Response: Correct the thing cache configuration in the cache.xml Portal configuration file. A valid entry is:
<cache name="Thing Cache" class="com.webmethods.portal.service.cache.impl.TransientCache"
maxSize="10000"
isClustered="true"
ID= "1"
enabled="true"/>
POP.004.0008 Unable to initialize content service component: "<itemName>".

Cause: Cannot initialize the content service.
Response: If you can't re-configure the offending content service, call Tech Support for a reset directive.
POP.004.0010 No provider for directory [name, type] : [<serviceName>, <serviceType>]

Cause: The server cannot initialize the specified directory service because it is an unknown type of directory
service.
Response: Correct the directoryConfig.xml Portal configuration file to remove the 'Service' element with a
'name' attribute value specified by the error message.
POP.004.0011 Invalid XML for directory, no DirectoryConfig element found: "<serviceName>".

Cause: The server cannot initialize the directory service because its configuration data is corrupt.
Response: Correct the directoryConfig.xml Portal configuration file to remove the 'Service' element with a
'name' attribute value specified by the error message.

POP.004.0012 Unable to construct component data for directory: "<directoryService>".

Cause: The server cannot initialize the directory service.
Response: Use the Directory Services Administration portlet to create a new directory service and then delete
the old one.
POP.004.0013 Alias Cache not found.

Cause: The server cannot initialize the alias service because the alias cache is not configured.
Response: Add the following entry to the cache.xml Portal configuration file: <cache name="AliasCache"
class="com.webmethods.portal.service.cache.impl.AliasCache"
maxSize="5000"
isClustered="true"
ID="2"
enabled="true"/>
POP.004.0014 Can't create alias cache.

Cause: The server cannot initialize the metadata service because the required cache cannot be located.
maxSize="10000"
isClustered="true"
ID= "1"
enabled="true"/>
POP.004.0015 Unable to create MetaContext: "<datasourceName>".

Cause: The server cannot create a connection to metadata data-source because the configuration information
for the data-source could not be retrieved.
Response: Correct the metaContext.xml Portal configuration file to remove the 'Context' element with a
'connection' attribute value specified by the error message.
POP.004.0016 Can't get schedule list: "<itemName>".

Cause: The server was unable to list all of the portal's schedules.
Response: Verify that the database has been properly configured and that the portal schema was properly
installed by paying close attention to the installation process.

POP.004.0017 Thing Cache not found.
Cause: The server cannot initialize the metadata service because the required cache cannot be located.
maxSize="10000"
isClustered="true"
ID= "1"
enabled="true"/>
POP.004.0018 Can't create thing cache.

Cause: The server cannot initialize the metadata service because the thing cache configuration is invalid.
maxSize="10000"
isClustered="true"
ID= "1"
enabled="true"/>
POP.004.0019 No queue specified.

Cause: The server cannot initialize the e-mail notification deliverer because the notification queue name was
not specified in the deliverer's configuration.
Response: Specify the queue name in the 'queue' attribute of the delivery initializers in the phaseProvider.xml
Portal configuration file.
POP.004.0020 Unexpected exception: "<exceptionMessage>".

Cause: The server cannot initialize the e-mail notification deliverer because an unexpected error occurred.
information.
POP.004.0021 Invalid ConnectionManager config file.

Cause: The server cannot initialize the datasource connection manager because it cannot acquire its
configuration file.
Response: Validate that the portal.properties Portal configuration file contains the following entry:
'sled.connectionmanager.config=config:/db.xml'.

POP.004.0022 Could not acquire meta context : version service name: "<serviceName>".
Cause: The server cannot acquire the metadata data-source by name because the specified name is
unrecognized.
POP.004.0023 Could not find root folder of version services.

Cause: The root folder of the version service does not exist.
Response: Reinstall the version service using the Portal Configurator.
POP.004.0024 Could not create service thing : version service name: "<versionService>".
Cause: The server cannot initialize the version service.
Response: Verify that all of the versioning components have been deployed. This includes the version service
and version portlet which can be located in the system portal folders.
POP.004.0027 Ftp login failed for user [<userName>] : <errorMessage>.

Cause: The server cannot login to the remote FTP server.
Response: Verify that the credentials are valid for the FTP connection service, and that the network
connectivity is valid.
POP.004.0028 Ftp Connection Error: Access Denied

Cause: The server cannot connect to the remote FTP server.
Response: Validate that the credentials and configuration are valid for the FTP connection service, using the
Content Service Admin portlet, and that the network connectivity is valid.
POP.004.0029 Ftp Connection Error: "<itemName>".

POP.004.0032 Invalid ID's in createThing.

Cause: The server was unable to publish a new portal object.
Response: Correct the invoking method to pass in a valid owner and parent ID parameters.

POP.004.0033 Database is busy or unavailable.
Cause: The server cannot execute the SQL command because the database is not responding to the Portal in a
timely fashion. The database could be experiencing too much load to respond to the Portal, the Portal may not
be able to access the database's server or port, or the database may not be running.
Response: Verify that the database is running, and is not experiencing heavy load. Verify that the database has
an adequate number of connection threads available. Verify that the machine on which the Portal is running
can access the data-source's configured hostname and port.
POP.004.0034 Datasource Mismatch, passed (<itemName>) to API on (<dataSourceID>).

Cause: Metadata data-source cannot operate on a resource from a different data-source.
Response: Correct the invoking source code to not use a metadata service to operate on a resource that does not
belong to the service's datasource. Consult the API documentation for more information.
POP.004.0035 Invalid URI

Cause: The server cannot resolve the data-source for a metadata Portal identifier.
Response: The identifier that caused this error does not identify a resource, so please don't try to use it to
identify a resource.
POP.004.0036 Invalid schedule info: interval "<intervalTime>", timeAt "<startTime>": Unable to parse 'timeAt' and/or 'interval'
Cause: An attempt to create or modify a schedule has failed because of invalid schedule parameters.
Response: Correct the invoking code to pass valid schedule parameters. Valid 'interval' and 'timeAt' parameter
values are times formatted according to the ISO 8601 date/time format.
POP.004.0037 Invalid schedule info: interval "<intervalValue>", timeAt "<timeToWaitValue>": 'timeAt' overlaps with 'interval'
Cause: The server cannot execute the scheduled event because the time to wait (timeAt) after the interval
setting but before executing the event is approximately as long as the interval itself.
Response: Edit the schedule using the Event Administration portlet (in the Portal Configuration category of the
Portal Admin Dashboard) so that the interval is of a scale longer than the On/At time-to-wait (weeks instead of
days, hours instead of minutes, and so forth).
POP.004.0038 Unknown thing type: <itemName>

Cause: The server was unable to identify the base type of the metadata service object.
Response: Verify that the portlet was built using the Portlet Developer.

POP.004.0039 Unable to unregister XType: <xtypeID>

Cause: Either the xtype was never registered, or there are published instances of that xtype.
Response: Ensure that all instances of that xtype have been deleted prior to unregistering. These types may be
found by using the Publish History reporting portlet.
POP.004.0040 Can't convert to xtype of different base type

Cause: Xtype conversion is an unsupported feature.
Response: Correct the invoking method to not attempt to modify the xtype parameter.
POP.004.0041 Invalid Principal.

Cause: The server cannot modify the access control entry.
Response: Correct the invoking method to specify a principal parameter.
POP.004.0042 Invalid Ace. Cannot set both granted and denied on the same right.
Cause: The server cannot set a single access control entry to grant and deny the same access right.
Response: Correct the invoking source code. Consult the API documentation for more information.
POP.004.0043 Invalid Ace. Unknown right.

Cause: The server cannot set access control entry with right bit outside of defined right bit range, as defined by
the access service API.
Response: Correct the invoking source code. Consult the API documentation for more information.
POP.004.0045 Invalid Ace. Cannot delegate a right not granted.

Cause: The server cannot modify the access control entry.
Response: Correct the invoking method to include the proper right set parameter.
POP.004.0047 Cookie is not set in this view.

Cause: The server cannot display the inbox notifications because a paging cookie was not set.
Response: Log out, log in, and try again.
POP.004.0048 Unable to load Subscription object. Subscription no longer exists.

Cause: The server cannot locate the subscription information that triggered the notification.
Response: Delete the notification, by locating the offending notification in the portal inbox and deleting it.

POP.004.0049 Unable to load Event.
Cause: The server cannot load event data because an error occurred in querying the database.
information.
POP.004.0050 Unable to remove Notification.

Cause: The server was unable to locate the notification in order to delete it.
Response: Correct the invoking method to specify a valid notification parameter.
POP.004.0051 Unable to remove Event.

Cause: The server cannot remove the event item from the database because of a SQL error in executing the
stored procedure that performs the removal.
information.
POP.004.0052 Start index beyond end of list.

Cause: The server cannot list a page of metadata resources because the specified start index of the page is
greater than the total number of resources in the list.
Response: Correct the source code that executes the query. Specify a start index that is less than the total
number of resources in the list by modifying the 'start' property of the
com.webmethods.portal.service.view.IPagingCookie.
POP.004.0053 Paged before first item.

Cause: The server cannot list a page of metadata resources because the specified start or end index of the page
is less than one.
Response: Correct the source code that executes the query. Specify a start index that is less than the total
number of resources in the list by modifying the 'start' or 'end' properties of the
com.webmethods.portal.service.view.IPagingCookie.
POP.004.0054 Invalid end index.

Cause: The server cannot execute a paged container query because the page-start index is greater than the
page-end index.
Response: Correct the source code that executes the query. Specify a start index that is less than the end index
by modifying the 'start' and 'end' properties of the com.webmethods.portal.service.view.IPagingCookie.

POP.004.0055 Invalid sort order for getTreeView.

Cause: The server cannot sort the tree view's results with the supplied sort parameter.
Response: Correct the invoking code to pass valid sort parameters.
POP.004.0056 Error saving subscription. No subscription or source information.

Cause: The server cannot add the subscription because the subscription information is corrupted.
Response: Correct the invoking method to specify a valid subscription parameter.
POP.004.0057 Error adding subscription. No subscription or source information.

Cause: The server cannot add the subscription because the subscription information is corrupted.
Response: Correct the invoking method and ensure that the proper parameters are passed.
POP.004.0061 Unable to load Role.

Cause: The server cannot load the metadata information about a registered role.
Response: Using the Role Administration portlet, regenerate and configure the portal role.
POP.004.0062 Missing results from the database.

Cause: The server has received Invalid results from a stored procedure.
Response: Verify that the database has been properly configured and that the portal schema was properly
installed by paying close attention to the installation process.
POP.004.0063 Access model not set.

Cause: The access service cannot evaluate access rights for a user until its access model has been specified.
Response: Correct the portal.properties file in the Portal's config directory so that it has the following line:
'framework.access.model=restrictive'.
POP.004.0064 Access model is not valid.

Cause: The server cannot set the access model because the specified model is unknown. The valid model values
are 1 (permissive) and 2 (restrictive).
Response: Correct the portal.properties file in the Portal's config directory so that it has the following line:
'framework.access.model=restrictive'.

POP.004.0065 Serialized object version is different then current version: [version, currentVersion]
[<serializedObjectVersionID>,<currentVersionID>]
Cause: The server cannot read the alias stored in the database because its serialized object version is out of date.
Response: Revert to the previous version of portal.jar, and restart the Portal server.
POP.004.0066 Unknown type: <queryType>

Cause: The server cannot initialize the directory search control because the specified query type is unknown.
Response: Correct the code invoking directory search to specify a type of 1 (users) or 2 (groups).
POP.004.0067 Attempted to set subkey on primary-key only key.

Cause: The server cannot create the cache key.
Response: Correct the invoking method to include appropriate cache key parameter.
POP.004.0068 Can't find or create valid cache.

Cause: The cache update stored procedure cannot resolve the cache identifier.
Response: Correct the invoking source code to provide a cache-key with a valid cacheID. Consult the API
documentation for more information.
POP.004.0069 Cache error: data is not a serializable object

Cause: The server attempted to cache an object that is not serializable.
Response: Correct the source code that invokes the
com.webmethods.portal.service.cache.impl.DBCache.getBytesFromObject() method to pass serializable object.
POP.004.0070 Invalid connection parameters.

POP.004.0071 Error persisting directory config.

Cause: The server cannot store the directory configuration modifications.
Response: Try to use the Directory Services Administration portlet to create a new directory service and then
delete the old one.

POP.004.0072 Cannot lookup non user or group thing based objects : <itemName>
Cause: The server cannot look up directory service resources using metadata identifiers unless the resource is a
user, group, or role.
Response: The identifier specified by the error message does not identify a directory resource, so please do not
try to use it to identify a directory resource.
POP.004.0073 Invalid URI, no directory service specified "<directoryService>"

Cause: The server cannot locate an invalid directory user.
Response: Verify that the Directory service is still properly configured by using the Directory Service
Administration portlet.
POP.004.0074 Specified domain in URI not found [domain, uri] -- [<serviceName>, <itemName>]
Cause: The server cannot look up the directory service based on a Portal identifier because the identified
directory service does not exist.
Response: This error may have happened because the specified directory service configuration was deleted.
Try re-adding the directory service using the Directory Services Administration portlet (in the Portal
Configuration category of the Portal Admin Dashboard).
POP.004.0076 Error adding new directory service: <errorMessage>

Cause: The server cannot add or update a directory service because of an error in validating or storing the
directory service configuration.
information.
POP.004.0077 Cannot build URI, unknown type <directoryServiceObjectType>

Cause: The server cannot construct a Portal identifier for the directory service object because the specified type
is not one of 'user', 'group', or 'role'.
Response: Correct the source code that invokes the
com.webmethods.portal.server.directory.impl.DirectoryTools.constructDirectoryURI() method to specify only
either 'user', 'group', or 'role'.
POP.004.0078 Invalid escape character in <itemName> at position <position>

Cause: The server was unable to normalize the LDAP DN.
Response: Investigate the original DN and try to remove offending characters if possible.

POP.004.0079 Cannot retrieve most significant attribute; invalid DN: "<directoryDN>"
Cause: The server cannot parse a directory service object dn (the object's LDAP ID), because the dn is invalid.
Response: Supply a valid dn to the com.webmethods.portal.service.directory.impl.jndi.JNDITools class's
getMostSignificantAttr() and getMostSignificantAttrSet() methods.
POP.004.0080 Unable to connect to: <directoryStore>

Cause: The server cannot connect to the remote LDAP directory store.
Response: Verify that the Directory configuration is valid by using the Directory Service Administration
portlet.
POP.004.0081 No user class specified in directory factory config

the old one.
POP.004.0082 No group class specified in directory factory config

Cause: The server cannot initialize the directory service.
POP.004.0083 Unable to wrap object. Unknown type: <itemName>

Cause: The server was unable to read an LDAP entry.
Response: Use the Directory Services Administration portlet to verify that the Directory configuration is valid.
POP.004.0085 Error setting attribute [name, value, action, message] - [<itemName>, <value>, <action>, <message>]
Cause: The server cannot modify the LDAP attribute.
Response: Validate that the connection to the LDAP directory store has adequate privileges to modify LDAP
entries. Use your LDAP vendor's administration tool.
POP.004.0086 No response controls for directory: <directoryName>

Cause: The server cannot update the directory search control.
Response: Start a new search.

POP.004.0087 Cannot page backward

Cause: The server cannot page directory search control backward because the control is at the first page of
results.
Response: Correct the source code invoking the directory search to check if the search has previous results
before trying to page forward. You can determine if a search has previous results by inspecting the value of the
'hasPrevious' property of the com.webmethods.portal.service.view.IPagingCookie that you used to perform
the search.
POP.004.0088 Cannot page forward

Cause: The server cannot page the directory search control forward because the search has no more results.
Response: Correct the source code invoking the directory search to check if the search has more results before
trying to page forward. You can determine if a search has more results by inspecting the value of the 'hasNext'
property of the com.webmethods.portal.service.view.IPagingCookie that you used to perform the search.
POP.004.0089 Unable to retrieve user list

Cause: The server cannot list the users of a directory service, most likely because of a problem connecting to the
directory service.
POP.004.0090 Unable to lookup user <userName>

Cause: The server cannot locate the specified user.
Response: Use the User & Group Management portlet to verify that the group exists in the LDAP directory
store.
POP.004.0091 Invalid username or password

Cause: You have supplied invalid credentials.
Response: Try authenticating again with proper username and password.

POP.004.0092 Could not lookup DN <dn>
Cause: The server cannot look up a user or group by directory dn (the user or group's LDAP ID) because an
error occurred while querying the directory store.
information.
POP.004.0093 Error looking up group <groupName>

Cause: The server cannot locate the specified group.
POP.004.0094 Unable to perform search : <itemName>

Cause: An unknown error occurred while performing an LDAP directory search.
Response: Correct the invoking method to specify a valid query parameter.
POP.004.0095 Error getting memberships

Cause: The server cannot fetch membership information from the LDAP directory store.
portlet.
POP.004.0096 Unable to modify password of user <userName> because the supplied old password is incorrect.
Cause: An attempt was made to change a user's password without supply the user's old password.
Response: Supply the correct old password.
POP.004.0097 INSTALL is not supported operation for: <itemName>

Cause: Installation of the deployable object has failed.
Response: The deployable object does not have any installation code associated with its file extension. This is
due to an attempt to deploy an unsupported type to the portal.
POP.004.0098 UNINSTALL is not supported operation for: <componentURL>

Cause: The server cannot uninstall the specified type of component.
Response: The specified component cannot be uninstalled, so do not try to do it.

POP.004.0100 Component file not found: <urlName>

Cause: The server cannot install the component because no component was found at the specified location.
Response: Specify the correct location. If you are installing a component using the Install Administration
portlet, select a valid location by means of the portlet's Browse button.
POP.004.0101 Cannot set properties for installer: <errorMessage>

Cause: The server cannot set install services because an internal error occurred.
information.
POP.004.0102 Script file not found: <itemName>

Cause: The server cannot execute a portlet deployment script.
Response: Using the Portlet Developer, rebuild and redeploy the portlet.
POP.004.0103 Script finished with <numberOfErrors> error(s). Please look at the log for details
Cause: An error occurred while installing or uninstalling a deployable component.
POP.004.0104 Error installing/uninstalling component

Cause: An error occurred while installing or uninstalling a deployable component.
POP.004.0105 Failed to initialize LoggingCollector: <itemName>

Cause: The server cannot initialize logging over the JMS provider.
Response: Verify that the JMS server is running and is properly configured.
POP.004.0106 PortletInfo is not available for uri [<uriName>]. Probably the portlet is not properly installed. Try to uninstall
and then install it again.
Cause: Portlet is not currently available.
Response: Probably the portlet is not properly installed. Try to uninstall and then install it again.

POP.004.0107 Invalid portlet descriptor. Portlet/DBO name is not defined
Cause: The server cannot load portlet information from the portlet descriptor because the portlet descriptor
does not contain the portlet's name, or the portlet descriptor is incorrectly structured.
Response: Using the Portlet Developer, correct the portlet descriptor and redeploy it to the Portal server.
POP.004.0109 Portlet URI is not published instance of the portlet or type. Unable to persist properties
Cause: The server cannot persist the properties of a portlet type without a valid portlet or portlet type
identifier.
Response: Supply a valid portlet or portlet type identifier to the
com.webmethods.portal.service.portlet.impl.PortletType.setProperties() method.
POP.004.0110 Portlet bean class is invalid: <itemName>

Cause: The server cannot initialize the portlet because the portlet doesn't implement the required interface.
Response: Using the Portlet Developer, correct the portlet's deployment descriptor or regenerate the portlet,
and then redeploy it.
POP.004.0111 Portlet bean is not poolable: <beanClassName>

Cause: The server cannot instantiate the portlet bean because the bean does not implement the
com.webmethods.portal.system.pool.IPooledObject interface.
Response: Use the Portlet Developer to correct the portlet bean source code to implement IPooledObject.
POP.004.0112 Portlet title bar class is invalid: <className>

Cause: The server cannot initialize portlet type information because the portlet titlebar class specified by the
portlet's descriptor could not be found.
Response: Using the Portlet Developer, remove the titlebar class specification from the portlet descriptor. Then
redeploy the portlet.
POP.004.0113 Invalid URI, no search service specified: <uriName>

Cause: The server cannot locate search provider because of an invalid URI.
Response: Correct the invoking code to use a valid URI.
POP.004.0114 Invalid datasource name: <itemName>

Cause: The server cannot execute an SQL statement against an invalid datasource.
Response: Correct the invoking method to pass the correct parameters. One of the critical parameters is the
handle of the datasource, which can be obtained from the DataManager's API.

POP.004.0115 Can't find data service folder: <itemName>

Cause: The server cannot locate the system folder.
Response: It is possible that a portal administrator has deleted a critical system folder. If so, you may need to
reinstall the Portal server.
POP.004.0116 Cannot obtain database connection from pool: <connectionName>

Cause: The server cannot obtain a database connection because all connections allocated for the Portal are
already in use or the Portal cannot connect to the database.
Response: Verify that the database is running, and is not experiencing a heavy load. Verify that the database
has an adequate number of connection threads available. Verify that the machine on which the Portal is
running can access the data-source's configured hostname and port.
POP.004.0117 Database connection is closed.

Cause: The server cannot execute the SQL query because the database connection is closed.
Response: Execute the statement again. If problems persist, shut down and restart the Portal server.
POP.004.0118 Error updating Clob field

Cause: An error occurred while updating an unbounded-size database field because something went awry at
the database level.
POP.004.0119 Error updating Blob field

Cause: An error occurred in updating an unbounded-size database field because something went awry at the
database level.
POP.004.0120 Could not find content service for: <itemName>

Cause: The server cannot store versioned content for a resource because the content service for the resource
cannot be found.
Response: Delete the resource.
POP.004.0121 Versioned content uri is null or empty: <itemName>

Cause: The server cannot access the versioning information.
Response: The version information is corrupted. Try to obtain a different version and recreate the changes.

POP.004.0122 Content doesn't exist: <itemName>
Cause: The server cannot read a resource's versioned content because the resource has no content.
Response: Delete the resource using the UI.
POP.004.0123 User ID is invalid: <itemName>

Cause: The server cannot locate the user's information about the versioned object.
Response: The version information is corrupted. Use the Publish portlet to publish a new instance of the item,
and add the item to versioning. This can be done by consulting the "webMethods Portal Getting Started
Guide."
POP.004.0124 Could not find user: <userName>

Cause: Cannot locate the user's information about the versioned object.
Response: The version information is corrupt. Publish a new instance of the item, and add the item to
versioning.
POP.004.0125 Could not find thing: <itemName>

Cause: Cannot resolve metadata resource identifier from string.
Response: The resource specified by the identifier does not exist, so don't use the identifier.
POP.004.0126 Cookie is not set on the List View

Cause: The server cannot sort or slice the list without a paging cookie.
Response: Correct the invoking source code to associate the paging cookie with the list by setting the 'cookie'
property of the list.
POP.004.0127 Unable to initialize directory service <directoryServerName>: <errorMessage>

Cause: The server cannot initialize the directory service due to an error.
Response: Verify the connection information to the directory service, by using the Directory Service
Administration portlet. Ensure that the login credentials are accurate. Ensure that there is network
connectivity to the directory service from the portal.
POP.004.0128 Invalid directory Uri: "<uriName>"

Cause: The URI is malformed.
Response: Correct the invoking method to specify a valid URI parameter.

POP.004.0130 Unidentified Clob implementation class: <className>

Cause: The server cannot retrieve an unbounded-length field from the database because the database driver is
incompatible with the Portal.
Response: Modify datasource driver settings in the db.xml Portal configuration file to use approved driver.
POP.004.0131 Unidentified Blob implementation class: <itemName>

Cause: The server cannot retrieve result set data because of an incompatible database implementation.
Response: Verify that the correct version of Oracle is installed and that you are using the portal-supplied
database drivers. You can consult your Oracle installation to verify the version of Oracle and ensure that you
haven't added any custom oracle drivers into the portal's class path.
POP.004.0132 Xtype not found: <itemName>

Cause: The server cannot locate the portlet xtype in the metadata store.
Response: Most likely the portlet has been undeployed. Use the Install Administration portlet to redeploy the
portlet.
POP.004.0134 Error loading class group: <groupName>

Cause: The server cannot load all the classes for the specified class-loader group.
information.
POP.004.0135 Error setting config on directory, rolling back to previous config.

the old one.
POP.004.0136 Unable to retrieve group list.

Cause: The server cannot fetch group information from the LDAP directory store.
portlet.
POP.004.0141 No configuration information found for content service, not initializing: <itemName>.
Cause: The server cannot initialize the content service.
Response: If you can't reconfigure the offending content service by using the Content Service Admin portlet
call Customer Care for a reset directive.

POP.004.0144 FTPconnection connect to <ftpSite>.
Cause: A connection was initiated with the remote FTP server.
Response: This is an informative statement. No action is necessary.
POP.004.0152 No Query Parameters specified.

Cause: The server cannot execute the search because there is no search query.
Response: Browse back to the Search portlet and try again.
POP.004.0153 Search Server is unavailable or not properly configured

Cause: The server cannot access the search service.
Response: Verify that the search service is properly configured by using the Search Admin portlet.
POP.004.0155 Error adding file to search index: <fileName>

Cause: The server was unable to properly index a portal component object.
Response: Determine if the document is in an unknown format or is malformed. Examine the Lucene Search
Admin portlet for details on formats.
POP.004.0156 content stream is null

Cause: The server cannot locate the content file in the content repository.
Response: Verify that the content repository still exists, and there is network connectivity. The content
repository has some configuration information in the storageConfig.xml, and if a custom content service has
been mounted, then verify that connectivity between the portal process and the network file system is intact.
Verify that you can browse to the content using the Portal UI. Purge all items pending deletion with the
Manage Deleted Items Admin Portlet.
POP.004.0157 Error getting resync list for library: <libraryName>

Cause: The server cannot resynchronize the search library index because an error occurred in querying the
database for the list of resources to be indexed.
POP.004.0158 Malformed Lanaguage Pack: <languagePackName>

Cause: The server cannot use the language pack because its name is malformed. The name should be one of
[language], [language]_[country], or [language]_[country]_[variant], where [language] is a language code
(such as en or ja), [country] is a country code (such as US or JP), and [variant] is a variant code.
Response: Correct the language pack name and re-install language pack.

POP.004.0198 Cannot create a user with a duplicate id: <userID>

Cause: An attempt was made to create a new user with a duplicate ID of an existing user.
Response: Use a unique identifier when creating a new user, group or role.
POP.004.0199 Cannot create a user with a duplicate id: <userID>

Cause: An attempt was made to create a new user with a duplicate ID of an existing user.
Response: Use a unique identifier when creating a new user, group or role.
POP.005.0002 Cannot call main twice.

Cause: An attempt was made to initialize the PortalSystem twice.
Response: After the Portal server is initialized, you should not attempt to do so again.
POP.005.0003 Error parsing segment urls: "<errorMessage>"

Cause: One of the Portal servers in the cluster has an incorrect URL.
Response: Verify the correct URL for the Portal server and use the Cluster Administration portlet to correct the
error.
POP.005.0004 Unable to register component: "<componentClassName>" due to "<errorMessage>"

Cause: The Portal server could not register the specified component.
component.
POP.005.0006 This server is not defined in the configuration: "<serverName>"

Cause: The specified Portal server is not included in the portal cluster configuration.
Response: Use the Cluster Administration portlet to add the specified Portal server to the cluster.
POP.005.0008 internal cache error

Cause: An internal error occurred in removing an item from a cache.
Response: Inspect the _problems_.log for details of the failure. This error could indicate that there is invalid
data in a cache. Restarting the portal server would likely remedy the problem.

POP.005.0009 Unable to loadComponent: "<componentClassName>"
Cause: A failure occurred in loading a portal component.
component.
POP.005.0010 Unknown object: "<itemName>"

Cause: The ComponentData object for a component is of an unknown type.
Response: The componentData must be one of the handled object types. This error means that a portal
component could not initialize because it is invalid and needs to be corrected.
POP.006.0003 portlet bean URI not specified

Cause: The portlet:bean JSP tag does not contain a uri attribute to identify a valid portlet instance.
Response: Correct usages of the 'portlet:bean' JSP tag to include a 'uri' attribute. The attribute value must
identify a valid portlet instance. Ensure that the portlet type referenced by the 'uri' attribute has been
deployed, and that the specific instance referenced by the attribute exists.
POP.006.0004 cannot create portlet bean for the URI "<uriName>"

Cause: The portlet:bean JSP tag does not contain a uri attribute that identifies a valid portlet instance.
Response: Correct usages of the 'portlet:bean' JSP tag to include a 'uri' attribute. The attribute value must
identify a valid portlet instance. Ensure that the portlet type referenced by the 'uri' attribute has been
deployed, and that the specific instance referenced by the attribute exists.
POP.006.0006 cannot find portlet bean named "<itemName>" in the current page context
Cause: The portlet:portletController JSP tag does not contain a portlet attribute. The value of this attribute is the
key to the pageContext entry in which a com.webmethods.portal.service.portlet.IPortletBean object is stored.
Response: Correct usages of the 'portlet:portletController' JSP tag to include a 'portlet' attribute that references
a valid IPortletBean.
POP.006.0007 cannot obtain portlet info

Cause: The portlet:info JSP tag does not contain an info attribute. The value of this attribute is the key to the
pageContext entry in which a com.webmethods.portal.service.portlet.info.IPortletInfo object is stored.
Response: Correct usages of the 'portlet:info' JSP tag to include an 'info' attribute that references a valid
IPortletInfo object.

POP.006.0008 cannot find portlet info named "<itemName>" in the current page context
Cause: The portlet:propertyGroups, portlet:propertyGroup, or portlet:propertyLine JSP tag does not contain an
info attribute. The value of this attribute is the key to the pageContext entry in which a
com.webmethods.portal.service.portlet.info.IPortletInfo object is stored.
Response: Correct usages of the 'portlet:propertyGroups', 'portlet:propertyGroup', and 'portlet:propertyLine'
JSP tags to include an 'info' attribute that references a valid IPortletInfo object.
POP.006.0016 cannot find portlet property info named "<itemName>" in the current page context
Cause: The portlet:propertyLine JSP tag does not contain a propertyInfo attribute. The value of this attribute is
the key to the pageContext entry in which a com.webmethods.portal.service.portlet.info.IPortletPropertyInfo
object is stored.
Response: Correct usages of the 'portlet:propertyLine' JSP tag to include a 'propertyInfo' attribute that
references a valid IPortletPropertyInfo.
POP.006.0018 cannot obtain portlet property bag

the key to the pageContext entry in which a com.webmethods.rtl.util.obj.IPropertyBag object is stored.
Response: Correct usages of the 'portlet:bean' JSP tag to include a 'propertyInfo' attribute that references a valid
IPropertyBag.
POP.006.0019 cannot find portlet property bag named "<itemName>" in the current page context
Response: Correct usages of 'portlet:bean' JSP tag to include a 'propertyInfo' attribute that references a valid
IPropertyBag.
POP.006.0020 object named "<itemName>" in the current page context is not a portlet property bag
Response: Correct usages of the 'portlet:bean' JSP tag to include a 'propertyInfo' attribute that references a valid
IPropertyBag.
POP.006.0024 'IterateTag' container is null

Cause: The util:iterate JSP tag does not contain a container attribute. The value of this attribute is the key to the
pageContext entry in which a java.util.Collection, java.util.Iterator, or java.lang.Object[] object is stored.
Response: Correct usages of the 'util:iterate' JSP tag to include a 'container' attribute that references a valid
container object.

POP.006.0028 cannot find XML DOM node named "<itemName>" in the current page context
Cause: Using the xml:valueOf JSP tag always raises this exception.
Response: Remove usages of the 'xml:valueOf' JSP tag.
POP.006.0029 connot create XML DOM document from given XML stream
Cause: The XML stream specified for the xml:xml JSP tag does not contain well-formed XML.
information.
POP.006.0030 cannot load XML DOM document for the specified location "<urlName>"
Cause: The xml:xml JSP tag could not load a file from the location specified by the location attribute.
Response: Correct usages of the 'xml:xml' JSP tag to include a 'location' attribute that correctly specifies the url
to an XML document.
POP.007.0007 Command not Found: "<commandName>"

Cause: An attempt was made to execute a portal command that is not deployed.
Response: Use the Install Administration portlet to deploy the missing portlet.
POP.007.0010 This renderer is unable to render: "<itemName>"

Cause: An attempt was made to use the FolderRenderer to render an item that is not a folder.
Response: You cannot use the FolderRenderer for non-folders.
POP.007.0011 Unknown response: "<responseCode>"

Cause: Dispatch Handler returned an unknown return code.
Response: Correct the dispatch handler to return a valid return code.
POP.010.0002 Root directory is invalid "<folderName>"

Cause: The portal configuration folder does not exist.
Response: Reinstall the Portal server.
POP.010.0010 Unable to create directory "<folderName>"

Cause: The server failed to create a folder inside the portal configuration registry.
Response: Determine if the user who started the Portal server process has rights to modify the Portal server's
config folder (Portal\server\config). If not, have someone with the correct permissions restart the server.

POP.010.0011 Unable to delete directory "<folderName>"

Cause: The server failed to remove a folder from the portal configuration registry.
Response: Determine if the folder really exists and that the user who started the server process has rights to
delete the folder.
POP.010.0012 Unable to delete file "<fileName>"

Cause: The server failed to remove a file from the portal configuration registry.
Response: Determine if the file really exists and is not read-only in the Portal server's config folder.
POP.010.0013 File "<fileName>" does not exist

Cause: A file that does not exist was requested from the portal configuration registry.
Response: To learn more about the error, examine the stack trace in the _problems_.log file.
POP.011.0012 <tempFolderPath> is not a directory.

Cause: The temporary save location for a file upload is not valid.
Response: Delete everything in the Portal/server/default/temp folder.
POP.011.0013 <folderPath> is not writable directory.

Cause: The temporary save location for a file upload is not writable.
Response: Make sure the Portal server was started by a user who has rights to the portal temp folder.
POP.011.0014 Posted content type "<contentType>" isn't multipart/formData.

Cause: The Portal server is expecting to upload a multipart portlet, but the specified content type does not
match.
Response: Check the file at the source for corruption. If the file is correct, try uploading it again.
POP.011.0015 Posted content length of "<contentLength>" MB exceeds limit of "<maxContentLength>" MB.

Cause: An uploaded file is larger than the size allowed by the portal administrator.
Response: Upload a smaller file or have the portal administrator use the Content Service Administration portlet
to increase the maximum file size configuration.
POP.011.0016 Separation boundary was not specified.

Cause: The specified file was corrupted before or during the upload process.

POP.011.0017 Corrupt form data. No leading boundary was found.
POP.011.0018 Malformed line after disposition "<line>"

POP.011.0019 The published file was empty or invalid.

POP.011.0020 Content disposition "<contentDisposition>" is corrupt.

POP.011.0022 Content type corrupt "<contentType>".

POP.011.0023 Malformed line after disposition "<line>".

POP.011.0025 Failed to create a DocumentBuilderFactory.

Cause: The XML parser appears to be missing.
Response: Check for the xercesImpl.jar file in the portal class path. If the file is missing, reinstall the Portal
server.
POP.011.0026 Failed to create a TransformerFactory.

Cause: The Xalan XSTL processor couldn't be loaded.
Response: Check for the xalan.jar file in the portal classpath. If the file is missing, reinstall the Portal server.

POP.011.0028 JMSProvider: failed to get configuration file.

Cause: The JMS provider does not appear to be connected.
Response: Verify that the Broker is running and that the Portal server can connect to the computer on which it
is running.
POP.011.0029 JMSProvider: failed to get configuration file "<configFile>", due to "<errorMessage>".

is running.
POP.011.0030 JNDI name not found: "<JNDIName>".

is running.
POP.011.0034 Size read mismatch "<actualSize>" vs "<expectedSize>"

Cause: An InputStream corruption error occurred.
POP.011.0036 Unable to delete file: "<fileName>"

Cause: An error occurred in removing a temporary file.
Response: Find the specified file and remove it manually.
POP.011.0037 Unable to delete directory: "<folderName>"

Cause: An error occurred in cleaning up temporary files.
Response: Find the specified directory and remove the temporary files manually.
POP.011.0039 ObjectUtil: illegal arguments.

Cause: An error occurred in setting a property on a object because the target object is null or the property name
is null or empty.

POP.011.0044 Error obtaining JMS topic for name: "<JMSTopicName>"
Cause: The requested JMS topic is not available.
is running.
POP.011.0045 no JMS provider, requesting topic name: "<JMSTopicName>"

is running.
POP.011.0046 JMSTopic.createTopicSession(), no JMS provider.

is running.
POP.011.0047 Unable to connect to registry.

Cause: The portal configuration registry is not available.
Response: In a cluster deployment, make sure the master server is started before starting the other cluster
nodes.
POP.011.0053 Error obtaining JMS queue for name: "<JMSQueueName>"

Cause: The requested JMS queue is not available.
is running.
POP.011.0054 no JMS provider, requesting queue name: "<JMSQueueName>"

is running.
POP.011.0055 JMSTopic.createQueueSession(), no JMS provider.

is running.

POP.011.0056 Invalid line: "<line>"

Cause: An error occurred in parsing a .properties file.
POP.011.0057 JMSDestination.Subscriber, unable to create consumer on: "<JMSDestinationName>"

is running.
POP.011.0058 JMSDestination.Subscriber, unable to create session for: "<JMSDestinationName>"

Cause: There are connectivity problems with the portal JMS server.
is running.
POP.011.0062 Stream exhausted.

Cause: An error occurred in decoding a BASE64 String.
POP.011.0063 BASE64Encoder: Bad Padding byte.

Cause: An error occurred in decoding a BASE64 String.
POP.012.0001.wm_chart Illegal <whatIsThis> property value: <propertyName>.

Cause: The Chart portlet is configured improperly.
Response: Change the value of the <propertyName> property to a legal value.
POP.012.0001.wm_contentrenderer Unable to parse regexps: <regularExpression>

Cause: The Portal installation is missing RegEx support jars.
Response: Reinstall the Portal server.

POP.012.0001.wm_managecomponents Cannot resolve portlet ID for "<portletName>".
Cause: The portlet is no longer installed or has become corrupted.
Response: Use the Install Administration portlet to redeploy the portlet
POP.012.0001.wm_perfmon No Perf Service is currently available.To enable the Service, please go to the Settings page.
Cause: The performance service is not currently running.
Response: To start the performance service, browse to the Administration Dashboard and in the Portal
Analysis folder, click Performance Monitor and then click Settings. Set the New Service Status field to Enabled.
The setting will be effective after the server restart. The Performance Monitor portlet (wm_perfmon.pdp) is not
displayed by default.
POP.012.0001.wm_permissions targetURI property is not specified

Cause: The Permission portlet could not locate the object to show permissions.
Response: Close and reopen the internet browser window.
POP.012.0001.wm_pghelpers No DSN was specified.

Cause: The server could not find a valid datasource name.
Response: Using the Portlet Developer, modify the database portlet to specify a valid datasource name.
POP.012.0001.wm_portalsearch ERROR: Unable to search because the search service was not specified.
Cause: The Search service is misconfigured or is missing.
Response: Redeploy the_portalsearch portlet using the Component Administration portlet.
POP.012.0001.wm_portletinportlet Recursive use of Portlet-in-Portlet for <itemName>.

Cause: Portlet-in-Portlet is attempting to display an item that displays the same Portlet-in-Portlet (for instance,
the Portlet-in-Portlet is displaying a portal page containing the same Portlet-in-Portlet).
Response: Change the Portlet-in-Portlet's "Portal Page" property to a different item.
POP.012.0001.wm_properties <portalResourceIdentifier> is not specified.

Cause: The Properties portlet could not locate the object to show its properties.
Response: Close and reopen the internet browser window.

POP.012.0001.wm_shelleditor Cannot clone parent's shell section because it is not a Portal Page
Cause: Some legacy shells created before Portal 6.2 or customer-created shells may have a raw JSP page
assigned to a shell section. Such shells cannot be cloned.
Response: Rework the legacy shell to not use JSP pages, but to use portal pages instead.
POP.012.0001.wm_skineditor <skinName> is not a valid skin.

Cause: The specified skin object is not a valid portal skin.
Response: Log off the portal and log back in.
POP.012.0001.wm_sqldata Query text is not defined

Cause: There is no valid SQL query specified for the SQL data portlet.
Response: Update SQLData properties and set a valid query
POP.012.0001.wm_thumbnailagent Error executing external process

Cause: The Thumbnail agent has failed to execute an external process to prepare thumbnails.
Response: Use the Install Administration portlet to reinstall the wm_thumbnailagent portlet.
POP.012.0001.wm_userhomefolder Empty <userAttributeName> property.

Cause: The userID is either invalid or was not found.
Response: Use the User Home folder portlet to refresh the page.
POP.012.0001.wm_version Unable to acquire publish portlet controller bean.

Cause: An internal portlet error has occurred.
POP.012.0001.wm_webclip Cannot clip from <urlName> because it is not an HTTP resource.

Cause: The Webclip portlet has failed to connect to the specified URL and get its HTML content.
Response: Check the URL specified for the Webclip portlet.
POP.012.0001.wm_wiring Can only wire portlets

Cause: An attempt was made to wire a non portlet.
Response: You can only wire portlets.

POP.012.0001.wm_xmlimport Can't create subscription for non Thing: <portalResourceIdentifier>
Cause: An invalid object is referenced in the XML import for the subscription.
Response: Correct the xml import file to not reference the invalid object. xmlImport.xml files are used to
migrate/populate portal content. Usually this file is found inside the portlet archive (*.pdp file) or inside a
package generated by the Content Migration portlet. Search within this file for the affected user or group ID
and correct or remove the entire XML element referring to it.
POP.012.0001.wm_xt_discotres_message Cannot execute ApproveMessage command against <resourceURI> because it is

not a forum message.
Cause: An attempt to execute the ApproveMessage command failed because it was executed against something
other than a forum message.
Response: Correct the invoking code to pass the URI of a forum message.
POP.012.0001.wm_xt_rule The current IDirectoryUser is null.

Cause: Rule matching has failed to load the user.
POP.012.0001.wm_xt_shortcut Unhandled object type found for the wm_xt_shortcut URL property:
<portalResourceIdentifier>
Cause: An invalid portal object type was referenced by a shortcut.
Response: Delete the specified portal object and start over.
POP.012.0001.wm_xt_skin Cannot delete <skinName> because it is the default system skin.

Cause: The specified portal skin could not be deleted.
Response: Before deleting the skin, use the Skin Administration portlet to make another skin the default.
POP.012.0001.wm_xt_webdav Cannot put on a non-container

Cause: An attempt was made to copy an item into a non-folder.
Response: Try to refresh Windows explorer. Try to publish another webDAV folder with another name and try
to access it again.
POP.012.0001.wm_xtypeview You have not specified an object to display in this portlet.

Cause: The Xtype View portlet does not have a valid target object to display.
Response: Update Xtype View portlet properties and specify a valid DBO to display.

POP.012.0002.wm_chart One of the following properties must be specified: <propertyName>

Cause: The Chart portlet is configured improperly.
Response: Specify a value for the <propertyName> property.
POP.012.0002.wm_contentrenderer Requested content was not found: <portalResourceIdentifier>

Cause: The server attempted to download invalid content.
Response: Check that content is present at the source location and can be downloaded.
POP.012.0002.wm_pghelpers No SQL Query was specified.

Cause: The server could not find a valid sql query.
Response: Using the Portlet Developer, modify the database portlet to specify a valid SQL query.
POP.012.0002.wm_sqldata Datasource is not defined

Cause: There is no defined database source for the SQL data portlet.
Response: Update SQLData properties and specify a valid datasource.
POP.012.0002.wm_version Unable to acquire target resource: <portalResourceIdentifier>

Cause: An internal portlet error has occurred.
POP.012.0002.wm_wiring <portalResourceIdentifier> is not a normal thing

Cause: An attempt was made to wire an invalid portlet instance.
Response: Delete specified portlet and locate the correct portlet.
POP.012.0002.wm_xmlimport Unable to import subscription. No prinicpal.

Cause: No subscriber is defined in the XML import for the subscription.

POP.012.0002.wm_xt_discotres_message Cannot execute ApproveMessage command because only forum moderators can
approve a message.
Cause: An attempt to execute the ApproveMessage command failed because the user who executed it had
insufficient permissions.
Response: Log on as a user with Moderator permissions on the forum.
POP.012.0002.wm_xt_skin Cannot delete <skinName> because it is the base system skin.

Cause: The specified portal skin could not be deleted.
Response: The base portal skin cannot be deleted because it is used as a parent for all other portal skins.
POP.012.0003.wm_commonsearchresults Failed to parse the max search results setting of <specifiedMaxResultsSize>,

using default of <defaultMaxResultsSize>
Cause: The common search code is attempting to build a search query object from a query string that was
passed into it. The query string supplied contains an invalid value for the 'maxResults' setting. The warning
message gets written to the logs and the process continues with the default maxResults value.
Response: Make sure the portlet that invoke the API supplies a valid number for the 'maxResults' setting in the
search query string. Typically, the end user would not cause this scenario because the wm_commonsearchbar
portlet that usually builds the query string validates the maxResults field before allowing the submission of
the search form.
POP.012.0003.wm_discotres_messagewizard The request cannot be sent because none of the forum administrators or
moderators have a registered e-mail address. Contact the Portal Administrator address this problem.
Cause: An attempt to request the retraction of a form message failed because no one to whom the request
should be sent has registered an e-mail address for notifications.
Response: Contact a portal administrator to request that forum moderators and administrators have e-mail
addresses registered so they can receive retraction requests.
POP.012.0003.wm_shelladmin The URI <portalResourceIdentifier> does not identify a valid shell.

Cause: The shell instance is not a valid portal shell object type.
Response: Restart the Portal server to flush its internal caches.
POP.012.0003.wm_skinadmin The URI <portalResourceIdentifier> does not identify a valid skin.

Cause: The skin instance is not a valid portal skin type.
Response: Restart the Portal server to flush its internal caches.

POP.012.0003.wm_sqldata Invalid Params Specification: <parameterValue>

Cause: The SQL query parameter has an invalid type.
Response: Check the SQL query parameters passed in. Check, for example, that no strings are passed where
integers are expected.
POP.012.0003.wm_wiring Can only wire portlets within folder

Cause: An attempt was made to wire portlets from different pages.
Response: Only portlets on the same page can be wired together.
POP.012.0003.wm_xmlimport Unable to import subscription. Could not acquire uri for principal: <userOrGroupName>
Cause: The subscriber used in the XML import for the subscription no longer exists.
POP.012.0003.wm_xt_rssfeed Unable to find suitable factory for: <rssVersion>

Cause: An RSS feed has failed to parse RSS content.
Response: Choose another RSS feed.
POP.012.0003.wm_xt_webdav Operation : <webDAVFolderOperation> is not supported

Cause: An invalid operation request was made to the portal webDAV folder.
Response: Try to refresh Windows Explorer.
POP.012.0004.wm_contentserviceadmin Content service not found: "<itemName>".

Cause: The content service is no longer valid.
Response: If you can't reconfigure the offending content service by using the Content Service Admin portlet
call Customer Care for a reset directive.
POP.012.0004.wm_discotres_messagewizard The request cannot be sent because an error occurred e-mailing the forum
administrators or moderators. Contact the Portal Administrator address this problem.
Cause: An attempt to request the retraction of a form message failed because some other error occurred either
in formatting the message or in sending it via SMTP.
Response: Check the settings of the E-mail Administration portlet (located in the Portal Configuration section
of the Administration Dashboard) to ensure that the SMTP Host and Port settings identify a working SMTP
server.

POP.012.0004.wm_shelladmin Cannot delete <shellName> because it is the default system shell.
Cause: The default portal shell cannot be deleted.
Response: Use the Shell Administration portlet to make another shell the default, and then delete the first shell.
POP.012.0004.wm_xmlimport Unable to import subscription. Could not acquire thindID for principal: <userOrGroupName>
Cause: The subscription source used in the XML import for the subscription no longer exists.
POP.012.0004.wm_xt_webdav Malformed destination: <folderName>

Cause: The server encountered an invalid target folder.
to access it again.
POP.012.0005.wm_contentserviceadmin Cannot remove default content service.

Cause: The default content service may not be deleted.
Response: Do not attempt to delete the default content service.
POP.012.0005.wm_shelladmin Cannot delete <shellName> because it is the base system shell.

Cause: The shell could not be deleted because it is a parent shell for other deployed shells
Response: The Portal server explicitly disallows deletion of the base shell. The base shell is installed during
portal initialization and is identified by the alias. The operation to alter a base portal shell can be performed
only by an experienced portal engineer.
POP.012.0005.wm_xmlimport Unable to locate command: <portalCommandName>

Cause: An invalid or non-existing command is referenced in the XML import file.

POP.012.0005.wm_xt_webdav writeHeader not supported for: <folderName>

Cause: An invalid operation request was made to the webDAV folder.
to access it again.
POP.012.0009.wm_installadmin Cannot download component from "<itemName>".

Cause: The server was unable to locate the uploaded component.
Response: Verify that the component exists and then try to upload it again.
POP.012.0010.wm_clusteradmin Segment not found: "<itemName>".

Cause: The cluster information is corrupted.
Response: Verify that the cluster.xml file is a valid xml file by opening it with an xml file utility. Optionally,
revert to the cluster.xml.bak file created after every modification.
POP.012.0010.wm_installadmin An error occurred receiving the uploaded file.

Cause: The server was unable to locate the uploaded component.
Response: Verify that the component exists and then try to upload it again.
POP.012.0011.wm_clusteradmin Role not found: "<itemName>".

POP.012.0011.wm_installadmin Invalid component location: "<itemName>".

Cause: The server cannot deploy a component from an unknown location.
Response: When using the Install Administration Portlet, provide the location from which the portlet is to be
deployed. Remote locations require a complete path (FTP, HTTP, and so forth).
POP.012.0012.wm_clusteradmin Server not found: "<itemName>".


POP.013.0005 This item is either inactive or deleted and can not be viewed.
Cause: The item is deleted but has not yet been purged.
Response: Use the Deleted Items Administration portlet to remove the deleted items completely from the user
interface.


CHAPTER 12
webMethods Process Run Time (PRT)
PRT.0101.0024 *** Error trying to encode the pipeline for step-level audit logging on step <stepID>: <exception>
Cause: Unable to encode pipeline for audit logging.
Response: Check the exception for details.
PRT.0101.0026 Custom logging: cannot find value for <documentName>.<fieldName> (tried path <path>)
Cause: Unable to get the field using the specified path.
Response: Make sure the field and path are correct.
PRT.0101.0028 Custom logging: cannot convert <className> to logging type <fieldType> (value <fieldValue>)
Cause: Failed to do custom fields logging because the type of the field value cannot be determined.
Response: Check that the custom field value is the correct field type.
PRT.0101.0029 *** Error trying to push audit log context: <exception>

Cause: Unable to add audit log context.
PRT.0101.0030 *** Error trying to pop audit log context: <exception>

Cause: Unable to remove audit log context.
PRT.0101.0031 *** Error publishing single log event <pipeline>: <exception>

Cause: Unable to publish the log document for audit logging.

CHAPTER 12 webMethods Process Run Time (PRT)
PRT.0101.0032 *** Error publishing <numberOfLogEvents> log events w/ header <pipeline>: <exception>
Cause: Unable to publish the log documents for audit logging.
PRT.0101.0033 *** Error generating UUID through audit subsystem: <exception>

Cause: Unable to create a new process Id.
PRT.0101.0034 No audit runtime available

Cause: Unable to perform the task because an audit runtime storage is not found.
Response: Make sure the audit runtime storage is properly setup and running.
PRT.0101.0057 *** Error encoding pipeline for transition from <sourceStepID> to <targetStepID>: <exception>
Cause: Unable to sends an output transition the over specified transport.
PRT.0101.0059 *** Error sending <documentName>: <exception>

Cause: Cannot publish the document over the transport.
Response: Check the exception in IS error logs for details.
PRT.0101.0081 *** Error checking for models in package <packageName>: <exception>

Cause: Failed to load the specified package.
PRT.0101.0084 *** Error reading model fragment <modelFile>: <exception>

Cause: Error while reading model file.
PRT.0101.0087 Error reading <modelFile>: <exception>

Response: Check the Process Exception in IS error logs for details.

PRT.0101.0112 *** Error parsing timeout reap interval <timeInterval>: <exception>
Cause: Invalid timeout or database runtime lock interval.
Response: Make sure the values for timeout or database runtime lock interval are correctly expressed in
seconds.
PRT.0101.0121 *** Error while processing timeouts: <exception>

Cause: Unable to process timeout.
PRT.0101.0122 *** Error invoking timeout for pid=<processInstanceID>, mid=<modelID>, tgt=<targetStepID>: <exception>
Cause: Failed to invoke timeout.
PRT.0101.0124 Starting absolute timeout for pid=<instanceID>, sid=<stepID>: <deadline>

Cause: Starting absolute timeout.
Response: Information only -displays that an absolute timeout is being started for the process and step with the
displayed IDs.
PRT.0101.0125 Starting relative timeout for pid=<instanceID>, sid=<stepID>: <duration>,

Cause: Starting relative timeout.
Response: Information only - displays that an absolute timeout is being started for the process and step with
the displayed IDs.
PRT.0101.0128 Canceling timeout for pid=<instanceID>, sid=<stepID>

Cause: Canceling timeouts as a result of a stop directive.
Response: Information only - displays that all timeouts are being cancelled due to a stop directive.
PRT.0101.0132 Invoking <timeoutType> timeout for pid=<instanceID>, mid=<modelID>, sid=<stepID>,threadId=threadID>,

Cause: Timeout (of type step or join) is being executed by worker thread for the corresponding process, model,
step and thread ID.
Response: Information only - displays that the following timeout (of type step or join) is being executed
(initiated by a process) for the corresponding process, model, step and thread ID.

PRT.0101.0137 Constructing timeout with pid=<instanceID>, mid=<modelID>, sid=<stepID>, timerEntry=<timerEntry>

Cause: Timeout created for the corresponding process, model, step ID, with the specified timerEntry.
Response: Information only - displays that a timeout has been created for the corresponding process, model,
step ID with the specified timerEntry.
PRT.0101.0138 Creating timout timer

Cause: Timeout created a corresponding worker thread.
Response: Information only - displays that a timeout has created a corresponding worker thread.
PRT.0101.0139 Invoking timeout timer with pid=<instanceID>, mid=<modelID>, sid=<stepID>, threadId=<threadID>,

classification=<timeoutClassification>
Cause: Timeout expired.
Response: Information only - displays that a timeout has expired.
PRT.0101.0140 <killed> step thread with pid= <instanceID>, mid = <modelID>, sid = <stepID>, threadid =<threadID>
Cause: The step thread for the corresponding process, step and thread ID has been killed by a step timeout.
Response: Information only - displays that an expired step timeout has killed its associated step thread.
PRT.0101.0140 IOException writing frag file <modelFilename>

Cause: Error while saving model file.
Response: Make sure you have write permission to the file system.
PRT.0101.0141 Creating timer event

Cause: Creating a timer event.
Response: Information only - displays that a timer event has been created.
PRT.0101.0142 Enqueuing timer event

Cause: Enqueuing a timer event.
Response: Information only - displays that a timer event has been added to the event queue.
PRT.0101.0143 <creatingOrAccessing> IS Session Object

Cause: Timeout accessed an IS service session in order to get the service thread.
Response: Information only - displays that an IS service session has been accessed in order to get the service
thread.

PRT.0101.0144 <creating> timer Entry <timeoutClassification>
Cause: Created a persistable timer entry.
Response: Information only - displays that the timer entry has been created.
PRT.0101.0150 Broker push error: <error>

Cause: Unable to sync documents with the broker.
Response: Check the errors for details.
PRT.0101.0179 (<loggerThreadID>) cannot create new instance of <modelID>

Cause: Model is not enabled.
Response: Make sure the model is enabled in Monitor.
PRT.0101.0242 No match for bizdoc

Cause: Not starting any process because we are unable to find any model that matches the bizdoc.
Response: Make sure there is a model that subscribes to this bizdoc.
PRT.0101.0243 (<loggerThreadID>) no step for document in model <modelID>

Cause: Unable to match a step to the bizdoc.
Response: Make sure at least one step in the model subscribes to this bizdoc.
PRT.0101.0251 (<loggerThreadID>) IM failed: model is disabled or non-start step

Cause: Unable to create a process instance because it is a non-start step or the model is inactive.
Response: If joining a running process, make sure it has the correct conversation ID. Otherwise, make sure the
model is enabled in Monitor.
PRT.0101.0254 *** Error fetching info for <processInstanceID> from profile store: <exception>
Cause: Unable to get TN partner profile summary.
Response: Check the TN partner profile.
PRT.0101.0256 Extended profile field <fieldID> is required in a process, but no definition is available on this server
Cause: Unable to get the extended profile field.
Response: Make sure the extended profile field is populated.

PRT.0101.0257 *** Error fetching info for field <profileFieldID> from database: <exception>
Cause: Unable to get TN extended profile field.
Response: Check the TN extended profile field.
PRT.0101.0289 (<loggerThreadID>) *** NO MATCHING STEP ***

Cause: Unable to find the step that responds to this document.
Response: Make sure a step in the model subscribes to this document.
PRT.0101.0290 (<loggerThreadID>) no step matching <document> (model <modelID>, frag <fragmentID>)

Cause: Unable to find the step that responds to this document.
Response: Make sure a step in the model subscribes to this document.
PRT.0101.0294 (<loggerThreadID>) *** NO MATCHING INPUT ***

Cause: Unable to get the input definition for this document.
Response: Make sure the document exists and is synced to the broker.
PRT.0101.0295 (<loggerThreadID>) no input matching <documentDefinition> (model <modelID>, frag <fragmentID>, step
<stepID>)
Cause: Unable to get the input definition for this document.
Response: Make sure the document exists and is synced to the broker.
PRT.0101.0300 Can not connect to the ProcessAudit database for cross referencing IDs in the PRT.
Cause: An error occurred while accessing the ProcessAudit database.
Response: Make sure that the ProcessAudit pool alias is configured and functional.
PRT.0101.0301 Error connecting to the ProcessAudit database for cross referencing IDs in the PRT
PRT.0101.0305 DELETE of cross reference failed in the ProcessAudit database for PID <processID>

PRT.0101.0307 *** Error invoking correlation svc <correlationServiceName>: <exception>
Cause: Failed to invoke the specified correlation service.
PRT.0101.0308 (<loggerThreadID>) *** NO PID FOUND ***

Cause: Failed to create a new process instance or unable to join a running process because no matching
correlation ID found.
Response: Make sure there is a model that subscribes to the triggering document, or that the correlation ID is
correct to join a running process instance.
PRT.0101.0311 (<loggerThreadID>) cannot start step <stepID>: no fragment for model <modelID> contains that step
Cause: Unable to find the step in the model fragment.
Response: Make sure generated model fragment contains this step.
PRT.0101.0315 *** Error handling transition event <processTransitionEvent>

Cause: Failed to handle process transition document.
PRT.0101.0316 Could not get process ID from conversation ID

Cause: The process ID cannot be obtained from the TN model's conversation ID. The conversation ID may be
missing or invalid.
Response: Make sure that the conversation ID exists and is valid.
PRT.0101.0317 Error joining PID <instanceID> because it is terminated already

Cause: Cannot join a process which is not running.
PRT.0101.0359 *** Error trying to step <stepID> (pid <processInstanceID>): <exception>

Cause: Unable to execute the specified step.
PRT.0101.0359 Exception while evaluating XPath expression: <conditionExpression>

Cause: The XPATH expression cannot be parsed.
Response: Verify that the XPATH expression is valid.

PRT.0101.0360 *** Error saving step context for step <stepID> (pid <processInstanceID>): <exception>
Cause: Failed to save the context of the step.
Response: Check the Exception in IS error logs for details.
PRT.0101.0374 (<loggerThreadID>) *** SERVICE EXECUTION FAILED ***

Cause: Caught a service exception. If an error handler is defined, the appropriate error action will be taken.
Otherwise, process will be marked as failed.
Response: Check Monitor for details about the failure.
PRT.0101.0376 *** Error invoking step <stepID> (<serviceName>): <exception>

Cause: Failed while executing the step. Service throws an error.
Response: If an error handler is defined, the appropriate error action will be taken. Otherwise, the process will
be marked as failed.
PRT.0101.0378 PROCESS <processInstanceID> TERMINATED ABNORMALLY; step <stepID> died with no error handler
Cause: Failure during process execution. No error handler defined for the step.
Response: Define an error handler for the step so that appropriate error action can be taken.
PRT.0101.0387 (<loggingThreadID>) missing content for document <documentName>

Cause: Unable to get the document from the publish output due to missing or corrupted document object.
Response: Make sure the document is in the publish output pipeline.
PRT.0101.0391 *** Error considering output <outputNumber> of <totalNumberOfOutputs> on step <stepID>: <exception>
Cause: Error while sending output documents.
PRT.0101.0400 *** Error on transition from <stepID>: <exception>

Cause: Failed to evaluate the condition associated with this output possibly due to invalid condition
parameter.

PRT.0101.0407 *** Error evaluating condition <condition> on step <stepID>: <exception>
Cause: Failed to evaluate the condition associated with this output possibly due to invalid condition
parameter.
PRT.0101.0409 Invoking service <serviceName>

Cause: Invoking service.
PRT.0101.0410 Error accessing <exceptionMessage>, <processID> from storage <partnerLinkName>

Cause: Could not access endpoint reference document from storage.
Response: Make sure that binding information for the Web service is set-up correctly.
PRT.0101.0411 Error accessing global data in pipeline

Cause: Global Data is not properly copied into the pipeline.
Response: Verify that the process was generated properly.
PRT.0101.0412 Cannot execute step <stepID> because the process was terminated already
Cause: Cannot execute step because the process was terminated.
Response: Check for incorrect use of the correlation service.
PRT.0101.0415 After step invoke outPipe=<pipeline>

Cause: Displays the result of the service execution.
Response: Information only - displays the input pipeline for a Web service invoke after service execution.
PRT.0101.0416 After transformation for rpcInvoke, inPipe=<pipeline>

Cause: Displays the result of the input pipeline transform.
Response: Information only - displays the input pipeline for a Web service invoke (using SOAP-RPC) after
transformation.
PRT.0101.0418 *** Error parsing wsdl for web service interaction, detail=<errorMessage>
Cause: A WSDLException occurred while processing the WSDL. The Web service endpoint may be invalid.
Response: Make sure the WSDL contains a valid endpoint reference for the Web service.

PRT.0101.0419 *** Error handling web service interaction, detail=<errorMessage>

Cause: An error occurred while parsing the WSDL for the Web service invocation.
Response: Make sure the WSDL contains a valid endpoint reference for the web service.
PRT.0101.0420 PID <processID>: No variable type specified for web service invoke step SID=<stepID> using dynamic binding
Cause: The Web service could not be invoked because its endpoint reference is undefined.
Response: Make sure the specified field contains a valid endpoint reference for the Web service.
PRT.0101.0421 PID <processID>: The step definition for SID=<stepID> is malformed

Cause: The WSDL URI for the Web service is invalid.
Response: Make sure the WSDL URI is valid.
PRT.0101.0426 Failure invoking web service via deployment time binding using a wsdl file. PID <processID>: SID <stepID>
Cause: The WSDL file could not be processed and may not be accessible.
Response: Make sure that the WSDL file is in the proper location and is accessible.
PRT.0101.0427 *** Error parsing endpoint reference document from pipeline, reason=<errorMessage>,
detail=<exceptionStack>
Cause: An error occurred while parsing the endpoint reference for the Web service. The endpoint may be
invalid.
Response: Make sure the Web service endpoint in the pipeline is valid.
PRT.0101.0427 Failure parsing endpoint reference document from pipeline. Reason: <partnerLinkName>. Detail:
<errorMessage>
Cause: The endpoint reference document could not be processed.
Response: See the detailed error message for specific information.
PRT.0101.0428 *** Workflow Error: <errorMessage>

Cause: An error occurred while executing a Workflow step.
PRT.0101.0428 Workflow Error: <errorMessage>

Cause: An error occurred while executing a Workflow step.

PRT.0101.0434 *** Error assembling pipeline for timeout on step <stepID>: <exception>
Cause: Cannot create transition pipeline for the specified step.
PRT.0101.0448 <timeoutValue> starting Step timeout

Cause: Starting join timeout.
Response: Information only - displays that a join timeout has been started.
PRT.0101.0449 <timeoutValue> starting join timeout

Cause: Starting step timeout.
Response: Information only - displays that a step timeout has been started.
PRT.0101.0468 Something just tried to dequeue an event with a null ID

Cause: Unable to dequeue metadata.
Response: Check the IllegalArgumentException in IS error logs for details.
PRT.0101.0469 Error encountered: Document with duplicate correlation ID submitted.

Cause: An error occurred when a document with a duplicate correlation ID was found.
Response: Make sure each correlation ID is unique.
PRT.0101.0510 *** Error checking enablement for model <modelID>: <exception>

Cause: Failed while checking enablement state of the model.
PRT.0101.0511 Can not initialize jdbc runtime storage for PRT. Reverting to repo. Make sure ProcessAudit or PRT runtime
pool is configured properly
Cause: Failed to establish DB for PRT storage; using repo instead.
Response: Check the Process Audit and PRT Associated Pool Alias configurations.
PRT.0101.0512 Database Storage problem. Exception: <exception>

Cause: Exception executing SQL statement.
Response: Check for incorrect database setup.

PRT.0101.0514 Failure saving configuration file: <filename>

Cause: An error occurred while saving the Web service binding file. The user may not have the correct access to
the directory.
Response: Make sure that the user has proper read/write access to the directory.
PRT.0101.0515 Failure saving configuration value: <errorMessage>, <filename>

the directory.
PRT.0101.0516 Failure saving configuration values: <errorMessage>

the directory.
PRT.0101.0517 Failure writing configuration to file: <filename>

the directory.
PRT.0101.0518 Configuration file does not exist: <filename>

Cause: The Web service binding file does not exist. The user may not have the correct access to the directory.
PRT.0101.0523 Error encountered in accessing file: <filename>

Cause: The WSDL file for the Web service could not be accessed. The file may not exist, or it may be in the
wrong directory location.
Response: Make sure that this file exists and has been deployed to the correct directory location.
PRT.0101.0528 The wsdl at: <wsdlFile> is malformed; it provides no binding information

Cause: The WSDL file does not contain an endpoint reference for the Web service.
Response: Make sure that the WSDL file provides a valid endpoint reference for the Web service.

PRT.0101.0529 The wsdl at: <wsdlFile> is malformed; it provides no definition information
Cause: The WSDL file does not contain a definition for the Web service.
Response: Make sure to use a well-formed WSDL file that contains a definition for the Web service.
PRT.0101.0530 The wsdl at: <wsdlFile> is malformed; it provides no service information

Cause: The WSDL file does not contain Web service information.
Response: Make sure to use a well-formed WSDL file that contains the Web service information.
PRT.0101.0532 Error encountered in accessing wsdl configuration file for package <packageName>
Cause: The WSDL file for the Web service could not be accessed.
Response: Make sure that the WSDL file exists and has been deployed to the generated package.
PRT.0101.0533 Failure accessing package name <packageName>. Detail: <errorMessage>

Cause: An error occurred while accessing the model package.
Response: Make sure that the model has been generated and the corresponding namespace package has been
created.
PRT.0101.0600 web service invoke <serviceName>

Cause: Invoking Web service.
Response: Information only - displays that the PRT dispatcher is performing a Web service invoke.
PRT.0101.0601 web service request/reply <functionName>

Cause: Performing Web service request/reply.
Response: Information only - displays that the PRT dispatcher is processing a Web service request/reply.
PRT.0101.0604 soapStatus=<soapStatus>
Cause: SOAP Status of Web service invoke.
Response: Information only - displays the SOAP status returned form a Web service invoke.
PRT.0101.0610 Could not determine trigger

Cause: Could not determine what trigger was used in Model.

PRT.0101.0611 Could not determine doc type

Cause: Could not determine the document type to be used in a Web service interaction.
PRT.0101.0612 Missing <messageName>

Cause: The document used in a Web service interaction was not available in the pipeline or Global Data.
PRT.0101.0613 Could not identify model/fragment from trigger <triggerName>

Cause: Could not determine the model/fragment from the following trigger.
PRT.0101.0620 No SOAP operations could be parsed from pipeline <pipeline>

Cause: No SOAP operations were available in the pipeline to perform a Web service invoke.
Response: Check that the wsdl used for a Web service interaction is valid.
PRT.0101.0621 No SOAP operations QNames could be parsed from pipeline <pipeline>

PRT.0101.0623 No binding documents could be parsed from pipeline <pipeline>

Cause: No SOAP binding data was available in the pipeline to perform a Web service invoke.
PRT.0101.0624 Encountered SOAP-FAULT invoking web service: <address>

Cause: A SOAP-FAULT was returned from the Web service invoke.
Response: Check the exception for details. This is an error condition encountered when invoking a Web service.
PRT.0101.0625 Encountered error parsing SOAP document from pipeline <pipeline>. Please confirm that you have correctly
specified the web service to be invoked, including authentication and partnerTo.
Cause: The SOAP Message could not properly be parsed from the output pipeline from a Web service invoke.
Response: Check the exception for details. This condition is caused by an internal failure in the IS SOAP stack.

PRT.0101.0626 Encountered error parsing SOAP header from pipeline <pipeline>. Please confirm that you have correctly
Cause: The SOAP Header could not properly be parsed from the output pipeline from a Web service invoke.
PRT.0101.0627 Encountered error parsing SOAP header entries from pipeline <pipeline>. Please confirm that you have
correctly specified the web service to be invoked, including authentication and partnerTo.
Cause: The SOAP Header entries could not properly be parsed from the output pipeline from a Web service
invoke.
PRT.0101.0628 Encountered error parsing SOAP body from pipeline <pipeline>. Please confirm that you have correctly
Cause: The SOAP Body could not properly be parsed from the output pipeline from a Web service invoke.
PRT.0101.0629 Encountered error parsing SOAP body entries from pipeline <pipeline>. Please confirm that you have
Cause: The SOAP Body entries could not properly be parsed from the output pipeline from a Web service
invoke
PRT.0101.0632 Encountered error linking with web service interaction <exceptionMessage>. Please confirm that you have
correctly specified the partnerTo name.
Cause: The partnerTo name specified to the Web service invoke was incorrect, and the PRT cannot associate it
with an endpointReference.
Response: An incorrect partnerTo name was used in either the model or the assign service.
PRT.0101.0633 Encountered error linking with web service interaction <errorMessage>

Cause: The Web service could not be associated with its partner link name.
Response: Make sure that you have correctly specified the partnerTo name.

PRT.0101.0640 Encountered fatal error invoking web service <exceptionMessage>. Please confirm that you have a valid
installation.
Cause: A fatal error occurred in performing a Web service invoke.
Response: Check the exception for details. This occurs when the endpointReference in the pipeline to be used
for the invoke is not valid or malformed.
PRT.0101.0641 unable to access SOAP-FAULT information <exceptionMessage>

Cause: The PRT was unable to parse the SOAP-FAULT information from the return of a Web service
invocation.
Response: The invoked Web service returned a soapStatus of 1 (indicating failure), while failing to package the
fault information as a SOAP-FAULT.
PRT.0101.0642 unable to access SOAP-DATA information <exceptionMessage>

Cause: The PRT was unable to parse the SOAP-DATA information from the return of a Web service invocation
PRT.0101.0643 web service invoke input pipe=<pipeline>

Cause: The input pipeline for the Web service invoke is as follows.
Response: Information only - displays the input pipeline to be used for the Web service invoke.
PRT.0101.0644 web service invoke soapRPC signature: method=<method>, + "address=<address>,

auth=<authorizationSignature>, inputMessage=<inputMessage>, outputMessage=<outputMessage>,
inputSignature=<inputSignature>, " + "outputSignature=<outputSignature>, soapAction=<soapAction>
Cause: The PRT performed the Web service invoke over SOAP-RPC using the following signature.
Response: Information only - displays the signature used to invoke a Web service over SOAP-RPC.
PRT.0101.0645 after web service invoke, outPipe=<pipeline>

Cause: The output pipeline from the Web service invoke is as follows.
Response: Information only - displays the output pipeline from the Web service invoke.
PRT.0101.0646 with web service response parameters, outPipe=<pipeline>

Cause: The output pipeline with the response parameters from the Web service invoke is as follows.
Response: Information only - displays the response parameters for the Web service invoke in the output
pipeline.

PRT.0101.0647 with SOAP-FAULT, outPipe=<pipeline>
Cause: The output pipeline from the Web service invoke (where a FAULT was encountered) is as follows.
Response: Information only - displays the output pipeline from the Web service invoke.
PRT.0101.0648 Encountered error connecting to web service <webServiceName>: Detail <errorMessage>. Please confirm
that you have correctly specified the web service to be invoked.
Cause: The Web service could not be invoked. It may not be accessible or may not be correctly identified.
Response: Make sure the Web service is valid and functioning.
PRT.0101.0650 Error evaluating XPath expression: <XpathExpression>

Cause: A general error was encountered while evaluating the provided XPath expression.
Response: The XPath evaluator encountered a general error while parsing the provided XPath expression. Most
likely the XPath expression was invalid.
PRT.0101.0651 Null IData provided for extracting the XPath context: <Empty Idata will be created>
Cause: The IData stack containing the XPath context (the data to be extracted using an XPath evaluation) was
null.
Response: No XPath context/global data was provided for the XPath expression to be evaluated.
PRT.0101.0652 Error: element <inputValue> is not a Deadline: <exception>

Cause: The provided XML element was not of type xsd:date or xsd:datetime
Response: A non-deadline (xsd:date or xsd:datetime) value was used in evaluating an XPath deadline
expression.
PRT.0101.0653 Error: element <InputValue> is not a Duration: <exception>

Cause: The provided XML element was not of type xsd:duration.
Response: A non-duration (xsd:duration) value was used in evaluating an XPath duration expression.
PRT.0101.0654 Error: element <InputValue> is not a TimeStamp: <exception>

Cause: The provided XML element was not of type xsd:timestamp.
Response: A non-timestamp (xsd:timestamp) value was used in evaluating an XPath timestamp expression.

PRT.0101.0700 Adding thread to thread table, thread id=<threadID>

Cause: Added a thread with the following thread ID to the PRT's internal thread table.
Response: Information only - displays the thread ID for a thread added to the PRT's internal table.
PRT.0101.0701 Getting thread from thread table, thread id=<threadID>

Cause: Retrieved a thread with the following thread ID from the PRT's internal thread table.
Response: Information only - displays the thread ID for a thread retrieved from the PRT's internal table.
PRT.0101.0720 Using IData to construct the XPath context: <pipeline>

Cause: The following IData stack containing the XPath context (the data to be extracted using an XPath
evaluation) was used for XPath evaluation.
Response: Information only - displays the XPath context to be used for an XPath evaluation.
PRT.0101.0800 Parameter <objectName> is missing

Cause: The specified Web service object is missing.
Response: Make sure the object exists.
PRT.0101.0801 Parameter <objectName> is of incorrect type

Cause: The specified Web service object is of the wrong type.
Response: Make sure the object is of the correct type.
PRT.0101.0802 Parameters <objectName>, '$filestream' and '$filedata' are all missing. One of these must not be null.
Cause: XML filestream or filedata information is missing from the WSDL file.
Response: Make sure the WSDL file is valid and accessible.
PRT.0101.0829 General XML Error: <exceptionMessage>

Cause: An error occurred while parsing the XML.
PRT.0101.0850 Invalid BOOLEAN value <booleanValue> for variable <variableName>; must be 0 or 1

Cause: An invalid BOOLEAN value caused an error when a header was added to a SOAP message.
Response: Make sure that the SOAP message contains a valid header.

PRT.0101.0852 An Exception was thrown in the server
Cause: An error occurred while processing a SOAP message.
Response: Make sure that the SOAP message is valid.
PRT.0101.0856 The server cannot execute the requested SOAP utility; required parameter <objectName> is missing or
invalid
Cause: A missing or invalid object caused an error during processing of a SOAP message.
Response: Make sure that the object exists in the pipeline.
PRT.0101.0857 One or more header entries were not understood by the SOAP processor
Cause: The SOAP processor aborted processing the SOAP message because of a problem with the header.
Response: Make sure the header entries of the SOAP message are valid.
PRT.0101.0858 Parameter <objectName> must be a valid soapData

Cause: The SOAP message cannot be retrieved because the specified object is not recognized as a SOAP object.
Response: Make sure that the pipeline contains a valid SOAP message.
PRT.0101.0859 Parameter <parameterName> is not one of the valid data types: <dataType>
Cause: An error occurred while processing a SOAP message because the specified object is not of a valid data
type.
Response: Make sure that the SOAP message object is of a valid data type.
PRT.0101.0899 General SOAP Error: <exceptionMessage>

Cause: An error occurred while processing the SOAP message.
PRT.0101.0900 Type mismatch in assigning value <inputValue> for pid <instanceID>, property <property>
Cause: Type mismatch in BPEL assign.
Response: Check that the mapping performed in the assign step is valid. Mapping is not typesafe.
PRT.0101.0901 can not convert String <inputValue> to appropriate type

Cause: Cannot convert string to specified type in BPEL assign.
Response: Check that the mapping performed in the assign step is valid. Mapping is not typesafe.

PRT.0101.0902 Can not get type for pid <instanceID>, variable <variableName>, part <part>, query <XpathQuery>
Cause: Unable to find type of the field for the record using the specified part and Xpath query.
Response: Check that the type used in the part and XPath query is defined in your IS instance. This can occur
when the field or record are not defined in the IS instance to which the corresponding process has been
deployed.
PRT.0101.0903 Can not get type for record <ISDocument> query <XpathQuery>
Cause: Unable to find type of the field for the record using the specified part and Xpath query.
Response: Check that the type used in the part and XPath query is defined in your IS instance. This can occur
when the field or record are not defined in the IS instance to which the corresponding process has been
deployed.
PRT.0101.9123 No value was supplied for the required parameter <parameterName>.

Cause: Due to missing or corrupted parameter, the value was not obtained.
Response: Make sure that the parameter object exists.
PRT.0101.9124 An invalid value was supplied for the required parameter <key>. The bad value was <value>.
Cause: Value of the specified key is invalid.
Response: Make sure the value is the specified type.
PRT.0101.9125 Service <serviceName> failed

Cause: Caught a service exception.
Response: Check the ServiceException in IS error logs for details.
PRT.0101.9135 <error> <readingOrWriting> timer Information to get

Cause: Error accessing a timer entry from the repository.
Response: Do not use the repository for persistence.
PRT.0101.9135 Cannot read frag file <modelFilename>: the file does not exist.
Cause: Error while reading model file; file does not exist.
Response: Make sure the model has been generated correctly.

PRT.0101.9136 <error> <readingOrWriting> timer Information to set
Cause: Error updating a timer entry in the repository.
Response: Do not use the repository for persistence.
PRT.0101.9136 Cannot read frag file <modelFilename>: the file is not readable.
Cause: Error while reading model file; file is not readable.
Response: Check the file permissions.
PRT.0101.9137 Malformed frag file <modelFileName>: the file does not contain the 'fragment' key.
Cause: Unable to read the model file; it may be corrupted.
Response: Regenerate the model.
PRT.0101.9138 IOException reading frag file <modelFileName>

PRT.0101.9139 Cannot write frag file <modelFilename>: the file already exists and is not writeable.
Cause: Error while saving model file; file already exists.
Response: Check the file permissions.
PRT.0101.9151 Cannot rebind role <roleName> from partner ID <currentProfileID> to partner ID <documentProfileID>
Cause: Unable to add TN sender or receiver role because the current public role information indicates a
different partner ID.
Response: Make sure the sender or receiver matches the partner ID, then restart the process.
PRT.0101.9162 RepositoryException setting model <modelID> to <notExistOrExist>

Cause: Unable to set the model as <exists|not exists> due to a failure while accessing PRT repository storage.
PRT.0101.9169 RepositoryException trying to fetch status for process <processInstanceID>

Cause: Unable to get the status of this process instance due to a failure while accessing PRT repository storage.

PRT.0101.9170 RepositoryException trying to save and unlock status for process <processInstanceID>
Cause: Unable to save the status of the process instance due to a failure while accessing PRT repository storage.
PRT.0101.9171 RepositoryException trying to release status for process <processInstanceID>

Cause: Unable to unlock the status of the process instance due to a failure while accessing PRT repository
storage.
PRT.0101.9172 Pop from suspension list for process <processInstanceID> failed: RepositoryException on <readOrWrite>
Cause: Error while removing process instance to suspension list.
PRT.0101.9173 Push from suspension list for process <processInstanceID> failed: RepositoryException on <readOrWrite>
Cause: Unable to write process instance to the suspension list.
PRT.0101.9174 Failed fetching model ID for process ID <processInstanceID>

Cause: Unable to get model ID from this process instance from the repository.
PRT.0101.9175 Repository error trying to create process context (pid <processInstanceID>, mid <modelID>, stack
<processData>)
Cause: Error while writing this process instance to repository.
PRT.0101.9177 RepositoryException getting stack for process <processInstanceID>

Cause: A failure occurred while getting the process instance from PRT repository storage.
PRT.0101.9179 Failed to unlock state for step <stepID>; process <processInstanceID> does not exist in the repo
Cause: Cannot save the state of the step because the process instance either has never been stored or has been
removed from PRT repository storage.
Response: Make sure that the process instance has started and is properly stored.

PRT.0101.9182 Failed to unlock queue for step <stepID>; process <processInstanceID> does not exist in the repo
Cause: Cannot release the step queue because the process instance either has never been stored or has been
removed from PRT repository storage.
Response: Make sure that the process instance has started and is properly stored.
PRT.0101.9184 Failed creating context for process <processInstanceID> to enqueue <targetStepID>

Cause: While writing document to the step, the process context cannot be created possibly due to a corrupted
PRT repository storage.
Response: Restart the Integration Server.
PRT.0101.9185 Non-unique event ID on incoming <targetStepID>; cannot enqueue event for process <processInstanceID>
Cause: A document with the same document ID is found in PRT repository storage while writing the
document to the step.
Response: Make sure the document is not a duplicate.
PRT.0101.9187 Failure trying to dequeue event <eventID>: process <processInstanceID> does not exist in the repo
Cause: Unable to find the process instance in the repository.
PRT.0101.9188 Failure trying to remove repo entry for event <eventID> in process <processInstanceID>
Cause: Document entry cannot be found in the repository, therefore, it was not removed.
PRT.0101.9190 Failure trying to update iteration info with <processInstanceID>:<iteration>

Cause: Error while updating process instance iteration.
PRT.0101.9191 Failure trying to get iteration info for <processInstanceID>

Cause: Cannot load the process instance iteration from the repository.
PRT.0101.9192 Failure trying to delete iteration info for <processInstanceID>:<iteration>

Cause: Unable to delete process instance iteration from the repository.

PRT.0101.9193 No lock for Global Data for pid <instanceID> and variable <variableName>
Cause: Global data is not locked but attempted to be changed.
Response: LockGlobalData is not called in the assign service.
PRT.0101.9195 Can not acquire lock for Global Data for pid <instanceID>
Cause: Cannot get Lock for Global Data.
Response: Determine whether another step in the process currently has a lock on global data.
PRT.0101.9196 No lock for Global Data for pid <instanceID> and stepid <stepID>
Cause: Cannot get Lock for Global Data.
Response: Determine whether another step in the process currently has a lock on global data.
PRT.0101.9197 No GlobalData exists for pid <instanceID>, variable <variableName>, part <partName> and query
<xpathQuery>
Cause: Field is not present in Global Data when using BPEL assign.
Response: Make sure the data exists.
PRT.0101.9198 No description of global data available in fragment for pid <instanceID> and variable <variableName>
Cause: The model was not generated properly or there is no such variable for the process.
Response: Make sure the variable is defined in Modeler.
PRT.0101.9199 Type mismatch in assigning value <inputValue> for pid <instanceID>, variable <variableName>, part <Part>,
query <XpathQuery>
Cause: Type mismatch in BPEL assign.
Response: Please verify your source and target data.
PRT.0101.9200 Failure trying to execute correlation service <serviceName>

Cause: Failed to execute the specified correlation service.
PRT.0101.9203 Failure trying to start process <processInstanceID> at step <stepID>

Cause: Unable to start a step.

PRT.0101.9204 The CID returned from <correlationService> is too long. CID length is <correlationServiceIDLength>;
maximum allowed is <maxCorrelationServiceIDLength>
Cause: The conversation ID has exceeded the maximum allowed length.
Response: Shorten the conversation ID and rerun the process.
PRT.0101.9205 Can not join a process <processInstanceID>. It is not in running state

Cause: Joins are not allowed on process instances that are not of running status.
Response: Change the state to running, or start a new process instance.
PRT.0101.9215 Cannot start process <processInstanceID>: unable to determine the appropriate model
Cause: The model ID had not been properly stored in PRT storage.
Response: Check that the storage is working properly and rerun the process.
PRT.0101.9216 Cannot start process <processInstanceID> with model <modelID> at step <stepID>: there is no fragment
defined that contains that step
Cause: PRT fragment does not contain the definition for the specified step.
Response: Check that the step is properly generated in the PRT fragment. If not, regenerate the process.
PRT.0101.9217 Cannot start process <processInstanceID> at step <stepID>: there is no such step defined in fragment
<fragmentID>
Cause: PRT fragment does not contain the definition for the specified step.
Response: Check that the step is properly generated in the PRT fragment. If not, regenerate the process.
PRT.0101.9228 Missing ConversationID for call to getInstanceId()

Cause: Cannot start a process because conversion ID was not present in the TN document envelope.
Response: Make sure that the conversation ID is properly defined and extracted.
PRT.0101.9229 Model <modelID> was specified, but there is no step in this model for a bizdoc of type <documentName>
Cause: Cannot find any steps in the model that subscribes to this document.
Response: Make sure the model has a step that subscribes to this document.

PRT.0101.9230 Couldn't start process. Either the model is disabled or this document targets a non-start step.
Cause: Process cannot be started either because the model is disabled or the step subscribing to this document
is not a start step.
Response: Make sure the model is enabled and that the step that subscribes to this document is a start step.
PRT.0101.9231 No ConversationID available; PRT bizdoc processing fails

Cause: Cannot start a new process or join an existing process because conversation ID was not present in the
TN document envelope.
Response: Make sure that conversation ID is properly defined and extracted.
PRT.0101.9232 *** Bad filter: <exception>

Cause: Unable to evaluate the filter while matching the supplied document to a fragment and step.
Response: Validate the filter expression.
PRT.0101.9232 Database error trying to create new process instance <processInstanceID>

Cause: Encountered a SQL exception while creating the new process instance.
Response: Check your database configuration. Make sure it is running and has proper read/write permission.
PRT.0101.9243 Storage.getStatus() with lock returned null status. PID <processInstanceID>

Cause: Unable to determine the status of the process possibly due to an error while retrieving from the PRT
storage.
Response: Check that the PRT storage is configured and running properly.
PRT.0101.9244 PID <processInstanceID>: Cannot <action> process; status is <status>

Cause: The process instance has one of the following statuses: STAT_UNKNOWN, STAT_RUNNING,
STAT_SUSPENDED, STAT_FAILED, STAT_CANCELLED, or STAT_DONE. Because the process instance is
in one of these states, it cannot run the requested action. The requested action will be one of: START,
SUSPEND, RESUME, CANCEL, FAIL, RESTART, QUIET, or DONE.
Response: Make sure the action is allowed on processes with the specified status.
PRT.0101.9245 PID <processInstanceID>: Bad command RESTART; target step is missing

Cause: Unable to restart the process because of missing or corrupted target step ID in the pipeline.
Response: Check the pipeline then restart.

PRT.0101.9246 PID <processInstanceID>: Bad command RESTART; pipeline is missing
Cause: Unable to restart the process because of a missing or corrupted pipeline.
PRT.0101.9247 PID <processInstanceID>: Bad command RESTART; pipeline is corrupt

Cause: Unable to decode pipeline data due to a corruption.
PRT.0101.9248 PID <processInstanceID>: Bad command RESTART; pipeline is missing /ProcessData

Cause: Unable to restart the process because of missing or corrupted ProcessData object in pipeline.
PRT.0101.9249 PID <processInstanceID>: Bad command RESTART; pipeline is missing /ProcessData/LastEvents

Cause: The process instance was not restarted because the pipeline is missing.
Response: Make sure that the pipeline is properly logged.
PRT.0101.9250 PID <processInstanceID>: Bad command RESTART; RestartParameters is missing

Cause: Cannot restart the process instance because some or all of the restart parameters are missing.
Response: Make sure that all of the restart parameters are present in the pipeline.
PRT.0101.9251 PID <processInstanceID>: restart failed because the supplied pipeline contains an invalid ProcessInstanceID
<oldProcessInstanceID>
Cause: Unable to restart due to invalid process instance ID.
PRT.0101.9253 MID <modelID>: Cannot restart process; frag <fragmentID> step <stepID> does not define bizdoc
<documentName> as input
Cause: Process cannot be restarted because the target step does not define the document as an input.
Response: Make sure that the target step has the document as an input.
PRT.0101.9254 PID <processInstanceID>: failed to restart at step <stepID> because at least one valid event is needed in path
/ProcessData/LastEvents/ of the supplied pipeline <pipelineContent>
Cause: Process cannot be restarted because all documents in the pipeline have been removed.
Response: Start a new instance of the process.

PRT.0101.9255 MID <modelID> Failed to restart the process because Model <modelID> is not enabled
Cause: Process cannot be restarted because the model is disabled.
Response: Enable the model and restart again.
PRT.0101.9262 PID <processInstanceID>: Could not get a connection in <methodName>

Cause: An error occurred while trying to connect to PRT DB storage.
Response: Make sure that PRT DB storage is properly configured and running.
PRT.0101.9263 PID <processInstanceID>: Update thread count failed

Cause: An error occurred while communicating with PRT DB storage.
Response: Make sure that PRT DB storage is properly configured and running.
PRT.0101.9274 PID <processInstanceID>: Cannot execute step <stepID> because the process was terminated already
Cause: The step was not executed because the process instance is in a failed, cancelled, or done state.
Response: Start a new instance of the process.
PRT.0101.9285 Could not create TN facade

Cause: Unable to create a TN implementation.
PRT.0101.9286 Could not handle doc output

Cause: Error while handling the output of a bizdoc.
PRT.0101.9287 bizdoc_output() failed because pipeline object <documentName> is not a TN bizdoc object
Cause: The specified document is the wrong type.
Response: Make sure the document is a TN document.
PRT.0101.9301 Error connecting to the ProcessAudit database for cross referencing IDs in the PRT
Cause: Unable to perform ID correlation due to an error while connecting to PRT DB storage.

PRT.0101.9305 DELETE of cross reference failed in the ProcessAudit database for PID <processInstanceID>
Cause: A connection to the Process Audit DB cannot be established.
Response: Make sure that Process Audit DB is properly configured and running.
PRT.0101.9314 *** Error invoking step dispatch service: <exception>

Cause: Unable to start a step.
PRT.0101.9327 handlePublishedInput: Could not determine trigger

Cause: Trigger not found in the input pipeline.
PRT.0101.9328 handlePublishedInput: Could not determine doctype

Cause: Document type not found in the input pipeline.
PRT.0101.9329 handlePublishedInput: Missing <documentName>

Cause: Document not found in the input pipeline.
PRT.0101.9330 Could not identify model/fragment from trigger <triggerName>

Cause: Model or fragment ID is missing.
Response: Make sure the trigger contains the model and fragment ID.
PRT.0101.9340 Bad join expression; invalid character <character>

Cause: Specified character is not allowed in the join expression.
Response: Verify that the join expression is valid.
PRT.0101.9341 Bad XOR join specification <xorString>; id required

Cause: XOR join expression does not contain an unique ID.
Response: Make sure that a unique ID is present for the XOR join expression.

PRT.0101.9342 Bad XOR join specification; unparseable timeout <timeoutValue>

Cause: Timeout value of the XOR join expression is not in a valid format.
Response: Make sure the timeout value for the XOR join expression is in milliseconds.
PRT.0101.9343 Bad join expression; one or more unmatched )

Cause: Missing parenthesis in join expression.
Response: Make sure the join expression is valid.
PRT.0101.9344 Bad join expression; one or more unmatched (

Cause: Missing parenthesis in join expression.
PRT.0101.9345 Bad join expression; bad standalone join spec <joinExpression>

Cause: Invalid standalone join spec.
PRT.0101.9356 Can not set track count to <trackCountNumber>; only 0 or 1 allowed for EventMetaData
Cause: Track count is not 0 or 1.
Response: Make sure the track count is 0 or 1.
PRT.0101.9358 Exception while executing SQL statement

Cause: The SQL processor failed to execute this statement because there is an error in the statement itself--
reference to a non-existent table, non-existent (misspelled) field, or an incorrect SQL keyword.
PRT.0101.9417 Can not publish <documentName>. Document is not in pipeline

Cause: Cannot publish document. Document is not in pipeline.
Response: Check for improper or missing mapping in the IS flow.
PRT.0101.9620 Could not determine SOAP operations


PRT.0101.9621 Could not determine SOAP operations Qname <exception>
PRT.0101.9622 Could not determine binding document <exception>

Cause: No SOAP binding data was available in the pipeline to perform a Web service invoke.
PRT.0101.9623 Encountered SOAP-FAULT invoking web service: <address>

Cause: A SOAP-FAULT was returned from the Web service invoke.
Response: Check the exception for details. This is an error condition encountered when invoking a Web service.
PRT.0101.9624 Encountered error parsing SOAP document from pipeline <pipeline>. Please confirm that you have correctly
specified the web service to be invoked.
Cause: The SOAP Message could not properly be parsed from the output pipeline from a Web service invoke.
PRT.0101.9625 Encountered error parsing SOAP header from pipeline <pipeline>. Please confirm that you have correctly
Cause: The SOAP Header could not properly be parsed from the output pipeline from a Web service invoke.
PRT.0101.9626 Encountered error parsing SOAP header entries from pipeline <pipeline>. Please confirm that you have
Cause: The SOAP Header entries could not properly be parsed from the output pipeline from a Web service
invoke.
PRT.0101.9627 Encountered error parsing SOAP body from pipeline <pipeline>. Please confirm that you have correctly
Cause: The SOAP Body could not properly be parsed from the output pipeline from a Web service invoke.

PRT.0101.9628 Encountered error parsing SOAP body entries from pipeline. Please confirm that you have correctly specified
the web service to be invoked.
Cause: The SOAP Body entries could not properly be parsed from the output pipeline from a Web service
invoke
PRT.0101.9629 Encountered error querying an XML node <exception>

Cause: An error occurred while querying an XML node using an XPath expression.
Response: Check the exception for details. This occurs when the XML used in an XPath evaluation is
malformed.
PRT.0101.9630 Encountered error parsing an XML node to document <exception>

Cause: An error occurred while querying an XML node using an XPath expression.
malformed.
PRT.0101.9631 Encountered error parsing a document to an XML string <exception>

Cause: An error occurred while parsing an XML node to a Idata document
malformed.
PRT.0101.9640 Encountered fatal error invoking web service <exceptionMessage>. Please confirm that you have a valid
installation.
Cause: A fatal error occurred in performing a Web service invoke.
Response: Check the exception for details. This occurs when the endpointReference in the pipeline to be used
for the invoke is not valid or malformed.
PRT.0101.9641 Encountered error accessing SOAP-FAULT information <exceptionMessage>

Cause: The PRT was unable to parse the SOAP-FAULT information from the return of a Web service
invocation
Response: The invoked Web service returned a soapStatus of 1 (indicating failure), while failing to package the
fault information as a SOAP-FAULT.
PRT.0101.9642 Encountered error accessing SOAP-DATA information <exceptionMessage>

Cause: The PRT was unable to parse the SOAP-DATA information from the return of a Web service invocation

PRT.0101.9914 Error Cloning Data
Cause: Error copying Idata.
Response: Internal error means that Idata contains non serializable types.


CHAPTER 13
webMethods RosettaNet Module
ESIPRT (WmIPRoot Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
ESRN11 (WmRUNIF11TRP Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
ESRN20 (WmRNIF20TRP Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
ESRNET (WmRosettaNet Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752

CHAPTER 13 webMethods RosettaNet Module
ESIPRT (WmIPRoot Package)
ESIPRT.000000.000001 Error while executing service <serviceName>.

Cause: The service failed to execute because of improper service input or unexpected data during execution.
Response: Make sure that the service output in the pipeline matches the output signature and constraints
specified on the Input/Output tab for the service. Use the listed errors to locate invalid output values.
ESIPRT.000000.000002 <varName> and <varName> cannot be null.

ESIPRT.000000.000003 Pipeline variable <varName> is null.

ESIPRT.000000.000008 <varName> parameter must be null when using <varName> parameter.

ESIPRT.000000.000009 bad element

Cause: While invoking the service documentToRecord, a bad element was found in the document.
Response: Replace the bad element in the document and invoke the service again.
ESIPRT.000000.000010 Unknown package <pkgName>.

Cause: The package could not be found on Integration Server.
Response: Check for the package in the Server Administrator.
ESIPRT.000000.000011 <varName> is required.

specified on the Input/Output tab for the service. Use the listed errors to locate invalid variables.

ESIPRT.000000.000012 <varName> or <varName> is required.

ESIPRT.000000.000013 Unable to find id for event <eventName>.

Cause: Parameters or lastEvents do not exist in the service input.
Response: Make sure that the parameters or lastEvents exist, and check your Trading Networks installation.
ESIPRT.000000.000014 Record <IS docTypeName> does not exist.

Cause: The IS document type name is not specified, or the record is an invalid IS document type, or the record
does not exist.
Response: In Developer, check the Integration Server document type. Reload the package with the IS document
type.
ESIPRT.000000.000020 Error trapped in service <serviceName> \n.

Cause: An error occurred while executing this service.
Response: Check the pipeline contents (pub.flow:savePipeline) in the specified service to locate the error. Call
webMethods Technical Services for assistance.
ESIPRT.000000.000024 Could not find starting index for character \" <char> \".
Cause: Character '-' is missing from conversationID.
Response: Check conversationID for the character '-'.
ESIPRT.000000.000030 In service <serviceName>: Payload validation failed -- <errorMessage>.

Cause: The document contains a validation error.
Response: If the document is incoming, the errors will be sent to the trading partner. No further action is
required. If the document is outgoing, check the service and correct the errors. Send the document again.
ESIPRT.000000.000033 In service <serviceName>: No content part with partName <partName> in the bizdoc envelope.
Cause: partName does not exist in the bizdoc envelope. The RNO may have been created incorrectly.
Response: Check with your trading partner to make sure that they are using an agreed upon and valid
transport. Make sure to apply any transport-related fixes.

ESIPRT.000010.000002 Could not find exact match TPA or default TPA for Sender : <DUNSID> Receiver : <DUNSID> and
Agreement ID : <TNDocTypeName>.
Cause: A TPA does not exist for this process.
Response: Create a default TPA or a TPA using the sender DUNS, receiver DUNS, and TN document type
name.
ESIPRT.000010.000003 TPA for Sender : <DUNSID> Receiver : <DUNSID> and Agreement ID : <TNDocTypeName> are not in
'Agreed' status.
Cause: The TPA for this process is not set to 'Agreed' status.
Response: In the Trading Networks Console, set the applicable TPA to 'Agreed' status.
ESIPRT.000020.000001 Invalid content type.

Cause: Content Type name is not specified in the content header.
Response: Specify the correct content type name in the content handler before posting the document.
ESIPRT.000020.000002 Content handler not found for the type.

Cause: A content handler is not registered for this content type.
Response: Provide a content handler. For information about how to create a content handler, go to
http://advantage.webmethods.com.
ESIPRT.000020.000003 Invalid transport type.

Cause: The transport name was not specified during the transport package startup.
Response: Make sure that the RosettaNet installation is not corrupted and that start up services are being
invoked during package startup.
ESIPRT.000020.000004 Transport object to be registered is null.

Cause: A transport object is not provided during the transport package startup.
Response: Make sure that a transport is provided. Check that the RosettaNet installation is not corrupted and
that no errors are thrown for the startup services while starting the server.
ESIPRT.000020.000005 Transport not found for '<transportName>'.

Cause: The transport is not registered.
Response: Make sure that the RosettaNet installation is not corrupted and that no errors are thrown for the
startup services while starting the server.

ESIPRT.000020.000006 No href attributes have been specified in the PIP.

Cause: The hrefList does not exist in the PIP. Attachments may not have been set up correctly for this message.
Response: In the outbound map, make sure that attachments are added using the wm.ip.util:addAttachment
service in the WmIPRoot package.
ESIPRT.000020.000007 Number of href elements <numOfHRefElements> is less than the number of attachments
<numOfAttachments>.
Cause: HRef elements do not match the number of attachments. Attachments may not be set up correctly for
this message.
Response: In the outbound map, make sure attachments are added using the wm.ip.util:addAttachment service
in the WmIPRoot package.
ESIPRT.000020.000008 ContentID <contentId> has not been specified in any href attribute in the PIP.
Cause: The content ID was not specified for the attachment. Attachments may not be set up correctly for this
message.
ESIPRT.000020.000009 Not enough bytes to read.

Cause: The envStream may not exist. Bytes from the Input Stream may not be available. The Input Stream may
have been read and not reset.
Response: Check the inputs to the service. Check for any debug services where the Input Stream may have
been used and not reset.
ESIPRT.000020.000010 Did not read sufficient bytes.

Cause: Bytes from the Input Stream may not be available. The Input Stream may have been read and not reset.
Response: Check the inputs to the service. Check for any debug services where the Input Stream may have
been used and not reset.
ESIPRT.000020.000011 In service <serviceName>: Transport name and version specified in the Conversation script
<conversationScript> does not match with transport name <transportName> received from trading partner DUNS <DUNSID>.
Cause: The transport specified in TPA does not match the transport of the document received.
Response: Check TPA parameters for correct transport. Check with your trading partner to make sure that they
are using an agreed upon and valid transport.

ESIPRT.000020.000012 In service <serviceName>: HTTP failed with following error:\n<errorMessage>\n. Unable to establish
communication with the trading partner : <DUNSID>".
Cause: An HTTP protocol error occurred while sending the message. The protocol may be configured
incorrectly in Trading Networks.
Response: Check the service and use the listed error(s) to correct the problem. See error log for more details. In
Trading Networks Console, check protocol information in the profile and check TPA parameters.
ESIPRT.000020.000013 In service <serviceName>: Pipeline variable <varName> is null.

Response: Make sure that the service inputs in the pipeline match the input signature and constraints specified
on the Input/Output tab for the service. Use the listed errors to locate missing variables.
ESIPRT.000020.000019 In service <serviceName>: Retry <num> of <totalNumRetries>: Failed to send data using protocol
<protocolName>. The response code is <responseCode>. The status message is <statusMessage>.
Cause: Possible causes: Trading Networks may have a configuration issue, trading partner may be down,
trading partner may not be handling RNO correctly, or the internet connection may be faulty.
Response: Possible actions: Check Trading Network installation and database connectivity, check delivery
method configuration for the trading partner profile, check that the trading partner has a valid transport and
URL or e-mail address, or check internet connectivity.
ESIPRT.000020.000022 In service <serviceName>: SMTP retry <number> of <totalNumRetries>: Mail could not be sent.
\nError is <errorMessage>. \nTO:<DUNSID> \nFROM: <DUNSID> \nMAILHOST: <mailServer>.
trading partner may not be handling RNO correctly, or internet connection may be faulty.
Response: Possible actions: Check Trading Network installation database connectivity, check the delivery
method configuration for the trading partner profile, check that the trading partner has a valid transport and
e-mail address, or check internet connectivity.
ESIPRT.000020.000023 HTTP retry <num> of <totalNumRetries>: HTTP connection to URL <urlName> failed with following
error: \n\n\t<errorMessage>.
Response: Possible actions: Check Trading Network installation, check the delivery method configuration for
the trading partner profile, check that the trading partner has a valid transport and URL or e-mail address, or
check internet connectivity.

ESIPRT.000020.000025 In service <serviceName>: Receipt Acknowledgement could not be sent to trading partner -
<DUNSID>.\nError Message: <errorMessage>.
Response: Possible actions: Check Trading Network installation database connectivity, check the Delivery
Method configuration for the trading partner profile, check that the trading partner has a valid transport and
URL or e-mail address, or check Internet connectivity.
ESIPRT.000020.000026 In service <serviceName>: ContentID <contentId> has been specified for more than one attachment.
Cause: The same content ID was specified for more than one attachment. Each attachment must have a unique
content ID.
Response: Make sure each attachment has a unique content ID. This can be accomplished using the
wm.ip.util:createContentID service and dropping the content ID after each attachment is added.
ESIPRT.000030.000001 No such algorithm exists.

Cause: An error occurred while creating the message digest. The algorithm may be missing or incorrect. The
content also may be corrupt.
Response: Make sure the algorithm is supported as indicated in the "webMethods RosettaNet Module User's
Guide."
ESIPRT.000030.000003 Error setting profile certificates for HTTPS. \n <errorMessage>.

Cause: An error occurred while retrieving certificates from the trading partner profile or setting the certificates
for HTTPS.
Response: Make sure that valid certificates are specified for the trading partner profile, or check the HTTPS
configuration.
ESIPRT.000040.000001 Error creating reservation : <errorMessage>.

Cause: An error occurred while creating Tspace reservation for this large document. Permissions may not be
set correctly, or space may not be available.
Response: Check permissions, or check device for available space.
ESIPRT.000040.000002 Error resizing reservation : <errorMessage>.

Cause: An error occurred while resizing Tspace for this large document. Permissions may not be set correctly,
or space may not be available.

ESIPRT.000040.000003 Error resizing reservation to final size : <errorMessage>

Cause: An error occurred while resizing Tspace for this large document. Space may not be available, or
permission may not be set correctly for available space.
ESIPRT.000050.000001 Pipeline variable <fileName> is null.

Cause: A file name was not specified in the input to this service.
Response: Make sure a valid file name is specified in the filename field.
ESIPRT.000050.000002 <fileName> cannot contain <separatorChar> characters.

Cause: The specified archive input file name has at least one invalid file separator character.
Response: Make sure a valid file name with valid file separator characters is specified in the filename field.
ESIPRT.000050.000003 <fileName> is a directory.

Cause: The specified input file name already exists on the file system as a directory.
Response: Make sure the archive's input file name does not exist already as a directory.
ESIPRT.000050.000004 <fileName> has no parent.

Cause: No directory was specified for the input filename.
Response: Make sure to specify a directory where the archive file will be created.
ESIPRT.000050.000005 Directory <directoryName> does not exist.

Cause: The file directory for the specified archive could not be created.
Response: Make sure your device and permissions are set correctly. Check to make sure that you specified a
valid directory name.
ESIPRT.000050.000006 Archive <archiveName> is Empty. It was not created.

Cause: No valid content was specified for the archive file.
Response: Check to make sure that you specified valid content for the archive.
ESIPRT.000050.000007 Failed adding TPA <TPAName>.

Cause: A failure occurred while adding Trading Networks TPAs to the archive file.
Response: Check your Trading Networks installation for database corruption. Check the Trading Networks
database connection.

ESIPRT.000050.000008 Failed adding NS ref <NSNode>.

Cause: A failure occurred while adding an IS document type or folder to the archive file. File may be in use by
another process.
Response: Disable any process that may be using the node. Check validity of the IS document type and folder.
Restart Integration Server to reload packages.
ESIPRT.000050.000009 Failed adding BizDocType <TNDocType>.

Cause: A failure occurred while adding a TN document type to the archive file.
Response: Check the Trading Networks installation. ANY OTHER OPTIONS?
ESIPRT.000050.000010 Unable to create file <fileName>.

Cause: Archive file could not be created.
Response: If file already exists, disable any process that may be locking the file. Check permissions on the file.
ESIPRT.000050.000011 Unable to use package <pkgName>.

Cause: An error occurred while importing an IS document type or folder into the WmRNPips package.
Response: If WmRNPips already exists, check whether it is a valid Integration Server package. Reload the
WmRNPips package and try again.
ESIPRT.000050.000012 File <fileName> not found.

Cause: The file specified was not found on the file device.
Response: Make sure that the file name specified is a valid location and file.
ESIPRT.000050.000013 Input archive cannot be null.

Cause: A valid archive was not found.
Response: Make sure a valid archive is specified in the WmRosettaNet/import directory.
ESIPRT.000050.000014 Type <archiveItemType> not found.

Cause: A valid archive item type was not found for this item.
Response: Recreate the archive using the current RosettaNet Module version. Restart Integration Server to
make sure that the WmIPRoot package is loaded properly.

ESIPRT.000050.000015 Unsupported key type <archiveItemKey>.

Cause: A valid archive item key was not found for this item. The RosettaNet Module installation may be
corrupt.
Response: Make sure that the WmIPRoot package is loaded properly. Reload the package to load the
appropriate classes.
ESIPRT.000050.000016 Unable to rewrite file <fileName>.

Cause: An archive file was found but could not be updated. The file may be locked or have incorrect
permissions.
Response: Disable any process that may be locking the file. Check the permissions for the file.
ESIPRT.000050.000017 Unable to create null file.

Cause: An error occurred while creating or importing the exported archive file.
Response: Try recreating the archive. Follow the directions in the "webMethods RosettaNet Module User's
Guide" to ensure the archive file is created correctly. Check that the WmIPRoot package is loaded properly.
Reload the package to load the classes.
ESIPRT.000050.000022 File <fileName> not found.

Cause: The archive file specified was not found.
Response: Make sure that a valid file name is specified in the filename field and that the file exists in the correct
directory.
ESIPRT.000050.000023 Cannot import directory <directoryName>.

Cause: The archive file specified is in the file directory.
Response: Make sure that a valid file name is specified in the filename field and exists as a file in the correct
directory.
ESIPRT.000050.000024 Error opening import file <fileName>.

Cause: An error occurred while reading the specified archive file. The version of the archive may not be
compatible with this version of the RosettaNet Module, or the file may be corrupt.
Response: Recreate the archive using the current RosettaNet Module version. Follow the directions in the
"webMethods RosettaNet Module User's Guide" to ensure that the archive file is created correctly.

ESIPRT.000050.000025 Error reading header in import file <fileName>.

Cause: An error occurred while reading the archive file header for the specified archive file. The archived file
may not have been created successfully and may be corrupted.
Response: Recreate the archive from the current RosettaNet Module version. Follow the directions in the
"webMethods RosettaNet Module User's Guide" to ensure the archive file is created correctly.
ESIPRT.000050.000026 Zip file not open.

Cause: An error occurred when reading the specified archive file. The version of the archive may not be
compatible with the version of the RosettaNet Module, or the file may be corrupt.
ESIPRT.000050.000027 No header information in file <fileName>.

Cause: No information was provided in the archive file header for the specified archive file.
Response: Recreate the archive using the current RosettaNet Module version and provide all required header
information. Follow the directions in the "webMethods RosettaNet Module User's Guide" to ensure that the
archive file is created correctly.
ESIPRT.000050.000029 Entry <archiveItemKey> not found.

Cause: The specified archive item in the archive manifest was not found. The archive may be corrupt.
Response: Recreate the archive from the current RosettaNet Module version. Follow the directions in the
ESIPRT.000050.000038 Node <NSNode> not found.

Cause: An IS document type or folder cannot be found.
Response: In Developer, check for the IS document type or folder. Restart Integration Server to reload
packages.
ESIPRT.000050.000039 Unable to overwrite existing file <nodeFileName>.

Cause: The existing IS document type or folder cannot be overwritten.
Response: Disable any process that may be locking the file, check the file's permissions., and check that the
WmIPRoot package is loaded properly.

ESIPRT.000050.000040 Unable to create directory.

Cause: An error occurred while importing an IS document type or folder into the WmRNPips package.
Response: If WmRNPips already exists, check whether it is a valid Integration Server package and check its
permissions. Restart Integration Server to reload packages.
ESIPRT.000050.000041 Header format is not valid.

Cause: Required information in the archive file header does not exist.
Response: Recreate the archive from the current RosettaNet Module version and provide all required header
information. Follow the directions in the "webMethods RosettaNet Module User's Guide" to ensure the archive
file is created correctly.
ESIPRT.000050.000042 Unable to delete tmp file.

Cause: The temporary file used in archive creation cannot be deleted.
Response: Disable any process that may be locking the file and check the permissions on the file. Restart
Integration Server to release any locks on the file.
ESIPRT.000050.000043 Model <processModel> not found.

Cause: An error occurred while exporting the process model.
Response: Restart Integration Server and re-export the process model from the compatible Modeler.
ESIPRT.000050.000044 Model Name not specified.

Cause: The imported process model cannot find a valid process model name.
ESIPRT.000050.000045 Model File does not exist.

Cause: The imported archive cannot find a valid process model in the archive file. The archive is the wrong
version or it is corrupt.
ESIPRT.000050.000046 Unable to create model directory <processModelDirectory>.

Cause: The file directory for the specified process model could not be created.
Response: Make sure that permissions are set correctly for that directory.

ESIPRT.000050.000048 Unable to locate package <packageName>.

Cause: The package where the specified process models are located cannot be found.
Response: Make sure that the process models are placed correctly as indicated in the "webMethods RosettaNet
User's Guide." Restart Integration Server to reload the specified package.
ESIPRT.000050.000049 Parameter <IS docTypeName> is required.

Cause: The IS document type name is not specified or it is not a valid IS document type.
Response: Check the IS document type. Restart Integration Server to reload the document types.
ESIPRT.000050.000050 Interface <Integration Server folder> does not exist.

Cause: The Integration Server folder name is not specified or it is not a valid Integration Server folder.
Response: Check the Integration Server folder. Restart Integration Server to reload the packages.
ESIPRT.000050.000054 <TPAItem> is null.

Cause: The Imported archive cannot find a valid TPA in the archive file. The archive is the wrong version or
corrupt.
Response: Check the Trading Networks installation. Recreate the archive using the current RosettaNet Module
version. Follow the directions in the "webMethods RosettaNet Module User's Guide" to ensure that the archive
file is created correctly.
ESIPRT.000070.000001 There is no conversation with conversation ID <processID>.

Cause: The ConversationID in the incoming document does not match the ConversationID of a running
process.
Response: Ensure that a process with the same ConversationID as specified in the incoming document does
exist. Also, verify that the process is in Started status.
ESIPRT.000070.000008 Cannot specify conversation ID <conversationId> for non-existant conversations.

process.
Response: Ensure that a process with the same ConversationID does exist as specified in the incoming
document.

ESIPRT.000070.000009 No matching conversation script.

Cause: The incoming document is not a valid starting document for a new process or it does not join an existing
process.
Response: If a process exists with the same conversationID, then make sure that the document is assigned as an
input to a process model step. Also, If a process does not exist with the same conversationID, then verify that
you have enabled the process that the document triggers. Finally, if a process is enable but does not exist with
the same conversationID, then make sure that the document is assigned as an input to this process model step.
ESIPRT.000070.000020 In service <serviceName>: Received document that does not match with any conversation or
conversation scripts. ConversationID <processId>
process. Also, the incoming document is not a valid starting document for a process.
Response: If a process exists with the same conversationID, then make sure that the document is assigned as an
input to a process model step. Also, If a process does not exist with the same conversationID, then verify that
you have enabled the process that the document triggers. Finally, if a process is enable but does not exist with
the same conversationID, then make sure that the document is assigned as an input to this process model step

ESRN11 (WmRUNIF11TRP Package)
ESRN11.000000.000001 Transport information definition not found. Could not find file(s) <fileName> or <fileName> in folder
<dirName>. Please check the file system.
Cause: The rnif11.cnf or chem11.cnf file is missing from the packages/WmRNIF11TRP/config directory.
Response: Make sure that rnif11.cnf or chem11.cnf (or both) are present in the packages/WmRNIF11TRP/config
directory. Check the Trading Networks TPA to make sure that the correct transport is configured.
ESRN11.000000.000002 No data found in <fileName> file.

Cause: The rnif11.cnf file is corrupt.
Response: Make sure that rnif11.cnf is a valid XML file and contains valid required values.
ESRN11.000000.000008 Error while inserting document type to database.

Cause: RN11BizDocType could not be inserted or updated in the Trading Networks database. The Trading
Networks database may be corrupt, or the RN11BizDocType may contain an ID that already exists in the
database with a different document type name.
Response: Check the Trading Networks database installation. Check for the existence of RN11BizDocType.
Export Trading Network objects, re-initialize the database, and import exported objects.
ESRN11.000000.000013 Error while executing service <serviceName>.

specified on the Input/Output tab for the service. Check the error log. Use the listed errors to identify and
correct the error.
ESRN11.000000.000015 Error in <methodName> method.

Cause: The service failed to execute.
Response: Check the error log and use the listed errors to identify and correct the error.
ESRN11.000010.000002 Could not recognize document in : <serviceName>.

Cause: Synchronous response was not recognized. The TN document type may not be set up correctly.
Response: Verify that the PIP should be synchronous and the TN document type for the response document is
configured correctly. Check the Trading Networks installation and configuration.

ESRN11.000020.000001 No data in pipeline to create MimeMessage.

Response: Make sure that the service input in the pipeline matches the input signature and constraints
specified on the Input/Output tab for the service.
ESRN11.000020.000002 One of the variable(s) <varName> or <varName> or <varName> are null.

specified on the Input/Output tab for the service. Use the listed errors to locate invalid or missing input values.
ESRN11.000020.000003 Transport <transportName> is not enabled.

Cause: The specified transport is not enabled.
Response: Check the "webMethods RosettaNet Module User's Guide" for the valid configuration files, and then
verify that the valid transport configuration file is present.
ESRN11.000020.000004 Transport <transportName> is not supported.

Cause: A transport was specified in the content header that is not supported by this package.
transport.
ESRN11.000020.000005 No variable <varName> in pipeline.

Cause: Transport name is not specified or is invalid during processing.
Response: Make sure that documents are being received over a valid protocol. Check with your trading partner
to make sure that they are using an agreed upon and valid transport.
ESRN11.000020.000006 Pipeline variable <varName> is null.

Cause: Transport name is not specified or is invalid during processing.
ESRN11.000020.000009 RNO Format Error: Content length <contentLength> is less than eight bytes.
Cause: Content length was specified incorrectly in the RNO. Per the transport specification, it must be eight
bytes.
transport.

ESRN11.000020.000010 RNO Format Error: Content length is <contentLength>. Data length is <dataLength>.
Cause: Content length was specified incorrectly in the RNO. The content length specified must be equal to the
data length.
Response: Make sure that the RNO was not edited manually. Check with your trading partner to make sure
that they are using an agreed upon and valid transport.
ESRN11.000020.000016 Preferred protocol not specified.

Cause: The preferred protocol was not specified in the receiver's profile in Trading Networks.
Response: In Trading Networks Console, select the preferred protocol for the receiver's profile.
ESRN11.000020.000017 No input stream in pipeline.

Cause: Input stream is not being sent correctly.
transport.
ESRN11.000020.000018 Input is null in <transportAction>.

Cause: Data is not available at this transport action. One or more services or methods before this action were
not successful.
ESRN11.000020.000019 Decoded IData is null in <transportAction>.

Cause: Decoded data is not available at this transport action. One or more services or methods before this
action were not successful.
ESRN11.000020.000020 No bytes in decoded content.

Cause: Bytes in decoded data are not available at this transport action. One or more services or methods before
this action were not successful.

ESRN11.000020.000024 In service <serviceName>: Pipeline variable <varName> does not exists.

Cause: The service failed to execute because of an improper service input or unexpected data during execution.
ESRN11.000020.000025 In service <serviceName>: Signature does not exist in the incoming document even though it is
required.\n Offending message received from trading partner DUNS <DUNSID>.
Cause: The incoming document was not signed.
Response: Check with your trading partner to verify that they are signing the document. If a signature is not
required, modify the user parameters in the corresponding TPA.
ESRN11.000020.000026 In service <serviceName>: Inbound validation of synchronous response failed. Reason:

<errorMessage>; Intiating NOF.
Cause: The incoming document contained a validation error.
Response: An NOF specifying the error has been sent to the trading partner. No action is required.
ESRN11.000020.000027 In service <serviceName>: Payload validation failed. Reason: <errorMessage>.

Cause: The incoming document contained a validation error.
Response: If the document is outgoing, please correct the errors and send again. If the document is incoming,
check with your trading partner to make sure that they are using an agreed upon and valid process and
transport.
ESRN11.000020.000030 In service <serviceName>: Error while decoding synchronous response.Reason: <errorMessage>.

Cause: The synchronous response contained an error. The response may not have been formed correctly. The
transport configuration may be incorrect.
Response: Make sure that the Trading Networks TPA parameters are set correctly. Check with your trading
partner to make sure that they are using an agreed upon and valid transport. Make sure to apply any
transport-related fixes.
ESRN11.000020.000032 In service <serviceName>: Attachment validation failed.\nReason:\n <errorMessage>.

Cause: Attachments may not have been set up correctly for this message.

ESRN11.000020.000033 In service <serviceName>: Failed header validation. \nReason:\n <errorMessage>.

Cause: The incoming document contained a header validation error.
ESRN11.000020.000034 In service <serviceName>: Preamble header validation failed. Reason: <errorMessage>.

Cause: A preamble header validation error occurred in the incoming document.
ESRN11.000020.000035 In service <serviceName>: ServiceHeader validation failed. \nReason:\n <errorMessage>.

Cause: A service header validation error occurred in the incoming document.
ESRN11.000020.000040 In service <serviceName>: Could not send Exception to trading partner -- <DUNSID>. Reason:
<errorMessage>.
Cause: An error occurred while sending an exception to the trading partner. A transport configuration issue
may exist.
Response: Possible actions: Check transport parameters and network connectivity, or check with your trading
ESRN11.000020.000041 In service <serviceName>: Could not extract DUNS number from ServiceHeader. Bad FileName =
<fileName>
Cause: The DUNS may not be specified in the trading partner profile.
Response: Assign the DUNS for the specified profile.
ESRN11.000020.000042 In service <serviceName>: Transport <protocolName> not supported for RNIF11.

Cause: RNIF 1.1 supports only HTTP and HTTPS, which were not specified as the preferred protocols in the
trading partner profile.
Response: In the Trading Networks Console, either set or create the preferred protocol for the specified profile
to HTTP or HTTPS.

ESRN11.000020.000043 In service <serviceName>: Attachment data must be either a <dataType> or an <dataType>.

Cause: The attachment is not a valid data type. It must be added as a byte[] or InputStream.
Response: Modify the output map to add attachments as a byte[] or InputStream in the
wm.ip.util:addAttachment service.
ESRN11.000030.000001 In service <serviceName>: No Message Digest in incoming <rootTag> document.

Cause: Required message digest was not specified in the document.
ESRN11.000030.000002 In service <serviceName>: Incoming Message Digest \<messageDigest>\ does not match the original
Message Digest \<messageDigest>\.
Cause: The incoming message digest in the document did not match the automated message digest.
Response: Verify that both partners are using the same hash algorithm.
ESRN11.000031.000001 In service <serviceName>: Signature verification failed. \nReason:\n <errorMessage>.

Cause: The certificates for the trading partner profile do not exist or are invalid.
Response: Make sure that valid certificates are specified for the profile. Make sure that the signature transport
parameters are correct. Check with your trading partner to make sure that they are using an agreed upon and
valid transport. Make sure to apply any transport-related fixes.
ESRN11.000031.000002 In service <serviceName>: Certificate Authority (CA) is untrusted.

Cause: The CA certificates for the trading partner profile do not exist or are invalid.
Response: Make sure that valid CA certificates are specified for the profile. Make sure that the signature
transport parameters are correct. Check with your trading partner to make sure that they are using an agreed
upon and valid transport. Make sure to apply any transport-related fixes.
ESRN11.000031.000003 In service <serviceName>: Trading partner DUNS = <DUNSID> is NOT a valid user on the system.
Cause: The user does not exist on the Integration Server. It may have been deleted accidentally or created
improperly.
Response: Create the user in the Integration Server or re-create the profile in Trading Networks Console (the
user will be added automatically in Integration Server).

ESRN11.000031.000004 In service <serviceName>: Document has been tampered.

Cause: The signature does not verify against the incoming document. Either the document was tampered with
or the certificates are corrupt.
Response: Check with your trading partner to make sure that the document was not tampered with. Obtain
new certificates from your trading partner. Check with your trading partner to make sure that they are using
an agreed upon and valid transport. Make sure to apply any transport-related fixes.
ESRN11.000031.000005 In service <serviceName>: Private Key bytes for <DUNSID> not found.
Cause: The private key for the trading partner profile is invalid.
Response: Make sure that a valid private key is specified for the trading partner profile. Make sure that the
signature transport parameters are correct.
ESRN11.000031.000006 In service <serviceName>: Certificate bytes for <DUNSID> not found.

Cause: The certificates for the trading partner profile are invalid.
parameters are correct.
ESRN11.000031.000007 In service <serviceName>: Signature does not exist even though it is required.
Cause: The required signature does not exist on the incoming document.
transport.

ESRN20 (WmRNIF20TRP Package)
ESRN20.000000.000001 Transport information definition not found. Could not find File <fileName>.
Cause: The transport.cnf file is missing from the packages/WmRNIF20TRP/config directory.
Response: Make sure that transport.cnf is present in the packages/WmRNIF20TRP/config directory. Check the
Trading Networks TPA to make sure that the correct transport is configured.
ESRN20.000000.000002 Error while executing service <serviceName>.

specified on the Input/Output tab for the service. Check the error log and use the listed errors to locate invalid
values.
ESRN20.000000.000005 Error while inserting document type to database.

Cause: RN20BizDocType could not be inserted or updated in the Trading Networks database. The Trading
Networks database may be corrupt, or RN20BizDocType may contain an ID that exists already in the database
with a different name.
Response: Check the Trading Networks database installation. Check that RN20BizDocType exists. Export
Trading Network objects, re-initialize the database, and import exported objects.
ESRN20.000000.000009 Error while inserting attribute to database.

Cause: Trading Networks may be the wrong version or the database may be corrupt.
Response: Check Trading Networks version and Trading Networks configuration.
ESRN20.000000.000011 No variable <varName> in pipeline.

ESRN20.000000.000012 Pipeline variable <varName> is null.

specified on the Input/Output tab for the service. Use the listed errors to locate invalid values.

ESRN20.000000.000013 Transport <transportName> is not enabled.

Cause: The transport name is not specified or invalid during processing.
ESRN20.000000.000014 Error in <methodName> method.

Cause: The service failed to execute.
Response: Check the error log and use the listed errors to identify and correct the error.
ESRN20.000010.000001 Invalid protocol information.

Cause: Preferred protocol either was not specified in Trading Networks receiver's profile or it is invalid.
Response: Make sure that the preferred protocol for receiver's trading partner profile is selected and valid.
ESRN20.000010.000002 Error reading headers : <serviceContentError>.

Cause: The incoming document contains a header validation error.
ESRN20.000010.000044 Missing protocol.

Cause: Preferred protocol was not specified in the receiver's Trading Networks profile.
Response: In Trading Networks Console, check that the preferred protocol for receiver's profile is selected and
valid.
ESRN20.000010.000046 Invalid <x-RN-Version>. Should be : <2.0>.

Cause: The transport version is missing or invalid.
ESRN20.000010.000047 Invalid response type in the HTTP header : <responseType>.

Cause: The response type is missing or invalid. It should be "async" or "sync".

ESRN20.000010.000048 Method <methodName> failed : <errorMessage>.

Cause: The method failed with the listed error.
Response: Use the listed errors to identify and correct the error.
ESRN20.000010.000049 Debug headers do not exist.

Cause: The required debug headers are missing or invalid.
ESRN20.000010.000052 Debug headers xml data not found.

Cause: The required debug headers are missing or invalid.
ESRN20.000010.000053 Could not recognize document in : <serviceName>.

Cause: The document was not recognized. The TN document type may not be set up correctly.
Response: Make sure that the PIP transport parameters are set correctly. Make sure that the TN document type
for the incoming document is configured correctly. Check the Trading Networks installation and
configuration.
ESRN20.000020.000001 No data in pipeline to create MimeMessage.

ESRN20.000020.000003 One of the variable(s) <varName> or <varName> or <varName> are null.

ESRN20.000020.000004 Missing <varName> in service <serviceName>.


ESRN20.000020.000016 Preferred protocol not specified.

Cause: The preferred protocol was not specified in receiver's Trading Networks profile.
Response: In Trading Networks Console, select the preferred protocol for the receiver's profile.
ESRN20.000020.000017 No input stream in the pipeline.

Cause: The input stream is not being sent correctly.
transport on a valid protocol.
ESRN20.000020.000018 Input stream is empty.

Cause: The input stream may not have been provided as input, or bytes from Input Stream may not be
available. The input Stream may have been read and not reset.
Response: Check the input to the service. Check for any debug services where the input stream may have been
used and not reset.
ESRN20.000020.000019 Error reading incoming data : <serviceContentError>.

Cause: Data is not available at this transport action. One or more services or methods before this action were
not successful.
ESRN20.000020.000020 No content parts in the incoming message.

Cause: No content parts were found in this message. The message may not have been created correctly.
ESRN20.000020.000022 One of the headers is missing/incorrect : <serviceContentError>.

Cause: One or more of the headers are missing from this message. The message may not have been created
correctly.
ESRN20.000020.000023 Error in : <serviceName> service. Message : <errorMessage>.


ESRN20.000020.000024 Error in : <serviceName> service. Signature does not exists even though it is required.
Cause: Required signature does not exist for the incoming document.
Response: Check transport parameters. Check with your trading partner to make sure that they are using an
agreed upon and valid transport.
ESRN20.000020.000025 Error in : <serviceName> service. Payload encryption does not exist in the incoming document even
though it is required.
Cause: Required encryption does not exist on the incoming document.
Response: Check transport parameters. Check with your trading partner to make sure they are using an agreed
upon and valid transport.
ESRN20.000020.000026 Error in : <serviceName> service. Header encryption does not exist in the incoming document even
though it is required.
Cause: Required header encryption does not exist on the incoming document.
ESRN20.000020.000027 Error in : <serviceName> service. Pip code does not match -- <pipCode>.
Cause: PIP code does not match the PIP code specified in the Trading Networks TPA.
ESRN20.000020.000028 Error in : <serviceName> service. Pip version does not match -- <pipVersion>.
Cause: PIP version does not match the PIP version specified in the Trading Networks TPA.
ESRN20.000020.000029 Error in : <serviceName> service. <usageCode> code in the conversation script does not match with
-- <usageCode>.
Cause: Usage code in the incoming RNIF 2.0 document does not match the usage code in the Trading Networks
TPA.
Response: Verify that you and your partner are using the same usage code when exchanging RNIF 2.0
documents.

ESRN20.000020.000030 Error in : <serviceName> service. <errorMessage> -- Error reading <contentPart>.

Cause: An error occurred while reading one or more of the content parts from this message. The message may
be malformed.
agreed upon and valid transport. Make sure to apply any transport-related fixes.
ESRN20.000020.000031 Error in : <serviceName> service. <errorMessage> -- Profile not found for trading partner DUNS
<DUNSID> to verify the signature.
Cause: The certificates for the trading partner profile are invalid.
Response: Make sure valid certificates are specified for the trading partner profile. Make sure that the signature
transport parameters are correct.
ESRN20.000020.000032 Error in : <serviceName> service . <errorMessage> -- Sender certificate does not match with signed
document.
Cause: The signature does not verify against the incoming document. The document was tampered with or the
certificates are corrupt.
Response: Check with your trading partner to make sure that the document was not tampered with. Obtain
new certificates from the trading partner, and check that they are using an agreed upon and valid transport.
Make sure to apply any transport-related fixes.
ESRN20.000020.000033 Error in : <serviceName> service . <errorMessage> -- Private key not found.

Cause: The private key for the trading partner profile is missing.
Response: Make sure a valid private key is specified for the profile. Make sure that the signature transport
ESRN20.000020.000034 Error in : <serviceName> service . <errorMessage> -- Certificate chain not found.

Cause: The certificate chain for the trading partner profile is missing.
ESRN20.000020.000035 Error in : <serviceName> service . <errorMessage> -- Error decrypting header.


ESRN20.000020.000036 Error in : <serviceName> service . <errorMessage> -- Error decrypting service content.

Response: Make sure valid certificates are specified for the profile. Make sure that the signature transport
ESRN20.000020.000038 Error in : <serviceName> service -- inbound validation of synchronous response failed :

<errorMessage>. Intiating <NOF>.
Cause: The incoming message contained an error in the header.
Response: Check the transport parameters. Check certificates. Check with your trading partner to make sure
that they are using an agreed upon and valid transport. Make sure to apply any transport-related fixes.
ESRN20.000020.000039 Error in : <serviceName> service -- Message sequence error : <errorMessage>.

Cause: The parameters in the conversation script do not match the values received in the incoming document.
Response: Check the transport parameters. Re-check transport parameters. Check with your trading partner to
make sure that they are using an agreed upon and valid transport. Make sure to apply any transport-related
fixes.
ESRN20.000020.000040 Error in : <serviceName> service -- inbound validation of synchronous request failed. Error reading
service content.
Cause: The incoming message contained an error in the header.
Response: Check the transport parameters. Check certificates. Check with your trading partner to make sure
that they are using an agreed upon and valid transport. Make sure to apply any transport-related fixes.
ESRN20.000020.000041 Error in : <serviceName> service -- <errorMessage> -- Error reading service content.

Cause: An error occurred while decoding this message. The message may be malformed, or the transport may
be configured incorrectly.
ESRN20.000020.000042 Error in : <serviceName> service -- Payload validation failed. \nReason: \n <reason>.

Response: If the document is outgoing, correct the errors and send again. If the document is incoming, check
with your trading partner to make sure that they are using an agreed upon and valid process and transport.

ESRN20.000020.000043 Error in : <serviceName> service -- <contentId> exists without attachments.

Cause: The message may be malformed.
transport and response type. Make sure to apply any transport-related fixes.
ESRN20.000020.000044 Error in : <serviceName> service -- Attachment verification failed : <errorMessage>.

Response: If the document is outgoing, in the outbound map, make sure that attachments are added using the
wm.ip.util:addAttachment service in the WmIPRoot package. If the document is incoming, check with your
trading partner to make sure that they are using an agreed upon and valid transport.
ESRN20.000020.000045 Error in : <serviceName> service -- Attachment verification failed : <errorMessage>. Initiating <NOF>.
Cause: Attachments may not have been set up correctly for this incoming message.
transport.
ESRN20.000020.000046 Error in : <serviceName> service -- Attachment verification failed. \nReason:\n <errorMessage>.

ESRN20.000020.000047 Error in : <serviceName> service -- Error while decoding synchronous response : <errorMessage>.
Cause: An error occurred while decoding the synchronous response. The message may be malformed. The
transport may have been configured incorrectly.
partner to make sure that they are using an agreed upon and valid transport and valid response type. Make
sure to apply any transport-related fixes.
ESRN20.000020.000050 Error in : <serviceName>. Attachment verification failed : <errorMessage>.


ESRN20.000020.000051 Error in : <serviceName>. Signature verified with the error : <errorMessage>.

Cause: Signature was verified, but an error still occurred.
Response: Check signature-related transport parameters. Check certificates. Check with your trading partner to
make sure that they are using agreed upon and valid transport. Make sure to apply any transport-related fixes.
ESRN20.000020.000052 Error in : <serviceName>. <errorType> -- Signature verification failed : <errorMessage>.

ESRN20.000020.000053 Error in : <serviceName>. <errorType> -- <contentPart> validation failed with reason :

<errorMessage>.
Response: If the document is outgoing, correct the errors and send again. If the document is incoming, check
with your trading partner to make sure that they are using an agreed upon and valid process and transport.
ESRN20.000020.000054 Error in : <serviceName>. No messageDigest in incoming Receipt Acknowledgement!

Cause: The required message digest was not specified in document.
ESRN20.000020.000055 Error in : <serviceName>. Incoming Message Digest is not the same as the original Message Digest!
Incoming Message Digest: <messageDigest>. Original Message Digest: <messageDigest>.
Cause: The required message digest was not specified correctly in document.
ESRN20.000020.000057 Error in : <serviceName>. Signature does not exist in the incoming document even though it is
required.
Cause: The required signature does not exist on the incoming document.
Response: In the Trading Networks Console, check your transport parameters. Check with your trading
partner to make sure that they are using an agreed upon and valid transport.

ESRN20.000020.000058 Error in : <serviceName>. Unable to run <NOF> with <RNIF 1.1 Service Header>.
Cause: NOFv2 cannot be initiated from a PIP using the RNIF2.0 transport.
Response: In the Trading Networks Console, check your transport parameters on the corresponding TPA.
ESRN20.000020.000060 Error in : <serviceName> service -- Could not send exception to trading partner -- <DUNSID>.
\nReason:\n <errorMessage>.
Cause: An error occurred while sending an exception to the trading partner. The transport may not be
configured correctly.
Response: In the Trading Networks Console, check your transport parameters. Check your network
connectivity. Check with your trading partner to make sure that they are using an agreed upon and valid
ESRN20.000020.000061 In service <serviceName>: Attachment data must be either a <dataType> or an <dataType>

Cause: The attachment is not a valid data type. It must be added as a byte[] or InputStream.
Response: Modify the output map to add attachments as a byte[] or InputStream in the
wm.ip.util:addAttachment service.
ESRN20.000020.000062 In service <serviceName>: ContentID <contentID> has been specified for more than one attachment.
Cause: The same content ID was specified for more than one attachment. This violates the specifications for the
transport.
Response: Make sure that each attachment has a unique content ID. This can be accomplished using the
wm.ip.util:createContentID service and dropping the content ID after each attachment is added.

ESRNET (WmRosettaNet Package)
ESRNET.000000.000001 IO problem while attempting to load the RosettaNet properties: <errorMessage>.

Cause: The RosettaNet properties located in the <serverDir>/packages/WmRosettaNet/config directory may be
corrupt.
Response: Make sure that the RosettaNet properties are valid and in the correct location. In Server
Administrator, reload the package to load the properties file.
ESRNET.000000.000002 Cannot find RosettaNet properties file in this directory: <directoryName>.

Cause: The RosettaNet properties file is not being found in the correct location. By default, the rosettanet.cnf
file is located in the <serverDir>/packages/WmRosettaNet/config/ directory.
Response: Make sure that the RosettaNet properties file is valid and in the correct location. Restart Integration
Server to reload the properties file.
ESRNET.000010.000001 Could not recognize document in : <serviceName>.

Cause: The document was not recognized. The TN document type may not be set up correctly.
Response: Make sure that the PIP transport parameters are set correctly. Make sure that the TN document type
for the incoming document is configured correctly. Check your Trading Networks installation and
configuration.
ESRNET.000033.000001 Signature verification failed, returning HTTP 403.

Cause: The certificates for the trading partner profile either do not exist or are invalid.
ESRNET.000040.000001 Header validation failed, returning HTTP <responseCode>.

Cause: The document header is not valid.

CHAPTER 14
webMethods Trading Networks
TRNSERV.000000.000001 <variable> is empty. At least one <value> must be supplied. Please supply the required value.
Cause: You did not supply a value for the specified variable. At least one value is required.
Response: Supply a value.
TRNSERV.000000.000002 <variable1> and <variable2> are required (<variable1>=<value1>, <variable2>=<value2>). Please

supply the required values.
Cause: Both values are required.
Response: Supply both values.
TRNSERV.000000.000009 The value originally supplied as sender ID for this document was not a valid partner ID. The value
was <partnerID>
Response: Either create a partner profile for the document sender, add this ID to an existing partner's profile, or
tell the document sender to resend the document using a different sender ID value.
TRNSERV.000000.000010 Error formatting error message <messageID>: <exception>

Cause: Unable to format the error message.
TRNSERV.000000.000011 The value originally supplied as receiver ID for this document was not a valid partner ID. The value
was <partnerID>.
Response: Either create a partner profile for the document receiver, add this ID to an existing partner's profile,
or tell the document sender to resend the document using a different receiver ID value.

C H A P T E R 1 4 w e b M e t h o d s Tr a d i n g N e t w o r k s
TRNSERV.000000.000012 <internalVariable> is null.

Cause: An internal variable is unexpectedly null.
TRNSERV.000000.000013 At least one of "<variable1>" and "<variable2>" is required.

Cause: A required value is missing.
Response: Supply one or both of the missing values.
TRNSERV.000000.000016 "\"sourceVersion\" is required. Please supply the required value.

Response: Supply the required value.
TRNSERV.000000.000017 "\"feature\" is required. Please supply the required value.

TRNSERV.000000.000018 At least one input is required.

TRNSERV.000000.000019 Enumeration contains elements that are not Strings.

Cause: An unexpected value was passed to an internal method.
TRNSERV.000000.000020 Bad indexing in <string>.

Cause: Encountered a problem with navigating the structure of an IData object.
TRNSERV.000000.000021 schema cannot be null.

Cause: Attempted to create a Trading Networks IData object with an empty set of name/value pairs.

TRNSERV.000000.000022 schema rows must be 2 wide
TRNSERV.000000.000023 keys cannot be null

TRNSERV.000000.000024 index out of bounds: <index>

Cause: Attempted to seek beyond the end of or before the start of a TNFixedData object.
Response: Supply a valid index to the seek method.
TRNSERV.000000.000025 TNFixedData does not support setKey

Cause: Attempted to use an unsupported method.
Response: Do not call the setKey method.
TRNSERV.000000.000027 TNFixedData does not support delete

Cause: Attempted to use an unsupported method.
Response: Do not call the delete method.
TRNSERV.000000.000028 illegal null key

Cause: Supplied a null key to the keyMatch method on a TNFixedData object.
Response: Supply a valid key value.
TRNSERV.000000.000031 Must supply props

TRNSERV.000000.000032 Must shutdown before starting up again

Cause: Invoked the wm.tn.admin:startup service while the WmTN package is enabled and loaded.
Response: Use the Integration Server Administrator to stop and start the WmTN package. Do not invoke the
wm.tn.admin:start service directly.

TRNSERV.000000.000042 No such enum: <id>

Cause: A wm.tn.enumerate service was invoked with an invalid query enumeration identifier.
Response: Supply a valid enumeration identifier.
TRNSERV.000000.000043 Either <value1> or <value2> must be supplied. Please supply one of these values.
Cause: A valid value was not supplied.
Response: Supply one of the valid values, which are listed in the error message.
TRNSERV.000000.000044 <storageType> is required whenever <storageRef> is supplied. Please supply a value for
<storageType>.
Cause: A storageRef value was supplied, but no value was supplied for storageType.
Response: Supply a value for the storageType variable.
TRNSERV.000000.000047 The following TN properties can only take numeric values: <propertyList>
Cause: Attempted to assign non-numeric values to numeric system properties.
Response: Supply numeric values for numeric system properties.
TRNSERV.000000.000048 Error setting features on SAX parser. Exception message is : <exceptionMessage>

Cause: Threw a SAXException while initializing the SAX parser.
TRNSERV.000000.000056 The <serviceName> service is for Trading Networks internal use only.
Cause: The specified service was invoked, but not by Trading Networks. This service is Trading Networks
internal use only.
Response: Do not invoke this service.
TRNSERV.000000.000057 Error encountered in invoking service wm.tn.samples.helpServices:installTNSamplesACLs

Cause: Internal error installing ACLs for Trading Networks Sample services.
Response: If you want to protect the WmTNSamples services, invoke the
wm.tn.samples:installTNSamplesACLs service.

TRNSERV.000000.000058 Error encountered in writing TN ACL information to disk
Cause: An exception was thrown saving the Trading Networks ACLs to the file system.
Response: The exception was written to the server log. See the server log for details. Take appropriate action to
resolve the problem described in the exception.
TRNSERV.000000.000059 ThreadQueue: too many jobs waiting

Cause: Attempted to spawn more threads than the configured limit.
Response: Use the wm.tn.admin:setThreadQueueConfig service to increase the value of the
tn.thread.maxWaiting system property.
TRNSERV.000000.000061 <variable> is not an Integer

Cause: Invalid data type supplied to a service.
Response: Supply an Integer for the specified value.
TRNSERV.000000.000067 Unable to update password for <deliveryMethodName> with handle <passwordHandle>

Cause: An exception was thrown when Trading Networks attempted to update the password associated with a
profile delivery method.
Response: Take appropriate action to resolve the problem described in the exception.
TRNSERV.000000.000068 Unable to retrieve password for <deliveryMethodName> with handle <passwordHandle>

Cause: An exception was thrown when Trading Networks attempted to retrieve the password associated with
a profile delivery method.
TRNSERV.000000.000069 Unable to insert password for <deliveryMethodName> with handle <passwordHandle>

Cause: An exception was thrown when Trading Networks attempted to insert the password associated with a
TRNSERV.000000.000070 Unable to save password for <deliveryMethodName> with handle <passwordHandle>

Cause: An exception was thrown when Trading Networks attempted to save the password associated with a

TRNSERV.000000.000071 Unable to delete password for <deliveryMethodName> with handle <passwordHandle>

Cause: An exception was thrown when Trading Networks attempted to delete the password associated with a
TRNSERV.000000.000072 Either <value1> or <value2> must be supplied, but not both. Please supply a value for only one of
these.
Cause: You supplied the specified two values; however, only one value can be specified.
Response: Supply only one of the two values.
TRNSERV.000001.000001 Invalid datatype. "cert" must be a byte[] or a X509Certificate.

Cause: You invoked a service and supplied a digital certificate value that is not a recognized type.
Response: Supply either an X509Certificate or the bytes from an X509Certificate.
TRNSERV.000001.000005 The user associated with this certificate (<userName>) does not have a TN profile.
Cause: The supplied digital certificate is associated with an IS user, but that user is not a Trading Networks
partner.
Response: Either create a partner profile for the user, or supply a certificate that is associated with a Trading
Networks partner.
TRNSERV.000001.000007 An error occurred when the intended receiver tried to accept this document. The original error
message was <exception>.
Cause: An exception was thrown while accepting a polled document.
TRNSERV.000001.000008 Unable to retrieve partner profile associated with supplied certificate.

Cause: An exception was thrown while retrieving the partner associated with a digital certificate.
Response: Trading Networks wrote the exception to the server log. See the server log for details. Take
appropriate action to resolve the problem described in the exception.
TRNSERV.000001.000010 Unable to save partner's certificate.

Cause: An exception was thrown while saving a partner's certificate.

TRNSERV.000001.000011 There is no Integration Server user associated with the supplied certificate.
Cause: The supplied digital certificate is not associated with an IS user.
Response: Supply a certificate that is associated with an IS user that is also a Trading Networks partner.
TRNSERV.000001.000014 Unable to set signing keys to be used for sending documents to specified partner.
Cause: The wm.tn.access:setSigningKeys service was unable to save the security information needed to sign
documents sent to a partner.
TRNSERV.000001.000015 Unable to retrieve signing keys to be used for sending documents to specified partner.
Cause: The wm.tn.access:getSigningKeys service was unable to retrieve the security information needed to sign
TRNSERV.000001.000019 Unable to retrieve certificate information of requested partner (partnerID=<partnerID>).

Cause: The wm.tn.access:getSigningKeys service was unable to retrieve the security information needed to sign
Response: Use the Trading Networks Console to ensure that the signing keys for this partner are set correctly.
TRNSERV.000001.000028 Invalid feature specified.

Cause: While checking whether a feature was enabled, discovered that an invalid feature was specified.
TRNSERV.000001.000029 Error retrieving Console restrictions.

Cause: An exception was thrown while determining what features are available to the Console.
TRNSERV.000001.000030 No session available

Cause: Attempted an action that requires an active session, but no active session was found.

TRNSERV.000001.000031 No user available from session

Cause: Unable to determine the connected user.
TRNSERV.000001.000032 Group TNPartners not defined

Response: Run the wm.tn.admin:install service to create TNPartners and other required user groups.
TRNSERV.000002.000002 Document type <doctypeName> has no validation service defined. Validation fails.
TRNSERV.000002.000003 No Validation Service

Cause: A TN document type has no validation service defined. Validation fails.
TRNSERV.000002.000004 <xmlElement>: <errorMessage>

Cause: A document sent to Trading Networks failed validation.
Response: Notify the document sender.
TRNSERV.000002.000005 Doctype <doctypeName>: no validation svc. defined; validation skipped

Cause: Document type has no validation service defined. Validation fails.
TRNSERV.000002.000010 The doctype for this document (<doctypeName>) does not have a validation schema defined;
validation fails.
Cause: The document matches a TN document type that indicates the document's structure should be
validated, but no schema was defined.
Response: Update the TN document type, and specify the schema to use for document validation.
TRNSERV.000002.000011 No Validation Schema

Cause: The document matches a processing rule that indicates the document's structure should be validated,
but no schema was defined.
Response: Update the TN document type that the document matches to specify the schema to use for document
validation.

TRNSERV.000002.000012 The validation service for this XML document, <serviceName>, could not be successfully invoked.
The original exception message is: <exceptionMessage>
Cause: The service used to validate the document's structure threw an exception.
TRNSERV.000002.000013 The validation service used for this document (<serviceName>) failed with the following exception
message: <exception>
TRNSERV.000002.000014 Validation Service Failed

TRNSERV.000002.000015 XML validation failed: does not apply to non-XML documents.

Cause: Invoked the wm.tn.doc.xml:validate service with a document that is not XML.
Response: Supply an XML document.
TRNSERV.000002.000016 XML validation failed: no document content available

Cause: Document is empty.
Response: Supply an XML document that has content.
TRNSERV.000002.000017 The validation service, <serviceName> aborted processing of this document. The message was
<exceptionMessage>.
Cause: The document is not valid XML.
TRNSERV.000002.000019 Flat file validation failed. Document type is not "flat file".
Cause: Attempted to use a flat file validation service to validate a document that is not a flat file.
Response: Supply a flat file document.
TRNSERV.000002.000020 Flat file validation failed: no document content available

Cause: Document is empty.
Response: Supply a flat file document that has content.

TRNSERV.000002.000021 Flat file validation failed. Document type "<doctypeName>" has no parsing schema.
Cause: The document matches a TN document type that indicates the document's structure should be
validated, but no schema was defined.
Response: Update the TN document type, and specify the schema to use for document validation.
TRNSERV.000002.000022 Validation error

Cause: The flat file document structure is invalid.
TRNSERV.000003.000003 System property <propertyName> is invalid: <propertyValue>. To correct the property, go the TN
Properties page of the WmTN package in the Integration Server Administrator, or edit the
\'packages\\WmTN\\config\\properties.cnf\' file.
Cause: not used; only used for internal testing purposes.
TRNSERV.000003.000010 Error running archive operation: <exceptionMessage>

Cause: Encountered an Exception while archiving documents.
Response: See the Exception message for details. Take appropriate action to resolve the problem described in
the Exception.
TRNSERV.000005.000003 Service manager create failed for server <b2b.my-company.com> - <SQLException>

Cause: Encountered a problem while communicating with the database. See the text in the SQL exception for
details.
Response: Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can
connect to the database. If no connection problem exists, take appropriate action to resolve the problem
described in the exception.
TRNSERV.000005.000005 Unable to get profile for <partnerID> - <SQLException>

details.

TRNSERV.000005.000006 Unable to remove delivery service <MyCustomService> - <SQLException>
details.
TRNSERV.000005.000014 Unable to create delivery task <ID> - service <custom.delivery:deliverOne> does not exist
Cause: Attempted to deliver a document using a non-existent delivery service.
Response: Correct the serviceName parameter sent to wm.tn.delivery:deliver.
TRNSERV.000005.000027 Unable to create service data for partner <partnerID> - <errorDetails>

Cause: Attempted to deliver a document to a partner that cannot receive the document. Receiver is either
INACTIVE or is My Enterprise (the entity hosting this Trading Network).
Response: Deliver the document to a valid trading partner with an ACTIVE status.
TRNSERV.000005.000028 Unable to set private key and certificate chain - <exceptionMessage>

Cause: Encountered an exception while setting the certificate chain and private key in preparation to deliver a
document. See the exception message for details.
TRNSERV.000005.000032 <IOException> refreshing <deliveryJob> cache: <exceptionMessage>

Cause: Encountered an exception while refreshing an internal cache. See the exception message for details.
TRNSERV.000005.000038 Error transporting via <primaryHTTP>: <exceptionMessage>

Cause: Encountered an exception while delivering a document. See the exception message for details.
Response: Take appropriate action to resolve the problem described in the exception, if possible. It may be a
network error beyond your control.

TRNSERV.000005.000040 <IOException> initializing task store: <exceptionMessage>

Cause: Encountered an exception while initializing internal caches used for document delivery. See the
exception message for details.
TRNSERV.000005.000041 <SQLException> deleting delivery service <MyCustomService>: <exceptionMessage>

Cause: Encountered an exception while removing a registered delivery service from the database.
TRNSERV.000005.000050 <SQLException> deleting task <taskID>: <exceptionMessage>

Cause: Encountered an exception while deleting a delivery or routing task.
TRNSERV.000005.000054 DeliveryUtils init error: Unable to get profile store: <exceptionMessage>

Cause: Could not access the Profile Store during server initialization.
Response: Copy the exception details and call webMethods Customer Care.
TRNSERV.000005.000055 Unable to register delivery service <MyCustomService> - <exceptionMessage>

Cause: Encountered an exception while registering a delivery service.
TRNSERV.000005.000064 Unable to initialize delivery interface

Cause: Encountered an exception while initializing the Delivery Service Manager.

TRNSERV.000005.000065 Unable to register delivery defaults
Cause: Encountered an exception while registering the built-in delivery services.
TRNSERV.000005.000066 Unable to deliver bizdoc by service

Cause: Encountered an exception when wm.tn.deliver:deliverByService was invoked.
TRNSERV.000005.000067 Error delivering bizdoc

Cause: Encountered an exception while delivering a document.
TRNSERV.000005.000068 Error getting delivery job

Cause: Encountered an exception while retrieving a delivery job.
TRNSERV.000005.000069 Error getting delivery job output

Cause: Encountered an exception while retrieving the output of a reliable delivery job.
TRNSERV.000005.000070 Error getting delivery job status

Cause: Encountered an exception while retrieving the status of a delivery job.

TRNSERV.000005.000071 Error removing delivery job

Cause: Encountered an exception while removing a reliable delivery job.
Response: Use the JDBC Pools page on the Integration Server Administrator to check that the Integration
Server can connect to the database. If no connection problem exists, take appropriate action to resolve the
problem described in the exception.
TRNSERV.000005.000072 Error restarting delivery job

Cause: Encountered an exception while restarting a reliable delivery job.
Response: Use the JDBC Pools page on the Integration Server Administrator to check that the Integration
Server can connect to the database. If no connection problem exists, take appropriate action to resolve the
problem described in the exception.
TRNSERV.000005.000073 Error getting registered delivery service <My Custom Service>

Cause: Encountered an exception while retrieving a registered delivery service.
TRNSERV.000005.000074 Error getting registered delivery services

Cause: Encountered an exception while retrieving the set of registered delivery services.
TRNSERV.000005.000075 Error determining if delivery service <customServiceName> is registered

Cause: Encountered an exception while retrieving a named registered delivery service.
TRNSERV.000005.000076 Error refreshing service cache

Cause: Encountered an exception while refreshing the cache of registered delivery services.

TRNSERV.000005.000077 Error registering service <MyCustomService>
Cause: Encountered an exception while registering a delivery service.
TRNSERV.000005.000078 Error removing service <MyCustomService>

Cause: Encountered an exception while unregistering a delivery service.
TRNSERV.000005.000081 Couldn't query delivery service table

Cause: Encountered a SQLException while reading delivery services.
Response: Take appropriate action to resolve the problem described in the exception, if possible.
TRNSERV.000005.000082 Couldn't query delivery job table

Cause: Encountered a SQLException while reading delivery jobs.
Response: Take appropriate action to resolve the problem described in the exception, if possible.
TRNSERV.000005.000083 Property watt.server.smtpServer is not set

Cause: Cannot send e-mail messages because the system property, watt.server.smtpServer, has not been set.
Response: Use the properties page of the Integration Server Administrator to supply a value for the
watt.server.smtpServer property.
TRNSERV.000005.000084 Receiver of document cannot be self

Cause: A document is being sent from this Trading Networks server and the receiver of the document is the
host of the Trading Network. You cannot send a document to yourself.
TRNSERV.000005.000085 Receiver of document is not Active

Cause: Status on the partner profile for the receiver of the document is not 'Active'. Documents can only be sent
to active partners.

TRNSERV.000005.000086 Unknown protocol: <protocol>

Cause: Attempted to send a document via an unknown protocol. Documents must be sent using one of the
registered delivery services.
Response: Use a registered delivery service to send the document.
TRNSERV.000005.000087 Destination info not found

Cause: Attempting to send a document, but the receiver's destination information cannot be found.
Response: Examine the document to learn the intended receiver. Make sure the receiver's profile has valid
delivery method information.
TRNSERV.000005.000090 Unable to initialize DeliveryStore <Exception message>

Cause: Encountered an exception during initialization.
TRNSERV.000005.000092 Service not registered

Cause: Attempted to remove a delivery service that is not registered.
Response: Check the name of the registered delivery service you want to remove.
TRNSERV.000005.000094 <exceptionType> dequeuing task from queue <queueName>: <exceptionMessage>

TRNSERV.000005.000096 Delivery queue <queueName> refers to Delivery service <serviceName> which is not registered.
Response: Use the Trading Networks Console to update the delivery queue so that it uses a valid batch
delivery service.
TRNSERV.000005.000097 Cannot deliver document. Receiver is not active. (DocID=<internalDocID>, ReceiverD=<partnerID>)

Cause: Queued a document for scheduled delivery, but the receiver is inactive and cannot receive documents.
Response: Activate the receiver's trading partner profile, if appropriate.
TRNSERV.000005.000098 Unable to get document content for delivery. (DocID=<internalDocID>)

Cause: Queued a document for scheduled delivery and encountered an error while retrieving document
content.

TRNSERV.000005.000099 Cannot register a delivery service with the same name as a built-in delivery service (<Primary
HTTP>).
Cause: This name is reserved for a built-in Trading Networks delivery service.
Response: Change the delivery service's name.
TRNSERV.000005.000101 Cannot get certificate information from security store for partner <partnerID> in getting delivery
information: <Exception message>
Cause: Encountered an exception while retrieving the certificate chain and private key for a trading partner.
TRNSERV.000005.000105 Unable to get profile for partner <partnerID> - <Exception message>

Cause: Encountered an exception while retrieving a trading partner profile.
TRNSERV.000005.000106 Unable to get destination info for partner <partnerID> - <Exception message>
Cause: Encountered an exception while retrieving destination information from a trading partner profile in
preparation for document delivery.
TRNSERV.000005.000107 Encountered error while delivering by context: <Exception message>

Cause: Encountered an exception while delivering a document using an internal webMethods protocol
(Context).
TRNSERV.000005.000108 Unable to deliver document <internalDocID>. Delivery service [<serviceName>] does not exist
Cause: Document delivery failed because the associated delivery service does not exist.
Response: Create the missing delivery service or specify a different delivery service.

TRNSERV.000006.000002 An ID type named <type> already exists.

Cause: Trading Networks attempted to create an external ID type with the name <type>; however an external
ID type with that name already exists.
Response: Specify the name of an external ID type that does not already exist when creating an external ID
type.
TRNSERV.000006.000003 A contact type named <type> already exists.

Cause: Trading Networks attempted to create a contact type with the name <type>; however a contact type
with that name already exists.
Response: Specify the name of a contact type that does not already exist when creating a contact type.
TRNSERV.000006.000004 A field group named <group> already exists.

Cause: Trading Networks attempted to create a field group with the name <group>; however a field group
with that name already exists.
Response: Specify the name of a field group that does not already exist when creating a field group.
TRNSERV.000006.000005 Could not get profile dictionary.

Cause: Trading Networks encountered an unexpected error during initialization.
Response: The exception was written to the server log. See the server log for details. Take action appropriate to
TRNSERV.000006.000006 Could not retrieve field definitions.

Cause: An exception was thrown while retrieving profile field definitions.
TRNSERV.000006.000007 Could not add field definition.

Cause: An exception was thrown while saving a profile field definition.
TRNSERV.000006.000008 Could not update field definition.

Cause: An exception was thrown while updating a profile field definition.

TRNSERV.000006.000009 "definition" is required.
Cause: A service was invoked that requires a value for "definition."
TRNSERV.000007.000001 Persistence Service Failed

Cause: Encountered an exception while saving the document to the database.
Response: See the full message for details.
TRNSERV.000007.000002 An error occurred trying to insert this document into the database. The original error message
was: <exceptionMessage>
Response: Take appropriate action to correct the problem described in the exception.
TRNSERV.000007.000007 Non-unique ID(s) detected

Cause: This document duplicates one already in the database.
TRNSERV.000007.000008 This document matched <number> existing documents in the database on the basis of extended
uniqueness criteria (document ID and/or sender ID).
Cause: This document duplicates one already in the database.
TRNSERV.000007.000015 Couldn't get document bytes

Cause: An exception was thrown while adding the document content to the BizDocEnvelope. The document
might be corrupt.
TRNSERV.000007.000016 No such document: <docId>

Cause: The wm.tn.doc:view service was passed an invalid internal document ID.
Response: Supply a valid internal document ID to the wm.tn.doc:view service.

TRNSERV.000007.000018 Invalid duplicate checking service.

Cause: Custom duplicate check was selected, but either a duplicate check service was not specified or the
specified duplicate check service was invalid
Response: Using the Trading Networks Console, update the TN document type and/or the processing rule and
specify a valid duplicate checking service.
TRNSERV.000007.000019 The BizDocType refers to a non-existent duplicate checking service: <serviceName>. It may have
been renamed, disabled or deleted.
Cause: Custom duplicate check was selected, but no duplicate check service was specified or the specified
duplicate check service was invalid. This error also could occur when the specified duplicate check service has
been renamed, disabled, or deleted.
Response: Using the Trading Networks Console, update the TN document type and/or the processing rule and
specify a valid duplicate checking service.
TRNSERV.000007.000020 Duplicate document detected.

Cause: You received a document that failed a custom duplicate document check. The custom duplicate
checking service flagged the document as a duplicate.
Response: You can ignore this message, or you can notify the sender of the document that you have received a
duplicate.
TRNSERV.000008.000001 No profile store to validate partner ID.

Cause: Trading Networks was unable to retrieve the profile store.
TRNSERV.000008.000002 Error transforming attribute <attribName>: <exceptionMessage>

Cause: An exception was thrown while transforming a document attribute value.
Response: The exception was written to the server log. See the log for details. Take appropriate action to resolve
the problem described in the exception.
TRNSERV.000008.000003 BizDocAttribute: can't connect to profile store.

Cause: Encountered an Exception during initialization.
error logs, a copy of the Support Information page from the Trading Networks Console, and the
WmTN/config/properties.cnf file.

TRNSERV.000008.000006 No profile store to transform attribute <attribName>.
Cause: Trading Networks was unable to retrieve the profile store.
TRNSERV.000008.000007 Unable to transform attribute <attribName>: attribute type <dataType> doesn't match function type
<dataType>.
Cause: Trading Networks could not transform the value of the attribute because the selected transformation is
inappropriate for the data type of the attribute.
Response: Using the Trading Networks Console, update the TN document type that specifies the invalid
transformation for the specified attribute. Select a transformation that is appropriate for the data type of the
attribute.
TRNSERV.000008.000008 Error fetching all attributes: <exceptionMessage>

Cause: An exception was thrown while reading all attributes from the database.
TRNSERV.000008.000009 Error defining attribute <attribName>: <exceptionMessage>

Cause: An exception was thrown while saving an attribute to the database.
TRNSERV.000008.000010 Error listing types for <attribID>: <exceptionMessage>

Cause: An exception was thrown while retrieving all TN document types that use an attribute.
TRNSERV.000008.000011 Error redefining attribute <attribID>: <exceptionMessage>

Cause: An exception was thrown while updating an attribute in the database.
TRNSERV.000008.000012 Supplied value must be a number.

Cause: A processing rule contains extended criteria that uses a custom attribute with a NUMBER data type;
however, the value you specified in the condition for this attribute is not a numeric value.
Response: Using the Trading Networks Console, update the extended criteria in the processing rule to supply a
numeric value for attributes that have a NUMBER data type.

TRNSERV.000008.000013 Supplied value can not be transformed to a date.

Cause: A processing rule contains extended criteria that uses a custom attribute with a DATETIME data type;
however, the value you specified in the condition for this attribute is not a date.
Response: Using the Trading Networks Console, update the extended criteria in the processing rule to supply a
date value for attributes that have a DATETIME data type.
TRNSERV.000008.000014 <attribName> attribute value is a date but there is no transform.

Cause: A TN document type indicates that a custom attribute with a DATETIME data type should be extracted
from a document. However, the TN document type does not specify a date transformation for the custom
attribute.
Response: Using the Trading Networks Console, update the TN document type to specify an appropriate date
transformation for the custom attribute.
TRNSERV.000008.000015 <attribName> attribute is configured for custom transformation, but no transformation service is
specified.
Cause: A TN document type indicates that a custom attribute should perform custom attribute transformation.
However, the TN document type does not specify a transformation service.
Response: Using the Trading Networks Console, update the TN document type to specify a transformation
service.
TRNSERV.000008.000016 Error performing custom transformation on the <attribName> attribute.

Cause: Encountered an Exception while updating an attribute in the database.
the exception.
TRNSERV.000008.000017 Custom transformation <serviceName> for the <attributeName> attribute returned the wrong type.
Should be <dataType>
Cause: Custom attribute transformation did not return the data type that matches the data type of the
associated attribute.
Response: Modify the custom attribute transformation service to return the correct data type specified in the
error message.
TRNSERV.000008.000018 Custom transformation service <serviceName> for the <attributeName> attribute did not return
\"newValues\" in the pipeline.
Cause: Custom attribute transformation service did not return the required output parameter 'newValues'.
Response: Modify the custom attribute transformation service to return the 'newValues' output parameter.

TRNSERV.000008.000019 <attribName> attribute value is a date list but there is no transform.
Cause: The TN document type does not specify a transformation for a date list type attribute.
Response: Using the Trading Networks Console, update the TN document type to specify a transformation
service.
TRNSERV.000008.000020 Unable to parse the given value. Value <value> could not be converted to date format.
Cause: Unable to convert the value extracted from the document to date format.
the exception.
TRNSERV.000008.000021 Attribute transformation for <attribName> of doctype <docTypeName> generated an exception.

The original exception message is: <exceptionMessage>.
Cause: Encountered an Exception while updating an attribute in the database.
the exception.
TRNSERV.000008.000022 Attribute transformation function code <functionCode> is invalid.

Cause: A TN document type indicates an invalid attribute transformation function.
Response: Using the Trading Networks Console, update the TN document type to specify a valid
transformation function.
TRNSERV.000009.000006 Converting the signed body of this document into a string failed. Verification cannot continue. The
original signed body was <content>.
Response: If the signed body of the document is invalid, notify the document sender.
TRNSERV.000009.000008 This doctype (<doctypeName>) has no verification service defined. Verification cannot continue.
Cause: This TN document type (<doctypeName>) has no verification service defined. Verification cannot
continue.
Response: If you are using a built-in TN document type, contact webMethods Customer Care. If you are using
your own TN document type, specify a verification service for it.
TRNSERV.000009.000009 No Verification Service.

Cause: The TN document type has no verification service defined. Verification cannot continue.
Response: If you are using a built-in TN document type, contact webMethods Customer Care. If you are using
your own TN document type, specify a verification service for it.

TRNSERV.000009.000011 The signature query for doctype <doctypeName> (<query>) generated an error. The error was
<exceptionMessage>.
Cause: The signature query (<query>) for the TN document type (<doctypeName>) generated an error. The
error was <exceptionMessage>.
Response: If the signed body of the document is invalid, notify the document sender.
TRNSERV.000009.000015 Query Failed.

Cause: A signature query was defined for the TN document type, but failed to produce a result on this
document.
Response: Either adjust the signature query that is defined in the TN document type, or notify the document
sender that the structure of the document is incorrect.
TRNSERV.000009.000017 This document type (<doctypeName>) is missing one or both of its signature queries (Signature
and SignedBody). Verification cannot proceed.
Response: Using the Trading Networks Console, update the TN document type to specify both a signature
query and a signed body query.
TRNSERV.000009.000018 Missing Signature Query(s).

Cause: This TN document type is missing one or both of its signature queries (Signature and SignedBody).
Trading Networks cannot proceed with the verification of the signature.
Response: Using the Trading Networks Console, update the TN document type to specify both a signature
query and a signed body query.
TRNSERV.000009.000019 The signed body query for doctype <doctypeName> (<query>) generated an error. The error was
<exceptionMessage>.
Cause: The signed body query (<query>) for the TN document type (<doctypeName>) generated an error. The
Response: Take appropriate action to resolve the problem described in the exception. If the structure of the
document is incorrect, notify the document sender.
TRNSERV.000009.000020 The signature of this document was invalid; no information was available about the party or parties
that signed it.

TRNSERV.000009.000021 No Signer Info Available.
Cause: The signature of this document was not valid. No information was available about the party or parties
that signed it.
TRNSERV.000009.000022 The PKCS verification service, pub.security.pkcs7:verify, produced an error trying to verify this
document. The error was <exception>.
Cause: Trading Networks threw an exception verifying a document signature.
Response: Take appropriate action to resolve the problem described in the exception. If the signature is invalid,
notify the document sender.
TRNSERV.000009.000023 PKCS Service Error

Cause: The PKCS verification service, pub.security.pkcs7:verify, produced an error trying to verify this
document.
TRNSERV.000009.000024 The verification service for this document (<serviceName>) generated an error. The original error
was <exception>.
Cause: An exception was thrown verifying a document signature.
TRNSERV.000009.000025 Verification Failed.

Cause: An exception was thrown verifying a document signature.
TRNSERV.000009.000026 The signature query for doctype <doctypeName> (<query>) failed to produce a value. Without a
signature, verification cannot proceed.
Cause: A signature query was defined for the TN document type, but failed to produce a result on this
document.
Response: Either update the TN document type to adjust the signature query, or notify the document sender
that the structure of the document is incorrect.

TRNSERV.000009.000028 The signed body query for doctype <doctypeName> (<query>) failed to produce a value. Without a
signed body, verification cannot proceed.
Cause: A signed body query was defined for the TN document type, but failed to produce a result on this
document.
Response: Either update the TN document type to adjust the signed body query, or notify the document sender
that the structure of the document is incorrect.
TRNSERV.000009.000030 Base-64 decoding the signature for this document failed to produce a value. The signature (before
decoding) was <number> bytes.
Cause: Trading Networks could not decode the signature. The signature might be invalid.
TRNSERV.000009.000031 Decoding Error

Cause: Trading Networks could not decode the signature. The signature might be invalid.
TRNSERV.000009.000032 XML <operation> failed: does not apply to non-XML documents.

Cause: Trading Networks attempted to perform an operation on a non-XML document; however, the operation
can be performed only on XML documents.
TRNSERV.000009.000033 XML <operation> failed: no document content available.

Cause: Trading Networks attempted to perform an operation that failed because the document has no content.
TRNSERV.000009.000034 Bad XML content.

Cause: An exception was thrown while retrieving the document.
TRNSERV.000009.000035 An error prevented fetching the content of this XML document for <operation>. The original error
was <exception>.
Cause: An exception was thrown while retrieving the document.

TRNSERV.000009.000036 The verification service, <serviceName> aborted processing of this document. The message was
<errorMessage>.
Cause: A RoutingAbortedException was thrown from the verification service, which caused the document
processing to abort.
Response: Take appropriate action to resolve the problem described in the exception. If the document is
invalid, notify the sender.
TRNSERV.000009.000037 The signing service, <serviceName> aborted processing of this document. The message was
<errorMessage>.
Cause: A RoutingAbortedException was thrown from the verification service, which caused the document
processing to abort.
Response: Take appropriate action to resolve the problem described in the exception. If the document is
invalid, notify the sender.
TRNSERV.000010.000010 Unable to map certificate to user for new partner <partnerID>.

Cause: The wm.tn.security:setVerifyCertificateSet service was unable to save certificates for a new trading
partner.
Response: Save the partner's profile with no certificates; then add the partner's certificates.
TRNSERV.000010.000019 <SecurityUtil> could not retrieve the ProfileStore.

Cause: The Profile Store is inaccessible.
Response: Reload the WmTN package or restart the Integration Server.
TRNSERV.000010.000030 Unable to retrieve the <externalIDType> ID for partner <partnerID>

Cause: Could not convert the internal partner ID into an external ID.
Response: Make sure the partner has a value for this type of external ID.
TRNSERV.000010.000034 An invalid or expired certificate was received from <TradingPartner> and rejected.
Cause: An invalid or expired certificate was received and rejected from the Trading Partner specified in the
message.
Response: Notify the Trading Partner specified in the message that their certificate is either invalid or expired.
TRNSERV.000010.000037 Received a certificate issued by <CertificateAuthority>, who is not on your list of trusted
Certificate Authorities.
Cause: The Certificate Authority specified in the message is not on your list of trusted sources.

+TRNSERV.000010.000038 Problem creating B2B account for partner (username=<userName>).

Cause: An account could not be created on the Integration Server for the partner.
Response: Create the account manually for the partner. The user name must match the partner's required
external ID.
TRNSERV.000010.000050 If <variable1> is supplied, <variable2> must also be supplied.

Cause: You must supply either both values or neither value.
Response: Supply both values or neither value.
TRNSERV.000010.000085 The Trading Networks user does not have permission to change System properties. The certificate
chain verifier is not correctly initialized. All incoming certificate chains will be trusted.
Cause: The watt.security.cert.wmChainVerifier.trustByDefault property may not be set correctly.
Response: Ask the Administrator to set the 'watt.security.cert.wmChainVerifier.trustByDefault' property
appropriately.
TRNSERV.000010.000103 Either <variable1> or <variable2> must be supplied.

Cause: A value must be supplied for one of the two variables, but no value was supplied for either variable.
Response: Supply a value for one of the variables.
TRNSERV.000011.000002 An error occurred when this partner polled for documents on this server. The original error
message was <exception>.
Cause: An exception was thrown while polling for documents.
TRNSERV.000011.000014 Error polling for documents.

Cause: An exception was thrown while polling for documents.
TRNSERV.000011.000017 An error occurred when trying to connect to this partner for polling. The original error was:
<exception>
Response: Take appropriate action to resolve the problem described in the exception. You might need to
contact your trading partner about the error.

TRNSERV.000011.000018 Error connecting for polling.
Cause: An error occurred when trying to connect to this partner for polling.
contact your trading partner about the error.
TRNSERV.000011.000021 The user account that schedules polling jobs is <userName>. The account does not exist on the
B2B Server.
Response: Create a user account for <userName> and reload the WmTN package or restart the Integration
Server.
TRNSERV.000011.000031 An error occurred in the process of accepting a document polled from this partner. The original
document ID was <docID>. The original error message was <exception>.
TRNSERV.000011.000037 Error accepting document.

Cause: An exception was thrown while accepting a document polled from a partner.
TRNSERV.000011.000052 Unable to initialize TN Polling.

Cause: An exception was thrown during initialization.
Response: The exception was written to the server log. See the log for details. Take appropriate action to resolve
TRNSERV.000011.000053 User <userName> (partnerID=<partnerID>) is not an administrator and attempted to accept a

document (docID=<internalDocID>) that does not belong to him.
Cause: A partner attempted to accept a pollable document; however, the specified partner is not the receiver of
the document.
Response: Review the log message. Contact the partner identified in the log message to inform the partner that
the partner can only accept pollable documents for which that partner is the receiver.
TRNSERV.000011.000054 You do not have the authority to accept this document. Only administrators may accept
documents that they did not receive.
Cause: A partner attempted to accept a pollable document; however, the partner is not the receiver of the
document.
Response: Review the log message. Contact the partner identified in the log message to inform the partner that
the partner can only accept pollable documents for which that partner is the receiver.

TRNSERV.000011.000055 No document with an ID of <internalDocID> exists. No document accepted.

Cause: A partner is trying to accept a pollable document that does not exist within Trading Networks.
Response: Review the log message. Work with the partner specified in the log message to resolve the issue.
TRNSERV.000012.000001 Could not delete field group.

Cause: An exception was thrown while deleting a profile field group.
Response: The exception was written to the error log. See the log for details. Take appropriate action to resolve
TRNSERV.000012.000003 Could not add partner profile for <corporationName>.

Cause: An exception was thrown while saving a partner profile.
Response: The exception was written to the error log. See the log for details. Take appropriate action to resolve
TRNSERV.000012.000005 The partner specified (id=<partnerID>) has a <idType> ID of <idValue>, but there is no matching IS
user account.
Cause: Trading Networks could not find an Integration Server user account for this partner.
Response: Verify that the partner has a user account on the Integration Server and that the account name
matches the partner's required external ID value.
TRNSERV.000012.000006 Attempted to save an extended field value with an unknown field ID (id=<fieldID>).
Response: Specify a valid field ID.
TRNSERV.000012.000008 Got null or empty extended profile fields

Cause: The "fields" input variable is required.
Response: Pass the extended fields you want to save in the "fields" variable.
TRNSERV.000012.000009 Attempted to save an external ID that has an unknown type (type code=<idTypeCode>).
Cause: Trading Networks attempted to save an external ID for a partner; however, the external ID is associated
with an external ID type that has not been defined.
Response: To save a new type of external ID for a partner, you must first define the external ID type. To do so,
use the wm.tn.dictionary:addIDType service.

TRNSERV.000012.000010 ID Type <idType> is not valid. Not found in the Trading Networks database.
Response: Supply a valid external ID type. Use the wm.tn.dictionary:addIDType service to define a new
external ID type.
TRNSERV.000012.000011 Attempted to save a contact that has an unknown type (type code=<contactType>).
Cause: Trading Networks attempted to save a contact for a partner; however, the contact is associated with a
contact type that has not been defined.
Response: To save a new type of contact for a partner, you must first define the contact type. To do so, use the
wm.tn.dictionary:addContactType service.
TRNSERV.000012.000012 Cannot delete a standard field

Cause: Attempted to delete a standard profile field. You can only delete extended profile fields.
TRNSERV.000012.000013 Partner (id=<partnerID>) has no <idType> ID. Cannot add certificate to IS Certificate Map.
Cause: To add a certificate for a partner, Trading Networks associates the certificate with the partner's
Integration Server user account. The partner's IS user account name is its required external ID; however, this
partner does not have an external ID that is associated with the required external ID type (<idType>).
Response: Create an external ID of the specified required external ID type (<idType>) for the partner. Verify
that corresponding Integration Server user account was created. The partner's user account name must match
the value of the required external ID type.
TRNSERV.000012.000014 <number> not a valid Group ID. Must be greater than 0.

Response: Supply a valid group ID value.
TRNSERV.000012.000015 Port must be a positive integer

Cause: When specifying a partner's host and port, the port value must be greater than zero.
Response: Supply a valid value for the port number.
TRNSERV.000012.000016 Could not decode bizdoc

Cause: Trading Networks created an internal BizDocEnvelope in order to validate the profile data, but Trading
Networks could not decode the BizDocEnvelope.
TRNSERV.000012.000017 Could not add <typeData>. A <typeInstance> with an ID of <id> already exists.
Response: Save this type with a different ID.

TRNSERV.000012.000018 A profile already exists for the host of this Trading Network. Turn off the SELF setting on the
corporate component of the profile and save it again.
Cause: The Enterprise profile already exists.
Response: If you are programmatically saving profiles, set the Self? variable to false before attempting to save
the profile. If you are using the Trading Networks Console to save profiles, contact webMethods Customer
Care.
TRNSERV.000012.000019 Could not validate profile: received null bizdoc

Cause: Trading Networks should have created an internal BizDocEnvelope to validate profile data, but the
BizDocEnvelope is null.
TRNSERV.000012.000020 No '<elementName>' element found in bizdoc.

Cause: Trading Networks created an internal BizDocEnvelope to validate profile data, but the BizDocEnvelope
did not contain the "errors" element.
TRNSERV.000012.000021 Cannot set extended fields.

Cause: An exception was thrown while saving extended fields to the database.
TRNSERV.000012.000024 Cannot access profile store.

TRNSERV.000012.000026 You are using webMethods Trading Partners. To be able to add more partner profiles, please
upgrade to webMethods Trading Networks.
Cause: When using webMethods Trading Partners, you can create only one profile other than your own.
Response: If you need to create additional partner profiles, upgrade to webMethods Trading Networks.
TRNSERV.000012.000027 Could not retrieve <id1> using <id2>

Cause: The <id2> value is invalid.
Response: Supply a valid value.

TRNSERV.000012.000028 An error occurred while retrieving company logos.
Cause: An exception was thrown while retrieving company logos.
TRNSERV.000012.000029 Importing a profile for <CorpName_UnitName> (id=<partnerID>), which is marked as \"My

Enterprise\", but it has different ID than the existing My Enterprise profile for this Trading Network. Cannot change the
identity of the My Enterprise profile. Process terminated.
Cause: You attempted to import the Enterprise. However, the target Trading Networks system already has an
Enterprise profile, which has a different ID than the one you are attempting to import. Trading Networks
cannot import the Enterprise profile.
Response: Do not attempt to import the Enterprise profile.
TRNSERV.000012.000030 Could not get profile for user (username=<name>).

Cause: An exception was thrown while retrieving a partner profile for a user.
TRNSERV.000012.000031 <securityObject> is required if any of the following is supplied: Certificate, CA Certificate or Private
key.
Cause: If any of the following fields are supplied, they must all be supplied: Certificate, CA Certificate, Private
Key.
Response: Supply all the required values.
TRNSERV.000012.000032 Extended fields cannot have a column name.

Cause: The column name on an extended profile field is not null.
Response: If you are programmatically creating extended fields, do not set the Column Name. If you are using
the Trading Networks Console to create extended fields, contact webMethods Customer Care.
TRNSERV.000012.000033 Extended fields cannot have a table name.

Cause: The table name on an extended profile field is not null.
Response: If you are programmatically creating extended fields, do not set the Table Name. If you are using the
Trading Networks Console to create extended fields, contact webMethods Customer Care.
TRNSERV.000012.000034 Partner status can only be 'Active' or 'Inactive' when adding a new profile.
Response: Supply a valid value for the Partner Status field.

TRNSERV.000012.000035 Corporation is invalid: no partnerID.

Cause: Trading Networks attempted to update a partner profile, but the corporation component has no partner
ID.
Response: Set the partnerID field to a valid value.
TRNSERV.000012.000036 Attempted to save a binary object that has an unknown type (type code=<code>).
Cause: The database does not have binary types defined.
Response: Populate your database with initial values by importing the file
<IntegrationServer>/packages/WmTN/bin/init.xml, where <IntegrationServer> is the location where your
server is installed.
TRNSERV.000012.000037 Could not add Field Group <group>.

Cause: An exception was thrown while adding a profile field group.
TRNSERV.000012.000039 Could not get <protocol> for partner (partnerID=<id>).

Cause: An exception was thrown while retrieving protocol information for a partner.
TRNSERV.000012.000041 Cannot delete required External ID

Cause: Each partner must have a value for the required external ID type. The required external ID value is used
for the user name of the partner's Integration Server user account.
Response: Do not attempt to delete the required external ID from a partner's profile.
TRNSERV.000012.000042 The value for profile field <fieldName> is not one of the valid values.
TRNSERV.000012.000044 Standard fields must have a column name.

Cause: The column name on a standard profile field is null.
TRNSERV.000012.000045 Could not update <object>.

Cause: An exception was thrown while updating a profile component.

TRNSERV.000012.000046 A profile already exists in the database with the supplied PartnerID (<id>).
Cause: Trading Networks attempted to save a new profile with the same partnerID as an existing profile.
Response: Do not specify a value for the partnerID when creating a new profile. Trading Networks will
generate a unique ID for you.
TRNSERV.000012.000048 Could not get profile for partner (id=<partnerID>)

Cause: An exception was thrown while retrieving a partner profile.
TRNSERV.000012.000049 webMethods Trading Partners is restricted to the creation of one profile in addition to your own.
Cause: When using webMethods Trading Partners, you can create only one profile other than your own.
TRNSERV.000012.000050 Could not upgrade your profile. Please contact webMethods Customer Service.
Cause: An exception was thrown while upgrading your profile from webMethods for Partners to webMethods
Trading Networks.
Response: Take appropriate action to resolve the problem described in the exception. If necessary, contact
TRNSERV.000012.000051 At least 1 field has been defined for this group. Cannot delete.
Response: To delete this field group, you must first delete all extended profile fields in the group, or assign
them to other groups.
TRNSERV.000012.000053 Could not delete <profileComponent> (<componentID>=<idValue>).

Cause: An exception was thrown while deleting a profile component.
TRNSERV.000012.000054 Cannot set valid values for a standard field

Cause: You cannot define a list of valid values for standard fields.
Response: Do not attempt to define a list of valid values for a standard field.
TRNSERV.000012.000056 Errors encountered validating profile/profile fields

Cause: A list of one or more errors follows this message.
Response: Take appropriate action to resolve the errors.

TRNSERV.000012.000058 Another partner profile with the name \"<CorpName_UnitName>\" already exists. Cannot have
duplicate partner names. Please enter a different name.
Cause: You are attempting to create a profile; however, a profile with the Corporation Name and User Name
that you specified already exists in Trading Networks.
Response: Supply a different Corporation Name and/or Unit Name.
TRNSERV.000012.000060 You must add a profile for your enterprise before you can upgrade to webMethods Trading
Networks. Please create a profile for your enterprise.
Cause: You have not defined the Enterprise profile. The Enterprise profile must exist before you can upgrade
webMethods Trading Networks.
Response: Create the Enterprise profile.
TRNSERV.000012.000062 Cannot undelete a standard field

Cause: Standard fields cannot be deleted or undeleted.
Response: Do not attempt to delete or undelete a standard field.
TRNSERV.000012.000064 <errorMessage>, no change made on server

Cause: Trading Networks encountered an error while saving partner profile information. See the error message
for details.
Response: Take appropriate action to resolve the problem described in the error message.
TRNSERV.000012.000065 An error was encountered deleting a partner's profile (partnerID=<partnerID>).

Cause: An exception was thrown while deleting a partner profile.
Response: The exception was written to the log. Take appropriate action to resolve the problem described in
the exception.
TRNSERV.000012.000066 Could not get host profile.

Cause: An exception was thrown while retrieving the Enterprise profile.
the exception.
TRNSERV.000012.000068 <variable> is required.

Cause: No value was supplied for a required input variable.

TRNSERV.000012.000069 Standard fields must have a table name.
Cause: Trading Networks encountered an invalid field definition in the Trading Networks database.
TRNSERV.000012.000072 Error initializing ProfileStore

TRNSERV.000012.000073 Could not set binary object for partner (id=<partnerID>).

Cause: An exception was thrown while saving binary data to the Trading Networks database.
the exception.
TRNSERV.000012.000074 Company Logo is missing from the PartnerBinary table in the Trading Networks database. Unable
to retrieve Profile Summaries.
Cause: Required data is missing from the Trading Networks database.
Response: Import the file <IntegrationServer>/packages/WmTN/bin/init.xml, where <IntegrationServer> is the
location where your server is installed.
TRNSERV.000012.000075 Could not get Extended Field template (group=<groupID>).

Cause: An exception was thrown while creating a new extended field.
TRNSERV.000012.000076 Invalid group specified.

Cause: The group that was specified is not a valid group.
Response: Use the wm.tn.dictionary:getFieldGroups service to retrieve a list of valid groups.
TRNSERV.000012.000077 <profileComponent> must be specified for partner <partnerName>

Cause: Required data is missing from a partner profile.
Response: Supply a value for the required fields.
TRNSERV.000012.000078 Datatype cannot be null

Response: Supply a valid data type.

TRNSERV.000012.000079 Your webMethods Trading Networks server is restricted to the creation of <number> profiles in
addition to your own.
Cause: Your webMethods Trading Networks server is restricted to the creation of the number of profiles
specified in the message.
Response: If you need to add more profiles, contact webMethods to upgrade your server.
TRNSERV.000012.000080 Attempted to set the datatype of a field to an unrecognized value: <userValue>

Response: Supply a valid data type.
TRNSERV.000012.000082 Binary type not found in the Trading Networks database: <userValue>.
Cause: Trading Networks attempted to set the value of a binary object, but the type does not exist in the
database.
Response: Supply a valid binaryTypeDescription or binaryTypeCode. If you have specified a valid binary type
and the problem persists, import the init.xml file from the <IntegrationServer>packages/WmTN/bin directory,
where <IntegrationServer> is the location where you installed your server.
TRNSERV.000012.000083 Could not change <ID/Contact> Type <exception>.

Cause: An exception was thrown while attempting to update an external ID type or contact type.
the exception.
TRNSERV.000012.000084 Standard fields cannot have a set of extended valid values

TRNSERV.000012.000085 The specified delivery data (id=<destinationId>) does not exist in the database. Cannot delete.
Cause: Trading Networks was unable to perform the specified database action because the Destination data
does not exist.
TRNSERV.000012.000086 Standard fields cannot have an extended default value


TRNSERV.000012.000087 The value for <fieldName> must be a String.
Response: Supply a String value for the field.
TRNSERV.000012.000088 A <idType> ID of <idValue> already exists in the database. External IDs must be unique.
Cause: Cannot have two external IDs of the same external ID type that have the same value.
Response: Supply another value for this external ID.
TRNSERV.000012.000089 Could not get internal ID for partner (id=<idValue>, typeCode=<idTypeCode>,

typeDesc=<idTypeDescription>).
Cause: An exception was thrown while retrieving the internal partnerID.
the exception.
TRNSERV.000012.000090 Fields must have a datatype

TRNSERV.000012.000091 Could not get profile summaries.

Cause: An exception was thrown while retrieving profile summaries.
the exception.
TRNSERV.000012.000092 <field> cannot be null. <profileComponent> not <added/updated>.

Cause: Trading Networks did not add or update the changes because a required value is missing.
TRNSERV.000012.000093 <field> must be equal or greater than <number>

TRNSERV.000012.000094 You are already using webMethods Trading Networks. No upgrade is necessary.
Cause: Attempted to upgrade from webMethods for Partners to webMethods Trading Networks, but you are
already using webMethods Trading Networks.

TRNSERV.000012.000096 Could not get <profileComponent>.

Cause: An exception was thrown while retrieving a profile component.
Response: An exception was written to the log. Take appropriate action to resolve the problem described in the
exception.
TRNSERV.000012.000099 Status was not changed to <status> because the profile has the following errors <errorList>
Response: Take appropriate action to resolve the problem described in the errors.
TRNSERV.000012.000100 Cannot set Column Name for an extended field

Cause: It is not valid for an extended profile field to have a value for Column Name.
Response: Do not attempt to set a value for Column Name for an extended profile field.
TRNSERV.000012.000101 At least one <field> is required.

TRNSERV.000012.000102 Cannot set Table Name for an extended field

Cause: It is not valid for an extended profile field to have a value for Table Name.
Response: Do not attempt to set a value for Table Name for an extended profile field.
TRNSERV.000012.000105 Could not add <Contact/ID> Type <value>.

Cause: An exception was thrown while attempting to create an IDType or ContactType.
the exception.
TRNSERV.000012.000106 Could not get profile summary (partnerID=<partnerID>).

Cause: An exception was thrown while attempting to retrieve a profile summary.
the exception.
TRNSERV.000012.000107 An error occurred while retrieving polling frequencies.

Cause: An exception was thrown while retrieving a partner's polling frequency.
the exception.

TRNSERV.000012.000108 Could not delete External Partner ID (internal PartnerID=<partnerID>).
Cause: An exception was thrown while deleting a partner's external ID.
the exception.
TRNSERV.000012.000109 Got null profile field metadata for extended field at index <number>
Cause: Required internal data is missing.
TRNSERV.000012.000110 Could not undelete profile for partner (id=<partnerID>).

Cause: An exception was thrown while undeleting a partner profile.
the exception.
TRNSERV.000012.000111 Corporate information must be specified for this partner.

Cause: Required Corporate information is missing from the partner's profile.
Response: Update the partner's profile to supply the required Corporate information.
TRNSERV.000012.000113 Attempted to save a field definition for an unknown group (group id=<id>).
Cause: The specified field group does not exist and is not valid.
Response: Supply a valid field group. If you are using the Trading Networks Console to create an extended
field, contact webMethods Customer Care.
TRNSERV.000012.000114 Could not get profile summary (username=<user>).

Cause: An exception was thrown while retrieving a profile summary.
the exception.
TRNSERV.000012.000115 Profile has errors. Saved with a status of <status>.

Response: Take appropriate action to resolve the errors listed below this message.
TRNSERV.000012.000116 Could not add external ID data for partner (id=<partnerID>).

Cause: Encountered an Exception while saving a profile component.
the exception.

TRNSERV.000012.000117 webMethods Trading Networks requires a special license key. Please contact webMethods to get a
Trading Networks key. Until you do so, you will be limited to the creation of one profile in addition to your own.
Cause: You currently have a webMethods for Partners license key, which allows you to create only a single
partner profile.
TRNSERV.000012.000118 Profile status may only be changed to <status1> or <status2>.

Cause: Attempted to change the profile status to an invalid status.
TRNSERV.000012.000120 Could not change partner's status.

Cause: An exception was thrown while updating the status of a partner profile.
the exception.
TRNSERV.000012.000121 <Primary/Secondary> <protocol> delivery data already exists in the database for this partner.
Cause: You attempted to add a delivery method for a partner that is already defined for the partner. You
cannot have two instances of the same delivery method for a partner.
Response: If the existing delivery method contains the information you want, no action is required. Otherwise,
you can update the information for the existing delivery method.
TRNSERV.000012.000122 Extended fields must have a name.

Cause: You did not specify a name for the extended profile field.
TRNSERV.000012.000123 Problem initializing Profile services.

the exception.
TRNSERV.000012.000124 Cannot set default value for a standard field.

Cause: You cannot define a default value for a standard profile field.
Response: Do not attempt to define a default value for a standard profile field.

TRNSERV.000012.000125 Could not retrieve extended fields.
Cause: An exception was thrown while retrieving extended fields for a partner.
the exception.
TRNSERV.000012.000126 Standard fields cannot be marked as deleted

Cause: You cannot delete a standard profile field.
Response: Do not attempt to delete a standard profile field.
TRNSERV.000012.000129 Following errors occurred during updating profile

Cause: A list of one or more errors follows this message.
Response: Take appropriate action to resolve the problems described in the errors.
TRNSERV.000012.000130 Cannot delete preferred delivery method

Cause: The delivery method you tried to delete is the preferred delivery method for the partner.
Response: Before you can delete this delivery method, choose another delivery method to be "preferred".
TRNSERV.000012.000131 Could not delete <Contact/ID> Type <value>.

Cause: An exception was thrown while deleting profile data.
the exception.
TRNSERV.000012.000132 Could not update corporation.

Cause: An exception was thrown while updating the Corporate component of a partner profile.
the exception.
TRNSERV.000012.000133 Could not update addresses.

Cause: An exception was thrown while updating one or more addresses on a partner profile.
the exception.

TRNSERV.000012.000136 Could not delete connection (destinationID=<idValue>).

Cause: An exception was thrown while deleting a delivery method from a partner profile.
the exception.
TRNSERV.000012.000138 Could not update external IDs.

Cause: An exception was thrown while updating one or more external IDs in a partner profile.
the exception.
TRNSERV.000012.000141 Could not get binary object for partner (partnerID=<partnerID>).

Cause: An exception was thrown while retrieving a binary object for a partner profile.
the exception.
TRNSERV.000012.000142 "extID" is required. Please supply the required value.

Cause: You attempted to invoke a service that requires a value for the "extID" input variable, but no value was
supplied.
TRNSERV.000012.000143 Either idTypeCode or idTypeDesc must be supplied (idTypeCode=<userValue>,

idTypeDesc=<userValue>)
Cause: You invoked a service without providing a required input variable to identify the external ID type.
Response: Supply one of the required values.
TRNSERV.000012.000144 partnerID is required.

Cause: You invoked a service without providing a required input variable to identify the partner.
TRNSERV.000012.000145 Could not get external ID for partner (partnerID=<partnerID>)

Cause: An exception was thrown while retrieving an external ID for a partner profile.
the exception.

TRNSERV.000012.000146 Error encountered updating binary object in the database (partnerID=<partnerID>).
Cause: An exception was thrown while updating a binary object for a partner profile.
the exception.
TRNSERV.000012.000147 <fieldName> must be supplied.

Cause: You called a Java method without supplying a value for a required field (<fieldName>).
TRNSERV.000012.000148 A status of <status> is not one of the permitted values.

Cause: Attempted to set the status to an invalid value.
TRNSERV.000012.000149 Error encountered changing partner status.

Cause: An exception was thrown while updating the status of a partner profile.
the exception.
TRNSERV.000012.000151 A profile is required.

Response: Supply the required data.
TRNSERV.000012.000152 Error encountered adding profile to the database.

Cause: An exception was thrown while adding a partner profile.
the exception.
TRNSERV.000012.000153 Error encountered adding contacts to the database.

Cause: An exception was thrown while adding one or more contacts to a partner profile.
the exception.

TRNSERV.000012.000155 Error encountered adding destinations to the database.

Cause: An exception was thrown while adding one or more delivery methods (destinations) to a partner
profile.
the exception.
TRNSERV.000012.000156 Error encountered adding IDs to the database.

Cause: An exception was thrown while adding one or more external IDs to a partner profile.
the exception.
TRNSERV.000012.000157 Error encountered adding addresses to the database.

Cause: An exception was thrown while adding one or more addresses to a partner profile.
the exception.
TRNSERV.000012.000158 Error encountered adding binary objects to the database.

Cause: An exception was thrown while adding one or more binary objects to a partner profile.
the exception.
TRNSERV.000012.000160 <field> cannot be null.

Cause: The field must have a value.
Response: Supply the missing data.
TRNSERV.000012.000161 Error encountered deleting profile from the database.

Cause: An exception was thrown while deleting a partner profile.
the exception.
TRNSERV.000012.000162 Error encountered undeleting profile from the database.

Cause: An exception was thrown while undeleting a partner profile.
the exception.

TRNSERV.000012.000163 Error encountered deleting contact (contactID=<id>, partnerID=<id>).
Cause: An exception was thrown while deleting a contact from a partner profile.
the exception.
TRNSERV.000012.000164 Error encountered deleting address (addressID=<id>, partnerID=<id>).

Cause: An exception was thrown while deleting an address from a partner profile.
the exception.
TRNSERV.000012.000165 Error encountered deleting destination (destID=<id>).

Cause: An exception was thrown while deleting a delivery method (destination) from a partner profile.
the exception.
TRNSERV.000012.000166 Error encountered deleting external id (id=<id>).

Cause: An exception was thrown while deleting an external ID from a partner profile.
the exception.
TRNSERV.000012.000167 Error encountered retrieving extended fields.

Cause: An exception was thrown while retrieving extended fields for a partner.
the exception.
TRNSERV.000012.000168 Error encountered adding extended field <fieldName> to the database (partnerID=<id>).
Cause: An exception was thrown while adding an extended profile field for a partner.
the exception.
TRNSERV.000012.000169 Error encountered updating extended fields.

Cause: An exception was thrown while updating extended profile fields for a partner.
the exception.

TRNSERV.000012.000170 Error encountered retrieving contact <type> (partnerID=<id>).

Cause: Encountered an Exception while retrieving a contact for a partner.
the exception.
TRNSERV.000012.000171 Error encountered retrieving binary type <type> (partnerID=<id>).

Cause: An exception was thrown while retrieving a binary object for a partner.
the exception.
TRNSERV.000012.000172 Invalid binary type: <type>.

Response: Supply a valid binary type value.
TRNSERV.000012.000173 A connection was requested for an unknown partner (partnerID=<id>).

Cause: Attempted to establish a connection to a partner's server, but the supplied partnerID was invalid.
Response: Supply a valid partner ID.
TRNSERV.000012.000174 Delivery method is <protocol>. Can only create contexts for HTTP or HTTPS destinations.
Cause: A webMethods context can only be established when using HTTP or HTTPS.
Response: If you want to connect to a partner's server with a different protocol (e.g., FTP or SMTP) use the
appropriate service in the WmPublic package or one of the delivery services in the wm.tn.transport folder.
TRNSERV.000012.000175 Error encountered connecting to partner's server.

Cause: An exception was thrown while connecting to a partner's server.
the exception.
TRNSERV.000012.000181 constant must start with FLD_[TBL]_

Cause: Internal error.
TRNSERV.000012.000182 bad constant results in non or multiple fields


TRNSERV.000012.000184 RetryFactor cannot be zero
TRNSERV.000012.000187 External Field: <fieldName> has errors. Error = <errorList>

Cause: See the errors listed in the message.
Response: Take appropriate action to resolve the problems described in the errors.
TRNSERV.000012.000188 Is a required External Field

Cause: No data was supplied for a required extended profile field.
Response: Supply a value for this field.
TRNSERV.000012.000189 Field value must be of data type java.lang.String

Response: Supply a String value.
TRNSERV.000012.000190 Invalid value selected

TRNSERV.000012.000192 Could not retrieve ID Types from database

Cause: An exception was thrown while retrieving external ID types.
the exception.
TRNSERV.000012.000193 Could not retrieve IDType Descriptions from database

Cause: An exception was thrown while retrieving external ID type descriptions.
the exception.
TRNSERV.000012.000194 A database error occurred while adding an ID Type.

Cause: An exception was thrown while adding an external ID type.
the exception.

TRNSERV.000012.000195 A database error occurred while changing an ID Type.

Cause: An exception was thrown while updating an external ID type.
the exception.
TRNSERV.000012.000196 A database error occurred while deleting an External ID Type.

Cause: An exception was thrown while deleting an external ID type.
the exception.
TRNSERV.000012.000197 Could not retrieve Contact Types from database

Cause: An exception was thrown while retrieving contact types.
the exception.
TRNSERV.000012.000198 A database error occurred while adding a Contact Type.

Cause: An exception was thrown while adding a contact type.
the exception.
TRNSERV.000012.000199 A database error occurred while changing a Contact Type.

Cause: An exception was thrown while updating a contact type.
the exception.
TRNSERV.000012.000200 A database error occurred while deleting a Contact Type.

Cause: An exception was thrown while deleting a contact type.
the exception.
TRNSERV.000012.000201 Could not retrieve Binary Types from database

Cause: An exception was thrown while retrieving binary types.
the exception.

TRNSERV.000012.000202 Could not retrieve Field Groups from database
Cause: An exception was thrown while retrieving field groups.
the exception.
TRNSERV.000012.000203 A database error occurred while adding a Field Group.

Cause: An exception was thrown while adding a field group.
the exception.
TRNSERV.000012.000204 A database error occurred while changing a Field Group.

Cause: An exception was thrown while updating a field group.
the exception.
TRNSERV.000012.000205 A database error occurred while deleting a Field Group.

Cause: An exception was thrown while deleting a field group.
the exception.
TRNSERV.000012.000206 Error initializing Profile Dictionary.

TRNSERV.000012.000207 pfmd cannot be null.

Cause: You did not supply a required value.
TRNSERV.000012.000208 A problem was encountered updating the field definition.

Cause: An exception was thrown while updating a field definition.
the exception.

TRNSERV.000012.000209 Cannot add a standard field definition. Set Extended to true before saving this definition.
Cause: Attempted to add a standard profile field. You cannot add standard profile fields.
Response: Add the profile field as an extended profile field.
TRNSERV.000012.000210 A problem was encountered adding the field definition.

Cause: An exception was thrown while adding a field definition.
the exception.
TRNSERV.000012.000211 Error retrieving profile

Cause: Encountered an Exception while retrieving a partner profile.
the exception.
TRNSERV.000012.000212 Could not retrieve profile from database using external ID

Cause: An exception was thrown while retrieving a partner profile.
the exception.
TRNSERV.000012.000213 Could not retrieve Profile Summaries from database

the exception.
TRNSERV.000012.000214 Could not retrieve profile summary from database (partnerID=<id>)

the exception.
TRNSERV.000012.000215 Could not retrieve profile summary from database (user=<userID>)

the exception.

TRNSERV.000012.000216 Could not retrieve Custom Fields from database
Cause: An exception was thrown while retrieving extended profile fields.
the exception.
TRNSERV.000012.000218 Could not retrieve internal ID from database using PartnerIDID (<id>).
Cause: An exception was thrown while retrieving a partner profile ID.
the exception.
TRNSERV.000012.000219 Could not retrieve internal ID from database using DestinationID (<id>).
Cause: An exception was thrown while retrieving a partner profile ID.
the exception.
TRNSERV.000012.000220 Error retrieving <idType> external ID for <partnerID>.

Cause: An exception was thrown while retrieving the external ID for a partner.
the exception.
TRNSERV.000012.000221 Could not retrieve IDType from database using PartnerIDID (<id>).
Cause: An exception was thrown while retrieving an external ID type.
the exception.
TRNSERV.000012.000222 Could not update profile.

Cause: An exception was thrown while updating a profile that has been marked deleted.
the exception.
TRNSERV.000012.000223 Corporation can not be null.

Cause: Required Corporate information was not supplied.
Response: Supply the required Corporate information.

TRNSERV.000012.000224 Could not update Corporation.

Cause: An exception was thrown while updating a partner profile.
the exception.
TRNSERV.000012.000225 Contacts can not be null.

Cause: Required Contact information was not supplied.
TRNSERV.000012.000226 At least one Contact is required.

Cause:
The supplied Vector must contain at least one contact.
TRNSERV.000012.000227 Could not update Contacts.

Cause: An exception was thrown while updating a partner's contact information.
the exception.
TRNSERV.000012.000228 Address can not be null.

Cause: Required address information was not supplied.
TRNSERV.000012.000229 At least one Address is required.

Cause: The supplied Vector must contain at least one address.
TRNSERV.000012.000230 Could not update Addresses.

Cause: An exception was thrown while updating a partner's address information.
the exception.

TRNSERV.000012.000231 Destinations can not be null.
Cause: Required delivery method (Destination) information was not supplied.
TRNSERV.000012.000232 At least one Destination is required.

Cause: The supplied Vector must contain at least one delivery method (destination).
TRNSERV.000012.000233 Could not update Destinations.

Cause: An exception was thrown while updating a partner's delivery method (destination) information.
the exception.
TRNSERV.000012.000234 IDs can not be null."

TRNSERV.000012.000235 At least one ID is required.

Cause: The supplied Vector must contain at least one external ID.
TRNSERV.000012.000236 Could not update IDs.

Cause: An exception was thrown while updating a partner's external ID information.
the exception.
TRNSERV.000012.000237 A vector of Contacts is required

Cause: The first argument to ProfileStore.addContacts is null.
TRNSERV.000012.000238 A vector of Destinations is required

Cause: The first argument to ProfileStore.addDestinations is null.

TRNSERV.000012.000239 A vector of IDs is required

Cause: The first argument to ProfileStore.addIDs is null.
TRNSERV.000012.000240 A vector of Addresses is required

Cause: The first argument to ProfileStore.addAddresses is null.
TRNSERV.000012.000242 "addresses" is empty. At least one Address must be supplied.

Cause: No address was supplied.
TRNSERV.000012.000243 "connections" is empty. At least one Destination must be supplied.

Cause: No delivery method (destination) was supplied.
TRNSERV.000012.000244 Could not validate profile extended fields: received null bizdoc
Cause: Internal error occurred during profile validation.
TRNSERV.000012.000245 No extended fields found in bizdoc

Response: This error can be safely ignored. If it persists, contact webMethods Customer Care.
TRNSERV.000012.000246 Could not validate profile standard fields: received null bizdoc
TRNSERV.000012.000247 No standard fields found in bizdoc


TRNSERV.000012.000252 Attempted to import extended field "<fieldName>" for partner ID <id>, but this partner does not
exist on your Trading Networks system.
Response: You must import the partner's profile before you can import extended fields for the partner.
TRNSERV.000012.000253 Attempted to import extended field "<fieldName>" that has an extended profile field ID of <id>, but
this extended field is not defined on your Trading Networks system.
Cause: Cannot import the value of the extended profile field because there is no definition for the extended
field.
Response: You must import the extended field definitions before you can import extended field values.
TRNSERV.000012.000254 Error encountered invoking wm.tn.profile:addProfile <exceptionMessage>.

Cause: An exception was thrown while saving a new partner profile.
TRNSERV.000012.000255 The <idType> ID is used as the Integration Server account name. The partner may not have more
than one <idType> ID.
Cause: The partner already has an external ID for the required external ID type. Because the required external
ID is used as the user name of an Integration Server user account, you can only define one required external
ID.
Response: You cannot add another external ID that uses the required external ID type. You can add multiple
external IDs of other external ID types, but only one for the required external ID type.
TRNSERV.000012.000256 The <id> ID is used as the Integration Server account name. It may not contain whitespace.
Cause: Because the value of the required external ID type is used as the user name for an Integration Server
user account, it cannot contain white space.
Response: Remove all white space from the external ID.
TRNSERV.000012.000257 Error encountered refreshing ID cache.

Cause: An exception was thrown while refreshing an internal cache.
the exception.
TRNSERV.000012.000258 Could not get external IDs for partner (partnerID=<id>)

Cause: An exception was thrown while retrieving external IDs.
the exception.

TRNSERV.000012.000259 The <id> ID is used as the Integration Server account name. It must be specified for partner
<name>.
Cause: Because the value of the required external ID type is used as the user name for an Integration Server
user account, it must be specified.
Response: Specify the required external ID.
TRNSERV.000012.000260 Could not retrieve Profile Groups from database.

Cause: Encountered a SQLException while retrieving profile group information from the database.
the exception.
TRNSERV.000012.000262 profileGroupName can not be null or empty.

Cause: Trading Networks cannot accept null or an empty string for the profile group name.
Response: Please specify a non-null a profile group name.
TRNSERV.000012.000263 profileGroupName <name> already exists in database.

Cause: Trading Networks cannot accept a duplicate profile group name.
Response: Please specify a unique profile group name.
TRNSERV.000012.000264 A database error occurred while adding Profile Group <name>

Cause: Encountered a SQLException while adding the new profile group.
the exception.
TRNSERV.000012.000265 A database error occurred while changing Profile Group <id>

Cause: Encountered a SQLException while changing the profile group name from its old name to a new name.
the exception.
TRNSERV.000012.000266 A database error occurred while deleting Profile Group <id>.

Cause: Encountered a SQLException while deleting the profile group from the database.
the exception.

TRNSERV.000012.000267 A databse error occurred while querying profile information.
Cause: Encountered a SQLException while executing a profile query.
the exception.
TRNSERV.000012.000275 Error encountered invoking service <name>

Cause: Encountered an Exception while invoking the specified service.
TRNSERV.000012.000276 <profileGroupIds> can not be null or a 0-length array.

Cause: The input signature profileGroupIds should be a non-null array.
Response: Specify non-null values for the profileGroupIds input.
TRNSERV.000012.000281 Attempted to import security data for partner ID <id>, but this partner does not exist on your
Cause: You attempted to import a trading partner's security data without first importing this trading partner's
profile.
Response: Import the trading partner's profile before you attempt to import the security data for this trading
partner.
TRNSERV.000012.000282 No <Primary/Secondary> <delivery protocol> delivery data exists in the database for this partner.
Cannot update.
Cause: The profile update operation cannot be completed because the delivery protocol data is not available.
Response: Please provide the delivery protocol details.
TRNSERV.000012.000283 Could not add contact data for partner (id=<id>).

Cause: Encountered an Exception while invoking wm.tn.profile:addContacts. The operation cannot be
completed.
the exception.
TRNSERV.000012.000284 Could not add address data for partner (id=<id>)

Cause: Encountered an Exception while invoking wm.tn.profile:addAddresses. The operation cannot be
completed.
the exception.

TRNSERV.000012.000285 Could not add delivery data for partner (id=<id>)

Cause: Encountered an Exception while invoking wm.tn.profile:addConnections. The operation cannot be
completed.
the exception.
TRNSERV.000012.000287 Could not delete profile group <id>, it is still in use.

Cause: The delete operation cannot be completed because the profile group is in use.
Response: Check the trading partner profiles to make sure that no partner belongs to the group you are
attempting to delete.
TRNSERV.000012.000289 Database error in adding partner <partnerID> to profile groups. Import operation aborted.
Cause: Trading Networks encountered a problem with its database. There is a problem in the database or
database driver.
Response: Use the JDBC Pools page on the Integration Server Administrator to ensure that the Integration
Server can connect to the Trading Networks database. Correct all connection problems. If no connection
problem exists, take appropriate action to resolve the problem described in the exception.
TRNSERV.000012.000290 Cannot import partner profile(s) without my enterprise profile.

Cause: You are attempting to import one or more partner profiles; however, the target Trading Networks
server does not have an Enterprise profile.
Response: Create an Enterprise profile on the target server; then import the partner profiles.
TRNSERV.000012.000291 SQLException encountered in ProfileStore.addPartnerCertificate().

database driver.
TRNSERV.000012.000292 EXMLException encountered in ProfileStore.addPartnerCertificate().

Cause: Trading Networks encountered a problem when attempting to save a certificate for a partner.

TRNSERV.000012.000293 SQLException encountered in ProfileStore.getPartnerIDForCertificate().
database driver.
TRNSERV.000012.000294 EXMLException encountered in ProfileStore.getPartnerIDForCertificate().

Cause: Trading Networks encountered a problem when attempting to retrieve a certificate for a partner.
TRNSERV.000012.000295 Cannot deliver to My Enterprise. The supplied partnerID (<partnerID>) is the partnerID of the My
Enterprise profile. Please supply a different partnerID.
Cause: The document receiver is the Enterprise profile, which indicates Trading Networks is to deliver the
document to itself. This is not valid; Trading Networks cannot deliver a document to itself.
Response: Either change the receiver to specify a trading partner, or do not attempt to deliver this document.
TRNSERV.000012.000296 A deleted partner profile with the name "<corporationName>" already exists. Cannot have
duplicate partner names. Please enter a different name.
Cause: You attempted to create a profile; however the Corporation Name and Unit Name you specify will
make the profile a duplicate of a profile that was previously deleted. Although a profile is deleted, Trading
Networks continues to maintain information about it in its database. As a result, you cannot create another
profile using the same Corporation Name and Unit Name.
Response: If you want to reinstate the deleted profile, use the wm.tn.profile:undeleteProfile service. Otherwise,
enter a different Corporation Name and Unit Name when creating a profile.
TRNSERV.000012.000297 Importing a profile for <corporationName> (id=<partnerID>), which is marked as "My Enterprise".
A "My Enterprise" profile already exists for this Trading Network. If you want to update it, use the Force option. Process
terminated.
Cause: You attempted to import an Enterprise profile into a Trading Networks system that already has an
Enterprise profile.
Response: If you want to replace the existing Enterprise profile with the profile you are trying to import, use
the Force option.

TRNSERV.000012.000298 A deleted profile with the name "<corporationName>" already exists. Unable to recreate a deleted
profile.
Cause: A deleted partner profile with this Corporation Name already exists. Trading Networks maintains
information about deleted profiles in its database and does not allow duplicate partner names.
Response: You can either use a different Corporation Name, or use the wm.tn.profile:undeleteProfile service to
reinstate the deleted partner profile.
TRNSERV.000013.000001 This document type (<docTypeName>) is missing one or both of its signature queries (Signature
and SignedBody). Signing cannot proceed.
Cause: Trading Networks cannot create a digital signature because the TN document type did not instruct
Trading Networks to extract the signature or signed body system attributes.
Response: Add queries to extract the Signature and SignedBody system attributes to the TN document type. To
update the TN document type, use the Document Type screen of the Trading Networks Console.
TRNSERV.000013.000002 The signing service for this document (<docID>) generated an error. The original error was
<exceptionMessage>.
TRNSERV.000013.000003 Signing Failed

Cause: See message TRNSERV.000013.000002 for full details.
Response: Take appropriate action to resolve the problem described in the exception displayed with message
TRNSERV.000013.000002.
TRNSERV.000013.000005 Base-64 encoding the signed body for this document failed to produce a value. The signed body
(before encoding) was <content>.
Cause:
The query used to extract the signed body from the document might be invalid. You specify the query that
Trading Networks uses in the TN document type used for the document.
Response:
If the query used for the signed body returned an empty string, adjust the signed body query for this TN
document type. To do so, use the Document Type screen of the Trading Networks Console to update the TN
document type.
TRNSERV.000013.000006 Encoding Error


TRNSERV.000013.000007 An error prevented fetching certificate info for the sender of this document. The error was
<exceptionMessage>.
Cause: An exception was thrown while retrieving certificates needed to sign a document.
TRNSERV.000013.000008 Error fetching cert info

TRNSERV.000013.000010 No private key information was available for the sender of this document. <errorMessage>
Cause: Trading Networks encountered an error while fetching a private key. See the error message for details.
Response: You might need to import security data for this partner.
TRNSERV.000013.000011 No Private Key

TRNSERV.000013.000012 Applying the <xqlQuery> query to this document failed. The error: <exceptionMessage>
Cause: Trading Networks encountered an error while executing the query to extract the signature from a
document. See the exception for details.
TRNSERV.000013.000013 Query Error

TRNSERV.000013.000014 The signature query for doctype <doctypeName> identified the <xqlQuery> node as the target of
the signature, but this node is missing in this document. Signing cannot proceed.
Cause: The query used to extract the signature from the document identified a node that is not in the
document. You specify the query that Trading Networks uses in the TN document type used for the
document.
Response: Adjust the signature and/or signed body query for this TN document type. To do so, use the
Document Type screen of the Trading Networks Console to update the TN document type.
TRNSERV.000013.000015 Missing Document Node


TRNSERV.000013.000017 No cert chains are available for the sender of this document. <errorMessage>
Cause: Trading Networks encountered an error while fetching a certificate chain. See the error message for
details.
Response: Take appropriate action to resolve the problem described in the error.
TRNSERV.000013.000018 No Cert Chain

TRNSERV.000013.000019 Cannot sign documents from UNKNOWN sender

Cause: The sender of the document is unknown to Trading Networks. Reasons that Trading Networks might
be unable to determine the sender are: 1) The query that Trading Networks uses to extract the Sender value
from the document might be incorrect. The query is defined in the TN document type. 2) The value extracted
from the document for the Sender query does not match the external ID of any partner in the Trading
Networks database. 3) The structure of the document is incorrect.
Response: Do one of the following: 1) If the query used to extract the Sender value is not valid, adjust the query
in the TN document type. To do so, use the Document Type screen of the Trading Networks Console. 2) If the
value extracted for the Sender query does not match an external ID in the Trading Networks database, add the
external ID to the appropriate partner's profile. To do so, use the Profile screens of the Trading Networks
Console. 3) If the document structure is incorrect, notify the partner that sent the document.
TRNSERV.000013.000020 Sender Unknown

TRNSERV.000013.000021 This doctype (<doctypeName>) has no signing service defined. Signing cannot continue.
Cause: This TN document type has no signing service defined, as a result Trading Networks cannot continue
with signing.
Response: If this is an XML TN document type, contact webMethods Customer Care. If this is not an XML TN
document type and the TN document type supports signing services, define a signing service for the TN
document type.
TRNSERV.000013.000022 No Signing Service


TRNSERV.000013.000024 The signature query for doctype <doctypeName> (<xqlQuery>) failed to identify a node to insert the
signature into. Signing cannot proceed.
Cause: Either the query that Trading Networks uses to extract the signature is incorrect in the TN document
type or the structure of the document is incorrect.
Response: If the query is not correct, adjust the signature query for this TN document type. To do so, use the
Document Type screen of the Trading Networks Console to update the TN document type. If the document
structure is incorrect, notify the document sender.
TRNSERV.000013.000025 The signature query for doctype <doctypeName> identified the <xqlQuery> node as the target of
the signature, but this node is not unique in this document. Signing cannot proceed.
Cause: Either the structure of the document is incorrect or the query that Trading Networks uses to extract the
signature is incorrect in the TN document type.
Response: If the document structure is incorrect, notify the document sender. If the query is not correct, adjust
the signature query for this TN document type. To do so, use the Document Type screen of the Trading
Networks Console to update the TN document type. Note that if your XQL query is returning an array of
nodes, you can force it to return a single node by adding a subscript. For example, change "/anXMLtag" to
"/anXMLtag[0]".
TRNSERV.000013.000026 Ambiguous Document Node

Response:
TRNSERV.000013.000027 No signing service for doctype <doctypeName>

Cause: This TN document type has no signing service defined, as a result Trading Networks cannot continue
with signing.
Response: If this is an XML TN document type, contact webMethods Customer Care. If this is not an XML TN
document type and the TN document type supports signing services, define a signing service for the TN
document type.
TRNSERV.000013.000030 Trading Networks will not sign documents originating from the Unknown partner. Signing fails.
Cause: The sender of the document is unknown to Trading Networks. Reasons that Trading Networks might
be unable to determine the sender are: 1) The query that Trading Networks uses to extract the Sender value
from the document might be incorrect. The query is defined in the TN document type. 2) The value extracted
from the document for the Sender query does not match the external ID of any partner in the Trading
Networks database. 3) The structure of the document is incorrect.
Response: Do one of the following: 1) If the query used to extract the Sender value is not valid, adjust the query
in the TN document type. To do so, use the Document Type screen of the Trading Networks Console. 2) If the
value extracted for the Sender query does not match an external ID in the Trading Networks database, add the

external ID to the appropriate partner's profile. To do so, use the Profile screens of the Trading Networks
Console. 3) If the document structure is incorrect, notify the partner that sent the document.
TRNSERV.000013.000031 The signed body query for this document type (<doctypeName>) failed to produce a value. Signing
the document fails. The query was <xqlQuery>.
Cause: Either the query that Trading Networks uses to extract the signature is incorrect in the TN document
type or the structure of the document is incorrect.
Response: If the query is not correct, adjust the signature query for this TN document type. To do so, use the
Document Type screen of the Trading Networks Console to update the TN document type. If the document
structure is incorrect, notify the document sender.
TRNSERV.000014.000002 Processing recursion was detected: the processing rule <ruleName> invoked itself, most recently
with document <docID>. Processing fails.
Cause: A processing rule recursed, and no recursion is allowed. Or recursion is allowed, but the maximum
recursion level was exceeded.
Response: If you want a processing rule to recurse (to call itself), set the tn.recursion.max property to an
appropriate value. If you do not want the processing rule to recurse, check the service that the processing rule
invokes. The service is submitting a document that matches the same routing rule.
TRNSERV.000014.000004 If alertPartner is not specified, neither alertContact, alertSubject nor alertMessage may be
specified.
Cause: An invalid combination of input values was sent to wm.tn.route:create.
Response: If you are not supplying a value for alertPartner, do not supply a value for alertContact, alertSubject,
or alertMessage.
TRNSERV.000014.000008 Error sending mail: <exceptionMessage>

Cause: Encountered an exception while sending an e-mail alert.
TRNSERV.000014.000011 An error occurred invoking the processing service (<serviceName>) for this document. The
original error was of type <errorType>; the message was <errorMessage> and the service output this pipeline:
<serviceOutput>
Cause: A processing rule invoked a service, and that service returned an error.
Response: Take appropriate action to resolve the problem described in the error message.
TRNSERV.000014.000012 Error signaled in processing service

Cause: A processing rule invoked a service, and that service returned an error.
Response: See the full message (TRNSERV.000014.000012) for details.

TRNSERV.000014.000013 An internal error prevented processing from finishing normally on this document. The aborted rule
was <ruleName>, and the original error message was <exceptionMessage>.
Cause: See the exception message for details.
TRNSERV.000014.000014 Internal processing error

Cause: See the full message (TRNSERV.000014.000013) for details.
TRNSERV.000014.000017 <exceptionType> loading rules

Cause: Encountered an Exception while reading processing rules from the database.
the Exception.
TRNSERV.000014.000023 <exceptionType> saving rules

Cause: Encountered an exception while saving processing rules to the database. Trading Networks wrote the
exception to the server log.
TRNSERV.000014.000027 An exception occurred invoking a processing service for document <docID>. The processing
service was <serviceName>, and the original error message was: <exceptionMessage>.
Cause: A processing rule invoked a service, and that service threw an exception.
TRNSERV.000014.000028 An error occurred invoking the processing service <serviceName> for this document. The original
TRNSERV.000014.000029 Service invoke err: <serviceName>


TRNSERV.000014.000034 Error sending via <deliveryMethod>

Cause: See the full message for details.
TRNSERV.000014.000035 Fatal processing error: <exceptionMessage>.

Cause: Encountered an exception while processing a document. See the exception for details.
TRNSERV.000014.000038 Changing the user status on document <docID> generated an error. The original error message
Cause: Encountered an exception while changing the status for a document. See the exception for details.
TRNSERV.000014.000039 Error changing status

Cause: Encountered an exception while changing the status for a document. See the exception for details.
TRNSERV.000014.000040 An error occurred sending via protocol <protocol>. The original error message was:
<exceptionMessage>
Cause: Encountered an exception while sending a document. See the exception message for details.
TRNSERV.000014.000041 Error delivering document

Cause: Encountered an exception while sending a document.
TRNSERV.000014.000052 Processing Alert Failed

Cause: Encountered an error while sending an e-mail alert.
Response: See full message for details.
TRNSERV.000014.000053 The server was unable to send email to <address> during processing. The subject of the email was
<subject>. The error message was: <exceptionMessage>.
Cause: Encountered an error while sending an e-mail alert.

TRNSERV.000014.000054 PROCESSING ERROR: partner contact <partnerID>/<contactType> is not defined
Cause: Processing is configured to send alerts to a specific contact type, but the partner profile does not have a
contact of that type.
Response: Either change the processing rule to send alerts to a different contact type (or use a hard-coded
e-mail address), or create a contact of this type for the partner.
TRNSERV.000014.000055 Partner <actualCorporationName> sent this document posing as <otherCorporationName>.

Cause: When Trading Networks receives a document, it determines the partner initiating the request based on
the user account that sent the document. The partner that sent the request does not match the sender from
within the document content.
Response: You might want to notify the partner who sent the document and/or the partner being
impersonated.
TRNSERV.000014.000056 Partner <actualCorporationName> sent document <docID> posing as <otherCorporationName>.

Cause: When Trading Networks receives a document, it determines the partner initiating the request based on
the user account that sent the document. The partner that sent the request does not match the sender from
within the document content.
Response: You might want to notify the partner who sent the document and/or the partner being
impersonated.
TRNSERV.000014.000057 Partner ID mismatch

Cause: The partner who sent the document does not match the partner in the document content.
TRNSERV.000014.000058 The sender of this document (<corporationName>) has been deleted. Documents from this partner
are not permitted at this time.
Cause: Trading Networks received a document from a partner whose profile was deleted. Although Trading
Networks still maintains a copy of the deleted profile in its database, it will not accept documents nor process
documents from the partner.
Response: If you do not want to accept documents from the partner, you can either ignore this error or notify
the partner to stop sending documents. If you want to receive and process documents from this partner, use
the wm.tn.profile:undeleteProfile service to reinstate the partner's profile.

TRNSERV.000014.000059 The sender of document <docID> (<corporationName>) had been deleted. Documents from this
partner are not permitted at this time.
Cause: Trading Networks received a document from a partner whose profile was deleted. Although Trading
Networks still maintains a copy of the deleted profile in its database, it will not accept documents nor process
documents from the partner.
Response: If you do not want to accept documents from the partner, you can either ignore this error or notify
the partner to stop sending documents. If you want to receive and process documents from this partner, use
the wm.tn.profile:undeleteProfile service to reinstate the partner's profile.
TRNSERV.000014.000060 Partner deleted

Cause: Received a document from a partner whose profile was logically deleted.
TRNSERV.000014.000067 An attempt was made to send email to the <contactType> contact of the Unknown partner. No
email was sent.
Cause: The processing rule is configured to send an alert to a partner's contact, but Trading Networks could not
identify the partner.
Response: Examine the document content and the Sender/Receiver queries on the document type to determine
why Trading Networks could not identify the partner.
TRNSERV.000014.000068 Can't send to UNKNOWN

Cause: The processing rule is configured to send an alert to a partner, but Trading Networks could not identify
the partner.
Response: Examine the document content and the Sender/Receiver queries on the document type to determine
why Trading Networks could not identify the partner.
TRNSERV.000014.000070 Processing aborted

Cause: Threw a RoutingAbortedException while processing the document.
TRNSERV.000014.000071 The processing service, <serviceName> aborted processing of this document. The message was
<exceptionMessage>.

TRNSERV.000014.000074 The user that posted this document (<docID>) could not be associated with a partner to check their
identity.
Cause: Received a document from someone other than a trading partner.
Response: You can either ignore this error or contact the document sender. The sender is using a valid
Integration Server account, but not the account associated with their profile.
TRNSERV.000014.000075 The user that posted document <docID> (<userName>) could not be associated with a partner to
check their identity.
TRNSERV.000014.000076 No user ID
TRNSERV.000014.000078 No email address

Cause: Could not determine the address to send an e-mail alert to.
Response: Examine the processing rule and the receiver's profile. You must specify an address either in the
processing rule or the receiver's profile.
TRNSERV.000014.000079 No email address was available for sending to <partnerID> (<contactType>). No email was sent.
Cause: Could not determine the address to send an e-mail alert to.
Response: Examine the processing rule and the receiver's profile. You must specify an address either in the
processing rule or the receiver's profile.
TRNSERV.000014.000086 No SMTP server defined: check property watt.server.smtpServer

Cause: The processing rule is configured to send an e-mail alert, but no e-mail server is defined.
Response: Set the SMTP Server on the Settings > Logging page of the Integration Server Administrator, or
directly set the watt.server.smtpServer property.
TRNSERV.000014.000087 Cannot specify a Sender of <'Any' or 'Unknown'> and also supply a specific senderIds
Cause: When invoking wm.tn.route:create, you cannot specify that the processing rule matches 'Any' sender or
the 'Unknown' sender, and also supply specific senderIDs.
Response: Either remove "Any", "Unknown", or the specific senderIDs.

TRNSERV.000014.000089 Cannot specify a DocType of <'Any' or 'Unknown'> and also supply specific docTypeIds.
Cause: When invoking wm.tn.route:create, you cannot specify that the processing rule matches 'Any'
document type or the document type is 'Unknown', and also supply specific document type IDs.
Response: Either remove "Any", "Unknown", or the specific document type IDs.
TRNSERV.000014.000090 An exception prevented the sender\'s identity from being completely checked. The original
exception was <exceptionMessage>.
Cause: Threw a ProfileStoreException while checking the identity of the document sender.
TRNSERV.000014.000092 Profile store error

Cause: Threw a ProfileStoreException while checking the identity of the document sender.
TRNSERV.000014.000094 The sender of this document (<corpName>/<orgUnitName>) is in status <status>. Documents from
this partner are not permitted at this time.
Cause: The document sender is not active. Inactive partners are not allowed to send documents to Trading
Networks.
Response: You can either ignore this error, activate this partner's profile, or notify the partner to stop sending
documents.
TRNSERV.000014.000095 The sender of document <docID> (<corpName>/<orgUnitName>) is in status <status>. Documents

from this partner are not permitted at this time.
Networks.
documents.
TRNSERV.000014.000096 Bad status

Networks.
documents.

TRNSERV.000014.000097 An error occurred trying to send this document via <protocol> (intended receiver: <receiverID>).
The original error message was: <exceptionMessage>.
TRNSERV.000014.000098 An error occurred trying to send this document via <protocol> (sender: <senderID>). The original
error message was: <exceptionMessage>.
TRNSERV.000014.000099 Couldn't send doc <docID> via <protocol>: <exceptionMessage>

TRNSERV.000014.000100 An error occurred trying to fetch profile information for sending email to the <contactType>
contact of partner <partnerID>. The original error was: <exception>
Cause: Unable to retrieve the partner profile while sending an e-mail alert. See the exception message for
details.
TRNSERV.000014.000101 Profile error

Cause: Unable to retrieve the partner profile while sending an e-mail alert. See the exception message for
details.
TRNSERV.000014.000102 Processing aborted: <exceptionMessage>

TRNSERV.000014.000104 <attributeName> is not a known document attribute."

Cause: The wm.tn.route:create service was supplied an invalid attribute name.
Response: Supply only names of existing document attributes.

TRNSERV.000014.000107 No preferred protocol. Status changed to POLLABLE.

Cause: The processing rule was configured to send the document using the receiver's preferred protocol, but
the receiver does not have a preferred protocol.
Response: Signify one of the receiver's delivery methods as the preferred protocol.
TRNSERV.000014.000111 No profile summary was available for the sender of this document
Cause: Could not process the document because Trading Networks could not find a partner profile for the
sender.
Response: Modify either the sender identification in the document or the external ID in the profile.
TRNSERV.000014.000112 No profile summary was available for the sender of document <docID>. The sender ID was
<partnerID>, and the sender logged in as <userID>.
sender.
TRNSERV.000014.000113 No profile summary available

sender.
TRNSERV.000014.000114 A supplied attribute condition has an invalid combination of datatype, operator and value
(<dataType> <operator> <condition>).
Cause: The wm.tn.route:create service was supplied an invalid attribute condition.
Response: Correct the attribute condition.
TRNSERV.000014.000115 An invalid value was supplied for the tn.recursion.max property. No recursion of processing rules
will be allowed.
Cause: The value of the tn.recursion.max property is not a valid number.
Response: Supply a valid number for this property.

TRNSERV.000014.000116 Processing recursion exceeded the allowed recursion depth of <maxRecursions>. The processing
rule <ruleName> invoked itself, most recently with document <docID>. Processing fails.
Cause: One or more processing rules invoked services that resubmitted documents to Trading Networks,
causing the recursion limit defined by the tn.recursion.max property to be exceeded.
Response: Increase the value of the tn.recursion.max property, or configure your processing rules not to
resubmit documents.
TRNSERV.000014.000117 Couldn't load routing schedule: <exceptionMessage>

Cause: Encountered an exception while reading the set of processing rules from the database.
TRNSERV.000014.000118 Couldn't save routing schedule: <exceptionMessage>

Cause: Encountered an exception while saving the set of processing rules to the database.
TRNSERV.000014.000119 Cannot specify a Receiver of Any and also supply a specific receiverIds.
Cause: When invoking the wm.tn.route:create service, you cannot specify that the processing rule matches
'Any' receiver and also supply specific receivers.
Response: Either remove "Any" or the specific receivers.
TRNSERV.000014.000120 Cannot specify a Receiver of Unknown and also supply a specific receiverIds.
Cause: When invoking the wm.tn.route:create service, you cannot specify that the processing rule matches an
'Unknown' receiver and also supply specific receivers.
Response: Either remove "Unknown" or the specific receivers.
TRNSERV.000014.000121 Cannot specify a DocType of Any and also supply specific docTypeIds.
Cause: When invoking the wm.tn.route:create service, you cannot specify that the processing rule matches
'Any' TN document type and also supply specific TN document types.
Response: Either remove "Any" or the specific TN document types.
TRNSERV.000014.000122 Cannot specify a DocType of Unknown and also supply specific docTypeIds.
Cause: When invoking the wm.tn.route:create service, you cannot specify that the processing rule matches the
'Unknown' TN document type and also supply specific TN document types.
Response: Either remove "Unknown" or the specific TN document types.

TRNSERV.000014.000123 If deliverUsing is "Queue for delivery", then deliveryQueue cannot be null

Cause: An invalid combination of input values was sent to the wm.tn.route:create service.
Response: Supply a value for the "deliveryQueue" variable.
TRNSERV.000014.000125 Cannot queue a bizdoc for deliver that has not been persisted. This bizdoc (id=<docID>) has not
been persisted.
Cause: The scheduled delivery mechanism requires that the document be saved to the database.
Response: Change the TN document type or processing rule to save documents of this type.
TRNSERV.000014.000130 qname is required

Cause: Attempted to enqueue a delivery job without supplying a queue name for the "qname" parameter.
Response: Supply a valid queue name for the "qname" parameter.
TRNSERV.000014.000131 Invalid queue name (<queueName>).

Cause: Attempted to enqueue a delivery job without supplying a queue name for the "qname" parameter.
Response: Supply a valid queue name for the "qname" parameter.
TRNSERV.000014.000132 Receiver does not have a delivery queue.

Cause: The processing rule is configured to send the document to the receiver's private delivery queue, but the
receiver does not have a delivery queue.
Response: Change the processing rule to deliver the document by a different means, or create a delivery queue
for the receiver.
TRNSERV.000014.000133 Receiver does not have a delivery queue. Document has been made POLLABLE (document
id=<docID>)
Cause: The processing rule is configured to send the document to the receiver's private delivery queue, but the
receiver's profile does not contain a definition for a delivery queue.
Response: Change the processing rule to deliver the document by a different means, or update the receiver's
profile to specify a delivery queue.
TRNSERV.000014.000134 Receiver does not have a preferred protocol. Document has been made POLLABLE. (document
id=<receiverID>)
Cause: The processing rule is configured to send the document by the receiver's preferred delivery method, but
the receiver does not have a preferred delivery method.
Response: Change the processing rule to deliver the document by a different means, or signify one of the
delivery methods on the receiver's profile as "preferred".

TRNSERV.000014.000135 Error encountered in RoutingActions.invoke(): can not clone input pipeline.
Cause: An internal error occurred while invoking a service to process the document.
TRNSERV.000014.000136 Unable to save document: <exceptionMessage>.

TRNSERV.000014.000138 The processing rule list has been modified by another user. Added this rule to the bottom of the
list. Refresh your rule list.
Cause: The rule list displayed on your Trading Networks Console is not the current list that resides in the
database. As a result, the newly added rule is appended to the end of the rule list rather than the specific
position required in the list.
Response: Refresh your routing rule list and move the newly added rule to the desired position.
TRNSERV.000014.000139 Error encountered while inserting processing rule <id>. The exception message is : <message>.
Cause: Encountered an Exception while inserting processing rule.
the Exception.
TRNSERV.000014.000140 Error encountered while updating processing rule <id>. The rule index cannot be changed during
an update operation.
Cause: You attempted to update both the contents of a processing rule and its location within the list of
processing rules (i.e., its index) at the same time. You cannot make both these changes at the same time.
Response: Please update the rule first, and then move the rule to a new position in the rule list.
TRNSERV.000014.000141 Error encountered while updating processing rule <id>. The exception message is : <message>.
Cause: Encountered an Exception while updating processing rule.
the exception.

TRNSERV.000014.000142 Processing rule update failed. Processing rule update collision detected. This rule has been
modified by another user. Refresh your rule list and retry this operation.
Cause: While you were updating this processing rule, another user edited and saved the same processing rule.
To prevent your changes from overwriting those made by the other user, Trading Networks did not save your
changes.
Response: Refresh the list of processing rules and update the processing rule again.
TRNSERV.000014.000145 Error encountered while deleting processing rule(s). The exception message is : <message>.
Cause: Encountered an Exception while deleting processing rule(s).
the exception.
TRNSERV.000014.000146 Processing rule delete operation aborted. The processing rule list has been modified by another
user. Refresh your rule list and retry this operation.
Cause: While you were deleting this processing rule, another user edited and saved the rule. So that your
changes do not overwrite those made by the other user, your changes have not been saved.
Response: Refresh your rule list, and then delete the rule again.
TRNSERV.000014.000147 Processing rule <id> does not exist.

Cause: The specified routing rule cannot be retrieved because the rule ID does not exist in the database.
Response: Check that the rule id is correct, modify it if necessary, and then attempt to retrieve it again.
TRNSERV.000014.000148 Error encountered while reading processing rules from the database. The exception message is :
<message>.
Cause: Encountered an Exception while retrieving processing rules from the database.
the exception.
TRNSERV.000014.000149 Error encountered while moving processing rules. The exception message is : <message>.
Cause: Encountered an Exception while moving the processing rule in the rule list.
the exception.

TRNSERV.000014.000150 Processing rule move operation aborted. The processing rule list has been modified by another
user. Refresh your rule list and retry this operation.
Cause: While you were moving this processing rule, another user edited and saved the rule list. So that your
changes do not overwrite those made by the other user, your changes have not been saved.
Response: Refresh the rule list, and then move the rule again.
TRNSERV.000014.000151 Illegal move operation. The insertAt position cannot be within the range of rules to be moved.
Cause: The insertAt position is not within the range of rules to be moved.
Response: Change the insertAt position to be outside of the range of rules to be moved.
TRNSERV.000014.000152 Illegal move operation. You cannot move a non-contiguous set of rules.
Cause: You attempted to change the order of processing rules by moving a non-contiguous set of rules. Trading
Networks does not support this type of operation.
Response: Re-define the set of rules to be moved.
TRNSERV.000014.000153 Processing rule update failed. Processing rule <ruleName> has been deleted by another user.
Refresh your rule list
Cause: While you were editing this processing rule, another user deleted the rule.
Response: Refresh your list of processing rules, and then re-create the processing rule.
TRNSERV.000014.000156 <className>.<methodName> could not retrieve the ProfileStore.

Cause: An error occurred attempting to look up the Profile Summary.
Response: Ensure that the partner IDs on the document being processed are valid.
TRNSERV.000015.000002 Delivery service for <taskID> failed with a status of <status> and status message of
<statusMessage>
Cause: Unable to deliver the document, possibly due to a problem with the network or the destination server.
Response: Verify that your server has network connectivity. If <statusMessage> indicates a problem with the
destination server, contact the person responsible for that server.
TRNSERV.000015.000004 Unable to get output for task <taskID> - Task has not finished. Status is <status>
Cause: The task was still executing when the request for output expired.
Response: Request the output again.

TRNSERV.000015.000005 Unable to refresh <cacheName> cache on server <hostName> - <exceptionMessage>

Cause: A cache could not be refreshed, probably due to a database problem
connect to the database. Verify that your database is successfully processing requests.
TRNSERV.000015.000007 Unable to remove task <taskID> - Does not exist

Cause: An invalid task ID was supplied.
Response: Supply a valid task ID.
TRNSERV.000015.000011 Disabling reliable task manager at <timestamp) - Fatal error: <exceptionMessage>

Cause: Encountered an exception that requires the task manager to shut down.
TRNSERV.000015.000013 Unable to restart task <taskID> upon initialization

Cause: The task's status could not be updated to "Pending" in the database.
TRNSERV.000015.000015 Unable to persist task <taskID>

Cause: Encountered an exception while saving the task to the database.
Response: See the full message (TRNSERV.000015.000089) for details.
TRNSERV.000015.000019 Task <taskID> unable to move to server <hostName>

Cause: Task has already completed. Status is "Done".
TRNSERV.000015.000020 Unable to refresh Delivery Service cache - <exceptionMessage>

Cause: See exception message for details.
TRNSERV.000015.000025 Task <taskID> failed, status changed to <status>

Cause: Task has failed. No more retries.
Response: See full message (TRNSERV.000015.000036) for details.

TRNSERV.000015.000026 Unable to init task manager for server <hostName> - <exceptionMessage>
Cause: The task manager could not be initialized, probably due to a database problem.
TRNSERV.000015.000031 Error invoking service <serviceName> - message: <exceptionMessage> - stacktrace: <stackTrace>

Cause: The task manager invoked a service to process a document, and that service threw an exception.
Response: See the exception message for details. Correct the invoked service to handle the exception condition.
TRNSERV.000015.000036 Task <taskID> failed with no more retries available. Reason for failure - <statusMessage>
Cause: See the status message for details.
Response: If the failure is due to an error on another server, contact the person responsible for that server.
TRNSERV.000015.000037 Unable to restart task <taskID> - <taskStatus>

Cause: The task status is neither "Failed" nor "Stopped", so the task cannot be restarted.
Response: No action necessary.
TRNSERV.000015.000039 Unable to shut down the task manager.

Cause: The wm.tn.task:shutdown service was unable to stop the task manager. See the nested exception for
details.
Response: Take appropriate action to resolve the problem described in the nested exception.
TRNSERV.000015.000042 Unable to initialize task manager.

Cause: The wm.tn.task:init service was unable to start the task manager. See the nested exception for details.
TRNSERV.000015.000043 Unable to reset task manager.

Cause: The wm.tn.task:restart service was unable to restart the task manager. See the nested exception for
details.

TRNSERV.000015.000044 Unable to retrieve tasks.

Cause: The wm.tn.task:getTasks service was unable to get tasks from the task manager. See the nested
exception for details.
TRNSERV.000015.000045 Unable to retrieve task <taskID>.

Cause: The wm.tn.task:getTask service was unable to get a task from the task manager. See the nested
TRNSERV.000015.000046 Unable to get output for task <taskID>.

Cause: The wm.tn.task:getTaskOutput service was unable to get output for a task. See the nested exception for
details.
TRNSERV.000015.000047 Unable to get status for task <taskID>.

Cause: The wm.tn.task:getTaskStatus service was unable to get the status of a task. See the nested exception for
details.
TRNSERV.000015.000048 Unable to change server for task <taskID>.

Cause: The wm.tn.task:changeServerForTask service was unable to move a task from one server to another. See
the nested exception for details.
TRNSERV.000015.000049 Unable to remove task <taskID>.

Cause: The wm.tn.task:removeTask service was unable to remove a task from the task manager. See the nested
TRNSERV.000015.000050 Unable to restart task <taskID>.

Cause: The wm.tn.task:restartTask service was unable to restart a task in the task manager. See the nested

TRNSERV.000015.000051 Unable to stop task <taskID>.
Cause: The wm.tn.task:stopTask service was unable to stop a task in the task manager. See the nested exception
for details.
TRNSERV.000015.000052 Unable to move task <taskID> to server <hostName>. Task does not exist.
TRNSERV.000015.000053 Unable to move task <taskID> to server <hostName>. Task has completed.
Cause: Task status is "Done". Cannot move a completed task.
TRNSERV.000015.000054 Unable to move task <taskID> to server <hostName>. Could not \'ping\' server:
<exceptionMessage>.
Cause: Invoked the wm.server:ping service on the other server, and it threw an exception.
Response: Take appropriate action to resolve the problem on the other server as described in the exception.
TRNSERV.000015.000055 Unable to move task <taskID> to server <targetHost>. Server <originalHost> is up, but the task has
not failed.
Cause: The server that created this task is running. Therefore, the task cannot be moved because the task's
status is neither "Failed" nor "Stopped".
TRNSERV.000015.000056 Unable to move task <taskID> to server <targetHost>. Server <originalHost> is down, but the task
is done.
Cause: Task status is "Done". Cannot move a completed task.
TRNSERV.000015.000057 Unable to stop task <taskID>. Job has completed.

Cause: Cannot stop a completed task.

TRNSERV.000015.000058 Unable to stop task <taskID>. Job does not exist.

TRNSERV.000015.000060 Delivery Job Manager error: task <taskID> is not NEW.

Cause: Cannot start a task that does not have a "New" status.
Response: No action necessary. Task has already started.
TRNSERV.000015.000061 Delivery Job Manager error with task <taskID>. <exceptionMessage>

Cause: Encountered an exception while writing to the database. See the exception message for details.
TRNSERV.000015.000062 Task <taskID> unable to restart. Does not exist.

TRNSERV.000015.000064 Unable to remove task <taskID>. <exception Message>

Cause: Encountered an exception while writing to the database. See the exception message for details.
TRNSERV.000015.000065 Cannot get job output. Job does not exist.

TRNSERV.000015.000066 Unable to initialize task manager. ServerId is null.

Cause: Unable to determine server ID.
Response: Supply a value for the watt.net.localhost property in the Integration Server's server.cnf file.
TRNSERV.000015.000068 Unable to delete tasks. There are <number> active jobs in the list of jobs to be deleted. Stop the
active jobs and retry
Cause: Cannot delete active tasks.
Response: If you want to delete tasks that are active, stop them first.

TRNSERV.000015.000069 Unable to get task
Cause: The wm.tn.route:getTask service can only retrieve tasks that are service execution tasks. A taskID of a
delivery task was supplied.
Response: Request only service execution tasks from the wm.tn.route:getTask service.
TRNSERV.000015.000070 Error getting task

Cause: The wm.tn.route:getTask service encountered an exception while retrieving a task. See the nested
TRNSERV.000015.000072 Unable to restart queued task (id=<taskID>). Its delivery queue no longer exists. You can resubmit
the document to process it again.
Cause: The delivery queue for this document has been deleted. Cannot be requeued.
Response: Verify that the processing rule that handles this document is configured to use a valid delivery
queue. Resubmit the document.
TRNSERV.000015.000081 Error invoking service, <serviceName> - Service did not return valid output
Cause: The task manager invoked a service to process a document. The output of the service did not conform to
the expected format.
Response: If this is a delivery service, make sure the output matches the wm.tn.rec:DeliveryServiceOutput IS
document type. If this is a service invoked by a service execution task, make sure the output matches the
wm.tn.rec:reliableServiceOutput IS document type.
TRNSERV.000015.000082 ERROR: Unable to update task <taskID> due to database error : <exceptionMessage>. Since task
update retry is truned off, manual correction is required. Please correct the database errors and manually update the task
using the additional task details provided. Additional Details of this task : Task ID=<taskID>; DocID=<bizdocID>>;
TaskStatus=<taskStatus>; Retries=<currentRetryCount>; TransportStatus=<transportStatus>;
TransportStatusMessage=<transportStatusMsg>; TransportTime=<duration>
Cause: Could not update the task. See exception message for details.
Response: Manually update the task on the Trading Networks Console using the details provided in the
message.

TRNSERV.000015.000089 ERROR: Unable to update task <taskID> due to IOException : <exceptionMessage>. Task update
will continue to fail until this exception is rectified. Until this error is rectified, manual correction is required. Manually update
the task using the additional task details provided. Additional Details of this task : Task ID=<taskID>; DocID=<bizdocID>;
TaskStatus=<taskStatus>; Retries=<currentRetryCount>; TransportStatus=<transportStatus>;
TransportStatusMessage=<transportStatusMsg>; TransportTime=<transportDuration>
Cause: Could not update the task. See exception message for details.
Response: Manually update the task on the Trading Networks Console using the details provided in the
message.
TRNSERV.000015.000091 TN Job Manager sweep time property tn.task.sweepTime contains (<value>), which is not a
numeric value. Using the default value 300 seconds
Cause: The tn.task.sweepTime property contained an invalid value.
Response: Supply a valid, numeric value.
TRNSERV.000016.000004 Cannot save a <profileComponent> without a <field>.

Cause: The specified profile component cannot be saved because it is missing a required field.
Response: Supply a value for the field.
TRNSERV.000016.000005 Error logging database event

Cause: Encountered an exception while writing an ActivityLogEntry to the database.
Response: The exception is written to the server log. See the exception for details.
TRNSERV.000016.000006 Error encountered deleting <tnObject>. <number> rows changed in database.

Cause: Expected to delete exactly one row from a table in the database. Instead the specified number of rows
were deleted.
TRNSERV.000016.000008 Table not recognized: <tableName>.

Cause: Found a profile field in the database that references a non-existent table.
TRNSERV.000016.000009 Error inserting document <docID>

Cause: Encountered an exception while writing a document to the database.
Response: The exception is in the full message. Take appropriate action to resolve the problem described in the
exception.

TRNSERV.000016.000011 Error querying documents: <exceptionMessage>. Original SQL: <sql>
Cause: Encountered an SQLException while performing a document query.
TRNSERV.000016.000012 Insert of field definition failed.

Cause: Attempted to add a profile field definition, but the database was unchanged.
TRNSERV.000016.000016 An attempt was made to access the SQL statement <statementID>, which was not defined in the
configuration file
Cause: Attempted to execute an SQL statement that is not available in the file of externalized SQL statements
(dbops.sql).
Response: If you have modified the dbops.sql file, restore the file to its prior state.
TRNSERV.000016.000026 An attempt was made to save an extended field with an unsupported datatype. Name=<fieldName>,
Datatype=<supportedDatatype>.
Cause: Attempted to save an extended field for a partner, but the field's value is not a supported data type.
Response: Supply a value that is one of the supported data types for an extended field.
TRNSERV.000016.000027 Couldn't update type <doctypeID> for attribute <attributeName>

Cause: Attempted to save a document attribute, but the attribute did not reference a valid document type.
Response: If you are explicitly calling services to save an attribute, ensure that the attribute refers to a valid
document type.
TRNSERV.000016.000029 The database has no version information. Either it has not been initialized, or it has been changed
to an invalid state by an external process.
Cause: The TNModelVersion table is missing. Either data from this table was accidentally deleted, the table
was dropped, or your database is corrupt.
Response: Restore this table from the most recent backup. If your database is corrupt, work with your DBA to
determine the cause. In this case, you will need to restore your entire database to the most recent backup.
TRNSERV.000016.000031 No model version information was available from the database.

Cause: The TNModelVersion table is missing. Either data from this table was accidentally deleted, the table
was dropped, or your database is corrupt.
Response: Restore this table from the most recent backup. If your database is corrupt, work with your DBA to
determine the cause. In this case, you will need to restore your entire database to the most recent backup.

TRNSERV.000016.000036 Unsupported encoding <encoding> declared in the TN config file (tn.store.encoding)

Cause: The tn.store.encoding property was set to an invalid value.
Response: Set the tn.store.encoding property to a valid value.
TRNSERV.000016.000037 The model version specified (tnmv:) seems to be missing from the dbops.sql file in your WmTN
package. Check the file and try again.
Cause: The dbops.sql file must begin with "-- tnmv: x.x", where "x.x" is the current TNModelVersion number.
This line has been removed or altered.
Response: Restore the dbops.sql file to correct state.
TRNSERV.000016.000039 There was an error reading the dbops.sql file in your WmTN package. The original error message
Cause: Encountered an exception while reading the dbops.sql file. See the exception message for details.
TRNSERV.000016.000040 Error encountered updating <tnObject>. <number> rows changed in database.

Cause: Expected to update exactly one row in a table in the database. Instead the specified number of rows
were updated.
TRNSERV.000016.000041 Error redefining attribute <attributeID> (<attributeName>)

Cause: Encountered an SQLException while updating a document attribute.
TRNSERV.000016.000042 Error encountered updating <profileComponent>. <number> rows changed in database for
<partnerID>.
Cause: Expected to update exactly one row in a table in the database. Instead the specified number of rows
were updated.
TRNSERV.000016.000047 No extended fields were deleted for group <fieldGroup> (partnerID=<partnerID>).

Cause: Expected to delete exactly one row in the PartnerProfileField table in the database. Instead no rows
were updated.

TRNSERV.000016.000051 Unable to insert binary object (partnerID=<partnerID>).
Cause: An INSERT statement was unsuccessful in adding a row to the database.
TRNSERV.000016.000064 There was an error interpreting the model version specifier (tnmv:) in the dbops.sql file in your
WmTN package. The original error message was: <exceptionMessage>
Cause: The dbops.sql table must begin with "-- tnmv: x.x", where "x.x" is the current TN Model Version
number. This line has been altered.
Response: Restore this line to its correct state.
TRNSERV.000016.000066 The main connection to the datastore has not been initialized. Check the Trading Networks JDBC
connection pool.
Cause: There is no connection to the Trading Networks database.
Response: Use the Integration Server Administrator JDBC Pools page to test the connection to the Trading
Networks database. You may need to adjust the connection pool settings or verify that the database is
functioning normally.
TRNSERV.000016.000067 Extended field (fieldID=<fieldID>) not deleted (partnerID=<partnerID>).

Cause: A DELETE statement was unsuccessful in removing a row from the database.
TRNSERV.000016.000079 More than one extended field (fieldID=<fieldID>) removed in a single delete operation
(partnerID=<partnerID>).
Cause: Expected to delete exactly one row in a table in the database. Instead multiple rows were deleted.
TRNSERV.000016.000085 Cannot change a <profileComponent> without a <field>.

Cause: Attempting to update a profile component, but a required field is missing.
Response: Supply a value for the missing field.

TRNSERV.000016.000089 Trading Networks could not retrieve data from your database. Go to the JDBC Pools page in the
Integration Server Administrator and make sure your database URL, user name, and password are set correctly. Also make
sure you created the Trading Networks database tables as described in the webMethods Installation Guide.
Cause: The TNModelVersion table is missing from the Trading Networks database. The reason can be one of
the following: 1) The Trading Networks database tables have not yet been created. 2) Data from
TNModelVersion table was accidentally deleted. 3) The TNModelVersion table was dropped. 4) Your
database is corrupt.
Response: Check your database. If the Trading Networks tables have not been created, create them. If the
TNModelVersion table is missing or not valid, re-create it. If your database is corrupt, work with your
database administrator to determine the cause. You might need to restore your entire database from the most
recent backup.
TRNSERV.000016.000096 Document <docID> from this sender was not successfully stored in the datastore. The original
exception message was: <exceptionMessage>
Cause: Encountered an exception while writing a document to the database.
TRNSERV.000016.000104 An attempt was made to access the SQL statement <sql> before SQL statements were read from
disk.
Cause: An SQL statement was used before the SQL statement cache was initialized.
Response: If your package uses Trading Networks facilities, be sure to declare a dependency on the WmTN
package in your package's manifest.v3 file.
TRNSERV.000016.000110 Error decoding type <doctypeID>

Cause: Encountered an IOException while decoding binary data from the database into a BizDocType object.
TRNSERV.000016.000112 Document type not saved. A document type with the name <doctypeName> already exists. Cannot
have two document types with the same name but different IDs.
Cause: You cannot have two document types with the same name.
Response: Change the name of the document type and save it again.
TRNSERV.000016.000114 The system could not load the JDBC driver <className> for connection to the datastore. Check
the CLASSPATH setting and try again.
Cause: The driver specified for the Trading Networks functional alias on the JDBC Pools Configuration page of
the Integration Server could not be found.
Response: Make sure the driver is on your classpath.

TRNSERV.000016.000119 Unknown or deleted attribute <attributeID>
Cause: the wm.tn.doc:setAttribute service was supplied an invalid attribute ID or name.
Response: Supply a valid attribute ID or name.
TRNSERV.000016.000127 Error encountered updating Contact. <number> rows changed in database for <givenName>
<surname>.
Cause: Expected to update exactly one row on the Contact table in the database. Instead the specified number
of rows were updated.
TRNSERV.000016.000131 Couldn't find doc <docID>; no doctype <doctypeID>

Cause: Could not create a bizdoc from binary data in the database. The TN document type it references does
not exist.
TRNSERV.000016.000132 Couldn't archive documents

Cause: Encountered an SQLException while archiving documents.
TRNSERV.000016.000133 Couldn't delete archived documents

Cause: Encountered an SQLException while deleting archived documents.
TRNSERV.000016.000134 Couldn't delete documents

Cause: Encountered an SQLException while deleting documents.
TRNSERV.000016.000135 Couldn't queue document

Cause: Encountered an SQLException while queuing a document for polling.

TRNSERV.000016.000136 Couldn't poll documents

Cause: Encountered an SQLException while polling for documents.
TRNSERV.000016.000137 Couldn't accept document

Cause: Encountered an SQLException while accepting a polled document.
TRNSERV.000016.000138 Couldn't query event table

Cause: Encountered an SQLException while querying activity log entries.
TRNSERV.000016.000139 Couldn't delete events

Cause: Encountered an SQLException while deleting activity log entries.
TRNSERV.000016.000140 Couldn't instantiate document <docID>

Cause: Encountered an SQLException while retrieving a document.
TRNSERV.000016.000141 Couldn't check uniqueness <docID>

Cause: Encountered an SQLException while querying the database to determine if a document is unique.
TRNSERV.000016.000142 Couldn't get user status

Cause: Encountered an SQLException while retrieving the user status of a document.

TRNSERV.000016.000143 Couldn't insert new document
Cause: Encountered an SQLException while saving a new document.
TRNSERV.000016.000144 Couldn't change status for <docID>

Cause: Encountered an SQLException while changing the status of a document.
TRNSERV.000016.000145 One of (fromdoc,todoc) must be persisted

Cause: Attempted to relate two documents, but neither of them have been saved to the database.
Response: Save one or both of the documents to be related.
TRNSERV.000016.000146 Couldn't relate <fromDocID> and <toDocID>

Cause: Encountered an SQLException while relating two documents.
TRNSERV.000016.000147 Couldn't get rels: doc=<docID>, gr=<groupID>

Cause: Encountered an SQLException while retrieving related documents.
TRNSERV.000016.000148 The following exceptions occurred:

Cause: The following exceptions were encountered while retrieving the full set of TN document types.
Response: See each of the following exceptions for details. Take appropriate action to resolve the problem
described in each exception.
TRNSERV.000016.000149 Database error fetching all types: <exceptionMessage>

Cause: Encountered an SQLException while retrieving the full set of TN document types.

TRNSERV.000016.000150 Database error putting type <doctypeID>: <exceptionMessage>

Cause: Encountered an SQLException while saving a new TN document type.
TRNSERV.000016.000151 Encoding error putting type <doctypeID>: <exceptionMessage>

Cause: Encountered an IOException while saving a new TN document type.
TRNSERV.000016.000152 Database error updating type <doctypeID>: <exceptionMessage>

Cause: Encountered an SQLException while updating a TN document type.
TRNSERV.000016.000153 Encoding error updating type <doctypeID>: <exceptionMessage>

Cause: Encountered an IOException while saving a new TN document type.
TRNSERV.000016.000154 Can't aggregate over STRING attributes

Cause: Attempted to execute an aggregation operation (i.e., SUM, AVG, MIN, MAX) on a String attribute.
Response: Do not specify the aggregation operation.
TRNSERV.000016.000160 Couldn't queue document for delivery (id=<docID>)

Cause: Encountered an SQLException while changing the status of a document to "QUEUED".
TRNSERV.000016.000162 Trading Networks database pool is not configured. Please configure a database pool for functional
alias "TN" and restart WmTN package.
Cause: Data required to configure a connection to the database is missing or invalid.
Response: Use the Integration Server Administrator JDBC Pools page to recreate this data.

TRNSERV.000016.000164 Error logging activity entry to audit sub system. The exception message is : <exceptionMessage>
Cause: Encountered an exception while publishing an activity log entry.
TRNSERV.000016.000165 Error when reading database configuration. The exception message is : <exceptionMessage>
Cause: Trading Networks encountered an exception while reading the database configuration data.
resolve the problem described in the exception. You might need to use the JDBC Pools page in the Integration
Server Administrator to recreate this data.
TRNSERV.000016.000168 Trading Networks database pool is not configured properly. Make sure that a valid database pool is
assigned for functional alias "TN" and restart WmTN package.
TRNSERV.000016.000169 Unable to locate database configuration information. File <configFile> does not exist.
Cause: A file required to configure a connection to the database is missing.
TRNSERV.000016.000170 Trading Networks database pool is not configured properly. Make sure that a valid database pool is
assigned to functional alias "TN" and try again.
TRNSERV.000016.000175 The pool associated with TN should allow at least 2 connections. Your TN pool is currently
configured with a maximum of <number> connections. Aborting TN startup. Please increase your TN database pool
maximum and restart the server.
Cause: Trading Networks requires at least two connections for its pool. Trading Networks will not initialize
with less than two connections.
Response: Use the Integration Server Administrator JDBC Pools page to increase the number of connections
allowed for the Trading Networks database pool. Then restart your server.
TRNSERV.000016.000180 Database Error deleting document type <doctypeID>: <exceptionMessage>

Cause: Encountered an SQLException while deleting a document type.

TRNSERV.000016.000181 A BizDocType with this name already exists: <name>

Cause: You cannot have two document types with the same name.
Response: Save the document type with a different name.
TRNSERV.000016.000184 The profile field definition "<fieldName>" already exists with a different ID. The field definition was
not imported.
Cause: This error can occur when importing extended profile fields. The most likely cause is that the field was
already manually created on the target server.
Response: If you do not intend to import extended field values, this error can be ignored. If you do intend to
import extended field values, and no partner yet has a value for this field on your target server, you can
change the ID of the field definition to match the one on the source server. Carefully update the ProfileFieldID
key in the ProfileField table of the database into which you are importing.
TRNSERV.000016.000185 An IDType with a key of <keyValue> already exists with a different ID description. The IDType
"<idTypeName>" was not imported. You will need to directly edit the IDType table in your database to correct this problem.
Cause: The error can occur when importing extended ID types. The most likely cause is that the IDtype was
already manually created on the target server.
Response: Change the Type column of the IDType table on the target database to match that of the source
database.
TRNSERV.000017.000007 wm.tn.admin:installACLs: Unable to find group, <group>

Cause: The specified group, <group>, has not been created.
Response: Run the wm.tn.admin:install service to create the Trading Networks user groups.
TRNSERV.000017.000010 Can not create IS user group <group>

Cause: An exception was thrown while creating a user group during server startup.
TRNSERV.000017.000011 Can not create IS user <user>

Cause: An exception was thrown while creating a user during server startup.
TRNSERV.000018.000001 <variable> is required

Cause: A value was not supplied for the specified variable.

TRNSERV.000018.000002 wm.tnweb.wrapper:xmlEncode: could not encode IData to binary
Cause: An exception was thrown while encoding an IData.
Response: Gather error information from the log and contact webMethods Customer Care.
TRNSERV.000018.000003 wm.tnweb.wrapper:xmlDecode: could not decode binary to IData

Cause: An exception was thrown while decoding an IData.
TRNSERV.000018.000004 wm.tnweb.wrapper:xmlDecode2: could not decode binary to Values

Cause: An exception was thrown while decoding an IData.
TRNSERV.000018.000005 wm.tnweb.wrapper:removeNullAlerts: error caught in removing null alerts

TRNSERV.000018.000006 wm.tnweb.wrapper:compareRights: error caught in comparing rights

TRNSERV.000018.000007 wm.tnweb.wrapper:getTNRights: error caught in getting Trading Networks partner ACL privilege
TRNSERV.000018.000008 wm.tnweb.wrapper:getUserGroups: error caught in getting Trading Networks partner ACL group
memberships
TRNSERV.000018.000009 wm.tnweb.wrapper:getUserInfo: error caught in getting Trading Networks partner IS login name

TRNSERV.000018.000010 wm.tnweb.wrapper:getHashKeys: error caught in getting Hashtable keys

TRNSERV.000018.000011 <variable> cannot be null

TRNSERV.000018.000012 wm.tnweb.wrapper:IntegerToStrng: error caught converting Integer datatype to String datatype

TRNSERV.000018.000013 wm.tnweb.wrapper:ShortToStrng: error caught converting Short datatype to String datatype

TRNSERV.000018.000014 wm.tnweb.wrapper:isBIEnabled: error caught in retrieving enabled Integration Server packages

TRNSERV.000018.000015 wm.tnweb.wrapper:isBIEnabled: could not find if Business Integrator (ProcessMonitor) package is

installed and enabled
TRNSERV.000018.000016 wm.tnweb.wrapper:getStringFromBundle: could not get String from resource bundle

wm.tnweb.wrapper_bundle for key = <key>
TRNSERV.000018.000017 wm.tnweb.querySvc:getQuery: could not get pre-saved query (<query>) for partnerID=<partnerID>

TRNSERV.000018.000018 <variable> cannot be null or empty
TRNSERV.000018.000019 partnerID is null or empty in invoking wm.tnweb.querySvc:getSavedQueries

TRNSERV.000018.000020 wm.tnweb.querySvc:getSavedQueries: could not get pre-saved queries for partnerID=<partnerID>

TRNSERV.000018.000021 wm.tnweb.querySvc:getDocuments: could not get documents

TRNSERV.000018.000022 wm.tnweb.querySvc:createTaskQuery: could not create task query for document id=<id>
TRNSERV.000018.000023 wm.tnweb.querySvc:getCalendar: invalid input <year/month>

TRNSERV.000018.000024 wm.tnweb.querySvc:getCalendar: could not get calendar for year=<year>, month=<month>

TRNSERV.000018.000025 wm.tnweb.querySvc:getQueryRestriction: could not get document query restriction for document
id = <id>

TRNSERV.000018.000026 Could not get profile store

TRNSERV.000018.000027 Could not get document attributes for id = <id>

TRNSERV.000018.000028 Could not get internal document type id for name = <doctypeName>
TRNSERV.000018.000029 wm.tnweb.configSvc:checkDefaultConfigLoaded: could not check if default config is loaded

TRNSERV.000018.000030 wm.tnweb.configSvc:getHashes: could not construct Hashtables for TNAdministrators and

TNPartners
TRNSERV.000018.000035 wm.tnweb.configSvc:getUserConfig: could not get membership info for user <userName>
Cause: There is no user account for the specified user on the Integration Server.
Response: If you have deleted the user account for this user, use the Server Administrator to create the user
account again. If this is for an external user, ensure the user account is a member of the TNPartners group.
TRNSERV.000018.000039 wm.tnweb.configSvc:getUserConfig: could not get partner specific config for <userName>
TRNSERV.000018.000040 wm.tnweb.configSvc:getGroupConfig: could not get group specific config for <groupName>

TRNSERV.000018.000041 wm.tnweb.configSvc:getTNPartners: could not get partner information
TRNSERV.000018.000042 wm.tnweb.configSvc:getTNGroups: could not get IS group information

TRNSERV.000018.000043 wm.tnweb.configSvc:getTNUsers: could not get Trading Networks IS user information

TRNSERV.000018.000044 wm.tnweb.configSvc:getUserConfigDisplay: could not get specific user config information

TRNSERV.000018.000045 wm.tnweb.configSvc:getAvailableStatus: could not get user status from database

TRNSERV.000018.000047 wm.tnweb.configSvc:saveCustomPages: error encountered in saving new custom pages setting

TRNSERV.000018.000048 wm.tnweb.configSvc:addToHashes: invalid type value

TRNSERV.000018.000049 wm.tnweb.configSvc:addToHashes: could not add new config IData to hashtable


TRNSERV.000018.000050 wm.tnweb.configSvc:changeConfig: could not change config setting

TRNSERV.000018.000051 wm.tnweb.querySvc:getQueryRestriction: do not have privilege to check query restriction

TRNSERV.000018.000053 wm.tnweb.wrapper:logBrowserLocale: error encountered in getting browser locale

TRNSERV.000018.000054 cert is null

TRNSERV.000018.000055 CACerts is null

TRNSERV.000018.000056 CACerts[<index>] is null

TRNSERV.000018.000057 privateKey is null

TRNSERV.000018.000058 Can not get user specific configuration: no such user <userName>

TRNSERV.000018.000059 Error encountered calling wm.tnweb.configSvc:checkAndUpdateConfig
TRNSERV.000018.000061 Error updating/retrieving configuration info from repo

TRNSERV.000018.000062 Error encountered in invoking service wm.tnweb.querySvc:getPartnerNameAndID

TRNSERV.000018.000063 Can not get valid profile summary list: list is null or empty
TRNSERV.000018.000064 Error encountered in invoking service wm.tnweb.querySvc:runTaskQuery

TRNSERV.000018.000065 Error encountered in invoking service wm.tnweb.querySvc:taskQueryById

TRNSERV.000018.000066 Error encountered in invoking service wm.tnweb.querySvc:getDocDetails

TRNSERV.000018.000067 Got null bizdoc, docId = <id>


TRNSERV.000018.000068 Got null or 0-length bizdoc content parts, docId = <docID>

Cause: The content of this document might not have been saved to the Trading Networks database.
Response: Check the corresponding TN document type and processing rule to determine whether Trading
Networks saved the document content to the database.
TRNSERV.000018.000069 Invalid startIndex = <index>

TRNSERV.000018.000070 Can not convert content bytes to String: unsupported encoding

TRNSERV.000018.000071 NOTE: No privilege to view contents of this document

Cause: You attempted to view a document for which you were neither the sender nor the receiver.
Response: You cannot view the document contents.
TRNSERV.000018.000072 NOTE: No more data to display

Cause: Either the document has no content or the startIndex is beyond the end of the content.
Response: If you determine that this is an error, gather error information and contact webMethods Customer
Care.
TRNSERV.000018.000073 Got null bizdoc content part, docId=<id>, content part name=<part>
Cause: The content of this document might not have been saved to the Trading Networks database.
Response: Check the corresponding TN document type and processing rule to determine whether Trading
Networks saved the document content to the database.
TRNSERV.000018.000074 Error encountered in invoking service wm.tnweb.wrapper:getTNInfo

TRNSERV.000018.000075 Error encountered in invoking service wm.tnweb.wrapper:registerTNOnIntegrationServer


TRNSERV.000018.000076 Error encountered parsing date <fromDate> or <toDate>.
TRNSERV.000018.000077 Error encountered in invoking service wm.tnweb.wrapper:installTNWebACLs

TRNSERV.000019.000035 Recognize: unable to get XML DTD for comparison: <docTypeName> <dtdStatement> <publicID>
<systemID>
Cause: The DTD statement in the document may not be valid.
Response: Check the document being processed to ensure that it is well-formed. If it is not, notify the party
responsible for this document.
TRNSERV.000019.000036 BizDocTypeReg: ERROR invoking recognize for <exceptionMessage>

Cause: See the exception message for details.
TRNSERV.000019.000040 <docTypeName> No envelope queries specified

Cause: The TN document type has no envelope queries defined.
Response: Use the Trading Networks Console to edit the TN document type and define envelope queries.
TRNSERV.000019.000041 Error filling BizDocTypeStore cache

Cause: Encountered an error while reading the TN document types from the database and caching them in
memory.
connect to the database.
TRNSERV.000019.000042 Doctype info not initialized

Cause: The BizDocType Registry was not initialized.
Response: Reload the WmTN package.

TRNSERV.000019.000043 Unknown type name: <docTypeName>

Cause: The wm.tn.doctype:view service was passed an invalid TN document type name.
Response: Pass a valid TN document type name to this service.
TRNSERV.000019.000044 Unknown type id: <docTypeID>

Cause: The wm.tn.doctype:view service was passed an invalid TN document type ID.
Response: Pass a valid TN document type ID to this service.
TRNSERV.000019.000045 Operation not supported for RecordDocType

Cause: You cannot create an instance of the RecordDocType.
Response: Do not attempt to create an instance of the RecordDocType.
TRNSERV.000019.000054 IOException encoding pipeline

Cause: Encountered an exception while binary-encoding the data for an unknown document type. See the
nested exception for details.
TRNSERV.000019.000056 Query or Transform Failed

Cause: Encountered an exception while extracting a document attribute and transforming its value.
Response: Verify that the attribute extraction query in the TN document type is valid.
TRNSERV.000019.000057 Transform Failed

Cause: An error occurred while transforming the attribute value.
Response: Use the Trading Networks Console to verify that the Attribute Details for the TN document type
appear correct. If they are, gather details about the error, and contact webMethods Customer Care.
TRNSERV.000019.000058 Error generating query expression

Cause: Encountered an exception while generating an XML query to extract a document attribute.
Response: Correct the attribute extraction query on the TN document type.
TRNSERV.000019.000059 No such BizDocType: <docTypeID>

Cause: The wm.tn.doc:createReply service was passed an invalid replyTypeId.
Response: Pass a valid replyTypeId to this service.

TRNSERV.000019.000060 Doctype info not initialized. BizDocType registry has not been created.
Cause: The BizDocType Registry was not initialized.
Response: Reload the WmTN package.
TRNSERV.000019.000061 An error occurred when constructing the XML Document object

Cause: A document object could not be constructed from the XML. See the nested exception for details.
TRNSERV.000019.000062 Recognition failed.

Cause: Unable to recognize document. See next message for details.
Response: Take appropriate action to resolve the problem described in the next message.
TRNSERV.000019.000063 There is not enough space on TSpace storage system to store the content of this large document
Cause: The disk partition used for temporary storage of large documents is full.
Response: Either change the value of the tn.tspace.location property, or increase the size of this disk partition.
TRNSERV.000019.000065 Unknown datatype encountered transforming attribute for FFDocType <docTypeName>

Cause: The attribute value supplied in the pipeline for the flat file document is not a String.
Response: Correct the document gateway service that puts this value in the pipeline. The attribute value must
be a String.
TRNSERV.000019.000066 FFDocType <docTypeName> encountered an unknown datatype while applying the

<transformation ID> transformation to the "<attributeName>" attribute.
Cause: The attribute value supplied in the pipeline for the flat file document is not a String.
Response: Correct the document gateway service that puts this value in the pipeline. The attribute value must
be a String.
TRNSERV.000019.000067 The <attributeName> attribute is required by the <docTypeName> doctype. It is missing.

Cause: The attribute that is required for the flat file TN document type is missing from the pipeline.
Response: Correct the document gateway service that supplies the value for this attribute.

TRNSERV.000019.000068 FFDocType <docTypeName> encountered an error transforming an attribute.

Cause: The specified flat file document type extracts an attribute. Trading Networks encountered an error
while transforming the attribute value.
Response: Use the Trading Networks Console to verify that the Attribute Details for the TN document type are
correct. If they are, gather details about the error and contact webMethods Customer Care.
TRNSERV.000019.000069 FFDocType <docTypeName> encountered an error while applying the <transformationID>

transformation to the "<attributeName>" attribute: <exceptionMessage> : <stackTrace>
Cause: An error occurred while transforming the attribute value.
Response: Use the Trading Networks Console to verify that the Attribute Details for the TN document type are
correct. If they are, gather details about the error and contact webMethods Customer Care.
TRNSERV.000019.000070 FFDocType <docTypeName> encountered an error reading the document bytes.

Cause: Encountered a problem while processing the "ffdata" InputStream. See the full message for details.
TRNSERV.000019.000071 FFDocType <docTypeName> encountered an error reading the document bytes.

<exceptionMessage> : <stackTrace>
Cause: Encountered an exception while reading the "ffdata" InputStream. See the exception message and stack
trace for details.
Response: Verify that your document gateway service is not corrupting the "ffdata" InputStream. Resend the
document.
TRNSERV.000019.000072 Cannot unregister a built-in DocType Category: <categoryName>

Cause: The wm.tn.doctype:unregisterCategory service was passed the name of a built-in TN document type
category such as "XML" or "Flat file".
Response: Do not attempt to unregister a built-in category.
TRNSERV.000019.000079 Could not determine document sender.

Cause: The TN document type is configured to determine the document sender from the connected user, but
was unable to. See the full message for details.

TRNSERV.000019.000080 Could not determine document sender for doctype "<doctypeName>" because there is no
connected user.
was unable to, probably because there was no connected user.
Response: Determine why there is no connected user. Perhaps the document is being submitted from a
background thread.
TRNSERV.000019.000081 Could not get ProfileSummary for sender from connected user "<userName>"
was unable to. There was a connected user, but it does not have a partner profile.
Response: Create a partner profile for the user, or instruct the user to log in to your system with a valid partner
account.
TRNSERV.000019.000083 FFDocType <docTypeName> encountered an error reading the document bytes. Key "ffdata" is not
found in the pipeline
Cause: The "ffdata" InputStream is missing from the pipeline.
Response: Verify that your document gateway service is not dropping "ffdata" from the pipeline. Resend the
document.
TRNSERV.000019.000084 FFDocType <doctypeName> encountered an error reading the content of document <docID>
Cause: This is a large document, and Trading Networks encountered an error while reading the document's
InputStream from Tspace (hard disk drive space). See the nested exception for details.
TRNSERV.000019.000085 Error turning stream into bytes (docid=<docID>)

Cause: The document has an unsupported encoding. See the server log or view this document in Transaction
Analysis to see details about the error.
Response: Request that the document be resent with a supported encoding.
TRNSERV.000019.000086 Attribute transformation '<transformationFunction>' has no data

Cause: The attribute referenced by this transformation is null.
Response: Gather details about this error, and contact webMethods Customer Care.
TRNSERV.000019.000088 A corrupted document was encountered in recognition: <exceptionMessage>

Cause: Trading Networks received an XML document that was not well formed.
Response: Correct the original document and resend.

TRNSERV.000019.000090 Unable to load the following TN doc types <doctypeList> because their classes are not found in the
classpath. Either correct the classpath to include the required classes and restart the Server or if you no longer use these
doc types, you can delete them using wm.tn.doctype:delete service and then restart the Server.
Cause: There are TN document types in your database that are not on your classpath.
Response: You can correct the classpath to include the required classes, and restart the server. Or, if you no
longer use these TN document types, you can delete them using the wm.tn.doctype:delete service, and then
restart the server.
TRNSERV.000019.000093 This operation is not supported for MissingDocType.

Cause: An attempt was made to create a BizDocEnvelope from the MissingDocType class.
Response: If you have written code that creates instances of (No Suggestions), ensure that it does not attempt to
create a BizDocEnvelope from the MissingDocType class.
TRNSERV.000019.000094 ERROR: The Java class for this document type was not found
Cause: The JAR file that holds the TN document type editor was not found.
Response: If you are viewing a TN XML or flat file document type, make sure the tnclient.jar file is in the
webMethods6\IntegrationServer\packages\WmTN\code\jars directory on the Integration Server's file
system. If you are viewing another category of TN document type, make sure the JAR file with that TN
document type's editor is in the IntegrationServer\packages\WmTN\code\jars directory.
TRNSERV.000020.000001 Attribute transform for <attributeID> of doctype <doctypeID> failed to produce a value. The
transform function was <xformFunction>, the first original value was <value>
Cause: The data type of the attribute might not match the type of the data extracted from the document.
Response: Make sure the data type of the attribute matches the type of the data extracted from the document. If
this is an XML TN document type, make sure the XQL query that extracts the attribute is correct.
TRNSERV.000020.000002 Attribute query for <attributeID> of doctype <doctypeID> failed to produce a result. The document
may not be complete. The query was: <xqlQuery>
Cause: The XQL query for the attribute did not return a value.
Response: Adjust the XQL query, if needed.
TRNSERV.000020.000003 Attribute query for <attributeID> of doctype <doctypeID> generated an exception. The original
exception message is: <exceptionMessage>
Cause: There is either a problem with the document or with the query.
Response: Examine the document to see if it is well-formed XML. Correct and resubmit if needed. Examine the
query to determine that it is valid. Adjust the query if needed.

TRNSERV.000020.000004 Unable to get XML content for corrupted doc <docID>. The original exception message is:
<exceptionMessage>
Cause: The document is corrupt.
Response: Correct the document and resubmit it.
TRNSERV.000020.000005 Transform for <attributeID> of doctype <doctypeID> generated an exception. The transform
function was <xformFunction>. The original exception message is: <exceptionMessage>
Cause: There is either a problem with the document or with the query.
Response: Examine the document to see if it is well-formed XML. Correct and resubmit if needed. Examine the
query to determine that it is valid. Adjust the query if needed.
TRNSERV.000020.000006 Transform for <attributeID> of doctype <doctypeID> failed to produce a value. The transform
function was <xformFunction>, the first original value was <value>
Cause: Perhaps the data type of the attribute does not match the type of the data extracted from the document.
Response: Make sure the data extracted from the document is of the same type as the attribute. If this is an XML
TN document type, make sure the XQL query that extracts the attribute is correct.
TRNSERV.000020.000007 Envelope query for <attributeID> of doctype <doctypeID> failed to produce a result. The document
may not be complete. The query was: <xqlQuery>
Cause: The XQL query for the attribute did not return a value.
Response: Adjust the XQL query, if needed.
TRNSERV.000020.000008 Envelope query for <attributeID> of doctype <doctypeID> generated an exception. The original
exception message is: <exceptionMessage>
Cause: The document might be corrupt.
TRNSERV.000020.000009 There was an error in trying to get XML header information (DOCTYPE and DTD). The document
(<docID>) is probably not valid XML.
Cause: The document is probably not well-formed XML.
TRNSERV.000020.000010 There was an error in trying to get XML header information (DOCTYPE and DTD). The document
(<docID>) is probably not valid XML. The original exception message is: <exceptionMessage>
Cause: The document is probably not well-formed XML.

TRNSERV.000020.000011 XQL query <xqlQuery> failed recognizing document <docID>. The document is probably not valid
XML. The original exception message is: <exceptionMessage>.
Cause: The document is probably not well-formed XML. See the exception message for details.
TRNSERV.000020.000013 No bizdoc supplied to lookup validation schema

Cause: The wm.tn.doc.xml:getRecordBlueprint service was invoked with no BizDocEnvelope in the pipeline.
Response: Supply a BizDocEnvelope when invoking the wm.tn.doc.xml:getRecordBlueprint service.
TRNSERV.000020.000014 Non-XML bizdoc supplied to lookup validation schema

Cause: The BizDocEnvelope passed to the wm.tn.doc.xml:getRecordBlueprint service is not an XML document
type.
Response: Supply a BizDocEnvelope that matches an XML TN document type when invoking the
wm.tn.doc.xml:getRecordBlueprint service.
TRNSERV.000020.000015 No bizdoc ID supplied for testing validation

Cause: The wm.tn.doc.xml:testValidate service was invoked with no internal document ID in the pipeline.
Response: Supply an internal document ID (docID) when invoking the wm.tn.doc.xml:testValidate service.
TRNSERV.000020.000016 No such bizdoc: <docID>

Cause: The wm.tn.doc.xml:testValidate service was invoked with an invalid internal document ID in the
pipeline.
Response: Supply a valid internal document ID (decide) when invoking the wm.tn.doc.xml:testValidate
service.
TRNSERV.000020.000017 Required attribute is missing

Cause: An attribute is defined as required by the document type, but the document that matched the document
type did not contain this attribute.
Response: Either change the document type so that this attribute is no longer required, or instruct the
document sender to supply a value for the attribute.

TRNSERV.000020.000018 The <attribName> attribute is required by the <docTypeName> doctype. The query <xqlQuery> did
not return any results
Cause: An attribute is defined as required by the document type, but the document that matched the document
type did not contain this attribute.
Response: Either change the document type so that this attribute is no longer required, or instruct the
document sender to supply a value for the attribute.
TRNSERV.000020.000019 Attribute transformation for <attribName> of doctype <docTypeName> generated an exception.

The query is <xqlQuery>. The original exception message is: <message>.
Cause: Encountered an Exception.
Response: If the document is corrupt, notify the document sender.
TRNSERV.000021.000005 Error(s) encountered in WmTN initialization: <exceptionMessage>

Cause: Encountered an exception while Trading Networks was initializing. See the exception message for
details.
TRNSERV.000021.000006 Error initializing the datastore: <exceptionMessage>

Cause: Encountered an exception in the database or database driver while Trading Networks was initializing.
See the exception message for details.
TRNSERV.000021.000013 The wm.tn.access:getConsoleRestrictions service has been deleted, renamed or replaced.

Aborting Trading Networks initialization.", "Please restore the original version of this service.
Cause: wm.tn.access:getConsoleRestrictions has been tampered with.
Response: Restore the original version of this service.
TRNSERV.000021.000014 Error filling BizDocAttributeStore cache

Cause: Encountered an error while reading the document attributes from the database during startup.
Response: An exception was written to the server log. Take appropriate action to resolve the problem described
in the exception.
TRNSERV.000021.000018 Unable to register content types with FlatFile Content Handler. The WmFlatFile package seems to
be disabled. WmFlatFile Package should be enabled in order to use Flat File capabilities in TradingNetworks.
Cause: The WmFlatFile package is disabled.
Response: Enable the WmFlatFile package.

TRNSERV.000022.000001 <variable> is required.

Cause: A service was invoked, and a required input variable was not supplied.
Response: Supply a value for the specified variable.
TRNSERV.000022.000002 Unable to save queue "<queueName>"

Cause: Attempt to insert queue information into the Trading Networks database failed.
Response: Ask your database administrator (DBA) to examine the database logs to determine the cause of the
problem.
TRNSERV.000022.000003 Cannot reassign tasks to a private queue.

Cause: Each partner might have its own private queue. Private queues are defined in the profile for a partner.
A private queue can contain only tasks for the partner identified by the profile; private queues cannot contain
tasks from other partners.
Response: You can reassign these tasks to a public queue.
TRNSERV.000022.000004 Unable to remove queue "<queueName>"

Cause: Attempt to delete queue information from the Trading Networks database failed.
problem.
TRNSERV.000022.000005 Unable to update queue "<queueName>"

Cause: Attempt to update queue information in the Trading Networks database failed.
problem.
TRNSERV.000022.000006 The queue cannot be deleted because there is data that depends on it.
Cause: The queue cannot be deleted for one or more of the following reasons: 1) There might be tasks currently
on the queue. 2) There are partner profiles and/or processing rules that refer to the queue.
A list of objects that depend on the queue follow this message.
Response: Take one or more of the following actions: 1) If there are tasks on the queue, place it in a DRAINING
state so that the queue will empty. After all tasks in the queue are processed, you can delete the queue. 2) If
there are profiles and/or processing rules that refer to the queue, remove those references. After you remove
the references, you can delete the queue.

TRNSERV.000022.000007 There are <number> tasks on the queue.
Cause: The queue cannot be removed because it has tasks on it.
Response: Place the queue in a DRAINING state so that the queue will empty. After the tasks in the queue have
been processed, you can delete it.
TRNSERV.000022.000008 There are <number> partner profiles that refer to the queue.
Cause: The queue cannot be removed because one or more partner profiles refer to it.
Response: This message is followed by a list of partners whose profiles refer to the queue. Modify these profiles
so they no longer refer to the queue being removed. After you remove the references, you can delete the
queue.
TRNSERV.000022.000009 There are <number> processing rules that refer to the queue.
Cause: The queue cannot be removed because one or more processing rules refer to it.
Response: This message is followed by a list of processing rules that refer to the queue. Modify these
processing rules so they no longer refer to the queue being removed. After you remove the references, you can
delete the queue.
TRNSERV.000022.000012 There is no task with the supplied ID (<taskID>).

Cause: The wm.tn.queuing:updateQueuedTask service was supplied an invalid task ID.
TRNSERV.000022.000013 updateQueuedTask may only be invoked for tasks that are currently being processed from a
DeliveryQueue. This task (<taskID>) has a status of <status>.
Cause: You attempted to run the wm.tn.queuing:updateQueuedTask service for a task; however, you did not
first invoke the wm.tn.queuing:getQueuedTask service.
Response: Be sure to use the wm.tn.queuing:getQueuedTask service to retrieve a task from a queue.
TRNSERV.000022.000018 Attempted to update a DeliveryQueue that has not been registered (queue name=<queue>).
Cause: The specified queue does not exist.
Response: Either supply a valid queue name or use the Trading Networks Console to define the delivery
queue.
TRNSERV.000022.000019 status must be "success" or "fail". <status> was supplied.

Cause: The wm.tn.queuing:updateQueuedTask service was supplied an invalid status.

TRNSERV.000022.000020 Attempted to remove a DeliveryQueue that has not been registered (queue name=<queue>).
Cause: The specified queue does not exist.
Response: Supply a valid queue name.
TRNSERV.000022.000021 Unable to decode TypeData for a DeliveryJob (ID=<id>) while dequeuing from <queue>
TRNSERV.000022.000023 The scheduled delivery date/time is in the past.

Cause: Trading Networks cannot schedule delivery to run in the past.
Response: Supply a future date and time.
TRNSERV.000022.000024 The delivery schedule is empty. It has been ignored.

Cause: The delivery queue does not have a delivery schedule. The operation has failed.
Response: If you receive this error while invoking a service, make sure that you are supplying a valid
DeliveryQueue object that contains a DeliverySchedule. If you receive this error while using the Trading
Networks Console, contact webMethods Customer Care.
TRNSERV.000022.000025 Delivery schedule dates must be in the format "YYYY/MM/DD" and times must be in the format
"hh:mm:ss"
Cause: A date and/or time in the delivery schedule is invalid.
Response: All dates and times in the delivery schedule must be in the specified formats.
TRNSERV.000022.000027 Unable to schedule delivery for queue "<queue>". The pipeline for the delivery service does not
contain "queue"
Cause: The variable "queue" was not supplied in the pipeline.
Response: Supply the name of the delivery queue.
TRNSERV.000022.000028 The delivery schedule has no schedule type. It has been ignored.
Cause: The delivery schedule must have a type of "repeat", "complex", or "once".
Response: Set the type on the delivery schedule to a valid value.

TRNSERV.000022.000037 Scheduled delivery failed. No more retries.
Cause: The final attempt to delivery a document failed.
Response: See the message TRNSERV.000022.000038 for full details.
TRNSERV.000022.000038 Scheduled delivery of document <docID> failed. No more retries. <errorMsg>

Cause: The final attempt to deliver a document failed.
Response: See the error message for details. You might need to contact your trading partner.
TRNSERV.000022.000039 The queue "<queue>" has a status of "<status>". It is not accepting documents. This document will
not be delivered.
Cause: Attempted to route a document to a delivery queue that is either disabled or draining. Queues in either
of these statuses cannot accept documents.
Response: Either change the status of this queue or route the document to a different queue.
TRNSERV.000022.000040 Unable to validate private queue/partner relationship (id=<partnerID>) because the partner could
not be retrieved. The queue has been saved with a "disabled" status.
Cause: You can only create a private queue for a partner that has an active profile. The specified partnerID
identifies a partner that does not exist or whose profile is not active.
Response: Perform one of the following actions: 1) Specify a different queue. 2) If the profile is not active,
change its status to active.
TRNSERV.000022.000041 Private queue "<queue>" has a status of "<status>", but the partner's profile is not active. The
queue has been saved with a "disabled" status. To be able to enable the queue, you must first activate the profile.
Cause: Trading Networks attempted to route a document to a private queue that is defined for a profile that is
not active. Trading Networks can only route documents to private queues belonging to active partners; it
cannot route documents to private queues of inactive partners. Trading Networks has disabled the queue.
Response: Enable the partner by changing the profile status to Active. Then enable the partner's private queue.
TRNSERV.000022.000042 Delivery not scheduled from queue.

Cause: See full message that follows for details.

TRNSERV.000022.000044 Document was not queued for delivery on queue <queue>. The receiver's profile was not found.
(receiverID=<partnerID>).
Cause: A processing rule indicated that the document should be delivered to a queue that is associated with a
receiver. However, there is no profile for the receiver.
Response: Use the Transaction Analysis screen of the Trading Networks Console to determine who the
intended receiver is. If the receiver is valid but does not have a profile, create a partner profile for the receiver.
If the receiver is not valid, notify the document sender that the receiver information in the document is
incorrect.
TRNSERV.000022.000045 Document was not queued for delivery on queue <queue>. The receiver is not active
(receiverID=<partnerID>).
Cause: A processing rule indicated that the document should be delivered to a queue that is associated with a
receiver. However, the receiver's profile is not active. Trading Networks can only route documents to active
partners.
Response: Enable the partner by changing the profile status to Active. Then enable the partner's private queue.
TRNSERV.000022.000046 The queue "<queue>" does not exist.

Cause: The wm.tn.queuing:deliverBatch service was supplied an invalid queue name.
Response: Supply the name of an existing queue.
TRNSERV.000022.000048 The scheduled <date> is invalid. Format must be YYYY/MM/DD.

Response: Supply a valid date.
TRNSERV.000022.000049 The scheduled <time> is invalid. Format must be hh:mm:ss

Response: Supply a valid time.
TRNSERV.000022.000056 Interval is required.

Cause: An interval must be specified for repeating tasks.
Response: Supply an interval value.
TRNSERV.000022.000057 Interval is not a valid integer.

Response: Supply an integer greater than zero.
TRNSERV.000022.000058 Interval must be greater than zero.

Response: Supply an integer greater than zero.

TRNSERV.000022.000059 End date/time is in the past.
Response: Supply a future end date and time.
TRNSERV.000022.000060 End date/time is before start date/time.

Response: Ensure that the end date and time are later than the start date and time.
TRNSERV.000022.000061 Could not construct a valid timestamp from this schedule. Dates must be in YYYY/MM/DD format
and times must be in hh:mm:ss format.
Response: Ensure that the dates and times are formatted correctly
TRNSERV.000022.000062 A queue with this name already exists.

Response: Select another name for the queue.
TRNSERV.000022.000063 There is a task on the queue (task id=<taskID>).

Cause: The queue cannot be removed because it has tasks on it.
Response: Place the queue in a DRAINING state so that the queue will empty. After the tasks in the queue have
been processed, you can delete it.
TRNSERV.000022.000064 The profile for <partnerName> refers to the queue (partner id=<partnerID>).
Cause: The queue cannot be removed because one or more partner profiles refer to it.
Response: This message is followed by a list of partners whose profiles refer to the queue. Modify these profiles
so they no longer refer to the queue being removed. After you remove the references, you can delete the
queue.
TRNSERV.000022.000065 The <ruleName> processing rule refers to the queue.

Cause: The queue cannot be removed because one or more processing rules refer to it.
Response: This message is followed by a list of processing rules that refer to the queue. Modify these
processing rules so they no longer refer to the queue being removed. After you remove the references, you can
delete the queue.
TRNSERV.000022.000066 If an end time is supplied, an end date must also be supplied.

Response: Supply an end date.
TRNSERV.000023.000001 Invalid or missing page number.

Cause: The wm.tn.enumerate:nth service was not supplied a value for the input variable pageNum.
Response: Supply a value for the input variable pageNum.

TRNSERV.000023.000002 id is required.
Cause: The wm.tn.enumerate:nth service was not supplied a value for the input variable id.
Response: Supply a value for the input variable id.
TRNSERV.000023.000003 confirm is required; specify yes/no.

Cause: The wm.tn.enumerate:deleteQueryResults service was not supplied a value for the input variable
confirm.
Response: Supply a value of "yes" or "no" for the input variable confirm.
TRNSERV.000023.000004 Invalid time interval <interval> for query.

Cause: An invalid value was supplied for the interval field.
TRNSERV.000023.000005 Unknown attribute ID: <id>.

Cause: The wm.tn.query:createDocumentQuery service was supplied an invalid attribute ID.
TRNSERV.000023.000006 Unknown attribute name: <name>.

Cause: The wm.tn.query:createDocumentQuery service was supplied an invalid attribute name.
TRNSERV.000023.000007 Unknown op: <operator>.

Cause: The wm.tn.query:createDocumentQuery service was supplied an invalid operator.
TRNSERV.000023.000008 Invalid entry type <type> for event.

Cause: The wm.tn.query:createEventQuery service was supplied an invalid value for the input variable
entryType.
TRNSERV.000023.000009 Invalid time interval <interval> for query

Cause: The wm.tn.query:createEventQuery service was supplied an invalid value for the input variable
timeInterval.

TRNSERV.000023.000010 Invalid timeCreated interval <timeCreated> for query
Cause: The wm.tn.query:createTaskQuery service was supplied an invalid value for the input variable
timeCreated.
TRNSERV.000023.000012 Requested page is not available

Cause: Attempted to read beyond the end of the query results.
TRNSERV.000023.000013 Unable to retrieve page. Operation timed out.

Cause: The Integration Server might be busy doing other work.
Response: Attempt to retrieve the page again, or re-execute the query.
TRNSERV.000023.000014 Query execution failed.

Cause: An exception was thrown while executing a database query.
the exception.
TRNSERV.000023.000015 External ID value is required.

Cause: You created a profile query that specifies an externalIDType, but did not specify an externalIDValue.
Response: Supply a valid value for the externalIDValue input variable to the createProfileQuery service.
TRNSERV.000023.000016 fieldId[<idType>] is null or empty.

Cause: You created a profile query that specifies an externalIDValue, but did not specify an externalIDType.
Response: Supply a valid value for the externalIDType input variable to the createProfileQuery service.
TRNSERV.000024.000000 Unable to construct mime message

Cause: Source data used to construct the MIME message is not a properly formed MIME message.
Response: Check the input data. Fix the message to conform to the MIME standard.
TRNSERV.000024.000002 Unable to read mime message data source

Cause: Problem reading from input data source.
Response: Check input data source for errors.

TRNSERV.000024.000003 Unable to construct mime message

TRNSERV.000024.000004 Unable to handle data of type: <msgType>

Cause: Attempted to add a message of type <msgType> to a multi-part MIME message. This type cannot be
part of a multi-part MIME message.
Response: Check the message type being added to the multi-part MIME message. It must be either a multi-part
MIME or a MIME message.
TRNSERV.000024.000005 Unable to handle null data source

Cause: Cannot construct a MIME message from a null data source.
Response: Pass a non-null data source to the service.
TRNSERV.000024.000008 Can not replace existing body part

Cause: Attempted to add a MIME body part to a MIME message that already contains a body part.
Response: Set the input flag 'replace' on the wm.tn.mime:addBodyPart service to 'yes'. This will replace the
existing body part with the new one. OR set the flag 'multipart' to 'yes'. This will append the new body part to
the existing one, making the message a multi-part MIME message.
TRNSERV.000024.000011 getBodyPart not supported on non multipart message

Cause: Attempted to get a mime body part other than zero from a non-multipart MIME message.
Response: The number '0' (zero) is the only valid value for the input parameter 'index' of the
wm.tn.mime:getBodyPartHeader and wm.tn.mime:getBodyPartContent services when the input MIME
message is not a multi-part MIME message.
TRNSERV.000024.000024 Unable to determine Content type

Cause: MIME message does not contain content-type information. Message is improperly formed
Response: Inform the message sender of error.
TRNSERV.000024.000025 Unable to get boundary for multipart mime message

Cause: MIME message does not contain message boundary information. Message is improperly formed.

TRNSERV.000024.000031 Unable to determine content-type


Response: Please check the input data. Fix the message to conform to the MIME standard.
TRNSERV.000024.000034 Unable to parse Content-Type string

TRNSERV.000024.000035 Cannot write message to outputStream, content is null

Cause: Message contained no data.
Response: Construct MIME message with valid input data.
TRNSERV.000024.000036 Operation can only be performed on parsed message.

Cause: The size of a MIME body part can only be determined for MIME messages that are parsed from a
complete message. The size of each part cannot be determined when composing a MIME message.
Response: Do not attempt to obtain the size of a MIME body part that is part of a message that is being
composed.
TRNSERV.000024.000037 Unable to parse 'Content-Disposition'

Cause: MIME message does not contain content-disposition information. Message is improperly formed
TRNSERV.000024.000039 Unable to get content.

Cause: Error occurred reading message content.

TRNSERV.000024.000040 Message Digest Algorithm '<algorithm>' not supported.

Cause: User has specified an invalid value for the 'digestAlgorithm' input parameter of the
wm.tn.mime:setDigestAlgorithm service.
Response: Specify a valid value of either "MD5" or "SHA-1" for the 'digestAlgorithm' input parameter.
TRNSERV.000024.000041 Cannot set header for message that is not multipart. Either specify subType or set header using
addBodyPart
Cause: When calling the wm.tn.mime:createMimeData service, cannot set header for message that is not
multipart.
Response: Specify a value for subType, which will create a multi-part mime message. Alternately, for a MIME
message that is not multi-part, headers can be specified when calling the wm.tn.mime:addBodyPart service.
TRNSERV.000024.000101 Parameter input must be an InputStream

Cause: Input parameter 'input' must be an InputStream object.
Response: Pass in an InputStream object.
TRNSERV.000024.000103 content cannot be null when adding a mime body part

Cause: Content cannot be null when adding a MIME body part
Response: Specify a valid content.
TRNSERV.000024.000104 Unable to handle content of type <contentType>

Cause: Input parameter 'content' must be one of the following types: InputStream, byte array, or MIME
message.
Response: Specify the value of the 'content' input parameter to one of the three allowed types.
TRNSERV.000024.000105 Parameter index must be of type int

Cause: Specified a non-integer value for the 'index' input parameter when attempting to obtain a MIME body
part.
Response: Check the value of the input parameter 'index' to ensure it is a non-negative integer.
TRNSERV.000024.000106 outputStream required

Cause: Calls to the wm.tn.mime:writeToStream service require an OutputStream object to be specified for the
'outputStream' parameter.
Response: Pass an OutputStream object to the wm.tn.mime:writeToStream service.

TRNSERV.000024.000107 Unknown digest algorithm <algorithm>
Cause: User has specified an invalid value for the 'digestAlgorithm' input parameter.
TRNSERV.000024.000108 Parameter mimeData cannot be null

Cause: The 'mimeData' input parameter has a null value.
Response: Specify a valid value for the 'mimeData' parameter.
TRNSERV.000024.000109 Parameter headerName cannot be null

Cause: The headerName parameter cannot be null.
Response: Specify
TRNSERV.000024.000112 A digest algorithm must be specified when creating a message digest.

Cause: User has specified an invalid value for the 'digestAlgorithm' input parameter.
TRNSERV.000024.000200 Cannot recognize certificates

Cause: Cannot recognize certificates.
Response: Certificates must be passed in as byte array objects.
TRNSERV.000024.000201 Cannot recognize certifcate

Response: Check certificate format. The certificates must be a DER encoded ASN.1 format.
TRNSERV.000024.000202 Cannot recognize certificate at index <index>

Cause: Cannot recognize certificate in chain at index: <index>.
Response: Check certificate format. The certificate must be a DER encoded ASN.1 format.
TRNSERV.000024.000203 Certificate at index <index> is not valid

Cause: Cannot recognize certificate at index: <index>
Response: Certificate must be passed in as byte array object.

TRNSERV.000024.000204 Error attempting to parse message contents

TRNSERV.000024.000205 Error attempting to read from message source

TRNSERV.000024.000206 Recipient certificate is not valid

TRNSERV.000024.000209 Cannot recognize recipient certificate at index <index>

Cause: Cannot recognize certificate at index: <index>.
Response: Certificate must be passed in as byte array object.
TRNSERV.000024.000210 Certificate format is invalid for recipient certificate at index <index>

TRNSERV.000024.000211 Specified keylength <length>, is not allowed

Cause: Invalid value specified for key length of RC2 encryption algorithm.
Response: Specify one of the allowed key length values: "40", "64", or "128".
TRNSERV.000024.000212 Specified algorithm `<algorithm>`, is not supported

Cause: Invalid encryption algorithm has been specified.
Response: Specify one of the supported encryption algorithms: "TripleDES", "RC2", or "DES".
TRNSERV.000024.000213 In getEncryptedMimeObject: Cannot handle datasource of type: <invalidType>

Cause: When trying to create an encrypted message, the 'mimeSrc' object must be a MimeData object.
Response: Pass in a MimeData object. MimeData objects are created using the wm.tn.mime:createMimeData
service.

TRNSERV.000024.000214 In getEncryptedMimeObject: Cannot handle null datasource
Cause: The 'mimeSrc' input parameter cannot be null.
Response: Specify a valid MimeData object in the 'mimeSrc' parameter.
TRNSERV.000024.000216 Unable to get signer's private key

Cause: Cannot recognize the private key.
Response: Check the supplied private key. It should be a DER encoded ASN.1 representation of an RSA private
key.
TRNSERV.000024.000217 Unable to get recipient certificate(s).

TRNSERV.000024.000218 Signer's certificate is not a valid data format

TRNSERV.000024.000219 Signer's certificate is not recognized

TRNSERV.000024.000220 Input parameter mimeSrc to service createSignedData cannot be of type <invalidType>. It should
be of type MimeData.
Cause: When trying to create a signed message, the 'mimeSrc' object must be a MimeData object.
service.
TRNSERV.000024.000221 Input parameter mimeSrc to service createSignedData cannot be null. It should be of type
MimeData.
Cause: When trying to create a signed message, the 'mimeSrc' object must be a MimeData object.
service.

TRNSERV.000024.000222 Unable to parse message

TRNSERV.000024.000223 Input parameter mimeSrc should be of type MimeData

Cause: The 'mimeSrc' object must be a MimeData object or an InputStream object.
Response: Pass in a MimeData or InputStream object. MimeData objects are created using the
wm.tn.mime:createMimeData service.
TRNSERV.000024.000224 Could not obtain message content

TRNSERV.000024.000225 Content is not of a recognized encryption type

Cause: Cannot process the encrypted message.
Response: Contact the message sender to
TRNSERV.000024.000226 Given certificate does not decrypt message

Cause: The message was not encrypted for the certificate that was passed in to the service.
Response: First validate that the correct certificate is being used to decrypt the message. Then, if the certificate
appears correct, contact the message sender to determine which certificate was actually used to create the
encrypted message.
TRNSERV.000024.000229 Cannot Process this object. Write this MimeData to stream, then process that stream.
Cause: Cannot process this object.
Response: Write this MimeData to stream, then process the stream.
TRNSERV.000024.000230 Input parameter mimeData must be a MimeData object

Cause: The 'mimeData' input parameter is not a MimeData object.
service.

TRNSERV.000024.000231 Message content is not certificates only data. Message could not be processed.
Cause: The message cannot be handled by the wm.tn.mime:processCertsOnlyData service.
Response: Use the wm.tn.mime:createMimeMessage service to determine if the message is signed or
encrypted. Then use either wm.tn.mime:processSignedData or wm.tn.mime:processEncryptedData as
appropriate.
TRNSERV.000024.000232 Input parameter mimeSrc must be a MimeData object

Cause: The 'mimeSrc' object must be a MimeData object.
service.
TRNSERV.000024.000233 Message content is not signed data. Message could not be processed
Cause: The message cannot be handled by the wm.tn.mime:processSignedData service.
appropriate.
TRNSERV.000024.000234 Signing key is not valid

Cause: The key used to sign the message is invalid.
TRNSERV.000024.000235 Unable to sign document

Cause: The key used to sign the message is invalid.
TRNSERV.000024.000236 Invalid signer certificate file information

Cause: The signer certificate chain is invalid.
Response: The signer certificate chain must be an array of certificates.
TRNSERV.000024.000237 Certificate at index <index> not in recognizable format


TRNSERV.000024.000238 Invalid certificate input at index <index>

TRNSERV.000024.000239 Signature could not be verified

Cause: The signature is invalid. The signature cannot be validated.
Response: Contact the message creator to determine what message was originally sent.
TRNSERV.000024.000240 Expired certificate chain

Cause: A certificate used to sign the message has expired.
Response: Notify the message creator that the certificates used to sign the message are invalid.
TRNSERV.000024.000241 Error in certificate chain

Cause: The certificate chain is invalid.
Response: Check certificate format. The certificates must be a DER encoded ASN.1 format. Check that the
certificates form a chain. If the chain consists of Cert A and Cert B, the issuer of Cert A should be the same as
the subject of Cert B.
TRNSERV.000024.000242 Untrusted certificate

Cause: The certificate used to sign the message is not signed by a trusted certificate authority. The signature is
otherwise correctly formed.
Response: The message should not be trusted because the certificate authority is not trusted. Add the certificate
authority to the trusted certificate authorities, or the message creator must use a certificate issued by a trusted
certificate authority to sign the message.
TRNSERV.000024.000244 Error using temporary storage space

Cause: An error occurred when using the temporary storage system.
Response: See the "Trading Networks User’s Guide" for more details. Additional details should be contained in
the exception message.
TRNSERV.000024.000245 Unable to parse Encrypted Content. Invalid encrypted data.

Cause: The message could not be decrypted.
Response: Check the server log for additional error information. The stack trace for this error should contain
additional information about why this message could not be decrypted.

TRNSERV.000024.000246 Unable to decrypt data.
Cause: The message could not be decrypted.
Response: Check the server log for additional error information. The stack trace for this error should contain
additional information about why this message could not be decrypted.
TRNSERV.000024.000247 Unable to parse Encrypted Content. Private key does not decrypt data.
Cause: The private key used to decrypt this message cannot decrypt the message.
Response: First validate that the correct private key is being used to decrypt the message. Then, if the private
key appears correct, contact the message sender to determine which certificate was used to create the
encrypted message.
TRNSERV.000024.000248 Unable to determine hash algorithm. Parameter micalg was null

TRNSERV.000024.000249 Unable to determine hash algorithm. Unknown micalg: <algorithm>

TRNSERV.000024.000250 Improperly formed multipart/signed message

TRNSERV.000024.000251 Cannot process body part of type <contentType>

Cause: Error occurred processing the message.
TRNSERV.000024.000252 Cannot process signed data with content type <contentType>

Cause: Message does not appear to be a signed message and so cannot be processed by the
wm.tn.mime:processSignedData service.
appropriate. Otherwise, obtain the message contents by using the wm.tn.mime:getBodyPartContent service.

TRNSERV.000024.000253 Unable to parse Content Type

TRNSERV.000024.000254 Unable to compute message digest using algorithm:<digestAlgorithm>

Cause: The digest algorithm is either invalid or is not a supported algorithm.
Response: Specify a supported algorithm. Valid values for the digest algorithm are: "SHA-1" or "MD5".
TRNSERV.000024.000255 Either 'profileAlias' or ('privKey','signerCert') are required

Cause: To properly execute, the service requires either a valid value for 'profileAlias' or a valid value for the
'privKey' and 'signerCert' input parameters.
Response: Specify a value for either 'profileAlias', or 'privKey' and 'signerCert'. See the "webMethods Trading
Networks Built-In Services Reference" for more details on this service.
TRNSERV.000024.000256 Either 'profileAlias' or ('privKey','recipientCert') are required

Cause: To properly execute, the service requires either a valid value for 'profileAlias' or a valid value for the
'privKey' and 'recipientCert' input parameters.
Response: Specify a value for either 'profileAlias', or 'privKey' and 'recipientCert'. See the "webMethods
Trading Networks Built-In Services Reference" for more details on this service.
TRNSERV.000024.000257 Algorithm <algorithmName> not supported

Cause: The message was encrypted using the <algorithmName> algorithm. Cannot decrypt messages
encrypted with this algorithm.
Response: Can decrypt messages that are encrypted with RC2, TripleDes, or DES algorithms only.
TRNSERV.000024.000258 Invalid RC2 parameter version: <versionNumber>

Cause: This version of the RC2 algorithm is unsupported or invalid. The RC2 algorithm is supported with 40,
64, or 128 bit keys.
Response: Contact the message sender to ensure that a supported RC2 key length is being used.
TRNSERV.000024.000300 No algorithm specified

Cause: Mandatory 'algorithm' input parameter contained no value.
Response: Specify a valid value for the 'algorithm' input parameter. Valid values are either "SHA-1" or "MD5".

TRNSERV.000024.000301 Specified algorithm <algorithmName>, not supported
Cause: The 'algorithm' Input parameter contained an invalid value.
Response: Specify a valid value for the 'algorithm' input parameter. Valid values are either "SHA-1" or "MD5".
TRNSERV.000024.000302 Security provider not found

Cause: An internal error occurred.
TRNSERV.000024.000303 Input to createMessageDigest must be byte[] or InputStream

Cause: The 'input' input parameter must be a byte array or InputStream object.
Response: Specify a byte array or InputStream for the 'input' input parameter.
TRNSERV.000024.000304 Parameter 'data' must be a byte[] or InputStream

Cause: The 'data' input parameter must be a byte array or InputStream object.
Response: Specify a byte array or InputStream for the 'input' input parameter.
TRNSERV.000024.000305 Parameter 'signerInfo' cannot be null

Cause: Mandatory 'signerInfo' input parameter must contain a value.
Response: Specify valid information for the 'signerInfo' input parameter.
TRNSERV.000024.000306 Unable to process 'signerInfo' at index <index>

Cause: An error occurred attempting to process the signerInfo at index <index>.
Response: The server error log will contain a stack trace with additional information about why this error
occurred.
TRNSERV.000024.000307 Invalid certificate chain

TRNSERV.000024.000308 Invalid certificate at index <index>


TRNSERV.000024.000309 Required parameter 'signatureStream' cannot be null.

Cause: Required 'signatureStream' parameter cannot be null.
Response: Pass an OutputStream object to the wm.tn.mime:sign service, in the 'signatureStream' parameter.
TRNSERV.000024.000310 Error occured reading input stream, cannot construct signature.

TRNSERV.000024.000311 Hash Algorithm <algorithmName> not supported for signer at index <index>
Cause: Hash Algorithm <algorithmName> not supported for signer at index <index>.
Response: Change the <algorithmName> at <index> to be one of the allowed algorithm names: "MD5" or "SHA-
1".
TRNSERV.000024.000312 Bad certificate. Unable to set signer certificates.

TRNSERV.000024.000313 Input parameter 'signature' cannot be null.

Cause: The 'signature' input parameter cannot be null.
Response: Pass the signature to verify into the service in the 'signature' input parameter. The 'signature' object
should be either a byte array or an InputStream object.
TRNSERV.000024.000314 Input parameter 'signature' must be a byte[] or InputStream

Cause: The 'signature' input parameter must be a byte[] or InputStream.
Response: The 'signature' input parameter must be a byte[] or InputStream.
TRNSERV.000024.000315 Input parameter 'data' required for verifying detached signature

Cause: The 'data' input parameter cannot be null.
Response: Pass the data to verify into the service in the 'data' input parameter. The 'data' object should be either
a byte array or an InputStream object.
TRNSERV.000024.000316 Input parameter 'data' must be a byte[] or InputStream

Cause: The 'data' input parameter must be a byte[] or InputStream.
Response: The 'data' input parameter must be a byte[] or InputStream.

TRNSERV.000024.000317 An error occured while attempting to verify the signature.
TRNSERV.000024.000318 Signature provided is not PKCS#7 SignedData

Cause: Signature provided is not PKCS#7 SignedData.
Response: The wm.tn.mime:verify service can verify PKCS#7 SignedData signature only.
TRNSERV.000024.000319 Input parameter 'outputStream' must be an OutputStream

Cause: The 'outputStream' input parameter must be an OutputStream.
Response: The 'outputStream' input parameter must be an OutputStream.
TRNSERV.000024.000320 Input contained no signer information when processed as <signatureType> type signature
Cause: The message is not properly signed.
Response: This message cannot be verified. Contact the message creator to determine why the message was not
properly formed.
TRNSERV.000024.000321 Parameter 'data' must be null when parameter detachedSignature equals false.
Cause: The 'data' parameter must be null when 'detachedSignature' parameter equals false.
Response: If the signature is detached, then set the 'detachedSignature' parameter to "true". Otherwise, do not
pass in a value for 'data'. The signed message should be passed in via the 'signature' input parameter.
TRNSERV.000024.000323 Certificate chain cannot be null

Cause: Certificate chain cannot be null.
Response: Specify a certificate chain to use to sign this message.
TRNSERV.000024.000324 Private key or keyAlias required

Cause: Private key or keyAlias required.
Response: Specify either a private key or key alias to use to sign this message.
TRNSERV.000024.000325 Unable to decode signed message. Verify that signature type specified (detached or implicit)
matches actual type.
Cause: Unable to decode signed message.
Response: Verify that signature type specified (detached or implicit) matches actual type.

TRNSERV.000024.000327 Unable to write message to outputStream.

Cause: Error occurred writing signed message.
Response: The server error log will contain a stack trace with additional information about why this error
occurred.
TRNSERV.000024.000328 Only one '<profileAlias>' can be specified in 'signerInfo'

Cause: When signing a message using a profile alias, you can only use one alias.
Response: Sign the message with only a single profile alias.
TRNSERV.000024.000400 Values are required for both input parameters type and id
Cause: Values are required for both 'type' and 'id' input parameters.
Response: Set the 'type' input parameter to "file" and the 'id' parameter to the name of the file that the
InputStream will read from.
TRNSERV.000024.000401 Input parameter type cannot be null

TRNSERV.000024.000402 Input parameter id cannot be null

TRNSERV.000024.000403 Unable to open SharedInputStream

Cause: An error occurred reading from the specified data source.
Response: Check that the specified data source exists. The IS error log should contain additional error
information.
TRNSERV.000024.000404 Value '<value>' for parameter type is not supported. Please select from allowed values.
Cause: The 'type' input parameter must be set to "file".
Response: The 'type' input parameter must be set to "file".

TRNSERV.000024.000500 No profile exists for profile alias '<profileName>'
Cause: No profile has been created with that name.
Response: Check to see that the PKI profile has been properly created. See the “webMethods Integration Server
Administrator's Guide” for more details.
TRNSERV.000024.000501 Parameter '<parameterName>' must not be null

Cause: The parameter named in <parameterName> does not exist in the pipeline and must be present.
Response: Specify a valid value for the parameter called <parameterName>.
TRNSERV.000024.000502 Service '<serviceName>' in package WmTNPKI not enabled

Cause: The WmTNPKI package is disabled.
Response: Ensure that the WmTNPKI package is installed and enabled.
TRNSERV.000025.000001 Cannot setIData for CertificateData: data can not be null

Cause: The setIData method on a CertificateData object was passed a null IData.
Response: If your code is calling CertificateData.setIData, supply a non-null IData object. If it is not your code
that is calling this method, contact webMethods Customer Care.
TRNSERV.000025.000002 Cannot setIData for CertificateData.

Cause: The setIData method on a CertificateData did not succeed.
Response: If the Integration Server logging is configured at logging level 4 or higher, the exception was written
to the server log. See the server log for details. Take the appropriate action to resolve the problem described in
the exception.
TRNSERV.000025.000003 Certificate provider Entrust/IAIK not found, can not convert byte[] to
java.security.cert.X509Certificate. Please check if entrust jar files are in the Integration Server's classpath.
Cause: The Entrust jar files are missing from the Integration Server's classpath.
Response: Place the Entrust jar files in the Integration Server's classpath. If you need assistance, call
TRNSERV.000025.000004 CertificateException encountered, can not convert byte[] to java.security.cert.X509Certificat.

Cause: Trading Networks encountered a certificateException when attempting to convert a byte array to a
java.security.cert.X509Certificat.
Response: If the Integration Server logging is configured at logging level 4 or higher, the exception was written
the exception.

TRNSERV.000025.000005 Cannot convert byte[][] to X509Certificate[], exception encountered at index

<zeroBasedIndexNum>
Cause: Trading Networks could not create a certificate chain from the bytes. Trading Networks encountered
the error at <zeroBasedIndexNum> certificate.
Response: Check the byte array to ensure that it is in the correct format.
TRNSERV.000025.000006 Cannot convert byte[] to java.security.PrivateKey.

Cause: Trading Networks could not create a private key object from bytes.
Response: Check the byte array to ensure that it is in the correct format.
TRNSERV.000025.000007 Cannot convert X509Certificate[] to byte[][], CertificateEncodingException encountered at index

<zeroBasedIndexNum>. Please verify that the certificate is valid.
Cause: The certificate chain is not valid.
Response: Provide a valid certificate chain.
TRNSERV.000025.000008 Cannot convert PKCS7 formatted byte[] into .der formatted byte[][].
Cause: The PKCS7- formatted bytes are not valid.
Response: Check the byte array to ensure that it is in the correct format. Provide a valid byte array.
TRNSERV.000025.000009 Cannot load certificate from null File. Please supply a valid File.
Cause: The supplied certificate file is null.
Response: Supply a non-null certificate file.
TRNSERV.000025.000010 Certificate provider Entrust/IAIK not found, can not load java.security.cert.X509Certificate from file
<filename>. Please check if entrust jar files are in the Integration Server's classpath.
Cause: The Entrust jar files are missing from the Integration Server's classpath.
Response: Place the Entrust jar files in the Integration Server's classpath. If you need assistance, call
TRNSERV.000025.000011 CertificateException encountered getting certificate from file <filename>.

Cause: CertificateException thrown while attempting to load certificates from the specified file.
Response: Check the certificate file to ensure that it is in the correct format.

TRNSERV.000025.000012 Cannot load private key from null File.
Cause: Trading Networks attempted to load the private key from a file; however, the file is null.
Response: Supply a non-null private key file.
TRNSERV.000025.000013 IOException encountered loading RSA private key from file <filename>.
Cause: IOException thrown while attempting to load a private key from the specified file.
Response: If the Integration Server logging is configured at logging level 4 or higher, a stack trace was written
the exception.
TRNSERV.000025.000014 InvalidKeyException encountered loading RSA private key from file <filename>.
Cause: InvalidKeyException thrown while attempting to load a private key from the specified file.
Response: Check the private key file to ensure that it is in the correct format.
TRNSERV.000025.000015 Cannot check if certificate is self-signed: certificate byte[] is null.

Cause: The supplied certificate byte array is null.
Response: Supply a non-null certificate byte array.
TRNSERV.000025.000016 Cannot check if certificate is self-signed: both subject and issuer are null.
Cause: The supplied certificate is not in a valid format. Both the subject and issuer are null.
Response: Supply a valid certificate.
TRNSERV.000025.000017 Cannot check if certificate is self-signed: certificate is null.

Cause: The supplied certificate is null.
Response: Supply a non-null certificate.
TRNSERV.000025.000018 Integration Server's certificate file <filename> not found.

Cause: Trading Networks could not find the specified file that contains the Integration Server's client
certificate.
Response: Specify a file that contains a client certificate for the Integration Server.
TRNSERV.000025.000019 Integration Server's CA certificate file <filename> not found.

Cause: Trading Networks could not find the specified file that contains the Integration Server's CA certificate.
Response: Specify a file that contains the Integration Server's CA certificate.

TRNSERV.000025.000020 IOException encountered in retrieving Integration Server's private key <filename>.

Cause: IOException thrown when Trading Networks was attempting to retrieve the Integration Server's
private key from the specified file.
the exception.
TRNSERV.000025.000021 InvalidKeyException encountered in retrieving Integration Server's private key <filename>

Cause: InvalidKeyException thrown when Trading Networks was attempting to retrieve the Integration
Server's private key from the specified file.
Response: Specify a file that contains a valid private key for the Integration Server.
TRNSERV.000025.000022 Certificate chain bytes cannot be null or zero length.

Cause: The supplied certificate chain bytes is either null or has a length of zero.
Response: Supply a valid certificate chain.
TRNSERV.000025.000023 Certificate chain contains only one non-self-signed certificate.

Cause: The certificate chain is not valid. The certificate chain contains only one certificate, and that certificate is
not self-signed. When you are not using a self-signed certificate, a certificate chain must include a certificate
and its corresponding CA certificate(s).
Response: Supply a valid certificate chain. That is a single self-signed certificate or a certificate and its
corresponding CA certificates.
TRNSERV.000025.000024 Certificate chain can not be verified by Entrust: <errorMessage>

Cause: Entrust could not verify the certificate chain.
to the server log. See the server log for details. Take appropriate action to resolve the problem.
TRNSERV.000025.000027 Cannot decide if sign/verify certificate is trusted, my enterprise is null.

Cause: Trading Networks cannot determine whether to trust the sign/verify certificate because there is no
Enterprise profile.
Response: Create an Enterprise profile.

TRNSERV.000025.000028 Cannot set sign/verify certificate for receiver my enterprise, CertificateException encountered
verifying if chain is trusted by Integration Server.
Cause: Before setting the sign/verify certificates that are specified in the Enterprise profile, Trading Networks
ensures that the Integration Server trusts the certificates. A CertificateException was thrown when
determining whether the Integration Server trusts the certificates.
to the server log. See the server log for details. Take appropriate action to resolve the problem.
TRNSERV.000025.000029 Cannot set sign/verify certificate for receiver my enterprise, certificate is not trusted by my
enterprise's Integration Server
Cause: Before setting the sign/verify certificate that is specified in the Enterprise profile, Trading Networks
ensures that the Integration Server trusts the certificate. The certificate supplied in the Enterprise profile is not
among the certificates that the Integration Server trusts.
Response: Add this certificate to the Integration Server's directory of trusted certificates.
TRNSERV.000025.000031 SQLException encountered in setting certificate data for partner <id>, error message is
<message>.
Cause: SQLException thrown when Trading Networks attempted to set the certificate data for the partner with
the specified partner ID.
to the server log. See the server log for details. Take appropriate action to resolve the problem described in the
exception.
TRNSERV.000025.000032 SQLException encountered in retrieving certificate data for partner <id>, error message is
<message>.
Cause: SQLException when Trading Networks attempted to retrieve the certificate data for the partner with the
specified partner ID.
the exception.
TRNSERV.000025.000035 Cannot setIData() for CertData: CertData is null.

Cause: The setIData method on a CertData object was passed a null IData.
Response: If your code is calling CertData.setIData, supply a non-null IData object. If it is not your code that is
calling this method, contact webMethods Customer Care.

TRNSERV.000025.000036 EXMLException encountered in CertData.setIData().

Cause: com.wm.app.tn.err.EXMLException was thrown in the setIData() method.
Response: If your code is calling CertData.setIData, check the server log for a stack trace. Take the appropriate
action to resolve the problem described in the exception. If it is not your code that is calling this method,
TRNSERV.000025.000037 Cannot get expiration date for node certificate.

Cause: The certificate does not have expiration date information.
Response: Ensure that the certificate is in a valid format.
TRNSERV.000025.000038 Cannot convert byte array to java.security.PrivateKey

Cause: Trading Networks could not convert the byte array because it is corrupted.
Response: Ensure that the byte array in the Private Key file is in a valid format.
TRNSERV.000025.000039 Cannot set illegal usage <certificateUsage> for CertData.

Cause: The CertData object contains a certificate usage that is not legal.
Response: Ensure the certificate usage in the CertData object is one of the following valid choices: "sign",
"decrypt", or "ssl".
TRNSERV.000025.000040 Cannot insert CertData into database, CertData is null.

Cause: The CertData object is null.
Response: Supply a non-null CertData object.
TRNSERV.000025.000041 Cannot insert CertData into database, data already exists for supplied owner=<ownerID,
partner=<partnerID> and usage=<certificateUsage>.
Cause: You attempted to add certificate information for the specified owner/partner/usage combination.
However, there is already certificate information for this owner/partner/usage combination in the Trading
Networks database.
Response: If you want to update the certificate information for the specified owner/partner/usage combination,
use the update operation instead of insert operation. Otherwise, specify a unique owner/partner/usage
combination that does not already exist in the Trading Networks database.
TRNSERV.000025.000042 Error inserting CertData into database, update row count is not 1.
Cause: Trading Networks encountered a database error when performing the insert operation.
to the server log. See the server log for details. Take the appropriate action to resolve the problem.

TRNSERV.000025.000043 Error inserting CertData into database, IOException encountered encoding data into binary format
Cause: Trading Networks encountered an error when performing the insert operation; an IOException was
thrown when encoding data into binary format.
TRNSERV.000025.000044 Error inserting CertData into database, SQLException encountered, error message is <message>.
Cause: SQLException thrown when Trading Networks was attempting to perform a database insert operation.
TRNSERV.000025.000045 Cannot update CertData, CertData is null.

Cause: Trading Networks was attempting to perform a database update operation to update certificate
information. However, the supplied CertData object that Trading Networks is to use to update the existing
certificate information is null. As a result, Trading Networks cannot perform the database update operation.
Response: Supply a non-null CertData object.
TRNSERV.000025.000046 Cannot update CertData, CertID is null.

Cause: Trading Networks is not able to update the certificate information because the supplied unique
identifier, CertID, is null.
Response: Supply a non-null CertID.
TRNSERV.000025.000047 Cannot update CertData, data exists for supplied owner/partner/usage with a different
CertId=<certID>.
Cause: You attempted to update certificate information for the specified owner/partner/usage combination.
However, the supplied CertID does not match CertID that Trading Networks has for this owner/partner/usage
combination.
Response: Retrieve the correct CertID for the owner/partner/usage combination from database, and issue the
request again. This time specify the correct CertID for the owner/partner/usage combination.
TRNSERV.000025.000048 Error encountered updating CertData when executing database operation, update count is not 1.
Cause: Trading Networks encountered a database error when performing the update operation.

TRNSERV.000025.000049 Error updating CertData, IOException encountered encoding data into binary format.
Cause: Trading Networks encountered an error when performing the update operation; an IOException was
thrown when encoding data into binary format.
TRNSERV.000025.000050 Error updating CertData, SQLException encountered, error message is <message>.

Cause: SQLException thrown when Trading Networks was attempting to perform a database update
operation.
TRNSERV.000025.000051 Cannot delete CertData, CertID is null.

Cause: Trading Networks is not able to delete the certificate information because the supplied unique
identifier, CertID, is null.
Response: Supply a non-null CertID.
TRNSERV.000025.000052 Error encountered deleting CertData when executing database operation, delete count is not 1.
Cause: Trading Networks encountered a database error when performing the delete operation.
TRNSERV.000025.000053 Error deleting CertData, SQLException encountered, error message is <message>,

Cause: SQLException thrown when Trading Networks was attempting to perform a database delete operation.
TRNSERV.000025.000054 Cannot construct new CertData from SecurityOps.getCertificateData().


TRNSERV.000025.000055 Error selecting CertData for ownerId=<ownerID>, partnerId=<parnterID>,
usage=<certificateUsage>, IOException encountered decoding bytes to IData.
Cause: When Trading Networks was attempting to select CertData for the owner/partner/usage combination,
an IOException was thrown when decoding bytes to IData.
TRNSERV.000025.000056 Error selecting CertData for ownerId=<ownerID>, partnerId=<partnerID>,

usage=<certificateUsage>, SQLException encountered, error message is <message>.
Cause: SQLException thrown when Trading Networks was attempting select CertData for the
owner/partner/usage combination.
TRNSERV.000025.000057 Cannot construct new CertData from SecurityOps.getCertificateDataByCertID().

TRNSERV.000025.000058 Error selecting CertData for CertId=<certID>, IOException encountered decoding bytes to IData.
Cause: When Trading Networks was attempting to select CertData with the specified CertID, an IOException
was thrown when decoding bytes to IData.
TRNSERV.000025.000059 Error selecting CertData for CertId=<certID>, SQLException encountered, error message is
<message>.
Cause: SQLException thrown when Trading Networks was attempting select CertData with the specified
CertID.
TRNSERV.000025.000060 Cannot construct new CertData from SecurityOps.getCertificateDataForOwner().


TRNSERV.000025.000061 Error selecting CertData for ownerId=<ownerID>, IOException encountered decoding bytes to
IData.
Cause: When Trading Networks was attempting to select CertData for the specified owner, an IOException
was thrown when decoding bytes to IData.
TRNSERV.000025.000062 Error selecting CertData for ownerId=<ownerID>, SQLException encountered, error message is
<message>.
Cause: SQLException thrown when Trading Networks was attempting select CertData for the specified owner.
TRNSERV.000025.000063 Cannot search certificate data, expiration date is null.

Cause: The certificate expiration date search criterion is null.
Response: Supply a valid certificate expiration date for this search criterion.
TRNSERV.000025.000064 Cannot construct new CertData from SecurityOps.getCertificateDataForUpdate().

TRNSERV.000025.000065 Error selecting CertData for ownerId=<ownerID>, and expDate=<certificateExpirationDate>,

IOException encountered decoding bytes to IData.
Cause: When Trading Networks was attempting to select CertData for the specified owner and with the
specified expiration date, an IOException was thrown when decoding bytes to IData.
TRNSERV.000025.000066 Error selecting CertData for ownerId=<ownerID>, and expDate=<certificateExpirationDate>,

SQLException encountered, error message is <message>.
Cause: SQLException thrown when Trading Networks was attempting select CertData for the specified owner
and with the specified expiration date.

TRNSERV.000025.000067 Cannot construct new CertData from SecurityOps.getCertificateDataForPartnerAndUsage().
TRNSERV.000025.000068 Error selecting CertData for partnerId=<partnerID>, usage=<certificateUsage>, IOException

encountered decoding bytes to IData.
Cause: When Trading Networks was attempting to select CertData for the specified partner and with the
specified certificate usage, an IOException was thrown when decoding bytes to IData.
TRNSERV.000025.000069 Error selecting CertData for ownerId=<ownerID>, usage=<certificateUsage>, SQLException

encountered, error message is <message>.
Cause: SQLException thrown when Trading Networks was attempting select CertData for the specified partner
and with the specified certificate usage.
TRNSERV.000025.000070 Cannot get profile store or profile summary list, certificate migration can not be performed.
Cause: An exception was thrown while retrieving profile data.
TRNSERV.000025.000071 Cannot get partner's (<partnerID>) profile data, skip migrating this partner's certificate set
Cause: Trading Networks was not able to find profile data for the partner with the specified partner ID. As a
result, Trading Networks cannot migrate this partners certificate set.
TRNSERV.000025.000074 Error loading partner's (<partnerID>) certificate, skip migrating this partner's certificate set
Cause: An exception was thrown loading certificate data for the partner with the specified partner ID. As a
result, Trading Networks cannot migrate this partner's certificate set.

TRNSERV.000025.000075 Cannot migrate partner's (<partnerID>) certificate set: null certificate

Cause: When Trading Networks was attempting to migrate the specified partner's certificate set, it encountered
a null certificate. As a result, Trading Networks cannot migrate the certificate set.
Response: Supply a valid, non-null certificate.
TRNSERV.000025.000077 Error loading partner's (<partnerID>) CACertificate, skip migrating this partner's certificate set
Cause: An exception was thrown loading certificate data for the partner with the specified partner ID. As a
TRNSERV.000025.000078 Cannot migrate partner's (<partnerID>) certificate set: null CACertificate

Cause: When Trading Networks was attempting to migrate the specified partner's certificate set, it encountered
a null CA certificate. As a result, Trading Networks cannot migrate the certificate set.
Response: Supply a valid CA certificate.
TRNSERV.000025.000079 Error loading partner's (<partnerID>) private key, skip migrating this partner's certificate set
Cause: An exception was thrown loading the private key for the partner with the specified partner ID. As a
TRNSERV.000025.000080 Cannot migrate partner's (<partnerID>) certificate set: null private key
Cause: Private key is null.
When Trading Networks was attempting to migrate the specified partner's certificate set, it encountered a null
private key. As a result, Trading Networks cannot migrate the certificate set.
TRNSERV.000025.000081 Error adding partner's (TN partner ID <partnerID>, Integration Server user ID <userName>) verify
certificate to TN database, skip migrating this partner's verify certificate set
Cause: An exception was thrown while attempting to add the verify certificate to the database. As a result,
Trading Networks cannot migrate this partner's verify certificate set.

TRNSERV.000025.000082 Found null node certificate for CertId=<certID> in migration.
Cause: When Trading Networks cannot migrate the certificate with the specified CertID because the node
certificate is null.
Response: Supply a valid certificate.
TRNSERV.000025.000083 IOException encountered in migration, CertID=<certID>.

Cause: IOException thrown when Trading Networks attempted to migrate the certificate with the specified
CertID.
TRNSERV.000025.000084 Error duplicating sign cert data to ssl cert data for owner=<ownerID>, partner=<partnerID>.
TRNSERV.000025.000085 Cannot migrate certificate information. Cannot get current Trading Networks version from
database.
Cause: Trading Networks cannot migrate certificate information because it cannot determine the Trading
Networks version. The database information is not up-to-date or the database is not running.
Response: Ensure that the Trading Networks database is running. Use the JDBC Pools page on the Integration
Server Administrator to ensure that the Integration Server can connect to the Trading Networks database.
TRNSERV.000025.000087 fromVersion is required to run wm.tn.admin.migrate:migrateCerts.

Cause: The required fromVersion parameter was not supplied.
Response: Supply a valid fromVersion.
TRNSERV.000025.000092 SQLException encountered in wm.tn.admin.migrate:migrateCerts.

Cause: SQLException thrown when executing the wm.tn.admin.migrate:migrateCerts service.
TRNSERV.000025.000093 Error encountered in wm.tn.admin.migrate:migrateCerts.


TRNSERV.000025.000094 Error encountered invoking service <serviceName>

Cause: An error occurred when invoking the specified service.
TRNSERV.000025.000098 Cannot get verify certificate for sender/receiver.

Cause: Trading Networks could not retrieve the verify certificate for the sender and receiver.
Response: Ensure that the verify certificate information is provided the sender and receiver.
TRNSERV.000025.000099 Cannot get verify certificate for sender=<senderID>, receiver=<receiverID>, stack trace is
<stackTrace>.
Cause: Trading Networks could not retrieve the retrieve verify certificate for the specified sender and receiver.
Response: Ensure that the verify certificate information is provided for specified sender and receiver.
TRNSERV.000025.000101 No chain for signer <index> (<totalSignerNumber>).

Cause: Required security data is missing.
Response: If your application code is creating or updating certificates, ensure that you supply all required
certificate data to the services you are invoking. If you receive this error while using the Trading Networks
Console, contact webMethods Customer Care.
TRNSERV.000025.000102 Cannot find verification cert.

Cause: Trading Networks could not retrieve a verify certificate.
TRNSERV.000025.000103 Cannot find verification cert for sender=<senderID>, receiver=<receiverID>.

Cause: Trading Networks could not retrieve the verify certificate for the specified sender and receiver.
Response: Ensure that the verify certificate information is provided for specified sender and receiver.
TRNSERV.000025.000104 Error encountered verifying XML document.

Cause: An error was thrown when verifying an XML document.

TRNSERV.000025.000109 Error encountered signing XML document.
Cause: An error was thrown while signing an XML document.
TRNSERV.000025.000110 Signing certificate for sender=<senderID> receiver=<receiverID> not valid.

Cause: The signing certificate for the specified sender and receiver is not valid.
Response: Provide a valid signing certificate for the sender/receiver pair.
TRNSERV.000025.000111 Verify certificate for sender=<senderID> receiver=<receiverID> not valid.

Cause: The verify certificate for the specified sender and receiver is not valid.
Response: Provide a valid verify certificate for the sender/receiver pair.
TRNSERV.000025.000115 Error encountered invoking wm.tn.security:getDecryptCACertificates.

Cause: Error encountered invoking the wm.tn.security:getDecryptCACertificates service.
TRNSERV.000025.000116 Error encountered invoking wm.tn.security:getDecryptCertificate.

Cause: Error encountered invoking the wm.tn.security:getDecryptCertificate service.
TRNSERV.000025.000117 Error encountered invoking wm.tn.security:getDecryptKey.

Cause: Error encountered invoking the wm.tn.security:getDecryptKey service.
TRNSERV.000025.000118 Error encountered invoking wm.tn.security:getEncryptCACertificates.

Cause: Error encountered invoking the wm.tn.security:getEncryptCACertificates service.

TRNSERV.000025.000119 Error encountered invoking wm.tn.security:getEncryptCertificate.

Cause: Error encountered invoking the wm.tn.security:getEncryptCertificate service.
TRNSERV.000025.000120 Error encountered invoking wm.tn.security:getEncryptKey.

Cause: Error encountered invoking the wm.tn.security:getEncryptKey service.
TRNSERV.000025.000121 Error encountered invoking wm.tn.security:getSecurity.

Cause: Error encountered invoking the wm.tn.security:getSecurity service.
TRNSERV.000025.000122 Error encountered invoking wm.tn.security:getSignCACertificates.

Cause: Error encountered invoking the wm.tn.security:getSignCACertificates service.
TRNSERV.000025.000123 Error encountered invoking wm.tn.security:getSignCertificate.

Cause: Error encountered invoking the wm.tn.security:getSignCertificate service.
TRNSERV.000025.000124 Error encountered invoking wm.tn.security:getSignKey.

Cause: Error encountered invoking the wm.tn.security:getSignKey service.
TRNSERV.000025.000125 Error encountered invoking wm.tn.security:getVerifyCACertificates.

Cause: Error encountered invoking the wm.tn.security:getVerifyCACertificates service.

TRNSERV.000025.000126 Error encountered invoking wm.tn.security:getVerifyCertificate.
Cause: Error encountered invoking the wm.tn.security:getVerifyCertificate service.
TRNSERV.000025.000132 Error encountered invoking wm.tn.security:setDecryptCertificateSet.

Cause: Error encountered invoking the wm.tn.security:setDecryptCertificateSet service.
TRNSERV.000025.000133 cert is null but CACerts not null.

Cause: You provided information in CACerts to specify CA certificates; however, you did not provide a
certificate in cert.
Response: Provide a valid certificate in cert.
TRNSERV.000025.000134 CACerts is required for non self signed certificates.

Cause: You did not specify CA certificates in CACerts. CACerts is required unless the certificate you specify is
self-signed.
Response: Provide valid CA certificates in CACerts.
TRNSERV.000025.000137 Error encountered invoking wm.tn.security:setEncryptCertificateSet.

Cause: Error encountered invoking the wm.tn.security:setEncryptCertificateSet service.
TRNSERV.000025.000151 Error encountered invoking wm.tn.security:setSecurity.

Cause: Error encountered invoking the wm.tn.security:setSecurity service.
TRNSERV.000025.000152 privateKey and cert should be both null or neither null.

Cause: You specified a value for either privateKey or cert, but not for both. The values for privateKey and Cert
must either both be null or both have non-null values.
Response: Provide valid values for privateKey and cert.

TRNSERV.000025.000153 CACerts is required for non self signed certificates.

Cause: CACerts is required for non self signed certificates.
Response: Provide valid value for CACerts.
TRNSERV.000025.000156 Error encountered invoking wm.tn.security:setSignCertificateSet.

Cause: Error encountered invoking the wm.tn.security:setSignCertificateSet service.
TRNSERV.000025.000159 Error encountered invoking wm.tn.security:setVerifyCertificateSet.

Cause: Error encountered invoking the wm.tn.security:setVerifyCertificateSet service.
TRNSERV.000025.000164 Error encountered invoking wm.tn.security:updateCertificate.

Cause: Error encountered invoking the wm.tn.security:updateCertificate service.
TRNSERV.000025.000165 Error encountered in wm.tn.security:addCertificateData.

Cause: Error encountered when executing the wm.tn.security:addCertificateData service.
TRNSERV.000025.000166 Cannot get existing Certificate Data from supplied certID=<certID>.

Cause: Cannot get existing certificate data for the certificate information with certID=<certID>. The supplied
certID might be invalid.
Response: Ensure that the value for certID is valid.
TRNSERV.000025.000167 Cannot get existing CertID from supplied ownerID=<ownerID> partnerID=<partnerID> and
usage=<certificateUsage>.
Cause: Cannot get existing CertID for certificate data that is associated with ownerID=<ownerID>
partnerID=<partnerID> and usage=<certificateUage>.
Response: Ensure that the values for ownerID, partnerID, and usage are valid.

TRNSERV.000025.000168 Cannot construct new CertData in wm.tn.security:updateCertificateData.
TRNSERV.000025.000169 Error encountered in wm.tn.security:updateCertificateData.

Cause: Error encountered when executing the wm.tn.security:updateCertificateData service.
TRNSERV.000025.000170 Cannot delete non-existing CertData for ownerID=<ownerID>, partnerID=<partner ID> and
usage=<certificateUsage>.
Cause: Trading Networks could not locate certificate data for the specified ownerID, partnerID, or usage.
Response: Ensure that the values for ownerID, partnerID, and usage are valid.
TRNSERV.000025.000171 Error encountered in wm.tn.security:deleteCertificateData.

Cause: Error encountered when executing the wm.tn.security:deleteCertificateData service.
TRNSERV.000025.000172 Error encountered in wm.tn.security:getCertificateData.

Cause: Error encountered when executing the wm.tn.security:getCertificateData service.
TRNSERV.000025.000175 Error encountered in wm.tn.security:getSigningKeyAndChain.

Cause: Error encountered when executing the wm.tn.security:getSigningKeyAndChain service.
TRNSERV.000025.000176 Error encountered in wm.tn.security:getVerifyingChain.

Cause: Error encountered when executing the wm.tn.security:getVerifyingChain service.

TRNSERV.000025.000178 Error encountered in wm.tn.security:getDecryptionKeyAndCert.

Cause: Error encountered when executing the wm.tn.security:getDecryptionKeyAndCert service.
TRNSERV.000025.000179 Error encountered in wm.tn.security:getEncryptionChain.

Cause: Error encountered when executing the wm.tn.security:getEncryptionChain service.
TRNSERV.000025.000182 <sslClientSet> private key not defined.

Cause: The private key for the SSL client certificate set was not defined.
Response: Provide a valid SSL private key for the SSL client certificate set.
TRNSERV.000025.000183 <sslClientSet> certificate chain not defined.

Cause: The certificate chain for the SSL client certificate set was not defined.
Response: Provide a valid SSL certificate chain for the SSL client certificate set.
TRNSERV.000025.000184 Error encountered in wm.tn.security:getSSLKeyAndChain.

Cause: Error encountered when executing the wm.tn.security:getSSLKeyAndChain service.
TRNSERV.000025.000185 No SSL key and cert defined.

Cause: The SSL private key and certificate are not defined.
Response: Provide a valid SSL private key and certificates.
TRNSERV.000025.000187 Error encountered in wm.tn.security:setSSLKeyAndChain.

Cause: Error encountered when executing the wm.tn.security:setSSLKeyAndChain service.

TRNSERV.000025.000190 Certificate chain bytes cannot be null or zero length.
Cause: The certificate chain bytes is either null or a zero length. The certificate chain must contain data.
Response: Provide valid certificate chain byte array.
TRNSERV.000025.000191 Invalid RSA Private Key file.

Cause: The RSA private key file is not valid.
Response: Provide a valid RSA private key file.
TRNSERV.000025.000192 Can not construct new CertData.

Cause: Internal Error.
TRNSERV.000025.000193 Bad private key for usage <certificateUsage>: <errorMessage>

Cause: The private key that was provide is not valid.
Response: Provide a valid private key.
TRNSERV.000026.000001 Content Part <partName> does not exist in document <docID>.

Cause: The document does not have the requested content part.
Response: Request a different content part, or request this content part from a different document.
TRNSERV.000026.000002 Content for Part <partName> of document <docID> does not exist in TSpace.
Cause: This is a large document and the requested content part was not found in temporary storage.
Response: Request a different content part, or request this content part from a different document.
TRNSERV.000026.000003 Error retrieving content of content part <partName> of document <docID>. The exception message
is : <exceptionMessage>. The stack trace is : <stackTrace>
Cause: An exception was thrown while retrieving document content.
TRNSERV.000026.000004 Unable to find a document type for the given document type name, <docTypeName>.
Cause: While deleting documents by TN document type name, could not find the TN document type.
Response: Supply a valid TN document type name to the wm.tn.doc:deleteDocuments service.

TRNSERV.000026.000006 Attempted to update system attributes for the document, but no rows were changed in the
database.
Cause: Trading Networks encountered an error while attempting to update the system attributes for the
document.
Response: Retrieve this document from the database and examine it to determine why this error occurred.
TRNSERV.000026.000018 Error when adding large content part named <partName> to this document
Cause: Encountered an Exception while adding a large content part to a document.
the Exception.
TRNSERV.000026.000019 The actual exception is <exceptionMessage>.

Cause: Encountered an Exception while adding a large content part to a document.
the Exception.
TRNSERV.000026.000020 User <userName> (partnerID=<partnerID>) is not an administrator and attempted to retrieve a

document (docID=<docID>) that does not belong to him.
Cause: Users that do not have Administrator authority can only retrieve documents that they either sent or
received. The specified user attempted to retrieve a document for which the user was neither the sender nor
receiver.
TRNSERV.000026.000021 You do not have the authority to retrieve this document. Only administrators may access
documents that they did not send or receive.
Cause: Users that do not have administrator authority can only retrieve documents that they either sent or
received. The specified user attempted to retrieve a document for which the user was neither the sender nor
receiver.
Response: Ask someone with Administrator authority to look at this document.
TRNSERV.000027.000011 Error encountered during TN server starting: <exceptionMessage>

Cause: An exception was thrown while Trading Networks was starting.

TRNSERV.000027.000012 Error encountered during TN server stopping: <exceptionMessage>
Cause: An exception was thrown while Trading Networks was stopping.
TRNSERV.000027.000013 Error encountered during TN server restarting: <exceptionMessage>

Cause: An exception was thrown while Trading Networks was restarting.
TRNSERV.000027.000019 TN database connection pool failed: error initializing Datastore

Cause: An exception was thrown while initializing the Trading Networks database connection pool.
the exception.
TRNSERV.000027.000020 TN Server failed starting up: error initializing database connection pool
Cause: An exception was thrown while initializing the Trading Networks database connection pool.
the exception.
TRNSERV.000027.000021 TN Server failed starting up: OEM restriction was hacked

Cause: A user or developer attempted to bypass the OEM restrictions. The server will not start.
the exception.
TRNSERV.000027.000024 TN task manager encountered error: <exceptionMessage>

Cause: An exception was thrown that has terminated execution of the task manager.
TRNSERV.000027.000025 TN temporary storage space initialization failed: <exceptionMessage>

Cause: An exception was thrown while preparing temporary disk space for large files.
change the tn.tspace.location system property to a disk partition that has more free space.

TRNSERV.000027.000028 Invalid notification type encountered in pkginit:sendNotif

TRNSERV.000027.000039 MBean cannot record statistics for document id <docID>. Document does not exist.
TRNSERV.000027.000040 Exception thrown while saving document processing statistics.

the exception.
TRNSERV.000027.000041 Error encountered in writing WmOmiTN service ACL information to disk.

TRNSERV.000027.000042 Error encountered initializing DocStatistics: <exceptionMessage>.

Cause: An exception was thrown while initializing the statistics gathering mechanism.
TRNSERV.000027.000043 Error encountered shutting down DocStatistics: <exceptionMessage>.

Cause: An exception was thrown while stopping the statistics gathering mechanism.
TRNSERV.000028.000001 Cannot persist a TPA

Cause: An exception was thrown while saving a TPA to the database.
the exception.
TRNSERV.000028.000002 Cannot retrieve a TPA

Cause: An exception was thrown while reading a TPA from the database.
the exception.

TRNSERV.000028.000006 Cannot delete a TPA with status="agreed"
Response: Change the TPA's status to "Proposed"; then delete it.
TRNSERV.000028.000007 Cannot delete a TPA

Cause: An exception was thrown while deleting a TPA from the database.
the exception.
TRNSERV.000028.000008 Cannot update a TPA that has status="agreed"

Response: Change the TPA's status to "Proposed" before updating the TPA.
TRNSERV.000028.000009 Cannot update a TPA

Cause: An exception was thrown while updating a TPA in the database.
the exception.
TRNSERV.000028.000010 Cannot get a TPA lock

Cause: An exception was thrown while getting a lock on a TPA in the database.
the exception.
TRNSERV.000028.000011 Cannot update controlNumber for a TPA

Cause: An exception was thrown while updating the control number of a TPA in the database.
the exception.
TRNSERV.000028.000014 Cannot update tpaData when status="agreed" and dataStatus="immutable"

Cause: You attempted to update the TPA data that is associated with a TPA. The Agreement Status of the TPA
is "Agreed" and the Data Status is "Non-modifiable". You cannot update the TPA data when the Data Status is
"Non-modifiable".
Response: To be able to update the TPA data, perform one of the following actions: 1) Change the Data Status
to "Modifiable". 2) Change the Agreement Status to "Proposed".

TRNSERV.000028.000017 Cannot update tpaData

Cause: An exception was thrown while updating the TPA data in a TPA in the database.
the exception.
TRNSERV.000028.000018 Cannot get the next controlNumber for a TPA

Cause: An exception was thrown while determining the next control number for a TPA in the database.
the exception.
TRNSERV.000028.000020 Cannot change status for a TPA

Cause: An exception was thrown while changing the status of a TPA in the database.
the exception.
TRNSERV.000028.000021 A TPA that matches senderID, receiverID and agreementID does not exists
TRNSERV.000028.000022 Missing senderID, or receiverID, or agreementID or initService

TRNSERV.000028.000023 Cannot invoke initService

Cause: Unable to initialize the data in a TPA because the TPA's initialization service could not be invoked.
Response: Make sure the TPA's initialization service is an existing service in an enabled package.
TRNSERV.000028.000025 Query TPA exception

Cause: An exception was thrown while executing a TPA database query.
the exception.

TRNSERV.000028.000026 Cannot get all TPAs
Cause: An exception was thrown while retrieving a list of TPAs from the database.
the exception.
TRNSERV.000028.000027 Cannot import TPA

Cause: An exception was thrown while importing one or more TPAs.
the exception.
TRNSERV.000028.000028 Missing data schema

Cause: No IS document type is defined for the TPA.
Response: Define an IS document type for the TPA.
TRNSERV.000028.000029 Missing TPA data

Cause: The TPA Data field in the TPA is empty.
Response: Enter values into the TPA Data field.
TRNSERV.000028.000030 Cannot invoke validation service

Cause: An exception was thrown while invoking the pub.schema:validate service while validating the
structure of the IS document type in the TPA.
the exception.
TRNSERV.000028.000031 Missing <variable>

Cause: A required input variable was not supplied to the wm.tn.tpa:updateTPA service.
Response: Supply a value for the required variable.
TRNSERV.000028.000032 A TPA that matches senderID, receiverID and agreementID already exists
Cause: Cannot save this TPA because it would duplicate an existing TPA.
Response: Either add the data in this TPA to the one that already exists, or specify a different agreementID.

TRNSERV.000028.000033 A TPA that matches senderID, receiverID and agreementID does not exist
Cause: Cannot update the TPA because Trading Networks is unable to locate a TPA in the database that has the
supplied senderID, receiverID, and agreementID.
Response: Specify a senderID, receiverID and agreementID that matches an existing TPA.
TRNSERV.000028.000034 controlNumber cannot not be null

TRNSERV.000028.000035 tpaData cannot not be null

TRNSERV.000028.000036 Cannot update tpaData when dataStatus="immutable"

Cause: You cannot make changes to a TPA's data when the TPA's Data Status is "Non-modifiable".
Response: To make changes to the TPA data, Change the TPA's Data Status to "Modifiable".
TRNSERV.000028.000037 Cannot update controlNumber

Cause: An exception was thrown while updating the control number of a TPA in the database.
the exception.
TRNSERV.000028.000038 There are more than one TPA that matches senderID, receiverID and agreementID
TRNSERV.000028.000039 Cannot serialize tpaData

TRNSERV.000028.000040 Cannot de-serialize tpaData


TRNSERV.000028.000040 New controlNumber is not an integer
Cause: The supplied control number is not a valid integer.
Response: Supply a valid integer value.
TRNSERV.000028.000042 A TPA with the supplied ID (<tpaID>) does not exist.

Cause: An invalid value was supplied for the tpaID field.
Response: Supply a valid TPA ID.
TRNSERV.000028.000043 If "tpaID" is not supplied, then "senderID", "receiverID" and "agreementID" must be supplied.
Cause: The user did not supply the correct required inputs.
Response: Supply the required inputs.


CHAPTER 15
webMethods Workflow
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
WKT (Run-Time Support) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017

CHAPTER 15 webMethods Workflow
WKA (Authentication Server)
WKA.012.0007 WFUser object has NULL user name.

Cause: The user object got from the public API has a null user name.
Response: Check the implementation code for the public API, and refer to Authentication Server log files for
related CSEvent messages under VERBOSE log mode.
WKA.012.0008 WFUser object has NULL user id.

Cause: The user object got from the public API has a null user ID.
Response: Check Authentication Server log files for related CSEvent messages and any database access error
messages. Increase the log level to VERBOSE.
WKA.012.0009 WFRoleAttr object has NULL attribute name.

Cause: The WFRoleAttr object got from the public API has a null attribute name.
related CSEvent messages. Increase the log level to verbose.
WKA.012.0010 WFRoleAttr object has NULL attribute type.

Cause: The WFRoleAttr object got from the public API has a null attribute type.
related CSEvent messages. Increase log level to verbose.
WKA.012.0011 User password string restricted to 7-bit ASCII characters. Please retype.
Cause: The user typed in characters that fall outside the range of 7-bit ASCII character set [0x20 through 0x7E].
Response: Restrict password characters to fall within the 7-bit US ASCII character set.
WKA.012.0012 User password length has to be minimum <passwordLengthLimit> characters. Please retry.
Cause: The user password created is shorter than the minimum password length limit allowed.
Response: The user can either create a longer password or, alternatively, configure the password length limit to
be smaller. The latter choice will apply to all passwords that will be created henceforth.
WKA.012.0013 User password has been previously used. Please retry.

Cause: The administrator is trying to associate a previously used password with the user.
Response: Enter a new password. Previously used passwords cannot be used again.

WKA.012.0014 User password confirmation failed. Please retry.

Cause: The password string and confirmation do not match.
Response: Enter the same string in the password and confirmation fields.
WKA.012.0016 Invalid user name or password.

Cause: The user name or password entered is invalid.
Response: Enter a valid user name and password.



WKA.012.0020 Invalid username or password: <exceptionMessage>.

WKA.012.0021 No user name specified for logout.

Cause: No user name was specified during logout.
Response: If called via API, check the implementation code.


WKA.012.0023 Invalid username or password for user <userName>.

Response: Enter the correct user name and password.

WKA.012.0025 The user <userName> to be logged out, is not a valid user.

Cause: The user name specified during logout is an invalid user.
WKA.012.0026 Cannot obtain Workflow permission for NULL user.

Cause: No user was specified when obtaining Workflow permissions.
WKA.012.0029 <userNameOrPassword> string restricted to 7-bit ASCII characters. Please retype.

Cause: The user name or password typed falls outside the range of 7-bit US ASCII set (0x20 through 0x7E).
Response: Retry with a valid character string for the username and password
WKA.020.0001 No user associated with the authentication token.

Cause: The authentication token provided does not have a user associated with it.
Response: The token is invalid. Try to log in again to obtain a new token and retry the operation.
WKA.020.0002 UserRoleService: the authentication session is NULL.

Cause: The local cache store cannot be created because the associated authentication session object is null.
Response: If called from an API, check the implementation code. Log out and back in and then retry the
operation.
WKA.020.0003 UserRoleService: failed to get session id of the authentication session

Cause: The local cache store cannot obtain the session ID for the associated authentication session.
Response: If called from an API, check the implementation code. Log out and back in and then retry the
operation.

WKA.020.0007 ServerStateMonitor: failed to obtain URL to <RMIserviceForAuthenticationServer>, <errorMessage>

Cause: The client failed to obtain the URL for the Authentication Server.
Response: Check the classrv.properties file for Authentication Server settings. Check server logs to ensure the
resource server is running. Check network settings to see if the client can reach the server system.
WKA.020.0008 ServerStateMonitor: lookup failed for AuthenticationServer stub [<URLtoAuthenticationServerService>],

<errorMessage>
Cause: The client failed to reach the Authentication Server.
Response: Check server logs to ensure that the Authentication Server is running. If the Authentication Server
has yet to come up, this error can be ignored. Otherwise, the Authentication Server cannot be reached due to
network issues, such as the Workflow Server being down, etc. Restart the Workflow Server and retry the client
connection.
WKA.020.0010 Failed to register Authentication Server in RMI registry: <errorMessage>

Cause: The Authentication Server cannot register itself within the RMI registry.
Response: Check to ensure that the Workflow Server is started under the supported JVM version. Check server
logs for any earlier fatal errors that resulted in this error.
WKA.020.0011 Malformed URL to Authentication Server: <URLtoAuthenticationServerService>

Cause: The URL to the Authentication Server service is malformed
Response: Check the classrv.properties file for Authentication Server settings. Check server logs to ensure the
resource server is running.
WKA.020.0012 No support for SecureRandom algorithm in IBMJCE provider.

Cause: The IBM JCE provider does not have support for the SecureRandom algorithm.
Response: This error is specific to the operating system using the IBM JCE security provider as opposed to SUN
JCE, e.g., AIX. Check the operating system version and the JVM version on the AIX system on which
Workflow Server is installed. Make sure the Workflow Server is using the supported JVM version.
WKA.020.0013 Failed to initialize Authentication Session, (<errorMessage>).

Cause: Upon startup, the Authentication Server cannot establish an Authentication Session for its use.
Response: Check the classrv.properties file for Authentication Server settings. Make sure the configuration of
Workflow was successful. Check server logs for any earlier failures.

WKA.020.0014 Failed to initialize Authentication Server, (<errorMessage>).

Cause: Upon startup, the Authentication Server failed to get initialized.
Response: Check the classrv.properties file for Authentication Server settings. Make sure the configuration of
Workflow was successful. Check server logs for any earlier failures.
WKA.020.0015 The user trying to login is invalid.

Cause: The user trying to log in is not a valid user.
Response: Check the validity of the user. If using Workflow local security, the administrator should check this
via the Workflow Users tool. If using the public API, check the implementation code and contact the System
Administrator of the central store.
WKA.020.0016 The user does not have login privilege.

Cause: The user trying to log in is either invalid or has been disabled by the System Administrator.
Response: Contact the system administrator regarding the user account. If using Workflow local security, the
administrator should check this via the Workflow Users tool.
WKA.020.0017 Login operation failed for user <userName>: <errorMessage>

Cause: The login operation failed for the user.
Response: The login operation failed. Usually another error message will be associated with this to specify the
actual reason. In all other cases, the user name or password is invalid. Contact the system administrator.
WKA.020.0018 Login operation failed for user <userName>: <errorMessage>

Cause: The login operation failed for the user.
Response: The login operation failed. Usually another error message will be associated with this to specify the
actual reason. In all other cases, the user name or password is invalid. Contact the system administrator.
WKA.020.0020 Invalid Authentication Token signature.

Cause: The authentication token is invalid.
Response: If called from an API, check the implementation. Log out and back in to retry the operation.
WKA.020.0021 User is not logged in to obtain an Authentication Session.

Cause: The user's attempt to obtain an authentication session failed because the user was not logged in earlier.
Response: Log in again and try to obtain the session.

WKA.020.0022 Failed to get Authentication Session for <userName> : <errorMessage>

Cause: The user failed to obtain an authentication session.
Response: This error will be accompanied by another message explaining why the session access failed. Rectify
the condition as per the error message, and log in again to get the session.
WKA.020.0023 CSEvent : invalid Authentication Event <eventType>.

Cause: The event received from the public API is invalid.
Response: Check the public API implementation code.
WKA.020.0024 CSEvent User Event: <eventType>, user name is NULL.

Cause: The name change related authentication event received from the public API has a null user name.
WKA.020.0025 CSEvent Role Event: <eventType>, role name is NULL.

Cause: The role change related authentication event received from the public API has a null role name.
WKA.020.0026 CSEvent Role event: No role template for role <roleName>.

Cause: The role mentioned in the authentication event received from the public API has no associated role
template definition.
Response: Check the public API implementation code as well as the role template store for role definitions.
WKA.020.0027 Illegal logout access.

Cause: The user tried to log out without the proper credentials.
Response: This error occurs only via an API call that calls for a user logout without credentials passed in. To
rectify, choose the proper logout call and pass in valid credentials.
WKA.020.0028 Logout failed due to invalid Authentication token.

Cause: The token passed in during logout is invalid.
Response: If called via an API, try the logout operation with the password.
WKA.020.0029 User <userName> failed authorization to logout.

Cause: The token passed in during logout is invalid.
Response: If called via an API, try the logout operation with the password.

WKA.020.0030 User <userName>, trying to logout is invalid.

Cause: The user trying to log out is an invalid user.
Response: If called via an API, try the logout operation with the correct user name.
WKA.020.0031 The logout operation failed, <errorMessage>

Cause: The logout operation failed.
Response: This generic error contains the error message explaining the actual reason for the failure. If called
from an API, rectify the situation and retry the logout operation.
WKA.020.0032 Security API Tracing ERROR: <errorString>

Cause: An error message was logged by the boundary of the public API.
Response: The actual error string highlights the error. Check the implementation code and take corrective
action accordingly.
WKA.020.0033 Security API Logging: <errorString>

Cause: An error message was logged by the public API implementation code.
Response: The actual error string is implementation-dependent. Take corrective action accordingly.
WKA.020.0034 Cannot perform user search, field type is NULL.

Cause: The user attribute type on which the user record search is performed is NULL in value.
Response: If called from an API, check the implementation code.
WKA.020.0036 User <userName> [userid=<userID>], not found.

Cause: Failed to find a user with the specified user name and ID via the public API.
Response: Check the public API implementation code and verify the user name with the central store.
WKA.020.0037 User <userName> not found.

Cause: Failed to find a user with the specified user name via the public API.
Response: Check the public API implementation code and verify the user name with the central store.
WKA.020.0038 Cannot get roles for NULL user.

Cause: The roles requested from the public API are for a null user.
Response: If called via an API, check the implementation code.

WKA.020.0039 Cannot obtain Workflow permission for NULL user.

Cause: No user was specified when obtaining Workflow permissions.
WKA.020.0040 Error trying to create user record for user: <userName>

Cause: Failed to create a user record in the Workflow local security store.
Response: The reason for the failure is thrown to the user in a dialog box when using the Workflow Users tool.
Take corrective action accordingly and the retry the user creation operation.
WKA.020.0041 Error trying to create user record for user: <userName>, password not specified.
Cause: No password was specified when the user record was being created.
Response: Modify the user record in the Workflow Users tool to specify the password, and retry the user
creation operation.
WKA.020.0042 User password has been previously used.

Cause: The password that is being set has been previously assigned to the same user.
Response: Set a password that has not been previously assigned to the user.
WKA.020.0045 Unknown field type specified for user search: <fieldType>

Cause: The type of attribute field on which the search was made is invalid.
WKA.020.0046 Cannot find user with login id containing: <patternSubstring>, <errorMessage>

Cause: The search pattern substring on the login ID failed to retrieve any users.
Response: Try a new search pattern substring.
WKA.020.0047 Cannot find user with extended name containing: <patternSubstring>, <errorMessage>
Cause: The search pattern substring on the full name failed to retrieve any users.
WKA.020.0048 Cannot find user with title containing: <patternSubstring>, <errorMessage>

Cause: The search pattern substring on the user title failed to retrieve any users.

WKA.020.0051 Failed to register as WFLogListener, <errorMessage>

Cause: The authentication server failed to register to listen to log messages from the public API
implementation.
WKA.020.0052 User <userName>: login failed on central store, <errorMessage>.

Cause: The user failed to log in on the central store.
Response: Check public API implementation error messages as well as the implementation code.
WKA.020.0053 User <userName>: isLoggedIn failed, <errorMessage>

Cause: Failed to verify with the central store whether the user is logged in.
WKA.020.0054 canVerifyPassword failed: <errorMessage>

Cause: Failed to check whether the central store can verify the password.
WKA.020.0055 User <userName>: verifyPassword failed, <errorMessage>

Cause: Failed to verify the user's password with the central store.
WKA.020.0056 User <userName>: logout failed, <errorMessage>

Cause: Failed to log user out from the central store.
WKA.020.0057 getAllUsers [<patternSubstring>, <attributeFieldType>] failed: <errorMessage>

Cause: Failed to search users on the central store with the search pattern and attribute field specified.
WKA.020.0058 getAllRoles failed: <errorMessage>

Cause: Failed to get role template definitions of all roles from the central store.

WKA.020.0059 User <userName>: getUser failed: <errorMessage>

Cause: Failed to get user record for the specified user from the central store.
WKA.020.0060 User <userName>: getRolesForUser failed, <errorMessage>

Cause: Failed to get associated role records for the specified user from the central store.
WKA.020.0062 User trying to login is invalid.

Cause: The user trying to log in is not a valid user.
Response: Check the validity of the user with the system administrator.
WKA.020.0063 User password has expired. Please contact the system administrator.
Cause: The user password on the central store has expired.
Response: Contact the system administrator of the central store.
WKA.020.0064 User password has expired. User canceled option to change the password.
Cause: The user password on the local store has expired. The user canceled the option to change the password.
Response: No action is required by the user. At a later time the user must either set a new password, or the
system administrator must set it via the Workflow Users tool.
WKA.020.0065 Login username is NULL or an empty string.

Cause: The user name passed during login is either NULL or an empty string.
Response: If called via an API, check the implementation code. Enter the proper user name string during login.
WKA.024.0001 User account has been disabled. Please contact your System Administrator.
Cause: The user account has been disabled.
Response: Contact the system administrator.
WKA.024.0002 The user is not privileged to modify user accounts.

Cause: The user is attempting to modify user accounts on the local store, and is not privileged to do so.
Response: Check privilege access with the system administrator.






WKA.024.0008 The user <userName> is invalid.

Cause: The user trying an administrative function is an invalid user.
Response: Check the account validity with the system administrator.
WKA.024.0009 The user does not have administrative privilege.

Cause: The user trying an administrative function does not have the right privilege.
WKA.024.0010 The user does not have administrative privilege.



WKA.024.0012 The user <userName> is invalid.

Cause: The user trying an administrative function is an invalid user.

WKA.024.0014 User is not authorized to change passwords.

WKA.024.0015 User does not have read access.

Cause: The user has not been granted read access.
Response: Check the access granted with the system administrator.

Cause: The user has not been granted the privilege to modify user accounts.
WKA.024.0017 The user is not privileged to modify role accounts.

Cause: The user has not been granted the privilege to modify role accounts.
WKA.024.0018 User <userName>, trying the administrative function is not logged in.
Cause: The user is attempting to perform an administrative function without logging in.
Response: If called from an API, check the implementation code. Log in again to obtain an authentication
session and retry the operation.

WKA.024.0019 Unable to verify login for user <userName>, due to database connectivity issues.
Cause: The authentication server connection to the database is down.
Response: Check logs to identify database issues. If the database connection is not restored automatically,
identify the issue and restore the database connection. Then restart the authentication server and retry the
operation.
WKA.024.0020 Unable to verify login for user <userName>

Cause: The authentication server is unable to verify that the user has logged in. This problem is most likely due
to a failure to access the database.
Response: A related exception stack should show the actual error message that explains the cause of this error.
If the cause is database related, restore database connectivity. Then restart the authentication server and retry
the operation.

WKB (Common Client)
WKB (Common Client)
WKB.009.0001 Broker connection error.

Cause: The broker may be not be started, or there may be a networking problem.
Response: Ensure that the broker is started, and make sure the licenses have not expired. Ensure that your
machine has network connectivity to the broker's machine.
WKB.009.0002 Broker event conversion error.

Cause: Unable to obtain storage or classloader to perform mapping operation, or an attribute count mismatch
occurred.
Response: Compare the broker document definition with the project's data definition for the document. If the
definitions match, try increasing the client's JVM size allocation with by using VM arguments -Xms256m -
Xmx512m.
WKB.009.0003 DCS connection error.

Cause: Error creating a DCS session or pool, fetching all available tasks, or querying for a task
Response: Check that the DCS, process server, and authentication server are all running without having logged
any errors.
WKB.012.0001 Unknown message.

Cause: An unregistered WFMessage was encountered during a Workflow API commit, rollback, or release
operation.
Response: Check that the broker's document definitions match those mapped in the project.
WKB.012.0002 Wrong role attribute name.

Cause: A Workflow API operation cannot get a role attribute from the role.
Response: Verify that the authentication server is running and that there are no network problems.
WKB.012.0003 Wrong role attribute type.

Cause: A Workflow API operation found that a role attribute is of an unknown type.
Response: Verify that the document definition's attributes in your project is correct.
WKB.012.0004 Role attribute conversion failed.

Cause: A Workflow API operation was unable to convert a role attribute's value from String to its desired type.
Response: Verify that the type specified is supported. It may be necessary to map to a different type.

WKB.012.0005 No role attribute.

Cause: A Workflow API operation was unable to find a role attribute with the requested name.
Response: Verify that the role attribute name is correct.
WKB.012.0006 Attribute access error.

Cause: A Workflow API operation was unable to create, access, or find a specified attribute or attribute
information.
Response: Verify that the attribute name is correct.
WKB.012.0007 Task arguments number mismatch.

Cause: A Workflow API operation determined that the number of arguments for the task is greater or less than
expected.
Response: Check your project's tasks to correct the number of arguments being passed to the task.
WKB.012.0008 No gate information.

Cause: A Workflow API operation failed to get gate metadata.
Response: Verify that the attribute is defined and that the authentication server is started.
WKB.012.0009 Wrong task outgate name.

Cause: A Workflow API commit or rollback failed due to a wrong outgate name.
Response: Check the project's outgate names.
WKB.012.0010 Wrong task ingate name.

Cause: A Workflow API startWorkflow operation was passed a wrong task ingate name.
Response: Check the project's ingate names.
WKB.012.0011 Metadata not accessible.

Cause: A Workflow API operation failed to get a workflow metadata process descriptor.
Response: Verify that the process server is running.
WKB.012.0012 Data conversion error.

Cause: A Workflow API operation encountered a data conversion error when getting an object.
Response: Check the data types of the objects in your project.

WKB (Common Client)
WKB.012.0013 User not found.

Cause: A Workflow API operation encountered a distribution rule that was given a user name that it could not
find.
Response: Check the user names in your project's distribution rules.
WKB.012.0014 Role not found.

Cause: A Workflow API operation encountered a distribution rule that was given a role that it could not find.
Response: Check the role names in your project's distribution rules.
WKB.012.0015 Unknown distribution rule.

Cause: A Workflow API operation could not find the named distribution rule.
Response: Check the spelling of the name of the project's distribution rule.
WKB.014.0001 Invalid query.

Cause: A Workflow API fetchByQuery() operation was passed an invalid query string.
Response: Verify the syntax of the query string.
WKB.015.0001 password does not meet the required length.

Cause: A Workflow API operation failed due to the newly entered password being shorter then the minimum
length requirement.
Response: Enter a password which is at least the length of the defined minimum value.
WKB.015.0001 Password expired.

Cause: A Workflow API operation failed due to password expiration.
Response: Set a new password for the user and retry the operation.
WKB.015.0001 password has been previously used.

Cause: A Workflow API operation failed because to the newly entered password has been used previously by
the user.
Response: Enter a password which has not been used previously by this user.
WKB.016.0001 No permission to connect to workflow servers.

Cause: A Workflow API operation does not have permission to run the Workflow Inbox.
Response: Give the user permission to run the Workflow Inbox.

WKB.020.0001 No host specified.

Cause: A Workflow API operation was trying to create a session, but no host name parameter was specified.
Response: Specify a host name in the createSession operation.
WKB.020.0002 No session factory.

Cause: A Workflow API createSession() operation failed because it could not create a session factory.
Response: Verify that the authentication server is running.
WKB.020.0003 No security manager.

Cause: A Workflow API createSession() operation failed because there was no security manager.
Response: Set the system's security manager with System.setSecurityManager().
WKB.020.0004 No pdmessageinfo support.

Cause: A Workflow API operation failed. This should never occur.
Response: Restart the API container and retry the operation.
WKB.020.0005 No free listeners support.

Cause: A Workflow API operation failed. This should never occur.
Response: Restart the API container and retry the operation.
WKB.020.0006 No class server.

Cause: An invalid class server was specified on createSessionImpl().
Response: Verify the host and port for the class server.
WKB.020.0007 Cannot load info for <ProjectVersionMapping>. Will skip.

Cause: Cannot load the project name and ID information for this project mapping.
Response: Check that the project name and version are correct and that the process server and DCS are
running.
WKB.020.0008 No task properties for <taskName>.

Cause: No task properties were found for the task. The task may not be active.
Response: Check to see if the task is still active.

WKB (Common Client)
WKB.020.0009 No taskview info.

Cause: The task's properties do not contain any view information.
Response: Check the project's task view to see if view information has been set.
WKB.020.0010 No workflow [<process>] found in <ProjectVersionMapping>.

Cause: The workflow was not found. It may not be active.
Response: Check to see if the workflow and tasks are still active.
WKB.020.0011 Wrong ingate number <index> for <ProjectVersionMapping> <classname>.

Cause: Unable to obtain ingate.
Response: Check the project model and verify that the process server and DCS are running.
WKB.020.0012 Wrong outgate number <index> for <ProjectVersionMapping> <classname>.

Cause: Unable to obtain outgate.
Response: Check the project model and verify that the process server and DCS are running.
WKB.020.0013 Task checkout failed.

Cause: Task checkout failed.
Response: See if someone else checked out the task.
WKB.020.0014 Task commit failed.

Cause: Task commit failed.
Response: Check the server logs to see if there has been a process server or DCS failure. Take the appropriate
action for the problem indicated in the logs. It might be a server or database connectivity situation. When the
problem has been corrected, retry the operation.
WKB.020.0015 Task release failed.

Cause: Task release failed.

WKB.020.0016 Task rollback failed.

Cause: Task rollback failed.
WKB.020.0017 Workflow start failed.

Cause: Workflow start failed.
WKB.021.0001 No workflow servers to connect.

Cause: There are no Workflow servers to which to connect.
Response: Verify that the Workflow server is running.
WKB.024.0001 Authentication failed.

Cause: Authentication failed.
Response: Check the spelling of the user name, password, and host name. Verify that the authentication server
is running.
WKB.024.0002 Session disconnected.

Cause: Session disconnected.
Response: Check to see if the authentication server, process server, and DCS are still active; and restart them if
not.
WKB.024.0003 User is already logged in.

Cause: User is already logged in.
Response: Log the other user out.

WKC (Common Server)
WKC (Common Server)
WKC.002.0001 Unable to start Log Server.

Cause: The Log Server JVM failed to start up due to a fatal error. A related exception stack in the log should
identify the actual problem.
Response: Check the classrv.properties file for log server settings. Verify that the Resource Server is running.
Identify the issue from the error stack and take appropriate actions.
WKC.002.0002 No permission to create the top level log directory "<absolutePathOfLogDirectory>".

Cause: Permission issues to create a log directory are causing the log server not to start.
Response: Check directory permissions. This could be an installation issue.
WKC.009.0001 BusinessMonitor: failed to connect to broker: <errorMessage>.

Cause: The Business Monitor component cannot connect to the broker.
Response: The error message should explain the actual problem. Check that the Workflow configuration was
successful in connecting to the broker. Most broker access errors appear in the configuration logs. Check for
network connectivity issues if the broker is on a remote system.
WKC.010.0001 BusinessMonitor:: failed to <register/update> StepInfo object for PTE info related to process ID <processID>
Cause: A database error occurred during the registration/update of the StepInfo object.
Response: Investigate the reason. If the problem is due to a database connection failure, the error should stop
once database connectivity is restored. For other errors: Contact webMethods Customer Care. Please have the
following information available: - Copies of all logs in the <WorkflowServerDirectory>/log directory - Version
information saved to a file from <WorkflowServerDirectory>/bin/getversion.bat (or getversion.sh) - An
exported Workflow project that was being designed or deployed when the error occurred
WKC.010.0002 BusinessMonitor:: failed to <register/update> StepInfo object for stepKey <workflowStepKey>.

Cause: A database error occurred during the registration/update of the StepInfo object.

WKC.010.0003 BusinessMonitor:: failed to delete StepInfo entry for stepKey <workflowStepKey>.

Cause: A database error occurred during the deletion of the StepInfo object.
WKC.010.0004 BusinessMonitor:: failed to register ProcessInfo entry for processId <processID>.

Cause: A database error occurred during the registration of the ProcessInfo object.
WKC.010.0005 BusinessMonitor:: failed to delete ProcessInfo entry for processId <processID>.

Cause: A database error occurred during the deletion of the ProcessInfo object.
WKC.010.0006 BusinessMonitor:: failed to find all StepInfo objects.

Cause: A database error occurred during the search for all StepInfo objects.
WKC.010.0007 BusinessMonitor:: failed to find all ProcessInfo objects.

Cause: A database error occurred during the search for all ProcessInfo objects.

WKC (Common Server)
WKC.012.0001 The Resource Server URL is malformed: "<serviceName>".

Cause: The log server failed to start due to an incorrect URL setting.
Response: Check the classrv.properties file for resource server and log server settings. Re-run the Workflow
Configurator, verify host name and port settings, and restart the Workflow server.
WKC.017.0001 Log Server cannot reach Resource Server.

Cause: The log server failed to start because it cannot reach the resource server.
Response: Check server logs for any other error messages that occurred earlier. Check the classrv.properties file
for server settings. Re-run the Workflow Configurator, verify host name and port settings, and restart the
Workflow server.
WKC.017.0002 Connection to Log server is down.

Cause: The client cannot reach the log server.
Response: Check for network connectivity issues. Verify that the log server is running; if it is not, restart the
Workflow server.
WKC.017.0003 Unable to reach the Log Server.

Cause: The client side proxy cannot reach the log server.
Workflow server.
WKC.017.0004 Unable to reach the Resource Server.

Cause: The client cannot reach the resource server.
Workflow server.
WKC.017.0005 No URL for Log Server service.

Cause: Cannot find the URL for the Log Server service.
Response: Check the classrv.properties file for log server settings. Verify that the resource server is running.
Re-run the Workflow Configurator, verify host name and port settings, and restart the Workflow server.
WKC.020.0004 BusinessMonitor cannot publish event: <eventType>.

Cause: The BusinessMonitor component does not have permission to publish the specified event type.
Response: Check the WorkflowMonitor client group on the broker for publishable events. Verify that the
Workflow Configurator ran successfully. Check the workflow_events.adl file for the WorkflowMonitor client
group.

WKC.020.0005 BusinessMonitor cannot publish event: <eventType>.

Cause: The BusinessMonitor component does not have permission to publish the specified event type.
group.
WKC.020.0006 BusinessMonitor cannot subscribe for event: <eventType>.

Cause: The BusinessMonitor component does not have permission to subscribe to the specified event type.
group.
WKC.021.0001 There is no RMI service bound at "<serviceName>".

Cause: The log server failed to start because it cannot find any binding of the resource server.
Response: Check the classrv.properties file for resource server and log server settings. Verify that the Workflow
Configurator ran successfully with the correct host name and port settings. Restart the Workflow server.
WKC.021.0002 Unable to bind Log Server service name "<serviceName>".

Cause: The log server failed to start because it cannot register itself in the RMI registry with the specified
service name.
Response: Check the classrv.properties file for resource server and log server settings. Verify that the Workflow
Configurator ran successfully with the correct host name and port settings. Restart the Workflow server.

WKE (Resource Server)
WKE.002.0001 Unable to create file "<propertyFileName>".

Cause: Workflow Server is getting an error when attempting to update the properties file.
Response: Set the Workflow Administrator log level to VERBOSE for all servers, try to reproduce the problem,
and save the logs as text files. Then send the following information to Customer Care: - Copies of all logs in the
<WorkflowServerDirectory>/log directory - Version information saved to a file from
<WorkflowServerDirectory>/bin/getversion.bat (or getversion.sh) - An exported Workflow project that was
being designed or deployed when the error occurred
WKE.002.0002 Unable to create directory <libDirThatClassServerIsCreating>.

Cause: The server is attempting to initialize a lib directory and cannot create it.
WKE.003.0001 Unable to get icon for "<iconKey>".

Cause: Cannot retrieve the icon for the Workflow Client Manager.
Response: Check to see if the installation has been corrupted. A reinstallation may be required.
WKE.007.0001 A client is attempting to remove a host <hostnameToDelete> which cannot be found in <hostnameToDelete>
in classrv.hostNames property.
Cause: The client is attempting to remove a host that does not exist in the properties.
Response: Check to see if the host name was spelled correctly.
WKE.007.0002 The required property "<propertyKey>" is not set. This server is exiting.
Cause: A required property is not configured.
Response: Run the Workflow Configurator.
WKE.007.0003 Property not found: "<propertyKey>".

Cause: An optional property was not found.

WKE.007.0004 Property is empty: "<propertyKey>".

Cause: A property key is present but has no associated value.
WKE.010.0001 Failed to find HostInfo database for host <hostName>.

Cause: Property information for the host does not contain database information.
WKE.011.0001 The following is not a directory. Please remove: <directoryName>.

Cause: The server lib directory exists but is not a directory.
WKE.011.0002 No jars are defined for application "<applicationName>". The server is exiting.
Cause: The properties for this application do not include any code jars.
WKE.011.0003 No jars are defined for server type "<serverKey>". The server is exiting.
Cause: The properties for this server do not include any code jars.
WKE.011.0004 Host is not defined: "<hostName>".

Cause: The host indicated for a server cannot be found in the configured host list.
Response: Check to see if the host name you entered was spelled correctly.
WKE.011.0005 Type is not defined: "<serverType>".

Cause: The server type name indicated in the server properties is not known.
Response: Check the type name in classrv.properties to see if it is spelled correctly.
WKE.012.0001 Too many command line arguments.

Cause: The server startup command is incorrect.

WKE.020.0001 Project Class Loader: versionMapping is null.

Cause: A client is attempting to load a project class loader without a version mapping.
WKE.020.0002 Project Class Loader: Missing project version.

Cause: A client is attempting to load a project class loader without specifying a valid project version.
WKE.020.0003 DeploymentListenerImpl not initialized

Cause: The DeploymentListenerImpl code has not been initialized properly.
WKE.020.0004 Null cache path.

Cause: The DeploymentListenerImpl was not initialized with a valid cache path.
WKE.020.0005 Cache dir "<cacheDirectory>" does not exist.

Cause: The cache directory specified by the client initialization does not exist or is not accessible.
Response: Check the status of the indicated directory.

WKE.020.0006 No active versions of this project <projectName>.

Cause: Workflow attempted to load a project class loader for a project with no active versions.
Response: Deploy and activate the project.
WKE.020.0007 Invalid project specification <projectSpecification>

Cause: Workflow attempted to load a project class loader with an invalid project specification.
WKE.020.0008 CSNotifierBasic.createNotifier: undefined broker host name.

Cause: The broker host property is not defined.
Response: Configure the broker.
WKE.020.0009 CSNotifierBasic.CSNotifierBasic: has no permissions to publish <eventToPublish>

Cause: The client does not have permission to publish the event.
Response: Configure the broker.
WKE.020.0013 Missing user credentials.

Cause: A client without user credentials has attempted to invoke the class server.
Response: Check to see if the user should be allowed permission to access the server.
WKE.020.0014 Failed to reach authentication server after <numberOfRetries> attempts.

Cause: The host name may be spelled incorrectly, the authentication server may not have been started, or there
may be a network problem.

WKE.020.0015 Failed to reach authentication server after <numberOfRetries> attempts.

Cause: The authentication server may be down. Check to see if the server has been started.
WKE.020.0016 Unable to verify user credentials.

Cause: Cannot verify user credentials with the authentication server.
WKE.020.0017 Cannot decrypt value.

Cause: Alias values cannot be decrypted.



WKE.020.0021 Cannot decrypt value

WKE.020.0022 MISSING LOGGING PROPERTIES <missingLoggingProperties>

Cause: One or more properties required for logging is missing.
Response: Run the Workflow Configurator to configure logging properties.
WKE_020_0023 AliasJComboBox.setModel: require AliasComboModel but got <ClassName>.

Cause: The wrong type of model was used for the combo box.
WKE_020_0024 CSListener.CSListener: has no permissions to subscribe to workFlow::Classrv::PropertyChange.

Cause: The listener could not access this class.
WKE_020_0025 CSListener.CSListener: eventHandler is null

Cause: The listener initialized with a null eventHandler.

WKE_020_0026 WfDeployerImpl.getProjectJar(<jarFileName>, <versionNumber> ) Could not Retrieve Jar.

Cause: The requested jar file was null or had a size of zero.
Response: Check that the jar file exists and is not empty.
WKE_020_0027 WfDeployerImpl.getProjectJar(<sharedProjectName>, <versionNumber>) Could not Retrieve Jar.

Response: Check that the jar file exists and is not empty.
WKE_020_0028 WfDeployerImpl.getProjectJar(<projectName>, <projectVersion> )

Cause: An error occurred while trying to export the project for the specified version.
WKE_020_0029 WfDeployerImpl.getProjectMap(<fileName>, <versionNumber> ) Could not Retrieve project Jar.

Response: Check that the jar file exist and is not empty.
WKE_020_0030 WfDeployerImpl.getProjectMap( <projectName>, <versionNumber> ) Could not parse Jar.

Cause: Error occurred while trying to process the project for the specified version.
WKE_020_0031 WfDeployerImpl.deployProject( <projectName>, <versionNumber> ) Could not deploy Jar.

Cause: An error occurred while trying to deploy the project for the specified version.

WKE_020_0032 WfDeployerImpl.getAliasMap() Could not encode response.

Cause: An error occurred while processing Idata to get the response.
WKE_020_0033 WfDeployerImpl.setAliasMap() invalid IData format.

Cause: An error occurred while processing Idata.
WKE_020_0034 WfDeployerImpl.deleteProject( <projectName>, <versionNumber> )

Cause: An error occurred while locking or deleting the project file.
WKE_020_0035 Unknown error.

Cause: An unknown error occurred during the final import processing of the project file.

Cause: An unknown error occurred during the locking of the project file for import processing.


Cause: An unknown error occurred during the first import processing of the project file.

Cause: An unknown error occurred during the deployment update processing of the project file.
WKE_020_0039 Unable to create/store log images for this deployment.

Cause: An error occurred while trying to store the project file.
WKE_020_0040 Enterprise Wide Data Not Available.

Cause: Unable to load the class loader for importing the project.

WKG (Distribution Control Server)
WKG.009.0028 Cannot convert task start request to broker event: <exception>.

Cause: Failed to convert task information to the broker event.
Response: Ensure that the broker is running, stop Workflow servers and servlets, and run the Workflow
Configurator.
WKG.009.0029 Cannot convert broker event to task start request: <exception>.

Cause: Failed to convert the broker event to the task information.
Response: Ensure that the broker is running, stop Workflow servers and servlets, and run the Workflow
Configurator.
WKG.012.0001 Distribution rule is null.

Cause: The distribution rule passed as a parameter to the comparator is null.
Response: Check DCS logs for an OutOfMemoryError. Increase memory if needed and restart the DCS .
WKG.012.0002 Distribution rule is null.

Cause: The distribution rule passed as a parameter to the comparator is null.
WKG.012.0003 No user identity to perform "same as previous" distribution.

Cause: A user identity is required to perform a "same as previous" task distribution.
Response: Check the model. If the workflow starts via implementation module (IM), the first task cannot be
distributed as "same as previous". Another possibility is an OutOfMemoryError in the process server or DCS.
WKG.012.0004 Invalid task ID <taskID>, expected <taskID>.

Cause: Internal DCS error.
WKG.012.0005 No identity for "same as previous" distribution.

Cause: The user identity required to perform "same as previous" task distribution.
Response: Check the model. If the workflow starts via implementation module (IM), the first task cannot be
distributed as "same as previous". Another possibility is an OutOfMemoryError in the process server or DCS.

WKG.012.0008 Order or Users is null.

Cause: The value for order, number, or users is null in the dynamic distribution rules.
Response: Check the model to verify that the "Failed" outgate of the task is wired.
WKG.012.0009 Role is null.

Cause: The value for role name is null in the dynamic distribution rules.
WKG.012.0010 Invalid role name "<roleName>".

Cause: The value for role name is invalid in dynamic distribution rules
WKG.012.0011 User name is null.

Cause: The value for user name of the distribution rules is null in dynamic distribution rules
WKG.012.0012 RedistributionResult is null.

WKG.012.0013 No user in Authentication Event.

Cause: Invalid notification from authentication server.
WKG.012.0014 No session in Authentication Event.

Cause: Invalid notification from authentication server.
WKG.020.0001 You are already running task <projectName>.<processName>.<taskName>!

Cause: A user attempted to check out a task already checked out by the same user.
Response: If needed, requeue the task.

WKG.020.0002 Task <projectName>:<projectVersion>.<processName>.<taskName> is already locked by <user>.

Cause: A user attempted to check out a task already checked out by the same user.
Response: If needed, requeue the task.
WKG.020.0003 You have already done this task.

Cause: A user attempted to check out a task already executed by the same user.
Response: Check the DCS and Workflow servlet logs for an OutOfMemoryError. If needed, increase the
memory settings and restart the Workflow server.
WKG.020.0004 Task does not match any of your roles.

Cause: A user attempted to check out a task that does not match any of that user's roles.
Response: Check the DCS and Workflow servlet logs for an OutOfMemoryError. If needed, increase the
memory settings and restart the Workflow server.
WKG.020.0005 Unable to checkout task.

Cause: Unexpected error during task checkout.
Response: Check the DCS log for another exception, and verify that the broker and database are running.
WKG.020.0006 Cannot commit task.

Cause: Unexpected error during committing task results.
WKG.020.0007 Cannot release task: <taskID>.

Cause: Unexpected error during task release.
WKG.020.0008 Cannot release task: <taskID>.

Cause: Unexpected error during task release.
WKG.020.0009 User for <userID> not found.

Cause: The user attempting to check out the task is not defined.
Response: Check the broker and authentication server. If the problem persists, restart the authentication server
and DCS.

WKG.020.0010 Unknown event type.

Cause: An unknown broker event was received by the DCS.
Response: Check the broker clients. Most likely something is mistakenly delivering an event to one of the DCS
broker clients.
WKG.020.0011 Cannot perform fetch all request: <errorMessage>.

WKG.020.0012 Unknown event type: <brokerEventType>.

Cause: An unknown broker event was received by the DCS.
Response: Check the broker clients. Most likely something is mistakenly delivering an event to one of the DCS
broker clients.
WKG.020.0013 Cannot checkout message, identity is null.

Cause: The user attempting to check out the task is not defined.
Response: Check the broker and authentication server. If the problem persists, restart the DCS.
WKG.020.0014 Cannot checkout task.

Cause: An unexpected error occurred during task checkout.
Response: Check the DCS log for another exception, check that broker and database are up and running.
WKG.020.0015 Cannot commit message, identity is null.

Cause: The user attempting to commit the task is not defined.
WKG.020.0016 Cannot commit task.

Cause: An unexpected error occurred during task commit.
WKG.020.0017 Cannot release message, identity is null.

Cause: The user attempting to release the task is not defined.

WKG.020.0018 Cannot cancel task.

Cause: An unexpected error occurred during task cancellation.
WKG.020.0019 Cannot close session, identity is null.

Cause: The user attempting to close the session to DCS is not defined.
WKG.020.0020 Problem with session close: <errorMessage>.

Cause: An internal DCS error occurred while closing the session.
Response: Check the DCS log for other errors. Take action accordingly, and restart the DCS.
WKG.020.0027 <taskInfo>: <errorMessage>.

WKG.020.0028 <taskInfo> cannot be viewed by this user.

Cause: Task information was distributed to the wrong user.
Response: Check DCS logs for an OutOfMemoryError. Increase memory settings and restart the DCS and
Workflow servlet.
WKG.020.0029 Instance of DCSUtils already exists.

Response: Restart the DCS.
WKG.020.0030 No instance of DCSUtils.

WKG.020.0034 Missing role name.

Cause: There is a missing role name in the static distribution rule definition.
Response: Regenerate the project.

WKG.020.0035 ID is already pre-assigned (<DCSmessage>).

Cause: This is an internal DCS error. The ID for the DCS message was assigned more than once.
WKG.020.0036 Message already dead.

Cause: This is the second attempt to mark the DCS message as "dead."
WKG.020.0037 Attempt to get active distribution rule for null role.

Cause: This is an internal DCS error. "Null" was passed as a parameter instead of the role name.
WKG.020.0038 Task is not locked by <user>.

Cause: The user attempting to submit the task results has not checked out the task.
Response: Try to submit the task results again. If this fails, requeue the task and run it again.
WKG.020.0039 Cannot perform rollback: outgate not found.

Cause: Incorrectly generated project.
Response: Regenerate the Workflow project.
WKG.020.0040 Incorrect current DCSMessage!

Cause: Internal DCS synchronization error.
WKG.020.0041 Current message: <taskInformation>.

WKG.020.0042 Expected: <taskInformation>.


WKG.020.0043 Incorrect current message.

WKG.020.0044 Unsynchronized operation on DCSMessage!

WKG.020.0045 Unknown distribution.

Cause: The DCS received a request to distribute a task without a specified task ID.
Response: Check process server and DCS logs for errors. Look for OutOfMemoryError, increase memory
settings if needed and restart.
WKG.020.0046 Unknown distribution.

Cause: The DCS received a request to distribute a task without a specified task ID.
Response: Check the process server and DCS logs for errors. Look for an OutOfMemoryError. Increase
memory settings if needed and restart.
WKG.020.0047 No such task: <taskID>.

Cause: The task is obsolete. Refresh the Inbox to remove tasks that are no longer accessible.
Response: Refresh the Inbox. If the problem persists, restart the DCS and the Workflow servlet.
WKG.020.0048 Cannot get maximum ID from outlet storage.

Cause: The document ID cannot be retrieved from the task broker event.
Response: Check the broker and DCS logs for an OutOfMemoryError. Increase memory settings if needed and
restart.
WKG.020.0049 Not supported for TaskRuntime.

Response: Restart the Workflow servlet or the Workflow API container.













WKG.020.0062 Unknown DCS error.

Cause: An unexpected and unknown DCS error occurred.
Response: Check the DCS log for previous errors. Take action accordingly and restart the DCS.
WKG.020.0063 Cannot open session: <exception>.

Cause: A broker error occurred during the opening of the session to DCS.
Response: Check the broker log for errors. Take action accordingly and restart the broker.
WKG.020.0064 Cannot close session: <exception>.

Cause: A broker error occurred during the closing of the session to DCS.
WKG.020.0066 Cannot checkout task: <exception>.

Cause: A broker error occurred during task checkout
WKG.020.0067 Cannot commit task: <exception>.

Cause: A broker error occurred during task commit.
WKG.020.0068 Cannot release task: <exception>.

Cause: A broker error occurred during task release.

WKG.020.0069 Unknown DCS.

Cause: No DCS broker client ID was found for the task.
WKG.020.0070 Unknown message id: <taskID>.

Cause: No DCS broker client ID was found for the task.
WKG.020.0071 Unknown session pool type.

Cause: An internal error occurred in the Workflow servlet or the Workflow client API.
WKG.020.0072 Unknown pool type.

WKG.020.0073 Unknown pool type.

WKG.020.0074 <className>: Unsupported method.

WKG.020.0076 No parent VM.

Cause: An internal error occurred in the process server.
Response: Check the process server log for an OutOfMemoryError. Increase memory settings if needed and
restart the process server.
WKG.020.0077 No distribution rules.

Cause: No distribution rules for the task were found where they were expected.
Response: Check user values for dynamic distribution rules. Regenerate the project if the static distribution
rules failed.

WKG.020.0078 "Stopped" outgate not found.

Cause: Task "stopped" outgate was not found.
WKG.020.0079 Failed to stop task <taskName>.

Cause: The request to stop the task failed.
Response: Check the process server, broker, and database connections.
WKG.020.0080 Failed to cancel task <taskName>

Cause: The request to cancel the task failed.
Response: Check process server broker connections.
WKG.020.0081 Failed to set up distribution request.

Cause: An internal error occurred while creating the task distribution request.
WKG.020.0082 Failed to submit distribution request to the DCS.

Cause: A broker error occurred while publishing the task distribution request.
Response: Check the broker and process server logs for broker connection errors.
WKG.020.0083 Wrong task result.

Cause: A malformed task result was submitted by the DCS to the process server.
Response: Check the DCS, process server, and broker logs for errors, and restart all three servers.
WKG.020.0084 Wrong task result.

Cause: A malformed task result was submitted by the DCS to the process server.
WKG.020.0085 Unknown task distributionID: <taskID>.

Cause: A task result was received for an unknown task. This may happen if a container finishes just before the
task result has been submitted, for example, via a concurrent branch.

WKG.020.0086 Distribution failed outgate not found.

Cause: No outgate was identified for a "failed" task distribution.
WKG.020.0087 Incorrect state <taskState>.

Cause: An incorrect query string was used in the API.
Response: Check the query string used. The state can be "locked," "active," or "queued" only; no other values
are allowed.
WKG.020.0088 No numeric value for <queryVariable>.

Response: Check the query string used. ID, workflowID, containerID, and priority can have numeric values.
WKG.020.0089 Cannot distribute task: <exception>

Cause: An unexpected error occurred during task distribution request processing.
WKG.020.0090 Cannot rollback: <task>. Force destroy.

Cause: A broker error occurred while delivering the task result to the process server.
Response: Restart the process server and the DCS.
WKG.020.0091 No container in task stop request.

Cause: A malformed broker event was sent to the DCS with the stop task request.
Response: Check the broker and process server logs for an OutOfMemoryError. Increase memory settings if
needed and restart.
WKG.020.0093 Context message does not match the existing one.

WKG.020.0094 No current DCS message.


WKG.020.0095 Negative nesting count: <synchronizationCount>

WKG.020.0097 Task[name=<taskName>, container=<containerName>] distribution failed: <errorMessage>.

Cause: Task distribution failed.
Response: Check that the failed task outgate is linked.
WKG.020.0098 No text value for <queryVariable>.

Response: Check the query string.
WKG.020.0099 No date value for <queryVariable>

Response: Check the query string.
WKG.020.0100 No message.
WKG.020.0101 Task <projectName>.<workflowName>.<taskName> is already locked.

WKG.020.0102 Task <projectName>.<workflowName>.<taskName> is already done.

WKG.020.0103 Failed to create project jar cache for DCS.

Cause: Workflow Server failed to create a cache of project jars pulled from the database.
Response: Check the disk space on the Workflow server.

WKG.020.0104 Failed to create create project jar cache: <exception>.

Cause: Workflow Server failed to create a cache of project jars pulled from the database.
WKG.020.0105 No task properties <projectName> version <projectVersion>:<propertyFileName>.

Cause: Workflow Server failed to find task properties.
WKG.020.0106 Too many command line arguments. Usage: java <DCSserver> ServerName.
Cause: The command line to start the DCS was malformed.
Response: Stop Workflow servers and run the Workflow Configurator.
WKG.020.0108 Task is already done.

Cause: An attempt was submitted to finish a task that has already finished.
WKG.020.0109 This is DCS.

Cause: This is an internal DCS error. Illegal code was executed.
WKG.020.0110 This is DCS.

Cause: This is an internal DCS error. Illegal code was executed.
WKG.020.0114 Cannot deliver PDMessage event: <exception>.

Cause: A broker error occurred during task checkout.
Response: Cancel the task and check it out again.
WKG.020.0116 Can not extract role names from open role session event: <exception>.
Cause: A broker error occurred while getting the role name for an open role session broker event.
Response: Check the broker and DCS logs for errors. Take action accordingly and restart both servers.

WKG.020.0117 Can not extract user ID from open user session event: <exception>.
Cause: A broker error occurred while getting the user ID for an open user session broker event.
Response: Check the broker and DCS logs for errors. Take action accordingly and restart both servers.
WKG.020.0118 No message.
WKG.020.0119 No queue item for message <taskID>.

Cause: The task with the specified ID was not found in the internal DCS queue.
WKG.020.0120 Cannot notify role <roleName>.

Cause: A broker error occurred during the notification of the new or removed task for the role.
Response: Check the broker and DCS logs for other errors. Take action accordingly and restart both servers.
WKG.020.0121 Distribution request has no ID.

Cause: Malformed distribution request from process server, task id is missing.
WKG.020.0122 Cannot extract distribution request from <brokerEvent>.

Cause: An error occurred while converting the broker event to the distribution request object.
WKG.020.0123 No task for <taskID> in the database.

Cause: Workflow Server failed to retrieve a task with the specified ID from the database.
Response: Verify that the process server is running.
WKG.020.0124 <user> has no permissions for query commands.

Cause: A user without the proper permissions attempted to query or perform an administrative command with
the DCS.
Response: Use the Workflow Users utility to add Workflow Monitor to the list of tools that the user can run.

WKG.020.0125 Unknown operation [<codeOfOperation>].

Cause: An administrative command with an unknown code was submitted to the DCS.
WKG.020.0126 Cannott change task status: <errorMessage>.

Cause: An error occurred while processing an administrative command to cancel the task.
WKG.020.0127 Cannot update task attributes: <errorMessage>.

Cause: An error occurred while processing an administrative command to update the task attributes
(distribution rules, priority, or description).
WKG.020.0128 Cannot notify user <userID>.

Cause: A broker error occurred during the notification of the new or removed task for the user.
WKG.026.0001 Invalid query: "<QueryString>". <ErrorMsg>

Cause: An invalid query was passed as the parameter of the task cancel request. An attempt to cancel the task
failed.
Response: Check the query string that was passed to the DCS.

Cause: An invalid query was passed as the parameter of the task stop request. An attempt to stop the task
failed.

Cause: An invalid query was passed as the parameter to open a task status cursor request. An attempt to open
the task status cursor failed.
Response: Check the distribution rules that were passed to the DCS.

WKG.026.0004 Unknown task [custom id=<customID>].

Cause: An attempt was made to cancel a task with an unknown custom ID.
Response: Ensure that the correct custom ID has been used. Use Task List Management in My webMethods to
check whether or not the task is running.

Cause: An attempt was made to stop a task with an unknown custom ID.
Response: Verify that the correct custom ID has been used. Use Task List Management in My webMethods to

Cause: An attempt was made to get the status of a task with an unknown custom ID.
Response: Verify that the correct custom ID has been used. Use Task List Management in My webMethods to
WKG.026.0007 Task start failed <ErrorMsg>.

Cause: An attempt to start the task failed.
Response: Check the detailed error message. Possible reasons include database or broker failure and
insufficient memory or disk space.
WKG.026.0008 Invalid distribution rule <DistributionRule>.

Cause: An invalid distribution rule was passed as part of a start task request. An attempt to start the task failed.
WKG.026.0009 Unknown task [id=<taskID>].

Cause: An attempt was made to get the result for a task with an unknown ID.
Response: Verify that the correct task ID has been used. Verify that the DCSWebServiceRequest database table
contains a row with the ID that has been supplied as the task ID.
WKG.026.0010 Task [id=<taskID>] is running.

Cause: An attempt was made to get the result for a task that is still running.
Response: Wait until the task finishes and then get the result.

WKG.026.0011 Unknown task [id=<customID>].

Cause: An attempt was made to get the result for a task with an unknown custom ID.
Response: Verify that the correct custom ID has been used. Verify that the DCSWebServiceRequest database
table contains a row with the ID that has been supplied as the custom ID.
WKG.026.0012 Task [id=<customID>] is running.

Cause: An attempt was made to get the result for a task that is still running.
Response: Wait until the task finishes and then get the result.

Cause: An invalid query was passed as the parameter of a task reassignment request. An attempt to reassign
the task failed.
WKG.026.0014 Invalid distribution rule <DistributionRule>. <ErrorMsg>

Cause: An invalid distribution rule was passed as part of a task reassignment request. An attempt to reassign
the task failed.

Cause: An attempt was made to reassign a task with an unknown custom ID.
WKG.026.0016 Invalid distribution rule <DistributionRule>. <ErrorMsg>

Cause: An invalid distribution rule was passed as part of a task reassignment request. An attempt to reassign
the task failed.

Cause: An invalid query was passed as the parameter of a task description change request. An attempt to set a
new task description failed.


Cause: An invalid query was passed as the parameter of a task priority change request. An attempt to set a new
task priority failed.
WKG.026.0019 Invalid task priority: <taskPriority>.

Cause: An invalid task priority was passed as the parameter of a task priority change request. An attempt was
made to set the task priority to a value less than zero (0).
Response: Check the task priority parameter that was passed to the DCS.

Cause: An attempt was made to change the description of a task with an unknown custom ID.

Cause: An attempt was made to change the priority of a task with an unknown custom ID.
WKG.026.0022 Invalid task priority: <taskPriority>.

Cause: An invalid task priority was passed as the parameter of a task priority change request. An attempt was
made to set a task priority to a value less than zero (0).
Response: Check the task priority parameter that was passed to the DCS.
WKG.026.0023 Unknown task status cursor [cursor id = <cursorID>].

Cause: An attempt was made to fetch a task status with an unknown cursor ID.
Response: Use the correct cursor ID, acquired with the OpenTaskStatusCursor service.
WKG.026.0024 User <userName> has no permissions to perform <operation>.

Cause: An attempt was made to perform an operation without the necessary permissions.
Response: Check the access and functional privileges configured for the user in the authentication system used
with webMethods Workflow. Verify that the user has permission to use Task List Management.

WKG.026.0025 User <userName> has no permission to start task.

Response: Use the Workflow Users tool to grant the user permission to run the Workflow Inbox.
WKG.026.0026 User <userName> has no permission to get task result.

Response: Use the Workflow Users tool to grant the user permission to run the Workflow Inbox.

WKH (HTTP Server)
WKH.002.0001 <resourceName> : error writing response: <exceptionDescription>.

Cause: Network connectivity issues.
Response: Check the network status and restart all servers. If the problem persists, contact your system
administrator.
WKH.003.0001 Could not find file on any paths: <resourceName>.

Cause: A required resource is missing, or the client submitted a bad request.
Response: Check the installation and restart all servers. If the problem persists, contact your system
administrator.
WKH.012.0003 "<jarName>" does not contain "<resourceName>".

Cause: A required resource is missing, or the client submitted a bad request.
Response: Check the installation and restart all servers. If the problem persists, contact your system
administrator.
WKH.013.0001 Class Server died: <exceptionDescription>.

Cause: Network connectivity issues.
Response: Check the network status and the product configuration (HTTP port number) and restart all servers.
If the problem persists, contact your system administrator.
WKH.020.0001 Exception encountered <exceptionType> : <exceptionMessage>.

Cause: A required jar file was either not found or is corrupted.
Response: Check the installation, and verify the path and jar name.
WKH.022.0001 Unable to start ClassServer: <exceptionMessage>.

Cause: Network connectivity or configuration issues.
Response: Check the network status and the product configuration (HTTP port number) and restart all servers.
If the problem persists, contact your system administrator.
WKH.024.0001 Access denied to: <fileName>.

Cause: A client requested a file outside of the root path.
Response: Check the product configuration and restart all servers. If the problem persists, contact your system
administrator.

WKK (Event Subscription Support)
WKK.009.0001 No ESRuntime instance.

Cause: No instance of ESRuntimer is set for the JVM.
Response: Restart Workflow servers, the Workflow servlet, and the Workflow API container, if used.
WKK.009.0002 Invalid SSL password.

Cause: An invalid password was submitted to access the SSL certificate.
Response: Run the Workflow Configurator or use the Workflow Client Manager to set the correct password.
WKK.009.0004 Subscription [<brokerEventType>] is not permitted.

Cause: The broker client group has no permissions to subscribe.
Response: Stop Workflow servers, run the Workflow Configurator, then restart the Workflow servers.
WKK.009.0005 Broker Permissions Exception :<exception>.

Cause: The Workflow Server has no permission to connect to the broker.
WKK.009.0006 Broker Communication Failure Exception:<exception>.

Cause: A broker communication error occurred.
Response: Restart the broker and Workflow servers.
WKK.009.0007 Broker Host not found Exception:<exception>.

Cause: The broker host was not found.
Response: Run the Workflow Configurator and verify that the configuration is pointing to the correct host.
Check the network for connectivity issues.
WKK.009.0008 Broker Not Running Exception:<exception>.

Cause: The broker is not running.
Response: Start the broker.
WKK.009.0009 Broker Security Exception:<exception>.

Cause: A broker security error occurred.
Response: Restart the broker.

WKK.009.0010 Broker Client Group Exception:<exception>.

Cause: Unknown broker client group.
WKK.009.0011 Cannot create new Broker Client: <exception>.

Cause: A broker error occurred while establishing a new connection.
Response: Stop Workflow servers, run the Workflow Configurator, then restart the Workflow servers and the
broker.
WKK.009.0012 Cannot register connection callback.

Cause: A broker API error occurred that prevents broker callback registering.
Response: Restart all Workflow servers, servlets, and API containers.
WKK.009.0013 Cannot acknowledge event = <exception>.

Cause: A broker API error occurred during event acknowledgment.
Response: Restart Workflow servers.
WKK.009.0014 Cannot check subscription: <exception>.

Cause: A broker error occurred while checking a subscription.
broker.
WKK.009.0015 Cannot register callback: <exception>.

Cause: A broker error occurred while registering a callback.
broker.
WKK.009.0016 Cannot register callback for subscription ID: <exception>.

Cause: A broker error occurred while registering a callback.
broker.

WKK.009.0017 Cannot check permissions to subscribe: <exception>.

Cause: A broker error occurred while checking subscription permissions.
broker.
WKK.009.0018 Cannot check permissions to publish: <exception>.

Cause: A broker error occurred while checking permissions to publish.
broker.
WKK.009.0019 Cannot make unique subscription ID: <exception>.

Cause: A broker error occurred while creating a unique subscription ID.
broker.
WKK.009.0020 Cannot make transaction ID: <exception>.

Cause: A broker error occurred while creating a transaction ID.
broker.
WKK.009.0021 Cannot get the list of subscriptions: <exception>.

Cause: A broker error occurred while getting a list of subscriptions.
broker.
WKK.009.0022 Cannot registerCallbackForSubId: <exception>.

Cause: A broker error occurred while registering a callback for a subscription ID.
broker.
WKK.009.0023 Cannot subscribe to <brokerEventType> : <exception>.

Cause: A broker error occurred during an event subscription.
broker.

WKK.009.0024 Cannot cancel subscription to <brokerEventType>: <exception>.

Cause: A broker error occurred during a subscription cancellation.
broker.
WKK.009.0025 Cannot publish event : <exception>.

Cause: A broker error occurred while publishing an event.
broker.
WKK.009.0026 Cannot deliver event : <exception>.

Cause: A broker error occurred while delivering an event.
broker.
WKK.009.0027 Cannot deliver event: <exception>.

Cause: A broker error occurred while delivering an event.
broker.
WKK.009.0028 Cannot disconnect: <exception>.

Cause: A broker error occurred while disconnecting a broker client.
Response: Restart Workflow servers and the broker.
WKK.009.0029 Cannot destroy: <exception>.

Cause: A broker error occurred while destroying a broker client.
Response: Stop the Workflow server and destroy the client using the Broker Administrator.
WKK.009.0031 Cannot connect to [<brokerName>@<brokerHost>].

Cause: A broker connection cannot be established.
Response: Verify that the broker is running. Stop Workflow servers, run the Workflow Configurator, and
restart the broker and the Workflow server.

WKK.009.0034 Invalid SSL certificate file.

Cause: Invalid file name for SSL certificate.
Response: Run the Workflow Configurator or use the Workflow Client Manager to specify the correct file
name.
WKK.009.0035 No <brokerConnectionProperty>.
Cause: No broker connection property could be located.
Response: Stop Workflow servers and run the Workflow Configurator.
WKK.009.0036 Cannot get broker definitions from adl resource: <exception>.

Cause: Broker definitions are not accessible.
Response: Verify that the file WorkflowServer/etc/workflow_events.adl exists. If it does, run the Workflow
Configurator. If it does not, reinstall Workflow.
WKK.009.0039 No brokers on <brokerHost>.

Cause: No brokers are defined on the specified host.
Response: Create at least one broker.
WKK.009.0041 No events definition found.

Cause: No event types are defined.
WKK.009.0042 Argument must be ESClient instance.

Cause: An internal error occurred while creating a broker event.
Response: Restart all Workflow servers, servlets, and API containers.
WKK.009.0043 Event is null.

Cause: An event was null when attempting to convert it to a Java object.
Response: Check logs for an OutOfMemoryError. Restart Workflow servers, servlets, and API containers.
WKK.009.0044 Object is null.

Cause: An object was null when attempting to convert it to a broker event.
Response: Check logs for an OutOfMemoryError. Restart Workflow servers, servlets, and API containers.

WKK.009.0045 Cannot get event from object: <object>.

Cause: The converter from the object to the broker event was not found.
Response: Stop the Workflow servers and run the Workflow Configurator.
WKK.009.0046 Cannot put event to object: <object>.

Cause: The converter from the broker event to the Java object was not found.
Response: Stop the Workflow servers and run the Workflow Configurator.
WKK.009.0047 Broker field name is null.

Cause: The broker field name was null when setting a value in a broker event.
Response: Restart the Workflow servers.
WKK.009.0048 Cannot set field[<brokerEventFieldName>] in event with unknown type.

Cause: A value was set in an untyped broker event without specifying the field type.
Response: Check logs for an OutOfMemoryError. Restart the Workflow servers.
WKK.009.0049 Cannot set date field [<brokerFieldName>=<brokerFieldValue>].

Cause: Failed to set a value into a date type field of the broker event.
Response: Restart the broker and the Workflow servers.
WKK.009.0050 Cannot get date value: <brokerFieldName>.

Cause: Failed to get the value of a date type field of the broker event.
WKK.009.0051 Cannot get integer value: <brokerFieldName>.

Cause: Failed to get the value of an integer type field of the broker event.
WKK.009.0052 Cannot get value of the field [<brokerFieldName>]: <exception>.

Cause: Failed to get a value of a field of the broker event.

WKK.009.0053 Cannot create event [type = <brokerEventType>].

Cause: Failed to create a broker event.
Response: Stop the Workflow servers and run the Workflow Configurator. Restart the broker and the
Workflow servers.
WKK.009.0054 Failed to acknowledge untyped event: <brokerEventType>.

Cause: An attempt was made to acknowledge an event that is untyped (not defined on the broker).
Response: Stop the Workflow servers and run the Workflow Configurator. Restart the broker and the
Workflow servers.
WKK.009.0055 Failed to create Activation ID: <activationID>.

Cause: An attempt to create an activation id has failed, external process will not be able to control this
workflow object
Response: Use the Task List Manager to verify that the process ID was created. The process can be deleted and
a new one started. The process will run but can not be controlled or tracked.
WKK.100.0003 ESSUBSCRIBER: found subscription for <MessageType>[ <SequenceNumber> ]. Event details-

><MessageDetails>
Cause: This message contains detailed broker event information used to track broker event flow in Workflow.
Response: None. Debug message.
WKK.100.0083 Failed to decode Activation ID: <activationID>.

Cause: An attempt to decode an activation ID has failed. This message provides notification of failed action of
an external process with a bad ID.
Response: None. Debug message.

WKN (Object Relational Mapping)
WKN.020.0052 An error was seen deleting references on key <keyValue> for reference class <className>:
Cause: Either something went wrong with the database connection, or possibly an unexpected constraint
violation prevented the delete operation.
Response: Check the log in which this message occurred for subsequent messages indicating loss of database
connectivity. If the error is related to database connectivity, contact your DBA for assistance. Otherwise, run
"java -jar ormutils.jar >ormdump.txt" from the WorkflowServer\lib directory then send the resulting file,
ormdump.txt, to Customer Care with the following additional information: - Copies of all logs in the
<WorkflowServerDirectory>/bin/getversion.bat (or getversion.sh)
WKN.020.0053 An error was encountered while executing prepared statement "<SQLStatementTemplate>":

Cause: Either something went wrong with the database connection or possibly the current database schema is
inconsistent with the usage of the SQL statement shown.
WKN.020.0054 An error was seen in deletion for key <keyValue> with mapping class <className>:
Cause: Either something went wrong with the database connection or possibly an unexpected constraint
violation has prevented the delete operation.
WKN.020.0055 The supplied value for primary key was null.

Cause: This error indicates a very serious and unexpected bug.

WKN (Object Relational Mapping)
WKN.020.0056 Error "<JDBC-DriverErrorMessage>" was seen while executing SQL "<SQLStatementTemplate>".

Cause: The specified error occurred during an attempt to execute the specified SQL, either because the
database connection was lost or because some more serious and unanticipated error occurred.
WKN.020.0057 An error occurred executing prepared statement "<SQLStatementTemplate>":

Cause: The specified error occurred during an attempt to execute the specified SQL, either because the
database connection was lost or because some more serious and unanticipated error occurred.
WKN.020.0058 SQLConnectionFactory required file not found

Cause: The po.properties file cannot be found.
Response: This should never happen, but if it does a harmless fix is to stop the Workflow server, run the
Workflow Configurator, and restart the Workflow server.

WKO (Inbox)
WKO.007.0001 The required property <propertyName> is missing.

Cause: The required property has not been configured.
Response: Attempt to reconfigure the property.
WKO.007.0002 Client Table Headers are null.

Cause: The client has not been configured correctly.
Response: Reconfigure client table parameters.
WKO.007.0003 Client Table Widths are null.

Cause: The client has not been configured correctly.
Response: Reconfigure client table parameters.
WKO.012.0005 URL for Resource Server is null.

Cause: The URL configured for the resource server is null.
Response: Reconfigure the Workflow client.
WKO.012.0006 Invalid client type <invalidClientType>.

Cause: An attempt was made to instantiate a client of unknown type.
WKO.012.0007 No authentication token.

Cause: A client attempted to log on without authentication.

WKO (Inbox)
WKO.012.0008 Cannot load deployment information for project <projectName> version <projectVersion> : <error>.
Cause: The project is missing deployment information.
WKO.012.0009 Headers and widths length mismatch in client table configuration.

Cause: There is a mismatch in the client table configuration.
WKO.012.0010 Null parent.

Cause: The client Inbox has a null parent frame.
WKO.012.0011 ERROR: unexpected template <templateName>.

Cause: The servlet received an invalid template.
WKO.012.0012 URL for Resource Server is null.

Cause: The URL configured for the resource server is null.
Response: Reconfigure the Workflow client.

WKO.012.0017 Cannot get classloader for [<projectName>:<projectVersion>].

Cause: Cannot instantiate the project class loader for the specified project.
Response: Verify that the specified project is active. Set the Workflow Administrator log level to VERBOSE for
all servers, try to reproduce the problem, and save the logs as text files. Then send the following information to
Customer Care: - Copies of all logs in the <WorkflowServerDirectory>/log directory - Version information
saved to a file from <WorkflowServerDirectory>/bin/getversion.bat (or getversion.sh) - An exported Workflow
project that was being designed or deployed when the error occurred
WKO.012.0018 Cannot get deployment info for [<projectName>:<projectVersion>].

Cause: Cannot load deployment information for indicated project.
Response: Verify that the specified project is active. Set the Workflow Administrator log level to VERBOSE for
all servers, try to reproduce the problem, and save the logs as text files. Then send the following information to
WKO.012.0019 Null project name.

Cause: The client attempted to start a project with a null name.
Response: Verify that menus contain valid actions.
WKO.012.0020 Null process name.

Cause: The client attempted to start a process with a null name.
Response: Verify that menus contain valid actions.
WKO.012.0021 Cannot load client menus from the server.

Cause: The client cannot load menus from the server.
WKO.012.0022 No user ID was specified.

Cause: A user attempted to log on to the servlet with no user ID.
Response: User ID is required for to log in.

WKO (Inbox)
WKO.012.0023 No password was specified.

Cause: A user attempted to log on to the servlet with no password.
Response: A password is required to log in.
WKO.012.0024 Logging in to server "<resourceServerHost>" as user "<userID>" failed.

Cause: Login failed.
Response: Check to see if the user name was spelled correctly and if the host name and port are correct.
WKO.012.0026 Task <taskID> is no longer available.

Cause: The user has requested a task that is no longer available.
Response: Request an available task.
WKO.012.0027 Password does not meet minimum length of <requiredMinimumLength>.

Cause: The user has entered a new password that is shorter than the minimum length required.
Response: Enter a password that meets the length requirement.
WKO.012.0028 Unable to fully validate password.

Cause: An error occurred while attempting to validate a new password.
WKO.013.0001 Not done!

Cause: Illegal state of task VM.

WKO.013.0002 Failed to complete task.

Cause: An error occurred when attempting to complete a task.
WKO.013.0003 Task cannot complete. <errorMessage>

Cause: An error occurred when completing task
WKO.016.0001 You're not allowed to run the client (try changing client type in Workflow Users).
Cause: The user attempting to log in does not have permission to access the client.
Response: Verify that the user logging in has been added and given right to access the client.
WKO.016.0002 User isn't logged in.

Cause: The requested client is not logged onto this session.
Response: Check the session to see if it timed out. Also try logging this client out and then back in.
WKO.020.0002 Task is already running.

Cause: An attempt was made to start a task that was already running.

WKO (Inbox)
WKO.020.0004 Cannot load client menu.

Cause: An error occurred while loading a client menu.
WKO.020.0005 Failed to start process <processName>( version <projectName>).<projectVersion> .

Cause: An error occurred while trying to start the process.
Response: Check that the process server is running. If not, start it.
WKO.020.0006 Failed to connect to dispatcher.

Cause: An error occurred while connecting to the server.
Response: Check that servers are running and reachable. Set the Workflow Administrator log level to
VERBOSE for all servers, try to reproduce the problem, and save the logs as text files. Then send the following
information to Customer Care: - Copies of all logs in the <WorkflowServerDirectory>/log directory - Version
WKO.020.0007 Failed to refresh inbox.

Cause: An error occurred while attempting to refresh the Inbox.
WKO.020.0008 Cannot start task.

Cause: The task failed to start.

WKO.020.0009 Cannot release task.

Cause: The task failed to start and cannot be released.


WKO.020.0012 Cannot release the task.

Cause: Task cancellation failed.
WKO.020.0013 Cannot complete task.

Cause: The task failed to complete.

WKO (Inbox)
WKO.021.0001 Cannot establish session with auth server.

Cause: An error occurred while attempting to establish an authentication server session.
WKO.021.0003 Cannot get session pool from dcs.

Cause: An error occurred while getting a session pool from the DCS.
WKO.022.0001 Cannot Start process: <processName>.

Cause: An error occurred while starting a process.
WKO.022.0002 Cannot open session to dcs:<Exception>.

Cause: An error occurred when attempting to establish a DCS server session.
Response: Verify that the servers are running and reachable.
WKO.022.0003 Cannot start <version> client: <error>.

Cause: The client could not start.

WKO.022.0004 Cannot start process <projectName> (version <projectVersion>).<processName>.

Cause: An error occurred while starting the process.
Response: Verify that the project is active and that the process exists.
WKO.022.0005 Cannot load task: <taskName>.

Cause: An error occurred while starting the task.
Response: Verity that the project is active and that the task exists.
WKO.022.0007 Cannot start process: [project=<projectName>(<projectVersion>),process=<processName>].

Cause: The process cannot be started because of an invalid project/process specification.
Response: Check menus for appropriate actions. Set the Workflow Administrator log level to VERBOSE for all
servers, try to reproduce the problem, and save the logs as text files. Then send the following information to

Cause: An error occurred while starting a task.
WKO.022.0009 Cannot execute <menuActionName>.

Cause: A menu action cannot be executed.
Response: Verify that the menu action is valid. Set the Workflow Administrator log level to VERBOSE for all
servers, try to reproduce the problem, and save the logs as text files. Then send the following information to

WKO (Inbox)
WKO.022.0010 Cannot start process.

Cause: An error occurred while starting a process.
WKO.022.0011 cannot execute task <taskName> :

WKO.022.0012 Cannot start task. <errorMessage>

WKO.022.0013 Start pending task.

Cause: The client cannot start a task that is already pending.
Response: Start another task.
WKO.022.0014 Cannot start process.

Cause: An error occurred starting a process from a menu.
Response: The menu should contain valid actions for active projects.

WKO.023.0001 Not on event dispatch thread.

Cause: Task VM is in an invalid state.
WKO.023.0007 No task is activated <taskNumber>.

Cause: The task could not be accessed because no such task is active.

WKP (Process Server)
WKP.001.0034 Failed to suspend or resume Process for ID:<ID Number>.

Cause: The process ID was invalid. The ID did not match any of the currently running or loaded processes.
Response: Use the Task List Manager to check whether this process ID is running or suspended.
WKP.001.0035 "Failed to stop Process for ID:<ID Number>."

Cause: The process could not be stopped. The ID may be incorrect, or the user may not have permission to
control this process.
Response: Use the Task List Manager to verify that the process ID is running. Check the role information for the
user's right to control the process.
WKP.020.0004 ActivityLogEvent::toEvent failed: <exception>.

Cause: Broker API error.
WKP.020.0005 ActivityLogEvent::fromEvent failed: <exception>.

WKP.020.0006 Unable to start a new process. An active process was already started by event [<ProcessStartEvent>].
Cause: An attempt was made to start an instance of a process that was already running.
Response: No action is needed.
WKP.020.0007 Parameter has not been registered [id=null].

Cause: The parameter has not been registered.
Response: Check the broker queue storage and restart the broker.
WKP.020.0008 Field has the wrong type.

Cause: The field has the wrong type.
Response: Check the broker queue storage and restart the broker.

WKP.020.0009 Wrong parameter [id=<id>,class=<classname>].

Cause: Broker error.
WKP.020.0014 ProcessStartEvent::toEvent failed: <exception>.

Response: Restart the process server.
WKP.020.0015 ProcessStartEvent::fromEvent failed: <exception>.

WKP.020.0016 Unknown result: <brokerEvent>.

Cause: An unknown event type was received by the process server.
Response: Check the broker configuration for the ProcessServer client group.
WKP.020.0019 Wrong ProcessTransition [modelID=<modelID>, targetID=<targetID>].

Cause: The values inside the event are not set.
Response: Check the PRT log for errors.
WKP.020.0020 Wrong ProcessTransition [modelID=<modelID>, targetID=<targetID>].

Cause: The values inside the event are not set.
WKP.020.0021 Cannot load project information from jar for <project>.

Cause: The project was not generated correctly.
WKP.020.0022 Cannot get project information from class server.

Cause: The resource server is not running.
Response: Restart the resource server.

WKP.020.0023 Cannot load project information from jar for <ProjectVersionInfo>.

WKP.020.0024 Cannot get value for ingate # <ingate> index # <paramIndex> event <exception>.
WKP.020.0025 Cannot get value for ingate # <gate> event <eventType>.

WKP.020.0029 Wrong iteration: <businessContext>.

Cause: The iteration value is not set in the process transition event.
WKP.020.0030 Failed to get target step ID from PTE, <exception>.

WKP.020.0032 Wrong <PEInfo>.

Cause: The project containing this workflow was generated incorrectly.
Response: Regenerate the project associated with this workflow.
WKP.020.0033 Wrong mapping index for <PEInfo>.

WKP.020.0034 Cannot convert document <result> to <typeName> Error: <RTException>.

Cause: The broker event structure was changed.
Response: Remove the subscription to the broker event and redeploy the project.

WKP.020.0035 Operation is not implemented yet.

Cause: The project which contains this workflow was generated incorrectly.
WKP.020.0036 No client ID to deliver result.

WKP.020.0037 No deliver/publish type defined for attribute #<int>.

WKP.020.0038 Wrong <InputEventInfo>.

WKP.020.0039 Not implemented.

WKP.020.0040 No bin data.

Cause: An empty pipeline was sent to the broker from the process runtime.
WKP.020.0041 Unknown rule type: <type>.

Cause: The generated project is corrupted.
Response: Regenerate the Workflow project that contains this process.
WKP.020.0042 <RTUser> has no permissions to perform the command.

Cause: The user attempting to perform the operation is not authorized to do so.
Response: Grant the user permission to run Workflow Monitor.

WKP.020.0043 Unknown operation [<operation>].

Cause: The requested operation type was not recognized by the process server.
Response: Resubmit the request with the correct operation type.
WKP.020.0044 No client ID: <exception>.

WKP.020.0045 Event sequence number <seqNum> not found in table.

Cause: Out of memory error.
WKP.020.0046 Business Context is null for <ProcElement>.

WKP.020.0047 Exception on publishing <BCONSOLE_EVENT> : <exception>.

WKP.020.0048 Exception on publishing <BCONSOLE_EVENT> : <exception>.

WKP.020.0049 Failed to obtain active processes from table, <exception>.

WKP.020.0050 Failed to publish active processes list, <exception>.


WKP.020.0051 Exception on publishing <stepIteration> : <exception>.

WKP.020.0053 Error in ChangeCommand processing: <exception>.

Cause: An incorrect command was issued by webMethods Monitor
Response: Check webMethods Monitor for errors.
WKP.020.0054 Exception in event handler: <exception>.

WKP.020.0055 Failed to acknowledge event: <eventType>, <eventMessage>.

WKP.020.0056 ProcessInstanceID is null.

Cause: An incorrect command was issued by webMethods Monitor.
WKP.020.0057 The action is null.

WKP.020.0058 Unknown Action: <action>.

WKP.020.0065 Invalid token <token>.

Cause: The query syntax is incorrect.
Response: Double check the syntax of the query string.

WKP.020.0070 Unable to perform comparison.

WKP.020.0071 Unable to perform comparison.

WKP.020.0072 Unable to register persistent component: <exception>.

Cause: Database error.
WKP.020.0073 Unable to release persistent components: <exception>.

WKP.020.0074 Unable to activate persistent component nodeID = <nodeID> : <exception>.

WKP.020.0076 No persistent component nodeID = <nodeID>.

WKP.020.0078 The container has not been registered yet.

Cause: An attempt was made to use a which had not been stored in the database.
Response: Check the database, check for other errors and restart the process server.
WKP.020.0084 Attempt to register container failed.

Cause: There is a problem with the database.
Response: Check the database and restart the process server.

WKP.020.0085 Attempt to execute rollback failed.

Response: Check the database and restart the process server.
WKP.020.0086 External event container id mismatch received <id>, expected <id>.

Cause: An event was sent to the wrong process.
Response: Check the log for "out of memory" errors. Increase the memory if needed and restart the process
server.
WKP.020.0087 Error while processing event <event> for <stackTrace>.

Cause: An error, which was possibly corrected, occurred during execution of the workflow.
Response: Look for other messages in the log. If you find a message that the database was rolled back, restart
the server. Otherwise, the message can be ignored.
WKP.020.0088 Unable to modify context.

Response: Check the database and restart the Workflow server.
WKP.020.0089 Unable to remove component.

WKP.020.0090 Unable to delete container.

WKP.020.0096 The process dispatchers maximum number of attempts has been reached.
Cause: An error occurred while processing the workflow, and the database attempted to roll back the
transaction.
Response: Check the workflow log for previous errors.
WKP.020.0097 The process dispatcher has executed a rollback.

Cause: An error has occurred during the workflow execution.
Response: Check the workflow log for previous errors.

WKP.020.0098 The process dispatcher was unable to perform a rollback <exception>.

Response: Check the database and then restart the process server.
WKP.020.0103 Failed to create process root in database.

Response: Check that the database is available and restart the process server.
WKP.020.0104 The ID has already been assigned to (<class>).

WKP.020.0106 The resource server URL could not be determined.

Cause: The initialization context passed to the process server by the server manager during start is invalid.
Response: Check the server manager log and restart the process server.
WKP.020.0107 Unable to start the RMI server.

Cause: The process server could not be started.
Response: Check the database and broker and run the Workflow Configurator.
WKP.020.0108 No public key.

WKP.020.0109 An attempt was made to verify empty user credentials.

WKP.020.0110 Unable to verify user credentials.


WKP.020.0111 An attempt was made to verify a role which does not exist
Cause: The task distribution rules failed.
Response: Check the variable that was used for dynamic distribution.
WKP.020.0112 Invalid role name "<roleName>".

Cause: The task distribution rules failed.
Response: Check the variable that was used for dynamic distribution.
WKP.020.0113 Unable to deliver event.

WKP.020.0114 While trying to deliver and event, the attempt to get the event [<eventName>] failed.
Cause: This will occur if you did not run the Workflow Configurator after upgrading.
Response: Run the Workflow Configurator. Restart the broker and the process server.
WKP.020.0115 Attempt to create broker connection failed.

Cause: Either the broker is not running or Workflow has not been configured to used the correct broker.
Response: Make sure the broker is running. Run the Workflow Configurator and confirm that the correct
broker has been defined.
WKP.020.0116 Attempt to establish reference to a broker connection failed.

WKP.020.0117 Attempt to establish reference to a shared broker connection failed.

WKP.020.0119 Unable to find root for process instance ID <processID>.

Cause: Memory corruption or database error.

WKP.020.0120 Unable to find process instance ID <processID>.

Cause: Unable to find the process instance ID.
WKP.020.0121 The process with instance ID <processID> already exists.

Response: Check for "out of memory" errors in the process server log. Restart the process server.
WKP.020.0122 Unable to find root for container ID <containerID>.

WKP.020.0123 Attempt to load process root failed for process root ID <processID>.
Cause: An action related to the workflow appeared after the workflow had completed.
Response: No action is needed.
WKP.020.0124 An attempt was made to start an instance of the process server runtime after it was already started.
Response: Restart the process server
WKP.020.0125 Unable to access instance of process server runtime.

WKP.020.0126 Unable to access timer manager.

WKP.020.0127 Access to container VM (<dispatcherName>) in wrong thread context. Current thread is

<currentThread>(<currentThreadName>).
Cause: The requested container does not exist or is inaccessible in the current context.

WKP.020.0128 Unable to start process. There is no ESRuntime.

Cause: There is a problem with the connection to the broker.
Response: Verify that the broker is running and restart the process server.
WKP.020.0129 IMStartEvent cannot be publish because there is no ESRuntime.

Cause: There is a problem with the connection to the broker.
WKP.020.0130 Unable to delete timer instance <StorableTimerDescriptor> from persistent storage.

WKP.020.0131 Unable to update timer instance <StorableTimerDescriptor> in persistent storage.

WKP.020.0132 Failed to start timer <StorableTimerDescriptor>. The timer will be removed.

Cause: Possible database or memory issues.
Response: Check the process server log for "out of memory" messages.
WKP.020.0133 Failed to unregister timer <StorableTimerDescriptor>.

Response: Check the database connection and restart the process server.
WKP.020.0134 An internal error has occurred.

Response: Restart the Workflow server.
WKP.022.0001 You do not have the required permission to publish a workflow start event.
Cause: The required permissions have not been defined.
Response: Stop the Workflow server and run the Workflow Configurator.

WKP.026.0001 Invalid query: "<queryString>". <errorMessage>

Cause: An invalid query was passed as the parameter of a workflow stop request. The request failed.
Response: User error. Check the query string that was passed to the process server.

Cause: An invalid query was passed as the parameter of a workflow suspend request. The request failed.

Cause: An invalid query was passed as the parameter of a workflow resume request. The request failed.

Cause: An invalid query was passed as the parameter of an open workflow status cursor request. The request
failed.
WKP.026.0005 Unknown workflow [custom id=<customID>]. <errorMessage>

Cause: An attempt was made to stop a workflow with an unknown custom ID.
Response: Verify that the correct custom ID was used and that the workflow is running.

Cause: An attempt was made to suspend a workflow with an unknown custom ID.

Cause: An attempt was made to resume a workflow with an unknown custom ID.

Cause: An attempt was made to get a status for a workflow with an unknown custom ID.

WKP.026.0009 Workflow start failed <errorMessage>.

Cause: An attempt to start a workflow failed.
Response: Check the detailed error message. Possible reasons include database or broker failure and
insufficient memory or disk space.
WKP.026.0010 Unknown workflow [id=<workflowID>]

Cause: An attempt was made to get a result for a workflow with an unknown ID.
Response: Check that the correct workflow ID was used. Verify that the database table
ProcsrvWebServiceRequest contains a row with the ID that was supplied as the workflow ID.
WKP.026.0011 Workflow [id=<workflowID>] is running.

Cause: An attempt was made to get a result for a workflow that is still running.
Response: Wait until the workflow finishes and then get the result.
WKP.026.0012 Unknown workflow [custom id=<customID>]

Cause: An attempt was made to get a result for a workflow with an unknown custom ID.
Response: Check that the correct workflow ID was used. Verify that the database table
ProcsrvWebServiceRequest contains a row with the custom ID that was supplied as the workflow custom ID.
WKP.026.0013 Workflow [custom id=<customID>] is running.

Cause: An attempt was made to get a result for a workflow that is still running.
Response: Wait until the workflow finishes and then get the result.
WKP.026.0014 Unknown workflow status cursor [cursor id=<cursorID>].

Cause: An attempt was made to fetch a workflow status with an unknown cursor ID.
Response: Use the correct cursor ID, acquired with the OpenWorkflowStatusCursor service.
WKP.026.0015 User <userName> has no permissions to perform <operation>.

Response: Check the access and functional privileges configured for the user in the authentication system used
with webMethods Workflow. Verify that the user has permission to use Task List Management.

WKP.026.0016 User <userName> has no permission to start workflow.

Response: Grant the user permission to run the Workflow Inbox.
WKP.026.0017 User <userName> has no permission to get workflow result.

Response: Grant the user permission to run the Workflow Inbox.

WKQ (Persistent Object Layer)
WKQ.020.0001 An attempt has made to assign ID <newID> to an object of class <className> that already has ID <oldID>.
Cause: This message is not expected and indicates a bug.
Response: Contact webMethods Customer Care. Please have the following information available: - Copies of
all logs in the <WorkflowServerDirectory>/log directory - Version information saved to a file from
WKQ.020.0002 A null argument has been supplied as an object to register.

WKQ.020.0003 The second argument to this method, which has class <className>, has no ID.
WKQ.020.0004 The first argument to this method is null.

WKQ.020.0005 The first argument to this method, which has class <className>, has no ID.

WKQ.020.0006 The specified project name is null.

WKQ.020.0007 An attempt has been made to compare a project to a null pointer.

WKQ.020.0008 An attempt has been made to compare version numbers of two projects with different names.
WKQ.020.0009 Fatal error getting ORM for StorableIds:

Cause: Possibly the Workflow Configurator was never run.
Response: Try running the Workflow Configurator and see if this fixes the problem. If this fails, contact
webMethods Customer Care. Please have the following information available: - Copies of all logs in the
WKQ.020.0010 No transaction was in progress to commit.

Cause: This message indicates an attempt to commit a transaction when no transaction was in progress. This
indicates a bug.

WKQ.020.0011 No transaction was in progress to roll back.

Cause: This message indicates an attempt to commit a transaction when no transaction was in progress. This
indicates a bug.
WKQ.020.0012 POSession <sessionID> was already released.

Cause: This message indicates that the given POSession object was released more than once. This is not
expected, and indicates a bug.
WKQ.020.0014 The two arguments to this method are supposed to be arrays of the same length, but are not.
WKQ.020.0015 The second argument to this method is null or is an empty array.

WKQ.020.0016 There is no ORM corresponding to mapped class <className>.

Cause: Probably the Workflow Configurator was not run after a product upgrade.
Response: Stop the Workflow Server, run the Workflow Configurator, then restart the Workflow Server.




WKQ.020.0020 POSession <sessionID> was already released.


WKS (Server Manager)
WKS.007.0001 Cannot get smtp properties from resource server.

Cause: The server did not find any SMTP property information.
Response: Check to see if the SMTP information was configured and that the class server is active.
WKS.009.0001 webMethods Workflow could not establish a connection to Broker.

Cause: The Workflow server could not establish a connection to the broker.
Response: Check to see if the broker is active, that the broker information is configured correctly, and that the
server can access that broker's machine on the network.
WKS.009.0002 A Broker could not be found on <brokerHost>.

Cause: Broker could not be found on specified host. The specified broker may not be running.
Response: Check to see if the broker is running and that its name and port are configured correctly.
WKS.009.0003 A secure connection was attempted but was rejected by the Broker.
Cause: A broker security error occurred. This may be due to SSL.
Response: Check the configuration of the broker information and see if it matches the broker side.
WKS.009.0004 Broker Server is not active, not installed or no licenses are available on specified host. Please install or start.
Cause: The broker is not active, is not installed, or no licenses for it are available on the specified host.
Response: Install or start the specified broker or check the broker configuration information.
WKS.009.0005 Broker has an invalid license string.

Cause: The broker has an invalid license string.
Response: Correct the license string via Broker Administrator.
WKS.009.0006 webMethods Workflow BrokerServerClient connection has been destroyed or disconnected.

Cause: The Workflow server received an invalid client exception.
Response: Check for network connectivity issues and verify that the broker is running.
WKS.009.0007 Broker Exception - webMethods Workflow could not obtain license string.
Cause: The Workflow server could not check the broker license.
Response: Check for network connectivity issues and verify that the broker is running.

WKS.011.0001 This server manager is not configured.

Cause: This server manager has never been configured.
Response: Configure the server manager.
WKS.011.0002 Required property "java.rmi.server.codebase" is not defined.

Cause: The server configuration is incomplete or corrupted.
Response: Reinstall and reconfigure the server.
WKS.011.0003 SDK or JRE unsupported. Please use 1.3.1 or later.

Cause: Workflow releases before 6.1 on the AIX platform shipped with a 1.3.0 JDK, which did not fulfill
Workflow's requirements.
Response: For Workflow 6.0.1 and 6.0.2 releases on AIX, install a 1.3.1 JDK and configure the server to use that
JDK.
WKS.011.0005 This secondary server manager is not configured on the primary.

Cause: This secondary server manager is not configured on the primary server.
Response: Before starting the secondary server, configure it on the primary server.
WKS.011.0006 SDK or JRE unsupported. Please use correct platform specific 1.4 SDK.
Cause: An unsupported JDK is being used. This is perhaps due to intentionally setting the JDK being used
through manual editing of script files and property files.
Response: Reinstall Workflow so that the JDK installed with the product will be used.
WKS.012.0001 URL does not start with "rmi://" : "<resourceServerURLspecification>".

Cause: While checking to verify that it is a local resource server, the server manager determined that the URL
specified in the startup scripts was a bad URL.
Response: Correct the URL or reinstall and reconfigure.
WKS.012.0002 URL does not contain a file part: "<resourceServerURLspecification>".


WKS.012.0003 URL has a ":" in the file part: "<resourceServerURLspecification>.

WKS.012.0004 URL "<resourceServerURLspecification>" has an invalid port: "null".

WKS.013.0001 <serverMainJarName> stopped without getting context.

Cause: The server manager was unable to start a server.
Response: Check logs to determine which server failed and why it failed. Restart the servers.
WKS.013.0002 <serverInstanceName> died with exit code <exitCode>.

Cause: A server exited unexpectedly.
Response: Determine the cause of the problem from the exit code and restart the server.
WKS.015.0001 Invalid Authentication Signature.

Cause: Failed to validate authentication token.
Response: Check configuration security parameters.
WKS.016.0001 webMethods Workflow does not have ACL permission to Broker Server.
Cause: Workflow does not have ACL permission to the broker.
Response: Configure the broker using the Broker Administrator to give Workflow ACL read/write permission.
WKS.017.0001 Failed to send email to <e-mailAddresses>.

Cause: Unable to send e-mail.
Response: Verify that the mail server is active and start it if it is not. Also check the SMTP configuration
information.
WKS.017.0002 SMTP service is down.

Cause: SMTP service is down.
Response: Restart the SMTP service.

WKS.017.0003 Failed to send email notification to administrator.

Cause: Failed to send email notification to administrator.
Response: Verify that the SMTP service and mail server are running.
WKS.017.0004 webMethods Workflow could not locate <brokerHost>.

Cause: Workflow could not locate the specified broker.
Response: Check the Workflow configuration's broker information and verify that the broker name and port
are specified correctly. The server was unable to find the host on the network.
WKS.018.0001 webMethods Workflow does not have permission to access the SSL information.
Cause: The Workflow server does not have the broker's permission to access the SSL information.
Response: Use Broker Administrator to provide Workflow with access to the SSL information.
WKS.018.0002 Authentication properties missing. Please see system administrator

Cause: The authentication.properties file is missing. Perhaps the server was never configured or the file was
deleted manually.
Response: Reconfigure the Workflow server or restore the authentication.properties file.
WKS.021.0001 RemoteException getting server info for: <serverName>.

Cause: Could not access the specified server.
Response: Verify that the remote server allows RMI and is not behind a firewall.
WKS.021.0002 Server <serverName> failed to bind to <serviceName>.

Cause: A server failed to bind.
Response: Check that the system has enough memory, that the user has file read/write access to files in the
Workflow directory, and that Workflow has been successfully configured.
WKS.022.0001 A server manager is already running here.

Cause: A server manager is already running here. A service or daemon may have already started your desired
server, or a server using the same port is installed at another location.
Response: If the server installed in another location is already started and is not the one you wish to be running,
stop that server with srvmgr.bat (or via Windows Service) or allservers stop and restart your desired server.

WKS.022.0002 Failed to create mail support service.

Cause: Failed to create mail support service.
Response: Check that the system's mail server is configured correctly to start.
WKS.022.0003 Finished startup of servers. Some servers failed to bind.

Cause: Some servers may not have enough memory to start or there may be some other external factors
stopping some servers to bind.
Response: Check the servermgr log for clues as to why particular servers did not bind and take appropriate
measures.

WKT (Run-Time Support)
WKT.020.0001 Cannot load html page: <Event Information>

Cause: Cannot load the HTML page. The message includes additional information explaining the reason for
the error.
Response: Correct the problems explained in the error message and try again.
WKT.020.0002 The following files were not found: <fileList>

Cause: Files were not found. The message includes additional information explaining the reason for the error.
Response: Correct the problems explained in the error message and try again.
WKT.020.0003 Attribute VALUE is not defined in this tag. Please, define the attribute and try again.
Cause: Invalid HTML document structure. The attribute VALUE must be defined.
Response: Correct the HTML and re-import the file.
WKT.020.0007 MetaUtils.getElementIndex: wrong metaRoot [<Name>] or metaElement [<Name>]

Cause: Invalid DT model component structure.
Response: Validate the model to find and fix the broken component.
WKT.020.0008 MetaUtils.getElementIndex: wrong arrElements [<Name>] or metaElement [<Name>]

WKT.020.0009 MetaUtils.getElementIndex: not found <elementName> in <numberOf> elements

WKT.020.0010 Path is null.

Cause: Invalid DT model component structure or programmatic error. The target path is null.
WKT.020.0011 Wrong length<pathLength>.

Cause: Invalid DT model component structure or programmatic error.

WKT.020.0012 From is null.

Cause: Invalid DT model component structure or programmatic error. The path source is null.
WKT.020.0013 <path1> must be a part of <path2>.

Cause: Invalid DT model component structure or programmatic error.
WKT.020.0014 User home directory is not defined.

Cause: Missing "user.home" JVM property.
Response: Check the JVM installation and configuration. Contact your system administrator.
WKT.020.0015 No server name.

Cause: Incorrect RMI server name, configuration problems, or programmatic error.
Response: Check the product installation and configuration.
WKT.020.0016 Wrong service name := <serviceName>.

Cause: Incorrect RMI server name, configuration problems, or programmatic error.
Response: Check the product installation and configuration.
WKT.020.0017 Connection to <requestedServerName> timed out.

Cause: Network connectivity issue. Incorrect RMI server name, configuration problems, programmatic error,
or the server may be down.
Response: Check the network status. Check the servers and restart if necessary. Check the product installation
and configuration.
WKT.020.0019 Remote method invocation failed with RemoteException, <requestedServerName>, reconnection attempt in
progress...
and configuration.

WKT.020.0020 Failed to invoke remote <requestedServerName>() method. Please try again later.
and configuration.

6-5-1 Webmethods Error Message Reference PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

6-5-1 Webmethods Error Message Reference PDF

Uploaded by

Copyright:

Available Formats

webMethods

Error Message Reference

VERSION 6.5 AND 6.5.1

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

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

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

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

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

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

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

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

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

webMethods Error Message Reference Version 6.5 and 6.5.1 3

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

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

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

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

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

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

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

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

4 webMethods Error Message Reference Version 6.5 and 6.5.1

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

webMethods Error Message Reference Version 6.5 and 6.5.1 5

6 webMethods Error Message Reference Version 6.5 and 6.5.1

About This Guide

webMethods Components and Versions

webMethods Component Version

webMethods Error Message Reference Version 6.5 and 6.5.1 7

8 webMethods Error Message Reference Version 6.5 and 6.5.1

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

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

webMethods Error Message Reference Version 6.5 and 6.5.1 9

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

1001 Broker Server exiting, process id <processID>.

1002 Could not start Windows sockets: <errorMessage>.

1003 Wrong version of Windows sockets.

1008 Data store wrong version [EXITING].

1010 Error: Unknown subcommand "<subCommand>".

1011 Error: Missing subcommand.

10 webMethods Error Message Reference Version 6.5 and 6.5.1

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

1012 Error: No data directory supplied.

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

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

webMethods Error Message Reference Version 6.5 and 6.5.1 11

1019 Error: No description specified.

1021 Cannot accept connections: <errorMessage>.

1022 Error: No Broker Server executable specified.

12 webMethods Error Message Reference Version 6.5 and 6.5.1

1024 Error: No Broker Server configuration file specified.

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

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

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

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

webMethods Error Message Reference Version 6.5 and 6.5.1 13

1030 Error: No hostname specified.

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

1033 Error: "<switchString>" unknown switch.

1034 Error: Unexpected arg "<argString>".

14 webMethods Error Message Reference Version 6.5 and 6.5.1

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

1037 Wait on synchronization object failed: <errorMessage>.