BMC Remedy Action Request System 7.5.

00

Error Messages Guide

January 2009

www.bmc.com

Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada
Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000

Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000

If you have comments or suggestions about this documentation, contact Information Design and Development by email at doc_feedback@bmc.com.

© Copyright 1991–2009 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. IBM and DB2 are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Linux is the registered trademark of Linus Torvalds. UNIX is the registered trademark of The Open Group in the US and other countries. Oracle is a registered trademark of Oracle Corporation. Sun, Sun Microsystems, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. or other countries. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.

Restricted rights legend
U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.

Customer Support
You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer Support by telephone or email. To expedite your inquiry, please see “Before Contacting BMC Software.”

Support website
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can:
s s s s s s s

Read overviews about support services and programs that BMC Software offers. Find the most current information about BMC Software products. Search a database for problems similar to yours and possible solutions. Order or download product documentation. Report a problem or ask a question. Subscribe to receive email notices when new product versions are released. Find worldwide BMC Software support center locations and contact information, including email addresses, fax numbers, and telephone numbers.

Support by telephone or email
In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813 or send an email message to customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>, such as SupID:12345.) Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC Software
Have the following information available so that Customer Support can begin working on your issue immediately:
s

Product information — — — Product name Product version (release number) License number and password (trial or permanent)

s

Operating system and environment information — — — — — Machine type Operating system type, version, and service pack System hardware configuration Serial numbers Related software (database, application, and communication) including type, version, and service pack or maintenance level

s s s

Sequence of events leading to the problem Commands and options that you used Messages received (and the time and date that you received them) — — — Product error messages Messages from the operating system, such as file system full Messages from related software

License key and password information
If you have a question about your license key or password, contact Customer Support through one of the following methods:
s

E-mail customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>, such as SupID:12345.) In the United States and Canada, call 800 537 1813. Outside the United States and Canada, contact your local support center for assistance. Submit a new issue at http://www.bmc.com/support_home.

s

s

Contents
Preface Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AR System Error Messages form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology used in error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AR System documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1 AR System diagnostic messages 7 7 7 7 8 11 12 12 13 13 14 15 15 17

Message reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server error reporting in UNIX® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server error reporting in Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message catalogs in UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message not in catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AR System Error Messages form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Localizing error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Action Request System error messages

Finding AR System error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 AR System error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Index 249

Contents

5

6 Error Messages Guide .

AR System Error Messages form The information in this manual is also available through the AR System Error Messages form. Terminology used in error messages Message Text—A message in a dialog box that interrupts operations. Preface 7 . Messages include notes. Notes are labeled ARNOTE in AR System. For information about how to install the AR System Error Messages form. especially the necessary patch requirements. warnings. warnings.bmc. Note—A purely informational message. requires no action. administrators. and to provide helpful notes in the Notes field. and the system continues with normal operation. You can use this form to search for notes. See the compatibility matrix at http://www.Preface IMPORTANT The compatibility information listed in the product documentation is subject to change. see “To set up the AR System Error Messages form” on page 15. and error messages returned by AR System. You can also use this form to modify the message contents that appears to users. Read the system requirements for your particular operating system carefully.com/support_home for the latest. and users of BMC Remedy Action Request System (AR System). most complete information about what is officially supported. to customize the detailed description in the Description field. Audience This guide is written for developers. and errors.

Warnings are labeled ARWARN in AR System. but that are acceptable to the system. and images. AR System documents The following table lists documentation available for AR System products. Programmers3 Information about monitoring and maintaining AR System Administrators/ and AR System applications to optimize performance and Developers/ solve problems. menus. Error—A message that indicates a failure. Title Concepts Guide1 Description Audience Overview of AR System architecture and features. Information about the development of AR System applications. importing and exporting data.5. You can access product help through each product’s Help menu or by clicking Help links. on the Customer Support website (http://www. Administrators Developers2 Installation Guide Introduction to Application Development with BMC Remedy Developer Studio Form and Application Objects Information about AR System applications and their user Guide interface components. views. or both. Instructions for installing AR System.bmc. Unless otherwise noted. Errors are labeled ARERR in AR System. the system does not perform the current operation. plug-ins. Programmers Optimizing and Troubleshooting Guide 8 Error Messages Guide . but the system continues with normal operation. and using applications in browsers. includes Everyone information about add-on products that extend AR System functionality and a comprehensive glossary for the entire AR System documentation set. OLE. fields. and other products. including forms. setting up applications for the mid tier. You must correct the cause of this message to perform the attempted operation.com/support_home).BMC Remedy Action Request System 7. Workflow Objects Guide Developers Information about the AR System workflow objects (active Developers links. Integration Guide Administrators Instructions for integrating AR System with external Administrators/ systems by using web services. You can take action in response to this message.00 Warning—A message that warns you of facts you need to know. and ARDBC. filters. Administrators Configuration Guide BMC Remedy Mid Tier Guide Information about configuring the mid tier. Developers/ including LDAP. and archiving data. including an introduction to using BMC Remedy Developer Studio. online documentation in Adobe Acrobat (PDF) format is available on AR System product installation DVDs. localizing. Information about configuring AR System servers and clients. and escalations) and how to use them to create processes that enforce business rules.

For the location of the JAR file containing this online documentation.AR System documents Title Database Reference Description Database administration topics and rules related to how AR System interacts with specific databases. Instructions for configuring BMC Remedy Mid Tier. installation planning. and applications. Developers Information about AR System data structures. Instructions for using BMC Remedy User. Information about Java classes. Everyone Information about new features.00 Concepts Guide). Preface 9 . compatibility. Descriptions of AR System error messages. Audience Administrators/ Developers/ Programmers Administrators BMC Remedy Distributed Server Option Guide BMC Remedy Flashboards Guide C API Reference C API Quick Reference Java API Instructions for creating. Everyone Developers Administrators Everyone Administrators Everyone 1 The full title of each guide includes BMC Remedy Action Request System 7. Quick reference to C API function calls. BMC Remedy Action Request System 7. and OLE support. workflow objects. Instructions for using BMC Remedy Developer Studio to develop AR System forms. see the information about plug-ins in the Integration Guide. and variables used Programmers to write plug-ins for AR System. Instructions for using BMC Remedy Approval Server to automate approval and signature processes in your organization. methods.5. ™ ™ Programmers Programmers Information about Sun Java classes. and administering Administrators/ flashboards to display and monitor AR System information. For the location of the JAR file containing this online documentation. C API function calls. and open issues. modifying. see the information about the Java API in the Integration Guide. includes an overview of the data dictionary tables. international Everyone issues. compatibility. Instructions for using BMC Remedy Data Import. Instructions for configuring and using BMC Remedy Email Administrators Engine.00 (for example. Instructions for using BMC Remedy Alert. methods. Instructions for using AR System forms in browsers. Administrators/ Developers/ Programmers Everyone Administrators Java Plug-in API BMC Remedy Email Engine Guide Error Messages Guide Master Index BMC Remedy Approval Server Guide Release Notes Release Notes with Open Issues BMC Remedy User Help BMC Remedy Developer Studio Help BMC Remedy Data Import Help BMC Remedy Alert Help BMC Remedy Mid Tier Configuration Tool Help BMC Remedy Browser Help Combined index of all books. Information about implementing a distributed AR System server environment with BMC Remedy Distributed Server Option (DSO).5. and international issues. Information about new features. and Programmers variables that integrate with AR System.

00 2 3 Application developers who use BMC Remedy Developer Studio.BMC Remedy Action Request System 7. C and Java programmers who write plug-ins and clients for AR System. 10 Error Messages Guide .5.

the system usually reports one or more error or warning messages. Because error checking is built into how AR System clients (for example. This guide lists and describes these messages. it might not be clear from the diagnostic messages how to correct a problem. and outlines the process you must follow to resolve each of these problems. If you are still unable to resolve a problem or if you encounter a problem that is not covered in this chapter. These messages often provide you with information to determine the cause of a problem. When problems occur. The following topics are provided: Message reporting (page 12) Message catalogs in UNIX (page 13) AR System Error Messages form (page 15) Localizing error messages (page 15) Chapter 1 AR System diagnostic messages 11 . This chapter describes common problems. contact your Customer Support representative. BMC Remedy User) interact with AR System server. Occasionally. NOTE An online version of all messages and descriptions is available in the Error Messages form.Chapter 1 AR System diagnostic messages AR System includes diagnostic error and warning messages. you might see some of these messages only with client applications that you create using the AR System API.

log file: user.log To start logging. the error messages cannot be synchronized. you might find a few differences. all AR System daemon error messages are sent to the syslog daemon where. Instead. Server error reporting in UNIX® AR System daemons run in the background.conf) to direct all messages of type user.none or include a separate line that explicitly locates user. These daemons are not associated with a terminal and thus cannot report errors to a terminal. (See information about log files and debug modes in the Optimizing and Troubleshooting Guide.conf contains an entry of the form user. All errors are also written to the arerror. they display or are recorded.none.err/usr/ar/err.5. the following line specifies that you want all messages intended for syslog that are of the type user. add a line similar to the preceding line to the /etc/syslog. a pure Java qualification parser replaced the C-based qualification parser used in earlier releases. see the Configuration Guide. BMC Remedy Developer Studio. or direct all messages to a file by specifying a complete path name).err messages and sends them to a target you specify. To receive these messages. BMC Remedy Alert.00. For more information.00 Message reporting All interactive AR System tools (BMC Remedy User.log file in the ARServerInstallDir/db directory.conf file in your operating system reference manuals. configure your syslog instance (using syslog. Due to this change.conf file.err to one or more locations that you define (for example. For a complete discussion of the syslog process.err. NOTE BMC Remedy User and BMC Remedy Mid Tier might display slightly different error messages for the same problem. see information about the syslogd process and the syslog.) 12 Error Messages Guide . In BMC Remedy Mid Tier 7. and reset logging by sending a kill -1 signal to the syslogd process to cause it to reread its configuration file. If a tool fails during startup.BMC Remedy Action Request System 7.err written to the /usr/ar/err. specify the console device as /dev/console. and BMC Remedy Data Import) report errors directly to the terminal. Delete user. For example.5. Hence. to direct all messages to the console. AR System administrators can configure system logging options. If a line in syslog. no messages to class user are sent to the target on this line. Remember the following points about the syslog process: AR System daemons send messages about all fatal system and database errors to syslog as type user. depending on the configuration of your system. the error messages appear at the command line from which the program was started.

%N specifies the name of the message catalog.log file in the ARServerInstallDir\db directory. making it impossible to store a link to the message catalogs.cat for AR System messages. the message catalogs are stored in the following locations: Client Environment HP-UX and HP-UX Itanium AIX Solaris ™ Message Catalog Location /usr/lib/nls/msg/%L/%N /usr/lib/nls/msg/en_US/%N /usr/lib/locale/%L/LC_MESSAGES/%N arSystemInstallPath/locale/%L Linux® The path names contain these variables: %L specifies the value of the LANG environment variable (C by default). The installation process establishes a symbolic link in the default message catalog area to the catalogs installed by the system. You might want to store the catalogs in another location.) Message catalogs in UNIX All messages returned by UNIX® processes are stored in a message catalog. To review the contents of the event log. Chapter 1 AR System diagnostic messages 13 .) This catalog is named arsystem. By default.Message catalogs in UNIX Server error reporting in Windows In Windows. For example. the directory holding the catalogs is mounted as read-only. (See the discussion about log files and debug modes in the Optimizing and Troubleshooting Guide. (All messages returned by Windows processes are compiled into the software and are not stored in an accessible catalog. AR System messages have the Source column set to Remedy Action Request. which opens up the Event Viewer Application Log window. this is the syntax for specifying the AR System message catalog location (assuming the default language environment) on Solaris: /usr/lib/locale/C/LC_MESSAGES/arsystem. All error messages are also written to the arerror. Click Event Viewer. this is /usr/ar/locale). open the group for Administrative Tools.cat On some systems. AR Monitor sends server start and server stop messages to an event log. The catalog files are in the locale directory under the AR System installation directory (by default.

that they are in the appropriate directory. a process cannot access the message catalog: Message not in catalog. 14 Error Messages Guide .5.cat file is readable by all. for example. you can link to the catalogs by setting the NLSPATH environment variable as follows: setenv NLSPATH /usr/ar/locale/%N:/usr/lib/locale/%L/LC_MESSAGES/%N NOTE Include the default directory in the NLSPATH environment variable to make sure that catalogs for other products are still accessible. Make sure that the setting of your LANG environment variable is set to the correct language on both the server and the client. To troubleshoot this error Make sure that the message catalogs exist. and escalations) and might come from either the server or the client.00 Use the NLSPATH environment variable to place the catalogs in a directory other than in the default directory. or you can set it to the default value of C to cause the system to default to using the English language catalog. messages with numbers below 1000 are from the server. Make sure that the arsystem. if the default catalog directory is read-only. Errors above 10000 are defined by workflow (active links. On Solaris. You can clear this variable. For more information about internationalizing message catalogs. filters. while messages 1000 or higher are from the client. each end of the link must be readable by all. Message number = messageNumber Messages are returned by the server or the client. Message not in catalog If you receive the following message. see the documentation supplied with your operating system. and that the NLSPATH environment variable is set correctly on both the server and the client. If you set up symbolic links.BMC Remedy Action Request System 7. In general.

Chapter 1 AR System diagnostic messages 15 . but the text might not match. the AR System Error Messages form is available to search for notes. the message text a user sees might not match the text in this guide if the message was overridden in the AR System Message Catalog form.def (UNIX) 2 Use BMC Remedy Data Import to import error message data from this file: ARServerInstallDir\arserver\help\errars. The meaning of the message is still the same. including flashboards and notification error messages. Localizing error messages The AR System Message Catalog form enables administrators to provide localized versions of error messages. use the following procedure to import both the AR System Error Messages form and the error message data. After installing AR System. and error messages. Help text. and other text strings that appear to users in applications that are customized by locale. To set up the AR System Error Messages form 1 An AR System administrator must use BMC Remedy Developer Studio to import the form definition file from this location: ARServerInstallDir\arserver\help\remerror.def (Windows) ARServerInstallDir/help/remerror. menus. To search for AR System error messages.arx (Windows) ARServerInstallDir/help/errars. Because these error messages can be modified for localization. For more information. see the Form and Application Objects Guide. You can enable or disable the use of this form and use this form in both UNIX and Windows environments.AR System Error Messages form AR System Error Messages form In addition to this guide. warnings. select AR System in the product list.arx (UNIX) The AR System Error Messages form is now ready for use.

00 16 Error Messages Guide .BMC Remedy Action Request System 7.5.

server. The following topics are provided: Finding AR System error messages (page 18) AR System error messages (page 19) Chapter 2 Action Request System error messages 17 .Chapter 2 Action Request System error messages This chapter contains all the error messages in numerical order for the client. You can find any error message quickly by its number. and mid tier components of AR System.

they might be incompatible with future versions of AR System. In AR System.00 Finding AR System error messages This document includes only error messages used in AR System. warnings. and notes BMC Remedy Flashboards BMC Remedy Data Import client (Windows) AR System application servers BMC Remedy Email Engine BMC Remedy Developer Studio BMC Remedy Data Import errors. and notes AR System application servers. error messages are classified according to the ranges in the following table.00 and earlier only) AR System Server BMC Remedy Mid Tier AR System Server BMC Remedy Email Engine Server messages Mid tier error messages Server messages Email workflow messages 18 Error Messages Guide . error messages are arranged in numerical order. and web tools 7000 8000 9200 9700 11000 7999 9199 9699 9999 11099 BMC Remedy Administrator client BMC Remedy Administrator errors and warnings (release 7.BMC Remedy Action Request System 7.1.5. including BMC Remedy User. WARNING Do not define custom error messages for your applications with numbers in these ranges. warnings.1. In this document. BMC Remedy Email Engine. Start 1 1000 1800 2000 3000 3300 3350 3380 3500 4000 4500 4900 5000 5400 5500 6000 End 999 1799 1999 2999 3199 3349 3379 3499 3999 4499 4899 4999 5399 5449 5999 6999 Product AR System Server BMC Remedy User BMC Remedy User Description Server messages and notifications BMC Remedy User errors. and notes BMC Remedy User errors BMC Remedy Administrator client BMC Remedy Administrator errors and warnings (release 7. If you do. including BMC Remedy Approval Server Email errors and warnings BMC Remedy Developer Studio messages BMC Remedy Data Import BMC Remedy Developer Studio AR System clients BMC Remedy Data Import messages BMC Remedy Developer Studio messages Errors for any AR System client. It is not backward-compatible with earlier versions of AR System and thus does not include messages for obsolete features.00 and earlier only) AR System Server AR System Server AR System Server Reserved for AR System BMC Remedy Distributed Server Option messages BMC Remedy Data Import event messages Report ARDBC plug-in messages Reserved for AR System Flashboards errors. warnings. BMC Remedy Developer Studio.

This is a generic message indicates that the error was fatal.log output. The first step in troubleshooting a crash of the AR System server is often to upgrade to the latest patch release of a current version. The tag ARERR indicates that the condition is an error. see “Message catalogs in UNIX” in the Error Messages Guide. To resolve this problem: For UNIX. Make sure the ARSystemInstallDir is included in the PATH environment variable. Text corresponding to that message number was not found. then the message catalog is accessible but does not include this error. and ARNOTE indicates a note. or to a server crash.dll file is installed in the same directory as the AR System server.log file that includes the time of the crash.AR System error messages AR System error messages NOTE AR System messages can take the form of errors. Note: Only those processes that are started with the AR System server by means of an entry in the armonitor. the message catalog . and the process is shutting down.log file that includes the time of the crash. Chapter 2 Action Request System error messages 19 .cat on UNIX and is arcatalog_language. and follow the recommended steps to configure the NLSPATH. (For UNIX) If the signal is 15.log file. The error message includes the signal that was received. On Windows. In this case. contact Customer Support. the AR System server has failed and the incident will generate stack output to the arerror. The most common cause of this error is that the path to the message catalog file is not correctly defined. 20 Note AR System server terminated when a signal or exception was received by the server. The AR System server cannot find the message catalog file. If other AR System processes failed abnormally due to a shutdown of AR System server.conf file are included in armonitor.log file will provide information about other processes that failed. The armonitor. ARWARN indicates a warning. the armonitor. A fatal error occurred in the arserverd process. which is arsystem. This signal indicates that the process terminated from a command to do so. or notes. 21 Note AR System server terminated—fatal error encountered. Details about the error are in an associated message. If the shutdown signal is anything other than normal shutdown. The current version and patch level of the AR System server. check this document for the message number and information. and provide the message number and the circumstances that prompted the message. To help resolve this problem. warnings. If the message number is not present in this document.dll on Windows. Note: If you get the text for other message numbers but not the one causing this error. the AR System process was stopped due to a normal shut down command. 1 Error Message not in catalog—message number = messageNumber. contact BMC Remedy Support and provide the following information: The arerror. Any other AR System logs that cover the time of the crash.

contact your sales representative or visit http://www. Failure while trying to run the filter or escalation process. Additional actions occurred to access this file. contact your BMC sales representative. perform the server operations on the server in the group that allows administrator operations. Fields in set fields action incompatible with form for filter or escalation. Contact your distributor for license information. An error occurred while AR System was executing a filter or escalation that runs a process. A file system error occurred while AR System was running a filter or escalation that logs information to a file (using the Log to File action). Verify that the process definition is correct. This system can be used for evaluation. but logging to the log file is suspended until the problem is corrected (see Error 23). correct the process definition in the filter or escalation. For unlimited capabilities. or visit http://www. Processing continues. The demo license for the system on which you are trying to run the AR System server expired.com. Previous demo license has expired. The filter or escalation being executed is trying to set values in fields that do not exist in the target form. 29 Note The AR System server license is a demo license that expires expirationDate. Any operations between the message indicating a write failure (Error 22) and this message are not included in the log file. Specify values only for fields that exist in the target form. If necessary.00 22 Error Failure occurred during open or write to the filter or escalation log file. and is configured for each client to access a maximum of one server. and the file is now accessible and can be written to.5. Contact your distributor for information about upgrading your license. The AR System server is configured to disallow administrator operations. You are operating with a demo license.com. This version of BMC Remedy AR System has a maximum limit of 2000 requests per database table. 27 Note 28 Error The AR System server does not have a license. 23 Note 24 Error 25 Error 26 Error Administrator operations are disabled on this server.BMC Remedy Action Request System 7. Fix the definition. but is not allowed for production use. You must obtain a license to run AR System server in any mode other than evaluation mode. If the server is part of a group of servers sharing the same database. an authorized reseller. A failure was reported on an open or write action to the log file identified by Error 22. An associated message provides details. An associated message detailing the reason for the failure appears with this message. The system is now running in an unlicensed mode (see Error 27). This version of the Action Request System is ready for use or evaluation without purchasing or activating an authorization key. A common cause for this error is a filter or escalation that tries to assign a value to a field that formerly existed on the form but was deleted after the definition was created. 20 Error Messages Guide . Open or write action to the filter or escalation log file resumed successfully.bmc.bmc. which expires on the specified date. To obtain a version of BMC Remedy AR System without these limitations. includes a maximum of three fixed licenses.

390601 for arservdsd and ar. but the process returned an error message.lck at start-up. A filter or escalation was performing a Set Fields action using the option to run a process and return a value. and the current transaction is rejected.lck. If no arserverd process is running. If you have no more fixed licenses. Failure occurred during execl( ). Error occurred while opening the AR System server lock file. 35 Error 36 Error The database is not the expected version. the lock manager keeps a lock active even when the process holding the lock is no longer running. 31 Note A fixed licenseType license was issued for the new user: xOfY. you probably encountered a known problem with the NFS lock manager on Sun workstations. AR System failed to start a process. arservdsd.rpcNum (ar. To correct the problem. and rerun the server. The message shows the current number of users who have a fixed license and the total number of users allowed. The licenseType is replaced by write.390602 for arservftd) for servers on alternate RPC sockets. The licenseType is replaced by write. Error occurred while accessing one of the debug trace files. and ar. see the Configuration Guide. At times. full text. or flashboards. You can add the user with a read. Another copy of the server is already running on the same RPC socket. Your current number of users is equal to your current number of fixed licenses. An associated file system error message supplies more details. AR System server (arserverd. 37 Error 38 Error Chapter 2 Action Request System error messages 21 . You tried to define a new user and assign this user a fixed license. Start the arserverd process after removing this file. The error terminates the operation being performed. AR System server (arserverd) expects a different version of the AR System database from the version being referenced. Filter or escalation set field process returned an error. or floating license. You created a new user who is assigned a fixed license. If the server is not running. No update to the database occurs.lck. full text. AR System server cannot run against an unknown version of AR System database. 32 Note 33 Error 34 Error AR System server terminated normally. Server shut down without problems. The associated message provides details. These files are used to prevent multiple copies of the AR System processes from being started on a single RPC socket simultaneously. For a more detailed explanation. A user was successfully created.AR System error messages 30 Error You are already at the limit of the number of fixed user licenses of the type licenseType. Fix the problem. You might need to run an upgrade program. and the system cannot access one of the debugging trace flags. but not a fixed license. but debug tracing to the file is disabled. or flashboards to indicate the type of fixed license. none. Make sure that your system has no resource problems that prevent new processes from starting. or arservftd) opens a lock file named ar. Only one instance of AR System server can be run (on a specific RPC socket) on a computer at a time. see the message.lck. If a server is already running in this RPC socket. The system continues to run. Contact your distributor for information about obtaining additional licenses. The text of the message returned appears with this error. The system debugging mode was activated. no action is required. free the lock by deleting the lock file. to indicate the type of fixed license. verify that the sample users were deleted.

A $MENU$ pattern is specified for a field with a character menu. The server restricts access locally to the same server process for performance and consistency reasons. It can be configured. The server is configured to run multiple queues. Escalations do not have a message type action and do not support log or set field in the else branch. The administrator has control over the timeout setting for the process. If arserverd receives no response. You created an escalation and specified one or more message type actions or one or more log actions in the else branch. The command line argument displayed on the following line is not a legal command line argument for AR System server. You cannot use a $MENU$ pattern verification for a remote search. and use log actions in the action list only. the process disconnects from the mail system and issues this error. The mail will probably be delivered when the mail system recovers. 41 Warning Unrecognized command line argument—ignoring command line and continuing.00 39 Error Filter or escalation set field process timed out before completion. 46 Error 47 Warning 22 Error Messages Guide . The server restricts access locally to the same server process for performance and consistency reasons. but the process was not completed within the time-out interval specified for filter processes. You cannot use a $MENU$ pattern verification for a remote SQL command. To prevent the arserverd process from hanging while waiting for the mail system. the process waits for 20 seconds. Change the definition to eliminate the message type actions. but the search is encountering an error during retrieval.5. Remove one or more of the existing forms before you create a new form. The menu is built from a file. and you are at that limit. The RPC socket setting is being ignored. The menu is built using direct SQL against a local database. but you do not have a multiple server license. The system was blocked while trying to send a notification through email. and processing continues.BMC Remedy Action Request System 7. Message action and Log action in else branch are not supported for escalations. A character field with a $MENU$ pattern is failing due to errors retrieving the character menu to validate against. The command line argument is ignored and processing continues. A filter or escalation was performing a Set Fields action using the option to run a process and return a value. The menu is built from a search against a local form. The error can be due to one of the following reasons: The menu is built from a search against a form on a different server. Server is not licensed to run with multiple-RPC sockets—ignoring setting and continuing. and the file cannot be found. 42 Warning 43 Error 44 Error You are already at the limit of the number of forms allowed for your server license. Email notification operation timed out before completion. You are allowed to create only a specified number of forms. but the command is encountering an error during retrieval. to be from one to 20 seconds with a default of five seconds. in BMC Remedy Developer Studio. The AR System server you are running against has a limited license. and the server is encountering an error while building the menu to verify the value against. The menu is built using a direct SQL command against another server.

Enter the login name correctly (including case). Create Date. Entry does not exist on form. AR System allowed you to log in. You tried to log in with a user name that AR System did not recognize. Field ID specified does not exist in this form. if you want other users to access and manipulate this field. A client is accessing the server and has specified an invalid identifier for the requested information. but only as a guest user. or Status History). or character menus) to the current server. filters. The following item was not imported: item. but there were no modifications specified. You tried to retrieve a request that does not exist. and try to reimport the item. You specified a Modify operation to the system. A retrieval operation was attempted for the field identified by the indicated ID. The field is a core system field and cannot be changed. You requested permission information about a field. A client is accessing the server and has specified insufficient space for the response to be returned. An internal RPC failure occurred. One or more fields in the statistic operation had a NULL value. but the target form has no field with that ID. An internal RPC failure occurred. Last Modified By. the item might have been deleted by another user. ask the administrator to add the user as a valid login name to the system. If the login name does not exist. No changes have been specified for the update operation. No permission settings were specified to allow access to other users. active links. Fix the problem. verify spelling and capitalization to continue. These fields are managed by AR System and cannot be changed. Those values are excluded from the statistics computation. However. 51 Warning 52 Warning 53 Warning 54 Warning 55 Warning 56 Warning 57 Warning 59 Warning User does not exist—successfully connected as a guest user (type user name exactly—including capitalization). Only the administrator has access to this field. If the command is being executed programmatically and there is potential for set operations with no changes to be specified. The field is accessible only to administrators. The data for the correctly identified fields was retrieved. You tried to import one or more items (forms. escalations. you must assign permissions to the field. If this message is received when retrieving an item that was reported in a preceding retrieval. The requested statistical operation found one or more NULL values in the fields that were being used for the calculation. but all other requested information is retrieved. only those fields that contain non-NULL values are included in the computation. Because NULL fields contain no meaningful data for the calculation being performed. The listed item was not successfully imported. this warning can be trapped and ignored in your program. Last Modified Date. You tried to modify the contents of a core system field (Request ID. Administrator access required to get permission information. Only a user with administrator access can retrieve permission information. 49 Error 50 Warning Internal error: The request ID for a multipiece RPC response is invalid. Chapter 2 Action Request System error messages 23 . No permission information is returned. This is expected if you are restricting access to the field.AR System error messages 48 Error Internal error: The maximum response value in the control record is too small (minimum of 4096 bytes). If you think the login name exists. An associated message indicates why the item was not imported.

This message is issued (instead of Warning 60) when you may have access to this field on some requests. but only with access to the first form in the list of forms. create multiple filters. This is an older definition. ask the administrator to extend your permissions to include the fields. such as when you are the Submitter or Assignee. You created a filter or escalation action that logs to a file. with no menu where the file was to be expanded. AR System completed the statistical operation. You tried to access a request to which you do not have access. When the log file is created.00 60 Warning 61 Warning You do not have read access to this field. choose Tools > Options > Behaviors. ask the administrator to include read access to this field. ask the administrator to grant access to you. If it is necessary that those values be included in the computation. If access to this request is required. 64 Warning The filter or escalation action cannot write to the specified log file—action created but file must be verified. A character menu that references a file was being expanded. Only an administrator can change the server settings. You tried to perform a statistical operation that included values from fields that you are not allowed to access. The retrieval included a search that selected more than the maximum number of items allowed by the client or server. 66 Warning The search matched more than the maximum number of entries specified for retrieval—returned entries are limited to the specified maximum.BMC Remedy Action Request System 7. The action was created. and the filter is linked only to the first form in the list. but the file you specified does not exist and cannot be created. You tried to access a field to which you do not have read access. and re-expand the menu. 24 Error Messages Guide . You do not have read access (for this entry) to this field. Narrow your search criteria or change the limit in user preferences. 65 Warning The filter definition contains multiple form links. Fix the problem. If you need filters with the same actions. The filter is loaded. The character menu being expanded is incomplete. If access to this field is required. You tried to access a field to which you do not have read access for the current AR System request. The filter definition uses an older syntax in which filters could be linked to multiple forms. or are a member of the Assignee Group of the specific case. but the inaccessible values were not included in the results. The call returned the number of entries specified as the maximum. ask the administrator to extend your permissions to include this field. The new definition allows only a single form link.5. Ask the administrator to restructure the filter definition to see a single form. 67 Warning Attempt to open menu file failed—character menu is incomplete. An associated message contains details. Those values are excluded from the statistics computation. and modify the settings for Limit Number of Items Returned. 63 Warning One or more values in the statistic operation cannot be retrieved due to access control restrictions. To change the local setting in BMC Remedy User. the action logs transactions. and the specified file could not be accessed. If access to this field on this request is required. 62 Warning You do not have access to the requested entry. An associated message provides details. The action does not perform an operation until the file system error is corrected. This error results when you do not have access to the Request ID field (the unique key given to each request in the system).

the system encountered the associated SQL error.390695). This number is less than the maximum specified by the server for this call. Chapter 2 Action Request System error messages 25 . 390619 . The only missing information is a SQL view for this form. No permission settings were specified to allow access by other users. You can access the form and continue with operation of the system. There is no character menu for the field. 74 Warning A duplicate index has been specified—duplicate was omitted and indexes were created. 72 Warning 73 Warning A value change is pending on the Submitter Mode setting—change will take effect the next time the server is started. To use the ARRPC environment variable. AR System automatically creates a unique index on the Request ID field. and processing continues. 70 Warning 71 Warning One or more fields in this form reference character menus that no longer exist. While trying to create the SQL view for this form. You are allowed access to the database for read-only use. but processing was completed with the index created only once. You cannot create duplicate indexes. The active link is accessible only to Administrators. The table definition and the structure needed by AR System server is complete and in place.390669 are specialty servers and may have restricted functionality. You specified the same index twice for a form. 75 Warning No floating write license tokens are available. Group Access is not defined—only the administrator has access to this active link. The environment variable is being ignored. administrators must assign permissions to the active link. This error prevented the creation of the SQL view. Currently accessing the system in read-only mode. It is a pending change until the next restart. NOTE: The value 390603 and the range 390619 . but no floating write license tokens are available at this time. The definition of the form and associated fields are complete and in place. 390620 through 390634 (fast daemon). The system will try to upgrade your license type when a token is available. However. 390680 . The character menu referenced by one or more fields in this form does not exist. 390619 (the flashboard daemon).AR System error messages 68 Warning RPC environment variable is out of valid range (390600. This message is a warning about the duplicate. You are assigned a floating write license. even though the system has a menu defined for it. You receive this error if you try to create an index that contains only the Request ID field. clear this variable.390669. This is correct if you are restricting access to the active link. The search matched more than the maximum number of entries specified by the server—returned entries are limited to the specified maximum. The call returned the number of entries specified as the maximum by the server. The retrieval being performed included a search that selected more than the maximum number of items specified by the server. The value of the ARRPC environment variable is not a legal value. but the SQL view is not in place. or 390680 through 390694 (private daemon). Operation was completed successfully. A change to the Submitter mode setting does not take effect until AR System is shut down and restarted. 390603 (the escalation daemon). this value must be 390600 (the admin daemon). 390635 through 390669 (list daemon). License will upgrade when a token is available. it is present on every form. Only the SQL view for this form is not in place. To use the default RPC socket. if you want other users to perform this active link. 390603. which is needed only if you directly access the SQL database by using the SQL view. Although this index does not show in the list of indexes. 69 Warning Creation of one of the SQL views for the form failed within the SQL database.

This field is used in the list of fields defined to be returned in the results list. A field with a length of greater than 255 bytes cannot be used in an index. 26 Error Messages Guide . 83 Warning The query list fields definition of the form has been updated to remove references to the field— the length was changed so that it is not allowed in the query list. A unique index was requested for a field type that does not allow unique indexes. A change to the limits definition of a field was made. You now have full text search (FTS) access within your permissions. This field is used in one or more indexes for the current form. A change to the limits definition of a field was made. the reference to the field that cannot be in an index was removed from the index definition for the form. the reference to the field that cannot be in the results list was removed from the results list definition. The system will try to upgrade your license type when a token is available. Full Text Search Option license token became available. To prevent an error. Delete column failed—column contents set to NULL and column renamed. To prevent an error. and the remaining indexes were rebuilt. The delete operation failed. The field is a Distributed Server Option (DSO) reserved field that can be updated only by the DSO process. 79 Warning 80 Warning Request for unique setting on database index has been ignored for fields of this type. The system uses the default database search capability on all fields.5. Request a unique index only for field types that allow it. Currently accessing the system without full text search (FTS) capability. including the fields that are FTS indexed. You previously received Warning 75. but there are no floating. A floating. but you were allowed to access the system by using the default database search strategy. Full Text Search Option license. 81 Warning 82 Warning One or more indexes were updated to remove reference to the field—length was changed so that it is not allowed in an index. A field with a length of greater than 255 bytes cannot be used in the results list. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (or unlimited). Some of the DSO reserved fields cannot be changed except by arservdsd. You are allowed access to the database but without access to the full text search (FTS) engine. renaming it in the database to avoid naming conflicts. 78 Note A Full Text Search Option license token has become available and has been allocated to you— access has been upgraded to allow full text searching. Details are displayed in an associated message. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (unlimited). License will upgrade when a token is available. You tried to delete a field from a form. An attempt was made to change one of these reserved fields. 77 Warning No free-floating Full Text Search Option license tokens are available. and setting all data values to NULL. Full Text Search Option tokens available at this time.00 76 Note A write token has become available and has been allocated to you—access has been upgraded to write access. The system performed the next closest operation by logically deleting the column. A floating write token became available. and it was allocated to you. You now have full read and write access within your permissions.BMC Remedy Action Request System 7. You previously received Warning 77 indicating you could not get a Full Text Search Option license token. You are assigned a floating. such as a currency field. and it is allocated to you.

You cannot create indexes on a join form. To prevent an error. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is used in the sort list. define the index on the base form. A field with a length of greater than 255 bytes cannot be used in the sort list. To index a field. Chapter 2 Action Request System error messages 27 . 85 Warning Indexes are ignored for join forms—build the index on the base tables. the reference to the field that cannot be in the sort list was removed from the sort list definition.AR System error messages 84 Warning The sort list definition of the forms has been updated to remove reference to the field—the length was changed so that it is not allowed in the sort list. A change to the limits definition of a field was made.

Check the network connectivity At a command prompt on a computer where the error is reported. restart the AR System server. Check the UNIX server hosts file If the server is configured to use a portmapper (TCP port = 0). Make sure the server name is spelled correctly in the ar file or the Accounts list in the Windows client Login dialog box. there is a problem with the network connection to the AR System server. nnn. If the AR System server is not running.0.nnn. and the IP address (for example. use NETSTAT -a to determine whether the server port has been assigned. If it is running.100.0. serverName).log file. check for the arforkd process.log file and the armonitor. On Windows. the fully qualified domain name (serverName.exe) is running. The port is set when the cache load has completed. If necessary. Check the server process Use operating system tools to make sure that the server process (arserverd or arserver.100 localhost TestServer 28 Error Messages Guide .nnn) of the AR System server. check the network connectivity from the computer where the error is reported. make sure the correct TCP port is included in the entry. for example: 127.BMC Remedy Action Request System 7. To check if this is the case: On UNIX. the server process is running but error 90 still appears. make sure that the localhost line in the /etc/hosts file is above the hostName line. To resolve this problem. exit and restart BMC Remedy User. error 90 can appear while the server is still loading information into the cache.00 90 Error Cannot establish a network connection to the AR System server. add the entry or (on Windows) select it.nnn. If the ping command does not return a successful reply.1 100. Check the client computer’s configuration Review the etc/ar file (utilities or other server components) or the Login > Accounts dialog box (Windows clients) to verify that the server is registered for client access. If the error was reported in BMC Remedy User. errors reporting that the server terminated are reported to these logs. consider these questions and then follow the appropriate suggestions: Is the ARERR 90 isolated to a single client computer or user? If so: Check the configuration on the client computer. If the AR System server failed during startup. issue a ping command to the server.5. review the arerror. You might need to test the connection to the server using the short name (for example. the server is behind a firewall or is not using the portmapper). If no entry is present in the ar file or the server is not marked with a green check mark in the Accounts dialog box. Is the error reported to a group of computers or users or system wide? If so: Check the network connectivity from a computer where the error is reported Make sure the AR System server process is running. The server might have been temporarily inaccessible.com).100. the server has finished loading the cache. In this case. On both UNIX and Windows. work with a network administrator to resolve the problem. If access to the server requires a TCP port (for example. The AR System server is inaccessible from the client computer where the error occurred. If the configuration is correct. When the AR System server starts up.domainName.

BMC strongly recommends that AR System administrators work closely with database support to ensure optimum database tuning. When contacting BMC technical support for additional assistance with error 92. A less common cause of this error is running an API program that is incompatible with the AR System server.5 to 4 times the number of concurrent users. It is not uncommon to run with file descriptors set to 8192 on UNIX with recent releases of AR System to ensure that adequate file descriptors are available. API and SQL logs containing the SQL statements associated with the API call that returned the time-out error. Check Windows Task Manager to see if a process is using a large number of handles If this is a recurring error. On Windows. the operation is still performed after the time-out. the default setting of 10. For more information about logging. turn on ARAPILOGGING for the client that receives the error to isolate the API call that is failing with ARERR 91. the number of file descriptors allocated to the AR System server is determined by an operating system setting in the shell where the AR System server was started. A time-out occurred while data or structures in the database were being updated. This error occurs when an RPC call fails for some reason. use ARAPILOGGING along with client workflow logging to capture the specific API call and SQL statements associated with error 92. Some possible causes of this error include but are not limited to: An invalid RPC packet was detected The AR System server is low on file descriptors (UNIX) On UNIX. Chapter 2 Action Request System error messages 29 . For information about how to configure and use client-side API logging. In this case. AR System clients use the RPC layer to connect to the AR System server’s TCP port. In most cases. custom API programs. for example: Limits found: current rlimit=8192 max rlimit=8192 BMC recommends a minimum file descriptor setting of 2. Concurrent users include other server tier components such a Email Engine. or 2048 whichever is greater.AR System error messages 91 Error RPC call failed. recompiling the API program with the same API version used by the AR System server might resolve the error. Review what was expected to be updated to verify the update did complete and retry the operation if necessary. DSO. 92 Error Time-out during database update—the operation has been accepted by the server and will usually be completed successfully. Engage your database administration support and review performance of the database itself. see the Optimizing and Troubleshooting Guide. the error can be associated with a filter action. If thread logging is turned on when the AR System server starts.000 file handles is generally sufficient. The performance of AR System server during database updates is dependent on the performance of the database. the number of file descriptors appears in the thread log. and so on. see the Optimizing and Troubleshooting Guide. and increasing the file descriptors or file handles available to the AR System server does not resolve the problem. Since this error occurs on update. provide Filter. If this is a recurrent error.

AR System server environment information. This error is often associated with a query to a form when a large number of records is returned. and so on). . . it might be necessary to modify the workflow actions or adjust the server settings to return fewer records.00 93 Error Time-out during data retrieval due to busy server—try the operation again. database. 30 Error Messages Guide . filter. ARGetListEntryWithFields.as user . */-GSI FAIL -. Run the statement from the command line and not from a database tool to more accurately reflect the time it takes. log in at the database prompt as the database owner of the AR System server in the same environment where the AR System server is running. provide at least the following information: The server API and SQL logs that capture the time when ARERR 93 occurred. If the error is isolated to a given operation or to a user or group of users. Then use the information from the client-side API log to isolate the API and SQL SELECT statement associated with the error in the client workflow log output or the in the server API and SQL logs. or by the database being too busy to respond within the timeout period. including ARAPILOGGING. along with server API and SQL logging to capture the specific API call associated with error 93. Engage your database administration support and review performance of the database itself. Possible causes can include low system resources. saving a form). use client-side ARAPILOGGING to isolate the API call that fails with ARERR 94.conf or ar. The following example shows the entry for an ARGetServerInfo call with a timeout error: */+GSI ARGetServerInfo -. see the Optimizing and Troubleshooting Guide. To troubleshoot this error. 94 Error Time-out during database search—consider using more specific search criteria.5. The performance of AR System server during database updates is dependent on the performance of the database. or server resources. including: The server operating system and version The database type and version The AR System server version and patch level A list of other applications that might share server resources with the AR System server or the database. If this error is reproducible. You can resolve the time-out error by modifying the search to return fewer records. When contacting BMC technical support for additional assistance with ARERR 93 timeout errors. BMC strongly recommends that AR System administrators work closely with database support to ensure optimum database tuning. provide the client workflow logging with API. The failed API call is marked in the log with a status of FAIL. such as thread congestion. use client-side logging. such as CPU time. A copy of the server ar. If the error occurs during a workflow search. first determine whether the timeout error is isolated to a given operation (for example. to a user or group of users. You can check the database response time for the AR System API call that generates this error by running the SELECT statement captured in the SQL logging. A time-out occurred while data was being retrieved from the server during an ARGetList call (such as ARGetListEntry. active link. and macro output captured. or is reported system wide. To do so. A time-out occurred during a retrieval operation because the server or database was busy performing other operations. This error can be caused by poorly specified search criteria. If the error is isolated to a specific operation or user.cfg file.RPC Client has timed out For more information about logging.BMC Remedy Action Request System 7.

The system allows you to connect to a single unlicensed server at any time. You can connect to only one unlicensed server in a session. This operation requires at least one specified field or value item. The Administrator Command feature was removed from the product. Make sure the proper sockets libraries are present. and retry the operation.AR System error messages 95 Error 96 Warning 97 Error RPC and sockets initialization failure. Verify the name of the item. but the parameter was not supplied. Request ID parameter value is longer than the maximum allowed length. The request ID specified for the Request ID parameter was longer than the maximum length allowed (AR_MAX_ENTRYID_SIZE. The parameter meant to hold the data that is the result of this operation is a NULL pointer. Its functionality is no longer supported. 30 characters). which enable you to define a running process in which the process runs on the server. Remember that character strings must be terminated by a 0 (zero) character. The attempt to initialize the RPC and sockets subsystems failed. The operation being performed requires a name specification for an item. Some features cannot be fully mapped from earlier versions of BMC Remedy User and BMC Remedy Administrator. Field or value list item is empty. Two servers in your environment have the same AR System server ID. The list of operations to be performed in this statistical operation is NULL or empty. NULL pointer for result list. Specify a value for the name parameter. A comparable functionality is available through active links. Retry the operation. 99 Error 100 Error 101 Error Request ID parameter is empty. Both servers are disabled until the license conflict is resolved. To return the requested data. 15 characters). Either you specified multiple unlicensed servers to connect to or workflow is accessing a second unlicensed server. Name parameter (or name field in a parameter) is empty. Specify a list of one or more operations to be performed. Two servers have been encountered with the same AR System server ID—neither will be accessible until one is shut down and the tools started again. You must license your servers to connect to them at the same time from a single client tool. You can connect to any number of licensed servers. Statistics list is empty. 102 Error 103 Error 104 Error 105 Error 106 Error 107 Error Chapter 2 Action Request System error messages 31 . Connection has been attempted to two unlicensed servers. Request ID list is empty. this time specifying the request ID for the entry. The list of requests selected to perform the statistical operation on is NULL or empty. The name specified was longer than the maximum length allowed (AR_MAX_NAME_SIZE. The operation being performed requires the request ID to be specified. Feature not supported by this AR System client. 98 Error The Administrator Command feature is no longer supported. Verify the request ID of the entry. but no name was specified. The field or value list parameter for this call is NULL or contains zero items. Connection to the second server is denied. Name parameter (or name field in a parameter) is longer than the maximum allowed length. Specify a list of one or more requests to perform the statistical operation. this parameter cannot be NULL. and retry the operation. Remember that character strings must be terminated by a 0 (zero) character. and retry the operation.

5. You might have specified an illegal display type. The command string that issues an external command to the operating system is empty or is too long. In a field operation. you must reduce the command to the maximum length allowed (AR_MAX_COMMAND_SIZE. When they are expanded.h have legal values for this field.h have legal values for this field.BMC Remedy Action Request System 7. Unrecognized data type for default value. Character menu definition is empty. If empty. Verify that the #define statements in the include file ar. This parameter is a mask of one or more operations on which the filter might execute. Make sure that the file name you specified is a legal name. Filter does not have an action defined. the list containing the selection values for a selection type field is NULL or empty. Verify that the include file ar. If too long. the command line might expand to 4.096 bytes. label positioning. 32 Error Messages Guide . Entry error in the name list. File name is longer than maximum allowed file name. The structure you specified for defining the character menu for a field is either NULL or empty. or option.00 108 Error Field display definition is incorrect. you must set the option to AR_FIELD-OPTION_DISPLAY.h have legal values for this field. For example. This error relates the associated error to the name list instead of to another parameter in the call. you must supply a command.h have legal values for this field. 255 characters). you must supply a menu definition in this parameter. If you are defining a character menu. The action field for a filter is either NULL or empty. Operation mask parameter is out of bounds. 255 characters). Name list parameter is empty. filter. The value you specified for the data type parameter is not one of the legal values recognized by the system. Verify that the #define statements in the include file ar. The filter operation set parameter is invalid. This message can result from a change to the display option—either setting it or removing it—where this is not allowed. or escalation. During processing of a list of names (such as selection value names). A filter must define at least one action. the command string might contain parameters. This parameter either has an empty mask or has values outside the limits on the mask. Command string is empty or longer than the maximum allowed length. An associated message describes the problem. The file name parameter you specified is longer than the maximum file name allowed by the system (AR_MAX_FULL_FILENAME. Unrecognized data type. A selection field must contain one or more legal values. Remember that character strings must be terminated by a 0 (zero) character. if you create a trim or a control field. Verify that the #define statements in the include file ar. one or more of the values was invalid. One or more of the fields in the display structure for the field are invalid. The unexpanded line is limited by the value defined by AR_MAX_COMMAND_SIZE. The value you specified for the data type field of the ARValueStruct parameter defining the default value is not one of the legal values recognized by the system. or is inappropriate for usage in this case. Note that if the command being created is in an active link. 109 Error 110 Error 111 Error 112 Error 113 Error 114 Error 115 Error 116 Error 117 Error 118 Error Unrecognized or inappropriate value for field option. Verify that the #define statements in the include file ar. The value you specified for the field option parameter is not one of the legal values recognized by the system.h has legal values for these fields.

For a character field. Also. An associated error message contains details. Verify that the #define statements in the include file ar. One of the statistical operation codes is not recognized. Field limit definition is invalid. one or more of the values was invalid. verify that the value is a legal value for the field. verify that the specified character menu.h have a list of the valid permission tags. make sure that the pattern is within the size limit of the field. Entry error in the permission list. the menu style setting. and the match operation setting are legal. or a leaf item was specified but no leaf string exists. AR System server is a newer version than your client software.h have legal values for this field. To retrieve information. Unrecognized character menu item type. Chapter 2 Action Request System error messages 33 . Verify that the #define statements in the include file ar. A child menu tag was assigned but no child menu exists. This error connects the associated error to the ID list instead of to another parameter in the call. You specified a code for server information that was not recognized. Verify that the #define statements in the include file ar.h have a list of all valid codes that can be specified.h have a list of all valid character menu type tags. Unrecognized statistics operation. An associated message describes the problem. Verify that the #define statements in the include file ar.AR System error messages 119 Error Unrecognized create mode. 120 Error 121 Error 122 Error 123 Error 124 Error 125 Error 126 Error 127 Error 128 Error 129 Error 130 Error 131 Error Entry error in the character menu.h have a list of all valid operation codes. One of the permission tags is not recognized. Entry error in the statistics list. Unrecognized server information tag. One of the entries in the character menu is invalid. One of the items specified in the field or value list contains an error. Unsupported data type in this client. During processing of a list of request IDs. One of the entries specified in the statistics operation list is invalid. Unrecognized permission tag. Verify that the #define statements in the include file ar. One of the character menu type tags is not recognized. An associated error message contains details. One of the items in the permission list is invalid. and retry this request. The field limit specified for this field is invalid. For a selection field. Your client is too old to display one or more fields on this form. An associated error message contains details. Install an updated client. make sure that the high range is greater than the low range. Entry error in the Request ID list. The value you specified for the list of information to retrieve from the server was NULL or empty. ARServerInfoRequestList structure is empty. specify what information you are trying to retrieve. Entry error in the field/value list. The value you specified for the create mode parameter is not one of the legal values recognized by the system. For a numeric field.

you must have a list of the options to get or set. Verify that the #define statements in the include file ar. Option cannot change for core or reserved field that has a fixed options definition. which eliminates the default value and is not allowed. 139 Error 140 Error 141 Error 142 Error 143 Error 144 Error 34 Error Messages Guide . One of the items specified in the structure list is invalid. You specified the tag AR_COND_OP_NONE as the tag for an ARQualifierStruct structure when this structure was not at the top level of a qualification. Unrecognized structure item tag.00 132 Error 133 Error 134 Error 135 Error 136 Error 137 Error 138 Error Structure item is empty. You are trying to change the definition of the Status field. The code for the type of error message to return is invalid.h have a list of all valid tags.h have a list of all allowed notify mechanisms. Entry error in the structure item list. To perform a structure operation. One of the filter action codes was not recognized. Unrecognized message type. The core fields of the system have restrictions on what changes are allowed. You can alter the number of states and change the default value. Verify that the #define statements in the include file ar. or escalation message number must be greater than 10000. Verify that the #define statements in the include file ar. Numbers less than 10000 are reserved for AR System. Restructure the call to remove the tag from the middle of the tree. Unrecognized operation in qualify conditions. active link. Verify that the #define statements in the include file ar. The code specified for the notify mechanism in one of the filter actions is invalid. You are trying to change a characteristic of a core or reserved field that cannot be changed in the way you are requesting. Unrecognized filter action type. Unrecognized notify mechanism. Verify that the #define statements in the include file ar.h have a list of all valid message types. The tag for one of the nodes in the qualify condition structure is invalid. A default must be active for the Status field. The value portion of a relational operator qualification structure is NULL. Verify that the #define statements in the include file ar. The message number of a message you define through the Message action of a filter. One of the structure option tags is invalid. The Status field must have a default value. Can use the Qualify None option only at the top level of a qualification. Restrict your errors to values greater than 10000 to avoid conflicts between errors you add to the system and errors from AR System.h have a list of all filter action type tags. An associated error message contains details.BMC Remedy Action Request System 7. This tag indicates no qualification. The structure list parameter is NULL or is an empty list. Relational operation is empty.h have a list of all valid tags. Review the Form and Application Objects Guide for information about the restrictions for each of the core fields. or escalation must be greater than 10000.5. Unrecognized relational operation. Specify a value for a relational operation. The tag for the relational operation to perform is invalid.h have a list of all valid structure tags. active link. but you cannot eliminate it. Filter.

Return buffer is NULL. Load this parameter with the name of the form you want to reference. The buffer that holds the return value of the call was passed a NULL value. Supply a pointer to the input buffer for this parameter.AR System error messages 145 Error 146 Error 147 Error 148 Error 149 Error 150 Error 151 Error 152 Error 153 Error 154 Error Arithmetic operation is empty. The value portion of a field. You cannot specify IDs in this range for fields you create. The server field of the ARControlStruct parameter is empty. Required form parameter is missing.h have a list of the valid tags. but the value passed is either NULL or an empty string. This error usually occurs when there are too many processes running or some processes have grown to occupy most or all available memory space on the client. Unrecognized sort method. The value specified for the sort list parameter is invalid. For the call to return the data requested. Specify information for an arithmetic operation. or arithmetic value is invalid. The form parameter is required. Perform the call again. Supply the name of an AR System user in this field. Supply a value for this parameter. Specify information for this structure. there must be a value specified for this parameter. Unrecognized ARFieldValueOrArithOp structure tag. IDs of less than 100 are reserved for AR System. The tag specified for the arithmetic operation is invalid. Entry error in the sort list. ARFieldValueOrArithOp structure is empty. The system encountered an error during a call to allocate memory space. View the #define statements in the include file ar. For this call to perform the requested operation. value. Restart processes that have been running for a while to recover space the applications might have leaked over time. value. there must be a parameter specified to hold a pointer to the result. or arithmetic structure is NULL. The name field of the ARControlStruct parameter is empty.h for a list of the valid codes.h have a list of all valid tags. Malloc error in client library. You specified a field ID of less than 100 for a new field. Verify that the #define statements in the include file ar. Input buffer is NULL. A server name must be supplied in the control record. A user name must be supplied in the control record. Unrecognized arithmetic operation. The value portion of an arithmetic operator qualification structure is NULL. The buffer to hold the input value to the call was passed a NULL value. Field IDs below 100 are reserved for core fields. specifying a field ID greater than 100. The code for the specified sort method is invalid on one of the entries in the sort list. You can recover the memory space by shutting down unneeded processes. Supply the name of the server to reference in this field. The failure occurred on the client during processing of the call to or from the server. 155 Error 156 Error 157 Error Chapter 2 Action Request System error messages 35 . Verify that the #define statements in the include file ar. The tag for the type of the field. An associated error message provides details.

Notify text is empty or too long. If there are items. 12/25/01 is compatible with AR_DATA_TYPE_TIME. The data type of the default value must be compatible with the data type of the field. The format of the compressed data was not correct. This field is a character string containing from 5 to 15 characters. the numItems field must be initialized to 0. 159 Error A server name must be supplied. Invalid session identifier supplied in the control record. You requested a modification to the length of the Request ID field. but not with AR_DATA_TYPE_CHAR). All other combinations are illegal. You must correct your text string to 255 characters or less. 161 Error 162 Error 163 Error 165 Error 166 Error 36 Error Messages Guide . review the appropriate workflow logs and the workflow configuration to determine the cause of the problem. If there are no items. The text you specified is over that limit. The combination of the prefix and the total length allowed for the field must allow at least 5 characters free for the integer portion of the ID. There was a failure in decompressing the data being processed.00 158 Error Request ID field must contain at least 5 non-defaulted spaces. A parameter was specified that contains a numItems value that indicates one or more items for the parameter.BMC Remedy Action Request System 7. The session identifier in the control record is invalid. the value field must point to the items. This error can occur when the workflow uses a dynamic design (SAMPLE DATA data source) that supplies the server name at run time. for example. You are allowed to specify a default value of from 0 to 10 characters that acts as a prefix to the generated IDs.5. A default value of AR_DATA_TYPE_NULL is always compatible with any data type. the combination of the length you specified for the field and the default value prefix leave less than 5 spaces. and a server name is not specified. The data type specified as the default value for the field does not match the data type defined for the field. such as Open Window.h for a list of the valid tags. If you receive this error. The workflow or user must supply the correct server name. Field default type and data type do not match. A default value of the same type as the field is always compatible. Unrecognized notify field ID tag. Items specified are NULL pointers. This message occurs while creating or adding a workflow action. View the #define statements in the include file ar. The session identifier is set in the control record by the ARInitialization() function and is valid until a call to ARTermination() is made. A keyword value is compatible with the data type that matches the type of the resulting keyword (for example. The notify text you can specify for a notification is limited to 255 characters before expansion. but the value field in the structure is a NULL pointer. or Service. Character strings must be terminated by a \0 character. In this case. 160 Error Decompression has failed. The tag for the notify fields structure is invalid. Call Guide. when saving an attachment in the Save-Attachment Run Process filter command.

The status field value you specified does not match a defined status for this form. It indicates that the field has no limit. AR_DATA_TYPE_ENUM. the problem is an attempt to define an assignment between incompatible data types or to nonexistent fields. The only supported values for the tag field are AR_STAT_HISTORY_USER and AR_STAT_HISTORY_TIME. The tag that specifies whether you want the user name or time stamp for a status history value is not a recognized value. active link. 170 Error 171 Error 172 Error 173 Error 174 Error Display type specified is inappropriate for the data type. The data type in the limit structure must be compatible with the data type of the field. AR_DATA_TYPE_DIARY. or escalation definition contains a value out of range. 168 Error Error in one of the field or value assignments in the set fields action of a filter. This could be due to the service being stopped by the administrator prior to completion of its startup tasks or an error occurred that prevented the service from starting. or escalation definition. A default value of the same type as the field is always compatible. with items at lower values being performed before items at higher values. leave the language buffer empty (set to an empty string).AR System error messages 167 Error Field limit type and data type do not match. Status history selection value is out of range for status definition. and AR_DATA_TYPE_TIME Chapter 2 Action Request System error messages 37 . active link. 169 Error Execution order value is out of range. the language to use is picked up from the LANG environment variable. Service was not started. The selection value specified is a 0-based. You can set this value to any language your environment supports. To use the default language. You must choose an appropriate display type: Display type AR_DISPLAY_TYPE_CHECKBOX —supports data type AR_DATA_TYPE_ENUM Display type AR_DISPLAY_TYPE_CHOICE—supports data type AR_DATA_TYPE_ENUM Display type AR_DISPLAY_TYPE_NUMTEXT—supports data type AR_DATA_TYPE_INTEGER Display type AR_DISPLAY_TYPE_TEXT—supports data types AR_DATA_TYPE_INTEGER. All other combinations are illegal. The execution order field of the filter. The data type specified in the limit for the field does not match the data type defined for the field. Unrecognized status history tag. Consult the Application Event Log for details concerning any errors that occurred. If you are coding directly to the API. An associated message provides details. Usually. A default value of AR_FIELD_LIMIT_NONE is always compatible with any data type. The legal range for the execution order is 0 to 1000. AR_DATA_TYPE_CHAR. AR_DATA_TYPE_REAL. or escalation definition. You can also set the language to the default language of C to use the standard language defaults. The Windows Service was not started. Language specified in the control record not recognized—using default language on server. An error occurred with one of the field or value assignments in the Set Fields action of a filter. active link. positional index into the list of states defined for Status. If you are running one of AR System tools. Verify the setting of that variable and correct it if it is wrong (or delete it if the default language is sufficient). The display type value specified for this field is not compatible for the data type of the field. The language you specified for the system is not recognized by the server. the language field is in the control record passed to each call.

The length or numRows (number of rows) value for the display parameter is not within the allowed range. 182 Error Too many actions have been specified for this filter. the length field must not be zero (0). You specified a group ID more than once in the permission list you are sending to the system.00 175 Error The length or numRows value of the display parameter is out of range. active link. Cannot specify change access for a view-only group. For fields displayed as TYPE_CHECKBOX or TYPE_CHOICE. neither the length nor NumRows field should be zero (0). an API call can set the flag to 0 to have the system generate a unique ID. This is likely caused by a programming error. assign this field to 0. The length field specifies the width of the control. Duplicate group ID was specified in permission list. The value specified as the default value for a character field is longer than the maximum allowed by AR_MAX_DEFAULT_SIZE (256 bytes). the group is a View group and cannot be granted change permission. If you want the system to assign an ID. Reduce the number of actions by combining several action steps into one or by creating a second filter. The system returns the assigned ID. active link. The length specifies the width of the control. For fields displayed as TYPE_TEXT. Field ID parameter is NULL. Remove the duplicate reference. load this parameter with the value. and retry the operation. 176 Error 177 Error Duplicate selection value exists in the selection or bitmask value list. or escalation and separating some of the actions into the new filter. however. active link. Alternatively. It must be a pointer to a field ID. must be a pointer to memory. Rename one of the duplicate selection values so that each selection or bitmask value has a unique label. and the NumRows field specifies the number of rows of data that are displayed for the field. Any given ID can be specified only once with the permissions allowed for that group field. or escalation. the same name is used for two separate states. [c-a]). active link. or escalation has more actions defined than the maximum allowed by the system (25). Pattern in a character limit is invalid. To assign the ID for a field. Typically. The field ID parameter is a NULL pointer. 183 Error 38 Error Messages Guide . You can assign only view permission to the field for this group. and the length value is ignored. An API call did not set the flag indicating that it allows creation of fields in this range. and the system assigns a value and returns the result in this field. In the list of selection or bitmask values. or escalation. The filter. the numRows field must not be zero (0). API calls must set that flag to allow the creation of a field with this ID. Verify the default value. For fields displayed as TYPE_NUMTEXT. and the number of rows value is ignored. 178 Error 179 Error 180 Error 181 Error The ID specified for this field is in the reserved field range. Character strings must be terminated by a 0 (zero) character. The ID for the specified field falls within the reserved range of field IDs. Default value for a character type is longer than the maximum allowed length AR_MAX_DEFAULT_SIZE. You specified that a group must be given change access to a field.5. the pattern either has an opening bracket ([) with no matching closing bracket (]) or has a range within double brackets ([ ]) with the starting value greater than the ending value (for example. The pattern specified for a limit to the character field is illegal. The numRows field specifies how many rows the check boxes or choices must be displayed in.BMC Remedy Action Request System 7.

One of the active link action codes is not recognized.h have a list of all ARAssignFieldStruct tags. Field or assignment list item is empty. Modified Date. Modified Date. Unrecognized tag for filter. active link. The action field for an active link is either NULL or empty. Unrecognized assign type. Verify that the #define statements in the include file ar. or escalation set field definition is missing. Last Modified by. One or more fields. so no default value is needed or allowed. or assignment items in the field or assignment list. The only system-controlled core field that can have a default value assigned to it is the Request ID field. The ARAssignFieldStruct structure tag is not recognized. See the associated message for details. The system-controlled core fields cannot be assigned values by the user. Filter. The execute mask is a bitmask of the conditions under which an active link executes.h have a list of all assign type tags. You assigned a character menu to a system-controlled AR System core field (Request ID. Specify a default value that does not contain a quotation mark character. Specify the field where you want to attach the active link action. Active link does not have an action defined.h have a list of all active link action type tags. Create Date. A Set Fields action must define at least one field to be assigned a value. The field or assignment list for an active link Set Fields action is either NULL or empty. Last Modified By. Entry error in the field or assignment list. The active link you defined has the On Return or On Menu choice condition set in the execute mask. Cannot assign character menu to system-supported core or reserved fields. Verify that the #define statements in the include file ar. Verify that the #define statements in the include file ar. where the default is used as a prefix to the ID. The field definition in the field or assignment structure is set to NULL.AR System error messages 184 Error Cannot specify a quotation mark in default value for Request ID field. 185 Error 186 Error 187 Error 188 Error 189 Error 190 Error 191 Error 192 Error 193 Error 194 Error 195 Error Chapter 2 Action Request System error messages 39 . or Status History field). Supply a field definition value in this structure. active link. The bitmask can be created by totalling the set of defines that represent the conditions under which you want the active link to execute. so a character menu is not needed or allowed. Execute mask parameter is out of bounds. You assigned a default value to a system-controlled AR System core field (Request ID. The other AR System system-controlled core fields are automatically updated by the system. The default value for the Request ID field (used as the prefix for the IDs generated for each entry or request) cannot contain a single quotation mark character. encountered an error. Unrecognized active link action type. Execute mask setting requires a field choice. or Status History field). or escalation set field action. The value you specified includes bit settings outside the legal range of conditions under which you can execute an active link. Create Date. An active link must define at least one action to be performed. but no setting indicates which field to attach the operation to. Cannot assign default value to system-supported core or reserved fields (except Request ID). The assign type tag is not recognized.

200 Error 201 Error 202 Error 203 Error 204 Error 206 Error 207 Error 208 Error 40 Error Messages Guide . Notify user name is longer than the maximum size allowed for the name. Unrecognized character menu type. or on the qualification bar. Unrecognized keyword. The name specified for the user to be notified is too long (the maximum is defined by AR_MAX_NAME_SIZE. but the keyword identifier was not recognized. using it as the default itself creates a self-reference that cannot be resolved.h for a list of IDs for all supported keywords. 199 Error Missing or blank name for a macro parameter in the active link action.00 196 Error 197 Error 198 Error Macro branch of active link action must include both a name and macro text. This operation requires at least one value item to be specified. Unrecognized character menu refresh code. The value list parameter for this call is NULL or contains 0 items. You can omit parameters from the list of parameters. The value specified for the notification priority is outside the legal bounds for this field. If an arithmetic operation is involved or the operation is a complex one. Therefore. Notify priority is out of range (must be 1 to 10). the $DEFAULT$ keyword is disallowed in qualifications. The $DEFAULT$ keyword indicates that the default value must be used for the value. A keyword type value was specified. whether in an active link. The value specified as the default value for a character field is longer than the maximum allowed by AR_MAX_MACRO_VALUE (255 bytes). Verify the default value. filter. The keyword $DEFAULT$ cannot be used when specifying the default value for a field. View the include file ar. 30 bytes). The keyword $DEFAULT$ cannot be used when specifying a qualification. View the #define statements in the include file ar. but if they are included on the list. View the #define statements in the include file ar. Unrecognized or misused tag for field/value definition. supply the parameter name for the value you are specifying. The definition of a macro action must include both a name and the text of the macro to execute.BMC Remedy Action Request System 7. Unrecognized character menu file location. Cannot use the $DEFAULT$ keyword as a default value or in a qualification. Value list is empty. View the include file ar.h for a list of the valid codes. The ARCharMenuStruct structure tag is not recognized. Character strings must be terminated by a \0 character. The code for the location of the file for the character menu is not one of the defined choices. When specifying macro parameters. Macro value string is longer than the maximum length allowed. One or the other is either NULL or an empty string. A name field in the list of macro parameters is either NULL or blank. The code for the refresh interval for the character menu is not one of the defined choices. you must provide a name. Specify a name within the length restrictions. where 1 indicates the highest priority and 10 indicates the lowest priority.h for a list of the valid codes. The tag for indicating the type of field or value reference is undefined or is not allowed in the current context for the ARFieldValueOrArith structure. Specify a value between 1 and 10 for the priority.5. and retry the operation. or escalation. it is not clear which field’s default value is being referenced under all conditions.h for a list of the recognized ARCharMenuStruct tags.

Query value structure is empty. Remove one or more fields from the index definition to reduce the total length of the index information. You are not allowed to view this information. the settings with their values must be specified. is an empty string. setting only values that can be updated. The code specified for a local variable is outside the legal range for local variables. Server information associated with this tag cannot be updated. specify a query value structure definition that defines the form and conditions on that form. 211 Error 212 Error 213 Error 214 Error 216 Error 217 Error 218 Error 219 Error 220 Error 221 Error 222 Error Chapter 2 Action Request System error messages 41 . Server information data associated with this tag uses an incompatible data type. Query value structure item contains an error.AR System error messages 209 Error 210 Warning File name for a character menu is NULL. Your index definition specifies an index on no fields or an index on more than the maximum allowed number of fields. One of the items in the list of field definitions is invalid. The file name for a character menu is a pointer to NULL. The qualifier parameter must be a pointer to memory. or too long. Local variable number is out of range (must be 0 to 10). Define a legal file name for the character menu file. The query value structure pointer is NULL. Total length of all fields involved in an index is greater than maximum allowed length. or is longer than the maximum allowed length for a file-name. the display list containing information about the display definition for the field is NULL or empty. The server information for the specified tag represents information that has a different data type from the type specified in the update operation. Retry the operation. To define an assignment to a value from another form. specifying the correct data type for the value. To set one or more pieces of server information. ARServerInfoList structure is empty. Retry the operation. The server information for the specified tag is read-only data. Server information associated with this tag cannot be retrieved. Qualifier parameter is NULL—must be a pointer to memory. requesting only values that can be retrieved (viewed). This list of field definitions is for fields displayed in the query list. The server information list is either NULL or empty. See the associated error message for details. This memory location is where the base of the qualifier structure for the string being parsed is stored. A field must define at least one display definition. empty. One of the structures in the list of fields to display in the query list is invalid. Display list is empty. An index definition must reference from 1 to the number defined by AR_MAX_INDEX_FIELDS (10). Either zero or greater than the maximum number of allowed fields are specified in a single index. The server information for the specified tag is write-only data. If you receive this error when doing a field operation. See the associated error message for details. One or more of the fields in the query definition of an assignment operation contains an error. You are not allowed to update this information. The sum of the length of all fields specified for the index is greater than the maximum allowed for an index by AR_MAX_INDEX_BYTES (255 bytes). Specify a number between 0 and 10. Retry the operation.

or escalation. the parameter list can be NULL. The tag refers to an operation supported only during a filter or active link operation. A function definition that was specified has an error with the specified parameters. View the include file ar. Unrecognized value for set focus characteristic. but the count of parameters must be set to 0. but the number of items indicates one or more parameters. but the function code was not recognized. A Set Fields action in a filter or escalation can reference other forms for pulling data to the current request. The type of value specified in the ARFieldValueOrArithStruct structure is not allowed in a query list. The types of the values in a value set are not compatible. The code for the field where you want to set focus in the set field characteristics action of a filter is not one of the defined choices.h for a list of the valid codes. Choose another operation (for example. You defined a reference to a form on a different server.BMC Remedy Action Request System 7. All types must be the same or compatible types. To define an assignment to a function result. If the index is a multiple-field index. value. Cannot index a diary field. the referenced form must be on the same server. is not one of the defined choices. Unrecognized value for set access option characteristic. View the include file ar. Either the wrong number of parameters was specified. you can still create the index if you remove the field that is not allowed. the parameter list must contain the parameter values. of the Set Fields characteristics action of a filter. or a field with a maximum length over 255 bytes. active link. In a Set Fields action for a filter. The tag specified for the action to take if there are multiple matches in the ARQueryValueStruct structure is not a legal tag. or one or more of the parameters is the wrong data type. 225 Error Set fields actions that reference entries in other forms can only reference forms on the same server in a filter or escalation. perform the operation in an active link). A function was defined. or arithmetic operation is not supported on the GetListEntry operation. View the definition of the function to verify the parameters. If there are no parameters. 226 Error 227 Error 228 Error 229 Error Type of field.h for a list of valid function codes. one of the settings assigned the result of a function.h for a list of the valid codes. The function structure pointer is NULL. Wrong number of parameters or invalid parameter values specified in function for the field. 230 Error 231 Error 232 Error 233 Error 42 Error Messages Guide . specify a function definition that defines which function is to be performed and that provides the parameters to perform the function. Unrecognized function code specified. View the #define statements in the include file ar. or move the remote form to the server where the filter or escalation is being defined.5. Parameter list for a function is empty. The code for the set access option field. Fields that have lengths longer than 255 bytes (including diary fields and unlimited length character fields) cannot be indexed. Function definition is empty. an unlimited length field. The ID of the field that the function is associated with is reported. The parameter list for a function is NULL. If the number of items indicates parameters. You specified an index that includes a field that meets these criteria.00 223 Error 224 Error Unrecognized value for the query value multimatch code. However. The data types of the values in a value set are incompatible.

a character field with unlimited length or maximum length over 255 bytes (254 bytes for DB2). The time-out value can be as low as 1 second and as high as 20 seconds. Verify the values. Cannot specify a diary field. and correct as appropriate. You specified a sort that includes a field that meets these criteria. 238 Error 239 Error 240 Error Value for DDE item is larger than the maximum allowed length. The type of value specified in the ARFieldValueOrArithStruct structure is allowed only in a filter qualification.h for a list of supported codes. Specify a tag allowed outside a filter qualification. Verify the #define statements in the include file ar. The value specified in the DDE item field is larger than the maximum allowed (32767 bytes). or arithmetic operation is supported only for a filter qualification. Value specified for DDE service name or topic is missing or is larger than the maximum allowed length. or Status History as a field in a Get List description. The DDE service name or topic field of the DDE active link action is missing or is too large. and the Status History field) cannot be specified as fields in the list returned by the Get List operation. Value specified for the license time-out must be 1 or greater (in hours). To define an assignment to a DDE result.h for a list of supported codes. The value remains unchanged (defaults to 2 if nothing is set). The code for the DDE action to perform is not one of the legal codes. DDE definition is empty. Specify a sort list that does not include this field. The value specified for the license time-out value was 0 or a negative number. Remove this field from the list. For IBM® DB2® databases. specify a DDE definition that defines which DDE operation is to be performed and that provides the values to perform the operation. Retry the operation with the value in this range. Both of these fields are required. The code for the type of user list to retrieve is not one of the legal codes. and correct them as appropriate. This value must be greater than or equal to 1 hour. Verify the value.AR System error messages 234 Error Value specified for the filter or escalation set fields process time-out is outside the valid range of 1 to 20 seconds. 241 Error Cannot specify a diary field. 244 Error Chapter 2 Action Request System error messages 43 . value. 235 Error 236 Error 237 Error Unrecognized code for user list type. Fields that have lengths over 255 bytes (including diary fields. unlimited length character fields. View the #define statements in the include file ar. The filter Set Fields process time-out value is not in the legal range. or Status History as a sort field. Unrecognized value set for DDE action code. The path to the program field of the DDE active link action is missing or is too large. the limit is 254 bytes. unlimited length character fields. This field is required and has an upper limit of 255 bytes. and both have an upper limit of 64 bytes. and the Status History field) cannot be specified as sort fields. Verify the value. 242 Error 243 Error Type of field. Value specified for DDE path to program is missing or is larger than the maximum allowed length. and correct if necessary. The DDE structure pointer is NULL. Fields that have lengths over 255 bytes (including diary fields. You specified a list that includes a field that meets these criteria. a character field with unlimited length (or maximum length over 255 bytes).

The format specified for the day portion of the time is not recognized. There are two or more instances where the same display tag is used.h).h for a list of the submitter modes. Review the structure definitions in the include file (ar.h).h for a list of the server statistics tags supported.00 246 Error 247 Error 248 Error 249 Error 250 Error 251 Error 252 Error 253 Warning Invalid day format. Invalid hour selection. The format specified for the day portion of the time is not recognized. The value specified for the flag to enable or disable a structure is not recognized. and correct the definition to match the rules defined there. The tag specified for the server statistics structure is not recognized. Invalid interval time. Review the structure definitions in the include file (ar. and retry the operation. and correct the definition to match the rules defined there. One or more groups in the list of groups granted Subadministrator access to a form does not exist. Unrecognized submitter mode. One or more groups in the list of groups for the Subadministrator is not a group defined on this system. Fix the definition to supply unique tags. Review the structure definitions in the include file (ar. Unrecognized group in the Subadministrator group list for the form. A display tag to identify the view desired is not unique. View the #define statements in the include file ar. active link. The format specified for the hour portion of the time is not recognized. The format specified for the time portion of the time is not recognized. The group must exist to be assigned Subadministrator access to the form. Invalid day selection. 255 Error 256 Error 257 Error 44 Error Messages Guide . Each display tag must be unique. Review the structure definitions in the include file (ar.5. Review the structure definitions in the include file (ar. or you can update the definition of the form to remove the undefined IDs. or escalation. The value specified as the subject line for an email notification is longer than the maximum allowed by AR_MAX_NOTIFY_SIZE (255 characters). Duplicate tag used for several items within the display list. 254 Error Subject line is longer than the maximum length allowed. and correct the definition to match the rules defined there. and correct the definition to match the rules defined there. The format specified for the minute portion of the time is not recognized. The character strings must be terminated by a 0 (zero) character.h). and correct the definition to match the rules defined there. Set the value to True (1) to enable the structure or False (0) to disable it. and the import is completed successfully. Invalid minute selection. Unrecognized server statistics tag. The operation being performed is an import.h). You can define groups with the missing IDs. View the #define statements in the include file ar. Inappropriate group in the Subadministrator group list for the form in import. Verify the subject line value.h). The problem is treated as a warning. The code specified for the submitter mode is not recognized.BMC Remedy Action Request System 7. Invalid value for enabling or disabling a filter.

390636 through 390669.h for a list of the save login codes. Make sure that the definition of the view form is complete and accurate. unlimited length character fields. Verify the definitions in the include file ar. The qualification specified for a join form is invalid. 390680 . specify either 390600 (the Administrator server) or a value in the ranges 390621 through 390634.390694). 390636 . Verify that the #define statements in the include file ar. Unrecognized multiple match code. this structure is required. Verify the qualification. The value supplied as the RPC socket number. Invalid join form qualification. The code specified as the multiple match code (the action to take when there are multiple matches to the values in a Set Fields action) is not recognized. 259 Error Unrecognized no match code. and the Status History field) cannot be specified as fields to group by. to be used by the DSO daemon for access to AR System. a character field with unlimited length (or maximum length over 255 bytes). When a join or view form is defined. Compound form structure is empty. 390621 . Specify a grouping that does not include this field. Define a valid server name for the character menu file. inclusive. The code specified as the no match code (the action to take when there are no matches to the values in a Set Fields action) is not recognized. The server name for a character menu is an empty string or is longer than the maximum allowed length for a file name. is not a legal socket number. specify the command. For more information about using RPC sockets with DSO.AR System error messages 258 Error The RPC socket number for the Distributed Server process is not one of the legal values (390600. it must be a legal qualification that associates the two forms. The definition of the view form is invalid. Invalid join member form name.390634. Cannot specify a diary field. Fields that have lengths over 255 bytes (including diary fields. or 390680 through 390694 (private servers). and update it so that it is an acceptable join definition. The compound form structure is empty or has missing pieces. and set this structure to point to it.h have a list of all no match codes. 264 Error 265 Error 266 Error 267 Error 268 Error Chapter 2 Action Request System error messages 45 . Specify a join criteria for the join form. For the operations that the server must perform. or Status History as a field to group by. so the system cannot create a “clean” interface to the non-AR System table. 260 Error 261 Error 262 Error 263 Error Unrecognized save login code. The SQL command pointer is NULL or points to an empty string.h have a list of all multiple match codes. Server name for a character menu is empty or is too long. SQL command is NULL or empty. You can only create a join between existing forms. To define an operation that executes a SQL command. The name specified for either the primary or secondary form in a join form definition is not a legal name or does not exist in the current server. Verify that the #define statements in the include file ar. You specified a grouping that includes a field that meets these criteria. The code specified as the save login code (determining whether the user or the administrator has the ability to set the save login option on the client) is unrecognized. see Distributed Server Option Guide. Invalid view form definition.390669. One or more “pieces” of the view definition is missing or invalid.

Because join forms are relational joins of base tables. or view) is created. A form field is tied to an invalid index. an option controls whether the field can be deleted if it is used in the join qualification of a join form. Specify appropriate contents for this structure. and this action is not supported. The table referenced in a view form must exist before the view form can be created. A value for a selection field cannot exceed 2. but one or more join forms depend on this form. When deleting a field. The value of the index is not 0 or 1 in this case. To override this error. Invalid field mapping type. the structure is empty. To override this error. View the #define statements in the include file ar. 46 Error Messages Guide . To index one or more fields. Invalid compound form structure change. When deleting a form. specify an index (of 0 or 1) indicating whether the field is tied to a field in the primary or secondary form.147. For this call. 270 Error 271 Error 272 Error 273 Error 274 Error 275 Error 276 Error 277 Error The field is referenced by a join form as a base field.483. The fields in the join forms that are dependent on this field are also deleted. The fields in the join forms that are dependent on this field are also deleted. The field type in the field mapping specified for a field in a compound form is not recognized.h for a list of the recognized form types. Invalid base form index in a join field mapping structure. and one or more fields in some join forms depend on this field.5. specify the delete option AR_FIELD_FORCE_DELETE. View the #define statements in the include file ar. Field mapping structure is empty. This error indicates that an attempt was made to delete this field. an option controls whether the form can be deleted if a join form depends on this form. Invalid external table name in a view field mapping structure. The form is referenced by a join form as a base form. This error indicates that deletion of a form was attempted. specify the delete option AR_SCHEMA_FORCE_DELETE. When defining a join field reference in a join form. which deletes the field despite the dependency. which deletes the field despite the dependency.647. The join forms dependent on this form are also deleted. 278 Error The field is referenced in the join qualifier of a join form of which this form is a member. and the field is used in the qualification of a join form. To override this error. Index not allowed in this type of form. you cannot define indexes on join forms. specify the delete option AR_FIELD_FORCE_DELETE. or the table does not exist. join. specify the indexes on the base tables that underlie the join.h for a list of the recognized field types. The compound structure requested a change to the form type. The field mapping structure is required when defining a data field on a join or view form. The form type tag specified for the compound form structure is not recognized. After a form (base. 279 Error Selection Value ID too large. The table name identified in the view form definition is illegal. The form structure is empty and is not allowed. you cannot change the form type. This error indicates that an attempt was made to delete this field. Change the index to indicate the appropriate form.BMC Remedy Action Request System 7. When deleting a field. which deletes the form despite the dependency. an option controls whether the field can be deleted if it is referenced by a join form that depends on this field.00 269 Error Invalid form type in compound form structure.

but another view is set as the default. Only data fields can be included in qualifications. In older versions of the AR System server.AR System error messages 281 Error AR System server does not support multiple links to the same button. Chapter 2 Action Request System error messages 47 . Cannot create nested outer join form in Sybase or SQL Server. The text string might contain parameter references that are expanded before the message is delivered. Display only fields cannot be included in a query to the database. you cannot create it as an outer join if you are using Sybase. this error occurs when you try to attach additional active links to a button that already has an active link associated with it. You must provide an array for server to return request existence information. The Sybase database supports outer joins for joins of two tables only. Remove the default property setting from the view that contains the setting before giving it to another view. One of the properties of a view is whether the view is the default view for the form. 282 Error 283 Error 284 Error 285 Error AR System server does not support the specified dataType. They can. A field referenced in the qualification is not a data field. be included in workflow qualifications. Only one view per form can have this property set to True. Correct your text string to 255 characters or less. A form can have only one default view and there is another view defined as the default for this form. An RPC procedure mapping error between the client and the server occurred. Message text is empty or too long. Therefore. Display-only fields cannot be referred to in database searches. Status field must be created before status history field can be created. 286 Error 287 Error 288 Error 289 Error 291 Error 292 Error Invalid item list for entry existence. active link. The text you can specify for a filter. If you join more than two tables. a button can have only one active link associated with it. The expanded message can contain as many as 4096 characters. An attempt was made to set this property for the view. A newer version of an AR System client attempted an operation on an older version AR System Server that is unavailable on the older version AR System Server. Character strings must be terminated by a 0 character. A qualification being used to search the database contains a reference to a display-only field. the database supports only inner joins. When you create a status history field in a schema or a join schema. Because trim and control fields do not have associated data. they cannot be used in qualifications. or escalation is limited to 255 characters before expansion. The text you specified is over that limit. if you create a join that includes a join form. get. a status field must already be available. Direct the request to an AR System server with a version of AR System that supports the operation. The requested operation is not supported on the server. Escalation does not have an action defined. however. The field is included in the message. or set this field on this version of the AR System server because it is not supported. In these older versions. An escalation must define at least one action. A qualification contains a reference to a nondata field included in the message. You cannot create. The action field for an escalation is either NULL or empty. because the database contains no data for them.

this error message is returned. this error is returned. Determine why the write failed.000 filter limit per operation. Invalid support file type. with that action launching another filter with a push fields action. a filter that includes a push fields action. Administrator released license too recently. For example. File pointer is NULL or not a valid file pointer. this error occurs when too many processes are running or when some processes have grown to occupy most or all available memory on the server.00 293 Error Expected column data missing from multiple entries. Entry does not exist in database. An administrator can release a user’s license only once every two hours. If the internal column index is greater than the array size. This limit exists to protect against recursive filter actions. The specified Request ID is invalid. See the Workflow Objects Guide for more information about filters and push fields actions.h for a list of the recognized file types. This error might be caused by a push fields operation that runs recursive filters. 48 Error Messages Guide . If there are more than 100 requests specified in the entryId list parameter of the GetMultipleEntries( ) call. In the same situation. Requested number of multiple entries exceeds maximum allowed. No entry exists in the database with the Request ID you specified. There is a limit of 25 levels for filter processing. The file pointer specified for an API call is NULL or is not a pointer to an open file. The file type specified for a support file in a compound form is not recognized. There is a software bug in field value list processing in a GetMultipleEntries( ) call. This error occurs when more than 10.BMC Remedy Action Request System 7. There is a 10. In general. See the Workflow Objects Guide for more information about filter actions and push fields. and correct the problem before retrying the command. This is an internal error. similar 294 Error 295 Error 296 Error 297 Error 298 Error 299 Error 300 Error 301 Error 302 Error messages are returned by BMC Remedy User (see message 1200) and web clients (see message 9296). or the entry was deleted by another user during the time you were processing it. As an input parameter to call GetMultipleEntries( ).000 filters are run from a single operation.5. Each GetMultipleEntries( ) call can only return a maximum of 100 requests. The parameter must be a valid file pointer. the caller needs to provide a two-dimension array to hold the request value. An accompanying message from the operating system provides details. with that action launching another filter with a push fields action. The failure occurred on the server during processing of a call from the client. Note: This message is returned by web services and API programs. The administrator released this user’s license too recently. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. View the #define statements in the include file ar. Malloc failed on server. An error occurred while writing to the indicated file. Too many levels in filter processing. Too many filters processed during this operation. The system encountered an error during a call to allocate space. Error while writing to a file. and so on.

you must log in as a user who has administrative permission to the form you want to update. If you do not apply your changes. Entry has been modified since the get time. You can override this error and apply the changes. filters. Perform one of the following actions: Supply a value for this field. The value must be changed to be within the limits. 306 Error Value does not fall within the limits specified for the field.AR System error messages 303 Error 304 Error Form does not exist on server. 307 Error Required field (without a default) not specified. Either the specified name is incorrect. you can increase the size of the field to eliminate this problem. The actual limit and which field the limit is on are displayed with the error message. To perform this operation. to make this change successful. The field does not have a default value. and active links and the ability to delete existing requests from the database. in sequence. no value was supplied for the required field. These operations include the ability to restructure the database by adding forms. The next available ID will overflow the definition for the Request ID field. Change the definition of the field to specify a default value (used when the user does not supply the value) or change the field to be optional so that a value is not required. Verify the value specified against the limits defined for this field. all changes you make take precedence over the changes made by the previous user. so a value must be supplied during the submit operation. you can change the default value to a shorter string. Do not try this task yourself because numerous actions must be performed. 305 Error Next available ID produces a request ID that overflows Request ID field—contact the administrator. contact Customer Support to help you reset the next request ID counter. If you specified a length for the Request ID field that is less than the maximum allowed (AR_MAX_ENTRYID_SIZE). A field was specified twice in the field or value list. and reissue the command. or the limits must be redefined to allow the value specified. During submission of an request. Some operations in the system are restricted to users with Administrative access. or a maximum length or pattern if the field is a character field. The changes made might impact your changes. These limits might be a low and high range limit if the field is an integer or real field. Limits are specified for the indicated field. or the form is on another server. Remove the duplicate definition from the list. the previous user’s changes are retained. As a final option. The entry you are trying to modify was modified by another user after the last time you retrieved the definition. If the field is already at the maximum and a default value exists. If you apply the changes (and override the error). Each field can be assigned only a single value and can be specified only a single time in the field or value list. 309 Error Chapter 2 Action Request System error messages 49 . The server has no form with the specified name. Must have administrator permissions to perform this operation. AR System automatically generates IDs for requests in the system. 308 Error Duplicate field in the definition.

or remove the reference to this group and reissue the request.BMC Remedy Action Request System 7. By default. During processing. You are trying to delete a form or field that contains data. Then repeat the operation. Determine what groups are available. If the group ID was changed. Verify that this directory is present and writable by the user running the arserverd program. Change to the correct form or server. You attempted an operation against the wrong form or server. or remove the Field Name from the Field Sort Order list to complete the operation. The directory can be a link to another directory as long as the appropriate user can write to it. Field does not exist on current form. The data types of the fields used in an arithmetic operation are not consistent with the operations allowed for that operation. You must explicitly override this error for the operation to succeed.00 310 Error Value has wrong data type for the field. an error occurred while the server tried to use a temporary file. 50 Error Messages Guide . temporary files used by the server are created in the directory /usr/tmp (UNIX) or \tmp (Windows). Otherwise. Change the value specified to be compatible with the data type of the field to which the value is being assigned. use the ID of another group. the system deletes structures only when no data is lost. or the structure of the form was changed to eliminate the field ID from the form. A form with the same name already exists on this server. Form names must be unique. The group ID specified is incorrect. 313 Error 314 Error 315 Error 316 Error Must override form or field (where entries or data still exist) to delete. Failure with a temporary file. Data types are not appropriate for relational operation. An associated error message contains details. You attempted an operation against the wrong form or server. Review the Form and Application Objects Guide for information about the allowed data types of operations. Review the reason for failure. Also verify that the temporary directory was redirected and that the specified directory exists and is writable by the user running the arserverd program. simply change the ID. or the structure of the form was changed to eliminate the field ID from the form. or remove the ID from the field list to complete the operation. and reissue the request. The field is not related to the current form. The value of a field must be the same or compatible data type. 317 Error 318 Error Duplicate form name. 311 Error Field ID is not related to this form. Choose a different name. Change to the correct form or server. See the Form and Application Objects Guide for information about the allowed data types of operations. Group does not exist on server. By default. or the group with this ID was changed or deleted from the system. The value for a field in the field or value list is incompatible with the data type defined for that field. or rename the existing form. The field ID references a field that is not defined for the current form. The data types of the fields used in a relational operation are not consistent with the operations allowed for that operation. No group with the indicated ID exists on this server. 312 Error Data types are not appropriate for arithmetic operation. and correct the problem.5.

depending on the permission settings. See the Form and Application Objects Guide for information about the use and limits of the core fields. You must have write access to write to that field. or rename the existing filter. so you cannot change the field on this particular entry. The problem can be with the password or with the authentication string (for NT authentication. You have write access to this field for requests assigned to you (or to a group you are a member of) or submitted by you. The field you are changing has restrictions on its length. On this entry. The operation you are performing requests a length change to one of the core fields. A character menu definition was found in which the definition of menu items and children do not form a consistent tree structure. Character menu does not exist on server. Filter does not exist on server. Change to the correct server (if the former). or specify an existing character menu (if the latter). Assign a legal value for the field. Statistical operations can only be performed on integer and real fields or with arithmetic operations that result in real or integer fields (for example. The character menu is not defined on the current server. 327 Error 329 Error 330 Error 331 Error Chapter 2 Action Request System error messages 51 . or change the structure definition for the field so that it is no longer required. You attempted an operation against the wrong server. Enter the password defined for this user name to access the system as that user. You do not have write access to field. The name you are specifying for this filter is already in use by a filter on this server. or no filter is defined by that name. 325 Error 326 Error Duplicate filter name. You do not have write (change) access to a field that you are trying to change. Choose a different name for the filter. Cannot perform statistic operation on the data type of the target. The filter is not defined on the current server. You are trying to set a required field to a NULL value ($NULL$). or specify an existing filter (if the latter). You specified a menu that contains more than 15 levels at some point in its hierarchy. Invalid hierarchy in character menu definition. the authentication string is the NT domain) or with both. Change to the correct server (if the former). Some children item definitions have no parent item. You do not have write access for this entry to this field. Invalid password or authentication string for an existing user The password you specified for the user name is not recognized. You attempted an operation against the wrong server. Menus can contain a maximum of 15 levels.AR System error messages 319 Error Request for length change of core or reserved field is out of limits. You do not have write (change) access to a field that you are trying to change on this entry (request). Required field cannot be reset to a NULL value. The operation you attempted is incompatible with these limitations. the difference between two times). you are not serving in the role that allows you change access to the field. 320 Error 321 Error 322 Error 323 Error Too many levels in character menu definition. leave the previous value in the field. or no character menu is defined by that name.

The data contents of a reserved field do not meet the rules for the data in that field.BMC Remedy Action Request System 7. Cannot assign a user to the special Submitter (3).00 332 Error You do not have write access (at create time) to field. Assignee Group (ID 7) and Dynamic (IDs 60000 to 60999) groups define perinstance access rights.bmc. You did not specify to create a new ID in case of conflict. An AR System reserved field definition is incorrect. You do not have write access to this field at create time. Membership in a computed group is determined by the contents of the Computed Group Definition field on the Group form. You specified one of these fields with settings that are incompatible with the limits set on the definition of those fields by AR System. Assignee Group (7). Assignee (4). or Computed groups. and is configured for each client to access a maximum of one server. specify the option to create new IDs. Format for an AR System reserved field is invalid.5. you are not serving in any role yet. You are merging requests into a form from another source. 333 Error 334 Error 335 Error 336 Error 337 Error You have reached the maximum number of database entries permitted with this version of the Action Request System. The Submitter (ID 3). an authorized reseller. therefore. You cannot assign a user to any of these groups using the User form.com. contact your AR System sales representative or visit http://www. or visit http://www. and the create mode of the field is protected. To merge the new request. Because this request does not exist yet. 338 Error Duplicate request ID for merged item. You have access to this field on requests assigned to you (or a group you are a member of) or submitted by you. To obtain a version of BMC Remedy AR System without these limitations. To purchase the unrestricted version. This indicates that you do not have general write access to the field. but Create New ID was not specified. Dynamic. You are the Submitter if your login name appears in the Submitter field. contact your BMC sales representative. You have no access to field. includes a maximum of three fixed licenses. You do not have access (read or write) to the field that you are trying to access.com. depending on the permission settings. so you cannot set the field for this instance during a submit operation. This version of BMC Remedy AR System has a maximum limit of 2000 requests per database table.bmc. or delete the existing request before merging the new one. See the discussion of the AR System core and reserved fields in the Form and Application Objects Guide. Several reserved field definitions are reserved for AR System. the merge operation failed. Assignee (ID 4). See the discussion of the AR System core and reserved fields in the Form and Application Objects Guide for details on the allowed data format. You must have access to a field to read or change its values. and you are the Assignee if your login name appears in the Assigned To field. 52 Error Messages Guide . You become eligible for the extra access permissions allowed to these groups if you are the Submitter or Assignee or are a member of the Assignee Group or Dynamic group for the request being displayed. You specified a request ID in the merge operation that conflicts with an existing ID in the system.

Group type or category conflict between two groups with the same group ID. or change the type and category of the new or existing group to be of the same type and category. Active link does not exist on server. An associated error message describes why the ar file—/etc/ar (UNIX) or ARConfigDir\ar (Windows)—could not be opened. You attempted an operation against the wrong server. Permissions defined for the active link do not allow you to get the definition of or execute the actions for the requested active link. 341 Error 342 Error Cannot find or open the directory file. The active link is not defined on the current server. Two groups were defined with the same group ID but with different access characteristics. An error occurred when loading a filter definition from the database. Determine why the process did not run. Separators are defined in the include file arstruct. A diary field is a formatted character string consisting of a set of user name. correct the circumstances. The process was a filter or escalation Set Fields process action. time stamp. If there are two groups with the same ID. Separators are defined in the include file arstruct. Change to the correct server (if the former). and. Error in definition for a filter. Cannot run the requested process. 343 Error 344 Error 345 Error 346 Error Duplicate active link name. An internal error occurred. A Status History field is a formatted character string consisting of a set of user name and time stamp pairs organized (in order) by the various states that status can contain and separated by valid separator characters. Try importing without the change diary. or rename the existing active link. You have no access to active link. Choose a different name for the active link. 340 Error Incorrect format for the Status History field. This file contains the name of each AR System server that this client tries to connect to. both definitions must specify the same group type and group category. if possible. and the format of the status history value does not match the format expected. If you receive this error during an import action. Two or more groups with the same ID are actually a single group definition with two names.AR System error messages 339 Error Incorrect format for a diary field. All groups are keyed by the group ID.h.h. the process did not run. 347 Error Chapter 2 Action Request System error messages 53 . Could not run a process as requested. An associated error message might contain more details. it is probably caused by a corrupt change diary. Then retry the operation. and the format of the diary data does not match the expected format. To correct the problem. and character string triplets separated by valid separator characters. The AR System directory file could not be opened. You are not allowed to access the specified active link. Contact your AR System administrator if you need access to the active link. or specify an existing active link (if the latter). or no active link is defined by that name. The name you are specifying for this active link is already in use by an active link defined on this server. change the group ID for the group being added to be unique. In either case. You can do this by removing the lines beginning with change-diary from the export file. The file must be present to identify which servers to use. or manual changes were made to the contents of the database. You specified a diary field in the merge operation. You specified the Status History field in the merge operation.

5. Contact your AR System administrator if you need access to the form. Re-establish the group structure for successful use of the database. and the socket in use for this client is not the default socket of 390600. Reference to the Submitter or Assignee group exists in the referenced Submitter or Assigned To field. At startup. Only users with administrator permission can access (for read or change) a filter definition.00 348 Error Group cache structure is empty—no access to database is possible. 355 Error 356 Error 357 Error 358 Error 359 Error 54 Error Messages Guide . there was an attempt to notify the submitter or assignee of the request. Cannot delete a core field.BMC Remedy Action Request System 7. You can use multilevel menus to split large menus into multiple smaller and more manageable menus. However. The name you are specifying for this character menu is already in use by a character menu defined on this server. Cannot specify qualification on password field. you cannot specify a qualification on the password field. Must be administrator to access the filter. If you do not want to use the core field. Notification canceled to prevent a potential infinite loop. and Delete operations to structures are supported only on RPC socket 390600. You specified one of the core fields in a delete operation. 11. An associated error message contains details. You are not allowed to access the specified form. the group cache for the database contains no group definitions. Choose a different name for the character menu. 349 Error 350 Error 351 Error 352 Error 353 Error You have no access to form. All structural changes must be made using the server connected to the default socket. Notification to special Submitter or Assignee group specified. To maintain security. The character menu definition contains too many items on one level of the menu tree. AR System allows a maximum of 99 items on any one menu level. only AR System administrators can access the system. you can ignore it by defining it as a hidden field. The server is running in a multiple-socket mode. After you fix the problem. Create. To prevent an infinite loop. reconfigure the notification targets in your system to eliminate this condition. and 14) can be deleted from your form. Duplicate character menu name. the field holding this information contains a reference to the Submitter or Assignee group. Error while accessing a menu file on the server. 13. or restart this tool with the RPC socket definition reset to the default value of 390600. Use routines connected to the default socket. The obsoleted core fields (IDs 9. the menu is available. the system detected a divide by 0. the system is canceling the notification. Attempt to divide by zero (0) in arithmetic operation. or rename the existing character menu. If you are receiving this error. During an arithmetic operation. The current user does not have administrator permission. Restructure your queries to avoid this illegal operation. An error occurred while the system tried to access a menu definition file on the server. 10. Character menu contains too many items on one level (maximum 99). Set. Form permissions do not allow you to get the definition of the form or of its fields or to access the data it contains. This error usually occurs due to someone deleting data from the database. 12. The password field is a write-only field. Core fields cannot be deleted. Without group definitions. During a filter or escalation action.

No form ID was found in the file form. restore the file from a backup before the manual change. Error in definition for an escalation. a value specifying the keyword $DEFAULT$ was supplied for the required field. or manual changes were made to the contents of the database.ar file or by a file from a previous release of AR System. Must be administrator to access the escalation. the value of the Submitter field cannot be changed after submission (even by the administrator). The system can be configured with a Submitter Mode of Locked or Changeable. The escalation is not defined on the current server. Specify some qualifying criteria in one or more fields to limit the amount of data being returned from the server. Accordingly. The name you are specifying for this escalation is already in use by an escalation on this server. This server is configured not to allow unqualified searches. In this mode. Change the definition of the field to specify a default value or change the field to be optional so that a value is no longer required. If the former. or rename the existing escalation. No form ID for the form. You attempted an operation against the wrong server. You configured the system with a value of Locked. 371 Error Chapter 2 Action Request System error messages 55 . 364 Error Diary field cannot be set to a NULL value in a filter or escalation. You cannot change the value of the Submitter field—the Submitter Mode of the system is configured to be locked. Perform one of the following actions: Supply a value for this field. Only users with administrator permission may access (for read or change) an escalation definition. and the conversion ratio does not exist in the AR System Currency form. An error occurred when loading an escalation definition from the database. The filter definition contains a Set Fields action where a diary field was assigned a value of $NULL$. restore a file from the correct version or. if you have not run the upgrade program after installing the new version. The field does not have a default value specified so you cannot use the $DEFAULT$ keyword during the submit operation.AR System error messages 360 Error No currency conversion ratio exists for the requested conversion. This is usually caused by a manual edit to the form. An internal error occurred. Specify an alternate value. or specify an existing escalation (if the latter). run the upgrade program to bring the file up to date. 361 Error 363 Error Required field assigned $DEFAULT$. it cannot be assigned a NULL value. An unqualified search was issued. During submission of a new request. Supply conversion ratios in the AR System Currency form for all possible conversions. Change to the correct server (if the former).ar. and the server has been configured to disallow unqualified searches. and you issued an unqualified search. but there is no default value for the field. The current user does not have access to the escalation. Specify some search criteria to perform a search on this form. A currency conversion between two different currency types was needed during the execution of workflow. Choose a different name for the escalation. or no escalation is defined by that name. If the latter. Escalation does not exist on server. A diary field is append-only. or remove the assignment of NULL for the diary field. 366 Error 367 Error 368 Error 369 Error 370 Error Duplicate escalation name.

and retry the operation. One of these conditions exists: You attempted an operation against the wrong server. Perform the update on the current master copy of the entry. No distributed mapping with the specified name could be found. The distributed forms are part of the system structure and must not be deleted or modified. All but one form must be removed. A distributed or application operation activated by a filter action includes one or more arguments with single (‘) or double quotation marks (“). you can update only one entry (marked as the current master) in a chain. Somewhere in the command line. Change to the correct server. 373 Error 374 Error Must be administrator to access the distributed mapping. a pair of forms is automatically created by the server. select the forms for deletion. an error occurred. and use the correct command line syntax. Problem encountered during creation of one of the distributed forms.00 372 Error Could not create alert event. More than one form with the reserved alert events fields was found. An associated error message contains details. Retry the operation. Specify an existing distributed mapping. The command line arguments cannot be processed. To delete one or both of these forms in BMC Remedy Developer Studio. In a distributed environment. and retry the operation. You tried to update a copy other than the master. 379 Error 56 Error Messages Guide . The specified distributed mapping does not exist on the current server.BMC Remedy Action Request System 7. a mismatch in the number of quotation marks exists (the number of open and closed single or double quotation marks is not even). The distributed or application operation is not performed. Only users with administrator privileges can read or change a distributed mapping definition. Choose a different name for the mapping. The distributed or application operation specified in the filter Run Process action contains mismatched quotation marks. You cannot assign the same name to more than one distributed mapping.5. The command line in which the mismatch exists is displayed and includes an error message. Fix the problem. During the creation of these forms. The server could not create an alert event request in the database. 377 Error 378 Error Must be Distributed Server to perform this operation. The current user tried to access a distributed mapping and does not have administrator privileges. An associated error message contains details. You must be the user (process) Distributed Server to run the specified delete operation against the Distributed Server Pending and Distributed Server Mapping forms. The request was not added to the database. or rename the mapping with which the conflict exists. Cannot update this entry—this distributed entry is not the master copy. Distributed mapping does not exist on server. and ignore the system warning related to the forms. When a system is licensed for the Distributed Server Option. The following are possible causes: The server could not find an Alert Events form. 375 Error 376 Error Duplicate distributed mapping name. and restart the arserverd process (or send a SIGHUP signal) to re-create the forms.

AR System error messages 380 Error No item matches filter conditions—this operation has been defined so that no match generates an error. or from another table in the database. and found no rows that matched the qualification criteria. Change to the correct form or server or use a VUI ID that is associated with the form to complete the operation. this operation is not allowed using BMC Remedy User. You attempted an operation against the wrong form or server. File menu contains too many items on one level (maximum 1000). Only printable characters are allowed. The name contains a control character. an option controls whether a field used in the join qualification can be updated. If you specify two sets of changes or specify to delete the same object several times. consider breaking it into smaller pieces and connecting the appropriate menu with the subset you are interested in. The VUI is not related to the specified form. or from another table in the database. The administrator defined one or more unique indexes on this form. If you need a large menu. To maintain data integrity of the record in the join form. The same ID was specified several times in a “multiple” structure operation API call—each ID specified for this call must be unique. confusion about the desired operation can arise. A “nested filter exception” error is returned because a filter exception condition is already being thrown. Updating this entry will violate join condition. The administrator configured the action to return an error if multiple matches were found. and found multiple rows that matched the qualification criteria. The administrator configured the action to return an error if no matches were found. A filter action was extracting data from another form. Multiple API calls—those enabling you to perform a set of operations in a single call—do not support specifying the same ID several times in the same call. 383 Error 384 Error 385 Error 386 Error 387 Error Exception occurred while handling previous exception. 381 Error Multiple entries match filter conditions—this operation has been defined so that multiple matches generate an error. 388 Error VUI does not exist for the specified form. To override this error using the AR System C API. A filter action tried to extract data from another form. Object names can contain only printable characters. or the structure of the form was changed to eliminate the VUI ID from the form. specify the set option of AR_JOIN_SETOPTION_NONE. Chapter 2 Action Request System error messages 57 . When updating an entry in a join form. Change the name to remove the control characters. 382 Error The values for this entry violate a unique index that has been defined for this form. See the C API Reference. Large menus are unwieldy and can hurt performance. Reissue the operation without specifying the same ID multiple times. A setting of AR_JOIN_SETOPTION_REF enforces the referential integrity and causes the update to be rejected. Review the values for the entry to make sure that values that must be unique are unique. The values on the entry you are submitting or modifying duplicate the field (or fields) defined in the unique index. The name specified contains an invalid character. A maximum size restriction of 1000 menu items is placed on the size of file style menus when accessing the system from a Windows client.

Ask the administrator if the filter process time-out must be raised (up to 20 seconds) or if another change is needed so that the process returns a result in a timely manner. for example. An active link specified that a process is to be run on the server to return a value to be assigned to a field. Status History field cannot be used as labelField or valueField in the query menu. Creation of VUI failed.5. Reserved field Group List has too many characters. If you manually changed a file. You attempted an operation against the wrong object or server. Repair or replace the active link definition. Error in definition for an active link. consult your AR System administrator. Change the definition to be 255 bytes or less. The system has timed out while waiting for a process that is running on the server to return a value. The error is usually caused by a manual change to one or more AR System database definition files. The support file is not related to the specified object. The system requires that the name for all fields and VUIs on a form be unique. 395 Error 396 Error Support file does not exist for the specified object.BMC Remedy Action Request System 7. The file that was expected to hold the definition of a form does not hold a form definition or is incorrectly formatted. You are trying to delete the only VUI for the form. The definition being saved or imported has an unlimited length. The VUI is already associated with the form. If you cannot wait to try your operation. and this is not allowed. Both the VUI name and the VUI ID are unique values. or the structure of the form was changed to eliminate the indicated support file ID from the object. Unable to allocate memory for cache. The file specified for a form does not hold a form definition. the change is invalid. this is an unexpected error. Neither the Status History field nor any part of the Status History field can be used in a query style character menu. If the server is unable to allocate memory from the shared cache. 390 Error 391 Error 392 Error 393 Error 394 Error Cannot delete final VUI for a form—all forms require at least one VUI. You supplied a name already used by another field or VUI. AR System server was temporarily locked for use by users without administrator permissions. Field or VUI name must be unique for the form—there is already a field or VUI using this name. 397 Error 398 Error 399 Error 400 Error 58 Error Messages Guide . To create a new VUI.00 389 Error Duplicate VUI for the form. Every form must have at least one VUI defined. A new VUI for the form could not be created. The server timed out waiting for the process to return the requested value. specify a unique name and ID—or leave the name blank and the ID set to 0 to have the system create a name and ID for you. and retry the operation. Change to the correct object or server or use a support file ID associated with the object to complete the operation. The Group List field (field 104) is a reserved field with a restriction that the field cannot be more than 255 bytes in length. If you did not changed a file. Change the name of this item. An associated error message contains details. and the server terminates. The AR System server detected an active link definition integrity issue. because updates are being performed. this message appears. One or the other is already in use for this form. The administrator has set access for administrator users only. Please retry your operation later. must not contain more than 255 characters.

the change is invalid. the change is invalid. One of the core fields is missing from the form file definition. This error is usually caused by a manual change to the definition. If you manually changed a file. the change is invalid. The form definition contains a duplicate definition for one or more fields. Remove the definition file of all lines that are not part of a legal definition. The form definition file field count does not match number of fields in the file. The import file contains data that is not part of a legal structure definition supported by AR System. A format error was detected in a definition file. The number of fields defined for the form does not match the count in the form header definition. This error is usually caused by a manual change to one or more of AR System database definition files. If the file was deleted. A definition was found without that selection definition. The file contains a form definition. but it is not the expected form definition. You may or may not use them. Incorrect format in the definition file. the change is invalid. this is an unexpected error. therefore. This error is usually caused by a manual change to the form definition file. A file specified as holding the definition of a filter does not contain a filter definition. These fields must be present as part of the definition of the form. A field or VUI ID must be unique within a form. If the definition file was changed. the change is invalid. The ID is. If the file was deleted. and then retry the import operation. the change is invalid. This error is usually caused by a manual change to the form definition file. Duplicate field or VUI ID in the definition. The definition of one of the core fields is inconsistent with the rules defined for that core field. The error is usually caused by a manual change to one or more AR System database definition files. 402 Error 403 Error 404 Error 405 Error 406 Error 407 Error 408 Error 409 Error 410 Error 412 Error Chapter 2 Action Request System error messages 59 . an illegal ID and cannot be used. No definition is in the file. If you manually changed a file. If you did not changed a file.AR System error messages 401 Error Form definition in the source file is not the expected definition. A core definition from the definition file is incorrect. it must be restored from a backup. This error is usually caused by a manual deletion of the contents of a structure file. The import file is in an incorrect format. but they must be present. Field ID is in the core field range but is not recognized. This error is usually caused by a manual deletion of the contents of a structure file. If you manually changed a file. If the definition file was changed. it must be restored from a backup. This error is usually caused by a manual change to the form definition file. A field ID in the core range was found. the change is invalid. The structure file does not contain definitions. All fields with a Selection data type must define a list of one or more values that define the selection for that field. Selection data type requires a limit specification. The file specified for a filter does not hold a filter definition. The form definition being loaded is missing one or more of the required core fields. If the definition was changed. This error is usually caused by a manual change to one or more AR System database definition files. but this is not one of the defined core fields. The error message contains the error. If the definition file was changed.

one or more key pieces of information (such as the type of join or the primary or secondary form) are missing. all data fields must be defined with a field type indicating that they are a join field. The view form definition is dependent upon complete information about the view. Assignee Group [field ID 112]. an error occurred. 414 Error 415 Error 416 Error 417 Error 418 Error 419 Error 420 Error 421 Error 422 Error 423 Error 60 Error Messages Guide . but it is not the expected definition. A file specified as holding the definition of a distributed mapping does not contain the definition. However. The file specified for an escalation does not hold an escalation definition. The type of the action attached to the escalation is outside the allowed range of types. The system was translating the contents of a group (for example. because there are no base data fields when you are working with a join form. The join form definition is dependent upon complete information about the join.5. if the form is a join form. Cannot translate the group name in either the Group List or Assign Group field. A file specified as holding the definition of an active link does not contain the definition. During the conversion. Incomplete field mapping definition. For example. The likely cause of the failure is that the system encounters a name that is not a defined group. If the file was deleted. With a join or view form. a form defined itself as a join form. from the Group List [field ID 104]. A file specified as holding the definition of an escalation does not contain the definition. This error is usually caused by a manual deletion of the contents of a structure file.BMC Remedy Action Request System 7. If the file was deleted. a form defined itself as a view form. However. Unrecognized escalation action type. The field mapping of this join or view form is not consistent with the type of the form. so it cannot be created. it must be restored from a backup. it must be restored from a backup. This error is usually caused by a manual deletion of the contents of a structure file. This error is usually caused by a manual deletion of the contents of a structure file. The operation was occurring during the processing of a filter or escalation. Make sure that you did not changed the name of the file prior to import. During import. Incomplete join form definition. The file specified for a character menu does not hold a character menu definition. it must be restored from a backup. The file specified for a container does not hold a container definition. or a dynamic field) from a text string into the internal format of a sequence of IDs. it must be restored from a backup. one or more key pieces of information (such as the table being referenced) are missing. the field type specified in the field definition for a data field is not appropriate for that form type. During import. This error is usually caused by a manual deletion of the contents of a structure file. The file specified for a distributed mapping does not hold a distributed mapping definition. so it cannot be created. Invalid field type. The file contains a container definition. If the file was deleted. If the file was deleted. A file specified as holding the definition of a character menu does not contain the definition.00 413 Error The file specified for an active link does not hold an active link definition. Incomplete view form definition.

Supply a value for the input argument to the AR System API. The definition file is invalid. such as a currency field. The value supplied for the field identifier exceeds the maximum allowed value. Not a lock block definition. The input value for this server setting is invalid. Verify the validity of the export definition file and re-export it if necessary. Fields of this type cannot be included in multi-column indexes. An invalid or a corrupt lock block definition was skipped. Do not index the field. out of range. The file specified for the form data does not hold the form data definition. or remove some functional currencies from the field definition. Re-try the call with a proper index value. Administrative operations must be enabled before you can modify this server setting. Field ID is too large. Invalid array index. The import file does not hold a form definition. 433 Error 434 Error 435 Error 436 Error 437 Error 438 Error Invalid format for server information setting. A currency field selected for indexing has too many functional currencies to index each column without exceeding the index limit of 16. This message indicates that an error occurred during the post-cache upgrade. A multi-column index was specified that includes a field type that is not allowed. A portion of the definition file was skipped because it is invalid or corrupted. Server information associated with this tag cannot be updated because Admin operations have been disabled. After the server cache has been loaded. Specify a value less than or equal to 2147483647. It is possibly corrupted. Reload Failure. In filters and escalations. Contact Customer Support. The required API input argument is a null value. Indicates that a SQL error occurred during a certain stage of the AR System server initialization. Changing the field option of the field is not allowed You tried to modify a field option. The import file does not hold a view definition. Verify that the input value for this server setting is the correct type and is properly formatted. and escalations. but this option cannot be modified. you cannot use a Push Fields action to push values to forms residing on different servers.AR System error messages 424 Error Filter and escalation Push Fields actions can only affect forms on the same server as the filter or escalation. filters. 441 Error 442 Error 446 Error Chapter 2 Action Request System error messages 61 . Verify the validity of the export definition file and re-export it if necessary. Administrative operations are disabled. 429 Error 430 Error 431 Error 432 Error The file specified for a VUI does not hold a VUI definition. The array index given to the AR System API is out of range for the specified array. patches can be provided to correct database problems. Remove any fields that are not allowed from the index specification Currency field has too many functional currencies to allow indexing. See the Form and Application Objects Guide for more information about Push Fields actions.

Invalid or pre 6. Specify 0 or 1 for the license import option. the system encountered an error. You tried to change the name of a form on an AR System server that was installed with an application that does not support changing the names of forms. Cannot open a report definition file. The operation continues without the report file. Contact Customer Support. Contact Customer Support. An error occurred in loading data from the license_cache table in the AR System database.0 AR Server license file.5. and update the active link definition to have the file included in the active link. You cannot change the name of a form on this AR System server. You tried to create a form on an AR System server that was installed with an application that does not support added forms. see the C API Reference. Locate the expected file. Fix the invalid value in the AR System Administration: Server Information form (recommended) or in the server configuration file. AR System on the server containing the application was updated to a different version.0. Cannot change the form mapping criteria in a Lite licensed AR Server. The licensed application is supported only on the version of AR System included with the application. and put it in the proper location. and then retry the operation. Cannot create a form in a Lite licensed AR Server.conf/ar. The AR System server configuration setting for the specified tag includes a value that is outside the range of valid values or that is NULL for a non-NULL configuration. Continue with any other files. the user receives a warning about the missing file. The AR Server version does not match the Lite license version. 462 Error 463 Error 464 Error 465 Error 466 Error 467 Error 468 Error 62 Error Messages Guide .BMC Remedy Action Request System 7. 450 Warning 451 Warning Failure during load of report definition file into server. For more information. You cannot change the join criteria of a join form or the properties of a join. The error message provides information about the valid values. You cannot add forms on this AR System server. You cannot add forms to this application. While trying to read a report file referenced in a macro definition embedded in the active link definition being created or modified. and the system tried to load configuration information for the application auditing but could not locate it in the configuration file. or from a version of AR System prior to 6. Install the AR System included with the licensed application. Continuing the operation without the file identified in the associated message. Invalid AR Server license import option. then. 460 Error 461 Error Missing audit information in the ar. A form was added to a licensed application that does not support added forms. View the associated messages. or view form on this AR System server. The license file is corrupted. Application auditing was enabled. Error reading license cache table. and the report file was not retrieved.cfg file. The active link is created or updated without the file. formatted incorrectly.00 447 Error Server information data associated with this tag has an invalid value. The form is not a member of a Lite licensed application. Do not edit the license file. reselect the macro in the action. When creating or updating an active link. vendor. If it is replayed. a macro action or else definition contains a reference to a report file that does not exist. The file is not saved as part of the definition. Cannot change the form name in a Lite licensed AR Server.

3 Unicode database is not yet ready for upgrade. Too many arguments specified for upgrade program.0 or later. If this utility has not been run. Upgrade your Oracle database to Oracle 8i or higher. After this data move is completed. If the AR System server is in a server group environment. You need not run this program. Requested database table not found. If this warning appears on a single server. The correct column information (for example. 480 Error 481 Error 482 Error 483 Note 485 Error Status History field is not supported on View forms. Restart AR System. Reserved ID OK parameter is NULL -. User Cache utilities are disabled.unicode63handled.must be a pointer to memory. you can ignore the warning. You cannot create a Status History field on a view form.0 Unicode database. Indicates that the file supplied during an ARImportLicense() API call does not contain valid licenses. This warning indicates that the entered key is not valid for the AR System server where it was entered. Please contact Customer Service for details on how to prepare your database before attempting an upgrade to a 7. Please delete this column manually. In this case. created for upgrading the 6. This parameter must be supplied with a pointer to an ARBooleanList.0 or later Unicode server. Make sure that the key field is set to a nonnull. The reservedIdOKList parameter in the ARCreateMultipleFields() API function was supplied as a null pointer.AR System error messages 469 Warning Warning. could not be deleted. The program that upgrades the database structure to the current structure requires more arguments than you specified. there is a problem with the license entry. When upgrading a previous installation to AR System 7.0 database. the installer creates temporary tables to allow it to move and transform data types. If the delete fails. The upgrade program is run automatically as part of the installation operation.3 Unicode database to a 7. Oracle® 8. this key is not valid for this server. Too few arguments specified for upgrade program.0 is no longer supported by upgrade. unique column to avoid data corruption. No licenses in file. the installer attempts to delete these columns. Please check the spelling (table name is case-sensitive). The program that upgrades the database structure to the current structure requires fewer arguments than you specified. This View Form contains Request IDs that are null. Chapter 2 Action Request System error messages 63 . and make sure that the correct Host ID was used when generating the key. 470 Error 474 Warning 475 Error 476 Error 477 Error 478 Error 479 Warning The temporary column control. the right number of columns) for the external schema was not retrieved. this error is generated by the installer. you must prepare the database by first running a utility that prepares the database for this upgrade. this error is generated. When upgrading an AR System 6.0. Please restart the AR System server for the changes to take effect. The program that updates the database structure to the current structure no longer supports Oracle 8. Supply the correct file name. The upgrade program is run automatically as part of the installation operation. You cannot search the database for the entry ID in a view form if its value is NULL. Check the fields of the key for leading or trailing spaces. You need not run this program. the key might be valid for one of the other servers in the group. This 6.3 Unicode server to an AR System 7. The arcache utility was run on an AR System server that is configured to disallow the arcache utility.

An error occurred while the system tried to open a connection to the SQL database. An error occurred during one of the individual field creations for an ARCreateMultipleFields() API call. you must update the requests in this file and then restart the arserverd process. is the directory of the database server or client installation on the UNIX computer where AR System is installed.conf file (UNIX) or the ar. The value for Dbhome-directory. The ar. If this error is returned. Check preference server settings and make any necessary corrections. If it is correct. applicable only to the UNIX setup. 64 Error Messages Guide . At least one error occurred during the operation of the ARSetMultipleFields() API call. out of range. the transaction is not committed. Verify the permissions on the file to make sure that the user running the arserverd process has read and write access.BMC Remedy Action Request System 7. If you moved your database or changed these parameters. Due to a workflow design error or an AR System internal error. Make sure that the directory setting is correct. This error supplies appended text containing the zero based list position of the field the error occurred on. Update ownership or permissions as needed. The server could not open the form data dictionary file (form.conf file (UNIX) or the ar. Invalid preference server option. the error occurred on the third field in the field list. Sybase-Server-Name or Oracle-SID). This parameter must be supplied with a pointer to an ARStatusListList. Field creation error occurred at the reported list position. look in that directory for the definition file. An accompanying error message provides details. the transaction was rolled back.cfg file (Windows) contains definitions for the environment variables to set for each database.5. The specific error is reported as an item in the status list. If the file is not present. To ensure database integrity.00 486 Error Item count in a list parameter does not match the item count in the Field ID list. All list parameters that are supplied must have the same number of elements. Make sure that these values are correct. Ensure that the SQL database is running. The setFieldStatusList parameter in the ARSetMultipleFields() API function was supplied as a null pointer.ar). For example. the setFieldStatusList parameter supplies the details of the individual field failures. An associated error message explains why the file was not opened. restore the file from a backup. Failure while trying to connect to the SQL database. Set field status list parameter is NULL -. A list parameter supplied in an ARCreateMultipleFields() or ARSetMultipleFields() API call does not have the same number of elements as the fieldIdList parameter. This file is in the database directory referenced by the Server-directory setting in the ar. 487 Error 488 Error 489 Error 490 Error 504 Error 524 Error 550 Error This operation caused an uncommitted database transaction that has been rolled back. At least one set field failed in a multi-field operation. Missing or invalid form definition file. The names of other needed settings begin with the name of the database (for example. or contact the database administrator for help.cfg file (Windows).must be a pointer to memory. if the appended text is 2.

this error can occur if AR System needs to contact an external database that is not accessible. If the error occurs when saving a form or other workflow object. engage database administration support to capture the full CREATE VIEW statement in the database logs and to provide information about database limitations. the database error is usually captured in the AR System SQL log. 552 Error Failure during SQL operation to the database.AR System error messages 551 Error Cannot initialize contact with SQL database. generate client-side ARAPILOGGING (when the error is generated from user interaction) and server API and SQL logging to identify the call that failed and the specific database error message. You might need to reduce the number of fields on the form. Also turn on client workflow logging as well as ARAPILOGGING. To troubleshoot the error in this case. Use the installer logs to identify the cause of the problem. when opening a view of an external table. This error usually indicates a failed installation or a permissions issue. Chapter 2 Action Request System error messages 65 . To help diagnose the cause of this error. for example. the database was not accessible. if the table does exist and contains a single valid record. When ARERR 551 occurs. During operation. In this case. Verify that the database is running and is accessible to the AR System server. In the case the resolution is to modify the workflow to reduce the size of the operation. The operation you attempted generates a SQL command that is too large for the database to process. The Control record for the data dictionary in the database is missing or contains no records. the reason for the error might be the size of the CREATE VIEW statement generated when the form is saved. An associated error message contains the full text of the error message from the database. If the error occurs during execution of workflow. the CREATE VIEW statement in the AR System SQL log might be truncated. Use the workflow logging to identify the SQL operation that causes the error. 553 Error Operation requested is too large for a single SQL command. including: During server start-up. To identify the database error. work with the database administrator to determine if there is a permissions problem with the database. However. and use the database error from the SQL log to work with the database administrator or database vendor to identify and resolve the database problem. 554 Error AR System structure error in the SQL database—missing control record. The database error will appear in the SQL log. This error can have several causes. This is a serious error. turn on SQL and Filter logging on the AR System server. A SQL database error occurred during an operation against the database. turn on filter logging and active link logging on the AR System server to identify the workflow involved. the installation might not have completed successfully. If the error occurred directly after an installation. This error could be caused by a direct SQL command in active link or filter workflow.

For more information. To troubleshoot this error. also capture the UNIX console output during startup when the error is generated. if the error occurs during server startup. if the error occurs during server startup. When the data is managed through AR System. On UNIX. gather and provide the following information and to BMC technical support: The arerror.5 and later. If you manually updated the data dictionary definitions. For more information. Data expected to be found in the database cannot be found. This is a serious error.log file. More data was found in the database than was expected. 556 Error Missing data in the SQL database.00 555 Error AR System structure error in the SQL database—missing enumerated value.log file. gather and provide the following information and to BMC technical support: The arerror. all data is updated appropriately to avoid extra definitions. you might have added data that conflicts with existing definitions.5 and later. For more information. if the error occurs during server startup. In release 7. In release 7. It can also be caused when there is corruption or inconsistency in the data dictionary definition of a form or other object. see the Optimizing and Troubleshooting Guide. On UNIX. The API log and the SQL log. These will help identify which forms or tables were involved. The API log and the SQL log. Manual updates at the database level are not supported and can result in errors during AR Server startup or caching of form and object definitions. To troubleshoot this error. use the database consistency checker (the -dbcheck server option) and capture the output to a log file. This error is most often generated when the AR System server starts up. One or more enumerated (selection) values are missing from the data dictionary in the database. To troubleshoot this error. also capture the UNIX console output during startup when the error is generated. all appropriate cross-references are maintained. This error is usually caused by inconsistent definitions in the data dictionary. use the database consistency checker (the -dbcheck server option) and capture the output to a log file. gather and provide the following information and to BMC technical support: The arerror. see the Optimizing and Troubleshooting Guide.5 and later. On UNIX. These will help identify which forms or tables were involved.log file.5. In release 7. or are corrupted. This is a serious error. This is a serious error. 557 Error Too much data in the SQL database (likely data corruption). This error can be caused by data missing in an associated table to a base data table. also capture the UNIX console output during startup when the error is generated. use the database consistency checker and capture the output to a log file. When the definitions are managed through AR System. you might have broken one of the required references. see the Optimizing and Troubleshooting Guide. 66 Error Messages Guide . If you manually updated data in the database.BMC Remedy Action Request System 7.

see the Optimizing and Troubleshooting Guide. The Help text or change diary entry for a structure is missing. If you are using the SQL option of the Set Fields operation.5 and later. or correct the assignment to include one of the returned values. undo the change you made to restore the database to a consistent state. If you are not using the SQL option of the Set Fields operation. active link. More than one action for a filter or active link contains the same internal sequencing number. 561 Error The underlying database does not support qualifications on diary fields and on character fields with a maximum length over 255 bytes. If the field is a character string. This is a serious error. edit the data to less than the maximum allowed. 559 Error Character string exceeds maximum size allowed. This number allows ordering of the actions in the proper sequence. If you manually changed the database. The SQL database engine being used does not support the modulo operator. and values are being retrieved from the database. use the database consistency checker and capture the output to a log file. and escalation qualifications. Each database vendor has its own limitations for field sizes. You cannot specify a search that includes a field on the right side of a LIKE operator. You cannot specify a qualification that includes a reference to these type fields. However. this is an internal error. A SQL command was issued. 560 Error Multiple actions have the same internal index (likely data corruption). if the error occurs during server startup. Index for value in SQL command is greater than the number of values returned. This is a serious error.log file.AR System error messages 558 Error Table entry defining form or field is missing. but you cannot use it to search for entries in the database. 563 Error The underlying database does not support the modulo operator. If you manually changed the database. correct the definition of the SQL command used as the qualification to include sufficient columns. You can use the modulo operator in filter. ask your database administrator. The SQL database engine being used does not support field references in a LIKE operation. 562 Error Table entry defining help text or change diary for a structure is missing. In release 7. also capture the UNIX console output during startup when the error is generated. undo the change you made to restore the database to a consistent state. One of the data dictionary entries defining a form or field is missing. you cannot add data to the field for this request. A request was made for a value from the command. The total length of a character or diary string exceeds the maximum size of a string allowed in the underlying database (500K characters for Oracle). The underlying database does not support field references within a like operation. the index of the column requested is greater than the number of columns that were requested. For more information. Even when no Help text or change diary exists. gather and provide the following information and to BMC technical support: The arerror. The SQL database engine being used does not allow qualification on diary fields or character fields with a maximum length over 255 bytes. To troubleshoot this error. a NULL entry is present in these tables. On UNIX. If you have questions. The SQL database engine being used stores Help text and change diary information in separate tables from the structure definition. Chapter 2 Action Request System error messages 67 564 Error 565 Error . If the field is a diary field.

The database was configured not to supply the number of records affected by a SQL statement. This message periodically appears while the system tries to connect to a SQL database that is not responding. Incorrect format in SQL command. If this error occurs. The system failed to retrieve the list of AR System servers. and a connection was established. It is preceded by message 590. on Microsoft SQL Server the No count connection option cannot be selected. Incorrect format in the SQL command. 567 Error 569 Error Failed to connect to database after multiple attempts. Configure the database to supply this information.BMC Remedy Action Request System 7. Cannot specify both -G and -U. This is an internal AR System server error that happens while creating a new SQL command from another one. This message follows either message 590 or 591. 569 Error 570 Error 590 Note 591 Note 592 Note 600 Error 601 Error 602 Error 603 Error 68 Error Messages Guide . Error while opening or reading from AR System directory file. This message is issued as a reminder that the system is not connected. The number of database records affected by a SQL statement was not available from the database. SQL database is now available. The operation for which this message was received was canceled. continue by reissuing the command. The SQL database is unavailable. -g. you should not receive this error message.5. the -g. but that it is continuing to retry the connection.00 566 Error Deadlock during SQL operation to the database. and contact Customer Support. A deadlock condition was detected in the database. For example. One of the two options must be specified. You must break the operation into two commands. check the SQL and API logs to help debug the issue. Record the operation you were performing (and the message received). Specify which user or group form to use to reload the cache. Because the deadlock condition should be trapped and the command automatically retried by the server. and cannot specify either more than once. If you receive this message. The command line has both a -G and -U option (or either one) specified two or more times. If you start the tool from the command line and you use the command line option -s to specify an update to a single server. The specified command line argument is not a recognized argument for this program. Verify the definition of the program for information about the valid command line arguments. Either the -u. or both options must be specified for the arreload program. SQL database is not available—will retry connection. The process periodically retries the connection until a connection is obtained or it encounters a fatal error. Unrecognized command line option. Must specify the options -u. or both. The program does not execute with invalid arguments specified. The previously unavailable SQL database is now available. This list is retrieved only when you specify an update to all servers. and they cannot both be specified in the same command. SQL database is still not available—continuing to attempt connection. this error cannot occur because no server list is accessed. The system tried to establish a connection with the database and received errors after multiple attempts.

611 Error 612 Error 613 Error Computed group qualifier includes dynamic group. Although the system was configured to allow guest users. or 2 (floating). Group IDs in the range from 60000 to 60999 must be used only for groups in the dynamic group category. The server could not open the access control server cache file (server. The value specified is not one of these values. A command line argument is not appropriate for the operation being performed. An option required for the operation is missing. Specified user is not registered with this AR System server. The value for the group type option must be an integer code 1 for a view group and 2 for a change group. This file is in the database directory referenced by the Server-directory setting in the ar. and specify an appropriate value. If the file is not present.ar). 1 (fixed). or a group ID in the dynamic group range was specified for a regular group. 614 Error 615 Error 616 Error 617 Error Chapter 2 Action Request System error messages 69 . Make sure that the directory setting is correct. The computed group definition contains a circular reference. restore the file from a backup. Computed group includes circular reference. A required option for the specified operation is missing. Update ownership or permissions as needed.cfg file (Windows). 2 = floating license). No such user exists. Unrecognized group type—must be 1 (view) or 2 (change).ar). You must connect with a valid user with administrator access. Dynamic groups are not permitted in the definition of a computed group. Verify the permissions on the file to make sure that the user running the arserverd process has read and write access. Unrecognized license type—must be 0 (none). Indicate whether you are adding or deleting a group or user entry. Specify whether the system is adding or deleting the entry specified. The specified option expects a value but none was specified. The user specified as the administrator user to allow you to perform this command is not a recognized user in the system. and specify an appropriate value.AR System error messages 604 Error 605 Error 607 Error 608 Error 609 Error 610 Error Must specify the operation to be performed (-G or -U). The value for the license type option must be an integer code (0 = no license. The user trying to log in is not a registered user. Supply all required options. look in that directory for the file. If it is correct. Re-enter the command. Review the documentation for the command for details about the options required with each operation. An associated error message explains why the file was not opened. the user is not allowed to log in as a guest user because the user name differs from a registered user. The specified value is not one of the legal tags (a or d) for the -U or -G option. Review the documentation of the command for details about the options allowed with each operation. One or more of the command line options is not appropriate for operation. Re-enter the command. Invalid tag for Group or User operation. Group category is unrecognized or isn't appropriate. The value you specified is not one of these values.conf file (UNIX) or the ar. Supply an appropriate value. Remove the circular reference. A value is expected for the command line option. An incorrect group ID value was specified for a dynamic group. Specify either the -G or the -U option for this command. 1 = fixed license. Error while accessing server cache file (server.

The Workday form can be imported from that definition. During installation. Either correct the workflow to reference a legal tag or add a new tag to the Holiday form. You must delete one form for business time processing to continue. The system encountered an error while trying to prepare open write licensing. The system found two forms containing the reserved workday fields. No Workday form could be found on the server. Consecutive login attempts failed because of invalid passwords. An associated error message contains details. A date in the holiday list of the Business Time Holiday form is not a legal date. a definition file with copies of the business time forms was placed on the server system. Two forms contain all the reserved workday fields -.5. Invalid times are treated as if no time was specified. The two forms are identified in an associated error message.ignored for both forms. Make sure that your user name and password were entered correctly. No Holiday form could be found on the server. reset your password or contact your administrator. a definition file with copies of the business time forms was placed on the server system. Date in the holiday list is invalid. The Holiday form can be imported from that definition.00 618 Error 620 Error 621 Error 622 Error 623 Error 624 Error Computed group qualification contains invalid content.delete one to continue. The AR System server administrator can configure the number of attempts to allow. No holiday definition exists with the specified tag. The syntax of the computed group qualification is incorrect. However. Authentication failed. To unlock your account.BMC Remedy Action Request System 7. You must delete one form for business time processing to continue. During installation. The system found two forms containing the same open license tag specified in the change history. Two forms contain the same open license tag -. Illegal dates are ignored and processing continues. The two forms are identified in an associated error message. Business time processing involving workday schedules cannot proceed without this form. Two forms contain all the reserved holiday fields -. User locked out due to too many bad password attempts. Make sure that the syntax is correct. Problem while preparing open write licensing—open write licensing may be incomplete. 625 Warning 626 Warning 635 Error 636 Error 637 Error 638 Error 639 Error 70 Error Messages Guide . The tag included in this message was specified as a holiday tag on a business time calculation. The system could not find a form with the specified reserved workday fields on it. Time in the workday definition is invalid. The system could not find a form with the specified reserved holiday fields on it. The two forms are identified in an associated error message. this tag cannot be found in the Holiday form.delete one to continue. and processing continues. A time specified in the Business Time Workday form is invalid. The system encountered an error while trying to process the license tag file. Business time processing involving holiday schedules cannot proceed without this form. Problem processing the license tag file—license tag file ignored. The system found two forms containing the reserved holiday fields.

641 Error 642 Error 643 Error 644 Error 645 Error 646 Error 647 Error 648 Error 649 Error 651 Error 652 Error 653 Error Full text search (FTS) information data associated with this tag is invalid. Recurrence Start Time must be less than Recurrence End Time. Level 1 Time Segments must be 'Available' and Level 2 must be 'Unavailable. Rerun the command. The workday schedule does not contain any open hours. or create a new Time Segment. The level specified has to be from 1 to 1000 The level parameter of the Application-Bus-Time2-Get-Free-Window command is out of range. For a workday schedule to be valid. Fix the definition to specify open times for the schedule.' Level 1 and Level 2 Time segments are special time segments. You must omit this value from the Set operation. Two forms contain all the reserved Segment-Entity Association fields -. The full text search (FTS) information for the specified tag represents a piece of information that has a data type different from the type specified in the update operation. The data value specified for one of the full text search (FTS) values is an empty string. For a recurrence time segment. This error can occur if the shared library you are using for the catalog is old or corrupted. No Segment-Entity Association form could be found on the server A Business Segment-Entity Association form was not found.delete one to continue The Business Segment-Entity Association form must be unique. there must be at least one minute during the week defined as open. If a value is specified. it must have a legal value assigned. Level 1 can only be Available and Level 2 can only be Unavailable. No Time Segment form could be found on the server The shared library you are using for the catalog is old or corrupted. specifying a level of 1 to 1000.AR System error messages 640 Error No workday definition exists with the specified tag. The workday schedule defines no open hours. Chapter 2 Action Request System error messages 71 . Full text search (FTS) information data associated with this tag has an incompatible data type or the value is out of range. You cannot have more than one copy of this form. the settings and their values must be specified. The ARFullTextInfoList structure is either NULL or empty. However. this tag cannot be found in the Workday form. or the value specified is out of the legal range of values for the FTS information setting. the start time must be less than the end time. To set one or more pieces of server information. ARFullTextInfoList structure is empty. The tag included in this message was specified as a workday tag on a business time calculation. Two forms contain all the reserved Time Segment fields — delete one to continue The Business Time Segment form must be unique. No Time Segment exists with the specified tag You specified a time segment that does not exist in the Business Time Segment form. Either correct the workflow to reference a legal tag or add a new tag to the Workday form. Make sure that the associated tag name is correct. Retry the operation. specifying the correct data type for the value. You cannot have more than one copy of this form. or you must supply a value.

An attempt was made to retrieve or set information about the full text search (FTS) environment on the server. This error commonly occurs when the target location does not exist. A full text search on a field that is not a character. does not have appropriate permissions. this error can be ignored. or does not have enough disk space for the existing FTS index. Review the #define statements in the include file ar. Fix the problem. if you are searching on many different fields that are FTS-enabled or you are issuing many different qualifications against a single FTS-enabled field. An error occurred during an attempt to change the location of the full text search (FTS) index directory.stp. An associated error message contains the full text of the error message from the FTS engine. The server encountered an error while trying to connect to the full text search (FTS) database.5. Break the operation into smaller pieces. However. You specified a code for a piece of full text search (FTS) information that was not recognized. an error occurred while reading from the FTS database. This message indicates an error in the database structure tables. The file must exist in each directory. Failed to read full text search (FTS) documents. To use the full text search (FTS) capability. Failed to relocate full text search (FTS) index directory.BMC Remedy Action Request System 7. diary. An associated error message contains details. an error occurred. an error occurred. To retrieve information. For example. Search the FTS home directory and index directory for a file named style/style. An associated error message contains the full text of the error message from the FTS engine. Failed to open the Ignore Words list file. or attachment field is not allowed.00 654 Error The full text search (FTS) information tag is unrecognized. Contact Customer Support. Failed to complete full text search (FTS) operation. While performing a full text search (FTS) operation. you must obtain a license. If you are not using the full text search (FTS) capability of the product. or attachment field. and restart the server process. diary. An associated message contains the full text of the error message from the FTS engine. This generic message indicates that an error occurred during a full text search (FTS) operation. This error is often caused by a permission problem with the Ignore Words list file. The operation you attempted generates a full text search (FTS) command that is too large for the database to handle. An error occurred during a full text search. While the system tried to retrieve or set the Ignore Words list. and the user running AR System server must have read and write access to the files. reduce the number of operations being performed. An associated message contains the full text of the error message from the full text search (FTS) engine.h for a list of all valid codes that can be specified. 662 Error Operation requested is too large for a single full text search (FTS) command. ARFullTextInfoRequestList structure is empty. Error Messages Guide 663 Error 665 Error 72 . An attempt was made to search on a field that is not a character. 655 Error 656 Error 657 Error 658 Error 659 Error 660 Error 661 Error Failed to update the Ignore Words list file. Could not initialize the full text search (FTS) database. The value you specified for the list of information to retrieve from the FTS value was NULL or empty. you must specify what information you are trying to retrieve. No users are licensed for full text search (FTS) operations on this server. While the system tried to update the Ignore Words list. Consider using the accrue capability to combine searches for multiple values on the same field. An associated error message contains the full text of the error message from the full text search (FTS) engine. there are no Full Text Search Option licenses defined for the server.

1 = fixed license. The value for the license type option must be an integer code (0 = no license. Turn off FTS operations. and try your operation again. If the directory you specified is incorrect. Form based search is not allowed without a full text license or while full text searching is disabled A search was requested using the special form-based search field in the qualification. The field you are performing the search on is a full text search (FTS) enabled field. The full text search (FTS) query is not sufficiently qualified. You performed an operation that attempted to index this field. Field is pending a full text search (FTS) operation. and retry. The target directory already exists. To perform this operation. you must have a current license of the specified type. When the indexing is completed. It might take a few minutes or a few hours for the index to be created and put in place. and specify an appropriate value. The value you specified is not one of these values. For now. 1 (fixed). You tried to move the location of the full text search (FTS) index directory. The full text search capability does not support comparing two fields. Destination full text search (FTS) index directory already exists. and retry. however. You tried to perform an operation that can only be performed when the full text search (FTS) state is set to Disabled. Unrecognized license type -. change the name to the directory you want. and the search term matched too many words in the FTS dictionary. 667 Error Full text search (FTS) operations are enabled. or 3 = restricted read license). This directory is set during installation. The Status History field (core field ID 15) cannot be enabled for a full text search. 669 Error 670 Warning 672 Error 673 Warning 674 Error 675 Error 677 Error Cannot perform a full text search (FTS) index on a Status History field. The comparison is made using the functionality of the database. the directory you will be using cannot already exist. The full text search (FTS) operation failed because the search criteria had syntax errors. Full text indexing is disabled -. remove the directory and retry the operation. Turn on FTS operations. Its creation is pending.turn on full text indexing and retry your operation A full text related operation was requested. 668 Error Invalid full text search (FTS) query. the system defaults to the search strategy supported by the underlying database. and try your operation again. Re-enter the command. You cannot use the API call arsetfulltextinfo to set the FTS information home directory. but full text indexing is not enabled.should be 0 (none). The query compares two fields that involve full text search (FTS) indexed fields. To perform this operation. Contact Customer Support for assistance in resolving the error. To move the index directory. Chapter 2 Action Request System error messages 73 678 Error 679 Error . It is set to Enabled. You tried to perform an operation that can only be performed when the full text search (FTS) state is set to Enabled. The full text search (FTS) home directory can be set only by the installer. change the FTS state to Disabled. the index does not exist on this field. the field will be available for full text searches again. change the FTS state to Enabled. 2 (floating). The attempted query involved a full text search (FTS) indexed field. and you must enable full text searching. It is set to Disabled. or 3 (restricted read). An associated error message contains complete information from the FTS engine. depending on the amount of indexing pending. If it is correct and an empty directory is in place.AR System error messages 666 Error Full text search (FTS) operations are disabled. 2 = floating license. To use this search feature.

AR System NM Daemon: Failure checking whether configuration file has been accessed. you can remove the full text user licenses or ignore the error message. The specified command-line option is not a legal option for this program. this error occurs when too many processes are running or when some processes have grown to occupy most or all available memory on the server. A complete definition of the allowed command-line options is in the Integration Guide. AR System NM Daemon: Cannot register with network manager. A rebuilding of the corresponding full text index has been initiated due to the field length change. and rerun the daemon. the system cannot run without this file. Fix the problem. run the network manager if the manager is not running). Because this file contains the definition of all mappings to perform. AR System NM Daemon: Unrecognized command-line option. An associated error message contains details. This error is not expected. The system failed to connect to the event dispatcher of the network management platform. The specified command-line option requires an additional value with this program. The system encountered an error during a call to allocate space. Because this file contains the definition of all mappings to perform. An error occurred while the system tried to open the configuration file. AR System NM Daemon: Connection to trapd lost. it was not installed correctly. this error should not occur.5. more than this number are defined. The configuration specified more fields to be mapped than the maximum amount allowed. The format of one or more lines in the configuration file is unrecognizable. The system failed to connect to the network management platform. An associated error message contains details. and rerun the daemon. and rerun the daemon. and rerun the daemon. Fix the problem (for example. Fix the problem (for example. The system can map a maximum of 300 fields in any single trap mapping. If the file is updated through AR System NM daemons. The arxxxd process lost connection to the trapd process for the network management platform. the system cannot run without this file.BMC Remedy Action Request System 7. AR System NM Daemon: Cannot register with network manager event dispatcher. An error occurred while the system verified whether the configuration file was updated. restore it to its previous format. In general. if the event subsystem is not configured. 681 Error 700 Error 701 Error 702 Error 703 Error 704 Error 705 Error 706 Error 707 Error 708 Error 709 Error 74 Error Messages Guide .00 680 Error Unable to dynamically load full text search engine software library The server attempts to load the specified library if full text user licenses are present on the system. AR System NM Daemon: Too many fields specified for one of the traps or events. Fix the problem. AR System NM Daemon: Format error in configuration file. AR System NM Daemon: Malloc failure. An associated error message contains details. An associated error message contains details. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. If you installed the full text search engine. configure it). If the file was manually edited. AR System NM Daemon: A value is expected for the command-line option. If you do not want to use the full text feature. you must install it to activate the full text search feature. A complete definition of the allowed command-line options is in the Integration Guide. If you did not install the full text search engine. AR System NM Daemon: Cannot open the configuration file.

Cannot connect to any AR System server. While you were modifying the contents of the mapping file. cancel the dismiss operation. or (2) your password is different from the one supplied. To keep the changes. ignore this error and continue. and save the changes by using the Save command on the File menu. and save the changes. If you save your changes. To save the changes. you can exit the tool without losing them. Cannot successfully connect to any server as special NM user. To discard the changes. Changes you made to this screen will be lost if you continue. The file was not opened because of a previous error or because you did not click the Save button on the window. If any fields being mapped are “protected” fields.AR System error messages 750 Error Changes to your event or trap mappings will be lost if you exit. the system cannot verify permissions or retrieve information about forms to map into. If you continue with this operation. do not ignore this message—acknowledge it and save your changes before exiting. Verify the password that you entered (remember that passwords are case-sensitive). If all fields being mapped have an “open” create mode. 753 Error 754 Error 758 Error 759 Error 760 Error 761 Error 763 Error 764 Error Chapter 2 Action Request System error messages 75 . the new file will not be opened. No AR System servers registered—cannot validate user to allow configuration. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. Accordingly. You did not save the changes you made to this file. Data in other fields truncated for entry. The password you specified is not the password recognized for you. all changes will be lost. If you exit the tool. they will be lost if you exit. you will lose the changes you made. Unless you are discarding invalid changes. You (1) have not supplied a password. an unknown (or guest) user can perform submissions. You specified a file name in this window. You have not saved the changes you made. You cannot run this tool unless at least one AR System server is accessible as a target for traps that are mapped. or (3) the server does not have a registration for you and does not allow guest users. however. you must be a registered user with update permission to the field to perform the submission. Cannot connect to any AR System server as the current user. If you continue to exit the tool. You have not opened the file defined in this window—the file will not be opened if you continue. You did not save your new or changed definitions. Out of memory. Changes on this screen will be lost if you continue. Invalid password for user on server. The specified user does not exist on this server. After the changes are saved. simply continue. they overwrite the changes made by the other user. this error occurs when too many processes are running or when some processes have grown to occupy most or all available memory on the server. cancel the exit operation. and enter the corrected password. The configuration file has been changed by another user while you have been modifying its contents. The system encountered an error during a call to allocate memory. You cannot run this tool unless you can access at least one AR System server to be the target for traps that are mapped. If guest users are allowed and create modes are open. 751 Error 752 Error User does not exist on the server. The total of all data being mapped causes an overflow of the definition in the mapping file. This message indicates that one or more field definitions were truncated and will be lost from the mapping specification to fit within the file line-length limits. the file was changed by another user. In general.

Failure while writing to the file. if you are out of space. Failure while trying to create a backup file. A target form for the mapping must be supplied. The file indicated in the error message cannot be accessed. You have entered a nondigit character for a numeric field. An associated error message contains details. You cannot add new definitions until you can open the file. This message indicates that an error occurred while the system tried to create a backup file for the SunNet Manager definition file. See the associated error message for details. no mapping is performed. if you do not have read or write access to the file. You must supply both a label and a command. The program cannot open the specified SunNet Manager configuration file. and resave your changes. Fix the problem (for example. Unrecognized selection value. and rerun the tool. The specified network management configuration file cannot be opened. An associated error message contains details. Verify the syntax specified in the mapping. however. If no target form exists. and correct it as needed.5. and try to reopen the file. You can add the value as a new option to the selection choices. An error occurred while the system tried to write updates to the definition file. The system accepts real values in decimal or scientific notation. A failure occurred when system attempted to create a backup of the definition file named fileName. or you can change the value to one of the legal values. See the associated error message for details. An associated error message contains details. remove some files to create more space). and perform the operation again. An associated message contains details. Fix the problem. A value is required for both the label and the command. You must specify a form that is the target of the trap being mapped. An error occurred while preparing the Set Fields screen. no backup file is created. Change the contents of the indicated field to a legal number. An associated message contains details. the operation is continuing. Change the value to a legal real number format. An error occurred while the system tried to map an SNMP varbind variable. Fix the problem. You specified a character string in a numeric field.BMC Remedy Action Request System 7.00 765 Error 766 Error 767 Error 768 Error 769 Error 770 Error 771 Error Cannot open the network management configuration file. and repeat the operation. You can enter digits only in numeric fields. Failure while building Set Fields screen. change your file access permissions). Cannot access the indicated file. You have entered an improperly formatted value for a real field. The label is the name displayed on the menu. 772 Error 775 Error 791 Error 792 Error 793 Error 794 Error 76 Error Messages Guide . Invalid mapping of an SNMP varbind variable. Cannot open the SNM configuration file. Fix the problem (for example. Failure while writing to the file. The system continues the operation and updates the definition file. and the command is the operation performed when the label is selected.bak. A selection value was specified that is not one of the legal selection values for the field. The value for the real field is not a recognized real format. An error occurred while the system tried to save changes to the specified file.

The server process relaunches the server that shut down. The child process was not launched. 796 Error 797 Error 802 Note 842 Error 843 Error 844 Error 845 Error 847 Error 855 Error 856 Error 857 Error Failure during wait operation—unable to wait for status change. Malloc failed on TC server. You cannot specify a quotation mark in the command line. The file holding the list of fields that have indexing pending could not be opened when you tried to add a note about the updated field. and retry the operation. An associated error message provides details. the server stops trying to launch the process and removes it. AR System server terminated unexpectedly—restarting. This is an internal error. Fix the problem. You must change the label so that it does not include a quotation mark character. The child process was not launched. You defined a mapping (probably using varbind) where one of the mappings is wrong. this error occurs when too many processes are running or when some processes have grown to occupy most or all available memory on the server. Pending list file open action failed. An associated message provides details. A full text search (FTS)–enabled field was updated. A failure occurred while the system tried to launch a child process. An associated message provides details. An associated message provides details. Attempted to launch this server more than four times within 30 seconds—abandoning attempt to start this server. The system encountered an error during a call to allocate space. The name of the process being restarted is reported in an associated message. A failure occurred while the system tried to launch a child process. The server detected that one of the child processes it is responsible for terminated. Fix the mapping. and retry the operation. Pending list lock file does not exist The arservftd process cannot release the work file. Failure during exec operation—cannot launch child server. and reissue the mapping request. The failure occurred on the server during processing of a call from the client. Pending list lock file exists. Invalid mapping parameters. Fix the problem. You must change the command line so that it does not include a quotation mark character. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. Failure during fork operation—cannot launch child server. Cannot have a quotation mark in the command line due to SunNet Manager syntax. The work file must be locked by the arservftd process but is being held by another process. In general. The command line you specified contains a quotation mark. because it is a special character in the SunNet Manager definition syntax. The name of the child process that was not restarted is identified in an associated message. Chapter 2 Action Request System error messages 77 . Because this process continues to fail. A failure occurred while the system tried to wait for a status change. because the file does not exist. The server process tried to launch a child process more than four times within 30 seconds. You cannot specify a quotation mark in the label because it is a special character in the SunNet Manager definition syntax. The specified label contains a quotation mark.AR System error messages 795 Error Cannot have a quotation mark in the label due to SunNet Manager syntax.

If the signal is a number other than 15 or is one you sent directly to the process. A full text search (FTS)–enabled field was updated. You did not provided the minimum set of arguments required by the full text search (FTS) indexer process (arservftd).BMC Remedy Action Request System 7. Only one instance of the full text search (FTS) indexer process can be run on any given computer. An associated error message provides details. A full text search (FTS)–enabled field was updated. If the signal is 15. Failed to truncate the pending list file. The supplied action code is not recognized. Too few arguments for the full text search (FTS) indexer process. An associated error message provides details. You exceeded the limit of arguments allowed by the full text search (FTS) indexer process (arservftd). Request ID. There is a limit to the other arguments allowed when this option is specified. The optimize argument was specified for the full text search (FTS) indexer process. 859 Error 860 Error 861 Error 862 Error 863 Error 864 Error 865 Error 866 Error 867 Error Another copy of the full text search (FTS) indexer process is already running. The file holding the list of fields that have indexing pending could not be written to when you tried to add a note about the updated field because the record associated with the updated field was not found. no action is required. Too many arguments specified for optimize argument. Failed to purge pending list file. contact Customer Support for assistance in determining the cause of the problem. The process was stopped either accidently or intentionally by a user in your environment. See the Configuration Guide. restart the server and continue to work. See the Configuration Guide. If so. you must supply a form ID or name. An associated error message provides details. field ID. During a reindex operation. Determine whether a copy of arservftd is already running. The number following this error is the signal that was received. The file holding the list of fields that have indexing pending could not be written to when you tried to add a note about the updated field.00 858 Error Pending list file write action failed. and a Request ID. Record does not exist in the pending list file. one or more of the arguments that are not allowed were specified. In this case. 868 Error 78 Error Messages Guide . The file holding the list of fields that have indexing pending could not be truncated when you tried to add a note about the updated field.5. Too many arguments for the full text search (FTS) indexer process. The server most likely shut down due to a bug in the system. When specifying an operation against a specific request. See the Configuration Guide for information about allowed routines. One or more of these values is missing. a field ID. Invalid action for the full text search (FTS) index process One of the arguments for the full text search (FTS) indexer process (arservftd) indicates the action for the program to take. See the C API Reference for more information. an error occurred while the system tried to purge the list of pending changes. An associated error message provides details. See the C API Reference for more information. Form ID or name. Full text search (FTS) indexer process terminated when a signal was received by the server. The server for the full text search (FTS) search feature (arservftd) was terminated by a signal. A full text search (FTS)–enabled field was updated. and action are required together.

Change to the correct server or specify an existing image. There is a limit to the other arguments allowed when this option is specified. No image type. You must supply an appropriate value for the argument. or the file was moved). The system encountered an error while attempting to access the configuration file indicated on the command line. Failure occurred while accessing mail configuration file. Invalid image definition. The submitted mail message had a format that was not recognized. No image type specified. This error is usually caused by a manual deletion of the contents of a structure file. The specified image could not be found. The message can be resubmitted with a form specified. See the C API Reference for more information. The message can be resubmitted with the additional information added. Most likely. Missing value for command line parameter. To create a new entry by using the mail daemon. The specified image is not in the AR System database. one or more values must be provided. the specified file does not exist (file name was misspelled. Can not begin transaction because a transaction is already open. restore it from a backup. or rename the existing image. No image content has been specified for the image being created or updated. or a default form must be configured for the armail process. A file specified as holding the definition of an image does not contain an image definition. This argument is required when creating or updating an image object. such as jpg or bmp. and no default form is configured for the armail daemon. In this case. Duplicate image name. The retry argument was specified for the full text search (FTS) indexer process. Choose a different name for the image. An operation was attempted against the wrong server. one or more of the arguments that are not allowed were specified. The format of the mail message does not match the expected format that. No text exists in the body of the mail message to specify values to be assigned for the new entry. No image specified. has been specified for the image being created or updated.AR System error messages 869 Error Too many arguments specified for the retry argument. Maximum number of client transactions already in use. This argument is required when creating or updating an image object. The mail message does not contain a line identifying which form is the target of the submission. An associated message contains details. 881 Error 882 Error 883 Error 884 Error 885 Error 897 Error 899 Error 951 Error 952 Error 953 Error 955 Error 956 Error Chapter 2 Action Request System error messages 79 . A command line argument that requires a value was specified but no value was provided. or no image is defined by that name. Fix the problem. and reissue the command. The specified image is already in the AR System database. The submitted mail message did not contain a body providing details for the new entry. If the file was deleted. Review the message and verify the format against the formats shown in the Configuration Guide. The submitted mail message did not contain a form name.

958 Error 959 Error 961 Note 964 Error 965 Error 966 Error 967 Error 968 Error 971 Warning Your submission was accepted by the AR System. or is not accessible. and one or more requests were found. Make sure that the mail system is still accessible. When querying through the mail interface. A user tried to submit a request to another server. The maximum number of allowable matches are returned. However. The armail attempt to log on to the mail post office failed. 972 Warning 973 Warning No matches were found to your query request. No fields in the query list are accessible to you for this form. The return includes this message and the data for the specified maximum number of entries. does not exist in the mail system. This daemon was configured to support submissions to only a single specific server. Use the Request ID number for querying or modifying the request. The mail message specifies a submission to a form that is not the form specified as the required form in the mail configuration file. armail could not read a mail message from the post office. The submitted email message successfully created a request in AR System. Required currency value not specified. The server specified for this message is not a recognized server—access was attempted. Use a valid address. so you cannot see any data returned from your search. This error can be encountered only through an API program. Could not read mail from the mail post office. armail failed when trying to log in to the mail system. The submitted mail message specified a server that does not match the required server. you do not have access to any of the fields in the report. and make sure that the mail system is still accessible. The address indicated is either ambiguous. When retrieving data through the mail query interface. To: destination. but no server was found.BMC Remedy Action Request System 7. However. Make sure that the mail system is still accessible. Verify that the Mail login and password given during installation are valid and that the mail system is accessible. This daemon was configured to support submissions to only a single. armail could not log off from the post office. The armail process was run. no requests were found that match the query conditions specified. Attempt to send mail to the mail post office failed. the criteria specified matched more entries than the limit configured for the armail process. The number of matches to your query request exceeded the configured limit of limit. specifying the -x command line option to connect to a specific server.5. The mail message specifies a submission to a server that is not the server specified as the required server in the mail configuration file. Could not log off from the mail post office. the server or AR System on that server is not active. The value portion of the currency structure was not provided. A user tried to submit a request to another form. See your administrator to get the necessary permissions so you can see the data you are trying to retrieve. You specified a quick report format.00 957 Error The submitted mail message specified a form that does not match the required form. The process must be able to connect successfully with at least one server. ID for the new request is requestID. Could not resolve the armail address. 980 Error 80 Error Messages Guide . specific form. The armail address specified is not considered unique within the mail system.

This command line option requires that the name of a parameter and the value for that parameter be supplied. No common functional currency was found when currency constants were compared with functional currency data. The -e and -i options require a macro name. A currency field was specified to be the group-by field in a statistical query. AR System converts that value to a functional currency type and stores it. 986 Error 987 Error 988 Error 989 Error 998 Error 999 Error 1000 Error Currency value contains a currency code that is not allowed for this field. You cannot allocate memory on startup. When a character value is converted to a currency value. Add the currency code. Currency fields not allowed for grouping. This is an internal error that probably indicates the system is low on resources. The currency code either does not exist in the Currency Code form or has not been marked as Active. Unable to free shared or exclusive lock. A shared or exclusive lock cannot be released due to unexpected events in the server. or specify a parameter and value to go with the option. This error can be encountered only through an API program. this error message is returned if the string contains no numeric value or if the decimal number is invalid. A system error occurred. The -p option was specified as the last option on the command line. No common functional currency exists to use in relational operation. Bad currency value. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. Cannot create or modify a currency field without specifying at least one functional currency. Remove the option. An attempt was made to reference a currency code that does not exist or was disabled.AR System error messages 981 Error 982 Error 983 Error 984 Error 985 Error Required currency code not specified. or specify a macro to go with the option. Restart the server. A currency code was entered that is not an allowable currency code for this field. which is not allowed. When a request is submitted that includes a currency value. 1001 Error 1002 Error Chapter 2 Action Request System error messages 81 . Specify a currency field part. The -e or the -i option was specified as the last option on the command line. this error occurs when too many processes are running or when some processes grow to occupy most or all available memory on your server. Remove the option. which automatically re-creates the form if necessary. The system encountered an error during a call to allocate memory. In general. No Currency Code form exists. Both of these command line options require the name of the macro to be run at start-up. A currency field was specified in a context where only a specific currency field part is allowed. Currency part must be specified to use currency field in this context. or the AR System Currency Code form was deleted. Unable to free shared or exclusive lock on user cache hash list. The currency code portion of the currency structure was not provided. You must include at least one functional currency type. The -p option requires a substitution parameter and a value. Restart the AR System server.

If you specify parameters to be used in a macro. The -d command line option requires that you specify a directory. 1008 Error 1009 Error 1010 Error 1011 Error 1012 Error 1013 Error 82 Error Messages Guide . no macro is defined (by using the -e or -i options). The macro name specified on the command line is too long. Configuration information for your session is stored in a configuration file named config in the directory indicated by the ARHOME environment variable. You can specify a macro that runs other macros if desired. View the permissions on the file to make sure that you have read access (and write access if you intend to update the configuration file). Two startup macros have been specified. This option can be specified only once. it is in a directory named arHome under your UNIX login directory. The -p option requires the name of a parameter followed by an equal sign followed by a value. However. The directory name specified in the -d command line option is longer than the maximum length allowed for a directory name. See the Integration Guide for information about command line options. and restart the aruser program. The directory name in a parameter is longer than the maximum allowed length. The aruser program on UNIX is an X program. Re-enter the command. Start a windowing system. 1004 Error 1005 Error 1006 Error 1007 Error You cannot connect to the X server. The -d command line option was specified two or more times. If either the name or value contains spaces or special characters. BMC Remedy User allows a maximum of one macro to be specified at startup. Specify a legal macro name defined in your system. Parameters can be specified only if you specify a macro first. No servers were specified for the aruser program to connect to. if starting the aruser program from the command line. Two or more startup macros were specified on the command line. The -d option requires a directory name. one or more servers must be defined by using the -x command line option. specifying only one -d command line option for the directory that contains the startup macro you want to run. No window system is running in your environment. You specified a -p command line option that specifies values for parameters in a macro to be run at startup. No servers are defined for the AR System in the directory file.BMC Remedy Action Request System 7.5. specify the macro that uses them. The maximum length for a macro name throughout AR System is 30 bytes. The specified command line option is not recognized. Verify the setting of the ARHOME environment variable if you defined an alternate directory. the value must be quoted to be treated as a single value on the command line. The program cannot read the contents of that file. It requires that an X windowing system be running to allow the program to operate. One or more parts of the definition are missing. Verify the syntax of the command line to make sure that you did not omit required spaces between options. You cannot read the configuration file—ARHOME variable may be set incorrectly. so only one can be specified on the command line at any time. Re-enter the command. The macro name in a parameter is longer than the maximum allowed length. Two directories for startup macros have been specified.00 1003 Error The format for the -p option is -p name = value. omitting the -d option if not needed or supplying an appropriate directory name. There must be one or more servers defined in the /etc/ar file or. If no ARHOME environment variable is set. Both the -e and -i options specify macros to be run. Unrecognized command line option.

Re-enter the command.x or later AR System servers. The most serious messages are displayed. omitting the -x option (if not needed). 1201 Warning New text is longer than the maximum allowed length—truncating to fit. you can ignore this message. Chapter 2 Action Request System error messages 83 . This message notifies user when the attachments are exported to a directory for reporting. In the same situation. The field has a maximum length defined. No requests were found that match the qualification criteria you specified. No description. The server name specified in the -x command line option is longer than the maximum length allowed for a server name. This message gives the name of the active link and the specific action in the active link where the error occurred. some of the messages were suppressed. No matching requests (or no permission to requests) for qualification criteria. but no startup macro was specified using the -e or -i command line option. and the text that you entered is too long for the field. action action. The error occurred while running an active link. The process terminated unexpectedly. The -x command line option requires that you specify a server name. to avoid overflowing the screen. Note: This message is returned by BMC Remedy User. similar messages are 1015 Error 1016 Error 1017 Error 1067 Error 1100 Note 1101 Note 1102 Note 1103 Note 1200 Warning returned by web services and API programs (see message 302) and web clients (see message 9296). In general. The operation that was being performed generated a large number of error messages. However. Include this directory in the export file to import the data. Verify the syntax of the command line to make sure that you did not omit required spaces between options. You specified the -d command line option. Server is not compatible with BMC Remedy Alert. The preceding error occurred during execution of active link activeLink. Additional errors were truncated. You do not have access to the request or to the fields you specified in the request.AR System error messages 1014 Error A directory can be specified only if you specify a macro. or supplying an appropriate server name with the -x option. The server name in a parameter is longer than the maximum allowed length. omitting the -d option or specifying a startup macro with the -e or -i option. Re-enter the command. The BMC Remedy Alert client works only with 5. This message displays the entry ID of the newly saved entry. This information is useful for debugging active links. The text you specified is too long for the field you are trying to update. Attachments for the report are exported under directoryName. There are two possible reasons that requests were not returned: The criteria you specified do not match any requests. The extra text is truncated so that it fits in the target field. The -x option requires a server name. The entry was successfully created with ID = entryID The Save operation was completed successfully.

BMC Remedy Action Request System 7. Macros cannot record operations continuing from partial selections in a query list. you have a customized view of the form. To keep your changes. the recorded operations are lost. You have not saved changes on this screen—they will be lost if you continue. An administrator updated the form being opened. click Continue. To discard the changes. and then save the changes. or you can cancel the operation (not save your changes). click Continue Recording. If you continue with the Dismiss operation. One or more fields were added to the form. You started recording a macro and then requested that the macro recording be canceled.5. You changed the data on the current screen. You have not saved changes on a diary or text edit window—they will be lost if you continue. your changes will be lost. click Continue. click Cancel Dismiss. click Exit. If you are changing fields where the data you enter is supposed to be the final value. You can use the Customize View operation in BMC Remedy User to locate the new field. However. You have not saved changes on this screen—they will be lost if you continue. 1205 Warning 1207 Warning 1208 Warning 1209 Warning 1210 Warning 1211 Warning 84 Error Messages Guide . After the macro is saved. and make it visible if you want to use it. click Yes. This record has been updated by another user since you retrieved it. and then save the macro. your changes will be lost. To keep your changes. and then save the changes. You specified that you want to exit BMC Remedy User. You changed the data on the current screen. To keep your changes. 1203 Warning 1204 Warning Partial selections will become full selections on playback. click No. To save the macro you are recording. You changed the data on the form Item Properties associated with the Customize View window. If you continue with the Next or the Previous operation. continue with the operation. the new field is added as a hidden field on your view. move it to an appropriate location. retrieve the request again. your changes will be lost. New fields added or made accessible by administrator—added as hidden fields to local view file. A recording operation is in progress—current recording will be lost if you continue. If you continue with the Dismiss operation. You have not saved changes on the properties screen—they will be lost if you continue. however. To discard the changes. so the macro cannot reasonably record information about partial selections. To discard the changes. your changes will be lost. To continue with the recording. click Cancel Dismiss. click Cancel Exit. and then save the changes. saving your changes. To keep your changes. To avoid possible conflict with your customizations. you can exit without losing the macro. If you click Cancel Recording. The contents of the query list are likely to be different when the macro is replayed. The macro records the operation as if all items in the query list were selected. To discard the changes. If you do not want to save the macro and you want to exit the program. and then save the changes. If you are updating a diary field. Do you want to save your changes? The request you tried to save changes to was modified by another user after you last changed it. You can save your changes over the changes of the other user. You changed the data on a Diary or a Text Edit window. click Cancel Dismiss. your changes do not overwrite changes made by the other user. click Continue. a macro recording operation is in progress. and re-enter your changes. Saving your changes will overwrite the changes made by that user.00 1202 Warning A recording operation is in progress—your current recording will be lost if you exit. If you continue with the Dismiss operation.

A failure occurred while the system tried to retrieve Help text for the field. save the data in the Diary or Text Edit window by selecting Save in that window. Duplicate name for macro. the operation is canceled and the window remains unchanged. click Cancel Dismiss. Do you want to overwrite the existing macro? You specified a name for a new macro that matches the name of an existing macro. You have not saved changes on a diary or text edit window—the changes will not be included in the current save action if you continue. Multiple requests match qualification criteria—Information pulled from first matching request. To avoid modifying multiple entries. If you cancel this operation. but BMC Remedy Developer Studio defined AR System to display only the first matching request from the search. This message is displayed to indicate that the operation is complete and would have been performed if the macro recording was not in progress. and verify the operation you are performing. Locale-sensitive operation done on the server may not conform to the client’s locale convention. click Continue. You can overwrite the file or cancel the Report operation. You changed the data in a Diary or Text Edit window. The name for a macro is a combination of the name and the directory it is stored in. leaving the existing macro definition intact. Server cannot set the client locale. or you can cancel the operation and change the name for the new macro. An associated error message provides details. Do you want to continue? The operation you are performing modifies many entries in the database.AR System error messages 1212 Warning Search window is now connected to a different form—continuing will change the current form. You can have a macro with the same name in different directories without conflict. click Continue. 1213 Error 1214 Warning 1215 Warning 1216 Warning 1217 Warning 1221 Warning 1222 Warning 1223 Warning The specified file already exists. To discard your changes in the Diary or Text Edit window. and re-click Save on the current window. Make sure that the server and client can use the client’s locale convention. the Submit and Modify All operations are not performed when you are recording a macro. Macro recording is active—operation recorded but no database operation performed. More than one request matched your qualification. If you continue this operation. The Search window is connected to a form different from the form being referenced in the window where you are performing the operation. You can overwrite the existing macro to replace the old definition with the new definition. The data in the Text Edit or Diary windows might be overwritten by the existing text in the windows after the Refresh operation following a successful modification. The file you specified as the target of your report already exists. Your changes will not be saved if you click Continue. To continue with the modification. Chapter 2 Action Request System error messages 85 . This operation will modify number entries. If the changes are important. This message is issued only from the Modify All window. the window changes to the new form. The message specifies the number of entries that will be modified. and continue with the Save operation. click Cancel. To avoid spurious submissions to the database and to prevent incorrect bulk modifications of data. Unable to find help for the specified field.

leaving the existing custom report definition intact. Help text is too long.00 1224 Warning Duplicate name for custom report. The selected macro definition will be deleted. You can overwrite the existing custom report if you want the new definition to replace the old definition. please remove unwanted files. The name for a user command is a combination of the name and the directory it is stored in. or click Cancel to cancel the Delete operation and retain the user command definition. BMC Remedy User displays only 32. You can have a custom report with the same name in different directories without conflict. create space for the file. 1225 Warning Duplicate name for user command. or you can cancel the operation and change the name for the new user command. Click Continue to continue with the operation and delete the user command. No action was taken. any operation that used a global (Modify All) or unrecoverable (Delete) action was performed. only the first 32. but the operation was recorded and will replay on later use. 1229 Warning 1230 Warning 1232 Warning 1233 Warning 1234 Warning Your disk drive is almost full. The selected user command definition will be deleted. Do you want to overwrite the existing user command? You specified a name for a new user command that matches the name of an existing user command.000 characters of Help text.000 characters are shown here. You can overwrite the existing user command to replace the old definition with new definition. Click Continue to continue with the operation and delete the custom report. To continue with the operation. The disk containing the file you are writing is approaching its maximum storage capacity. This prompt is issued (when you try to delete a macro definition) to make sure that you do not accidentally and permanently delete the wrong definition. or click Cancel to cancel the Delete operation and retain the custom report definition. The name for a custom report is a combination of the name and the directory it is stored in. leaving the existing user command definition intact. or click Cancel to cancel the Delete operation and retain the macro definition. Do you want to overwrite the existing custom report? You specified a name for a new custom report that matches the name of an existing custom report. or you can cancel the operation and change the name for the new custom report. You can have a user command with the same name in different directories without conflict. An associated error message contains details. The selected custom report definition will be deleted. 86 Error Messages Guide . Macro recording is active—modifications will be made to the entry but will not be recorded in the macro. 1227 Warning 1228 Warning Failure trying to expand the character menu.5. You are recording a macro in BMC Remedy User. Click Continue to continue with the operation and delete the macro.BMC Remedy Action Request System 7. This prompt is issued (when you try to delete a user command definition) to make sure that you do not accidentally and permanently delete the wrong definition. An error occurred while the system tried to expand the definition of a character menu. When the macro was processed. This prompt is issued (when you try to delete a custom report definition) to make sure that you do not accidentally and permanently delete the wrong definition.

only the first 32. Fix the problem. This means that the name is not recognized as one of the groups defined for the system. Do you want to reload the form from the server? If you click Continue. You cannot open default file.arf files). capitalization. Verify that you have read and write access to the ARHOME directory and to the definition files (. Verify that you have read and write access to the ARHOME directory and to the default files (.rep file. or both—as specified by the user in the workflow logging options dialog of BMC Remedy User—cannot be opened. Verify that you have read and write access to the ARHOME directory and to the view files (. File will be saved in Report File format. If you add more characters to the field.000 characters in BMC Remedy User.AR System error messages 1235 Warning Text field is too long. Double-click a form from the list. A group name specified in the Group List field (ID 104) or Assignee Group field (ID 112) cannot be translated. The list contains all valid forms. you cannot further customize without reloading an Admin view from the server. The workflow log file’s path.rep if none specified. . The file containing the cached view for the form cannot be opened. you lose all information over the 32. 1236 Warning Your window resources are low.ard files). and retry the operation. and retry the operation. you will lose your customized view. Shut down all tools other than AR System tools. close unwanted windows or applications.000 characters are shown here. or . but you can recustomize the view and continue with the new view. You can continue with out-of-date customized view files. it will damage the record. You are running too many applications to operate AR System client tools efficiently.rep. You cannot open definition file. The file containing the cached definition for the form cannot be opened. The supplied qualification or assignment statement has improper syntax. the existing customized view remains available. Verify the spelling.000 character limit and any changes that you made. Character fields display only 32. Consider adding more memory or reconfiguring your system resources. You cannot open view file. name. Fix the problem. If you do not continue. All customizations will be lost. and spacing of the name to make sure that it is one of the legal group names. Default file extension is *. The workflow logging file specified in the logging options dialog cannot be opened. This message appears if you are saving a report and do not specify .arv files). If you change this request. or they can be reloaded from the server. The report definition defaults to saving the report as a . 1237 Warning 1242 Warning 1243 Warning You cannot translate the group name in the Group List or Assignee Group field. There was a problem expanding the EXTERNAL qualification. The file containing the user-defined defaults for the form cannot be opened. 1244 Warning 1301 Error 1400 Error 1401 Error 1402 Error 1404 Error Chapter 2 Action Request System error messages 87 . Verify that you have file or directory access permissions.csv formats. No such form exists—make a selection from the list.arx. and retry the operation. If you continue with the view from a previous version of the tool. You entered an unrecognized form name. Fix the problem. This can be caused by permission problems in your ARHOME directory.

An error occurred while the system tried to reset your view. and retry the operation. An associated error message provides details. An error occurred while the system tried to create a backup copy of the view file. You cannot write to the definition file. You cannot reset user view. Fix the problem. These files are stored in your ARHOME directory (. and retry the operation. An error occurred while the system tried to read from the file identified in the error message. These files are stored in your ARHOME directory (. You cannot write to the view file. Fix the problem. Fix the problem. An error occurred while the system tried to write to the view file for this form. An error occurred while the system tried to restore your previous view. and retry the operation. and retry the operation. You cannot open a temporary file. and retry the operation. 1408 Error 1409 Error 1411 Error 1412 Error 1413 Error 1414 Error 1415 Error 1416 Error 1417 Error 1418 Error 88 Error Messages Guide . An error occurred while the system tried to write to the definition file for this form. Verify that you have read and write access to the ARHOME directory and to the view files (. You cannot open support data or cache file.5. An error occurred while the system tried to write to the user-defined defaults file for this form.00 1405 Error 1406 Error 1407 Error You cannot open configuration file. Fix the problem. and retry the operation. Fix the problem. An associated error message provides details. Fix the problem. You cannot write to the specified file. An associated error message provides details.arv files). An associated message provides details. Verify that you have read and write access to the ARHOME directory and to the configuration file (config). and retry the operation. An associated error message provides details.arf files). You cannot restore previous view. Fix the problem. An associated message provides details. An error occurred while the system tried to write to the file identified in the error message. The file containing the support file for the form cannot be opened. and retry the operation. and retry the operation.BMC Remedy Action Request System 7. An associated error message contains details. You cannot make a backup view. Fix the problem. The operation continues without creating a backup file. The file indicated in the message cannot be opened. An associated message provides details. and retry the operation. You cannot open the specified file. An associated error message provides details. Fix the problem. An associated error message provides details.arv files).ard files). An error occurred while the system tried to write to the support file for this form. Fix the problem. An associated error message provides details. The configuration file cannot be opened. Fix the problem. You cannot write to the default file. A failure occurred when the system tried to open a temporary file. These files are stored in your ARHOME directory (. and retry the operation. You cannot read from the specified file. These files are opened in the directory /tmp. Fix the problem. These files are stored in your ARHOME directory (. and retry the operation. You cannot write to the specified support data or cache file.arv files).

and treat the error as if an Out of memory error occurred (see Error 1500). Cannot create new field. An associated message provides details. and rerecord your macro. you can ignore this message. A failure occurred while the system tried to start a child process that is retrieving data for a field. specify a field type appropriate for the data type of the field. specify a field type appropriate for the data type of the field. Otherwise. Only selection type fields can have a field type of exclusive choice. You cannot record operation: operationType. An error occurred while the system tried to create a field on the form. Out of memory. Only integer type fields can have a field type of numeric text. The view file will be deleted and reloaded the next time you access the form. The field type was changed to text for this field. You requested a field type of numeric text for a field that is not an integer field. so no data is changed in any fields. The system encountered an error during a call to allocate memory. View file format error: missing form name. The child process was not started. The form name found in the view file does not match the name of the form in the definition file. You requested a field type of exclusive choice (option buttons in UNIX) for a field that is not a selection field. Unrecognized field type (defaulting to text). The view file will be deleted and reloaded the next time you access the form. The failure occurred on the client (the one running the aruser program. Only integer data types can be displayed by using numeric text (defaulting to text field type). If a text field type is acceptable. Cancel the recording operation. Fix the cause of the failure. and retry the operation. You specified an unrecognized field type for a field. A failure occurred while the system tried to start a child process. The field type for this field is text. you can ignore this message. Only selection data types can be displayed using exclusive choice boxes (defaulting to text). An associated message provides details. and retry the operation. This error can occur when too many processes are running or when some processes have grown to occupy most or all available memory on your client computer. The field type was changed to text for this field. This error usually indicates a serious resource shortage for the application. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. The field type for this field is text. The view file for the form does not have a form name.AR System error messages 1450 Error 1451 Error Fork operation failed. If a text field type is acceptable. BMC Remedy User). View file format error: invalid form name. The system is probably out of memory. The child process was not started. specify a field type appropriate for the data type of the field. Otherwise. An error occurred while the system tried to add the specified item to the list of recorded operations. Only selection data types can be displayed using checkboxes (defaulting to text). Fix the cause of the failure. Only selection type fields can have a field type of check box. Failure occurred while trying to run a process to load a field value. Treat the error like an Out of memory error (see Error 1500). Otherwise. The indicated operation will not be in the macro you are building if you continue. you can ignore this message. you can ignore this message. specify a field type appropriate for the data type for this field. If a text field type is acceptable. Otherwise. You requested a field type of check box for a field that is not a selection field. If a text field type is acceptable. 1500 Error 1501 Error 1502 Error 1503 Error 1504 Error 1505 Error 1506 Error 1507 Error 1508 Error Chapter 2 Action Request System error messages 89 .

the format of the view file is unexpected. Definition file format error: missing form name. Because the end clause of a form or active link definition was not found where expected in the view file. the format of the view file is unexpected. View file format error: field definition. Because a menu definition that tries to jump more than one level in the menu hierarchy is present in the file. Because a field clause was not found where expected in the definition file. The view file will be deleted and reloaded the next time you access the form. The definition file will be deleted and reloaded the next time you access the form. View file format error: begin active link. Therefore. The definition file will be deleted and reloaded the next time you access the form. The only information expected after the end clause of a form is the definition of active links. Because an invalid clause was found in a field definition in the definition file. 1512 Error 1513 Error 1515 Error 1516 Error 1517 Error 1518 Error 1519 Error 1520 Error 90 Error Messages Guide . Definition file format error: invalid form or active link end. The view will be deleted and reloaded the next time you access the form.BMC Remedy Action Request System 7.00 1509 Error 1510 Error 1511 Error View file format error: field clause. The definition file will be deleted and reloaded the next time you access the form. Definition file format error: invalid form name. The definition file for the form does not have a form name. the format of the definition file is unexpected.5. Definition file format error: field clause. The view file will be deleted and reloaded the next time you access the form. Definition file format error: character menus. Definition file format error: field definition. View file format error: invalid form or active link end. The view file will be deleted and reloaded the next time you access the form. View file format error: active link definition. Because an invalid clause was found in a field definition in the view file. the format of the definition file is unexpected. the format of the definition file is unexpected. An error occurred with the definition of a character menu. The definition file will be deleted and reloaded the next time you access the form. When the file contents after the end clause were processed. the format of the definition file is unexpected. an entry was found that was not the start of an active link. The form name found in the definition file does not match the name of the form. The definition file will be deleted and reloaded the next time you access the form. the format of the view file is unexpected. Because an invalid clause was found in an active link definition in the view file. The definition file will be deleted and reloaded the next time you access the form. Because the end clause of a form or active link definition was not found where expected in the definition file. the format of the view file is unexpected. the format of the view file is unexpected. The view file will be deleted and reloaded the next time you access the form. Because a field clause was not found where expected in the view file.

AR System error messages 1521 Error Definition file format error: begin active link. An error occurred while formatting the diary text for a field. An associated error message contains details. Remember. Unrecognized selection value. The only information expected after the end clause of a form is the definition of active links or of character menus. A report requires space for at least five lines of text on the page. Therefore. The space available for a line is the total number of characters allowed on the line less the size of the right and left margins. and the Y coordinate must be between 0 and 3000 inclusive. Increase the page size. Accordingly. The X or Y coordinate value specified is out of the legal range for the coordinate. or decrease the size of the right or left margin so that the total space available is at least 40 characters. When processing the file contents after the end clause. No reference to a Status field can be found for this form. the format of the definition file is unexpected. The specified selection value is not a legal selection value for the field. Total number of characters per line between margins less than minimum of 40. Total number of characters per line including margins is greater than maximum of 4096. Change the value of the X and Y parameters. The X coordinate must be between 0 and 1500 inclusive. The definition file will be deleted and reloaded the next time you access the form. 1522 Error 1524 Error 1525 Error 1526 Error 1527 Error 1528 Error 1529 Error 1530 Error Status field is not accessible—cannot display Status History. 1531 Error 1533 Error Chapter 2 Action Request System error messages 91 . an entry was found that was not the start of an active link and also not a character menu. Update of custom operation failed. Column headers will not fit within the space defined between top and bottom margins—total number of lines increased to the following value. Increase the line length. A report requires space for at least 40 characters of text on a single line. The total number of spaces on the page between the right and left margins is fewer than the minimum of 40 characters. The update of the custom operation failed. or both. This is an unexpected error. you cannot display Status History information. The definition file will be deleted and reloaded the next time you access the form. selection values are case-sensitive. The number of lines per page was increased to the indicated value to provide enough space for the column headers and five lines of data. An associated error message contains details. A failure when the system opened or wrote to the file containing the custom operation is a common cause of this problem. The space available for a page is the total number of lines allowed on the page less the size of the top and bottom margins. Definition file format error: active link. Because an invalid clause was found in an active link definition in the definition file. A report cannot have lines with more than 4096 characters of text. the format of the definition file is unexpected. X. Cannot format diary entry. The total number of lines on the page between the top and bottom margins is fewer than the minimum of five lines. Decrease the line length so that the total space available is no more than 4096 characters. View the definition for the field to verify the legal values. or decrease the size of the top or bottom margin so that the total space available is at least five lines. The number of lines that remain between the top and bottom margin on the page are insufficient to allow the column headers to be printed. coordinates are out of range. Total number of lines between margins less than minimum of five. Y.

and retry the operation. 1544 Error 1545 Error 1546 Error 1547 Error 1548 Error You have entered an improperly formatted value for a decimal field. statistic result. If you are saving an updated macro or custom report under an existing name. specify a new name in the Name field. You must specify the field name (or arithmetic operation) on which the operation is performed. Use BMC Remedy Developer Studio to confirm the size limits of the field properties. You entered a value for a numeric field that is either smaller than the minimum size allowed or larger than the maximum size allowed. You can dismiss this window without changing the login information for the current user. An associated error message contains details. You entered a nondigit character for a numeric field. Change the value to a legal real value. The value specified for the field name must be a field defined for the form. Supply a name for your macro or custom report.5. You requested that a macro or custom report be saved.BMC Remedy Action Request System 7. Make sure that the spelling is correct. The field name is used to determine which column to display the result under in a column-style. A numeric field contains a nondigit value. Value specified for field name not numeric or not a field. 1539 Error 1540 Error 1541 Error Attempt to create macro or custom report failed—file system error. or one of the numeric or date keywords. The value is not a legal time value. The format of the time value is not recognized. You requested a count statistic with a column layout without specifying a field name to count on. You have entered an improperly formatted value for a real field. specify the name you are updating. 1543 Error A field name is required for all operations except COUNT. However. you did not specify a name for the operation. The indicated value was entered as a value for a field with a data type of real. The value is not a legal real value. The value is not a legal decimal value. The file system could not create or write to the file holding the definition of the operation. and update the field name request to be a legal operation. An error occurred while the system tried to create a list of the forms available from each of the connected servers. and retry the operation. You can specify digits only for integer (numeric) fields. The value was entered in a field with a data type of decimal. You cannot specify a COUNT operation with a column layout without specifying a field name. The value was entered in a field with a data type of date/time. You have entered an improperly formatted value for a date/time field. Cannot query servers. Change the value to a legal decimal value. a numeric value. The value you specified for the numeric field is either smaller than the minimum size or larger than the maximum size. An associated error message contains details. These are the only types of definitions allowed in the field name for a statistical operation. Change the value to a legal time value. specify a user name. and retry the operation. This name specifies the field the operation is performed on. You must specify a user name to log in. To change the login information.00 1534 Error 1535 Error 1536 Error Must specify a user name. All statistics operations (except COUNT) require a field name. Specify the field name to identify which column the result is printed under. If you are saving a new operation. Change the value to a legal integer value. 92 Error Messages Guide . and retry the operation. and click Continue when the prompt warning of duplicate names appears.

You requested that a user command be saved. Error in macro or custom report. you cannot run or edit a macro. Enter a directory to store the command in. However. 1563 Error Chapter 2 Action Request System error messages 93 . specify the name you are updating. An error occurred in this request during a Modify All operation. Fix the problem. No macros are defined. and then click Continue when the prompt warning of duplicate names is issued. The report operation in a macro consists of several commands. The requested user command cannot be located. The macro and custom report files cannot be edited. An associated error message contains details. A common cause is a missing end statement or incorrect formatting of one of the command lines. you did not specify a command to be performed for the operation. Specify the directory to store this user command definition in. 1550 Error 1553 Error 1555 Error 1557 Error 1558 Error 1559 Error 1562 Error Second part of report operation missing or invalid. However. Error in macro or custom report. This is a specific case of Error 1559. You might get this message for the following reasons: The macro or custom report does not exist. and retry the operation. If you are saving an updated command under an existing name. the command was probably deleted after the macro was recorded. Because there are no macros defined.AR System error messages 1549 Error Modify All operation failed during operation on request with ID number. If you are saving a new operation. An error occurred while the system tried to create a user command because the file system could not create or write to the file holding the definition of the operation. Enter a command string to execute. and then save the user command. Define one or more macros before you open the Select Macro or Edit Macros windows. However. You requested that a user command be saved. Rerecord the macro or custom report operation. Enter a command name. An associated error message contains details. All requests with IDs previous to the specified ID (in the sort order) were updated. specify a new name in the name field. It might have been deleted or moved to a new location. Cannot create user command—file system error. An error occurred while the system tried to perform the operation specified in the macro or custom report. and that embedded macro does not exist. You cannot locate the selected command. and all requests with IDs after the specified ID are unchanged. The second part of the command that provides the destination for the report is missing or is not recognized. Or a macro might run another macro as one of the operations it performs. Specify the command you want to be executed when this user command is performed. you did not specify a name for the operation. the command was probably deleted or moved by another user after you started the program. You requested that a user command be saved. The format of the file holding the macro or custom report does not match the expected format. If you are saving a new command. If you are selecting the command interactively. If you are selecting the command from a macro. specify a new name in the Name field. you did not specify a directory in which to store the operation.

To reference a specific Status History value for this form. Define one or more custom reports before opening the Manage Custom Reports window. 1566 Error 1567 Error 1569 Error 1572 Error 1574 Error 1579 Error 1580 Error Missing closing quotation mark on a character string or name. You must supply the ending quotation mark. Define a file name that fits within the size limit. Fix the format of the line. The file specified for this operation is longer than this maximum. OR. including the directory path and the name of the file. You cannot use a selection value name in Status History—you do not have access to the Status field. Unrecognized operation detected while loading a custom report format. and perform the search again. but no corresponding closing quotation mark is at the end of the string. The second part of the command that provides the destination for the statistics result is missing or is not recognized. The error is usually at or just before the marked position. There are no custom reports defined. Empty macro definition. Error in macro or custom report. A parsing error was detected in the search line. or LIKE). File name is longer than maximum allowed. Accordingly. Fix the format of the line. >=. Accordingly. Relational operator expected at this position. You are trying to save a macro that has no commands defined for it. and perform the search again.00 1565 Error Second part of statistics operation missing or invalid. If the name or string contains a quotation mark that is the same type of quotation mark around the value. The only legal operator at this position in a search line is a logical operator (AND. The only legal operator at this position in a search line is a relational operator (=. Fix the problem. use the 0-based selection index for the selection value you require. This error is usually caused by trying to rename a macro as a custom report when the macro contains data other than custom report definition data. The file name specified is too long. An unrecognized operation was detected in the custom report definition. you cannot manage a custom report. Make sure that the correct options are set on the Stop Recording window. Unexpected character at this location in the search line. and perform the search again. A custom report definition can contain only operations related to a custom report. you must double the embedded quotation mark. A field name or character string has an opening quotation mark as required.BMC Remedy Action Request System 7. <=. Usually. <. The maximum size for a file name is 255 characters. You cannot create new item. !=. >. You do not have access to the Status field for this form. An error occurred while the system tried to create the new definition on the Customize View window. You cannot create a macro that does not perform an operation. If they are correct. a lack of system resources causes the error. or NOT). The statistics operation in a macro consists of several commands.5. This is a specific case of Error 1559. Logical operator expected at this position. 1581 Error 1582 Error 1583 Error 94 Error Messages Guide . you did not perform any operations after you started recording. Perform the operations you want to record before saving the macro. An associated error message provides details. No custom report formats are defined. you cannot use a status selection value name as the middle portion of a Status History reference. This message indicates that an error occurred and shows the portion of the string containing the error with a caret marking the location.

1586 Error 1587 Error 1589 Error Format for status history reference is invalid.AR System error messages 1584 Error 1585 Error Field or value expected at this position. Verify the spelling. Status-History. Closing parenthesis expected at this position. Fix the format of the line. In either case. and perform the search again.Fixed. Fix the format of the line. followed by a period.1). A reference must be the name or ID of the Status History field. or you can omit the date and include only the time. A group name specified in the Group List field (ID 104) or Assignee Group field (ID 112) cannot be translated— the name is not recognized as one of the groups defined for the system. You can omit the time portion of a time stamp and include only the date. and spacing of the name to make sure it is one of the legal group names. followed by a period followed by the keyword or index of a user or time reference (for example. the format of the portion of time specified must match the rules for time stamps. When a parameter contains data that expands. The portion omitted defaults to an appropriate value. the maximum expansion of the values is 4096 characters.TIME or 15. capitalization. A closing parenthesis to match an open parenthesis specified in this command was expected at this position. Overflow while expanding active link process (maximum expanded command is 4096 bytes). At this position in a search line. Revise the parameter values that are passed to be fewer than 4096 characters. You cannot translate the group name in the Group List or Assignee Group field. The field referenced in the search line is not a recognized field on the current form. Fix the format of the line. Review the definition to make sure that the correct values are being specified. Fix the format of the line.2. followed by the name or index (0-based) of the status selection value. Overflow occurred while expanding the command line for an active link. Fix the format of the line. and perform the search again. the command line contains more than the maximum of 4096 characters after expansion. Too many nested levels of parentheses in command. This could be the command line for a Run Process action or for a $PROCESS$ operation in a Set Fields action. However. This error often has one of the following causes: Omitting the single quotation marks around a field reference that contains spaces or other special characters Using single quotation marks around a value when double quotation marks must be used Omitting double quotation marks from around a value Specifying an invalid field label Fix the format of the line. and perform the search again. The search operation is too complex—you must have fewer levels of nested operations in it. and perform the search again. The format of a time value is unrecognized. Unknown field referenced in search line. 1590 Error 1592 Error 1600 Error 1601 Error Chapter 2 Action Request System error messages 95 . There are too many open parentheses (maximum of 64 open parentheses active in the search line) at this position in the search line. There must be a balanced number of parentheses in the command. a field reference or value is expected. The format of a status history reference is incorrect. Format of date or time value is not recognized. Overflow occurred while substituting a parameter value for a macro parameter in a Run Macro action for an active link. and perform the search again. and perform the search again. Overflow while expanding active link macro parameter (maximum expanded parameter is 4096 bytes).

Data from these sources cannot be incorporated into a Push Fields source expression. the source expression cannot contain $PROCESS$. To use the Help system under the UNIX environment. Active link trying to set nonexistent field. or remove the active link. 1605 Error 1606 Error 1608 Error 1609 Error 1610 Error 1611 Error Found more entries than expected during workflow processing. 1603 Error 1604 Error Set fields active link running a process failed. Define one or more user commands before you open the Select User Commands window. The character menu for the field is being reset to the default menu for the field. verify that the macro exists.BMC Remedy Action Request System 7. DDE. each of which references 50 or fewer fields in the statistical operations. the specified character menu is not defined. An active link specified a new character menu for a field. You must set the environment variable ARHELP to point to the help directory. You tried to access a macro that is not found in the macro list. Fix the problem. An active link action was extracting data from another form or table in the database and encountered multiple rows that matched the search criteria. This message is usually accompanied by error messages that explain the failure. Cannot find this macro name in macro list. No user commands are defined.00 1602 Error No item matches active link conditions. incorrect. you cannot run or edit a user command. A value exceeded the maximum size of a value that is allowed in a report. it cannot be included in the report. This indicates a corrupted or incomplete definition. this operation has been defined so that no match generates an error. Active link attempting to set nonexistent menu—resetting to the default menu. or SQL. and re-create the report. Unexpected. set the environment variable ARHELP to point to the directory containing the Help files for the AR System. Source used in Push Fields active link not allowed: PROCESS. The process that was run to get a value for a field failed. The administrator configured the action to return an error if no matches were found. or inaccurate definitions were encountered during processing. The statistic operation is too complex—it references more than 50 distinct fields. or divide the report into several pieces. To continue. Because the value will overflow the internal buffers used for reporting. This is usually the directory named help under the AR System install directory.5. The administrator configured the action to return an error if multiple matches were found. 1612 Error 1613 Error 1620 Error 96 Error Messages Guide . Fix the active link to see an existing character menu. $DDE$. or create the character menu needed by this active link. An internal error has occurred during workflow processing. You defined a set of statistical operations for a report that includes more than 50 distinct fields in the reporting criteria. The reporting system supports a maximum of 50 unique fields referenced in statistical operations. An active link specified a new character menu for a field that does not exist. and retry the operation. Fix the active link to see an existing field for the form. An active link action was extracting data from another form or another table in the database and found no rows that matched the qualification criteria. Value exceeded report maximum length. In a Push Fields active link action. An associated error message contains details. Simplify the statistics you are gathering. However. There are no user commands defined. Specify a report that excludes the long field. or $SQL$. Accordingly.

or write to the active link debug file. Unable to read the saved search file. Insufficient memory is available to perform basic BMC Remedy User functions. Servers with versions earlier than 3. The list contains the first 6000 matching items. Unable to read the recent search file.arf files) contain unexpected content. The system cannot save the search file. Click Show Details in the message box for more information. The selection list opened by an active link operation contains more items than can be displayed.0 or later. Only version 3.arv and .0 or later AR System servers can be used by BMC Remedy User version 4. close. Cannot access the active link debug file. Incorrect format in the definition file. A message preceding this message contains details. The system cannot save the recent search file. An error occurred while updating the server. BMC Remedy User version 4. Click Show Details in the message box for more information. Unable to write the recent search file. Reformat your search to continue.AR System error messages 1621 Error 1622 Error 1624 Error 1625 Error 1629 Error 1630 Error 1650 Error 1651 Error 1653 Error 1654 Error 1655 Error 1656 Error 1658 Error 1659 Error 1660 Error Not all entries are displayed in the selection list. Active link debugging is active.0 are not supported by this client. This message appears as a hint in the error message box when a report error occurs. The system cannot read the recent search file. View has not been saved. No report or an incomplete report will be generated. Reporting to an external report writer is supported on the Windows platform only. It usually indicates that the cached form definition files (the . Unable to write the saved search file. This functionality is supported only on the Windows environment. This action is not supported. Try using the advanced search capabilities of BMC Remedy User. An associated message contains details. Login macro action is not supported. Insufficient memory is available to open additional windows or applications. You cannot record a macro that logs in to an AR System server. This message appears when an error occurs during report generation.0 or later tried to connect to a pre-3. Error occurred in generating report. Try using the advanced search capabilities of BMC Remedy User. Reformat your search to continue.0 AR System server. close unwanted windows or applications. An error occurred when the system tried to open. The system cannot read the saved search file. Your window resources are low. for example. you cannot access a form because there are insufficient memory resources to open it. Chapter 2 Action Request System error messages 97 . A macro specified that a report is to be generated to an external report writer. During an export view operation. Too many windows are open. BMC Remedy User generated this error message while loading a form. Close some windows before opening another. an error occurred while the system tried to update the view definition on the server.

0.BMC Remedy Action Request System 7. Insufficient memory to start application. During a Run Process active link action. not all macro statements are supported. In ARWeb 4. During a Run Process active link action. WinExec returned Error 15.5.00 1661 Error One or more items match active link conditions—this operation has been defined so that any match generates an error. Attempted to load second instance of application. Incorrect version of Windows software. Cannot open file fileName. During a Run Process active link action. you must have access to at least one server. 1662 Warning 1800 Error 1801 Error 1802 Error 1803 Error 1805 Error 1806 Error 1807 Error 1808 Error 1809 Error 1810 Error 1811 Error 1812 Error 1813 Error 1814 Error 1815 Error 1817 Error Run Macro was not executed because the macro contains statements that are not supported. 98 Error Messages Guide . Close some open windows or applications. WinExec returned Error 12. While storing a macro or report. WinExec returned Error 5. During a Run Process active link action. Unknown executable format. On the If Action page. Internal error—unable to create form information. To operate BMC Remedy User. Used by the Push Fields action when the administrator configures it to return an error when multiple matches are found. During a Run Process active link action. WinExec returned Error 8. System out of memory. WinExec returned Error 11. WinExec returned Error 2. During a Run Process active link action. WinExec returned Error 19. Invalid executable file format. During a Run Process active link action. BMC Remedy User could not open or create a printer setup file for a custom report. Application designed for different operating system. You cannot create directory directoryName. Path not found. WinExec returned Error 16. If the macro cannot be executed. During a Run Process active link action. BMC Remedy User failed to create a missing command directory on the local disk. Executable not found. WinExec returned Error 10. During a Run Process active link action. this statement is displayed. Unable to connect to any servers. Attempted to load compressed executable. executable file was corrupt. During a Run Process active link action. Application developed for older version of Windows software. WinExec returned Error 14. the If Any Requests Match field has Display ‘Any Match’ Error selected. Make sure that you have a network connection to a server and that it is running properly. Insufficient memory is available to allocate the form information structure. During a Run Process active link action. WinExec returned Error 3. and log in again. WinExec returned Error 0. Sharing or network protection error. or relocation was invalid. During a Run Process active link action.

Internal error (1). The form definition files might be unavailable or corrupt. WinExec failed for actionType. During a Run Process active link action. An MDI child window could not be created because an internal windows function provided an unexpected result that was detected during window creation. An internal Windows error occurred while updating user login information. An MDI child window could not be created because an internal windows function provided an unexpected result that was detected during window creation. Specifically. Specifically. Windows returned an LB error. Form information could not be loaded. This usually indicates a serious Windows error. You entered an invalid field name in the report sort dialog box. Windows provided an invalid LB index. Unable to load Submit form. Unknown error—error code = errorCode. Another error message documents the cause of failure. BMC Remedy User ran out of memory while building the statistics list for the statistics report window. An internal Windows error occurred while updating user login information. Unable to load Customize Default form. The form definition files might be unavailable or corrupt. During a Run Process active link action. The form definition files might be unavailable or corrupt. Memory failure—cannot initialize the current statistics information. WinExec failed. Application requires Windows 32-bit extensions. WinExec returned Error 21. Invalid field name—attempt the operation again. Failed to create the dialog box. Internal error (2). Internal error—invalid window description. Unable to load Customize View form.AR System error messages 1818 Error 1819 Error 1820 Error 1821 Error 1823 Error 1825 Error 1826 Error 1827 Error 1828 Error 1829 Error 1830 Error 1831 Error 1832 Error 1833 Error 1834 Error 1835 Error 1836 Error Invalid dynamic-link library. Failed to display all or some of the notification messages. This usually indicates a serious disk problem. In general. During a Run Process active link action. The form definition files might be unavailable or corrupt. Form information could not be loaded. Unable to load Query form. WinExec returned Error 20. Form information was not loaded. During a Run Process active link action. Internal error—invalid window description. WinExec returned an unknown error code. Chapter 2 Action Request System error messages 99 . BMC Remedy User could not retrieve notification information from the Alert client. Could not create an AR System home directory while updating user login or server information. Failed to create the AR System home directory directoryName. this is because the Alert client is not responding. Form information could not be loaded. This usually indicates a serious Windows error. The status history modeless dialog box could not be created because of a Windows error.

During application startup. The report to file or screen failed to generate. Not enough memory to initialize font. it was detected that Windows is not running in enhanced mode. Internal error—unable to initialize user information. BMC Remedy User could not open the specified report output file. The working directory must be the same as the program path in File > Properties. Report to file failed. BMC Remedy User ran out of memory while building the font preference structure when changing AR System font preferences. This condition is detected during application startup. During application startup. Failed to initialize the user information. BMC Remedy User ran out of memory while allocating the schemaInfo structure during user login. Ensure that you have enough disk space. Error Messages Guide 1856 Error 100 . This usually indicates a serious Windows error.00 1837 Error 1838 Error 1839 Error 1840 Error 1841 Error 1842 Error 1843 Error 1844 Error 1847 Error 1848 Error 1849 Error 1850 Error 1852 Error 1853 Error 1854 Error 1855 Error Failed to create memory.ini file cannot be located. Internal error—unable to create form information. Failed to get printer information. This usually indicates a serious Windows error. Failed to create the user home directory directoryName. Not enough memory to initialize all fonts. The Y location and height of the symbol is greater than 3000. During application startup. and so on) because memory allocations for lists failed.BMC Remedy Action Request System 7. The Y location of a field was made greater than 3000 in the Display Attributes dialog box. A home directory path was not found in the win. Action Request System requires Windows enhanced mode. BMC Remedy User globals could not be initialized. Failed to display the report. reports. During application startup. You encountered an unusual error condition. This usually indicates a serious disk problem. The X location and width of the symbol is greater than 1500. Creation of a home directory for the last user failed during application startup. Unable to register window class. the Windows working directory was not set to the AR System application directory. The X location of a field was made greater than 1500 in the Display Attributes dialog box. BMC Remedy User ran out of memory while building the user information list when updating the login information window. Printer driver initialization for the printer selected in printer setup failed while printing a report. Initialization of the user information in uiroot failed during user login. BMC Remedy User ran out of memory while building the font preference structures during font preference dialog box initialization.5.ini file for the last user logged in to AR System. Failed to initialize the system globals. The user home directory in the ARuser section of the win. BMC Remedy User could not initialize user information lists (macros.

Unable to create frame. You encountered an unusual error condition. You encountered an unusual error condition. You encountered an unusual error condition. You encountered an unusual error condition. You encountered an unusual error condition. This usually indicates a serious Windows error. Unable to register Dialog2 class. Unable to initialize APIs. Failed to initialize DDE. This usually indicates a serious Windows error. You encountered an unusual error condition. Unable to register report window class. Unable to register text viewer window class. You encountered an unusual error condition. Unable to register child window class. The form definition files might be unavailable or corrupt.AR System error messages 1857 Error 1858 Error 1859 Error 1860 Error 1861 Error 1862 Error 1863 Error 1864 Error 1865 Error 1866 Error 1867 Error 1868 Error 1869 Error 1870 Error 1871 Error 1875 Error 1876 Error 1877 Error 1878 Error Unable to register submit window class. Windows API initialization failed during BMC Remedy User startup. Internal Error—LoadIniFile. Unable to register customize view class. You encountered an unusual error condition. Unable to register custom windows class. Form information could not be loaded. BMC Remedy User for Windows failed to load menu accelerator tables during startup. User or password data is incorrect or irretrievable from win.ini file during BMC Remedy User startup. The form definition files might be unavailable or corrupt. Unable to register customize default class. DDE API failed during BMC Remedy User startup. You encountered an unusual error condition. You encountered an unusual error condition. Unable to register queryList window class. Unable to register query window class. Unable to register text view class. BMC Remedy User ran out of memory while allocating the schemaInfo structure during startup. Unable to load the menu accelerators. You encountered an unusual error condition. Form information could not be loaded. Creation of the MDI frame window failed during BMC Remedy User startup. Chapter 2 Action Request System error messages 101 . Internal Error—unable to create form information. Unable to load Submit form: schemaName. Unable to load Query form: schemaName.

The specified item is missing from the DDE target application entry in the dde.ini file while building DDE file specification for a DDE operation. GMT is the time zone from which all other time zones are adjusted. AR System cannot process a time that is out of range. While processing a notification get details DDE request. Date is out of allowed range of 01/01/1970 to 01/19/2038 (GMT) for Windows client. the DDE entry for the target application in the dde.5.ini file while building DDE file specification for a DDE operation. 1891 Error 1892 Error Time is out of allowed range of number and number. using a time within the allowed range. Version currentVersionNumber of MISCDLL.BMC Remedy Action Request System 7. This error also appears for dates that are within the hour that the time changes for the start of daylight saving time. Try again. The DDE application name is not defined in dde.ini. POKE. Blanks and spaces are invalid in a view name.00 1879 Error 1880 Error 1881 Error 1882 Error 1883 Error Failed to connect to application DDEApplicationName using specifiedDDEPath path. A DDE-invoked process failed and did not provide data to be used as the source of a Set Fields active link. Try again. DDE connection failed due to incorrect application file path setting. 102 Error Messages Guide . DDE action other than EXECUTE. the specified item could not be found in the notification application. Memory allocation failure during DDE process. If you enter a date outside of the listed range. DDE Target application entry was not found in the dde. Invalid DDE action specified. Reinstall the latest version of the BMC Remedy User. Error in reading the GetDetails Information for list item number item. This might be the result of installing an older version of BMC Remedy User in the same directory as a newer version. BMC Remedy User ran out of memory while allocating memory to support a DDE action.ini is invalid—you can specify only CSV or TAB for format. The customize view grid width and height parameters are not within the allowed range. AR System cannot process dates and times that are out of range.ini file does not specify CSV or TAB format.ini file.DLL is required. 1890 Error Currently running MISCDLL. using a date and time within the allowed range. Grid width and height must be between 2 and 128. based on Greenwich Mean Time (GMT).DLL version oldVersionNumber is an old version. or REQUEST DDE action was specified. Set Fields active link running a process through DDE failed. 1884 Error 1885 Error 1886 Error 1887 Error 1888 Error 1889 Error The item item is missing from application section section in dde. The format for the application section in dde. you receive this error message. No description. While reporting to an application. Date and time are out of allowed range of number through number.

An error occurred while loading the starting active link for an entry point guide.C. Error generating application list field content. An error occurred while generating the Crystal report: CrystalReportsError. Contact your AR System administrator.CrystalReportsError. errorNumber . Contact your AR System administrator for assistance. The Home Page form name specified on the Home Page tab of the Options dialog box in BMC Remedy User or on the Home Page tab of the AR System User Preferences form cannot be found. the Primary Allowable currency type is used.C. 9999. A date value was entered that is out of range. or contact your AR System administrator for assistance.AR System error messages 1893 Error 1894 Error 1896 Error Cannot perform this operation in the current mode of the form. See your Crystal Reports documentation for more information. The system is out of memory or resources while running active links. The specified currency value is a not an allowable currency type. Terminate unused applications to make system resources available. The system is out of memory or resources. The entry point chosen from File > Recent Entry Points and the form or guide is no longer a valid entry point. An invalid ODBC data source was found. Verify that you entered a valid AR System server and form name in your BMC Remedy User options. See your Crystal Reports documentation for more information. Contact your AR System administrator. Error generating navigation bar field content. Report to file failed. to January 1. or an error occurred when connecting to the specified ODBC data source. You have entered an improperly formatted value for a currency field. entryPoint is not a valid entry point. Please verify your user preferences or check with your administrator.E. Failed to create the window. Could not create a new child window.01/01/9999 A. A currency value was created with an incorrect format. An error occurred while generating the dynamic content for the Application List field. Ensure the directory does exist. Try again with a different mode of the form. This is a Crystal Reports Engine exception. 1897 Error 1898 Warning 1899 Error 1900 Error 1901 Error 1902 Error 1904 Error 1905 Error 1906 Error 1907 Error 1908 Error 1925 Error Cannot retrieve starting active link: activeLinkName. There might be a resource or memory limit on the client. Date fields can accept values from January 1. 4713 B. You have entered an invalid currency type. An error occurred while generating content for the navigation bar field. You can enter the currency decimal value and currency code directly into the field.ODBC data source: source. AR System cannot perform this operation in the current mode of the form. Date is out of allowed range of 01/01/4713 B. or enter the decimal value and select a currency code from the list. . If you specify only a decimal value. Chapter 2 Action Request System error messages 103 . There is no Home Page form available. numberString .D.

The failure usually indicates an incorrectly installed mail system. the menu did not load. Writing to a file failed in the field editor. 1966 Error 104 Error Messages Guide . Failed to initialize MAPI mail. This is usually caused by the failure to create a temporary file. these two functions cannot be evaluated correctly. Error loading menu. The application resource memory area is probably full. Character menu expansion failed in the symbols library. Unable to create work buffer for file fileName. the menu did not load. You cannot close all windows. Failure loading group information. The number of items returned for a menu load exceeded the maximum allowed. Group list expansion failed while the system tried to build the group list. BMC Remedy User failed to get the group list from the server. Failed to build the Windows popup menu. The login was aborted because all open windows could not be closed. Unable to read file fileName. Allocation of global memory failed while performing edit operations. Failure trying to expand character menu. Indicates a serious problem with menu loading. Error getting group information. Cannot commit changes to a dialog box or to a submit or a modify record action. Functions MAX and MIN are not supported in Push Fields actions. Unable to commit changes. Cannot write file fileName to disk. Character menu expansion failed in the symbols library. The field editor could not open a file with write permissions. Login aborted. Windows Help system failed to load. Push Fields actions provide little information about the destination field. Functions MAX and MIN are not supported in Push Fields actions. Error creating menu—out of resources. Unable to load help. This is often caused by a lack of space in the Windows resource heap when loading large menus. The field editor could not open a file with read permissions.5. Without knowledge of the destination data type. Adding a submenu to a menu failed and resulted in a Windows error. The MAPI mail system failed to initialize when sending an AR System object to a mail recipient. Error creating a menu—menu too large. This usually indicates a serious Windows error. Unable to load menu. You are trying to access a menu with more than numberOfEntries entries—the menu will be truncated. Unable to write to file fileName.00 1926 Error 1930 Error 1950 Error 1951 Error 1952 Error 1953 Error 1954 Error 1955 Error 1957 Error 1958 Error 1959 Error 1960 Error 1961 Error 1962 Error 1963 Error 1964 Error 1965 Error Unable to initialize frame. Creation of the main MFC frame failed during BMC Remedy User startup.BMC Remedy Action Request System 7.

The report type is being reset to Record mode. Verify the printer setup on your system. only the first number entries are reported. Report will not be displayed in specified external program because of the following error: errorType. This is usually caused by problems with your printer setup or with cables. The message was not sent. The MAPI mail system failed to send the mail when sending an AR System object to a mail recipient. The directory specified in a file path is invalid. For example. A printer error occurred. The directory cannot be created. The given directory does not exist in the search path. The Crystal Report Engine returned less data than requested. An I/O error occurred while generating a report to file. The report format is reset to Record. 1976 Warning 1977 Error 1978 Warning 1979 Error 1980 Error 1986 Error 2001 Error The given directory does not exist. Page setup could not be determined. an active link failed on window close. you entered 1. The SQL command passed to the Crystal Reporting Engine is invalid. Crystal Reports) during the print preview operation. One or more active links failed when closing the form. Do you still want to exit the application? When exiting BMC Remedy User.AR System error messages 1967 Error 1968 Warning 1969 Error 1970 Warning 1971 Error 1972 Error 1973 Error 1974 Note 1975 Error Send Mail failed. Failed to save file fileName. Due to the length limit of the SQL command by Crystal Reporting Engine. This note gives the user a chance to abort BMC Remedy User termination. The directory specified while saving a macro cannot be created. so printer defaults are being used. Too many columns (fields). In general. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. Printer error occurred. A report cannot be printed. The directory might not exist or the user may not have access rights.00 USD. The Crystal report contains an invalid SQL statement. Verify the syntax in the SQL command. You have entered an improperly formatted value for a currency field. Add the new directory? The directory specified does not exist. Ensure that all column titles fit into one report line. The system encountered an error during a call to allocate memory. The specified directory is not valid. There was a failure opening an external viewer (for example. this error occurs when too many processes are running or when some processes grow to occupy most or all available memory on the client. Cannot allocate memory. Chapter 2 Action Request System error messages 105 . This is likely caused by a file system error. The default page setup is used. You entered an invalid currency value on a currency field. Too many fields were selected in a Column type report. Create the new directory? The directory specified while saving a macro does not exist.

but that field number is within the range of reserved fields (100 to 536870911) in AR System. or the permission settings are such that you cannot access it. No window system is running in your environment. The UNIX configuration file (config) is missing. Failure while retrieving entries from the server directory file. If you did not use the -x command line option or are using Windows. /etc/ar (UNIX) or \ARHomeDir\ar (Windows). and then restart the aradmin program. No servers are currently accessible. This means that there is nothing to import. None of the servers specified in BMC Remedy Administrator are accessible. The import operation in BMC Remedy Administrator is used for structure definitions only. BMC Remedy Administrator cannot start without a server to connect to. If you do not want to create a specific reserved field. the AR System directory file is empty or contains references to inaccessible servers. If you cancel. and retry the operation. The aradmin program (BMC Remedy Administrator) on UNIX is an X program. You can create a field in this range. If you are creating this field to have the special meaning. You are deleting a filter. Start a windowing system. choose an ID outside of the reserved range (greater than or equal to 536870912). but be aware that the field might have a special meaning. and make sure that the field exists for the target form. Fix the problem. 2003 Error 2004 Error 2005 Error 2006 Error 2009 Error 2100 Error You have specified a field ID within the reserved range. 106 Error Messages Guide . and restart the tool. the system could not connect to any of the specified servers.00 2002 Error Cannot read the configuration file. the system could not find a field with the specified name for the current form. the tool did not find any AR System structure definitions in the file. It requires that an X windowing system be running to allow the program to operate.BMC Remedy Action Request System 7. ignore this message and proceed. Make sure that ARHOME is correctly set and that you can read and write to the config file. and then restart the tool. On UNIX. Failure occurred during a call to initialize AR System client environment. An associated error message contains details. Fix the problem. The error might have been caused by an inability to allocate memory to hold the list of servers found or by an inability to find or open the directory file. A Delete operation removes the definition and the workflow associated with the definition. Fix the spelling of the field name in the reference. No servers are specified on the command line or in the AR System directory file. If you proceed. Associated error messages provide information about why the tool could not connect. the operation is terminated. 2102 Error 2103 Error Incorrect parameter specification—verify field name spelling.5. No structures are in the import file. the definition is removed. If you are running BMC Remedy Administrator. An error occurred while the system retrieved entries from the server directory file. When specifying a field reference using the field name. You cannot connect to the X server. and the definition is retained. You cannot initialize the AR System. You specified a file to use during an Import operation. You tried to assign an ID number to a form field. use BMC Remedy Data Import. When trying to load this file. if you used the -x command line option to identify one or more servers. If you are trying to import data. leave the field ID blank to automatically generate an available ID outside the reserved range. Make sure that you specified the correct name for the file you are trying to import. 2101 Error Your filter definition and all associated actions will be deleted.

AR System error messages

2104 Error

You have not saved changes on this screen—they will be lost if you continue. You made one or more changes on the current window after changes were applied. You are now trying to close the window. If the window is closed, all changes after the last Save will be lost. Click Cancel to cancel the dismiss action and retain the window and its information. This server serverName is not licensed from BMC and has limited capabilities. For unlimited capabilities, contact your BMC sales representative or visit http://www.bmc.com. The server reported an invalid license during login verification. Your form definition and all associated data will be deleted. You are deleting a form. A delete operation removes the definition, the workflow associated with the definition (such as filters and active links), and all data associated with the definition. If you proceed, the definition will be removed. If you cancel, the operation will be terminated, and the definition will be retained. Your active link definition and all associated actions will be deleted. You are deleting an active link. A Delete operation removes the definition and the workflow associated with the definition. If you proceed, the definition will be removed. If you cancel, the operation will be terminated, and the definition will be retained. Language defined by LANG environment variable not recognized—using default on server. The language defined in the LANG environment variable is not recognized by AR System. The default language of the server is used instead. The following field labels are duplicated in your form. The field labels identified in the message are used for multiple fields on the form. Because fields are uniquely identified by field ID, duplicate labels are allowed. Because it can be confusing to have fields with duplicate labels, consider changing one of the labels. Changes on the following screens will be lost if you continue. After changes were last applied, you made one or more changes in a child window of the current window. A request was made to close or dismiss the parent window. If the window is dismissed, all changes after the last Save will be lost. Click Cancel to cancel the dismiss and retain the current window, its children, and their information. Your menu definition will be deleted. You are deleting a character menu. A Delete operation removes the definition. If you proceed, the definition will be removed. If you cancel, the operation will be terminated, and the menu definition will be retained. The following fields (including data), active links (or both), will be deleted. You requested that one or more fields or active links be deleted. The affected fields and active links are listed as part of the message. Deleting fields deletes the associated data for the fields and requires restructuring the table in the database. Deleting active links removes the workflow associated with the active link. Proceed with the Delete operation to continue. Click Cancel to stop the Delete operation from being performed. Additional errors were truncated. The operation encountered a number of errors—too many errors to fit in a single dialog box. The most critical errors are displayed in the current dialog box. Fix the problems, and repeat the operation to find out whether the other errors remain. Your filter action will be deleted. You are deleting a filter action. A Delete operation removes the action definition. If you proceed, the action definition will be removed. If you cancel, the operation will be terminated, and the action definition will be retained.

2106 Error 2107 Error

2109 Error

2112 Warning 2114 Warning

2115 Warning

2117 Warning

2119 Warning

2120 Note

2121 Warning

Chapter 2 Action Request System error messages

107

BMC Remedy Action Request System 7.5.00

2122 Warning

Your active link action will be deleted. You are deleting an active link action. A Delete operation removes the action definition. If you proceed, the action definition will be removed. If you cancel, the operation will be terminated, and the action definition will be retained. Your form view will be deleted. You are deleting an administrator view of a form. A Delete operation removes the view definition. Users using this view are reset to the default view the next time they connect to the system. If you proceed, the view will be removed. If you cancel, the operation will be terminated, and the view will be retained. Your form view name is not unique. The name of an administrator view must be unique for the form. Another view exists with the same name. Choose a unique name for the view. You currently have an escalation time specified. You are changing the timing setting for an escalation from calendar to interval, and a calendar screen is open on the system. The calendar screen is inappropriate when an interval time setting is used. This prompt enables you to cancel the operation or to close the open window. The full text search (FTS) reindex operation can take a long time. Do you wish to continue? You selected the full text search (FTS) reindex operation. FTS search capability will be disabled while the operation is in progress. Because this operation can take a long time and performance of the system might suffer, perform reindex operations during off hours whenever possible. Your escalation action will be deleted. You are deleting an escalation action. A Delete operation removes the action definition. If you proceed, the action definition is removed. If you cancel, the operation is terminated, and the action definition is retained. Your escalation definition and all associated actions will be deleted. You are deleting an escalation. A Delete operation removes the definition and the workflow associated with it. If you proceed, the definition is removed. If you cancel, the operation is terminated, and the definition is retained. You are logged in as a subadministrator—access to some structures and functions has been disabled. You are logging in to the system as a user who is a subadministrator. A subadministrator does not have access to all functions on the tool. If you are not allowed to perform a specific operation, you probably do not have sufficient permissions. You can log in as an administrator to get full access.

2123 Warning

2124 Warning 2126 Warning

2127 Warning

2128 Warning

2129 Warning

2130 Warning

2131 Warning 2132 Warning 2133 Warning 2134 Warning

Incompatible data types in qualification line. The data types of a pair of values in a qualification line are not compatible. In the qualification line, make sure that operations are performed only between items with compatible types. Full text search (FTS) index operations will be started. You activated the full text search (FTS) subsystem of AR System. Items that are pending indexing begin indexing immediately. Full text search (FTS) index operations will be shut down. You are deactivating the full text search (FTS) subsystem of AR System. All operations that require updating the FTS index are queued and performed when the system is reactivated. You must be a member of the Administrator or Subadministrator group with a fixed license to use this tool. Administrative functions in AR System require a user who is a member of the Administrator group (with full functionality) or Subadministrator group (with limited functionality). The user must have a fixed write license. The user trying to get access does not meet these criteria.

108

Error Messages Guide

AR System error messages

2135 Error

The selected distributed mapping will be deleted. You are deleting a distributed mapping. A Delete operation removes the mapping definition. If you proceed, the definition is removed. If you cancel, the operation is terminated, and the definition is retained. The selected pending mappings will be deleted. You selected one or more pending mapping definitions to delete. A Delete operation removes them from the set of operations to perform. The distributed operation that was initiated against these items is removed. If you cancel, these items are retained. Changes on the mapping fields screen will be lost if you continue. You made one or more changes on the current window after changes were applied. A request was made to close or dismiss the window. If the window is dismissed, all changes after the last Save are lost. Click Cancel to cancel the dismiss and to retain the window and its information. You are attempting to delete a Distributed Server Option (DSO) form or field—do you want to continue? The form you are deleting is a special DSO form. Deleting the form might affect the functionality of DSO. When you restart the system, the server automatically re-creates the form. If you are deleting a field, the field is a field that makes the current form a DSO form. Deleting this field makes this form unavailable as a DSO form. When the system is restarted, a new form that contains all the distributed fields is created.

2136 Warning

2137 Warning

2138 Error

2139 Warning 2140 Error

Changes in current view will be saved if you continue. You are changing views without saving your changes to the current view. If you continue, your changes are saved automatically. Other forms depend on the current form. Deleting this form will cause forms that depend on it to be deleted. Are you sure you want to continue? The form you are deleting is a base form for one or more join forms. Because join forms are dependent on this form, all such forms are deleted if you delete the base form. Continue only if you want all dependent forms to be deleted.

2141 Warning 2142 Warning 2143 Warning 2144 Warning

The following field names or IDs have blank labels in your form. You applied changes to a form that contains one or more fields with blank labels. Your guide will be deleted. You are deleting a guide. If you proceed, the guide is removed. If you cancel, the operation is terminated, and the guide is retained. Your application will be deleted. You are deleting an application. If you proceed, the application is removed. If you cancel, the operation is terminated, and the application is retained. Your packing list will be deleted. You are deleting a packing list. But because a packing list is really only a container of AR System objects, if you proceed, deleting the packing list does not delete any underlying forms, workflow, and so on, that are in the packing list. If you cancel, the operation is terminated, and the packing list is retained. Your web service will be deleted. You are deleting a web services object. If you proceed, you delete only the AR System web service object and not any underlying XML schemas or WSDL handler URLs. If you cancel, the operation is terminated, and the web service is retained.

2145 Warning

Chapter 2 Action Request System error messages

109

BMC Remedy Action Request System 7.5.00

2146 Warning

This view contains one or more intersecting FORM declarations. Any FORM tags inserted by the user must not overlap on the open and close service tags. You added a form to an existing web view between open and close services and are trying to save it. A limitation of the authoring environment does not allow nested or intersecting FORM declarations. Open and close services are the start and end of a form, respectively. The authoring environment checks to make sure that this situation is brought to the attention of the user.

2148 Warning

System does not ensure consistency if global elements/complex types in use are changed. Please choose 'embedded' option if you are not sure. This warning is returned when you select the Linked option from the Advanced Properties dialog box after clicking the Options button in the Web Service tab. Proceed at your own risk. The system does not guarantee any consistency.

2149 Warning 2200 Error

'Public' access is not specified. This will force users to login before accessing wsdl. This warning is returned when you do not have access to that web service and you try to save a web service without public permissions. You cannot allocate memory. The system encountered an error during a call to allocate memory. In general, this error occurs when there are too many processes running or when some processes have grown to occupy more, or all, of the available memory on your client computer. You can recover that memory by shutting down unneeded processes. Additionally, restart processes that have been running for a while to help recover space those applications might have leaked over time. Only integer can use numeric text type. While defining properties for a field, you tried to assign the field type Numeric Text to a field other than an integer field. Only fields with the data type Integer might be of numeric text type. Only selection type can use check box. While defining properties for a field, you tried to put check boxes on a field other than a selection field. Only fields with the data type selection can use check boxes. Unrecognized field type. Incompatible data types in qualification line. The type specified for the field is not recognized. Update the definition of the field to indicate a valid display type for the field. Set Up Search Database command failed during Import. BMC Remedy Administrator failed to import the required forms while setting up the Search database. This error can occur if a server exits unexpectedly or fails to import because of some other server-related cause. Verify the server status, and retry the Set Up Search Database command. You can not perform Synchronization of Search databases for same or different servers at the same time from the same instance of the BMC Remedy Administrator. More than one Sync Search Database command cannot be issued from the same instance of BMC Remedy Administrator. Open another session of BMC Remedy Administrator to perform these operations simultaneously.

2202 Error 2203 Error 2205 Error 2206 Error

2207 Error

2208 Error

Could not load the definition file from the resource. The definition file of the search database in BMC Remedy Administrator did not load. Close and reopen BMC Remedy Administrator before you retry the operation. If the error persists, contact Customer Support. Field fieldName has a duplicate name. Please select a unique name for this field before saving the form. All other changes are not saved. This form cannot be saved because two or more fields have the same database name. Make sure that each field has a unique database name, and resave the form.

2209 Error

110

Error Messages Guide

AR System error messages

2214 Error

You cannot open the export file. The file specified to receive the exported definitions cannot be opened by the tool. This error can be the result of an access problem or of a nonexistent directory. An associated error message contains details. Fix the problem, and retry the operation. Form definition problem: invalid field specification. An error occurred while the system tried to build the GUI structure to represent a field on a screen. An associated error message contains details. Button field is missing an active link assignment. This compatibility error occurs when you use a 3.0 (or later) UNIX Administrator Tool or BMC Remedy Administrator to connect to a pre-3.0 server. In the pre-3.0 AR System, all buttons in a form must have an assigned active link. You cannot open configuration file. An error occurred while the system tried to open your configuration file. An associated message contains details. Fix the problem, and repeat the operation. X or Y (or both) coordinates are out of range. The X or Y coordinates you specified for the layout of a form field are not in the valid range. The range for the X coordinate is 0 to 1500. The range for the Y coordinate is 0 to 3000. Change the coordinate to a valid range. Enter a form name. Specify the name of a form so you can complete the specifications for the window. Enter a user name. Specify the name of a user so you can log in. Enter a name, and click Save. Cannot query servers. An error occurred while the system tried to retrieve the list of forms available to the new user. The system could not connect to the servers. An associated message contains details. A selection is required. To perform an import or export operation, select one or more items to be imported or exported. You cannot open the specified file. An error occurred while the system tried to open a file. An associated error message contains details. Fix the problem, and retry the operation. Select an item. No field or active link is selected on the window; therefore, you cannot select the Delete operation. To delete a field or active link, select the item, and click Delete. Cannot delete the selected item from the list during a cut operation. An internal error occurred while the system tried to remove an item from an internal list. Exit the tool, and restart the tool. No data entered at selected menu level. No menu definition exists at the selected level in the menu. Save all work on the current window, and exit the window. The error message should be dismissed when you reopen the character menu definition. You must enter a label before selecting Insert or Modify. You must enter a label for a menu item that you are creating prior to selecting Insert or Modify. Enter a label, and reselect the desired operation.

2219 Error 2220 Error

2228 Error 2231 Error

2232 Error 2234 Error 2236 Error 2241 Error 2243 Error 2269 Error 2279 Error 2281 Error

2283 Error

Chapter 2 Action Request System error messages

111

BMC Remedy Action Request System 7.5.00

2284 Error

No data entered at previous menu level. No menu definition exists at the previous level in the menu. If you receive this message, save all work on the current window, and exit the window. The error message should not be displayed when you reopen the character menu definition. Enter a filter name. You did not enter a name, which is required, for the filter you are creating. Enter a name, and click Save. The message number is invalid. When creating a message type action, the message number is outside of the allowed range. User messages have message numbers of 10000 or greater. Fix the message number, and click Save. You must select a form. You did not specify a form for the structure you are creating. You must specify the form to which the structure is attached. You must select at least one operation. You did not specify an operation for the filter or escalation to execute. You must specify one or more operations. Select an operation and click Save. Missing closing quotation mark on a character string or name. When a line was parsed, an open quotation mark was found, but no corresponding closing quotation mark was found. Review the string for the missing quotation mark. If a quotation mark is contained within a string, you must double the contained quotation mark. Unexpected character found. When a line was parsed, an unexpected character was found. An associated message contains information about the position within the line where the unexpected character is located. A conditional operation expected at this position. When a line was parsed, a conditional operation was expected but not found. An associated message contains information about the position in the line where the operation was expected. A relational operation expected at this position. When parsing a line, a relational operation was expected but not found. An associated message contains information about the position within the line where the operation was expected. A field or value expected at this position. When a line was parsed, a field or value reference was expected. An associated message contains information about the position in the line where the field or value was expected. Too many nested levels of parentheses in command. When parsing a line, the system supports a maximum of 64 levels of nested parentheses. The string being parsed has more than 64 levels of nested parentheses. A closing parenthesis expected at this position. When a line was parsed, a closing parenthesis was expected. An associated message contains information about the position in the line where the parenthesis was expected. Unknown field reference found. When a line was parsed, a reference to a field was found, but it could not be translated to a known field for the current form. Make sure that you used the correct type of quotation marks (for example, you might have placed a single quotation mark around a value that should have included double quotation marks). The message contains information about the position in the line where the field reference is located.

2285 Error 2286 Error 2287 Error 2288 Error 2290 Error

2291 Error 2292 Error 2293 Error 2294 Error 2295 Error 2296 Error 2297 Error

112

Error Messages Guide

Specify an execution order greater than the current filter so the new actions run after the existing actions. An associated message contains information about the position in the line where the selection value is located. The format is controlled by the default LANG setting and can be overridden by using the ARDATE environment variable. If you do not want to specify data. create a new filter with the same conditions. and enter only the appropriate parameters. Fix the problem. To perform additional actions. Resulting file name is longer than maximum allowed. 2299 Error 2300 Error 2301 Error 2304 Error 2305 Error 2306 Error 2308 Error 2309 Error 2310 Error 2311 Error 2312 Error 2313 Error Chapter 2 Action Request System error messages 113 . A selection field requires that one or more values be specified. A name is required. While an item was being removed from the menu. Specify a directory and file name. The error should be gone when you reopen the character menu definition. Specify an execution order greater than the current active link. an internal error occurred.AR System error messages 2298 Error Value specified for selection not one of defined values for this field. Selection fields require one or more values. and exit the window. A filter can contain a maximum of 25 actions. create a new active link with the same conditions. The function definition contains more parameters than are allowed. You must select a form. For example. You did not specify a name for the active link you are creating. Enter an active link name. and add actions in the new active link. and click Save. Review the definition of the function. Specify both. You have created the maximum number of filter actions allowed. select Dismiss to skip this action. so the new actions run after the existing actions. Enter a name. on a Set Fields window. The file name specified is longer than the maximum file name supported by the system (up to 255 characters). No data is entered on the current screen. An associated message contains information about the position in the line where the function with the extra parameters is located. and add actions in the new filter. Make sure that you specified the required information in the fields you are assigning. Character menu Delete operation failed. You must specify a directory and file name to open a file. You must specify the form to which the active link is attached. The field is not fully defined until it contains one or more values. You did not specify a form for the active link you are creating. You have created the maximum number of active link actions allowed. You are already at the maximum number of actions allowed. a specified value for a selection field was determined not to be one of the legal values for the field. save all work on the current window. and retry the operation. Format of time value is not recognized. You have entered too many parameters in a set fields assignment. Please enter data. Error encountered writing to file. and click Save. An associated error message contains details. When a line was parsed. The format of the specified time value is not recognized. An error occurred while the system tried to write to a file. An active link can contain a maximum of 25 actions. To perform additional actions. If you receive this message. specify one or more fields to receive a value. You are already at the maximum number of actions allowed.

If you are using BMC Remedy Administrator. and continue with the operation. The internal field length may not be less than zero. and a legal ID is automatically created. You cannot create a new field with an ID less than 100. Qualification line error at position location. The execution condition requires that a field be selected to attach the operation of the active link to.00 2314 Error Select a field for your Execute On condition.5. You must specify one or more occasions for active link execution. Select an execution condition. Fix the problem. an error occurred. Fields in this range are reserved for the core fields that are created and managed automatically by the system. 2315 Error 2317 Error 2319 Error 2320 Error 2321 Error 2322 Error 2323 Error 2324 Error 2325 Error 2326 Error You have specified a field ID already in use. You did not specify when to execute the active link. This message contains information about the position of the error in the line. You have entered a nondigit character for a numeric field. While parsing a qualification line. The ID for every field must be unique. The system default connects to the first server listed in your configuration file. The length specified by a character field must be greater than or equal to zero. This message contains information about the position of the error in the line. Use the ARPATH environment variable to point to alternate locations for macro definitions. The arithmetic operation specified is illegal in the current context. you can use those field IDs for fields with compatible definitions. The one exception to this rule is the set of six fields that were core fields in the initial release of AR System (but are no longer core fields). 2328 Error 2329 Error There are no administrator macros defined. Your configuration file registered that you were last connected to a server to which you no longer have contact. This is required when you execute on Return or on Menu Choice. and click Save. While parsing an assignment line. When the contents of a Group List or Assignee Group field was parsed. You specified an ID in use by another field. Change the ID to be unique. Assignment line error at position location. You have entered an improperly formatted value for a real field. you can leave the field ID blank for the new field. Unrecognized group in group list.BMC Remedy Action Request System 7. an unrecognized group name was found. Error Messages Guide 114 . Unrecognized arithmetic operation. Select an execution condition for your active link. The value entered where a real value is expected is not in legal format for a real value. and click Save. Make sure that the macro you want to run is defined. Integer and real fields can contain only digits (except for real values in legal scientific notation). Real values can include a single decimal point or can be in scientific notation. Field IDs below 100 are reserved for core fields. Select a field to attach to. Re-enter the value in one of these formats. and click Save. or group list longer than maximum allowed. There are no macros available to the administrator for creating a macro-type action for an active link. You do not have a known server specified in your configuration file—the tool will default to the first server specified in your directory file. For compatibility. or the total length of the field exceeds 255 bytes. an error occurred. An integer or real field contains a nondigit character.

You cannot change type of an existing action. Review the definition stored in the database. The values specified for a selection type field must be unique. Review the documentation for the expected format of the DDE line. but they cannot be nested more than 15 levels deep. and correct the line. escalation. One of the field names is invalid. the maximum number of nested levels of macros is 15. Create at least one If action. Total width of your fields exceeds the maximum. The total width of all the fields specified for Get List fields is greater than the maximum of 128. You did not specify a form for the filter you are creating. Change the value to be in the legal range. The ID specified for the field is outside the legal range of field IDs. You specified two or more values that are the same. You must specify a valid macro definition. Delete operation failed. therefore. The macro specified is not in the correct format and is. An error occurred while the system tried to format the change history information for the structure. Too many levels in nested macro. Invalid macro definition file format. An error occurred while performing a Delete operation. You can change other aspects of the definition. You must select a form. If you are using BMC Remedy Administrator. Selection values must be unique. You must specify the form to which the filter is attached. The macro you are using has more than 15 levels of nested macros. An error occurred while the system tried to retrieve and build the indicated menu for the specified field. You cannot expand menu menuName for field fieldName. 2332 Error 2334 Error 2335 Error 2336 Error 2337 Error 2338 Error 2339 Error 2340 Error 2341 Error 2342 Error 2343 Error 2345 Error Chapter 2 Action Request System error messages 115 . or active link. as needed. and a legal ID is automatically created. There are no If actions defined. Verify the spelling of the names to make sure that you specified legal fields. to be within the maximum width of 128 bytes. You must specify at least one If action. but the change history is unavailable. If a macro nests to include other macros. The field ID is illegal. No If actions were defined for the filter. The format of the DDE assignment line used in a Set Fields operation is invalid. Invalid parameter specification in the DDE assign line. An associated message contains additional information. unrecognized. An associated message contains details. You must delete the existing action and create a new one. You can run the macros one after another in the same macro. The system cannot tell the difference between the identical values.AR System error messages 2331 Error An error occurred while formatting your diary text. One or more of the names specified in the Get list or Index list is not a valid field name for the current form. you can leave the field blank. Review the width specified for each field and the width of the separators and adjust. You cannot change the type of an existing action.

BMC Remedy Action Request System 7.5.00

2348 Error 2349 Error 2350 Error

Field data type and assignment data type are not compatible. A value with an incompatible data type that cannot be converted was assigned to a field. You must specify a value with a compatible (or at least convertible) data type. You have entered a value in your integer field that is outside of the legal range for integers. The value for an integer field is outside the range for a 4-byte integer value. Enter a value within the legal range for a 4-byte integer. Duplicate mapping name—rename your distributed mapping. While creating a distributed mapping, you assigned the mapping a name already used by another mapping. Mappings must have unique names. Return to the Modify Distributed Mapping window, and rename the mapping. Invalid mapping definition—respecify your custom mapping. The tool could not decode the mapping definition for the custom mapping. The format of this definition was manually changed, or there is a problem in the database with the storage of definitions. Re-create the custom mapping. One of your mapping servers is not available or does not exist. Because the server specified as the source or the target of the mapping is unavailable, the system cannot retrieve the list of forms that are on this server for menus (or a list of fields that are in a form) for a custom mapping specification. To specify a custom mapping or to view a menu of forms, wait until the server is available again. You do not have permission to perform Distributed Server Option (DSO) operations. You are connected to the system as a subadministrator, and you do not have access to the Distributed Mapping form to allow definition of Distributed Mappings. You must be an administrator or be given sufficient access by an administrator to create and modify distributed mappings. You have not entered data for any of your fields—enter data for at least one field before clicking the Save button. The Set Fields action is not defined to assign values to fields. Specify the assignment of one or more fields.

2351 Error

2352 Error

2353 Error

2354 Error

2355 Error 2356 Error 2357 Error 2358 Error 2359 Error 2360 Error 2361 Error

An active link already exists in this form with the name: activeLinkName. An active link with the same name already exists. The names of all active links must be unique. Change the name of the active link so that it is a unique name. You have entered a value in a real number field that is outside the valid range for real numbers. The value in a real field is outside the range for an 8-byte real value. Enter a value within the legal range for an 8-byte real field. Get operation failed. An error occurred while the tool tried to retrieve a property from a field. Set operation failed. An error occurred while the tool tried to set a property for a field. number is not a valid number for the date date. The number must be between number and number. This is an out-of-range error. For example, the message is displayed if you entered 1/1/2075 as a date. name is not a recognized monthOrDay. This message is displayed if you misspell a month or day name. name is not recognized as a legal component of the date or time format string. This message is displayed if the format string you specified in the Control Panel is illegal.

116

Error Messages Guide

AR System error messages

2362 Error 2365 Error

Date is out of allowed range of 01/01/1970 to 01/19/2038 (GMT) for Windows Client. If you enter a date outside the listed range, you receive this error message. GMT is Greenwich Mean Time, the time zone from which all other time zones are adjusted. The table field tableFieldName definition is corrupt. If you Save the form, you will delete this field. The table field did not find a field ID referenced by a column in the table field. The qualifier for the table field might be improper. If you proceed, the column representing the field ID is removed from the table field. See the Form and Application Objects Guide for more information about table fields. Table field tableFieldName has no columns. Add at least one column before you create or modify this table field. Table fields must have at least one column. See the Form and Application Objects Guide for more information about table fields.

2366 Error

2369 Error

The listed columns for the tableFieldName table field do not have corresponding data fields. One or more columns in a table field do not match field IDs in the corresponding form. All columns with no matching field IDs are removed from the table field when the table field is modified. See the Form and Application Objects Guide for more information about table fields. Form formName on table field tableFieldName does not exist on server serverName. The form was deleted from the AR System server. For more information about table fields and forms, see the Form and Application Objects Guide. For more information about servers, see the following AR System documentation: Configuration Guide Optimizing and Troubleshooting Guide Database Reference

2370 Error

2371 Error 2372 Error 2373 Error

Enter an application name. You tried to save an application without providing a name. Enter an application name before you save the application. Unable to save an image for the application. This message occurs when you select an invalid file type for the image you want to associate with an application. Valid file types include .bmp, .jpeg, .jpg, and .dib. Server serverName for table field tableFieldName is not accessible at this time. The table field tried to connect with the listed server, but the AR System server is not running. Try again later. For more information about servers, see the following AR System documentation: Configuration Guide Optimizing and Troubleshooting Guide Database Reference

2374 Error 2380 Error

Duplicate distributed mapping name. This message appears when you try to save a distributed mapping with an existing distributed mapping name. Change the name of the new mapping or delete the existing mapping. Page or Page Holder field cannot be set to a NULL Field ID. You cannot set the Database ID of the Page or Page Holder fields to a NULL value. You must supply a non-NULL value for the Database ID.

Chapter 2 Action Request System error messages

117

BMC Remedy Action Request System 7.5.00

2381 Error

Error getting active links list. The error occurs when BMC Remedy Administrator is unable to complete an operation because it failed to obtain an active links list from the current server. Close the dialog, and retry the operation. Error getting filter list. The error occurs when BMC Remedy Administrator is unable to complete an operation because it failed to obtain a filter list from the current server. Close the dialog, and retry the operation. Error getting escalation list. The error occurs when BMC Remedy Administrator is unable to complete an operation because it failed to obtain an escalation list from the current server. Close the dialog, and retry the operation. The application state system form could not be found on the queried server. The AR System Application State form was not found. Restart the AR System server, which recreates the form if necessary. The application roles system form could not be found on the queried server. The Roles form was not found. Restart the AR System server, which re-creates the form if necessary. The application roles system form did not contain any state fields. No state fields (fields with field IDs within 2000-2999) exist on the Roles form. A system failure occurred or you must add state fields to the form. The state fields included by default in the Roles form are the Test and Production fields. An entry in the state table could not be found for this application. The system failed to create an entry for the application in the AR System Application State form. Create an entry for the application manually. Could not query the application state table. A system error occurred or the AR System Application State form was deleted. Restart the AR System server, which automatically re-creates the form if necessary. Unknown error code errorNumber encountered. The message with error code errorNumber is missing from the string table. Unable to initialize user information. Reading of user preferences from ar.ini failed. This can be due to an invalid or missing home directory for the selected user name. Make sure that the ar.ini file exists in the user home directory and that a home directory is associated with the user in the aruser section of the win.ini file.

2382 Error 2383 Error

2392 Error 2393 Error 2394 Error

2395 Error 2396 Error 2401 Error 2403 Error

2404 Error

Unable to connect to any servers. While trying to log in and connect to the specified servers, BMC Remedy Administrator failed to connect to a server. This can occur when the server is down, when the network is too slow (leading to a time-out), or when you are not an administrator or subadministrator user for the server. Failed to initialize the system globals. You encountered an unusual error condition. The user home directory is missing from the ARuser section in the win.ini file. While trying to initialize the user preferences, BMC Remedy Administrator failed to read the home directory for the logged in user. The directoryName might be missing from the aruser section of the win.ini file, or the specified directory might not exist.

2405 Error 2408 Error

118

Error Messages Guide

AR System error messages

2412 Error

Currently running MISCDLL.DLL version oldVersionNumber is an old version. Version currentVersionNumber of MISCDLL.DLL is required. Installing an older BMC Remedy User or BMC Remedy Administrator in the same directory as a newer one might cause this error. Reinstall the latest version of the BMC Remedy User or BMC Remedy Administrator.

2416 Error 2417 Error 2418 Error 2419 Error 2420 Error 2421 Error 2422 Error 2423 Error 2426 Error 2427 Error

Failed to create memory. BMC Remedy Administrator could not allocate memory for its data structure. Close one or more applications to continue. Failed to create the AR System home directory. BMC Remedy Administrator failed to create the specified user home directory. Make sure that the path is valid and that the disk is not full. User Name is missing. You must specify a user name when saving user information in the Login Information dialog box. AR System home directory is missing. You must specify a home directory when saving user information in the Login Information dialog box. At least one field must have a value in a Set Fields action. You cannot save a Set Fields action without specifying a value for a field on the form. Specify a value for the field on the form to continue. You cannot delete an object that you are currently editing. You cannot delete an active link, filter, escalation, or form that is open. Close the window in question, and retry the deletion. Failed to load the selected image file. The selected file is not a valid BMP (bitmap) file, or it is larger than the supported size of 15 x 16 pixels. Select an appropriate file to continue. You must specify a menu or button field for active links that execute on a menu or button. You selected Execute On: Menu Item/Button in an active link without associating it with a menu item or button on the form. Server serverName not found in server list. You cannot access a server that is not specified in the list of servers you are logged in to. Add the server to your server list in the Login Information dialog box, and log in again. The following fields do not have valid values set: In an existing Set Fields action, BMC Remedy Administrator found some fields whose values are no longer valid. This can occur if BMC Remedy Administrator cannot allocate enough memory to get the fields’ value or if the fields’ data type is no longer valid. Specify an SQL command. To save a SQL Set Fields Action, you must specify a SQL command. This is not validated in any way but cannot be left blank. Enter a SQL command to continue. Could not remove all the specified pending operations. The server had a problem deleting the pending operation after you clicked Remove in the Pending Distributed Operations dialog. Supply a label index (greater than 0). In a SQL menu definition, you must specify the column number of the SQL query result to use to create the menu itself. Any number greater than 0 is accepted.

2428 Error 2431 Error 2432 Error

Chapter 2 Action Request System error messages

119

BMC Remedy Action Request System 7.5.00

2433 Error 2434 Error 2435 Error

Supply a value index (greater than 0). In a SQL menu definition, you must specify the column number of the SQL query result to use as the value the menu choice inserts into its associated field. Supply an SQL command. To save a SQL menu definition, you must specify a SQL command. This is not validated in any way but cannot be left blank. Enter a SQL command to continue. Button field is missing an active link assignment. While saving a form using a 3.x (or later) BMC Remedy Administrator into a 2.x AR System server, the specified button field was not associated with an active link. You must assign an active link to the button field (or delete the button) before you can save the form.

2437 Error

Cannot read forms for server. BMC Remedy Administrator failed to read the list of forms on the current server. BMC Remedy Administrator might have failed to allocate memory to save the list of forms, or there might be a network connection problem. You have selected more fields than will fit in the clipboard. Select fewer fields, and try again. If you selected more than 300 fields on the screen, you cannot use the Edit > Copy operation. Select 300 or fewer fields to continue. The following field cannot be displayed in this view because it contains invalid properties. Remove it from this view by using the Fields In View dialog box. The specified field in the current view has missing or invalid display properties and cannot be displayed in the view. Remove the field from the view to continue.

2438 Error 2439 Error

2440 Error 2441 Error 2442 Error 2443 Error 2444 Error

Insufficient resources to create the palette. The floating palette tool bar used to create new fields could not be created because Windows ran out of memory. Close some applications, or restart your Windows session. Another view already exists with that name. The name you specified is used by an existing view. Specify a new name for your view; remember that names are case-sensitive. You must specify the hours or minutes (or both) to retry a distributed operation. When defining a distributed mapping on the Options page, you can specify the length of time to retry. If you selected this option, you must enter this information. Get list of fields operation failed. Your attempt to get a list of fields from a server failed. The server might have failed after you logged in to it. value is not a valid value for field fieldName. Values set to newValue. When defining a Set Fields action in an active link, you specified a string value for an enumerated field that does not represent a valid state. For example, you cannot set Status to Done if the legal states are New, Assigned, and Closed. The Value field is set to the first member of the set of legal states. Note that value is outside the range for field fieldName. When defining a Set Fields action in an Active Link, you specified a numeric value out of range for that field. The Value field is not set. You must enter a distributed mapping name. When creating a distributed mapping, you did not specify a name. Enter a distributed mapping name to continue.

2445 Error 2446 Error

120

Error Messages Guide

Enter an escalation name to continue. and Server fields might not contain a combination of double and single quotation marks. You must have at least one field with a value in a push field action. A value must be entered for the following fields: Request ID. This can occur in the If Action or the Else Action page of the Create or Modify Filter window when the New Action selected is DSO Action. Chapter 2 Action Request System error messages 121 . 2455 Error 2458 Error 2459 Error The width of a results list field and its separator combined is limited to 128 characters. one or more of the field mappings is incorrect. or you entered a value for a parameter of type IDispatch. Form. Select a fewer number of items. You tried to Show Unmapped Fields in a custom distributed mapping. These fields might not contain a combination of single and double quotation marks because those values are stored already surrounded by either double or single quotation marks. The parameter can be filled only by nesting another method whose return type is compatible. Unable to display unmapped fields. the Mapping. Form. the Request ID. Specify a value for the field on the form and try again. You tried to export definitions for more than 1985 items.AR System error messages 2447 Error 2448 Error 2449 Error 2450 Error You must enter an escalation name. If the Distribute Transfer option button is selected. you did not specify a name. You tried to save a Push Field action without specifying a push field value for a field on the form. To avoid this error. To Form. The administrator tried to make a column of the results list wider than 128 characters. so one of these must not exist in the field. 2454 Error A maximum of 1985 items can be exported at once. but it cannot contain both kinds of quotation marks. This is a special object parameter in which you can only add another method which returns the same object. This error can occur when you select the items directly or when you select Related Items and the number of related items plus the number of selected items exceeds 1985. You defined an OLE method that has a parameter of type pointer and you nested another method whose return type is incompatible with the pointer type. and try the operation again. You tried to add or modify a DSO Action to a Filter with a field that contains a combination of double and single quotation marks. export fewer than 1985 items at one time. 2460 Error This is a special parameter in which you can only add another method which returns this object type. You defined an OLE method that has a parameter of type object (IDispatch) and you nested another method whose return type is incompatible with the object type. When specifying a Distributed Delete DSO Action for a filter. The current custom mapping is not valid. you must provide a request ID. You can also use $fld$ to enter the value for a pointer parameter. and Server. The field can contain double quotation marks (“) or single quotation marks (‘). and server. AR Runtime gets or sets the value of the $fld$ and treats this field as an OLE pointer variable. If the Distributed Delete option button is selected. and To Server fields might not contain a combination of double and single quotation marks. form name. or you tried to enter a value for a parameter of type pointer. When creating an escalation.

or Compatible. You cannot add a method here. You clicked Delete Method without first having selected a method. Can delete only methods at the root level.5. the parent method’s return must be one of the following types: IDispatch. If the parent method’s return type is not one of these types. You defined an OLE method that has a return value. This error occurs when you place your selection on one of these data structures and attempt an Add Method operation. Please select a method that returns a pointer. When you nest a method to a parameter. You cannot call another method on the parent method. When you provide a value for a parameter. Cannot be inserted by clicking the Add Method button. When you define an OLE method that has a return type and you try to nest or call another method on this return type. To be deleted. A label must be unique and consist of one or more characters. BMC Remedy Administrator validates whether the return type is of type object. You tried to add or nest a method to a parameter. Please select a method to delete. enums. and other data structures displayed in the type library tree are for display purposes only.00 2461 Error Please select a matching function. 2470 Error 2471 Error 2472 Error 2473 Error 122 Error Messages Guide . 2465 Error 2466 Error 2467 Error 2468 Error 2469 Error The Parameter or Return value is of wrong type. The constants. You defined an OLE method that returns a pointer. You can call or nest another method out of this return type only if the return type is of type object or object pointer. When you nest a method. BMC Remedy Administrator tries to map it to the OLE methods parameter OLE type. but the pointer is incompatible with the parameter pointer type you want to nest. Please select another one. Type incompatible. If unsuccessful in the conversion. You can't add methods to a return value. and you tried to add a method by clicking Add Method when the selection was at the return node. 2462 Error 2463 Error 2464 Error Please select a matching function. the parameter must be of type pointer. Rename the label. Labels in guides must be unique.BMC Remedy Action Request System 7. The Parent return type is not an Object. The two pointer types do not match. Please type in a proper value. and you tried to nest an incompatible return type. Incompatible objects. VARIANT. BMC Remedy Administrator returns this error message explaining that the value cannot be converted to the native OLE parameter type. You tried to add or nest a method. this error is returned. providing a name that has not yet been used in the guide. but the containing object of the child method differs from the return type object of the parent method. but the return value is incompatible with the parameter's native type. You tried to nest a method that returns a pointer. Looks like the return type of the method selected and the method to be added are incompatible. Cannot add the method. a method must be a nested parameter either at the parameter level or at the return level. Try again. The Constants and properties are for display only.

You must specify a name when creating or modifying a packing list. the HTML file generation stopped because the HTML file could not be created. an unspecified error was returned during HTML file generation. When an application was deployed. Bad Path: directoryPath. Enter a packing list name. Enter a unique name to continue. platform. The permitted number of open files was exceeded. 2475 Error 2476 Error 2477 Error 2478 Error 2479 Error 2480 Error 2481 Error 2482 Error 2483 Error 2484 Error 2485 Error 2486 Error 2487 Error Please enter a non-empty string in label and name fields. you can nest another method. Right-click to select a Field. platform. the HTML file generation stopped because the file is either corrupted or the file is open in a nonshared mode. specify a view label and name. the HTML file generation stopped because the permitted number of open files was exceeded. No work space has been selected. Please give the entry a unique name. When an application was deployed. To continue. Select a packing list. You do not have the proper permissions to access the file fileName. Enter a server name to continue.AR System error messages 2474 Error You have entered an improperly formatted value for a decimal field. If the return type is an object. and you selected Enable Workspace. When an application was deployed. This message occurs when the Server Name field in an Open Dialog action is empty. Right-click and select a field. create this view with a different combination of label. Please enter a server name. The administrator defines the number of places to the right of the decimal point (precision) for a given field. and retry the operation. The error was not covered under errors 2483 to 2495. the HTML file generation stopped because all or part of the path is invalid. and locale. and locale combination. There was an attempt to use an invalid file handle. Chapter 2 Action Request System error messages 123 . You selected View > By Workspace. An error occurred because you tried to create a view without a label or name. The file fileName could not be located. but you did not select a packing list. An error is returned because the view you are creating contains the same combination of information as another view. You cannot have duplicate named predefined searches. An unspecified error occurred. When deploying an application. the HTML file generation stopped because the file could not be accessed. To continue. You cannot enter a value in the return value node. Cannot edit return value. When an application was deployed. The value you entered does not meet the criteria defined by the administrator. Predefined searches cannot have duplicate names. There is already another view with the same label. When an application was deployed. The administrator might also define the high and low range for values entered into the field.

they have a default location and appearance. your drive is corrupted or you are trying to write to a network drive and the network is down. There was an attempt to lock a region that was already locked. the HTML file generation stopped because a shared region was locked. Any fields already in the view are unaffected. for example. the HTML file generation stopped because there are no more directory entries. 2505 Warning No integer or selection fields exist to cross-reference against. the HTML file generation stopped because the end of file was reached. When an application was deployed. The end of file was reached. all other forms that depend on this form will be deleted. you tried to add fields to the view that already exist in the view. Do you want to continue? You are removing data fields from their only view. the HTML file generation stopped because there was an attempt to lock a region that was already locked. the HTML file generation stopped because the disk is full. because they are already in this view. When an application was deployed. When an application was deployed. The disk is full. Verify your existing actions. When an application was deployed. You are removing these data fields from their only view: fieldNames.5. will be lost. Attempted access to file fileName produced a sharing violation. When an application was deployed. When an application was deployed. the HTML file generation stopped because there was an error trying to set the file pointer. Try another notification mechanism. the HTML file generation stopped because the current working directory cannot be removed. During a Copy or Paste operation from one view to another. If you continue. including label text and location. If you continue and put the fields back into a view. There was a hardware error. existing actions might be made invalid.BMC Remedy Action Request System 7. Do you want to continue? You are deleting a form used as a member of a join form. the HTML file generation stopped because there was a hardware error. There was an error trying to set the file pointer. When an application was deployed. All display information. Other forms depend on form formName. These fields do not exist on any other views. Those actions are invalidated if you reattach them to a form that no longer contains those fields. When an application was deployed. The number of directory entries for directory directoryPath has been exceeded. 2503 Warning 2504 Warning The following fields were not pasted. 124 Error Messages Guide . 2492 Error 2493 Error 2494 Error 2495 Error 2501 Warning 2502 Error Warning: If you change the form. the join form is also deleted. If you delete this form. Your active link and filter actions might contain references to fields on this form.00 2488 Error 2489 Error 2490 Error 2491 Error The current working directory cannot be removed. You specified Cross-Reference as the notification mechanism for a Filter Notify action. but there are no integer or selection fields that you can select to cross-reference against on this form.

Real number fields require a number in the valid range. You cannot close all windows. it is replaced by the first value in the list. and then try again. If you continue. and those changes are about to take effect. Failed to read field for form. User Heap: percentage% free. The minimum and maximum values are the same. Save the form before renaming it. 2510 Error 2513 Error 2514 Error 2515 Error 2516 Error 2517 Error 2518 Error 2519 Error 2520 Error 2521 Error 2522 Error Chapter 2 Action Request System error messages 125 . You illegally specified a range of exactly one value. BMC Remedy Administrator failed to read a field for the form you selected for an active link or filter. you can close the form without saving any changes. 2508 Error The status field must have a default value. the following fields will be deleted: fieldNames. because Windows resources are low. Otherwise. BMC Remedy Administrator failed to close all existing open windows. Changes are lost. If you save the changes. You deleted fields while editing the form. Login aborted. GDI Heap: percentage% free. Integer fields require a number in the valid range. The range is number to number. You cannot add or modify the Default Login name. The minimum value is out of range. you might want to specify a new default value. Close some windows or running applications to gain more space. Do you want to continue? The Status core field is special because a default value is required. The maximum value is out of range. You tried to change the name or add a new Default Login user name to the login user list. Do you want to continue? You are deleting a value from a selection field that matches the default value. possibly because of a user request for an unsaved window. The range is –2147483647 to 2147483647. The minimum value is out of range. If you delete the current default. You can create a character menu only up to 14 levels deep. Real number fields require a number in the valid range. Integer fields require a number in the valid range. the default value will also be deleted. 2507 Error The value being deleted is the same as the default value. Close some windows or applications to continue. The range is –2147483647 to 2147483647. If you continue. The Default Login name is a reserved name and cannot be added or changed. Character menus cannot exceed 14 levels. The range is –2147483647 to 2147483647. If you continue the default value will be changed to the first entry.AR System error messages 2506 Error Unable to open more windows. The range is number to number. the default value is also deleted. Integer fields require a number in the valid range. You might want to specify a new default value. 2509 Warning Confirm that you want to save the form. The maximum value is out of range. If you continue. A new window could not be opened because there are too many windows open or too many applications running. When you tried to log back in. Make sure that BMC Remedy Administrator can still connect to the server that the form is on. The default value is out of range. This is a final confirmation and a chance not to save the form changes. the fields are deleted. You must save the form before you can rename it.

There are no toolbar items on any of the menu items. The range is number to number. they no longer appear in the current view. Real number fields require a number in the valid range. and all fields in the view will be saved to the database when form changes are applied. If you continue.5. just as if you had explicitly deleted them. and the changes will take effect when you save the form. This message indicates that a mixture of join and trim fields was selected. 2536 Warning 126 Error Messages Guide . Real numbers must have a precision (number of places to the right of the decimal point) within the specified range. Only the Paste operation of trim fields will succeed. BMC Remedy Administrator detected and corrected a minor problem with the front-to-back ordering of fields in this view. This usually occurs because of direct API setting of field properties or because of problems with the conversion of an old form definition. 2534 Warning The layering of some fields in this view was not valid. If any of these fields were added to the current view after you last loaded the form.00 2523 Error 2524 Error 2525 Error 2526 Error 2527 Warning The default value is out of range. Active link activeLinkName is already used by controlFieldName. You cannot have a a join field appear more than one time in a form. You must give field coordinates (X. The operation most likely succeeded but the server is still busy. Normally. The precision is out of bounds. Valid range is 0 to 30. Therefore.” Your form has probably been copied. Y location) that keep the field within the maximum dimensions of a view (1500 x 3000). but verify at a later time (when the server is not busy) that the copy operation succeeded. This change will move the field out of bounds. The following restored fields are no longer in this view: You restored the selected fields from the database. the selected join fields will not be copied. BMC Remedy Administrator cannot display the Toolbar Layout dialog box. 2535 Warning Copy and Paste of join fields is not supported. You must give field coordinates (X. No menu items in the current view have an associated toolbar item. Do you want to continue? The current operation can affect the display properties of one or more unloaded views. This change will cause the field to be out of bounds. Use the Fields in View dialog box to see which views the fields are in. The problem has now been corrected. Are you sure you want to move it to controlFieldName? Active links can be attached to only one button or menu item. These fields will be deleted from the database. The server is busy and has “timed out. Do you want to continue? When trim or control fields are removed from all views. and a Paste operation was attempted. they are marked for deletion. Y location) that keep the field within the maximum dimensions of a view (1500 x 3000). Attaching an active link detaches it from its current button or menu item (if it has one). 2533 Warning A time-out occurred while copying form formName to formName. you can switch to the other views that contain the affected fields to see the result before applying the changes to the form. the Copy operation is disabled when join fields are selected. 2528 Warning 2531 Warning 2532 Warning You are removing these trim or control (or both) fields from their only view: viewName. This warning occurs when the Save Form As command is used to copy a form.BMC Remedy Action Request System 7. Multiple views may be affected by this operation.

Do you want to continue with overriding loop detection? By shutting down loop protection. 2542 Warning 2543 Warning 2544 Warning 2545 Warning Distributed Fields will be deleted. You opened a Set Field active link action. click Modify Action. Save the filter or escalation only if you are understand the risk in what you are doing. Selecting this option could cause an infinite loop in the system. When you selected the Form prefix option in the By Form dialog box. Distributed fields are system-generated and cannot be mixed-and-matched. Select Cancel if you do not want to delete the selected item. select None in the Distributed Fields dialog. button. Are you sure you want to have numberOfFields Distributed Fields? This is a confirmation message when you want to delete DSO mapping fields. It can not be added to buttonName. cancel this operation. possibly because one or more fields were deleted. the delete operation did not complete as expected. Use the Distributed Fields dialog box to re-create a standard set of distributed fields in your form. This version of AR System does not support moving an active link from one button to a different button. you did not enter a prefix before clicking OK. To correct this problem. you run the risk of creating infinite loops and overwriting the original record in a distributed transfer operation or a distributed return operation. This message occurs when an incorrect data type is associated with distributed fields. Select none. Chapter 2 Action Request System error messages 127 . Field IDs in this range are reserved by AR System. it will not exist on any view. 2548 Warning 2549 Warning Please enter a form prefix. it will be completely and permanently deleted. you specified a field ID less than 536870911. Unless you are intentionally using the AR System reserved field ID range. and choose a field ID outside of the reserved range. full. basic. and some of the fields used in the setfield/value list box were deleted from the form. Do you want to save this field anyway? While creating a new field in a form. If you delete this element from this view. Please close and reopen the form after the save operation has completed. or menu item field will be deleted because you are deleting its only view. To delete Distributed Fields. and then click OK. Select a form. To continue. Distributed Fields will be deleted. and press OK. 2541 Warning This form contains a non-standard set of Distributed Fields. or advanced to return to a standard set of fields. Please press Modify Action button to rectify the problem. You have specified an ID within the reserved range. Active link activeLinkName is already used by buttonName. An inconsistent set of distributed fields is present in your form. open the form after the save operation completes and try deleting the fields again. create a new active link. This warning is returned because. This form contains a Distributed Field of the wrong data type.AR System error messages 2537 Warning At least one trim. To continue. although the form is in the process of being saved. Are you sure you want to have numberOfFields Distributed Fields instead of numberOfFields? This is a confirmation message when you want to delete DSO mapping fields. 2546 Warning One/more fields have been deleted from the form which will affect Setfield list. You selected the Selected Form option in the By Form dialog box but did not select any forms before clicking OK. Please add at least one form to the selected form list. 2538 Warning 2539 Warning 2540 Warning None of the requested field deletions occurred on the server.

BMC Remedy Administrator warns you that all subsequent methods (if nesting was done) will be deleted. The precision is out of bounds. The minimum value has a bad value. You tried to import a pre-4. A global field has just been set to a regular field. Please remove some forms from the selected form list.0 form with a 4. 2561 Warning 2562 Warning 128 Error Messages Guide . This warning appears when you add the same server name.00 2550 Warning A maximum of numberOfForms forms can be selected. A maximum of number forms can be selected.5. in the list of servers. These field IDs are reserved for Alert Lists and Result lists.x or later. You chose an invalid field type to become a global field. By turning the field back into a “regular” field. 2557 Warning 2558 Warning Warning: Form formName not available in server serverName. To improve this view so that it looks the same on all clients. The entry mode selection will be set to default. Global fields by design have no default values.x (or later) version of BMC Remedy Administrator. Valid range is 0 to 28. When viewing a select number of forms in the Server Window. 2551 Warning 2552 Error 2553 Error 2554 Warning 2555 Error 2556 Warning Warning: All the subsequent calls will be deleted. To continue. this warning appears. You entered an invalid value for the minimum value in the Field Properties Attributes page for a Decimal Field. You entered an invalid value for the maximum value in the Field Properties Attributes page for a Decimal Field. A duplicate server was detected in the server list for user userName. for both the short and long names.gif). you selected more than 10 forms. This changes all fields’ bounding boxes so that they are compatible with 4. The maximum value has a bad value. select a number less than 10. 2559 Warning 2560 Warning The field type selected is not valid for global fields. You entered an invalid value for a Decimal Field in the Attributes page of the Field Properties Dialog Box. This message indicates that you selected more than 10 forms. The valid range is between 0 and 28. A workaround would be to create a packing list and use it to view a larger number of forms. Field ID 706 and 1020 are reserved for Alert and Results List respectively. Server Name in list: serverName Short Name of detected server: serverShortName Long Name of detected server: serverLongName. BMC Remedy Administrator will upgrade the layout information for this view when you save this form. Choose another field ID not from these reserved numbers. No image conversion will take place. This warning appears when you change a server name for an open dialog active link action. you now can specify an entry mode. You are given the option to reset the value to the previous server you selected. This warning appears the first time a form is imported and when the form’s views are changed. Please choose another Field ID for field—fieldType. Save anyway? If you try to change the extension of an image format’s extension (for example.BMC Remedy Action Request System 7. see the Form and Application Objects Guide for available field types. When you try to delete an OLE method. trying to save a JPEG file as something. To continue. You can select a maximum of 10 forms through the Selected Form option of the By Form Dialog Box. The maximum is 10.

An entry point guide was created without a starting active link. No field mappings have been defined for Input and Output modes. No field mappings have been defined. Please press Modify Action button to rectify the problem. 2572 Warning 2573 Warning 2574 Warning 2575 Warning 2576 Warning 2577 Warning 2578 Warning One/more fields have been deleted from the form which will affect the Open Window action field mappings. The entry point guide cannot execute correctly in an Application List field without a starting active link. Choose another field ID not from this reserved range. No field mappings have been defined for Open and Close dialog states. The guide will not be executed. in Search or Submit mode. If you delete an object that belongs to a locked group. Choose a different ID or renumber other entries first. you did not define any field mappings. Continue? Only positive integers. This warning is returned because you cannot export extension objects (non-AR System objects) in XML format. This warning is returned because. would you like to proceed? Locked workflow is attached to the form being deleted. To remove this warning. will delete all objects in the same lock group. Deleting this object. This option is deprecated from BMC Remedy Administrator. Selected extension objects will not be exported. Exporting extension objects in XML is not supported. Verify field mapping for the deleted fields. then those form definitions and all the associated data will be removed. and existing data will never be affected. One/more fields have been deleted from the form which will affect the Service Window action field mappings. objectName. appears to have dependant workflow that is part of a lock group. may be set. This warning is returned because you changed the Form Name in the Open Window action and these field mappings might be invalid in the On Open or On Close modes. This range of field IDs is reserved for columns in an Alert List. Go to BMC Remedy User and open the corresponding option in the AR System Administration Console. If there are any forms in this lock group. Any existing custom IDs will be replaced with a linear sequence. formName. IDs must be in ascending order. 2564 Warning 2565 Warning 2566 Warning 2567 Warning Some fields that are mapped will not be relevant for this form. Deleting this form will trigger the deletion of one or more lock groups. and then click Modify Action. these will not be saved until you save the form. Are you sure you want to continue? A single object that is a member of a locked group cannot be deleted. Chapter 2 Action Request System error messages 129 . Please choose another Field ID for field—fieldType. such as a filter in a locked group of filters. This warning is returned because you did not define any field mappings for Dialog window type. the attached workflow must also be deleted. However. all objects in the locked group are deleted. 0 to 2147483648. Please press Modify Action button to rectify the problem.AR System error messages 2563 Warning Field IDs from 711 to 718 are reserved for columns of Alert List. To successfully delete this form. 2569 Warning Entry point guide does not have a starting active link. specify a starting active link for the active link guide. 2570 Warning 2571 Warning The form.

If necessary. you did not enter a server name. create multiple indexes for this form. Unable to malloc memory. When creating or saving a menu. Specify a refresh code to continue. The system encountered an error during a call to allocate memory space when creating query lists on a form. Good candidates for indexing include fields that you search on frequently. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. This error usually occurs when too many processes are running or when some processes have grown to occupy most or all available memory space on the client. One or more indexes does not have any fields specified. The maximum number of fields that can be specified in one index is numberOfFields. you did not specify a menu type. which is 16. When creating or saving a menu. For complete functionality go to BMC Remedy User and open the corresponding option in the AR System Administration Console. Good candidates for indexing include fields that you search on frequently. You exceeded the number of fields that can be added to a single index. The system encountered an error during a call to allocate memory space when creating indexes. you did not specify a refresh code.BMC Remedy Action Request System 7. Please supply a menu name. This error usually occurs when too many processes are running or when some processes have grown to occupy most or all available memory space on the client. Please select a menu type. 2707 Error 2709 Error 2710 Error 2711 Error 2713 Error 2714 Error 2716 Error 2717 Error 2718 Error 2719 Error 130 Error Messages Guide . When creating or saving a Search menu type. You might be indexing too many fields in your form. If necessary. Enter a menu name to continue. Please select a refresh code. You exceeded the number of fields that can be added to a single index. which is 16. Please supply a server name. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. You might be indexing too many fields in your form. When creating or saving a menu. when removing items from the list). The system encountered an error during a call to allocate memory space when updating query lists on a form (for example. This error usually occurs when too many processes are running or when some processes have grown to occupy most or all available memory space on the client. You have reached the maximum limit of the fields in an index. Enter a server name to continue.00 2579 Warning 2706 Error This option is partially deprecated from BMC Remedy Administrator. add fields that you search on frequently to your index. To continue. Unable to malloc memory. you did not enter a menu name.5. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. You created an index without any fields. create multiple indexes for this form. This error usually occurs when too many processes are running or when some processes have grown to occupy most or all available memory space on the client. Specify a menu type to continue. Unable to realloc memory. The system encountered an error during a call to allocate memory space when adding indexes. Unable to realloc memory.

When creating a DDE active link action. DDE 'Item' is missing. When creating a Message active link action. DDE 'Topic' is missing. Enter a DDE path. you did not select a field name. you did not enter a form name. Select a value field to continue. These fields are system-generated and must exist in any regular form. you did not enter a DDE path. you did not enter a DDE topic. Menu definition is empty. When creating a DDE active link action. DDE 'Service Name' is missing. you did not enter any message text. DDE poke actions must include a DDE item. you did not enter a file name. When creating a DDE active link action. When creating a Change Field active link action. Select a field name. If necessary. you did not add any menu items. Add menu items to continue. you did not enter a DDE item. and click Add Action. Enter a DDE topic. Please supply a file name. Enter a DDE item. When creating or saving a File menu type. Please supply a label field. When creating a Message active link action. you did not enter a file location. and click Modify Action. and click Add Action. Enter the missing message text. the message number is outside of the allowed range. Please supply a value field. but you cannot delete them. When creating or saving a Search menu type. When creating a DDE active link action. Please select a file location. and click Add Action. Select a label field to continue. You cannot delete the following core field(s): When creating or modifying a form. When creating or saving a Search menu type. When creating or saving a Search menu type. Enter a form name to continue. Missing message text. and click Modify Action. and click Add Action. Enter a file name to continue. Fix the message number. and click Add Action. 2727 Error 2728 Error 2729 Error 2730 Error 2731 Error 2732 Error 2733 Error Chapter 2 Action Request System error messages 131 . Enter a service name. you illegally tried to delete a core field. When creating or saving a Character menu type. User messages have message numbers of 10000 or greater. Must be greater than 9999 and less than 2147483647. you did not enter a DDE service name. you did not select a value field.AR System error messages 2720 Error 2721 Error 2722 Error 2723 Error 2724 Error 2725 Error 2726 Error Please supply a form name. you can hide these fields. you did not select a label field. Missing field name. DDE 'Path' is missing. Enter a file location to continue. When creating or saving a File menu type.

The search database has been synchronized successfully. try performing the synchronization later. When choosing a default form view in the Manage Views dialog box. Macro name is missing. The minimum value is greater than the maximum value. Click OK. you specified an illegal default value. When creating an integer field. To continue. Specify a run macro command. You cannot perform searches for new objects added to your search database. Invalid View Name. To continue. When creating a DDE active link action. The default value: When creating a decimal field. and click Add Action. When creating a character field. If you close the Field Property dialog box. 132 Error Messages Guide . You attempted changes to a form that were not accepted by AR System. To continue. you selected an illegal menu. When creating a Run Macro active link action. 2745 Error 2746 Error 2747 Error Do you wish to close the field property dialog before correcting the errors? You specified incorrect field property settings. Unable to Save/Update Form. you did not specify a run macro command. To continue. To continue. You now can search for any new objects added to your search database. your settings are not saved. do you wish to continue? When attaching a menu to a character field. you specified an illegal range of minimum and maximum values. The minimum value minimumValue and the maximum value maximumValue. and click Add Action. create a default value within the minimum and maximum ranges. you specified an illegal default value. You must select a defined name. Enter a DDE command. To continue. Server object objectName cannot be opened from here. 2744 Error The Default value is out of range with the minimum and/or maximum value.5. and then open the server object from the Server Window. The Default value is out of range with the minimum and/or maximum value. You successfully updated the search database. Synchronization of the Search Database Failed. You cannot open server objects from the Related Workflow tab on the Field Properties window. The named menu is not defined at this time. Try again. you did not enter a DDE command. create a minimum value larger than the maximum value.BMC Remedy Action Request System 7. The Default value is out of range with the minimum and/or maximum value. you specified an input length outside the legal range of values. specify an input length within the legal range. To continue. create a default value within the minimum and maximum ranges.00 2734 Error 2735 Error 2736 Error 2737 Error 2738 Error 2739 Error 2740 Error 2741 Error 2742 Error 2743 Error DDE 'Command' is missing. select a menu from the drop-down list of available menus. you specified an illegal default value. When creating a decimal field. The minimum value minimumValue and the maximum value maximumValue. Please open it from the Server Window. When creating a real field. you can choose only from the listed views in the drop-down menu. There was a failure in updating the search database. The field length must be between 0 and 4294967295. create a default value within the minimum and maximum ranges.

You can troubleshoot this problem by verifying that you can select a different font as a preference. Sorry. and click Add Action. When creating a Push Fields action. When creating a Notify filter action. you did not select the reference field required when the notification Mechanism is Cross-Reference. rerun BMC Remedy Administrator analyzer. and click Add Action.com. When creating a Search type menu. you did not enter a Push Field If qualification. After you verify that you have enough memory resources and that the server is running. BMC Remedy Administrator analyzer could not find a list of filters on the server. or AR System server might have stopped running. 2760 Error 2761 Error Chapter 2 Action Request System error messages 133 . After you verify that you have enough memory resources and that the server is running. and click Add Action. Possible problems might be a memory allocation error. When creating a Notify filter action. Check your qualification. BMC Remedy Administrator analyzer could not find a list of forms on the server. There was a failure during log in for these reasons: AR System did not recognize this user name as a valid administrator. Feel free to visit our website for the latest information about BMC Remedy products and services at http://www. You choose items from Help > Remedy on the Web > Remedy Home Page in BMC Remedy Administrator. 2759 Error Error getting form list on server serverName. Possible problems might be a memory allocation error. and click Add Action. Reference Field is missing. and click Add Action. you did not enter a user name. 2754 Error 2755 Error 2757 Error Please enter Qualification query for this action. Select a reference field. The fonts you selected in the Form Fonts tab in the Preferences dialog box were not accepted for some internal reason. Possible problems might be a memory allocation error. When creating a Notify filter action. You entered an invalid server name. verify that the server and administrator names are correct. After you verify that you have enough memory resources and that the server is running. Enter a qualification. unable to locate your default browser. or AR System server might have stopped running.AR System error messages 2748 Error 2749 Error 2750 Error 2751 Error Alert text is missing. Error getting filter list. Qualification line error at position number. you did not enter a valid qualification. Error getting active links list on form formName. 2753 Error Unable to log on to any server as administrator or sub-administrator. If you can. Enter a user name. Error Getting Font Data. or AR System server might have stopped running.bmc. Enter notify text. rerun BMC Remedy Administrator analyzer. you did not enter notify text. To continue. the font you previously selected cannot be understood by AR System for some unknown reason. rerun BMC Remedy Administrator analyzer. User text is missing. BMC Remedy Administrator analyzer could not find a list of active links connected to this form on the server. You must install a browser to access this information.

or AR System server might have stopped running. Possible problems might be a memory allocation error. Create a set of field/value mappings to continue. Error: No guide selected for CallGuide action. To continue.5. You will lose your existing guideName assignments by changing the form. you did not specify a server. an error occurred. Enter or select a server name to continue. you changed which form controls the active links. Active links and filters can be attached to multiple forms. This change might create unanticipated results in your guide. you specified a server that the system could not find or resolve. rerun BMC Remedy Administrator analyzer. When creating or modifying an Open Window action. Enter or select a different server name to continue. 2778 Error 2779 Error 134 Error Messages Guide . Verify that the guides exist and try repeating the creation of the Call Guide action to continue. Error: Addition of guide guideName addition to tree failed.BMC Remedy Action Request System 7. Enter or select a different server name to continue. Enter or select a form name to continue. Select a guide to continue. After you verify that you have enough memory resources and that the server is running. Do you want to continue? When modifying an active link or filter guide. but the action does not function properly. Form formName not found in list of forms. make sure that all fields requiring a value are visible in the default administrator view of the form and that the Allow Any User To Submit check box is selected before you attempt the export operation. Enter a new set of mappings. An error occurred when the system tried to add a complete list of guides to the tree. When creating or modifying an Open Window action. BMC Remedy Administrator analyzer could not find a list of escalations on the server. 2765 Error 2766 Error 2768 Error 2770 Error 2771 Error 2772 Error 2773 Error 2776 Error 2777 Error Error in export! Export aborted. BMC Remedy Administrator lets you save the action. When creating an Open Window action. Error: No server has been selected. When creating or modifying a Call Guide action. you did not specify a set of field/value mappings. or select the form used for these mappings. Warning: No field mappings have been defined for Open and Close dialog states. Error: No form has been selected. you specified a server that the system could not find or resolve. This message contains information about the position of the error in the line. When creating an Open Window action. When creating or modifying an Open Window action. verify which form or forms you want to control the active links in your guide. you tried to enter a set of field/value mappings that are invalid for the form you selected. Warning: Some fields that are mapped will not be relevant for this form. you did not select a guide. When creating an Open Window action. Server serverName not found in list of servers. While parsing a qualification line in the Open Window action.00 2762 Error Error getting escalation list. To continue. An error occurred while the system tried to export mail templates. Assign line error at position number. you did not specify a form.

2791 Error Unable to open file. After you verify that you have enough memory resources and that the server is running. Could not detect image type of imageType. Failed to analyze filter filterName in form formName. BMC Remedy Administrator analyzer could not find a list of fields connected to this form on the server. Failed to analyze escalation escalationName in form formName. Error opening file fileName. When creating a decimal field. or AR System server might have stopped running. When attempting to save a report of results from BMC Remedy Administrator analyzer. Please check the tab order to make sure that all shared fields are in the same order relative to each other. Make sure that you are using a . Enter a guide label to continue. To continue. This error occurs only with multiple native views of a form in which you are creating the tab order. BMC Remedy Administrator analyzer could not find this field connected to this form on the server.jpeg . When you tested the Help file or saved it to disk.jpg .txt format for the file and that you have write access to this directory path.bmp . Possible problems might be a memory allocation error. an error occurred. After you verify that you have enough memory resources and that the server is running. create a default value within the minimum and maximum ranges. Failed to analyze field fieldName in form formName. rerun BMC Remedy Administrator analyzer.AR System error messages 2781 Error 2782 Error 2783 Error Error: No Active Link specified for guide to go to. The Default value has a bad value. rerun BMC Remedy Administrator analyzer. Possible problems might be a memory allocation error. After you verify that you have enough memory resources and that the server is running. or AR System server might have stopped running.dib You can use only these formats. or AR System server might have stopped running. BMC Remedy Administrator analyzer could not find a list of escalations connected to this form on the server. Chapter 2 Action Request System error messages 135 . you did not enter a guide label. Possible problems might be a memory allocation error. Error getting field list on form formName. To continue. verify that you have the necessary permissions to access the file. you specified an illegal default value. and you can save only to a file of the same image type. you were unable to open a new file. make sure that the tab order is the same for each view of the form. rerun BMC Remedy Administrator analyzer. There was an error because the image you tried to save to a file is not from the following types: . 2784 Error 2785 Error 2786 Error 2787 Error 2788 Error 2789 Error Errors were found. When creating or modifying a Go To Guide Label action. Possible problems might be a memory allocation error. BMC Remedy Administrator analyzer could not find a list of filters connected to this form on the server. rerun BMC Remedy Administrator analyzer. After you verify that you have enough memory resources and that the server is running. or AR System server might have stopped running. When you create a tab order for shared fields across pages in a page holder.

To enable source control integration with AR System. The View will return to default. To enable source control integration with AR System. Otherwise. the form was created on the AR System server. The export operation fails. 136 Error Messages Guide .5. Use a different name. first click the Browse button to select a project and location from the Project Name drop-down list. Then restart BMC Remedy Administrator and open the form. and then click OK. and then click OK. Open the form in BMC Remedy Administrator and choose Form > Select a View to verify that the view you want to use exists. along with other modified fields. Any further operation on this form can cause unpredictable behavior. There was a failure during login because AR System did not recognize this user name as a valid administrator or subadministrator. or AR System server might have stopped running. When an object was exported. You can continue as a guest user. but the call failed because of instability in the client tool. Failed to get related items. This problem might be connected to the inability of your underlying RDBMS to create these fields. its related items were not loaded. and so on. Export file will not be generated. During the login process. BMC Remedy Administrator issued an API call to refresh the fields on this form. Possible problems might be a memory allocation error. for example.BMC Remedy Action Request System 7. You tried to create an object that has the same name as an object that already exists in the source control system. 2810 Error Object already exists in Source Control. 2808 Error Please select a Source Control Provider. When you created an Open Window action. If this does not work. Accordingly. Failed to load serverObject for form formName from server serverName. you might need to reboot your system. Nevertheless. the Form View you selected was not found on the AR System server. Verify in BMC Remedy Administrator if you can view all forms and all objects. 2794 Error 2795 Warning Some Fields could not be saved in this form. you overwrite the old object with a new one. 2809 Error Please select a Source Control Project. the server failed to load the different AR System objects connected to this form when you were viewing objects by workspace or by form. Verify in BMC Remedy Administrator whether objects are related. User userName does not have admin or subadmin privileges on server serverName. After you verify that you have enough memory resources and that the server is running. rerun BMC Remedy Administrator analyzer. Unable to refresh field detail for field fieldName in form formName on server serverName. You did not select a source control application before you clicked OK in the Source Control tab. whether an active link is connected to a form. The server failed to save some of the fields you tried to add to or modify on this form. close both the form and the BMC Remedy Administrator client. To handle this problem. first select a provider from the Provider Name drop-down list. 2796 Warning 2797 Error 2805 Error 2807 Error Error: The Active Link activeLinkName could not find the View viewName in Form formName. BMC Remedy Administrator analyzer could not find a list of applications on the server. You did not select a source control project before you clicked OK in the Source Control tab. or enter a different login name.00 2793 Error Error getting application list. the view used in the action is the default administrator view. Connecting as a guest user.

but your BMC Remedy Administrator client is not properly initialized with the source control system. Contact the other user if possible to resolve any administrative issues. you are not deleting an object from AR System server. For more information about source control. but the operation failed. You tried to check out an object that is checked out by another user. The server is configured for Source Control but you have not integrated it on your client. You tried to perform an operation on an object that was not first added to the source control system. You cannot modify this object because it does not exist in Source Control. Chapter 2 Action Request System error messages 137 . and then configure it in the Source Control tab in the AR System Administration: Server Information form. only one user at a time can check out an object. In Enforced mode. You tried to perform a source control action. However. Error writing Registry values. 2818 Error You are in Enforced mode of the Source Control Integration. However.AR System error messages 2811 Error 2812 Error 2813 Error Error getting definition file for object. Add the object to the source control project. you tried to modify an object that does not exist in the source control database. you lose the ability to track the history of any changes made to the object. see the Integration Guide. In Enforced mode. You tried to import the object definitions from source control. You are in Enforced mode of the Source Control Integration. Are you sure you want to remove the selected objects from Source Control. Click OK to continue. First check the object in to source control. or you did not properly configure it with your BMC Remedy Administrator client. as you will lose history data along with them? When you remove an object from source control. Contact the other user if possible to resolve any administrative issues. 2817 Error You are in Enforced mode of the Source Control Integration. You cannot modify this object because you did not check it out first. Contact the other user if possible to resolve any administrative issues. so modifying an object could overwrite or conflict with someone else’s work. You cannot modify this object. you run the risk of conflicting with another user’s work. Your Integration is not initialized. You tried to modify an object under source control in Enforced mode on the AR System server. Configure your system to have the proper source control integration with AR System. 2819 Error You are in Enforced mode of the Source Control Integration. Object does not exist in Source Control. the user who checked it out first is its owner. 2820 Error You are in Advisory mode of the Source Control Integration. you do not have a source control client installed. You cannot modify this object because it is already checked out to another user. You tried to retrieve user information from source control. You can then modify objects under source control. If conflicts occur when two users are trying to check out an object at the same time that is in Enforced mode. Otherwise. 2814 Error 2815 Error 2816 Error Object is checked out by userName. but the properties could not be displayed in the User Info dialog box. Make sure that you properly installed the source control client software.

If your development environment absolutely requires Advisory mode. After you make any changes in your source control provider. You tried to perform a source control operation on a group. by opening it in the source control client. The operation to AR System server was successful but the update to the source control database failed. Please relogin to this server for the changes made to Source Control Integration to take effect. and other configuration settings in the AR System Administration: Server Information form. 2824 Error 2825 Error Please enter a definition file name. you must log in to BMC Remedy Administrator again. To continue. Check out the object before performing any further operations. 2826 Error 2827 Error 2828 Error 2829 Error 2830 Error Error updating Source Control database. multiple users run the possible risk of accessing the same object at the same time. Modifying an object could overwrite or conflict with someone else’s work because it does not exist in Source Control. Enter a file name to continue. Verify that you have access to the file. Then you can start using source control integration with the AR System server. Contact the other user if possible to resolve any administrative issues. for example. 2822 Error You are in Advisory mode of the Source Control Integration. You tried to perform a source control operation on a distributed mapping. You are in Enforced mode of the Source Control Integration. You cannot import this object because it is already checked out to another user. Source Control operations can not be performed on Distributed Mappings. In Advisory mode. There was a failure to retrieve a definition file from source control. project. contact the other user if possible before making any changes to resolve any conflicts. you run the almost certain risk of overwriting another user’s changes or introducing inconsistencies. Source Control operations can not be performed on Groups. Modifying an object could overwrite or conflict with someone else’s work because it is already checked out to another user. When importing from source control into a file. verify that you have access to the project.BMC Remedy Action Request System 7. You tried to perform an operation on an object under source control in Advisory mode on AR System server. Modifying an object could overwrite or conflict with someone else’s work because you did not check it out first. In Advisory mode. This functionality is disallowed with AR System integration. for example. This functionality is disallowed with AR System integration. 2831 Error 138 Error Messages Guide . Error opening Source Control project. by opening it in the source control client. multiple users run the risk of accessing the same object at the same time. to continue. checking a mapping in to source control.00 2821 Error You are in Advisory mode of the Source Control Integration. Error getting file from Source Control database. You tried to perform an import operation on an object checked out to another user. Be careful not to overwrite some other user’s changes. and then retry the update operation to continue. checking a group name in to source control. Verify that the source control database is running. 2823 Error You are in Advisory mode of the Source Control Integration. for example. You tried to modify an object under source control in Advisory mode on AR System server. You tried to open a source control project but were unable to. for example.5. You tried to modify an object under source control in Advisory mode on AR System server. Because AR System integration detects that the object is checked out to another user. you did not enter a file name before you clicked OK.

When configuring the number of server threads in the Server Ports and Queue tab in the Server Information dialog box. If you are using a server name alias. for example. 2840 Error 2842 Error The Form name has not changed. Ask yourself whether this type of server thread is necessary in your operation. Import to server anyway? If the object is checked out to another user. and retry the import operation. The operation is only partially successful. Make sure that you properly installed the source control client software. The server is configured for Source Control but you have not integrated it on your client. 2834 Error 2835 Error Object is not checked out. preventing you from modifying the selected objects. Make sure that the number of Min threads is less than the number of Max threads. To continue. For a detailed discussion on source control issues. you do not have a source control client installed or you did not configure it properly with your BMC Remedy Administrator client. You can then modify objects under source control. Make sure that you properly installed the source control client software. You tried to manipulate an object (for example. You are in Enforced mode of the Source Control Integration. log back in to BMC Remedy Administrator.def file and a server name alias exists that cannot be resolved in either of the following places: Server Name Alias field in the Platform tab in the AR System Administration: Server Information form Server-Name: in the ar. You also see this error message if you import server objects from a . You can then modify objects under source control. When configuring the number of server threads in the Server Ports and Queue tab in the Server Information dialog box. to continue. 2836 Error 2839 Error Min value should be less than Max value. there was a failure importing some of the objects because the server name alias could not be resolved and show the server name. Check out the object from source control to continue. You tried to modify objects that are under source control in Enforced mode on AR System server. However. verify that it is valid. Chapter 2 Action Request System error messages 139 . by trying to access them in the source control client. Error importing some objects. Perform one of the following tasks: Make sure that the number of Min and Max threads is greater than zero. see the Integration Guide and the Configuration Guide. Please specify a new name. To continue. You cannot modify the selected objects. verify that you have access to the objects in the source control database. an error occurred. Min and Max value should be greater than 0. you tried to set the number of Min and Max threads to zero. and then configure it in the Source Control tab in the AR System Administration: Server Information form. If you are successful.cfg/ar.conf file. that object is skipped and the import process continues.AR System error messages 2832 Error 2833 Error The object you are importing has been checked out to someone else. you tried to make the number of Min threads exceed the Max number. You tried to save a form under source code control. checking it in to the source control project) that was not first checked out. change the name of the form. and then configure it in the Source Control tab in the AR System Administration: Server Information form. For a detailed discussion on source control issues. see the Integration Guide and the Configuration Guide. During an import operation from source control. Do you wish to continue? During a bulk update to the source control database. Import the object to the server later.

Source Control operations cannot be performed on Distributed Pools. Deleted objects do not appear even if the database is not synchronized.5. or change the configuration settings. Source control is configured in the Server Info window to require comments when objects are checked into or checked out of the source control project. Do you want to overwrite it? You tried to retrieve the latest version of the file from the source control database. verify the user’s access control settings. When trying to create and name a Distributed Pool object. You tried to perform a source control operation on a distributed pool.BMC Remedy Action Request System 7. To continue. Click Yes to overwrite the existing file with the latest version from source control. During the login process. you did not specify a target location. and that both AR System server and the source control database are running. verify that the object exists in the source control database. but the file already exists either on AR System server or in the location you specified. Verify that the objects exist in the source control database. Duplicate distributed pool name. verify that the server is running. Enter or select a target location to continue. To continue. and that both AR System server and the source control database are running. You can then manipulate the object as needed. The specified file already exists. Also. Invalid refresh state returned. Enter a number equal to or less than 230. You did not select a source control application before you clicked OK in the Source Control tab. Use a different name or rename the original object. there was a failure to load the server objects that the user is permitted to see. Also. This functionality is disallowed with AR System integration. if you are copying the file to a location. there was an error in creating the file on AR System server or in the location you specified. check your permissions. When creating or modifying an Open Window action. and then click OK. When retrieving the latest version of the file from source control. you tried to set the rows displayed in a form to a number larger than 230. Developer comments are required for this operation. The object is added to source control. but an invalid status was returned. 2850 Error No matches found in the database for the given query. 2851 Error 2861 Error 2862 Error 2863 Error 140 Error Messages Guide . Error creating the file. you used the name of an object that already exists. Do you want to create it? You tried to retrieve an object from a source control database that does not exist on the AR System server. The number of rows exceeded the maximum allowed limit of 230. first select a provider from the Provider Name drop-down list. Missing target location text. 2844 Error 2845 Error 2846 Error 2847 Warning 2848 Error 2849 Error Failed to load serverObjects from server serverName. Click Yes to create the object. To enable source control integration with AR System.00 2843 Error The specified file does not exist. You tried to refresh the status of an object from the source control database. Please select a source code control provider. for example. Objects might have been deleted or the names modified. no results were returned. Please enter a comment. Add the required comment. In the Display tab of the Field Properties window. checking a distributed pool in to source control. When the system searched the Search Objects window for an object.

contact your BMC sales representative.AR System error messages 2864 Error 2865 Error 2866 Error 2867 Error Error: No sample server has been selected. Enter or select a form view to continue. you did not specify a set of field/value mappings. Cannot add file. The Create Directory function failed while deploying an application or a form. When creating or modifying an Open Window action. When creating an application object. you did not specify a sample form name. Cannot delete root element. Enter a sample form to continue. for example. When creating an application object. This version of the BMC Remedy AR System has a maximum limit of 2000 requests per database table. BMC Remedy Administrator lets you save the action. and is configured for each client to access a maximum of one server. Directory depth exceeds the maximum allowed limit. there was a failure importing some of the objects. To obtain a version of BMC Remedy AR System without these limitations. you cannot delete or change the name of the Resources Directory Structure level under the Support Files tab. When using the Advanced functionality for an Open Window action. When using the Advanced functionality for an Open Window action. the directory is removed from the directory structure the next time you open the application object. and retry the import operation. This error can error because of one of several reasons. you need to specify a unique alias value.bmc. Create a set of field/value mappings to continue. or invalid directory name. When creating an application object. Warning: No field mappings have been defined. Error: No view has been selected. or visit http://www. To continue. Some items failed to import. This version of the Action Request System is ready for use or evaluation without purchasing or activating an authorization key. such as no disk space. For unlimited capabilities. When creating an application object. 2868 Error 2871 Error 2872 Error 2873 Error 2874 Error 2876 Error 2877 Note 2878 Error Alias values must be unique. File already exists in the current directory.bmc. When creating or modifying an Open Window action. by trying to access them in the source control client. Error: No sample form has been selected. but the action does not function properly. If you are successful. Chapter 2 Action Request System error messages 141 . you cannot add more than 255 support files to the current directory. Could not create the directory. verify that you have access to the objects in the source control database.com. Please select an item before creating the directory. log back in to BMC Remedy Administrator. During an import operation from source control. If you do not add support files to the new directory. you cannot add a support file to your application that already exists in the current directory. you did not specify a sample server name. you did not specify a form view. an authorized reseller. contact your sales representative or visit http://www. includes a maximum of three fixed licenses. you cannot create a directory before selecting a support file. Enter a sample server to continue. duplicate directory name.com. The operation is only partially successful. When adding localized text in the Alias Value field.

However. As a workaround.x workflow still functions. 2881 Error Error in converting to Open Window action. However.x workflow still functions. you could create new active links that use the 5. Number of resultant actions exceeded the maximum. please decompose the active link into multiple active links and try again.x workflow still functions. and then retry the macro conversion.BMC Remedy Action Request System 7.x (or later) workflow functionality. you can manually create a workflow action as a substitute for your BMC Remedy User macro used in workflow. divide the old active link functionality into multiple active links. Your pre-5. AR System was successful in converting the existing macro functionality to a new set of active link actions. contact your AR System administrator for assistance in modifying this packing list. Error in converting modify to Push Fields action. AR System could not convert the existing macro functionality to its equivalent 5. Error in converting to Run Process action. Succeeded. Your pre-5. AR System could not convert the existing macro functionality to its equivalent 5.x (or later) Open Window action. Error in converting to Run Process (Preferences) action.x (or later) workflow functionality.5.x (or later) macro conversion tool. To continue. you did not first save the contents of the web view to the server. Your changes to this packing list in your role as a subadministrator might result in loss of data. Your pre-5. AR System could not convert an existing macro to a new active link action. 2882 Error 2883 Error 2884 Error 2885 Error 2886 Error 2887 Error New Action cannot be inserted. AR System could not convert the existing macro command preferences (found in the Desktop preferences) to its equivalent 5. AR System could not convert a keyword used in a macro command to its equivalent 5. as a workaround. Your pre-5. AR System could not convert the existing macro functionality to a new set of active link actions. as a workaround.x workflow still functions. Error in converting a macro command. Otherwise. as a workaround. To use the 5. However.x (or later) Run Process action. The maximum number of new actions that can be created is 25. To enable successful conversion.x (or later) Push Fields action.x (or later) Run Process action. you can manually create a Run Process action as a substitute for your BMC Remedy User macro used in workflow. you can manually create an Run Process action as a substitute for your BMC Remedy User macro used in workflow.x workflow still functions.00 2879 Error 2880 Error Modifying Packing List may result in loss of data. as a workaround. When you were saving the application to disk in BMC Remedy Administrator. create a new active link that uses the 5.x workflow still functions. as a workaround. Your pre-5. the active link will not be saved. Your pre-5. However. AR System could not convert the existing macro functionality to its equivalent 5.x (or later) workflow action. you can manually create an Open Window action as a substitute for your BMC Remedy User macro used in workflow. Web view is created but not initialized! Please initialize the web view by opening and saving the web view. you can manually create a Push Fields action as a substitute for your BMC Remedy User macro used in workflow. 2888 Error 142 Error Messages Guide . However.

No key field specified. As a workaround. create a new active link that uses the 5. platform. As a workaround. In the Password Administration tab of the AR System Administration: Server Information form. create a new active link that uses the 5. you did not specify a unique table column to be used as the “key field. select a unique table column to be used as the key field. This problem might also affect your pre-5.x (or later) workflow actions.x workflow. There is already another view with the same alias. Your web alias started with a characters that was not alphanumeric. 2892 Error Failed to convert QBE into equivalent qualifier structure. Please specify a key field for this form.AR System error messages 2889 Error Server is referred by a keyword or field ID.x (or later) workflow functionality.x (or later) workflow actions. Conversion Complete. As a workaround. 2890 Error Could not connect to QBE referred server. you tried to enter a port. Your pre-5. Alias must contain alphanumeric characters only. password. 2891 Error Could not load the form specified by QBE.x (or later) workflow functionality.x (or later) workflow actions. create a new active link that uses the 5. 2901 Error Chapter 2 Action Request System error messages 143 . because the qualification used in the macro used a form that could not found and loaded. As a workaround. or RPC program number before you entered a server. and locale. Alias should start with an English alphabet. AR System could not convert a macro that contained the $Server$ keyword to an equivalent qualification used by the 5. This problem might also affect your pre-5. Server name should be currently available to process QBE type of queries.x workflow still functions.x (or later) workflow actions. because one of the macro action is not supported. AR System could not convert the macro to an equivalent qualification used by the 5.x (or later) workflow functionality. create a new active link that uses the 5. create a new active link that uses the 5.” This key field functions as the equivalent to the Request ID field in a regular AR System form. As a workaround. Use only alphanumeric characters in your alias.x (or later) workflow functionality. 2894 Error 2895 Error 2896 Error 2897 Error 2898 Error 2899 Error You must first specify a server. and locale combination.x (or later) workflow functionality.x workflow. When creating a View form. platform. In the View Properties window. AR System could not convert the macro to an equivalent qualification used by the 5. AR System could not convert the macro to an equivalent qualification used by the 5. At least one macro command is not supported. To continue. you tried to create more than one view with the same web alias. To continue. because the qualification used in the macro used a server that could not be found. AR System could not convert the macro to an equivalent 5. Server name should be currently available to process QBE type of queries. Begin your alias with alphanumeric characters only. AR System was 100% successful in converting the existing macro functionality into a new set of active link actions. Your web alias contained characters that were not alphanumeric. Only one view per form is allowed this unique set of features. Form name should be currently available to process QBE type of queries.x (or later) workflow action. enter a server name first.

a Flashboards server object). in the Explore window) to continue. To continue. However. you did not specify the names of database tables associated with the vendor. 2903 Error 2904 Error 2906 Error 2907 Error 2910 Warning 2911 Warning Form and some web views do not have WebAlias property. you did not specify a field type under Field Details. Without a web alias for a form’s web view. for example. enter a web alias. you cannot deploy a form to the web. You tried to create a web view without a web alias. When creating a Vendor or View form. Some web views do not have WebAlias property. You tried to perform a save operation on a form without first creating a web alias. There was a failure to access a file when making a link. 2916 Error 2917 Error 144 Error Messages Guide . To continue. When creating or saving a Data Dictionary menu type.5 (or later). To continue. When creating a Vendor form. 2913 Error Please install Internet Explorer 5. Please specify web alias. to where an external image is stored. You might also see this error message when performing a command-line bulk conversion of the form layouts.00 2902 Error No table name specified. The web view of your form cannot be opened because it requires Microsoft Internet Explorer 5.5. you did not select a database table name. This may result in invalid . This database table provides the external data used in the creation of an AR System form. select and load a table name. 2914 Warning 2915 Error The selected extensions will be deleted. This may result in invalid . Click Yes to continue the delete operation. to the folder where an external image is stored. To continue. There was a failure to create a directory when making a link. Without a web alias for a form’s web view. To continue. Without a web alias. Verify that you have access to the file (for example. You have attempted an action which requires this component. No vendor name specified. You tried to create a Status History field (a character field with a field ID of 15) in a view or vendor form. Specify a field type to continue. Please specify a vendor name for this form. Verify that you have access to the file (for example.5 or later version to proceed further.BMC Remedy Action Request System 7. for example.jsp file names after deployment. select a vendor name.jsp file names after deployment. Please specify a table name for this form. enter a web alias. You cannot create the following core fields in view or vendor forms. you cannot deploy the form to the web. enter a web alias. When creating or saving a Data Dictionary menu type. in the Explore window) to continue. You are about to delete one or more custom server objects (for example. Directory directoryName creation failed. you cannot deploy the form to the web. you did not select an object type. You tried to create view properties without entering a web alias. the Status History field is the only system-generated core field not allowed in the view or vendor forms. The file fileName does not exist. Please select object type. Please enter field type. These database tables are connected to data sources exposed by an ARDBC plug-in. Specify an object type to continue.

Field specified in assignment structure is missing in the schema. tries to convert the other macros. and retry the conversion process.5 or later cannot be found. and retry the conversion process. remove the unsupported commands (login-related macro commands) or repair the incorrect syntax in the commands. repair the macro appropriately.jsp file name for its web views. To continue. for example. see Error 2927. When the Macro Conversion utility was used. repair the macro appropriately. In the Configuration tab on the AR System Administration: Server Information form. the AR System administrator configured this server to disable admin operations. You do not have access to certain view functionality because Microsoft Internet Explorer 5. CCSSchema could not be loaded. Error in saving active link. however. an error in saving the active link occurred. 2922 Error 2923 Error 2924 Error 2925 Error 2926 Error Chapter 2 Action Request System error messages 145 . reset the configuration settings.5 (or later) is not installed on your system. Active link could not be converted successfully. see Error 2927. remove the unsupported commands (login-related macro commands) or repair the incorrect syntax in the commands. install Internet Explorer 5. an internal error occurred when a string was transformed to its equivalent assignment structure (ARAssignStruct). tries to convert the other macros. Portions of the BMC Remedy Administrator will not be available until it is installed. When the Macro Conversion utility was used. a failure converting the macro into its equivalent active link functionality occurred. No new objects can be created. When the Macro Conversion utility was used. For a workaround. To continue. see Error 2927. 2920 Warning 2921 Error Form must have web alias to generate valid . see error message 2927. For a workaround. for example. For a workaround. however. To continue. Original Active Link is restored. To continue. To continue. install Internet Explorer 5. see Error 2927. create a web alias. Administrator operations are disabled for this server. 2919 Warning Internet Explorer 5. an internal schema error occurred when the macro was converted into its equivalent active link functionality. To continue. The conversion. You tried to create a web view of a form without supplying a web alias.AR System error messages 2918 Error Internet Explorer 5. For a workaround. The conversion. an internal error occurred when a value was converted to its equivalent assignment structure (ARAssignStruct). When the Macro Conversion utility was used. When the Macro Conversion utility was used.5 or later cannot be found. You do not have access to important functionality in BMC Remedy Administrator because Microsoft Internet Explorer 5. Cannot create new objects. This functionality will not be available until it is installed.5 (or later) on your system.5 (or later). Value assigned to field cannot be converted to equivalent AR structure. For a workaround.5 (or later) is required for application initialization.

the administrator can see $fieldid$ by directly editing the Open Window action. verify that it is valid. 2928 Error 2929 Error 2930 Error 2931 Error Error in converting AR System Report’s keyword.5.00 2927 Error The following description lists active links and indicates nature of failure or success under each RunMacro action. An error indicating that the QBE query could not connect to the server. Cannot find server ARSystemServer. The schema and server names are represented by $field-id$. Workaround: Verify that the fields are display fields. An error indicating that the QBE cannot be loaded might indicate that the schema is unavailable. When editing the Open Window action. You tried to perform a source control operation on a custom server object (for example. Error in creating or opening of temporary AR System Report file. Possible server alias name problem. the database does not contain any associated values. original active link will be restored. These values can be replaced with specific values for conversion. Users can see the FAQ for resolutions and try again. an error occurred during HTML file generation because of nonexistent fields in the web view of the form. a Flashboards server object). This functionality is disallowed with AR System integration. Verify that the conversion of the query string to a qualifier is correct. 2932 Error 2933 Error Source Control operations cannot be performed on Extension Objects. To continue. See the following workaround. an internal error occurred when the AR System report command in the macro was converted. allowing the schema and server names to be edited. During import operation. After successful conversion. the objects could not be imported because: The object iteration was not constructed properly.BMC Remedy Action Request System 7. Error in finding report’s end. In case of failure. Workaround: The schema and server names are not available to queries and can be validated. The server name alias embedded in the object could not be resolved properly. Field with ID IDNumber is not present in this form. and should be available to process QBE queries. Because your query is on field values in database and display fields. When you used the Macro Conversion utility. an internal error occurred when the temporary AR System Report file in the macro was created or opened. 146 Error Messages Guide . an internal error occurred when the end of the AR System report in the macro was converted. delete the field. If you are using a server name alias. Looks like a corrupt field. the administrator must choose the Advanced option. When you used the Macro Conversion utility. The following errors frequently occur when macros are converted to active links: An error indicating that the qualifier could not be loaded might indicate (1) that specified fields are not present or (2) that the field labels are referred to in the macro query but the conversion process expects the field database names. Would you like to delete this field? When an application was deployed. The server is referred to by a keyword or field ID. This corruption might be due to the user hard coding a new field in the form. When you used the Macro Conversion utility. See the following workaround. Display fields should not be in a QBE and are ignored during conversion. Another error that occurs when macros are converted is that the query is converted but some field/value pairs that were present in the QBE part of the query are missing.

Source control applications return this error message. You tried to perform a source control operation on an object checked out to another user. start the source control application and verify that the source control project exists on your system. You tried to perform a source control operation on a file exclusively locked by another user. Source control applications return this error message. wait until the object is checked in. Error from Source Control Provider—Unknown project. by opening it in the source control client. Source control applications return this error message. You cannot modify an object under source control unless you check it out first. You tried to perform a source control operation on a locked file. Error from Source Control Provider—Check in conflict. You failed to access a file because it is not under source control. delete the file from the source control database first. Error from Source Control Provider—Initialize failed. The source control engine failed. When creating an application object. You cannot add this file to source control because the file already exists. verify your permissions and that the support file exists and is not corrupted. you lose history data. Error from Source Control Provider—Already checked out. Error from Source Control Provider—File out exclusive. The project name is a local directory of . To continue. You failed to check the object in to source control because of a conflict between you and another user. To prevent this happening in the future. Error from Source Control Provider—File is locked. 2936 Error 2937 Error 2938 Error 2939 Error 2940 Error 2941 Error 2942 Error 2943 Error 2944 Error 2945 Error 2946 Error Chapter 2 Action Request System error messages 147 . To continue. verify that you have access to the project. Error from Source Control Provider—Access failure. To continue. The source control project could not be located. To continue.def files on your system. Source control applications return this error message. Also. Error from Source Control Provider—Could not create project. To continue. set the source control project in AR System server to Enforced mode. To continue.) Error from Source Control Provider—File not controlled. Source control applications return this error message. To continue. The source control project could not be created. (When removing the object from the source control database. verify that you can start the source control executable independently of BMC Remedy Administrator. for example. Source control applications return this error message. Source control applications return this error message. confirm whether some other user is accessing the file. check out the object. You failed to access a file in use by another user.AR System error messages 2934 Error Could not open file: fileName. Error from Source Control Provider—Not checked out. To continue. To continue. confirm whether some other user is accessing the file. verify your permissions. you cannot open the support file that you wanted to add to your application. Source control applications return this error message. add the file to the source control database. To continue. Source control applications return this error message. Source control applications return this error message. Error from Source Control Provider—File already exists.

The file merge operation failed under source control. Source control applications return this error message. Error from Source Control Provider—Requested operation not supported. Source control applications return this error message. Source control applications return this error message. You failed to access this file because it contained no specific version history in the source control database. You are not a recognized user in the source control database. Source control applications return this error message. Source control applications return this error message. Error from Source Control Provider—Project not open. Error from Source Control Provider—Invalid user. 2948 Error 2949 Error 2950 Error 2951 Error 2952 Error 2953 Error 2954 Error 2955 Error 2956 Error 2957 Error 2958 Error 2959 Error 2960 Error 148 Error Messages Guide . Source control applications return this error message. Source control applications return this error message. Error from Source Control Provider—Project already open. You failed to check out this file because it is checked out to another user. Error from Source Control Provider—Requested operation not performed. Error from Source Control Provider—Verify merge. There was an unspecified project syntax error displayed by the source control application. Contact the other user if possible to resolve any administrative issues. open the project first. You failed to access this file because this operation was not performed by your source control application. Error from Source Control Provider—Shell Failure. Error from Source Control Provider—Type not supported. Source control applications return this error message. Error from Source Control Provider—Fix merge. Error from Source Control Provider—Invalid file path. The file merge operation failed under source control. You tried to open a source control operation on an object that was already opened by you or another user. Verify that an account was created for you and that you have permission to access the source control database. You failed to access this file because this operation is not supported by your source control application. Source control applications return this error message. To continue. You could not access files in your source control project because of an invalid file path.00 2947 Error Error from Source Control Provider—File is checked out.5. examine the version history of AR System objects under source control. This file type is not supported under source control. To continue. verify the correct file path. Error from Source Control Provider—Non-specific error. Error from Source Control Provider—Project syntax error. Source control applications return this error message. Source control applications return this error message. You tried to access a file from a source control project that was not open. To continue. An unspecified error was returned in your source control provider that was not covered under any specific error conditions. Use your source control application to repair the file merge.BMC Remedy Action Request System 7. Source control applications return this error message. Error from Source Control Provider—No specified version. Source control applications return this error message. An unspecified shell failure was displayed by the source control application. Source control applications return this error message.

The name will not be modified.AR System error messages 2961 Error 2962 Error 2963 Error 2964 Error 2965 Error 2966 Error 2967 Error 2968 Error 2969 Error 2970 Error 2971 Error 2972 Error 2973 Error 2974 Error 2975 Error 2976 Error 2977 Error Error from Source Control Provider—Not authorized. You tried to map the fields before you mapped the form. There was a failure to connect to the source control application. Objects are not mapped. You did not define a single digit of numeric precision (for example. You tried to access a file that does not exist under source control. Error from Source Control Provider—File syntax error. or left the currency code field blank. Please enter a unique name for operation. Source control applications return this error message. Source control applications return this error message. Source control applications return this error message. You entered an invalid currency code in the Currency Codes preferences. You created a duplicate mapping. You created a duplicate operation name in the Operations List. Source control applications return this error message. Rename operation failed on the Source Control Provider. All operation names must be unique. Please enter a single digit numeric precision. Please select at least one Functional Currency. There was an unspecified file syntax error displayed by the source control application. No objects are mapped. Please enter a valid 3 digit Currency Code. Name should start with an English alphabet. One or both of the objects have already been mapped. Error from Source Control Provider—Connection failure. Cannot create or modify a Currency Field without at least one selected Functional Currency. The web services name does not use English alphanumeric characters. Error from Source Control Provider—File does not exist. Format of date value is not recognized. numbers 1 to 9) for the Currency Codes preferences. Duplicate Operation Name. You did not select a functional currency list. Unmap and continue. Duplicate Operation Name. Incorrect precision. The rename operation failed. Your mapping is invalid. Form should be mapped before the fields. All operation names must be unique. Mapping cannot be defined. Objects selected do not have the same map. Source control applications return this error message. You tried an operation not authorized by your source control engine. Chapter 2 Action Request System error messages 149 . You modified an operation name but the operation name is not unique. Incorrect currency code. The web services mapping is not unique. The value of a time stamp was incorrectly converted for a date type field.

the primary key should be mapped. You did not map any of the choice nodes in a XML schema. If username and password are mapped. and try creating a new one. At least one choice is not mapped in the mapping object. All the choice nodes have to be mapped for the web service to work properly. Unmap and continue. WebService Handler is using an insecure (http) protocol. This mapping is not supported. Primary key is mapped. Primary key is not mapped. 2988 Error 2989 Error 2992 Error 2993 Warning 2994 Error 2995 Error 2996 Error 2997 Error 2998 Error The Database Name for a Flashboard field must not be NULL. In a multi-layered XML schema with a parent-child relationship. The XML element selected has maxoccurs greater than 1. You cannot create a web service that has no operations. One or more of the immediate children under the choice/all node are mapped to a different form. A field other than the Request ID (1) is used as the primary key but not mapped to any element in the XML schema. 2984 Error 2985 Error 2986 Error 2987 Error Web service cannot be saved without any operations. When creating a view form. The primary key should not be mapped. This mapping is not supported. Delete this operation. The web services name is empty. Map and continue. you cannot leave the Name field in the Database tab (in the Field Properties window) empty. Please delete the current operation and continue. Any critical information (for example. Enter at least one operation in the operations list. The distinguishing key in a child form is not mapped. The mapping you created for the web service operation is corrupt. Cannot create or modify a data field without specifying a corresponding DB column name. Enter a name for the field. The primary key of the parent form was mapped. passwords) are not properly encrypted. Cannot create or modify a display-only field which has a valid DB column name. 150 Error Messages Guide . When creating a view form. Foreign Key(s) is mapped. you cannot link a display-only field to an underlying database column. One or more of the fields selected as foreign keys in the child forms are mapped. The web service you are consuming is not secure. you cannot map a field in a web service object from one form to an XML element whose top-level form mapping is done with another form.00 2978 Error 2979 Error Name must contain alpha numeric characters only. Form mapping under a choice node or a complex element of type all is not supported. When creating or modifying a Flashboard field. you must link data fields to an underlying database column. they will be sent in plain-text. This mapping object is corrupted.5. Please specify a valid DB column name. A field cannot be mapped more than once. Distinguishing key(s) is not mapped. Please specify a valid entry mode.BMC Remedy Action Request System 7. If field ID is not 1.

The AR System Distributed Server Option was previously unable to connect to the AR System server. AR Datatype . The number following this error denotes the signal that was received. If the signal is 15. A subsequent connection attempt succeeded. the field is updated to the status Canceled. and the process was shut down. An error occurred while the system tried to transfer or update a request. which is specified in the Modify Distributed Mappings form or overridden in the distributed fields on the actual request. nonNegativeInteger. and rerun the server. Fix the problem.lck. Contact your distributor for information about obtaining a DSO process license. The request is removed from the pending list. Pending distributed operation canceled due to error. This scenario is possible when the Distributed Server Option is started before the AR System server is ready to accept connections.Character can only be mapped to XML Datatype . contact Customer Support for assistance in determining the cause of the problem. The AR System Distributed Server Option cannot connect to the AR System server. 3000 Note 3001 Note 3002 Note AR System Distributed Server terminated—fatal error encountered. A license for the DSO process is required to use the distributed functionality of the system. A fatal error occurred in arservdsd. 3003 Note 3004 Note 3005 Note 3100 Error The AR System is not licensed for the Distributed Server Option. AR System Server is now available. If the request has a Transfer or Update Status distributed field.390601 at startup. You tried to map incompatible data types. an associated error message is generated and no further attempts are made. An associated error message contains details.string. The process was stopped either accidently or intentionally by a user in your environment.AR System error messages 2999 Error Invalid mapping because of incompatible data types. If the signal is a number other than 15 or is one you sent directly to the process. negativeInteger. The server most likely shut down due to a bug in the system. or positiveInteger. nonPositiveInteger. AR System Server is not currently available—will retry connection. 3101 Error Chapter 2 Action Request System error messages 151 . integer. Entry pending transfer or update has been pending for longer than the specified retry timeout. AR System Distributed Server terminated when a signal was received by the server. the field is updated to the status Time-out. Error while opening the Distributed Server lock file. and continue to work. An associated file system error message contains details. The connection attempt is retried periodically for several minutes. If a Transfer or Update Status field is on the request. If repeated connection attempts fail. The server for the DSO process (arservdsd) was terminated by a signal. A request pending transfer or update was in the pending state for longer than the Maximum Time to Retry interval. An associated error message contains details. AR System DSO process (arservdsd) opens a lock file named ar. restart the server. and the operation is not performed. This file is used to prevent multiple copies of arservdsd from being started. arservdsd cannot be run unless the system is licensed for it.

The system found two forms containing the reserved distributed mapping fields. The server defined as the From server does not match the server that is the source of this transfer. A Distributed Mapping form is required for the system to support distributed operations. delete the lock file to free the lock. The two forms are identified in an associated error message. You must delete one form or change it so that it is not considered a Distributed Pending form (remove fields in the 250 to 260 range). Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while. Typically. 3106 Error 3107 Error 3108 Error 3109 Error 3110 Error 3111 Error 3112 Error 3113 Error 152 Error Messages Guide . 3103 Error Malloc failed on Distributed Server. The system encountered an error during a call to allocate space. No Distributed Mapping form could be found on the server. No form containing all the special reserved fields indicating it is a Distributed Mapping form could be found. and then restart arservdsd. The server being accessed is not licensed for the Distributed Server Option. In general. From form in mapping definition is different from the source form in the attempted mapping. no action is required. this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server. The system found two forms containing the reserved distributed pending fields. If another DSO process is running. The form defined as the From form does not match the form that is the source of this transfer. and define the appropriate mappings. No form containing all the special reserved fields indicating it is a Distributed Pending form could be found. A computer can run only one instance of the DSO process at a time. Two forms contain all the reserved distributed pending fields—delete one to continue. or change it so that it is not considered a Distributed Mapping form (remove fields in the 200 to 220 range). this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server. You must delete one form. From server in mapping definition is different from the source server in the attempted mapping. To form in mapping definition is different from the target form in the attempted mapping. this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server. The failure occurred on the server in the DSO process. The form defined as the To form does not match the form that is the target of this transfer. The two forms are identified in an associated error message.5. Load the Distributed Pending form.00 3102 Error Another copy of the Distributed Server is already running. If no arservdsd is running. Two forms contain all the reserved distributed mapping fields—delete one to continue. this error occurs when too many processes are running or when certain processes occupy most or all available memory on your server. Typically. A Distributed Pending form is required for the system to support distributed operations.BMC Remedy Action Request System 7. Typically. The arservtcd process might be on a target server that is not licensed to use the DSO process or on a version 2. you probably encountered a known problem with the NFS lock manager on Sun workstations—the lock manager sometimes keeps a lock running even when the process holding the lock is no longer running. No Distributed Pending form could be found on the server. Load the Distributed Mapping form.0 or earlier target server that does not interact with arservdsd. If another DSO process is not running.

contact Customer Support. This error should occur only if you manually added requests to the Distributed Pending form. Thus. arserverd received a request to record a distributed command or encountered a situation in which it tried automatically to record a distributed command. This information is stored with the pending operation. A pending request with the pending operation tag set to an unrecognized value was found. you must make sure that there are also values assigned for the From Form and the From Server fields (you can also change these by using ardist). The attempted command is displayed in this message. Unrecognized pending type. the error is created—because the request against which the distributed process is run no longer exists. the distributed process waits for the operation to be completed. The distributed operation being attempted expected additional information which is not present. Remove or disable the filter attempting the distributed operation. When a distributed process begins. An associated message contains details. Only the master copy of an entry can be transferred. and a failure occurred during recording. the target form does not have a From Request ID field. the operation cannot be performed.AR System error messages 3114 Error To server in mapping definition is different from the target server in the attempted mapping. Distributed-Update. which is a system form that should not be manually manipulated. The server defined as the To server does not match the server that is the target of this transfer. If you made no manual requests to the Distributed Pending form and encounter this error. If you encounter this message. The From Form and From Server fields contain information about the previous copy of this request (from where the request was transferred). which is a system form that should not be manipulated manually. A specific mapping was specified on the entry and is currently disabled. A filter invoked a distributed process (Distributed-Transfer. so the transfer or update cannot be performed. If you used the ardist program to manually change the Master Flag value. pass the request as data only. Failure during an attempt to perform a distributed command. the system expects a value in the From Form and the From Server fields. The specified mapping is disabled. this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server. DistributedReturn) during the deletion of a request. You tried to transfer a request to the target form with ownership transferred to the new request. However. This error should occur only if you manually added requests to the Distributed Pending form. Chapter 2 Action Request System error messages 153 . Specified “Create New” as the action if duplicate entry IDs are encountered during transfer— target form is missing the required From Entry ID field. contact Customer Support. Update unsuccessful—From Form or From Server field has no value. If you must retain ownership on the original. but the Master Flag field on the request is set to No. or reset the filter so it does not execute on a delete operation. 3115 Error 3116 Error 3117 Error 3118 Error 3119 Error 3120 Error 3121 Error 3122 Error Cannot specify a distributed operation during a Delete of an entry—the delete of the entry and the distributed operation canceled. which is required for this action. thus creating a new request due to ID conflict. the required additional data is missing. The From Request ID field provides a place to store the original ID of the request so the original can be updated when the copy changes. You can only transfer the master instance of a request. Typically. A transfer was attempted with mapping defined in the To Mapping (or From Mapping for an update) field. The Distributed Delete operation requires information about the item being deleted. the distributed command was not performed. If you made no manual requests to the Distributed Pending form and you encounter this error. The system tried to transfer the specified request. If the Master Flag is set to Yes. If a delete operation is in progress. Without this data.

Fix the mapping. Illegal value specified for -m option—legal values are 0 (not master) and 1 (master).00 3123 Error Must map the Entry ID field to the target Entry ID field. The value specified for the -m argument was not 0 (not master) or 1 (master). The two forms are identified in an associated error message. and specify a legal value for this argument. or the From Entry ID field must be present on the target form. You tried a distributed transfer operation using a mapping to another form with transfer mode of Data + Ownership. Two forms contain all the reserved distributed pending errors fields -. The value specified was either a character or an integer other than 0 or 1. No Pending Errors form could be found on the server. The source form does not contain a Master Flag field. The source form (identified in the error) must contain a Master Flag field if ownership is being transferred.BMC Remedy Action Request System 7. You tried a distributed transfer operation by using a mapping to another form with a transfer mode of Data + Ownership. 3125 Error 3126 Error 3127 Error 3128 Error 3129 Error 3130 Error 3131 Error 3194 Error 3195 Error 154 Error Messages Guide . You tried a distributed transfer operation to another form by using a custom mapping with a transfer mode of Data + Ownership. and retry the transfer. and the target form does not contain a From Form field. A Distributed Pool form is required for the system to support distributed operations. No Distributed Pool form could be found on the server. and the target form does not contain a Master Flag field. The target form (identified in the error) must contain a From Form field if ownership is being transferred. You must delete one form. Transfer with ownership requires that target form contain From Form field. A Distributed Pending Errors form is required for the system to log pending errors to that form. Transfer with ownership requires that target form contain From Server field. You did not map the Request ID field on the source form to a From Request ID field on the target form. Must specify the -e {entryID} option.delete one to continue. No form containing all the special reserved fields indicating it is a Distributed Pending Errors form could be found. You must specify the -e argument to denote the ID of the request (entry) to be modified. The field is a selection field and requires a numeric value. 3124 Error Transfer with ownership requires that target form contain Master Flag field. The system found two forms containing the reserved distributed pending errors fields.5. You tried a distributed transfer operation by using mapping to another form with a transfer mode of Data + Ownership. Reissue the command. and the target form does not contain a From Server field. as required. You must map the Request ID field on the source form to one of these fields on the target form. The two forms are identified in an associated error message. Transfer with ownership requires that source form contain Master Flag field. You must delete one form or change it so that it is not considered a Distributed Pending Errors form. and one of these conditions exists: You did not map the Request ID field of the source form to the Request ID field of the target form. The system found two forms containing the reserved distributed pool fields. The target form (identified in the error) must contain a From Server field if ownership is being transferred. Two forms contain all the reserved distributed pool fields—delete one to continue. The target form (identified in the error) must contain a Master Flag field if ownership is being transferred. No form containing all the special reserved fields indicating it is a Distributed Pool form could be found. A distributed transfer operation was attempted that included a mapping to another form with a Data + Ownership transfer.

An associated error message contains details. The server could not successfully import the Alert Events form at startup. You included an argument with no specific value on the ardist command line. The two forms are identified in an associated error message. Turn on alert logging to view a trace of the communication activity. The server could not locate a form containing the reserved alert events field. Turn on alert logging to view a trace of the communication activity. Timeout occurred attempting to communicate with alert client. Must be AR_NOTIFIER user to perform this operation.AR System error messages 3196 Error 3197 Error 3198 Error 3199 Error Must specify the -s {form} option. A failure occurred while the system tried to decode an alert message sent from the server to an alert client. You must specify the -s argument to denote the name of the form to be modified. See the Distributed Server Option Guide for more information about valid command line arguments. indicating a data transmission error. This can occur on a system that is not releasing address/port combinations in a timely manner. ardist cannot execute with invalid arguments specified. An attempted communication with an alert client did not succeed within the configured time period. A value is expected for the command line option. The server does not allow the removal of the Alert Events form or its reserved fields. A sockets error occurred while the system tried to establish communication with an alert client. Error occurred prior to connection attempt with alert client. Error occurred attempting to communicate with alert client. Address in use error occurred attempting to communicate with alert client. Invalid alert message format. Two forms contain all the reserved alert event fields -. An associated error message contains details. Must specify the -x {server} option. There was an error while trying to establish the connection with the BMC Remedy Alert client. The server could not successfully import the CleanupAlertEvents escalation at startup.delete one to continue. The most common reason for this error is a network connectivity issue. When attempting to send an alert to a client. You must delete one form. Reissue the command with values assigned to all arguments. Failed to load the alert cleanup escalation. The specified command-line argument is not recognized by ardist. No Alert Events form could be found on the server. Problem encountered during creation of the Alert Events form. You must specify the -x argument to denote the name of the AR System server containing the form to be modified. Unrecognized command line option. 3300 Error 3301 Error 3302 Error 3303 Error 3314 Error 3315 Error 3316 Error 3317 Error 3318 Error 3319 Error Chapter 2 Action Request System error messages 155 . Re-try the operation. the AR System server encountered a socket address that the system was still using. Turn on alert logging for more information about the server actions taken. The system found two forms containing the reserved alert events fields.

The AR System Server Group Operation Ranking form definition could not be imported. A floating license specification was ignored because it is not allowed to have a server group tag. Unrecognized server group operation encountered in the ranking form. Contact your AR System administrator. An error occurred during the creation of a server group entry in a data dictionary table. The AR System server encountered a floating license definition that was ignored because a server running as a member of a server group accepts only licenses that have a server group tag.00 3320 Error Two forms contain all the reserved server group fields -. Unable to find a server group entry for this server. The system found two forms containing the reserved server group fields. The specified check interval is below the minimum value of 30 seconds and has been set to 30. The AR System server encountered a floating license definition that was ignored because an AR System server not running as a member of a server group accepts only licenses that do not have a server group tag. It might take two restarts of the server to prevent the error from being reported when the operation is removed from the ranking form. You cannot set the check interval to a value of less than 30 seconds.BMC Remedy Action Request System 7. A floating license specification was ignored because differing server group tags were encountered The AR System server encountered a floating license definition that was ignored because an AR System server running as a member of a server group accepts only floating licenses that have the same server group tag. Make sure that all floating license definitions have the same server group tag. Contact your AR System administrator. remove the ranking entry for the corresponding operation from the AR System Server Group Operation Ranking form. A server group operation was found that the AR System server does not recognize. No server group operation ranking form could be found on the server. The setting of the configuration item is not allowed because it conflicts with server group operation management. Problem encountered during creation of the server group operation ranking form. if the operation is not appropriate in the current environment. Make sure that the specified program is present in the AR System server's directory. Check the server error log for the cause of the problem. which qualifies both forms as the AR System Server Group Operation Ranking form. Error Messages Guide 3321 Error 3322 Error 3323 Error 3324 Error 3325 Error 3326 Error 3327 Warning 3328 Error 3329 Error 3330 Error 3331 Error 156 . Replace the license definition with a license that has a server group tag. An error occurred during the automatic creation of the AR System Server Group Operation Ranking form. Unable to launch an agent process to communicate with an external program.delete one to continue. Make sure the arsignal utility program is present in the AR System directory. or. A value of less than 30 seconds was specified for the check interval. You must delete one form. Do not set the configuration item while the server is a member of a server group. Failed to start a server group related agent process. Failed to send a server group related signal to another server.5. Use only the supplied operation names. Replace the license definition with a license that does not have a server group tag. This configuration setting is not allowed when the server is a member of a server group. A floating license specification was ignored because it requires a server group tag. The two forms are identified in an associated error message. The AR System could not successfully run a signaling process.

Make sure that the arsignald executable is in the AR System server installation directory. A failure occurred while the system tried to get a temporary file name for a report definition.ordering cannot be guaranteed. 3341 Error 3342 Error 3350 Error 3351 Error 3352 Error Chapter 2 Action Request System error messages 157 . A value change is pending on the Check Interval setting -. Contact your AR System administrator. Unable to create arsignald start up info. Unable to locate Report form. This error is typically caused by the executable file not being in the same directory as the AR System server executable (possibly as an installation error). make sure the AR System server has permission to run the arsignald executable. Indicates that the AR System server was unable to start the arsignald process because it was unable to allocate memory for the required start up information. A duplicate server group operation ranking was encountered during loading of the ranking data. This is a warning that AR System must be restarted on all servers in the server group before a change in how often the server communicates with other servers in the group takes effect. because the AR System server attempts to restart arsignald if it detects a communications problem. The name of the operation is supplied as appended text. Invalid or missing server group license entry. An internal table containing server group license entries has an invalid entry or is missing an expected entry.change will take effect when all servers in the group are restarted. The report plug-in could not locate a form containing the reserved Report form fields. If this does not resolve the problem. Although this is not a fatal server error. 3340 Error Unable to start arsignald. Server group error indicating that the AR System server was unable to start the arsignald process. This error is caused by a broken communication pipe between the AR System server and arsignald. The ordering of duplicate values is not guaranteed to be consistent. 3336 Warning Duplicate server group ranking value encountered in the ranking form -. The Server Group Member option was changed and the new value does not take effect immediately. Additional information contains the file name. Unable to create temporary file for report definition file.change will take effect the next time the server is started. The AR System server must be restarted for the setting to take effect. managed by the AR System server. Arsignald is a small process. 3333 Error 3334 Error 3335 Warning Invalid or missing server group operation definition. Give the server more memory. Contact your AR System administrator. An internal table containing server group operation definitions has an invalid entry or is missing an expected entry. Unable to write to arsignal daemon. therefore you should change the ranking values to be unique. A failure occurred while the system tried to create a temporary file for a report definition. The situation should be corrected automatically. it is unlikely that the server will successfully start up when memory cannot be allocated. possibly caused by arsignald being killed or crashing. Unable to get temporary file name for report definition file. Indicates that the AR System server was unable to issue a command to the arsignald process. that is used for communication between members of a server group.AR System error messages 3332 Warning A value change is pending on the Server Group Member setting -.

External authentication endpoint URL not configured. Invalid report definition encountered. Only fields that map to individual fields on the Report form are allowed. Additional information contains the field number. The LDAP search URL does not follow the standard format. The specified LDAP URL is not formatted correctly. The sort list in a list retrieval contains fields that are not part of the report creation vendor form’s list of reserved or core fields.00 3353 Error Illegal field encountered in the field list. The qualifier in a list retrieval contains fields that are not part of the report creation vendor form’s list of reserved or core fields. The field list in a list retrieval contains fields that are not part of the report creation vendor form’s list of reserved or core fields. The LDAP operation was unsuccessful. Unable to initialize web service interface. The BMC Portal External Authentication plug-in could not locate an endpoint URL configuration item in the AR System server's configuration file. Verify that a line with the Ext-Auth-EndpointURL label is in the configuration file.BMC Remedy Action Request System 7. Illegal field encountered in the qualifier. an unexpected definition format prevented proper decoding. or authentication with the directory service failed.5. While the system tried to transfer data from a formatted report definition to the fields on the report creation vendor form. The field value list supplied to the report creation vendor form is missing a required field. Illegal field encountered in the sort list. The format is: ldap[s]://hostName[:portNumber]/ The LDAP operation has failed. 3402 Error 158 Error Messages Guide . Inspect the contents of the report definition file for the entry. because proper attribute names were not specified or the operation would violate access privileges enforced by the directory service. The BMC Portal External Authentication plug-in could not access the AR System server's configuration file. The host name or port number for the directory service is incorrect. Empty or NULL value encountered for the Distinguished Name attribute during a create operation. Verify that the server's configuration file is present and accessible. Cannot connect to the directory service. The distinguished name must have a value to create objects. See the supporting text for more information. Required report field is missing. The BMC Portal External Authentication plug-in could not initialize a web service interface to perform authentication. At least one field on the form must reference the Distinguished Name attribute At least one field on the form must reference the distinguished name attribute. for example. The field associated with the distinguished name attribute has no value. Only fields that map to individual fields on the Report form are allowed. Only fields that map to individual fields on the Report form are allowed. 3354 Error 3355 Error 3356 Error 3357 Error 3375 Error 3376 Error 3377 Error 3378 Error 3379 Error 3400 Error 3401 Error Unable to access server configuration file.

You must provide a name to save an alarm. You tried to save a flashboard that references a variable with collection interval end date and times that are greater than its start date and time. 3503 Error 3504 Error 3505 Error There are no variables in this server. You tried to save an alarm for which you did not specify a name. Please create a variable before creating an alarm. You tried to save a data source that does not contain any variables. You tried to save a flashboard without specifying a name. but in the Notify Properties area of the Configure Alarm tab. At least one data source is required to define a valid flashboard. You tried to save a data source without specifying a name. The BMC Portal External Authentication plug-in could not terminate a web service interface that was performing authentication. You must add at least one variable to save a data source. An alarm cannot be saved without selecting a variable. You must create a variable before you save the alarm. You opened or created a flashboard without a data source. Please provide a name for the alarm. The variable associated with this alarm has been deleted. You opened a flashboard when the variable was deleted. You tried to save a flashboard without first associating a data source with it. Please enter them. You tried to save an alarm. You tried to open an alarm that references a variable that no longer exists.AR System error messages 3403 Error 3501 Error 3502 Error Unable to terminate web service interface. Please provide a name for the flashboard. Select one from Configuration tab. You tried to save a flashboard with a maximum custom Y-axis value less than the minimum custom Y-axis value. See the supporting text for more information. End Date and Time should be greater than Start Date and Time. You tried to save a data source without assigning public permissions to it. You tried to save an alarm for which you did not select a variable. Maximum custom range can not be less than the minimum custom range. Provide a name for the data source. you selected a notify mechanism value other than None and you did not specify a user name and message. A variable should be associated for this alarm to work.only the administrator has access to this data source. Group access is not defined -. You must enter a user name and message. Select a data source with variables. No data source has been defined. The data source you selected does not contain any variables. One of more variables have been deleted from the selected datasource since this flashboard was saved. 3506 Error 3507 Error 3508 Error 3509 Error 3510 Error 3511 Error 3512 Error 3513 Error 3514 Error 3515 Error Chapter 2 Action Request System error messages 159 . You must create a new variable for this alarm. Please select a variable. You tried to create an alarm before you created any variables on the server. You tried to save a flashboard that references a data source that has no variables. You must associate a data source name with the flashboard.

Please provide a name for the Variable. you tried to change the data collection start time to be the same as or earlier than the end time. While working with a variable. was renamed. Group access is not defined—only the administrator has access to this Variable. Invalid Flashboard Data Source: Statistic and History Variables should not be mixed together. Re-create the flashboard. No forms found containing Flashboards field ID: fieldID Make sure that the form contains the correct fields. Check the data source type and modify. Invalid schedule interval. You did not add permissions to the variable. you specified data collection start and end times such that the data collection interval can only contain one data collection. While working with a variable. You must type an expression for this operation. You tried to save a variable without providing a name. Contact your AR System administrator. Internal error. If you modified the forms. Pie charts cannot be selected for History/Summary display type. You will have only one data collection in the specified interval. You did not add permissions to the flashboard. Group access is not defined—only the administrator has access to this Flashboard. you tried to change the data collection end time to be the same as or later than the start time. Pie charts are valid only for realtime data. Multiple forms contain Flashboards field ID: fieldID Do not modify the Flashboards forms. Work only with the forms provided. but set start and end times only one hour apart. To make sure that users can see the flashboard. add the appropriate permissions. While working with a variable.5. or was deleted. You cannot select the end time less than/same as start time. 3518 Error 3519 Error 3520 Error 3521 Error 3522 Error 3523 Error 3524 Error 3525 Error 3600 Error 3601 Error 3602 Error 3603 Error 3604 Error 3605 Error 160 Error Messages Guide . such as when you try to save a variable with an invalid schedule. if necessary. The flashboard was never created. if necessary. A system error occurred. you have the same field IDs in multiple forms.BMC Remedy Action Request System 7. add the appropriate permissions. The schedule interval is invalid. you could only have one data collection for that interval and start/end time combination. To make sure that users can use the variable. You tried to save a variable without specifying a form name. if you specified hourly collection. You tried to save a variable for which you specified an operation other than Count and an empty expression.00 3516 Error 3517 Error You cannot select the start time greater than/same as end time. Flashboard flashboard not found on server ARSystemServer. No forms found with the name: formName Check the name of the form and rename the form. For example. Please select form before proceeding. You tried to select a pie chart for a History/Summary display.

AR System error messages

3606 Error 3607 Error

Invalid Flashboard type. The type of flashboard is invalid for the action. For example, you might have tried to use an active link to change a line chart to a stack chart. Enter the correct flashboard type. The following parameter(s) needed to display the chart are missing: parameters. You may need to relogin to view the chart. The required parameters might be missing from the flashboard definition. Check the flashboard definition.

3608 Error

You have exceeded the allowed usage of Flashboards. Please obtain a license if you wish to continue using Flashboards. Review the license information in the BMC Remedy Flashboards Guide to make sure that you purchased a license, or contact Customer Support.

3609 Error 3610 Error 3611 Error 3612 Error 3613 Error 3614 Error 3615 Error 3616 Error 3617 Error 3618 Error 3619 Error 3620 Error 3621 Error 3622 Error

Error encoding image: imageName. A system error occurred. Contact your AR System administrator. Error sending image: imageName. A system error occurred. Contact your AR System administrator. General exception creating Flashboard. Contact Customer Support with a copy of the log statements for the action. User has no access permission to Flashboards data source dataSource. Permissions problem. Contact your AR System administrator. There was no valid Datasource for this Flashboard. The data source is either not associated with the flashboards correctly or does not exist. Check the flashboard definition. There was no valid Variable for this Flashboard. The variable is either not associated with the flashboards correctly or does not exist. Check the flashboard definition or create a new variable. Invalid chart type, valid numbers for a chart are from 0 to 5. Specify a chart type from 0 to 5. Internal error. A system error occurred. Contact your AR System administrator. Internal error. Form meta data is invalid. A system error occurred. Contact your AR System administrator. No history data was found in the AR System server to display this Flashboard. No history data was collected in the FB:History form for this flashboard. History data can not be displayed on a pie chart. History data can be displayed in all chart types except pie charts. To display history data, specify a different chart type. No user-customizable parameters have been defined. User-customizable parameters have not been defined for the flashboard. See your AR System administrator. No summary data was found in the AR System server to display this Flashboard. No history summary data was collected in the FB:History Summary form for this flashboard. There is no data available to display this chart. The AR System form defined for this flashboard contains no data.

Chapter 2 Action Request System error messages

161

BMC Remedy Action Request System 7.5.00

3623 Error 3624 Error

Summary data can not be displayed on a pie chart. History summary data can be displayed in all chart types except pie charts. To display history summary data, specify a different chart type. Cannot login to the AR System server. The flashboards mid tier system could not log in to the AR System server because the user does not have the required permissions, or the flashboards mid tier system could not connect with the AR System server. Contact your AR System administrator. Cannot display a graph that contains more than number data points. The number of data points to be plotted on the flashboard exceeds the limit. The default limit is 3000 data points. An AR System administrator can increase this limit by adding the following property to the config.properties file in the midTierInstallDir/WEB-INF/classes directory: flashboards.maxDataPoints An example property that increases the limit to 4000 is: flashboards.maxDataPoints=4000

3625 Error

4000 Note 4001 Note 4002 Note 4003 Note 4004 Note

Import completed successfully -- number records imported. This message appears after a successful Import operation. No errors occurred during import. Import of importFileName started. System reports that the Import operation started. This message is logged only to the log file. Only one field title exists in import file -- ensure that you specified the import file correctly. System warns you that the specified import file has only one field. This is usually caused by an incorrect Import file format or separator string specified on the Open Import File dialog box. You have not added or saved your changes to the current fallback mapping -- if you continue, those changes will be lost. System dismisses the Fallback Mappings window before applying the changes. You have not saved nor imported data with the current mappings -- if you continue, the mappings will be lost. You tried to exit the tool without saving the modified mappings in the main window. Use the Save Mapping menu item or the Import button before exiting the tool to avoid this note.

4005 Note

You have not added or saved your changes to the current mapping -- if you continue, those changes will be lost. The current mapping was changed but not applied. Click the Modify or the Add button to avoid this note.

4006 Note

You have not saved your changes to the current mapping -- if you continue, those changes will not be used for this import. The current mapping was changed but not applied when the Import button was clicked. Click the Modify or Add button to avoid this note.

4007 Note 4008 Note 4009 Note

Are you sure you want to delete all mappings? System confirms the Delete All button is in both the main and Fallback mapping windows. Record number: Field fieldName truncated to number characters. This message is logged to the log file when a field is truncated during an Import operation. This message is logged only to the log file. Are you sure you want to start importing? System confirms that you really want to begin the Import operation.

162

Error Messages Guide

AR System error messages

4010 Note 4011 Note 4012 Note 4013 Note 4014 Note 4015 Note

Mapping mappingName not loaded. The specified mapping is not loaded. Earlier messages described why. Duplicate name for mapping. Do you want to overwrite the existing mapping? A mapping with the name you specified already exists. If you overwrite it, the earlier mapping is replaced by the new one. Exit Import Tool? System confirms that you want to exit BMC Remedy Data Import. Did not find any matching fields to add as new mappings. The Add All button operation did not find any matching form and import fields to add as mappings. Copy unprocessed import records to the log file? You stopped the Import process before the tool completed its operation. Specify whether you want the remaining records to be copied to the log file. You have not saved your changes to the current fallback mappings. If you continue, your changes will not be used for this import. You are starting the Import operation without applying the changes made to the fallback mapping window. If you continue, any settings you made to the fallback mappings window that were not saved are ignored. If you want those settings used, do not continue with the import; instead, save the changes on the fallback mappings window, and restart the import.

4016 Note

Save your current mappings before closing this window? You made but did not save changes to the Save Mapping window. If you continue, your changes will be lost. To save your changes, click No to cancel closing the window. This file contains duplicate or empty field titles. A number has been appended to those titles. The .csv or .asc import data file contains duplicate field titles. A number was appended to the end of the field titles in the import fields list so you can distinguish between them. Names are processed from left to right in the file with the field toward the right being modified. You can continue with the Import operation and no data will be changed. The name was changed so that BMC Remedy Data Import can distinguish between the two fields during mapping of data values. This file contains duplicate or empty field titles. Those titles have been replaced by their field ids. Duplicate field titles exist in the .arx import data file. When duplicate names are found in an .arx format file, both fields are replaced with their IDs to eliminate confusion about the fields. This form contains duplicate or empty field labels. Those labels have been replaced by their field ids. The form contains duplicate field names. These fields are shown by their field IDs in the form fields list.

4017 Note

4018 Note 4019 Note

4102 Error 4104 Error 4105 Error

Invalid AR Export format, file: importFileName. The specified import file is not in AR Export format, which you specified it to be. Import completed with errors: number records were imported; number records were not. The Import operation was completed. View the log file to see the error messages and records that did not get imported. User did not wish to continue operation. The user terminated the Import operation after it started.

Chapter 2 Action Request System error messages

163

BMC Remedy Action Request System 7.5.00

4106 Error

Copying remaining records of importFileName to log file. This is the second part of the message that appears after you stop the Import operation before it is completed and copy the remaining records to the log file. You should never see this message by itself. Stop broadcast. During a broadcast of messages within Windows, the broadcast message was stopped. Cannot log record starting at fileOffsetOfRecord. The record starting at the specified offset cannot be read. This error might indicate that Open or Seek operations cannot be performed in the import file. No mapping selected to delete. You tried to delete a fallback mapping in BMC Remedy Data Import without first selecting one. No saved mappings specified in batch mode. The tool is running in batch mode, but you did not specify which mapping to use for import on the command line. Cannot get children widgets, or widget not a child. When you tried to add, change, or remove a mapping request (regular or fallback), the mapping or the fallback mapping list box failed to add, remove, or change the request. Cannot login to any AR Server. The tool is running in batch mode, but none of the servers specified on the command line or in the /etc/ar file are available. Two mappings have been specified on the command line. The tool is running in batch mode, but you specified two mappings to use for the Import operation on the command line. Only one mapping is allowed. The -m option requires a mapping name. You used the -m flag on the command line, but did not supply a mapping name following the flag. The mapping name is longer than the maximum allowed length. You specified a mapping name that is longer than 30 characters. A directory may be specified only if you specify a mapping. You used the -d flag on the command line, but did not also specify a mapping with the -m flag. fieldName is not a Form Field. The field name specified in the Form Field text control is not a valid field name for the current form. Enter a valid field name. Try reselecting the form and redefining the mappings; it is possible that the definition of the form was changed by another user.

4108 Error 4110 Error 4112 Error 4114 Error 4116 Error 4118 Error 4120 Error 4122 Error 4124 Error 4126 Error 4128 Error

4130 Error 4132 Error 4134 Error

fieldName is not an import field name, id, or keyword. You used the variable syntax ($) in the mapping value, but the string enclosed by the dollar signs ($) is not an Import field, an Import field ID, or a keyword. Cannot get the status of or cannot open log file. You specified a log file name that cannot be opened for read and write. You might not have permission to use the log file. Verify the owner and the permissions for the file. A log file name is required. You erased the log file name and clicked Save in the Preferences window.

164

Error Messages Guide

AR System error messages

4135 Error 4136 Error 4137 Error 4138 Error 4140 Error 4142 Error 4144 Error 4146 Error 4148 Error 4150 Error 4152 Error 4153 Error 4154 Error 4155 Error 4156 Error

Log file pathName is a directory. You specified a directory in the log file text field. Import log file name is longer than the maximum allowed length. You specified a log file name longer than 255 characters. Log file fileName is not a regular text file. You specified a log file that is a special file type instead of a normal text file. Choose another file as the log file. Cannot write to log file. A system error occurred while writing the log file. The system error is the second part of this message. Cannot initialize the server API. BMC Remedy Data Import cannot initialize the server API and so cannot establish a connection to AR System server. Cannot build the main import window. BMC Remedy Data Import could not create the main window, and the tool could not be started. The system is probably out of memory. Bad parameters. This is an internal error. You might be able to perform the operation by shutting down BMC Remedy Data Import, restarting it, and performing your operation. Bad globals. This is an internal error. You might be able to perform the operation by shutting down BMC Remedy Data Import, restarting it, and performing your operation. Cannot add to mapping list. This is an internal error. You might be able to perform the operation by shutting down BMC Remedy Data Import, restarting it, and performing your operation. Cannot set mapping list item. This is an internal error. You might be able to perform the operation by shutting down BMC Remedy Data Import, restarting it, and performing your operation. No tokens for a Direct Mapping. This is an internal error. You might be able to perform the operation by shutting down BMC Remedy Data Import, restarting it, and performing your operation. Cannot open map file for specified mapping. The mapping file that contains the specified mapping cannot be opened. You might have moved the file or the directory that contained the mapping. Cannot find specified mapping. This is an internal error. You might be able to perform the operation by shutting down BMC Remedy Data Import, restarting it, and performing your operation. Cannot read map file for specified mapping. The mapping file that contains the specified mapping cannot be read. The file probably has incorrect permissions set. The import option value is invalid. This is an internal error. You might be able to perform the operation by shutting down BMC Remedy Data Import, restarting it, and performing your operation.

Chapter 2 Action Request System error messages

165

You specified an import file that is a special file type instead of a normal text file. Bad Mapping list. You specified a directory as the import file. The mapping file contains invalid syntax. restarting it. and performing your operation. The import file is of length zero. restarting it. You might be able to perform the operation by shutting down BMC Remedy Data Import. is no longer accessible. You might be able to perform the operation by shutting down BMC Remedy Data Import. Specified import file does not exist. restarting it. restarting it. You tried to close the Open Import File window without specifying an Import file. Import fields' titles-list is invalid. The tool could not understand the syntax in the mapping value string. You specified a nonexistent file as the import file. and performing your operation. This is an internal error. and performing your operation. Error Messages Guide 166 . This is an internal error. This condition could result from low memory. Bad Form Information UI Fields list. This is an internal error. This is an internal error. Specified import file is empty. and performing your operation. or you removed the file after BMC Remedy Data Import started. Bad internal list. You might be able to perform the operation by shutting down BMC Remedy Data Import. Rewrite the mapping. This is probably caused by a user who edited the mapping file manually. This is an internal error. This condition could result from low memory. An import file name is required.00 4158 Error 4160 Error 4162 Error 4164 Error 4166 Error 4168 Error 4170 Error 4172 Error 4174 Error 4175 Error 4176 Error 4177 Error 4178 Error 4179 Error 4180 Error 4182 Error 4184 Error The mapping file has a syntax error. The import file.5. and performing your operation. Specified import file is a directory. Fix the syntax as necessary. Specified import file has no data. Cannot get the status of import file. You might be able to perform the operation by shutting down BMC Remedy Data Import. Specified import file is not a regular text file. Bad Fallback Mapping list. or the directory it is in. Record number: Cannot parse record in import file The tool could not understand this record in the import file. This is an internal error. The Import file contains only field titles (if that) and no data.BMC Remedy Action Request System 7. Syntax error in the mapping string. Bad Mapping or Compound mapping within Compound mapping. and performing your operation. Cannot parse import field titles in import file. You might be able to perform the operation by shutting down BMC Remedy Data Import. restarting it. restarting it. You might be able to perform the operation by shutting down BMC Remedy Data Import. The tool could not understand the field titles in the import file.

Record number: value is not a valid value for field fieldName. found numberFound. You never see this message in a dialog box. Digits are expected in the line after the string FLD-ID. The specified import file contains an improperly formatted record. expected numberExpected. Import completed successfully: numberImported records imported. A data line in an export data file (. 4208 Error 4210 Error 4212 Error 4214 Error End of numberOfCopiedRecords records. Make sure that the export data file (. The import file type is not set.arx) did not begin with DATA. The system error is in the second part of this message. Cannot seek in import file. Bad Import file record. The record has more fields than the number of field titles.arx) is not corrupt. The data in the file must be corrected before an import of this line is possible. found numberFound. Cannot open specified import file. numberTruncated records were truncated. This could be caused by an unrecognized selection when mapping to a selection form field. The value in the import file is invalid for the form field it is mapped to.AR System error messages 4186 Error 4188 Error 4190 Error 4192 Error 4194 Error 4196 Error Import file name is longer than the maximum allowed length. This message is printed in the log file at the end of all copied records from the Import file. a field separator string is required for reading in the field titles. Chapter 2 Action Request System error messages 167 . this message indicates how many records were truncated and imported. Record number: Not enough fields. The specified Import field separator string is longer than 30 characters. A field separator string is required. AR Export file's Field ID string does not contain a number. A Seek operation cannot be completed in the import file due to a system error. The record has fewer fields than the number of field titles. The import field separator string is longer than the maximum allowed length. This is an internal error. but a character that is not a digit was found. or by a character that is not a digit when mapping to a numeric field. After you choose the Truncate option in the Preferences dialog box and records are truncated. 4198 Error 4200 Error 4202 Error 4204 Error 4206 Error Record number: Unrecognized tag in AR Export file: fileName. expected numberExpected. You failed to put the mapping at a given index into the form and into the mapping text field in BMC Remedy Data Import. The system error appears in the second part of this message. Import file fileName is of an unknown type. Cannot find form field with saved index. and correct the file so that it contains only digits in the FLD-ID line. Record number: Too many fields. For the ASCII file format. The specified import file cannot be opened due to a system error. The specified Import file name is longer than 255 characters.

You chose the Load Mapping menu item.5.00 4216 Error Import completed with errors: numberImported records were imported. A window broadcast a message to another window. and that window could not handle the message. AR System Approval Server restarting. 4227 Error Cannot open the default log file. The mapping file could not be created. 4499 Warning 4500 Note AR System Application server terminated when a signal/exception was received by the server. After you choose the Truncate option in the Preferences dialog box and records are truncated (and some records not imported due to errors). User stopped import after numberProcessed records were processed. You can take one of the following actions: Exit the record to make the field shorter. Details are in an associated message. This message indicates that the error was fatal and the approval engine is shutting down. you should be able to restart the server and continue to work. If the signal is 15. of which numberImported were imported. You decided to stop the import process before it was completed.fatal error encountered.log on UNIX. Record number: a field exceeds the maximum size allowed. A field of the specified record exceeded 32. The system does not allow this. A signal terminated the approval engine. 4501 Note 4502 Note 4503 Note 4510 Warning 168 Error Messages Guide . No mappings are defined.BMC Remedy Action Request System 7. but there are no mappings files in $ARHOME/arcmds or in any of the directories on the ARPATH environment variable. this message indicates how many records were truncated and not imported. Verify the file path to make sure that there is enough disk space and that all the directories exist. The default import log file (/tmp/arimport_user. Turn on the truncate character fields’ value option if it is a character field. The command that failed is included in this message. Only one -d argument is allowed on the command line. numberTruncated records were truncated. numberNotImported records were not. It was terminated either accidentally or intentionally by a user in your environment. This message indicates how many records were processed and how many were imported. and arimport.log in the ARHOME directory on Windows) cannot be opened. The system encountered two or more entries in the Approval Role form for the specified name. Two or more roles have the same name. A fatal error occurred within the approval engine. The number following this error is the signal that was received. The command could not be performed because of an unspecified error.767 bytes (one byte less than 32 kilobytes). The name is included in this message. Broadcast message not handled. 4218 Error 4220 Error 4222 Error 4224 Error 4226 Error Two directories to look for saved mappings have been specified on the command line. Operation cancelled due to error. Create of mapping failed. The error was displayed in previous dialog boxes. Delete or change one entry. AR System Application server terminated -.

so it is also possible that the Change History field is corrupted. and enter a form name as required. During the creation of the Application Pending form. Details are in an associated message. The forms should be considered part of the system structure and should not be deleted or modified. Check the syntax of the command. the command was not performed. Form name specified on command is not valid. so it is also possible that the Change History field is corrupted. Problem encountered during creation of one of the application forms. You must be the user (process) “AR System Application Service” to run the specified delete operation and mapping forms. To delete one or both of the forms. Load the Application Pending form. The form is found by searching for a form with a specific tag in the Change History field. The specified form name is invalid on the system. The specified form name must be the name of an existing form. The form is found by searching for a form with a specific tag in the Change History field. No form containing all the special reserved application pending fields was found. The approval process is configured to require users to enter their password to approve or reject a request. The system could not locate the Approval Form form. An associated message contains more information. The attempted command is displayed with this message. or the supplied password was invalid for the user performing the operation. The system received a request to record a command or encountered a situation in which it attempted to record one automatically. Failure during an attempt to perform an application command. so it is also possible that the Change History field is corrupted. this means that the Approval subsystem is not installed. and ignore the system warning related to the forms. and restart the arserverd process (or send a SIGHUP signal). To re-create the form. Must be Application Server user to perform this operation. an error occurred. No Approval Form form was found. Delete one of the forms. The form is found by searching for a form with a specific tag in the Change History field.AR System error messages 4511 Warning No Approval Administration form was found.delete one to continue. correct the reason for the failure. and a failure was encountered during recording. this means that the Approval subsystem is not installed. The system could not locate the Approval Notification form. No Approval Notification form was found. Confirming password is not valid for the current user. Command requires a form name be specified. use AR System Developer Studio to select the forms for deletion. Either the password was not supplied. The parsing or formatting command requires a form name. The system encountered two forms that have all the reserved application pending fields. this means that the Approval subsystem is not installed. Generally. Thus. The system could not locate the Approval Administration form. Generally. 4512 Warning 4513 Warning 4549 Error 4550 Error 4551 Error 4552 Error 4553 Error No Application Pending form could be found on the server. 4554 Error 4555 Error 4556 Error Chapter 2 Action Request System error messages 169 . Generally. Two forms containing all the reserved application pending fields encountered -. The system cannot work correctly if two forms contain pending information. None was specified. or change it so that it is not considered an Application Pending form by removing fields in the 250 to 260 range. The two forms are identified in an associated message. An Application Pending form is required for the system to support application operations.

and retry the operation. The Request ID specified for the command is invalid. The start or end time provided for the command is not valid. The command is invalid without the Approval subsystem. Additional information identifies the error and the position in the assignment where the error occurred.BMC Remedy Action Request System 7. Review the syntax and retry the command with the appropriate field name specified. Command requires appropriate parameters. The command is invalid without the Approval subsystem. An error was detected in an assignment line. this means that the Approval subsystem is not installed. Entry ID specified on command is not valid. A request was made for finding forms joined to the Approval Details form. Generally. Field name specified on command is not valid.5. The field name specified for the command is invalid within the indicated form. this means that the Approval subsystem is not installed. The command requires that a field name be specified. For an approval license to exist. The command requires that a valid field name be specified.00 4557 Error 4558 Error 4559 Error 4560 Error Parse set fields command requires two forms be specified. The parse set fields command requires that two forms be specified. Limited licensing is in effect for approvals. 4561 Error 4562 Error 4563 Error 4564 Error 4565 Error 4566 Error 4567 Error 4568 Error 4577 Error 4578 Error 170 Error Messages Guide . and the system encountered two forms with the same license tag. Command requires a field name be specified. No Approval Server license—cannot run the approval engine. There are two forms with the same license tag. Command requires a entry ID be specified. a valid server license must exist because the server license is the base license and the approval license is an option. A request was made that requires access to the Approval Signature form. this means that the Approval subsystem is not installed. No Approval Details form could be found on the server. One or more expected parameters are missing from a process command. An error was detected in the qualification line. but no Approval Details form exists on the system. Generally. Make sure that the server license is valid and implemented. Generally. Assign line error. A request was made that requires access to the Approval Detail-Signature form. but no Approval Detail-Signature form exists on the system. but no Approval Signature form exists on the system. The command requires that a Request ID be specified. Qualification line error. Only the first form found with the tag will be loaded. No Approval Detail-Signature join form could be found on the server. Review the syntax of the command. Either none or only one was specified. Additional information identifies the error and the position in the qualification where the error occurred. The command is not valid without the Approval subsystem. BMC Remedy Approval Server checks licensing to determine whether a server is licensed for approval functionality. No Approval Signature form could be found on the server.

One of the forms must be deleted for the Approval system to work correctly. No Approval Signature Line form was found. Generally. The form is found by searching for a form with a specific tag in the Change History field.390609. An associated message identifies the forms. An associated message identifies the forms. Command requires form and entry ID be specified. Limited licensing is in effect for approvals. and the system could not find any form with the tags in the limited license tag list. One of the forms must be deleted for the Approval system to work correctly. The system encountered two forms designated as the Approval Signature Line form. The system encountered two forms designated as the Approval Detail form. this means that the Approval subsystem is not installed. The system does not allow this.lck. Form is not licensed to work with the approval engine. There are two forms identified as the Approval Detail form. The system could not locate the Approval Signature Line form. No Approval Rule Definition form was found. this means that the Approval subsystem is not installed. and the system could not find a license in the limited license tag list for the specified form. so it is also possible that the Change History field is corrupted. The system could not locate the Approval Rule Definition form. so it is also possible that the Change History field is corrupted. The form name is identified in the message. The system could not locate the Approval Process Definition form. Malloc failed in Approval Server. One of the forms must be deleted for the Approval system to work correctly. The system encountered two forms designated as the Approval Rule Definition form.AR System error messages 4579 Error 4580 Error 4581 Error 4582 Error 4583 Error 4584 Error Limited licensing for Approvals and no form was found linked to any license. Another copy of the Approval Server is already running or the Application Dispatcher is in use. The system does not allow this. No Approval Process Definition form was found. Parameters are missing from the command to the Approval Server. An associated message identifies the forms. The form is found by searching for a form with a specific tag in the Change History field. The form is found by searching for a form with a specific tag in the Change History field. The system does not allow this. An associated message with the actual command was sent to the Approval Process administrator. 4585 Error 4586 Error 4587 Error 4588 Error 4589 Error 4590 Error 4591 Error Chapter 2 Action Request System error messages 171 . An associated message identifies the forms. The system encountered an error while attempting to open the Approval Server lock file ARServerInstallDir\arserver\db\ar. One of the forms must be deleted for the Approval system to work correctly. Generally. Error while opening the Approval Server lock file. The system encountered two forms designated as the Approval Process Definition form. so it is also possible that the Change History field is corrupted. Generally. The system does not allow this. There are two forms identified as the Approval Signature Line form. There are two forms identified as the Approval Process Definition form. this means that the Approval subsystem is not installed. Limited licensing is in effect for approvals. This is an error condition. There are two forms identified as the Approval Rule Definition form.

Generally. The system could not locate the Approval Alternate form. You must either change the rule to allow multiple next approvers or specify only one next approver for this entry. More than one Next Approver record was returned for the entry. The system encountered two forms designated as the Approval Alternate form. No Approval Role form was found.00 4592 Error There are two forms identified as the Approval Alternate form. There are two forms identified as the Approval Process Administrator form.1.5. There are two forms identified as the Approval More Information form. An associated message identifies the forms. The form is found by searching for a form with a specific tag in the Change History field. or remove your AR System Application Service password. 4593 Error 4594 Error 4595 Error 4596 Error 4597 Error 4598 Error 4599 Error 4600 Error 4601 Error 4602 Error 172 Error Messages Guide . this means that the Approval subsystem is not installed. The system does not allow this. One of the forms must be deleted for the Approval system to work correctly. The system could not locate the Approval Process Administrator form. Either upgrade your Approval Server to 5. The form is found by searching for a form with a specific tag in the Change History field. There are two forms identified as the Approval Role form. and a Get Next Approver rule for the approval process is configured to return an error when multiple rows are returned. The system encountered two forms designated as the Approval Process Administrator form. The operation has stopped. Cannot create new approval detail as is already an active detail entry. The system could not locate the Approval Role form. so it is also possible that the Change History field is corrupted. The system does not allow this. so it is also possible that the Change History field is corrupted.x. this means that the Approval subsystem is not installed. this means that the Approval subsystem is not installed. No Approval Process Administrator form was found. One of the forms must be deleted for the Approval system to work correctly. The system could not locate the Approval More Information form. An associated message identifies the forms. The system encountered two forms designated as the Approval More Information form.BMC Remedy Action Request System 7. This can occur when AR System 5. Generally. The form is found by searching for a form with a specific tag in the Change History field. The system encountered two forms designated as the Approval Role form. Generally. so it is also possible that the Change History field is corrupted. The system does not allow this. No Approval Alternate form was found. An associated message identifies the forms.1 is used with Approval Server 4. An approval is in progress for the indicated approval process and entry ID. Generally. this means that the Approval subsystem is not installed. The system does not allow this. One of the forms must be deleted for the Approval system to work correctly. An associated message identifies the forms. One of the forms must be deleted for the Approval system to work correctly. The form is found by searching for a form with a specific tag in the Change History field. Multiple rows matched next approver condition and configured to error. AR System server does not support AR System Application Service user. so a new approval detail entry will not be created. so it is also possible that the Change History field is corrupted. No Approval More Information form was found.

Failure trying to map names to IDs in a string. If the process is defined as Ad Hoc. sig-reassign. sig-cancelled. Sig-xxx command requires process to match details if process is specified. but more than one approver was entered in the Next Approvers or Reassign To field. Instructions are in the Approval Server Guide. The field defined to specify the first approver for the process does not exist on the application form. sig-rejected. but the issued command (Add-sig or New-details) did not specify which one to use for the new approval. sig-cancelled. No process specified but there are two or more for form so cannot continue. You must configure a process for a form before using it for approvals. and Message fields in the AP:Notification entry could not be converted to their field IDs.AR System error messages 4603 Error Field specified for first approver is not defined on the form. The process specified in the issued command (sig-approved. Before you use the Approval Server with your application. No join is defined between the form and the approval detail form. sig-rejected. If the process is defined so that Anyone can specify the next approver (see the BMC Remedy Approval Server Guide). sig-reassign. An associated message identifies the forms. The issued command (sig-approved. If you are making approval configuration changes in the Server Settings form. try again. the operation will continue after this message. sig-notify) does not match the process specified in the details record of this pending approval request. or sig-notify) does not exist. Update-Config command requires tag. Process allows only one ‘next approver’ but two or more were specified. No process is associated with your approval application form. One of the forms must be deleted for the Approval system to work correctly. 4604 Error 4605 Error 4606 Error 4607 Error 4608 Error 4609 Error 4610 Error 4611 Error 4612 Error 4613 Error 4614 Error 4615 Error 4616 Error Chapter 2 Action Request System error messages 173 . Sig-xxx command requires form to be the approval signature line form. The field names specified in the Send to Other. sig-reassign. you must join your application form to the AP:Detail-Signature form. Your application has two or more approval processes configured for it. sig-notify) must come from the AP:Signature form. The issued Update-config command did not have a tag for the config parameter. The field ID is appended to this message. The system encountered two forms designated as the Approval Administration form. sig-approved. The actual error is appended to this message. See error number 4612. The issued MoreInfo-Return command must come from the AP:More Information form. so the operation stopped. A process was specified but no process by that name exists. MoreInfo-xxx command requires form to be the More Information form. Subject. There are two forms identified as the Approval Administration form. New-details. The process was configured to allow only one approver. Failure trying to retrieve join of a form with Detail-Signature. sig-cancelled. Instructions are in the Approval Server Guide. you must join your application form to the AP:Detail form. Before you use the Approval Server with your application. sig-rejected. the operation stopped. No active process is associated with this form. No join is defined between the approval detail and signature line forms. The system does not allow this. The process specified in the AP:Notification entry or in the issued command (Add-sig.

The system does not allow this. The system encountered two forms designated as the Approval Form form. To resolve this problem.5. Missing XML <> tag parsed instruction. Supply the value tag. The Completed? field (ID 13004) is missing from the AP:Detail form. The system encountered two forms designated as the Approval Notification form. such as for a user name or a server name. but no form was designated for this purpose. A NULL value was supplied. The Entry ID field is required on Detail form but is not present. The field value was supplied without the field label in the email message. 4618 Error 4619 Error 4620 Error 4650 Error 4651 Error 4652 Error 4653 Error 4654 Error 4900 Error 4901 Error 4902 Error 4903 Error 4904 Error 4906 Error 4907 Error 174 Error Messages Guide . Verify your email configuration or review the email engine logs to diagnose the problem. The Form field is required on Detail form but is not present. There are two forms identified as the Approval Preview Signature Line form Only one form can have this designation.00 4617 Error There are two forms identified as the Approval Notification form. An attempt was made to initialize a mail box that was already initialized. One of the forms must be deleted for the Approval system to work correctly. The Process field is required on Detail form but is not present. Missing : in the parsed instruction. One of the forms must be deleted for the Approval system to work correctly. An associated message identifies the forms. This message appears when the approval engine starts. Supply the missing XML tag. An associated message identifies the forms. NULL value. Supply the field label. This error can occur while parsing an instruction. The system does not allow this. The Entry ID field (ID 8) is missing from the AP:Detail form. An expected XML tag is missing in the email message. No Approval Preview Signature Line form was found An Approval Preview Signature Line form is required. A colon was not supplied after the label name in supplying field values. Verify your input. Missing name value tag in HTML parsed string. Supply a colon (:) between the field label and the value in your input. Contact your AR System administrator if necessary. Contact your AR System administrator if necessary. The Next Approver field is required on Sig Line form but is not present. Missing Field Label in parsed string. The Application field (ID 10050) is missing from the AP:Detail form.BMC Remedy Action Request System 7. An invalid value was supplied. Invalid Value. such as a user name or a server name. designate only one Approval Preview Signature Line form. The Completion field is required on Detail form but is not present. Verify your input email message. There are two forms identified as the Approval Form form. The Process field (ID 10000) is missing from the AP:Detail form. Already Bound. An expected HTML tag is missing in the email message. The Next Approvers field (ID 13205) is missing from the AP:Signature form.

Command Line Parameter Value is missing. The message provides information about which parameter value is missing. is missing in the incoming email message. Missing Instruction. Review the email engine logs to diagnose the specific problem. Provide the missing parameter value. A required action parameter. Missing Action Parameter. The command line parameter is specified more than once. Invalid configuration values in the EmailDaemon. The user instruction specified in the email message does not exist. depending on the field type in the incoming email message. Error creating mail message. The expected header instruction action is missing from the email message. The supplied data type does not match the data type required for the field. An invalid field value was supplied. Security Key is disabled. Invalid Email Daemon. A command line parameter is specified without a value in the email engine startup script. An expected attachment was missing while processing an incoming email message. 4912 Error 4913 Error 4914 Error 4915 Error 4916 Error 4918 Error 4919 Error 4920 Error 4922 Error 4923 Error Chapter 2 Action Request System error messages 175 . Supply the action instruction. Specify the parameter only once. such as a form name or a request ID. The message provides information about the missing parameter. A required command line parameter. You cannot modify the form because an invalid value was supplied. Provide the correct value for the field. Contact your AR System administrator if necessary. The message provides a description of the missing information.properties file to see if anything is missing. Unable to locate the specified User Instruction. is not specified in the email engine startup script. The message contains the parameter that is specified more than once. Supply the correct value.properties file. The message provides information about which parameter is invalid. Command Line Parameter not defined. Verify that the specified user instruction exists in AR System Email User Instruction Templates form. Provide the expected attachment. An outgoing email message cannot be created because certain information is missing or an internal error occurred. An invalid parameter or an invalid value for a parameter is specified in the email engine startup script. such as a server name. Security Key has expired The security key provided in the incoming email message expired. Contact your AR System administrator. such as a non-numeric value for an integer field. Provide the missing parameter. Field type does not allow the field to be modified. Command Line Parameter already defined. The security key provided in the incoming email message is disabled.AR System error messages 4908 Error 4909 Error 4910 Error 4911 Error Invalid value. Contact your AR System administrator. Command Line Parameter is not valid. Review the EmailDaemon. Missing Attachment.

Verify that the right security key was entered.00 4924 Error 4925 Error 4927 Error Security Key not found on Form. Make sure that the modify key was not deleted from the message. Check the email sent. Security Key is not valid for the specified From Email Address. Modify actions are disallowed for the incoming mailbox. Supply values for the date/time fields in the suggested format. Modifications are disabled on this mailbox. Contact Customer Support. The correct format is format. Make sure that the modify key was not modified and that the original outgoing email message was not deleted. Invalid Date/Time format for specified date. The modify key in the incoming email message with modify action is invalid. Check the instruction specified or contact your AR System administrator if necessary. Unable to encrypt. Make sure that the modify key was not modified and that the original outgoing email message was not deleted. 4928 Error 4929 Error 4930 Error 4931 Error 4932 Error 4933 Error 4934 Error 4935 Error 4936 Error 4937 Error 4938 Error 4939 Error Unable to locate the specified User Instruction. Verify that you specified the correct security key for the email address used. The specified template cannot be found in the AR System Email Templates form. The modify key contains an invalid AR System server name. Contact Customer Support 176 Error Messages Guide . An invalid format was used for the date/time fields. The specified instruction cannot be found in the AR System Email User Instruction Templates form. Unable to locate message with the specified Entry ID. You must provide the security key. This error message gives details about the correct date/time format. Missing AR System User Information.BMC Remedy Action Request System 7. The security key does not match the originating email address. make sure that the email mailbox is set to use user supplied login information. Contact your AR System administrator. Invalid Server Name. If the problem still occurs. Unable to execute Modify Action due to missing security key. Missing Modify Key. Missing Template. Invalid Checksum. An unknown system error occurred.5. The modify key is missing from the email message with the modify action. Verify that the correct template was specified or contact your AR System administrator if necessary. The email message with the modify action is missing a security key. No login information was specified or the specified login information is invalid. An invalid security key was entered. Internal Exception Caught. unable to execute Instructions. Make sure that the modify key was not modified. Unable to decrypt. Contact Customer Support. A problem occurred in decrypting the modify key. contact your AR System administrator. The modify key contains an invalid entry ID. If login information was specified. A problem occurred in encrypting the modify key.

Sender address not found in original email. None of the recipients have access to form: formName.AR System error messages 4940 Error 4941 Error 4942 Error Recipients have not been specified for this email. Invalid characters were found in the email address for the email message. Contact your AR System administrator. No fields were specified for submit or modify operation. Verify that the email address was specified. Wait for the email engine to reconnect to the server so that all pending actions can be completed. Verify your qualification or contact your AR System administrator AR System server is not available. The AR System Email Mailbox Configuration form does not exist or the AR System server is unavailable. Missing currency code for the currency value specified. A problem has occurred with the connection to the AR System server. Chapter 2 Action Request System error messages 177 . then check the network connectivity. because it was not saved in the database. The attachment is too large. This problem may occur due to the AR System server being unavailable. Will retry connection to server in numberMinutes minutes. See your AR System administrator. No field values supplied. 4943 Error 4944 Error 4945 Error 4946 Error 4947 Error 4948 Error 4949 Error 4950 Error 4951 Error 4952 Error 4953 Error Store entry for this message failed. Email address contains invalid characters. you must supply a form name and an AR System server name. Message’s From or Reply-To person is same as incoming mailbox user. Contact your AR System administrator. If the connection is not reestablished within timeInterval. No matching entries were found for the qualification. Specify a currency code for the value. The required form access permissions are unavailable. a database connectivity issue. Check whether all of these are working and then resend the message. If you use variable replacement with a qualification. No matching requests (or no permission to requests) for qualification criteria. A currency value was specified without a currency code. Variable replacement with a qualification requires a form and a server. Use a different name in the From or Reply-To field of the current email message. The supplied value for an option (radio button) or a drop-down list item is invalid. No email addresses are specified for the email message. or a connectivity issue between the AR System server and the email engine. Specify values for the action. The name in the From or Reply-To field of the current email message is the same as the incoming mailbox user name.properties. then check whether the AR System server is running. Invalid Enumerated Value supplied for selection field. Form is missing. which may cause message loop. we will not be storing this message in Message form. Verify that you provided the correct value. The Store entry has not been created for the current email message. Verify that the email address that was specified correctly. The email address of the sender of the modify email is not found in the original email message. Will retry connection to server in timeInterval. and if it is. See your AR System administrator. Attachment file size exceeds the limit set in emaildaemon. this may cause a message loop.

Unable to update cache. Because fields are uniquely identified by field ID. This is an internal error message used for debugging purposes. 5001 Error 5002 Error 5003 Error 5004 Error 5005 Error 5006 Error 5007 Error 5008 Error 5009 Error 5010 Error 5011 Error 5012 Error 5025 Warning 5026 Warning No field mappings have been defined. consider changing one of the labels.5. Unable to update enum value value for field fieldName. If the user is working against an AR System server it means that the user has not logged in to the server. This is an internal error message used for debugging purposes. duplicate labels are allowed. 5027 Error 178 Error Messages Guide . Wrong type for property property for field fieldName expected value. This is an internal error message used for debugging purposes. If the user is working against a different store implementation. and does not effect users. Object reservation is done via entries on a form on the AR System server. No metadata available for limit limit for field fieldName. Modify the form to give subadministrators permission. This warning is returned because you did not define any field mappings. it means that the store has not been initialized. Assign a valid store instance to the object. This is an internal error message used for debugging purposes. This is an internal error message used for debugging purposes. This error is generated if sub-administrators do not have permissions to the form. A dynamic field value was specified that does not match a field reference on the current form or a keyword. The form cannot be saved. Invalid store for object. Provide a correct dynamic value. The field label “label” is duplicated on this form. got value. Unable to retrieve field list for form formName. A dynamic field value in tableFieldType “tableFieldName” contains an invalid field or keyword reference. The store attached to a specific model object is invalid.00 5000 Error Store is not connected to ARSystemServer. Unexpected enum property value value found for property property for field fieldName.BMC Remedy Action Request System 7. Cannot create a value object for property ID ID in field fieldName. Subadministrators must have permission to the form formName because object reservation is enforced on this server. Property property for field FieldName not described in metadata. This is an internal error message used for debugging purposes. The field labels identified in the message are used for multiple fields on the form. The cache could not be updated for an object. Object is not editable. No field limit information available for field fieldname type type. The store is not connected. For additional information. see the log file. This is an error intended for Java developers who are developing plug-ins for BMC Remedy Developer Studio. This is an internal error message used for debugging purposes. Because it can be confusing to have fields with duplicate labels. Enter a field reference or select a keyword from the list for the field. This is an internal error message used for debugging purposes.

5030 Error 5031 Error 5032 Error 5033 Warning 5034 Warning 5035 Error 5036 Error 5037 Error 5038 Error Empty COM method list. Specify a valid database column name. You can also use $fld$ to enter the value for a pointer parameter. VARIANT. You can call or nest another method out of this return type only if the return type is of type object or object pointer. this error is returned. 5039 Error The parameter or return value is the wrong type. Character menus cannot exceed 15 levels. The error handler does not exist. When you try to delete an OLE method. You must remove this object from the application that owns it before you can add it to this application. The parameter can be filled only by nesting another method whose return type is compatible. Add at least one COM method. When you define an OLE method that has a return type and you try to nest or call another method on this return type. You defined an OLE method that has a parameter of type pointer and you nested another method whose return type is incompatible with the pointer type. All subsequent calls will be deleted. You applied changes to a form that contains a field with a blank label. the parent method’s return must be one of the following types: IDispatch. Enter a value with the correct type. The parent return type is not an object. a warning is returned that all subsequent methods (if nesting was done) will be deleted. You can only add another method that returns this object type. You must provide at least one method for this structure.AR System error messages 5028 Error Unable to add a menu item because there are too many levels in the character menu. BMC Remedy Developer Studio tries to map it to the OLE methods parameter OLE type. BMC Remedy Developer Studio validates whether the return type is of type object. Chapter 2 Action Request System error messages 179 . 5029 Warning The entry point guide will not be executed because it does not have a starting active link. specify a starting active link for the active link guide. Menus can contain a maximum of 15 levels. The field on this form with the name or ID of “name|ID” needs a label. When you provide a value for a parameter. If the parent method’s return type is not one of these types. This is a special parameter. When you nest a method. You cannot call another method on the parent method. or Compatible. An entry point guide was created without a starting active link. Select a matching function. You specified a menu that contains more than 15 levels at some point in its hierarchy. You cannot create or modify a data field without specifying a corresponding database column name. The return type of the method selected and method to be added appear to be incompatible. fieldName When creating a view form. AR Runtime gets or sets the value of the $fld$ and treats this field as an OLE pointer variable. To remove this warning. you must link data fields to an underlying database column. The method list required when defining an OLE Automation active link action is empty. If unsuccessful in the conversion. The entry point guide cannot execute correctly in an Application List field without a starting active link. This object has an application owner and cannot be added to this application. this error message is returned explaining that the value cannot be converted to the native OLE parameter type. or you tried to enter a value for a parameter of type pointer. Object is owned by another application : objectName : applicationName. The error handler does not exist to validate the property.

Unexpected enum property value propertyValue found for property propertyName for field fieldName. Field fieldName is not found on form formName. ask your AR System administrator to start it. A dynamic field value was specified that does not match a field reference on the current form or a keyword. If there is no network connectivity problem. Supply the missing value. shut down and restart BMC Remedy User. Specify a value that is equal to or greater than the listed value. The fieldName field’s length cannot exceed number characters. errrorMessage/ Reason The server is inaccessible due to one of the following reasons: There is a connectivity problem with the network.5. add the entry. If the problem is with the network connection. The value submitted is not a valid value for the enum property of the field. The specified property is not defined for the field. If no entry is present in the file or window. If the server is running. Could not parse the color string to a valid RGB color. The value set to the property does not exist in the list of valid values. The value submitted is not a valid value for the enum property of the field.BMC Remedy Action Request System 7. When the network connection problem is corrected. you must solve all network connectivity problems before you can use the AR System server. The referenced field fieldName does not exist. Specify a value that is equal to or less than the listed value. Invalid color: color. Issue a ping command to the server.00 5040 Error A network connection cannot be established to AR System server: ARSystemServer. If the connection is still unsuccessful after you eliminated these potential causes. Specify a value that is within the listed range. If it is not running. review the /etc/ar file (UNIX) or Login Information window (Windows) on your computer to verify that the server is registered as one of the servers you can access. 5041 Error 5042 Error 5043 Error 5044 Error 5045 Error 5046 Error 5047 Error 5049 Error 5051 Error 5052 Error 5053 Error 5054 Error 5055 Error 5056 Error propertyName requires a value to be specified. The fieldName field’s value cannot be less than fieldValue. make sure that the server process (arserverd) is running. Could not find an enum value for string. Dynamic values for the sampleForm/sampleServer must contain valid field/keyword references. you can successfully connect to the server. Enter a field reference or select a keyword from the list for the field. The fieldName field’s value must be in the range between value and value. Notify field references must be of type Integer or Selection. The server might have been temporarily inaccessible. Specify a field length that is within the listed number of characters. Property propertyName for field fieldName is not described in metadata. The fieldName field’s value cannot be greater than value. 180 Error Messages Guide . Unable to update enum value value for field fieldName.

The file might be corrupted. The file is incorrect or corrupted. Cannot import application because it is reserved by another user. Hidden locked object cannot be edited: objectName. Invalid webServiceName : userSpecifiedName. Application import failed. Cannot export to a file because creation of directory directoryName failed. You cannot modify a locked object. See the list of forms that follows this message. the AR System server is not running. An incorrect file was specified. The selected file does not exist or does not contain applications. objectName is locked as read-only. Cannot release the reserved objects due to an AR System server error. ”. Objects that are currently being edited cannot be renamed. The objectType objectName has an open editor. Adding associated forms and modifying permissions (if applicable) are the only changes allowed. The fieldName field’s value cannot be more than number digits. Specify a value that is equal to or less than the listed number of digits. The file does not exist or does not contain any object definitions. The name must start with an alphabetical character or ”_” and can have alphabetical characters. The def file specified to import view definitions from does not contain any view definitions. Enter a valid name. Cannot import because all the forms are reserved by other users. This might be caused by a file system error or a hardware problem. Cannot import because all the objects are reserved by other users. ARSystemServer errorMessage The connection could not be made to the AR System server. The file used to import applications does not contain any applications or the file does not exist. Any changes will result in an error when the object is saved. An error occurred parsing the def file with view definitions. objectName is locked as read-only. In Import Object definition. Cannot add the following forms to the application as they are either not reserved for you or reserved by other users. Open the Reserved Objects user list to view and release reservations. The specified directory cannot be created. You tried to modify a hidden object that has a read-only lock. Invalid file. Any other changes will result in an error when the object is saved. such as by adding a form to a readonly filter.”. the def file used does not contain any object definitions. Only forms reserved by you can be added to deployable applications.” Login failed for AR System server ARSystemServer.AR System error messages 5058 Error 5059 Error 5060 Error 5061 Error 5062 Warning 5063 Warning 5064 Warning 5065 Error 5066 Error 5067 Error 5068 Error 5069 Error 5070 Error 5071 Error 5072 Error 5073 Error 5074 Error 5075 Error Invalid qualification: problemDescription. ”_”. or ”-” only. digits. The file does not contain any view definitions. or the port number is incorrect. Errors were encountered while parsing the file. Chapter 2 Action Request System error messages 181 .

You must select one primary form. which is the maximum number of allowed actions. Applications that are currently being viewed cannot be deleted. make sure that all fields requiring a value are visible in the default administrator view of the form and that the Allow Any User To Submit check box is selected before you attempt the export operation. The file is read-only. Objects that are currently being edited cannot be deleted. objectNames A server exception occurred when deleting server objects. Refresh the object list to get a fresh list from the server and show the reason why the objects cannot be reserved. Unable to add new action. Objects that are currently being edited cannot be released. The selected packing list has an object list open.5. errorMessage Errors encountered while retrieving objectListType lists from ARSystemServer. Objects that are currently being edited cannot be reserved. Errors encountered while determining related objects. To continue. All of the selected objects have editors open. Packing lists that are currently being viewed cannot be deleted. The following objects could not be reserved: objectNames Refresh the object list to see if any of these objects are reserved. errorMessage Some of the selected working lists are open. The file type must be to arm format. You must reserve all the objects you need to edit. errorMessage Unable to populate the list information. errorMessage An error occurred while the system tried to export mail templates. Specify a writable file. Some of the selected objects have editors open. Some of the selected objects have editors open. Reserve them to edit. The objects might be reserved by another person. The selected application has an object list open. Working lists that are currently being viewed cannot be deleted. errorMessage Unable to retrieve application from ARSystemServer. 5079 Error 5080 Error 5081 Error 5082 Error 5083 Error 5084 Error 5085 Error 5086 Error 5087 Error 5088 Error 5089 Error 5090 Error 5091 Error 5092 Error 5093 Error 5094 Error 5095 Error Unable to retrieve the object from the AR System server.00 5076 Error 5077 Error 5078 Error Cannot export to file fileName. Cannot export to file. Unable to add new action. Selected objects cannot be deleted. Unable to export mail template. There are already 25 actions. Some of the objects you want to edit are not reserved by you.BMC Remedy Action Request System 7. The file type must be in either def or xml format. Cannot export to file fileName. errorMessage 182 Error Messages Guide .

The table column field fieldName refers to a remote field which does not exist. errorMessage This can occur when the preference server is down or when the network is slow (leading to a timeout). 5105 Error 5106 Error 5107 Error 5108 Error 5109 Warning 5110 Error 5111 Error fieldType Field “fieldName” has no label. ARSystemServer The record for the user in the AR System User Preference form might contain bad data or be corrupted. You can dismiss this window without changing the login information for the current user. fieldType Field “fieldName” has missing layout information. create a minimum value that is smaller than the maximum value. Add at least one functional currency value before you save. you must add forms to the application. AR System User Preference form not found on the server. or currency field. Currency field “fieldName” has no functional currency values. specify a user name. When creating a decimal. Error connecting to preference server. Update the value to a valid field by creating the missing field. Modify its layout to display it. integer. The AR System User Preference form is automatically recreated when you restart the AR System server. To continue. Only one reservedFieldType field is allowed per form. Error connecting to preference server. integer. Save successful with warnings. 5112 Error 5113 Error Chapter 2 Action Request System error messages 183 . Enter a user name. To define statistics. No AR System servers selected to log on. or currency field. The navigation fields you deleted had associated items. Error connecting to preference server.AR System error messages 5096 Error 5097 Error 5098 Error 5099 Error 5100 Error 5101 Error 5102 Error 5103 Error No user name entered to log on. or currency field. real. There are no forms included in the application. Update the fieldType field to reference a valid field before you save. dataType Field “fieldName” has a minimum value equal to the maximum value. Contact your AR System administrator. To continue. you specified an invalid range of minimum and maximum values. you specified an invalid default value. To change the login information. integer. When creating a decimal. To continue. Add at least one AR System server name. dataType Field “fieldName” has a default value less than the minimum value. real. Using the database name as the label. create a minimum value that is larger than the maximum value. resultsListField field is not allowed in a display-only form. you specified an invalid range of minimum and maximum values. Use the Form > Edit Menu Bar command to access these orphaned items. dataType Field “fieldName” has a minimum value greater than the maximum value. fieldType “fieldName” references a field that does not exist. You must specify a user name to log in. or remove the column field. real. The AR System server might be down. When creating a decimal. create a default value that is within the minimum and maximum ranges.

possibly because one or more fields were deleted. The error occurs when you try to open a Web . This form contains a non-standard set of distributed fields. panel Field “panelName” has an initial size less than the minimum size. This message applies only to panel fields inside the Collapsible and Splitter holder. 184 Error Messages Guide .0 and later. To continue.5. The form cannot be saved. To continue.00 5114 Error dataType Field “fieldName” has a default value greater than the maximum value. you have specified same value for the minimum and maximum properties. When creating a decimal. integer. real. This message applies only to panel fields inside Collapsible and Splitter holder. create a initial size that is greater than the minimum size. 5117 Warning panel Field “panelName” has a minimum size equal to the maximum size. Table fields must have at least one column. or currency field. fieldType “fieldType” has no cell fields. For a panel field inside a panel holder.Legacy as the default view. To continue. fieldType “fieldName” has no columns. Add a cell field. you have specified an invalid initial size. Distributed fields are system-generated and cannot be mixed-and-matched. or Advanced to return to a standard set of fields. you specified an invalid default value. which is not supported in AR System 7. Add a column. create a default value that is within the minimum and maximum ranges. Table fields must have at least one cell. See the Form and Application Objects Guide for information about table fields. create a default value that is within the minimum and maximum ranges. For a panel field inside a panel holder.Legacy (Relative) view. To continue. Full. The application could not be found on the AR System server. Switching to another supported view type. you have specified minimum value greater than maximum value. 5118 Error 5119 Error 5120 Error 5121 Error 5122 Error 5123 Error 5124 Error 5125 Warning 5127 Error 5128 Warning This view cannot be deleted because a form must have at least one view. panel Field “panelName” has a minimum size greater than the maximum size. The following indexes are empty and will be ignored: indexNames Unable to add this form to application applicationName. This form has Web . create a minimum size that is smaller than the maximum size. The form cannot be saved. When creating a decimal field. Select None. panel Field “fieldName” has an initial size greater than the maximum size. This message applies only to panel fields inside the Collapsible and Splitter holder. See the Form and Application Objects Guide for information about table fields. create a initial size that is smaller than the maximum size.BMC Remedy Action Request System 7. Enter a value that is equal to or greater than 25. Basic. To continue. For a panel field inside a panel holder. For a panel field inside a panel holder. you specified an invalid default value. This message applies only to panel fields inside the Collapsible and Splitter holder. 5116 Error panel Field “fieldName” has a minimum size less than 25. This message applies only to panel fields inside the Collapsible and Splitter holder. For a panel field inside a panel holder you have specified an invalid initial size. you have specified minimum size of less than 25. It might have been deleted. Use the Distributed Fields dialog box to re-create a standard set of distributed fields in your form. An inconsistent set of distributed fields is present in your form. The view is switched to the standard view. which is not supported in this version of Developer Studio.

The specified file name contains invalid characters. Cannot export to file fileName. Provide the required value. Chapter 2 Action Request System error messages 185 . Add an item to the character menu. Cannot export to file fileName. Specify an export destination file name. label is required. The specified file name does not contain an extension.DEF or . To delete distributed fields. valueIndex must contain a non-NULL value. Use the reported error value to help identify the root cause of the problem. Provide at least one operation node. Unknown error: error. valueIndex does not have a valid value. Cannot export to file fileName. The Entry Point Guide has no starting active link. Cannot export to file fileName. At least one field type must be selected for ‘fieldType’: select any one type from the check boxes. Internal error. An unknown or unexpected error occurred. labelIndexList has more than 5 labelIndex values defined. The specified directory does not exist. Empty mapping. It must be greater than 0 and less then a 10 digit number. The start active link is not allowed unless an application display order is also specified. The following characters are invalid in file names: . It has no items. This message occurs when an incorrect data type is associated with distributed fields. Start active link “activeLinkName” does not exist.XML. The character menu cannot be saved. Mappings are not present in the Mapping table on the Operations panel. If this error is received. The specified directory contains invalid characters."/\[]:. This message appears when Developer Studio catches an unknown or unexpected exception. select None in the Distributed Fields dialog box and click OK. The following characters are invalid in directory names: Windows— " \ [ ] UNIX— . " \ [ ] : 5133 Error 5134 Error 5135 Error 5136 Error 5137 Error 5138 Error 5139 Error 5140 Error 5141 Error 5142 Error 5143 Error 5144 Error 5145 Error 5146 Error 5147 Error Cannot export to file fileName. Contact your AR System administrator. provide a non-zero value. The extension of the file must be . A file name must be supplied. WSDL expected at least one operation element.AR System error messages 5129 Error 5130 Error 5131 Error 5132 Error This form contains a distributed field of the wrong datatype. At least one operation must be added to port: port. Display order expected.

viewName You tried to add fields to the view that already exist in the view. Load of model object objectName failed. The WSDL file that is being loaded is not valid because it requires mandatory elements and a specific format. when a field is selected in the field selector. An attempt was made to access a form that is not present on the AR System server. The field ID or field name is invalid. a field selector for Field or Button/Menu Field contains invalid selection. Provide at least one mappingName. a valid enabled option must be selected. In the Execute Option Panel of the active link. Internal error. This occurs when you did not enter a valid value for the item in question while working in a Developer Studio selector dialog box. Undefined XML mapping item name. You must select a valid option for the selected Execute Options field. The character menu cannot be saved. Table fields must have at least one column. Field with execution order needs a valid field selection. There are no columns in the table: tableName.5. The server has no form with the specified name. name is not a valid form name. Any fields already in the view are unaffected. mappingName has not been provided. Select an existing value or enter a valid value for the item. Supply the required label. field contains an invalid field selection.00 5148 Error 5149 Error 5153 Error 5154 Error 5155 Warning 5156 Error Unable to locate or load the specified file fileName. See the Form and Application Objects Guide for more information about table fields. such as the Field Selector or the View Selector. The specified name is not a valid field name for the current form. item does not contain a valid selection.BMC Remedy Action Request System 7. 5157 Error 5158 Error 5159 Error 5160 Error 5161 Error 5162 Error 5163 Error 5164 Error 5165 Error 5166 Error 5167 Error 186 Error Messages Guide . In the Execute Option Panel of the active link. or the form is on another server. Verify the spelling of the name to make sure that you specified a legal field. executeOnCondition has no valid field. value is not a valid selection for propertyName. Form does not exist on supplied AR System server ARSystemServer. Mapping is not present in the field mapping table. The following fields already exist on the view. Either the specified name is incorrect. Verify the spelling of the name to make sure that you specified a legal field. Only administrators can edit objectName on ARSystemServer. The menu or a menu item has an empty label. This might be because workflow points to a form that no longer exists. Mapping is not present in the field mapping table.

the server is down. or when you are not an administrator or subadministrator user for the server. or the AR System server version is less than 4. A menu parent cannot be added as a child to a horizontal navigation field. All objects are selected and no additional objects are available for adding to the selection.0. At least one port must be added to this web service. There are no additional objects available for selection. Enter a panel name to create. see error. Reserve failed for this object. error The file is read-only. is corrupted. Field: fieldName is not added. error Cannot be loaded because the image could not be accessed. error The file is read-only. No groups selected. BMC Remedy Developer Studio failed to connect to a server. Provide a value. The value supplied was greater than the maximum value allowed for this field. The value supplied was greater than the maximum value allowed for this field. Buttons must have values.AR System error messages 5168 Error 5169 Error 5170 Error 5171 Error 5172 Error 5173 Warning 5174 Error 5175 Error 5176 Error 5177 Error 5178 Error 5179 Error 5180 Error 5181 Error 5182 Error 5183 Error 5184 Error 5186 Error 5188 Error 5189 Error Only administrators can edit deployable applications on ARSystemServer. Use Save As to save a copy of your changes. or there was an error writing to the file. Provide a label. or is too large. This can occur when the server is down. Chapter 2 Action Request System error messages 187 . WSDLPorts Unknown error occurred while attempting to connect to the selected AR System server. the file path is invalid. or there was an error writing to the file. For more information. Buttons must have labels. The Entry Point Application List Display Order value has been reset to 2147483647. You can only delete methods. AR System server name ARServerName is invalid. when the network is too slow (leading to a time-out). Select at least one group. A menu parent cannot be added as a child to a horizontal navigation field. Your changes cannot be saved. Use Save As to save a copy of your changes. as objectType is reserved by user userName. Refresh the object list to see if this object is reserved. Unable to Export Custom Button Configuration. The Message Number value has been reset to 2147483647. objectType cannot be reserved due to error: error. the file path is invalid. Select a method to delete. Unable to export column preferences. Failed to load selected image.

Invalid primary field ID is defined for the root mapping item using form formName. error The file is read-only. there was an error writing to the file. there was an error writing to the file. The listed field could be found on the listed form. the file path is invalid. Error Messages Guide . Hours must be specified. Field fieldName has no associated parent form. ARSystemServer is not valid. Form does not exist not exist on AR System server. ARSystemServer is not valid due to error. or there was an error on the AR System server. AR System Server name expected in property.BMC Remedy Action Request System 7. No primary field is defined for the root mapping item using form formName. The label must be unique. because you entered an invalid server name. propertyName is not in the correct format. string is not a valid qualification. AR System server name is empty in a workflow action.5. It might have been deleted from the form. propertyName can only have a maximum length of maximumSize. The label \”guideLabel\” is already being used in the guide. There was a failure during login. the file path is invalid. providing a name that has not yet been used in the guide. such as a Set Fields or Push Fields action. for example. A property is invalid. error The file is read-only. Unable to transform property due to an API error error.00 5190 Error 5191 Error 5192 Error 5193 Error 5194 Error 5195 Error 5196 Error 5197 Error 5198 Error 5199 Error 5200 Error 5201 Error 5202 Error 5203 Error 5204 Error 5205 Error 5206 Error 5207 Error 5208 Error 5209 Error 188 Cannot export to the file. AR System Server name ARSystemServer is invalid. The Change Field menu is empty or invalid. Missing hour information. Unable to import objects from file. or there was an error on the AR System server. The parent form is missing from the web services field map for fieldName. providing a string for a numeric value. Unable to locate field fieldName on form formName. Rename the label. Labels in guides must be unique. This is an internal error. Specified primary field ID does not exist on the form. Connection could not be established to the selected AR System server in a Set Fields action due to an unknown reason. propertyName must have a minimum length of minimumSize. Minutes value must be between 0-59. menuName is not valid menu selection for propertyName. Unable to locate form formName.

The escalation time interval is set to 0. To save a SQL Set Fields Action. This is not validated but cannot be left blank. Select a reference field to continue.com. No If actions were defined for the filter. Unable to convert the output mapping XML document. an authorized reseller.com. Unable to parse the XML document. Time does not contain valid values. The Selected Fields option requires you to specify a field. and Time is not entered. or active link. contact your BMC sales representative. This error can result from corrupted mapping XML. and is configured for each client to access a maximum of one server. you did not select the reference field required when the notification Mechanism is Cross-Reference. To obtain a version of AR System without these limitations. The cross-reference mechanism is not allowed unless a reference field is also specified. Specify a minimum width that is less than or equal to the maximum width. contact your sales representative or visit www. embedded in another composite field. error Add at least one If action.AR System error messages 5210 Error 5211 Error 5212 Error 5213 Error 5214 Error 5215 Error 5216 Error 5217 Error 5218 Error 5219 Error 5220 Error 5221 Error Missing weekday information.bmc. A composite field. embedded in another composite field. fieldType Field “fieldName” has a minimum width greater than the maximum width. or visit http://www. includes a maximum of three fixed licenses. fieldType Field “fieldName” has a minimum height greater than the maximum height. escalation. you must specify a SQL command. Specify a SQL command. 5222 Error 5223 Note 5224 Error Forms cannot be moved from “ARServerA” to “ARServerB”. The Minimum value should not be greater than the Maximum value for this property. The Minimum value should not be greater than the Maximum value for this property.bmc. Enter a SQL command to continue. When creating a Notify filter action. Server: ARSystemServer. For unlimited capabilities. You must specify at least one If action. Specify a minimum height that is less than or equal to the maximum height. which is not allowed. Invalid interval time. This error can result from corrupted mapping XML. A weekday or day in the month must be specified. This version of BMC Remedy AR System has a maximum limit of 2000 requests per database table. with the Fill layout has a Height property under the Display category. Unable to convert the operations XML document. With the Escalation Time Execution option. Run By = Time. An attempt was made to drag a form from AR System server A to an application on AR System server B. BMC Remedy Action Request System is ready for use or evaluation without purchasing or activating an authorization key. A composite field. Chapter 2 Action Request System error messages 189 . Unable to convert the input mapping XML document. with the Fill layout has a Width property under the Display category.

Z order for fieldType field “fieldName” has been modified to make it consecutive with other fields. The duplicate files were not added.00 5225 Error 5226 Error 5227 Error 5228 Error 5229 Error 5230 Warning Form already exists on ”applicationName” application. You cannot delete the following core fields: fieldNames You cannot move a panel to the same parent.5. Save the filter or escalation only if you are understand the risk in what you are doing. Provide a correct remote form name. Duplicate file names were found in the current directory. for example. see the description of error 90. Specify a value. This error is similar to error 90. 5231 Error 5232 Error 5233 Error 5234 Error 5235 Error 5236 Error 5238 Error 5239 Error 5240 Error 5241 Error 5242 Error 5243 Error label is empty. This error occurs if an operation name like WSDLNameResponse is used and there is already an operation named WSDLName. A table column field is mapped to a remote field of a different type. Port not defined for operation: operationName. Z order for fieldType field “fieldName” has been modified to fix duplicate Z order. The Log to File action will create the file. Empty assignment value for target field fieldName. Because internal operations are saved with a suffix of Response.BMC Remedy Action Request System 7. For troubleshooting steps. Duplicate operation: operationName. You created a duplicate operation name in the Operations List. fieldType “fieldName” Field contains information that does not match the remote field type. Cannot establish a network connection to the AR System server. 190 Error Messages Guide . Invalid operation name “operationName” conflicts with output top level parent name for operation: operationName. you run the risk of creating infinite loops and overwriting the original record in a distributed transfer operation or a distributed return operation. All operation names must be unique. Creating field is not allowed in Tab Order Increment on Click mode. Set Field actions and Service action assignments need an assignment value for each fields added in mapping. The file name being added already exists in the current directory. fieldType “fieldType” contains an invalid form name. Selecting the override loop option could cause an infinite loop in the system. Missing port in WSDL operation in a web service. a column field with a type of char using a remote button field. You cannot create data fields on audit forms. filePath does not exist. fieldType “fieldName” is linked to an unreachable AR System server ARServerName. Remote form name is empty or form does not exists on AR System server. avoid using Response as a suffix. By shutting down loop protection.

png.jpeg.png. It does not appear to be a supported image format. Following Column fields for tableFieldType tableFieldName do not have referenced fields columnFieldNames on the current form. .jpeg. and . . Valid file types for images are . Objects might have been deleted or the names modified. Active links and filters can be attached to multiple forms.dib. AR System allows a maximum of 99 items on any one menu level.bmp. They will be deleted on OK. as objectName is reserved by user userName. Only servers that are 7. Unable to display image. The view will return to the default. Changing the form might make existing actions invalid. Web Services Publishing Location must contain a valid location. You have not specified any allowable currency types.AR System error messages 5244 Error 5245 Error 5246 Error 5247 Warning 5248 Error 5249 Error Vendor table tableName does not have any available columns. . All currency types are now allowed. Search did not match any objects. 5250 Error 5251 Error 5252 Error 5253 Error 5254 Warning Exporting flashboard objects in XML is not supported.jpg. The image cannot be displayed. The web service location must end with the web service name. Unable to display background image. . Web Services Publishing Location contains invalid name reference URL. It does not appear to be a supported image format. Search was canceled by the user.bmp. the Form View you selected was not found on the AR System server. but permissions have not been set to public for ''webServiceName''. the view used in the action is the default administrator view. Your changes cannot be saved. You can use multilevel menus to split large menus into multiple smaller and more manageable menus. Web Services Publishing location contains 'public' within the URL. Check existing actions. you changed which form controls the active link or filter. . Cannot connect to server with version version. 5255 Error 5256 Note 5257 Error 5258 Warning 5259 Warning 5260 Error Chapter 2 Action Request System error messages 191 . Accordingly. no results were returned. When you created an Open Window action.gif.jpg. Invalid Web Services Publishing Location has been updated with correct name. Valid file types for images are . The character menu definition contains too many items on one level of the menu tree. Deleted objects do not appear even if the database is not synchronized. and . . Cannot add a submenu because a menu in a character menu cannot have more than 99 submenus.gif. The active link activeLinkName could not find the view viewName in form formName. Verify your actions after you change the form in an active link or filter. The background image cannot be displayed. . When modifying an active link or filter. Open the form in BMC Remedy Developer Studio to verify that the view you want to use exists. When the system searched for an object. .dib. The results list might not be complete. The web service location must be a non-empty string. Selected flashboard objects will not be exported.0 or later versions are supported.

Add an integer field to the primary form. A valid Configuration Name has not been selected. Output Mapping to a static value is not allowed for mapping item “value”. A valid Web Services File has not been selected. The entry name might have been deleted from the form. this error is returned. You must select a valid Configuration Name. 5265 Error 5266 Error 5267 Error 5268 Error 5269 Error 5270 Error 5271 Error 5272 Error 5273 Warning 5274 Error 5275 Error 5276 Error 5277 Error 5278 Error 5279 Error 192 Error Messages Guide . There are no integer fields on this form. The menu might have been deleted. VARIANT. The named menu “menuName” referenced by “fieldName” is not defined. In the View form. Error connecting to BMC Atrium Orchestrator server.BMC Remedy Action Request System 7. or Compatible. The type is incompatible. If the parent method’s return type is not one of these types. Errors were encountered while accessing the file. A valid Operation has not been selected. the parent method’s return must be one of the following types: IDispatch. A valid Web Services Port has not been selected. A valid Process has not been selected. Column “columnName” used by Field “fieldName” is already referenced by another field. You must select one primary form. A panel or a page cannot be moved to its’ child page holder. You must select a valid Process Name. The fieldType must match the databaseColumnType. You cannot add a method here. When you nest a method. Unable to add an active link. columnName in the Column property of fieldName is already used in another field. Reason: error Closing current editor due to resource error.00 5261 Error 5262 Error 5263 Error 5264 Error You cannot move a panel to any field in the child hierarchy. fieldType Field ''fieldName'' cannot refer to Column ''databaseColumnName'' of type databaseColumnType. The configuration name name does not exist in the AR System Orchestrator Configuration form. You must select a valid Operation. Use some other available columnName. error This is an internal error. Layout style for panel panelLabel is changed from XY to Fill. You must select a valid Web Services Port. A valid Web Services Operation has not been selected. You must select a valid Web Services File. You must select a valid Web Services Operation. An Execution Order From Field Value option cannot be used in a Goto action if the primary form does not have integer field.5.

Invalid schedule interval. Specify a valid variable name that exists. Invalid alarm variable. Group access is not defined -. The alarm cannot be saved. Wait until the reserved application is released. Group access is not defined -. Specify a user and a message for the alarm notification. Pie charts cannot be selected for History or Summary display type. Specify a value that is greater than zero for the threshold value. or the specified variable name is invalid. The expiry schedule for collecting data in a Flashboards variable when one of the expiry options is chosen was incompletely specified. Invalid alarm variable. It might not exist or the server might not be able to retrieve it. Invalid alarm variable name. The threshold value must be a non-negative integer. 5281 Error 5375 Error fieldName is not allowed in a view form. See following messages for more information. See the following messages. A variable with the given name does not exist. You cannot create an Attachment Pool field in a view form.only an administrator has access to this flashboard. Alternatively. This occurs when object reservation is in use on the server.AR System error messages 5280 Error Cannot create new object because application “applicationName” is reserved by another user “user”. Alarm variable variableName is invalid. The alarm variable was not specified. Correct the following errors. Specify a trigger that exists on the AR System server for the alarm. and you try to create a new object in an application that is reserved by another user. The threshold value must be greater than zero. Specify an alarm variable that exists. Specify a variable that exists on the AR System server for the alarm to monitor. A user and a message must be specified for the alarm notification. Alarm variable variableName does not exist. Add the object to the application when the application is no longer reserved.only an administrator has access to this variable. create the object outside of the application by using the All Objects node in the AR System Navigator. Alarm variable variableName is invalid and might not exist. Specify a non-negative integer for the threshold value. See the following messages for the errors to correct. Chapter 2 Action Request System error messages 193 5376 Error 5377 Error 5378 Error 5379 Error 5380 Error 5381 Error 5382 Error 5383 Error 5384 Error 5385 Error 5386 Error 5387 Error 5388 Error 5389 Error 5390 Error . Specify an alarm name that exists on the AR System server. Specify a variable that exists on the AR System server for the alarm to monitor. Specify an alarm variable that exists. The alarm trigger is invalid. The amount to keep data before it expires must be an Integer.

The fieldName field’s length cannot exceed number characters. Add at least one server name. Target form is not selected. This version of BMC Remedy AR System has a maximum limit of 2000 requests per database table. Select a data file. You must select a target form name. Import failed.com. Specify a field length within the listed number of characters. Error connecting to preference server. Data file is not selected. Source form name is empty.bmc. For unlimited capabilities. Switching target form will clear all the existing mappings. No user name entered to login.5. and is configured for each client to access a maximum of one server. Create a mapping before doing the import. 5401 Error 5402 Error 5403 Error 5404 Error 5405 Error 5406 Error 5407 Error 5408 Error 5409 Error 5410 Error 5411 Error 5412 Error 5413 Error 5414 Error 5415 Warning 5416 Error Login failed for server ARSystemServer.00 5400 Note This version of BMC Remedy Action Request System is ready for use or evaluation without purchasing or activating an authorization key. No servers are selected to login. To obtain a version of AR System without these limitations. 194 Error Messages Guide . You must select a source data file. Select a valid source data file.BMC Remedy Action Request System 7. Select a field. AR System User Preference form not found on the server. No field is selected. You must select a field. ARSystemServer The record for the user in the AR System User Preference form might contain bad data or be corrupted. The import file cannot be accessed or the AR System server might be down. Use Save As and save file fileName to . contact your BMC sales representative. You must enter a user name. Server: ARSystemServer. Select a target form name. Contact your AR System administrator. includes a maximum of three fixed licenses.com. You must select a data file. You must select a form. Contact your AR System administrator. No mappings found to import. The AR System User Preference form is automatically recreated when you restart the AR System server. error This can occur when the AR System server is down or when the network is slow (leading to a timeout). Error connecting to preference server. Saving to . contact your sales representative or visit www. Enter a user name.armx file format. Server may be down. Select a form. Error connecting to preference server. or visit http://www. an authorized reseller.bmc.arm file is not supported. Form is not selected. ARSystemServer This can occur when the preference server is down or when the network is slow (leading to a timeout). A server must be selected when logging in.

Reason: reason Import engine received an exception. Enter a value or select a field or a keyword. Invalid search locations specified. 5533 Warning Searching for a string inside string constants is a intensive task.AR System error messages 5417 Error 5418 Error 5419 Error 5420 Error 5421 Error 5422 Error 5423 Error 5424 Error 5425 Error 5426 Error 5427 Error 5525 Error 5526 Error 5527 Error 5528 Error 5529 Error 5530 Error 5531 Error 5532 Error No fallback value is entered. Invalid field ID specified. To specify text as a field ID. You must restart the AR System Server for the changes to take effect. at least one location must be selected. click the Configuration tab. Enter text in Search Text. Select this option only when you are sure that the entered search text will not match many objects. a numeric value must be entered in Search Text. but none of the selected Search-In locations match any fields. Search text cannot contain the following special characters [characters]. No search location was provided.” Record Object Relationships configuration is not set. Enter a value or select a keyword. Reason: reason The specified file cannot be parsed.0 or later. You must enter a value or select a keyword. For every selected object type. Chapter 2 Action Request System error messages 195 . After the server restarts. try searching again in BMC Remedy Developer Studio. Reason: reason The specified file cannot be read. Invalid search text specified. possibly because the file could not be accessed or a write to the file failed. fileName Saving the file failed. No mapping value was entered. Reason: reason The AR System server version is version. It must be version 7. This error is reserved for a case where search cannot determine what went wrong. Select at least one search location. The specified file is not found. Search cannot be performed on \”ARSystemServer\. Empty search text. Reason: reason Cannot create the Mapping editor. Treat as field ID is selected. Cannot save to the specified file. Import failed. Search cannot be performed on the selected AR System server because the Record Object Relationships setting is not enabled. Unknown error: exception. Reason: reason The specified file has unsupported encoding and cannot be read. and then and select the Record Object Relationships option. You must enter a value or select a field or a keyword. Invalid search locations specified. update system information in the AR System Administration Console using BMC Remedy User. In the System Information form. To enable this setting.

string.View or Display can only be mapped to XML Datatype .00 5534 Error No objects were selected. Invalid mapping because of incompatible data types.hexBinary or base64Binary. AR Datatype . Invalid mapping because of incompatible data types. or gMonth.double or float. gMonthDay. Related Objects cannot be added. AR Datatype . AR Datatype . You tried to map incompatible data types.time. or unsigned Long. see the Configuration Guide. unsigned Int. Invalid search locations specified. AR Datatype .string.Date can only be mapped to XML Datatype .int. Only one search can be performed at a time. select at least one object using the Choose… button. You have chosen to match only string constants. You tried to map incompatible data types. 5535 Error 5536 Error 5550 Note 5551 Error 7001 Error 7002 Error 7003 Error 7004 Error 7005 Error 7006 Error 7007 Error 7008 Error 7009 Error 7010 Error 196 Error Messages Guide . You tried to map incompatible data types. AR Datatype . For Selected Objects scope at least one object must be selected. AR Datatype . gYearMonth. You tried to map incompatible data types.dateTime. AR Datatype . Select the Record Object Relationships option on the Configuration tab of the AR System Administration: Server Information form. You tried to map incompatible data types.TimeOfDay can only be mapped to XML Datatype . long. You tried to map incompatible data types.5. This error occurs when an attempt is made to search again when a previous search is still running in the background. You tried to map incompatible data types.date. AR Datatype . You tried to map incompatible data types. Invalid mapping because of incompatible data types.string. or unsigned Byte. Invalid mapping because of incompatible data types. boolean.BMC Remedy Action Request System 7. You tried to map incompatible data types. Search is already running in background. byte. unsigned Short. For more information. You tried to map incompatible data types. but no objects have been selected on which to perform the search. short. Invalid mapping because of incompatible data types. Invalid mapping because of incompatible data types.Integer can only be mapped to XML Datatype . gDay. Invalid mapping because of incompatible data types. This error occurs when Selected Objects is chosen as the search scope. gYear. Record Object Relationships configuration is not set.Enum can only be mapped to XML Datatype .Decimal can only be mapped to XML Datatype .Real can only be mapped to XML Datatype . but none of the selected Search-In locations match any string constants.DateTime can only be mapped to XML Datatype . AR Datatype . Invalid mapping because of incompatible data types.Diary can only be mapped to XML Datatype . Invalid mapping because of incompatible data types.Attachment can only be mapped to XML Datatype .decimal. AR Datatype . To resolve this error. Invalid mapping because of incompatible data types. Analysis completed with no inconsistencies found.

The Order field on the Basic tab of the Active Link Guide dialog box. A problem occurred when the external XML schema was loaded. Failed to resolve existing mappings with the specified schema. the dependencies of an element in a schema might be missing. Specify a value of one or greater than one for the entry point order. An integer value specifying the interval (in seconds) to collect statistics is required. Failed to initialize JRE and internal java module.AR System error messages 7011 Error A few warnings occurred while loading the xml schema. The WSUtil70. Please enter statistics logging interval for form. Turning off the Auto Layout mode. An integer value specifying the interval (in seconds) to collect statistics is required. The entry point order must be between 1 and 2147483647.dll file must be in the \Admin folder under AR System. or a default entry point on the Basic tab of the Form properties dialog box. Auto Layout Style Property must be available at application level or view level. Remove references to forms that are not in the application or in access points. If this file is not present. Check the required JRE configuration information in the Configuration Guide. or you opened a web service that is imported from another system but that does not have all the forms associated with the web service. No style sheet is available for the current view or the application. Failed to get top level elements from xml schema. Specified schema could not be imported. Can not switch to restricted list as selected form(s) do not belong to the application.dll (related to webservices). A problem occurred when the XML data type was retrieved from the schema. You entered an invalid URL (or a URL that you have no permissions to access) for loading Wsdl while creating the filter Set Fields web services action. and then turn on Auto Layout. For example. must have a value that of one or greater. the style sheet must have properties defined. The dynamic field values must contain valid field / keyword references. Please enter a new order. The interval is blank or invalid. Please enter statistics logging interval for application. verify the BMC Remedy Administrator installation logs. You loaded the external XML schema for the input and output mappings of a web services operation. Please verify your installation procedure. or the style sheet was removed. Problems occurred while the web service was imported from a definition file or while the web service was saved. Failed to create internal mapping from wsdl. Failed to create initial mapping from the specified top level element/type. Enter a field reference or select a keyword from the list for the field. 7012 Error 7013 Error 7014 Error 7015 Error 7016 Error 7017 Error 7018 Error 7034 Error 7035 Error 7036 Error 7037 Error 7038 Error There are no properties in the style sheet. A dynamic field value was specified that does not match a field reference on the current form or a keyword. Chapter 2 Action Request System error messages 197 7041 Error 7042 Error . The Sun Java runtime environment™ (JRE™) dependencies are missing or corrupt. When exporting a style sheet to an XML file. You loaded a new XML schema that might be affecting the mappings already created in the web service. The interval is blank or invalid. Failed to generate wsdl from internal mapping. Add the style sheet. Failed to load WSUtil70.

Do you wish to Continue? During the import-in-place operation.def and the objects are exported in definition file format. resulting in a loss of data and/or broken workflow. the license cannot be made less restrictive. You must assign roles to the packing list for proper access control. You must close the application window before you can delete the application 198 Error Messages Guide . 7052 Warning Moving a packing list into a deployable application will strip away all non-implicit groups from the packing list. Do you wish to Continue? This is a warning that as a result of the import-in-place operation from a pre-6.BMC Remedy Action Request System 7. You must either create a dynamic field assignment or clear the Advanced option. you cannot unlicense it.xml file name extension. You must assign roles to these objects for proper access control. 7046 Error 7047 Error 7048 Error 7049 Warning Navigation area is greater than VUI area. The objects will be exported in def file format. The most likely change to make is to increase the width of the View Area. The value for the width of the Navigation Area is greater than the value for the width of the View Area. Can not delete an application which is open in an Application Window. It is recommended that you back up your data and current definitions before continuing.5. Restart the AR System server. Export of locked objects is not supported. The Application Statistics Configuration form is deleted or corrupted. Licensing an application is not a reversible process. Left margin/Level Indent in the navigation properties is greater than the Navigation Area. Do you wish to continue? This is a warning that after an application is licensed. 7053 Warning All the Data associated with the forms selected for Import will be deleted. You should back up your data and current definitions before continuing. The sum of the leftMargin and the levelIndent values is greater than the width value in the Navigation Area. XML export of locked objects is not supported in this version. Do you want to continue? This is a warning that roles must be assigned to packing lists for access control in deployable applications. the extension is changed to .00 7043 Error 7045 Error Application Statistics Configuration form not found on the server. This is a warning that the license for a licensed application cannot be made less restrictive. which automatically re-creates the form. 7050 Warning 7051 Warning Permissions should be supplied to the owning application object. data might be lost and workflow that depends on fields that are deleted might be broken. If you specify an . The active link cannot be saved because the Advanced option is selected and no advanced features are used. 7054 Warning 7055 Warning 7056 Error Once you have licensed an application. This is a warning that you should supply valid corresponding permissions to the application object that owns the current server object. Moving a form into a deployable application will strip away all non-implicit groups from the form and its related workflow objects. The set field list did not contain a reference to a dynamic assignment. This operation may delete some fields. Reduce the value for the leftMargin or the levelIndent. data might be lost and workflow that depends on fields that are deleted might be broken.0 AR System server. Do you want to continue? This is a warning that roles must be assigned to objects for access control in deployable applications.

Please enter Qualification query for this search When you try to create a defined search (in the View Properties dialog box).AR System error messages 7058 Warning 7059 Warning This is an archive form. which might be needed as a backup copy of data on the source form.0. which is not supported in version 7. which probably indicates that the system is low on resources. Then. An internal error occurred during HTML processing. Can not add Menu types to Horizontal Navigation fields. An internal error occurred during HTML processing.Legacy (Relative) view. This informational messages explains that if you license a form. Please provide valid target directory for the following object type(s): objectType A target directory is required for all object types when the BMC Remedy integration with ClearCase is used. An internal error occurred during HTML processing. it has been modified by userName. Restart the computer running AR System. which probably indicates that the system is low on resources. change the default view to Standard. which is no longer supported in AR System 7. Do you want to overwrite userName's changes with your changes? This prompt appears when you try to modify an object that someone else is currently modifying. this warning appears when you click OK to close the dialog box. 7060 Error 7061 Error 7062 Error 7064 Error 7065 Error 7069 Error 7070 Error 7071 Error 7072 Error Unable to Save/Update Form due to an HTML processing error: systemErrorCode. The default view of this form is Web . Please enter a non-empty string in NULL Values field. To view this form in version 7. You entered 0 as the statistics logging interval. Restart the computer running AR System. which probably indicates that the system is low on resources. any associated archive form is automatically licensed.jsp file names after deployment. If you change a table field’s properties in the Multiple Field Properties dialog box.0 and later. Restart the computer running AR System. Tables may not be audited. you must enter a qualification for the search. Their audit status will not be changed.0. You tried to add menu types to horizontal navigation fields. 7076 Error 7077 Error 7078 Error 7079 Warning The specified application does not exist: applicationName.Legacy (Relative). Do you wish to continue saving? Since you retrieved this object from the server. For example. Unable to merge template due to an HTML processing error: systemErrorCode. Form does not have Web Alias. Some forms had archive forms associated with them. You tried to enter an empty string in the field. Unable to Import web page due to an HTML processing error: systemErrorCode. Chapter 2 Action Request System error messages 199 . Enter a number greater than 0. The error occurs when you try to open a Web . The error occurs when you try to open an application that was deleted after you logged in. 0 is not a valid value for statistics logging interval. You must enter a value. These archive forms have been automatically licensed. Are you sure you want to delete it? This warning appears because deleting an archive form deletes the data on the form. another administrator might have logged in and deleted the application. This may result in invalid . open it in a previous version of Remedy Administrator.

You must enter a name for the administrator-defined search you are trying to save. Click Display to display the view. The trailing spaces will be trimmed. The error handler does not exist. For an error handler to function. The error handler name can not be same as itself. Audit Log Key key is already in use. Please enter a new size. You attempted an operation against the wrong server. The sub-administrator cannot create deployable applications. attachment fields) into the destination structure occurred. and you confirmed that deleting the key field was the action you wanted to take. Change to the correct server. Could not locate error handler in schema workflow list. Too many levels reached processing filter error handlers. This error will occur if the AR System server encounters a defined error handler that is not associated with the schema related to the parent workflow object. One or more entries match filter conditions—this operation has been defined so that any matches generate an error. and the name has trailing spaces. You tried to create a deployable application. The Any Match for a Push Fields filter action is defined as Error. Contact Customer Support. but you are not an administrator with full access. You entered a form name when performing a Save or Save As operation. The copy operation failed because of problems with permissions. it must be associated with the same schemas as the “parent” workflow object. You deleted the key field in a vendor form. a failure filtering certain field IDs (for example. 8001 Error 8002 Error 8003 Error 8004 Error 8005 Error 8029 Error 8031 Warning 200 Error Messages Guide .BMC Remedy Action Request System 7. or specify the proper name. If you are working with a Unicode server. a workflow object must not refer to itself as its own error handler. Do you wish to continue? Click yes to continue to switch and click No to remain in view.00 7080 Error 7081 Warning 7082 Warning 7083 Warning 7084 Error 7085 Error 7107 Error 7117 Error 8000 Error Please enter a Name for this search. The specified error handler does not exist in the AR System database. The current view has been modified. You entered an incorrect number in the Next Request ID Block Size field in the Basic/Entry tab of the Form Properties window. The name of an error handler is limited to 254 characters. Some of the fields and/or workflow in this form are not supported in this version of the client. Internal AR System server error. only the current view is modified and saved. The next request ID block size must be between 1 and 1000. or no workflow object is defined by that name. and click Save to save your changes. Trailing spaces are not allowed in the form name. To avoid recursive operations. When a list of field definitions for a form was retrieved. Contents will be lost if you switch the view without saving.5. The error handler name is too long. Filter processing called with no filter context. The parent workflow object is the workflow that has been designed to invoke an error handler when an error occurs. You must designate another field as key field before saving.

To continue. you set the TCP/IP port to a value outside the legal range.65535). A value change is pending on the floating license timeout—change will take effect the next time the server is started. For more information. There was an error creating an RPC connection. The legal range of values are 0 and 1 to 65535. Create the character menu or remove the reference from the container. see the Configuration Guide. consult your database product documentation.may not work on all databases The operation proceeds. you set the RPC socket number to a value outside the legal range. Index length longer than 255 bytes -. because this version of AR System server is no longer supported. 390600. 8034 Warning A value change is pending on the full text floating license timeout—change will take effect the next time the server is started. When connecting the client to AR System server. 8035 Warning 8036 Warning 8037 Warning 8201 Error Referenced character menu does not exist. These server configuration settings do not go into effect until the server is stopped and restarted. some database products do not support indexes exceeding 255 bytes in length. Extraneous characters are ignored. The RPC socket number specified is not one of the legal values (0. Chapter 2 Action Request System error messages 201 . The character menu listed in the message is referenced in a container. The server’s RPC version is not supported. Character(s) remaining after parse completed The server parsed the data you specified. RPC control failed to set non-blocking I/O mode.AR System error messages 8032 Warning 8033 Warning An admin group list was found in an owned container.390669.390694). For more information.check with netstat to view ports in use This message appears when a server is started on a port that is in use. but at least one additional character could not be interpreted. These server configuration settings do not go into effect until the server is stopped and restarted. The RPC-Non-Blocking-IO parameter was set in the AR System configuration file. The number of hours for the Write Floating License Timeout was changed in the Timeouts tab of the Server Info window. An owned container cannot have a list of subadministrator groups. However.390634. 390636 . When connecting the client to AR System server. upgrade to a later version of AR System. Port is busy -. The number of hours for the Full Text Search Floating License Timeout was changed in the Timeouts tab of the Server Info window. The list is disregarded. 390680 . The legal ranges of values are: 0 390600 390621 to 390634 390636 to 390669 390680 to 390694 8202 Error 8203 Error 8204 Warning 8205 Warning 8301 Error The RPC port specified is not one of the legal values (0. but the AR System server continues in blocking mode. Continuing in blocked I/O mode. Only one form can contain the Server Version Control Reservation fields. The administrator’s access permissions are determined by the owning object. but no longer exists. 390621 . 1 .

The operation failed because another user has reserved the active link. The operation failed because another user has reserved the dependent join form. The operation failed because another user has reserved the related escalation. The operation failed because another user has reserved the application. Verify the Object Modification Log option on the Version Control tab of the AR System Administration:Server Information form. The operation failed because another user has reserved the related filter. Version control object modification log mode only supports 0 for disabled mode and 10 for enabled mode.00 8302 Error The data entered is invalid. The operation failed because another user has reserved the related container. The operation failed because another user has reserved the image. Only one form can contain the Server Version Control Object Modification Log fields. The operation failed because another user has reserved the related active link. The operation failed because another user has reserved the escalation. Version control object reservation mode only supports 0 for disabled mode and 10 for enforced mode. Verify the Object Reservation option on the Version Control tab of the AR System Administration:Server Information form. 8352 Error 8353 Error Only one form can contain the Server Version Control Task fields. The operation failed because another user has reserved the container. You must specify a value of 0 or 10. 8303 Error 8304 Error 8305 Error 8306 Error 8307 Error 8308 Error 8309 Error 8310 Error 8311 Error 8312 Error 8313 Error 8314 Error 8315 Error 8316 Error 8317 Error 8318 Error 8351 Error The operation failed because another user has reserved the object. You must save an object on the server before you can reserve it. 202 Error Messages Guide .5. The operation failed because another user has reserved the character menu.BMC Remedy Action Request System 7. The operation failed because another user has reserved the filter. You must specify a value of 0 or 10. The object cannot be reserved because it does not exist on the server. The operation failed because another user has reserved the related application. The data entered is invalid. The operation failed because another user has reserved the form.

but logging failed. The name of a method in an OLE Automation is either empty or exceeds the maximum length allowed (128 characters). Detailed errors follow that explain what part of the method structure is invalid.AR System error messages 8354 Error 8355 Error The operation succeeded. Verify the Definition Files option on the Version Control tab of the AR System Administration:Server Information form. Source Control page. You must provide at least one method for this structure. for example. You tried to set the number of rows for a character field in BMC Remedy Developer Studio to less than 999. or an interface of an OLE Automation active link action is either empty or exceeding the maximum length allowed (128 characters). by an API program. The name of an OLE server or a parameter of an OLE Automation active link action is empty or exceeding the maximum length allowed (64 characters). This error is usually caused by an attachment that is too large. a method ID. 8700 Error 8703 Error 8704 Error 8705 Error 8706 Error 8707 Error 8708 Error 8709 Error 8710 Error 8711 Error Chapter 2 Action Request System error messages 203 . This error can also be generated when an attachment is erroneously reported with a negative size. The method structure required when defining an OLE Automation active link action is empty. Use only these types. you clicked the Browse button but no source control provider is selected in the Provider Name field. but all or some of the corresponding log entries were not added to the AR System Version Control: Object Modification Log form. You must specify a value of 0 or 10. Version control object modification log save definition files only supports 0 for save and 10 for not save. Invalid class ID or interface ID. You must specify the appropriate contents for this structure. The method list required when defining an OLE Automation active link action is empty. AR System forms cannot store attachments of the size reported. Invalid COM value. The data entered is invalid. You must provide at least one method for this structure. In the Server Information Dialog. 8459 Error 8469 Error The number of rows exceeded the maximum allowed limit of 999. Empty automation. The value of an ARCOMValueStruct variable in a method or parameter of an OLE Automation active link action is invalid. Bad attachment locator type. You must install a source control system and select it in the Provider Name pull-down menu before you click the Browse button. Invalid COM name. Please select a source code control provider. Invalid COM method name. Empty COM method. Provide a valid value. The only acceptable attachment locator types are the filename or the buffer. The method structure of the OLE Automation active link action is invalid. Invalid attachment size. Fix the name to continue your work. Invalid COM method. The operation succeeded. The automation structure required when defining an OLE Automation active link action is empty. Empty COM method list. The name of an OLE class ID.

Call guide structure empty. The name identified in the vendor field definition is empty or exceeds the defined length restriction. The parameter list required when defining an OLE Automation active link action is empty. 390680 – 390694). The RPC socket number for the Approval Server process is not one of the legal values (390600. enter a value. The name identified in the vendor form definition is empty. Invalid COM parameter. The parameter structure of a method required when defining a method in an OLE Automation active link action is empty. enter a value. use a field or value. Use the Approval Server Admin-Server Settings form to set this to a legal value. Invalid automation string.00 8712 Error 8713 Error 8714 Error 8715 Error 8716 Error Empty COM parameter list.5. Invalid external table name in a vendor field mapping structure. 8717 Error 8720 Error 8721 Error 8722 Error 8723 Error 8724 Error 8725 Error 8726 Error 8727 Error 8728 Error The value for the Application Check Interval is not within the legal range of 0 to 3600 seconds. To create the Call Guide active link action. shorten the title or lengthen the button. Set this to a legal value. The value for the RPC socket is not set properly. 204 Error Messages Guide . This message occurs when you try to create a Go To active link action without specifying a Go To action label. An automation action string required when defining an OLE Automation active link action is either empty or exceeds the maximum length allowed (2000 characters). Go To action tag is invalid. Go To guide label empty. Empty COM parameter. You must specify the appropriate contents for this structure. This message occurs when you try to create an Open Dialog active link action without specifying an open dialog structure value. The value for Application Check Interval is not set properly. Detailed error messages explain what part of the structure is invalid. supply a title. To create the Go To active link action. If the title is too long.BMC Remedy Action Request System 7. Guide calling itself is not allowed. Continuation button title is empty or too long. The parameter structure of a method in this OLE Automation active link action is invalid. Guide name missing. Invalid vendor form definition. To create the Open Dialog active link action. enter a label. The tag must be a field or value. This message occurs when you try to create a Call Guide active link action without specifying a Call Guide active link name. This message occurs when you try to create a Go To active link action without specifying a field or value for the Go To action tag. This message occurs when you try to create a Call Guide active link action without specifying a Call Guide structure value. The button title cannot be empty or longer than the defined size of the button. To create the Call Guide active link action. If the title is empty. enter a name. Open dialog structure empty. You must provide at least one method for this structure. To create the Go To active link action. The guide cannot contain workflow that calls that same guide.

AR System error messages 8729 Error 8730 Error 8731 Error 8732 Error 8733 Error 8734 Error 8735 Error 8736 Error 8737 Error 8738 Error 8739 Error 8747 Error 8750 Error 8751 Error 8752 Error 8753 Error Vendor forms not allowed in join forms. The field definition for a field on a join form may not be modified after the field is defined. For example. Chapter 2 Action Request System error messages 205 . 1.abc##345 is an invalid decimal value. AR System database connectivity plug-in associated with the form does not support modify operations and a modification was attempted. Changing the field mapping is not allowed for join fields. Invalid decimal value. The currency code is not a valid three character string. You tried to define a disabled or nonexistent client type in the client list by setting the client type to a number less than zero. Changing the type in the field mapping structure is not allowed. Vendor forms may not participate in joins. Set entry operations are not supported for this form. you tried to change a field to a different type. The value must be a non-negative integer. When modifying an existing field in a form. The join form definition includes a vendor form as one of its base forms. Unrecognized currency part tag. The currency part structure tag contains an illegal value. Contact your AR System administrator for assistance. USD. The most likely cause is that the system is out of memory. Unable to access thread local storage. for example. Your system is unable to complete the arithmetic operation. The decimal data is formatted incorrectly. Notify footer name is over the maximum size allowed for the name. Error in plugin. A run-time exception occurred during a Java plug-in server call to a plug-in. Create entry operations are not supported for this form. Notify content name is over the maximum size allowed for the name. Enter a footer name of 255 bytes or less for the email notification template. AR System adds detailed information about the error to the ARServerInstallDir\Arserver\Db\arjavaplugin.234 is a valid decimal value. However. The AR System server encountered a serious error performing a fundamental operating system function.log file. Bad client type. while 1. you can modify it without error by setting it to the existing mapping. Invalid currency code string length. Enter a content name of 255 bytes or less for the email notification template. AR System database connectivity plug-in associated with the form does not support delete operations and a deletion was attempted. Notify header name is over the maximum size allowed for the name. Delete entry operations are not supported for this form. Enter a header name of 255 bytes or less for the email notification template. An arithmetic error was encountered in a decimal calculation. Specify only forms that are not Vendor forms. Only numeric characters are valid as decimal data. AR System database connectivity plug-in associated with the form does not support create operations and a creation was attempted.

The plug-in will not load.” 8759 Error The plug-in does not implement ARPluginIdentify(). The plug-in name is empty. may not contain space characters. such as “AREA.00 8754 Error 8755 Error 8756 Error 8758 Error Retrieving attachment data is not supported for this form. An associated error message contains details. 206 Error Messages Guide .5. and may not be a reserved name. The plug-in will not load. An error has occurred while loading a plug-in. contains invalid characters. AR System server referenced a plug-in that the plug-in service has not loaded. The specified plug-in does not exist. or is a reserved name.BMC Remedy Action Request System 7. All plug-ins must define the function ARPluginIdentify() and the specified plug-in does not do so. Plug-in names may not be empty. AR System database connectivity plug-in does not support attachments. The plug-in service could not load the specified plug-in.

or the plug-in server is not running. The plug-in encountered an error while trying to initialize and failed to load. check the output at the time the error occurred to verify the state of the plug-in server. check the following things. an attempt to create a vendor form. Some example operations that can generate this error include initial login to the AR System server. Contact your AR System Administrator for assistance. The set property function of the specified plug-in failed in some way.conf or ar. To diagnose the cause of this error. turn on client-side ARAPILOGGING on a client computer where the error appears. confirm that the arplugin process is running. interaction with ITSM consoles. see the Configuration Guide. Turn on Plug-in Server logging and set the Plugin Log Level to All. For each entry with the format Plugin:pathToPlug-inLibrary. In this case. 8761 Error An invalid password has been used for access to the plug-in server. To identify the API call that results in the error. If plug-in logging is turned on.bmc. if possible. see the BMC Remedy Support Knowledge Base at http://www. Contact your AR System Administrator for assistance.AR System error messages 8760 Error Cannot establish a network connection to the AR System plugin server. Verify that each plug-in listed in the ar. For more detailed information about troubleshooting the plug-in server connection.conf or ar. Error 8760 and error 8939 can be caused by a plug-in operation that fails when the AR System server’s connection to the plug-in server fails. The specified plug-in failed to set properties. the password used by AR System server does not match that of the plug-in service. 8762 Error 8763 Error The specified plug-in failed to initialize properly. The plug-in server password was established to restrict access to AR System servers that are similarly configured.com/support_home. Chapter 2 Action Request System error messages 207 . turn on server API and Filter logging. For information about these settings. If the plug-in connection error is related to a BMC Remedy application. or any other operation that is supported by plug-in functionality. check Task Manager to confirm that arplugin. the events that lead to the error: To help isolate the workflow or operation that triggers the error.cfg file appears with a successful start in the log file. verify that the plug-in library exists in the location defined and has permissions and ownership consistent with other AR System server libraries and binaries in the ARSystemInstallDir/bin directory.cfg file. Although the plug-in server can use a port mapper. and that each is successfully loading: View the contents of the ar. This is either due to a configuration problem. to troubleshoot this error. Verify that plug-ins are correctly configured to load when the plug-in server starts.exe is running. consider setting a plug-in port and a Server-Plugin-Alias setting in the configuration file to see if it resolves the problem. make sure that you have applied the latest patches for the application. Determine which plug-in is associated with the error and. On Windows. Confirm that the plug-in server is running: On UNIX.

One of the required values was not provided. Contact your AR System administrator. AR System does not support duplicate user names. The Java plugin server can host native and C plug-ins. such as two users called XYZ who use different passwords or belong to different user groups. Make sure the arpluginjni library and all its dependencies are in the system PATH. If you are unable to resolve the problem. This error from the Java plug-in server is logged to the arjavaplugin. You can ignore this error if you are not using C plug-ins in the Java plug-in server. Error while initializing the JNI type manager for native plugins. 390636 .xml file. 8765 Error 8766 Error 8767 Error 8768 Error 8769 Error 8770 Error 8771 Error 8780 Error Duplicate name detected for plugin. Choose a number in the listed range. User names must be unique. The RPC socket number for plug-in loopback is not one of the legal values (390621 . The Java plugin server can host native and C plug-ins. This is an internal error and indicates that the type manager could not be initialized.5. This error from the Java plug-in server is logged to the arjavaplugin. such as if the file could not be found or dependencies could not be found. For more information.390694). Make sure that the names configured for plug-ins are unique. 208 Error Messages Guide .390634. Make sure that the plug-in server configuration file is in the class path of the Java plugin server.390669.log file. The Java objects are converted to C structures by the ARTypeManager JNI layer.00 8764 Error Error while loading the native plugin hosting library arpluginjni. The appended text indicate the problem. This error indicates that the pluginsvr_config.BMC Remedy Action Request System 7. contact Customer Support. It does this by first loading the arpluginjnia JNIbased library that hosts the C plug-ins. Error encountered while invoking a Native plugin host call. This is an internal error and indicates that a call to a C plugin could not be made even though the plug-in has been loaded successfully.log file. This is an internal error and indicates that although the C plug-in was loaded successfully. Skipping duplicate entry. The Java plugin server can host native and C plug-ins. An invalid value was provided for one of the parameters in the plug-in configuration in the pluginsvr_config. Invalid configuration for a plugin. contact Customer Support. contact Customer Support. Plug-ins are identified by their names. which results in none of the native plug-ins configured being loaded. Make sure the values provided for configuration items in the plug-in server configuration are valid. the Java plug-in wrapper failed to load. If you are unable to resolve the problem. This is error from the Java plug-in server is logged to the arjavaplugin. It does this by first loading the arpluginjnia JNIbased library that hosts the C plug-ins. If you are unable to resolve the problem. Duplicate user. All C plug-ins loaded by the Java plug-in server are internally represented as Java plug-ins.xml plug-in server configuration file could not be loaded. Error while loading Java wrapper for native plugin. The Java plug-ins will function without any problems.log file. It does this by first loading the arpluginjnia JNIbased library that hosts the C plug-ins. The value specified for the plug-in loopback RPC socket number in the configuration file is not in the acceptable range. 390680 . Could not load/Save the plugin server configuration file. see the Integration Guide. This error indicates that the Java plug-in server Java Virtual Machine could not find or load the JNI-based arpluginjni library that hosts the C plugins library.

This error indicates that there was an error during encryption of data to be sent to the server. There was an error while setting up these keys. There was an error while fetching a public key. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder. Unknown host. The most common cause is uncaught exceptions encountered in the plug-ins. like null pointer exceptions. Depending on the encryption policy. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder.AR System error messages 8781 Error Invalid Command line arguments. Try using a different encryption policy or algorithm. Error encountered while encoding string to bytes. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder. all data flowing between the AR System server and the plugin server is encrypted. Specify a free port in the range between 1 and 65000. Error while creating setting up public/private key pair. Invalid or missing values were supplied for the Java plug-in server startup. Try using a different encryption policy or algorithm. Error fetching private key bytes. All string data sent to the AR System server from Java plug-in server is transcoded from the plugin server character set to the AR System server character set. The TCP port number to which the plug-in server will bind must have a valid value. The host name used for the Java plug-in server is invalid. contact Customer Support. The plug-in server sets up the encryption keys for key exchange between client (the AR System server in this case) and the server (plug-in server). unless the policy is chosen to not use encryption. Data decryption error encountered. Data encryption error encountered. 8785 Error 8786 Error 8787 Error 8788 Error 8789 Error 8790 Error Chapter 2 Action Request System error messages 209 . Try using a different encryption policy or algorithm. Error fetching public key bytes. An error was encountered while encoding string to bytes using the AR System server character set. 8782 Error 8783 Error 8784 Error Invalid port number. If you are unable to resolve the problem. There was an error while fetching a private key. Supply a valid value. The plug-in server sets up the encryption keys for key exchange between client (the AR System server in this case) and the server (plug-in server). all data flowing between the AR System server and the plugin server is encrypted. Try using a different encryption policy or algorithm. unless the policy to not use encryption is chosen. Unknown system error. This error indicates that there was an error during decryption of data coming from the AR System server. The plug-in server sets up the encryption keys for key exchange between client (the AR System server in this case) and the server (plug-in server). Try using a different encryption policy or algorithm. Depending on the encryption policy. Make sure the command line arguments are valid. This error most commonly occurs when an exception occurred while processing a call that is not recognized by the plug-in server.

Plugin Termination Error. This is likely caused by a programming error. This error indicates that the plug-in server Java Virtual Machine could not find or load this library. An error was encountered while encoding a string to bytes using the server character set. This error from the Java plug-in server is logged to the arjavaplugin. for example. for example. You can ignore this error if you are not using C plug-ins in the Java plug-in server.BMC Remedy Action Request System 7. Contact your AR System administrator for assistance. which results in none of the configured native plug-ins being loaded. the terminate method is called on all the plug-ins. in an incorrect API program. Make sure the arpluginjni library and all its dependencies are in the system PATH. You might also see this if an Open Window active link action tries to open a form from a different server and a different application name. for example. Delete instance is called on each plug-in on a thread shutdown so plug-ins can cleanup any thread safe data that was saved in the plug-in server thread’s context. in an incorrect API program. The Java plugin server can host native and C plug-ins. contact Support. The description of the specified reference is empty. All string data sent to the AR System server from Java plug-in server is transcoded from the plugin server character set to the AR System server character set. This error indicates there was an error during one of the terminate calls. The value of the specified reference is empty. for example. This error indicates that there was an exception while creating an instance. such as if the file could not be found or dependencies could not be found. Error encountered while encoding bytes to string string. in an incorrect API program. You do not have permission to access this container. It does this by first loading the arpluginjnia JNIbased library that hosts the C plug-ins. Check the log file for details about the error. The specified container does not exist. The Java plug-ins still function without problems. This is likely caused by a programming error. in an incorrect API program. The specified container owner name is incorrect. 8793 Error 8794 Error 8795 Error 8796 Error 8797 Error 8800 Error 8801 Error 8802 Error 8803 Error 8804 Error 8805 Error 210 Error Messages Guide .00 8792 Error Exception occurred while loading the native plugin host library.5. for example. This is likely caused by a programming error. check the log files for information about the reason for the failure. This is likely caused by a programming error. You do not have access to the specified container. This error indicates that there was an exception while deleting an instance. AR Plugin Server Startup Error. When a thread goes down in the plug-in server. Plugin Create Instance Error. Create instance is called on each plug-in on a new thread startup so plug-ins can create an instance of any thread safe data and save it in the plug-in server threads context. To resolve the issues. The appended text indicates the problem. A fatal error was encountered during plug-in server startup. This is likely caused by a programming error. in an incorrect API program.log file. Check the log file for details about the error. If you are unable to resolve the problem. Check the log files for details about the error. Plugin Delete Instance Error. The label of the specified reference is empty.

if necessary. Locking level cannot be decreased. if necessary. This is likely caused by old server containers. No owner name was specified. One of more objects being exported cannot be locked. for example. Contact Customer Support for assistance. for example. Unknown object lock level specified. Typically. The value of the external reference has an invalid format. Illegal container type. Chapter 2 Action Request System error messages 211 .AR System error messages 8806 Error 8809 Error The specified container is missing. No name was specified for the owning object. Load this parameter with the name of the form you want to reference. Contact Customer Support for assistance. Enter a different name for the container. for example. This is likely caused by a programming error. Object locking is not supported for DSO or flashboards objects. in an incorrect API program. Container cannot be owned by this type of object. but the value passed is either NULL or an empty string. in an incorrect API program. Object cannot be locked. this occurs when a definition file you try to import contains an error. Supported container types include: ARCON_GUIDE ARCON_FILTER_GUIDE ARCON_APP ARCON_PACK ARCON_WEBSERVICE Supported container owners are: ARCONOWNER_NONE (container is globally owned) ARCONOWNER_SCHEMA 8810 Error 8811 Error 8812 Error 8816 Error 8817 Error 8818 Error 8819 Error 8830 Note 8831 Warning 8832 Error The specified container already exists. Application owner mismatch for schema. The container is not supported by the server. You tried to define a container owner object that is not a supported container type. Specify one of the following lock levels: AR_LOCK_TYPE_NONE (0) AR_LOCK_TYPE_READONLY (1) AR_LOCK_TYPE_HIDDEN (2) This error can be encountered only through an API program. in an incorrect API program in which the reference list is invalid. A locked object can be exported only at the same lock level or a higher lock level. This is likely caused by a programming error. This is likely caused by a programming error. Illegal reference type. A parameter is required.

Safeguard mismatch . Attempt to modify a locked object failed -.5. 8840 Warning 8841 Error 8842 Error 8843 Error 8844 Error 8845 Error 8846 Error 8847 Error 8848 Error 212 Error Messages Guide . You cannot delete fields on a locked form. You must delete the group of objects that have the locked key. Cannot delete a locked object -.potentially corrupted active link. Use the AR_LOCK_BLOCK_DELETE option to delete all objects in the lock group. Lock information mismatch.inappropriate changes are discarded. A system error occurred. The object is possibly corrupted. The form might have been modified at the database level. Contact Customer Support. A system error occurred. The object is possibly corrupted. End of file reached. The escalation might have been modified at the database level. an application. A system error occurred. The definition file is possibly corrupted.potentially corrupted menu. This error is encountered only through an API program. Locking properties of the object do not match the locking properties of the lock group. No information is returned for the hidden locked object. such as a guide. Safeguard mismatch . The object is possibly corrupted. Contact Customer Support. The filter might have been modified at the database level. You tried to modify an object that has a read-only lock. The menu might have been modified at the database level. so the existing key will be kept. Contact Customer Support. Changing the lock key is not allowed. might have been modified at the database level. The active link might have been modified at the database level. The object is possibly corrupted.must override to delete.00 8833 Warning 8834 Error 8835 Error 8836 Error 8837 Note 8838 Warning 8839 Error Lock key cannot be changed. Unable to load object lock information into cache.potentially corrupted escalation. Safeguard mismatch . An unexpected end of file occurred during file processing.BMC Remedy Action Request System 7. You cannot create fields on a locked form. Field deletion not allowed on a locked form. Safeguard mismatch . Contact Customer Support. The object is possibly corrupted.potentially corrupted filter. The object is possibly corrupted.potentially corrupted form. Safeguard mismatch . Specified lock block cannot be found. Contact Customer Support. A system error occurred. A locked object can only be exported with the same lock key. such as by adding a form to a read-only filter. Safeguard mismatch . The container.potentially corrupted container. Contact Customer Support. Restart the AR System server. Field creation not allowed on a locked form. Contact Customer Support. You cannot delete just this single locked object. You cannot modify a locked object. or a packing list. A system error occurred. A system error occurred. Information is not returned for hidden locked objects. A noncritical error occurred in the server cache. Contact Customer Support. A system error occurred.

This warning indicates that the operation is successful but that the child entries are not considered. The object is possibly corrupted. A dialog has no data to query. GetListFields not allowed with this type of form.xml or . GetListFields ignored for this type of form. You cannot delete fields referenced in table field qualifications. Review your program and make sure the correct ARControlStruct parameter is passed. the XML Service Entry will process only the first entry. A dialog has no data to query. remove the field name from the qualification. Contact Customer Support. Sort list ignored for this type of form.potentially corrupted image. This type of form can only have display-only fields. To delete the field. A dialog has no data to query. A dialog has no data to query. In a single export call. During set or create operations locked object properties are not expected. Check server settings and make any necessary corrections. This operation cannot be performed on a dialog form. This operation cannot be performed on a dialog form. This operation cannot be performed on a dialog form. Escalations cannot access fields in this type of form. You must export the object as locked. Windows logon fails due to unknown user or invalid password.def. Server setting out of range. A dialog has no data to query. This operation cannot be performed on a dialog form. This error occurs when you use the API to send initialized locale information in ARControlStruct. The field is referenced in the qualifier of a table field. Invalid Locale Info Supplied. all objects must be exported in the same format. Make sure that the user name and the password exist and are correct. The image might have been modified at the database level. which can be . Setting BSM tag disallowed. An attempt was made to create a join form and one of the forms in the join was a dialog form. This operation cannot be performed on a dialog form. An XML Service Entry does not support processing of multiple entries. You tried to delete a field referenced in a table field qualification. If the input XML document holds multiple entries when executing an OpService web service operation. This operation cannot be performed on a dialog form. A system error occurred. You cannot create joins with dialogs. This action is for internal use only. A dialog has no data to query. Safeguard mismatch . A lock block must be exported entirely in xml or entirely in def format.AR System error messages 8849 Warning 8850 Error 8851 Warning 8852 Error 8853 Error 8854 Warning Setting object lock information is disallowed at this time. 8855 Error 8900 Error 8901 Warning 8902 Error 8903 Warning 8905 Error 8907 Error 8908 Error 8909 Error 8910 Error Chapter 2 Action Request System error messages 213 . Either the user name or the password is invalid or does not exist on Windows Logon Server. Child entries are not processed. Dialog forms not allowed in join forms. Child entries will not be considered. Sort list not allowed with this type of form.

Failure during attempt to update next available VUI ID. The workflow must be associated with a list of forms that exist on the server.00 8911 Warning Some of the fields have been truncated from the results list because the total length of the fields and separators is greater than the maximum allowed. The appended text is a message from the external authentication server. or reduce the separators between columns to reduce the total to less than AR_MAX_SDESC_SIZE. run arsystem stop. and then run arsystem start. free up space in the log directory by deleting old or unwanted files. The form was not found in the cache. You did not specify the forms for the workflow you are creating. The form list contains no forms. Authentication Note: note.5. The authentication service is not responding. To continue. The appended text is a message from the external authentication server. The legal value for the RPC socket number for the External Authentication process is 390695. Remove fields from the list. Make sure that your computer is correctly configured for shared memory and semaphores. or escalation. Unable to write logging to requested file. You must specify the forms to which the workflow is attached. Must specify a workflow connection structure to create an active link. Authentication Error: error. Error accessing semaphore. Specify 390695 only. This API call is not possible with older servers. If it is. 8914 Note 8915 Warning 8918 Error 8920 Error 8921 Error 8922 Error 8923 Error 8924 Error 8925 Error 8926 Note 8927 Error 8930 Error 214 Error Messages Guide . Two or more forms in a form list have duplicate form names. 8912 Error 8913 Error The ARGetListEntryWithFields call is not supported by the server. filter. The user tried to set the value of the external authentication RPC socket to a value other than 390695. The workflow must be associated with a single form or a list of forms that exist on the server. A server could not get or lock a semaphore. specify shorter field widths. Form name specified multiple times in workflow connection structure form list. Workflow logging active. This logging error typically is returned when you run out of disk space. The maximum allowed length of AR_MAX_SDESC_SIZE is 128 bytes. Unrecognized or misused tag for workflow connection structure. No form list exists for the workflow connection. The request log type matches the current log. Workflow connection structure type of form list specified. Active link workflow tried to perform an ARGetListEntryWithFields call with a pre-4. You were unable to update the next field ID column in the database for a new VUI in a form.BMC Remedy Action Request System 7. Contact your AR System administrator for assistance. but no form list was supplied. The external authentication server is not responding to calls from the AR System server. An invalid form was found in the form list. Cannot connect to the system at this time.0 AR System server.

XML Parsing error. for example. Your attempt to import views into the form failed. XML Parsing error. 8937 Error 8938 Error 8939 Error 8940 Error 8941 Error 8942 Error 8943 Error 8944 Error Error during XML definition parsing. and reimport the item. Fix the problem. To continue.AR System error messages 8931 Error 8932 Error 8933 Warning 8934 Error 8935 Error Error in semaphore name. This parsing error occurred while the character data was parsed. and therefore the event semaphore could not be opened to enable signals from server. The parser found an invalid attribute tag while parsing the XML document. The parser found an invalid element tag while parsing the XML document. The parser found an invalid enumeration value while parsing the XML document. Error during Xerces-c Initialization. Contact your AR System Administrator for assistance. The XML file. Client operation was disabled. The Xerces library globals used in the XML parser failed to initialize. For more information about troubleshooting plug-in server connectivity. This error also is returned if the size of the input buffer exceeds 57 bytes. Invalid element tag. Make sure that the plug-in server and AR System plug-ins are running. An error occurred when an XML document was parsed. it is greater than 255 characters). Cannot connect to the system at this time. XML Parsing error. see the entry for error 8760. No views were imported. Invalid enumeration value. Invalid attribute tag. and XML object name cannot be parsed. Upgrade of the server internal forms failed. A client-type operation was disabled for the current user. Compression failed when adding the attachment file to a request during the Perform-ActionAdd-Attachment command used in a Run Process filter action. XML string. The proxy fork process could not write information to its log file. An RPC time-out occurred when connecting to the plug-in server. An associated message indicates why the view was not imported. A user is modifying the contents of a field but does not have write access. Unable to communicate with arfork daemon. if a user belongs to an excluded group. increase the size of the buffer used in the attachment field. The AR System Plug-In server is not responding. Only the following forms are valid here: Distributed Mapping Distributed Pending Distributed Pool Application Pending 8936 Error Compression of file failed. Only a valid internal form definition can be upgraded. Chapter 2 Action Request System error messages 215 . You do not have write license. XML Parsing error. An error exists in the FTS handle (for example.

The requested dateparts is not supported by this operation.BMC Remedy Action Request System 7. The date format is invalid. 8955 Error 8956 Error 8957 Error 8958 Error 8959 Error 216 Error Messages Guide . Year 2002 (there are not 22 months in a year). The requested dateparts is not supported by this operation. The value for the session configuration option is not a valid value You were unable to set a valid public API session variable. XML import and export is not supported for this object in the file. The server failed to load the AR System XML shared library. The Status History field of a Data Dictionary style character menu cannot be expanded as a query style enumerated value. Duplicate values exist in a custom style enumerated data type. This parsing error is returned because no such XML object exists in the object list. The server could not parse the XML document because you specified an invalid XML document type. An invalid XML document type was specified. or this operation does not support the dateparts value. The values must be unique for each choice. Unable to load the arxmlutil library. While trying to append the string contents to the end of the file. The date value is invalid. Make sure all choices are unique. The XML data type being converted is not supported by AR System or the XML data type is invalid. The specified date string is invalid. The process stops and an error message is returned. There is an invalid value for an enumerated data type. Duplicate numeric values specified for a custom style enumerated value. To continue.00 8945 Error 8946 Error 8947 Error 8948 Error 8949 Error 8950 Error 8951 Error 8952 Error 8953 Error 8954 Error No such object in the parsed XML stream. You were unable to create a license because the license key does not match the generated key based on the license information provided. the operation failed because the file could not be opened. Please provide a valid license key. which would be converted to Month 22. Invalid license key. This error can be encountered only through an API program. Either the dateparts value is invalid. XML import and export is not supported. A failure occurred while trying to open the file. The Status field cannot be a query style enumerated value. The name of the library is arxmlutil. The XML data type is not supported. you see this error message if the string contains an invalid date value. verify that the file exists and that you have permissions to access it. The value of the enumerated value style is not a valid value.5. Day 15. an invalid date format would be 22/15/02. When converting a ISO or US date string to Julian calendar format. For example. An EXTERNAL qualification making a reference to itself is an illegal operation. EXTERNAL qualification contains a circular reference.

The system found two forms containing the reserved centralized administrator preference field. Required XML element is missing from the XML mapping. Verify that the XML input document is correct for the XML mapping document. Chapter 2 Action Request System error messages 217 . The format of the XML mapping document is incorrect and must be corrected. Notify replyto is over the maximum size allowed for the name.AR System error messages 8960 Error 8961 Error 8962 Error 8963 Error 8964 Error 8965 Error 8966 Error 8967 Error 8969 Error 8970 Error 8971 Error 8972 Error Server information data is in an incorrect format.delete one to continue. Notify cc is over the maximum size allowed for the name. Required attribute expected in the input XML document. You must delete one form. The format of the XML mapping document is incorrect and must be corrected. The key for this entry must be unique in the XML input document. The default notification mailbox is not specified. Server information data is not correctly formatted. Two forms contain the reserved centralized user preference field -. This error can occur with commands that take as parameters multiple strings separated by semicolons. Verify that the XML input document is correct for the XML mapping document. Required XML attribute is missing from the XML mapping.delete one to continue. Enter CC information of 255 bytes or less for the email notification message. The number of entries in the list must be equal to or less than the maxOccurs value. The number of entries is less than XML element's minOccurs value. The distinguishing key is not unique. A required attribute is missing from the XML input document. Two forms contain the reserved centralized administrator preference field -. The system found two forms containing the reserved centralized file preference field. No default mailbox was configured so no default mailbox is available for the email notification. The system found two forms containing the reserved centralized user preference field. Enter “reply to” information of 255 bytes or less for the email notification message. Notify bcc name is over the maximum size allowed for the name. An unexpected element is in the input document. You must delete one form. 8973 Error 8974 Error 8975 Error 8976 Error 8977 Error Two forms contain the reserved centralized file preference field -. Unexpected element encountered in the input XML document. The number of entries in the list must be equal to or greater than the minOccurs value. You must delete one form. Required element expected in the input XML document. The number of entries exceeds the XML element's maxOccurs value. Enter “from information” of 255 bytes or less for the email notification message. Verify that the XML input document is correct for the XML mapping document.delete one to continue. A required element is missing from the XML input document. Enter BCC information of 255 bytes or less for the email notification message. Notify from is over the maximum size allowed for the name.

An object not in a deployable application cannot have role permissions. Cannot modify Limit Info or Permission for a data field in an Archive or Audit form. To delete a field. Make sure the file specified in the error message is present and accessible. It will be set to empty string. Setting application owner is disallowed. This warning is returned when the LimitInfo or Permission property for a field that takes data (field types 1 to 14 and 35 to 37) in an archive or audit form is modified. Changing the data type of the field is not allowed. An attempt was made to delete data fields (field types 1 to 14 and 35 to 37) from an archive or audit form. 8981 Warning 8982 Error 8983 Error 8984 Warning 8985 Warning 8986 Warning 8987 Error 8988 Error 8989 Error Archive or Audit information could not be set for this form. Enter organization information of 255 bytes or less for the email notification message. 8990 Warning 218 Error Messages Guide . The application owner object property cannot be set. Contact your AR System administrator. The system sets these properties to NULL before setting them. This message is accompanied by more specific messages. You must remove this object from the application that owns it before you can add it to this application. Object is already owned by another application. The option value that was specified is invalid. Notify mailboxname name is over the maximum size allowed for the name.00 8978 Error 8979 Error 8980 Error Notify organization name is over the maximum size allowed for the name. Please see manual for valid values for this option. Group permissions have been removed from the object because the object is in a deployable application. The web alias names for views must be unique in all views for the form. These values will be made NULL before setting. Unrecognized option value for change field action. The server failed to open a system form definition file that should be present in a standard location. You cannot perform an import in place operation if the data type of a source field is different from the data type of a destination field with the same field ID.5. Cannot delete data fields from Archive or Audit form. Roles permissions have been removed from the object because the object is not in a deployable application. A deployable application cannot have group permissions. A failure occurred while trying to open a system form definition file: fileName. Enter mailbox name information of 255 bytes or less for the email notification message. The server needs to add the system form by importing the definition from the file. and views must be unique. It must be specified as 1 to indicate a field or to 0 to indicate a value.BMC Remedy Action Request System 7. This object has an application owner and cannot be added to this application. The alias for this object is not unique. clear the Enable option in the source form to disable archiving or auditing for the form first. The web alias names for applications. Set these values to NULL to avoid seeing the warning message. Examine the associated messages to diagnose the problem. forms.

Both the Source form and the Archive or Audit form must belong to the same Application. If you are using the MergeEntry API call. cannot be created in an archive or audit form. then a field with that ID exists in the Archive/Audit form and archive or audit will be disabled. such as fields with data types 1 to 14 and 35 to 37. should also be empty.AR System error messages 8991 Error Cannot create this field in Archive or Audit Form. The create or set operation on the source form completes. Please check the manual for requirements for a valid Archive or Audit form. This error is returned if another field with the same field ID but a different data type exists in the archive or form. Forms with a Dialog or Archive form type cannot be archived. enable. Either create the field with the same ID and data type in the source form. Fix the archive/audit form. including form name. The RPC call failed. or specify the name of an existing form. either disable archive/audit on the source form or. filters (Push field or Set field) cannot modify or create entries in an archive or audit form. The source form and a corresponding archive/audit form must be removed from an application together. and query. 8998 Error 8999 Error 9000 Error Encryption is disallowed by the AR System server. Also. but existing entries cannot be overwritten or modified. Cannot modify or create entries in an Archive or Audit form. time. You cannot add or remove only the source form or only the associated archive/audit form from an application. Archive not possible on Dialog or Archive forms. You cannot create or modify existing entries in an archive or audit form. all other fields. AR System tries to create the same field in the corresponding archive or audit form. If this is an Archive/Audit form then fields of this type cannot be created. If this is a main form. The Archive or Audit form is invalid. form name should be present. if you are using the ARDeleteSchema API call. 8992 Warning Could not create the Archive or Audit Form specified. Archive/Audit for this form has been disabled. When a field is created in the source form. For Vendor forms. but archive/audit is disabled. An existing form that is not a valid archive/audit form is specified as an archive/audit form. 8993 Error 8994 Error If any of the Copy options are chosen. Enter a form name in the Archive To Form field. Specify the correct archive type with the right parameters in the API call. see the Configuration Guide and the Form and Application Objects Guide. and AR System server does not support encryption. Archive or Audit form should be of proper type. Data fields. If an archive or audit form is being deleted and its source form has archive/audit enabled. Only the Copy to Archive archive type is available for Vendor type forms. Archive Type does not match the remaining archive information passed in. The Archive Type selected is Copy To Archive And Delete From Source or Delete From Source. only 'Copy to Archive' option is available. Chapter 2 Action Request System error messages 219 . or added to an application together. proper permissions as the source form. An archive or audit form cannot be created for a source form because of a lack of memory or a database error. use the AR_SCHEMA_SHADOW_DELETE option. but the archive form name was not specified. For more information about archive and audit forms. If archiveType is not one of the valid archive types or archiveType is AR_ARCHIVE_NONE. or clear the Enable option for archive or audit on the source form. and AR System automatically creates a valid archive/audit form. entries can be added to the form. 8995 Error 8996 Error 8997 Error Turn off the archive or audit to this form in order to delete this form.

No encryption licensing is invalid on the AR System server. Data encryption key exchanged failed. There was a failure in generating the random number used during the encryption routine. The actual size of the string exceeds the size limit specified for the string. An internal error occurred because the string has a NULL value. To encrypt/decrypt a null string is not allowed. but the required encryption shared library DLL could not be found or loaded. Error Messages Guide 9002 Error 9003 Error 9004 Error 9005 Error 9006 Error 9007 Error 9008 Error 9009 Error 9010 Error 9011 Error 9012 Error 9013 Error 9014 Error 9015 Error 9016 Error 9017 Error 220 . Unrecognized encryption algorithm. The MAC (message authentication code) failed during the decryption routine. Encryption is turned on. An unknown encryption algorithm was used. when comparing the MAC in the decrypted message against the locally generated MAC. The AR System server does not disallow encryption. XDR sizeof error during XDR encoding. The encryption shared library DLL could not be successfully loaded. The encryption license does not match the encryption library. This error indicates the encryption library failed to enter FIPS mode. XDR xres error during XDR encoding. FIPS encryption failed. The encrypted string could not be decrypted because the cyclic redundancy check (CRC) failed. An invalid CRC indicates that the encrypted string is corrupted.5. Error during public key data decryption. Loading of encryption library failed. The XDR (external data representation) process could not present the result pointer into the memory buffer. This error can occur when the string becomes corrupted. An error occurred in the encryption library. To comply with FIPS 140-2 standards. but the encryption shared library is not loaded. Encryption is not licensed on the AR System server. The actual key exchange between the client and the server failed due to a serious error by one or both of the RPC calls. The encrypted string is greater than the maximum length allowed. The size of the memory buffer used in XDR (external data representation) is invalid. Public key decryption failed due to no authentication between client and server. An error occurred with the decryption because the CRC is invalid. Either install the encryption library or disable client/server encryption. Encryption is required. The encryption library was not found and cannot be loaded.BMC Remedy Action Request System 7.00 9001 Error Encryption is required by the AR System server. the encryption library must enter FIPS mode. Client/server encryption is enabled but the encryption library was not found. Error during symmetric key data decryption. The key exchange protocol requires shared encryption keys between the client and the server and checks the encryption policy of the server. The client default is to make encrypted calls to the server. No encryption licensing is present on the AR System server.

The Localize Server check box is selected on the Advanced tab of the Server Information dialog box. Cannot connect to server. A field on the Message Catalog form might have been deleted. Corrupt data might have been added.1 encryption modes Servers using no encryption Servers whose encryption is disabled Servers on which encryption is allowed (Encrypt-Security-Policy set to 0) but not required (Encrypt-Security-Policy set to 1) 9019 Error Client cannot connect to this FIPS-noncompliant server because the client is connected to a server that enforces FIPS. set Encrypt-Security-Policy to 1 (encryption required). 9050 Error Chapter 2 Action Request System error messages 221 . Cannot connect to server. but an AR System Message Catalog form cannot be found on the server. . In this case. To continue.csv or .” Cannot connect to server. Servers that enforce FIPS compliance have one of these encryption configurations: Encrypt-Data-Encryption-Algorithm set to 8 (Performance Security) and Encrypt-Security-Policy set to 1 Encrypt-Data-Encryption-Algorithm set to 9 (Premium Security) and Encrypt-Security-Policy set to 1 Servers that do not enforce FIPS compliance include the following: Servers on which Encrypt-Data-Encryption-Algorithm is set to 6 or 7 Servers using AR System 7.1 encryption modes Servers using no encryption Servers whose encryption is disabled Servers on which encryption is allowed (Encrypt-Security-Policy set to 0) but not required (Encrypt-Security-Policy set to 1) 9020 Error FIPS mode requires the security policy to be “encryption required. you might need to delete the form and start over. This error can occur for several reasons: The form might have been deleted. Localization has been turned on but no Message Catalog exists. see the AR System server arerror.arx. make sure the form exists.AR System error messages 9018 Error Client cannot connect to this FIPS-compliant server because the client is connected to a server that does not enforce FIPS. If it does not exist.xml data file format so that you can reimport it after the form is re-created at system startup. For more information. the AR System server or the Java plug-in server did not start. If the form itself is corrupted. To fix this error. Servers that enforce FIPS compliance have one of these encryption configurations: Encrypt-Data-Encryption-Algorithm set to 8 (Performance Security) and Encrypt-Security-Policy set to 1 Encrypt-Data-Encryption-Algorithm set to 9 (Premium Security) and Encrypt-Security-Policy set to 1 Servers that do not enforce FIPS compliance include the following: Servers on which Encrypt-Data-Encryption-Algorithm is set to 6 or 7 Servers using AR System 7. The form is automatically re-created at system startup.log file. export any data into an . Therefore. The AR System server Encrypt-Data-Encryption-Algorithm option is set to 8 (FIPScompliant performance security) or 9 (FIPS-compliant premium security) but the Encrypt-Security-Policy option is set to 0 (encryption allowed but not required). stop and start the server.log file or the Java plug-in server arplugin.

not even defaults. For localization purposes. Two or more AR System Message Catalog forms were found on the same server. A system error prevented the Unicode converter from being opened. the previously existing default admin view is used.00 9051 Error Multiple Message Catalogs exist. VUIs for a form must be unique. The Localize Server check box was cleared in the Advanced tab of the Server Information dialog box. No VUI definition from the file was retrieved during the import operation. The default admin view of the form was not found during the import operation. and platform properties of this VUI must be unique to the form. locale. The format of the import file was corrupted so that it contains no VUI information. To continue. The timestamp of the localized active link or menu could not be updated. you can have only one Message Catalog form on a server. and platform. The join form contains a circular reference. Error encountered during string conversion from Unicode. that its contents is not corrupted. The VUI is not unique for the form. There must only be one Message Catalog. Unable to create the Unicode Converter.5. A query cannot retrieve more than one localized value of a message at a time. The server is not localized. Instead. The display instance of a field in the VUI did not correspond to the display instance of the field in the cache during the import operation. Character data could not be converted to Unicode format. 222 Error Messages Guide . To continue. and the import process continues. To continue. The label. Character data could not be converted from Unicode format. Update of Localized Active Link or Menu failed. The default VUI was redefined to a pre-existing VUI from the form. The VUI import file is in an incorrect format. This error is returned when a request is made to return multiple localized texts from the Message Catalog Form but the server is not actually localized. Delete one of the Message Catalog Forms and restart the server. Error encountered during string conversion to Unicode. 9052 Error 9053 Warning The default VUI specified in the schema import file was not found. Fix the join form definition. The field is not imported. create a unique VUI combination of label. Possible reasons include: Message Catalog Form was not found on the server.BMC Remedy Action Request System 7. No messages were found in the Message Catalog Form. make sure the Message Catalog Form exists. locale. 9055 Error 9056 Error 9057 Error 9058 Error 9059 Error 9060 Error 9061 Error 9062 Error Recursion of localized queries are not allowed. 9054 Warning The specified field does not exist in the form. and that the Localize Server check box is selected in the Advanced tab of the Server Information dialog box.

To automatically re-created the form. If an attempt is made to create a form that contains these fields while the Server Events form exists. The server provides limited Unicode support for BMC Remedy Administrator and BMC Remedy Alert. 9075 Error Problem encountered during creation of one of the server system forms. Use BMC Remedy Developer Studio instead of BMC Remedy Administrator. This message indicates that AR System failed to create the missing forms. AR System server does not support non-Unicode clients such as BMC Remedy User. and version 6. 9076 Error 9077 Error 9078 Error 9079 Error 9080 Error 9081 Error 9082 Error 9083 Error Chapter 2 Action Request System error messages 223 . If an attempt is made to create a form that contains these fields while the Application Statistics Configuration form exists. If an attempt is made to create a form that contains these fields while the Application Statistics form exists. The form might have been deleted. the AR System server could not find the Server Statistics form to record an entry. Cannot find the Server Events form. AR System prevents creation of the new form. While server statistics recording was enabled. The AR System server could not find the Application Statistics Configuration form. Cannot find the Server Statistics form. On AR System server startup. The Server Statistics form is defined from a unique combination of AR System reserved fields. these forms are automatically re-created. however. While server event recording was enabled. Only one form can contain the Server Events fields. Only one form can contain the Application Statistics fields. and the message no longer appears. The Application Statistics form is defined from a unique combination of AR System reserved fields. Only one form can contain the Server Statistics fields. restart the AR System server. use a browser instead of BMC Remedy User. To contact this server. Only one form can contain the Application Statistics Configuration fields. the server prevents creation of the new form. the server could not find the Server Events form to record an entry. The form might have been deleted or there might have been a system failure. AR System prevents creation of the new form. the runmacro program. delete the Server Events and Server Statistics forms. AR System prevents creation of the new form. BMC Remedy Data Import (GUI Version). The form might have been deleted or there might have been a system failure. To automatically re-created the form. restart the AR System server. if one of the AR System server’s system forms does not exist. The next time you restart AR System. AR System still starts. the AR System server could not find the Application Statistics form to record an entry. To automatically re-created the form. Cannot find the Application Statistics Configuration form. To eliminate the message. The Server Events form is defined from a unique combination of AR System reserved fields. While application statistics recording was enabled. AR System creates it.AR System error messages 9063 Error Server allows only Unicode clients (except Administrator and Alert tools). restart the AR System server.3 of the Mid Tier. If an attempt is made to create a form that contains these fields while the Server Statistics form exists. or there might have been a system failure. The Application Statistics Configuration form is defined from a unique combination of AR System reserved fields. Cannot find the Application Statistics form. You might also see this message when starting the AR System server if you replace the AR System executable or do not overwrite the database when installing AR System.

A user cannot log in to AR System from two computers at the same time. The import file does not hold an application definition. User information is being updated and information for the user is damaged or corrupted. The file specified for an application does not hold an application definition. Cannot change license type of a user to Fixed more than 3 times in 1 week. User information in an internal database table is damaged or corrupted. License deleted.BMC Remedy Action Request System 7. The command does not occur on the local server. Value specified for the Authentication Chaining Mode is outside the valid range of 0 . The AR System server can contain only one form containing the license fields. Subadministrator group permissions have been removed from the object because the object is in a deployable application.5. see the Configuration Guide. contact Customer Support. User data is corrupted. AR System runs in evaluation mode. Obtain additional fixed licenses if necessary.00 9084 Error 9085 Error 9088 Error 9089 Error 9090 Error 9091 Error 9093 Error 9094 Warning 9095 Warning 9096 Error 9097 Error User is currently connected from another machine. A user cannot log in to AR System from two computers at the same time. Contact Customer Support. An object not in a deployable application cannot have subadministrator role permissions. Note that the license form field IDs are in the restricted range. Cannot find the Server License form. The AR System server is unable to locate a form containing the server licenses. you might need to re-enter the server licenses. Subadministrator roles permissions have been removed from the object because the object is not in a deployable application. User is currently connected from another machine. which might have been accidentally removed.4. This error occurs when the authentication chaining mode parameter is set outside the valid range in the AR System configuration file. User data is corrupted. Contact Customer Support. Only one form can contain the Server License fields formName. Host IP address not found. The AR System server did not find the client IP address in the API call. A deployable application cannot have subadministrator group permissions. Contact Customer Support. so try restarting the server. This error can be caused by creating a copy of the license form. If the problem is not fixed. An attempt was made to change the license type of a user to fixed more than three times within one week. You can terminate the connection to AR System from the other computer. The user license was deleted by the system. For more information. The Server License form is automatically created when AR System is started. A nonlocal server execution error occurred during the following operations: Executing a run process command on the server Retrieving a list of SQL values specified in the SQL command 9098 Error 9100 Error 224 Error Messages Guide . If restarting fixes the problem. If the problem still occurs.

An associated error message provides details. Search. Your session is no longer available because either the session is invalid. save. There was an error returning the fully substituted command from the database. opening a form) to which you have no permissions. but the incoming value does not match it. During import and export operations. To continue. Default value of element should match the input value. (UNIX only) User has no access permission to objectName. No help available. you can run another instance of armonitor from a different installation directory. You tried to attach an object to an attachment pool in which no fields are available (all fields might be in use). an invalid server-side run process command. the processes are exported as clientside processes. Make sure that the host ID you entered is the one you supplied when you requested the license. the direct SQL and run process commands are valid only as server-side processes. Remove any unnecessary attachments if you have permissions. Error while opening the armonitor lock file. Check with your administrator. You cannot run multiple instances of armonitor from the same installation directory. There was an error in one of the form actions. You tried a display. XML Output mapping cannot be NULL. Session is invalid or has timed out. In web services. not as client-side. Server does not have a valid host id. There are no available attachment fields. or Delete Entry. or ask your AR System administrator to add more attachment fields to the attachment pool. You tried to perform an operation (for example. Please correct this error to enable licensing for this server. Please select an attachment file first. A failure occurred while retrieving the list of fields that contain Help text. The form action request failed. Error in parsing the Run Process or Direct SQL command. This error message is generated by the Web Service plug-in whenever an error occurs during the execution of a Web Service. or delete operation but did not first select an attachment. Log in again to continue. The host ID you entered does not match the host ID in your license. Please reload page to log in again. or no session data was retrieved. Modify. Submit. verify if the SQL command or run process command works from a command line. Error encountered while executing a Web Service. for example. 9102 Error 9110 Error 9130 Error 9131 Error 9132 Error 9150 Error 9200 Error 9201 Error 9202 Error 9203 Error 9204 Error 9205 Error 9206 Error Chapter 2 Action Request System error messages 225 .AR System error messages 9101 Error The command is not a server-side command. In certain cases. However. a field in the output mapping is set to a default value. the session timed-out. for example. Cannot get the fields in the form. A failure occurred while the system tried to retrieve Help text for this form or field.

not POST. for example. There was a failure in viewing or saving an attachment file. Make sure that the file exists. The operation of saving the attachment file to disk failed. including the following conditions: Name of a system object or field ID is NULL when the system tries to retrieve a system object Internal cache error Web tier exception XSL stylesheet not found for certain type of object Failure to create request in Push Field workflow action at runtime Failure to set a field in the Set Field workflow action at runtime Failure to expand an open window 9210 Error 9211 Error 9212 Error 9213 Error 9214 Error 9215 Error 9216 Error Display or save attachment failed. A failure occurred in retrieving a property from the configuration properties file. Failed to get config property. No field in the attachment pool is large enough to contain this particular file. enter or select a file. it could not be sent. contact your AR System administrator. or you did not enter a file path name. There was a failure in viewing or saving an attachment file because the file could not be found on the web server. This is an unexpected error. a new window could not be opened to display the file. even though the system located the file. Problem sending file.5. or try zipping the file to make it smaller. Internal error. This error occurred here because the request parameters for the file were invalid. The size of the attachment is too large. Check your permissions. There was a failure in loading the attachment file because the method attribute of the form tag in the servlet request was set to GET. You can also try to attach to a different attachment field. 9217 Error 9218 Error 226 Error Messages Guide . If that does not solve your problem. There was a problem viewing the file because. an invalid qualification statement. The file does not exist or is empty. either because the file does not exist or its value is NULL. Servlet does not support the doGet() method. You tried to attach a file to an attachment field but did not enter a file name. Invalid request parameters. You tried to attach a file larger than the maximum size allowed for this attachment field. Contact your administrator to enlarge the size of the attachment field so that you can attach it later. This all-purpose error occurs during numerous internal system failures. Cannot find an empty attachment field large enough to hold this attachment. because the file path was NULL. Contact your administrator. You have to specify a file to upload. for example. Failed to add attachment.00 9207 Error 9208 Error 9209 Error Illegal request parameter.BMC Remedy Action Request System 7. You entered a set of incorrect parameters for this operation. The operation of adding an attachment file failed. Either the file requested is not present or the URL supplied is bad. Maximum size of available slot is number K bytes. or try zipping the file to make it smaller. Contact your administrator to enlarge the size of the attachment field so that you can attach it later. To complete this process. File not found.

9227 Error Query conversion failure unknown: queryName. Cannot convert AR System query into a Crystal query: invalid data type for enum value. The conversion failed because an invalid enum string value appeared in the AR System query. rewrite the AR System query into a format more easily understood by the Crystal Report engine. 9229 Error 9230 Error Report filespec location not specified for native reports. A failure occurred during conversion because the field value is NULL and the field name is incorrect. Because the AR System query did not use this format. Cannot convert AR System query into a Crystal query: no fieldname to match with NULL value. Please see your administrator. 9225 Error 9226 Error Cannot convert AR System query into a Crystal query: bad enum field type. rewrite the AR System query into a format more easily understood by the Crystal Report engine. 9228 Error Unsupported syntax in query conversion. An illegal field name not allowed by Crystal Reports was found when an AR System query was converted into a Crystal Report web query. Try to rewrite your AR System query in another way. Make sure that the file exists. There was a failure during conversion because the field for which an enum value was provided is not an enum field type. There was a failure saving the attachment file to the client’s local file system because it could not be located on the web server. There was a failure displaying the attachment file in a new window because it could not be located on the web server. Make sure that the file exists. There is no attachment file to save. Download attachment failed. and then retry the conversion. 9224 Error Crystal Report does not allow ‘}’ in fieldname. Please see your administrator. There is no attachment file to display.AR System error messages 9219 Error 9220 Error 9221 Error 9222 Error 9223 Error There is no attachment file to delete. A valid AR System query that uses a $NULL$ value must be either in a “‘field’ = $NULL$” or “‘field’ != $NULL$” format. There was a failure to delete an attachment file because it could not be located on the web server. Cannot convert AR System query into a Crystal query: character value in QualifierInfo object is NULL. Try again or rewrite your AR System query in another way. Remove this character from the fieldname. Please see your administrator. The native report output failed because the file location was not specified. Make sure the file exists. Please see your administrator. Please see your administrator. To continue. Rename the AR System field so that it does not use a close brace. To continue. Chapter 2 Action Request System error messages 227 . rewrite the AR System query into a format more easily understood by the Crystal Report engine. the attempt to convert it into a Crystal Report web query failed. To continue. There was a failure in converting the AR System query into a Crystal Report web query because of unsupported syntax. There was a failure in converting the AR System query into a Crystal Report web query. There was a failure downloading the attachment file because it could not be located either on the web server or AR System server. but the specific reason for the failure is unknown. Make sure that the file exists.

The URL supplied is invalid.BMC Remedy Action Request System 7. Re-attach the definition and try again or create a new report. To continue. The report operation could not parse the field attributes in the definition file. An invalid operation was specified for a AR System report. No attachment info for report attachment. Please see your administrator. Contact your AR System administrator. The report consists of a string that cannot be understood by the system.5. Bad data type for report attachment field. To continue. To continue. 9234 Error 9235 Error 9236 Error Cannot display AR System report reportName. try creating a different definition file or redesigning your report.00 9231 Error 9233 Error Invalid AR System report definition. Ask your administrator to check the report form definition. The native report failed to appear on your browser for unknown reasons. Problem in parsing AR System report definition: no 'Report: ' string found. check that the report’s entry in the report form has a valid attachment. see the remainder of the message. 228 Error Messages Guide . To continue.arr definition file. use the BMC Remedy Mid Tier Configuration Tool to specify a report directory. Please see your administrator. No base directory specified for reporting. The report was not extracted because the file name of the report could not be retrieved. The report operation could not parse the field IDs and sort order. reattach the definition and try again or create a new report. Please see your administrator. To continue. No filename for report attachment. Bad report operation for AR System reports. The native report operation failed to open the report *. 9240 Error 9241 Error 9242 Error 9243 Error 9244 Error 9245 Error Cannot decode URL. Please try again or see your administrator. try creating a different definition file or redesigning your report. Please see your administrator. Cannot open AR System report file fileName. Cannot create report directory directoryName. See your administrator. try creating a different definition file or redesigning your report. Re-attach the definition and try again or create a new report. Field has no info in AR System report definition. Please try again or see your administrator. There was a failure when extracting the report due to an invalid data type for the attachment field. Also check the disk permissions on your configured report directory. The report definition file was not extracted because no session-specific report directory could be retrieved from the configuration. The location (URL) of the native report cannot be decoded. 9237 Error 9238 Error Cannot parse AR System report definition. Please try again or see your administrator. The native report output failed because of an invalid report definition. try creating a different definition file or redesigning your report. check that the report’s entry in the report form has a valid attachment. To continue. Verify that the report exists. The native report output failed because the report definition specified no fields. The report was not extracted because information about the attachment field could not be retrieved. You might also check your permissions and try again. Please see your administrator. Check the name of the configured report directory and try again. To continue. To continue. Re-attach the definition and try again or create a new report. Please try again or see your administrator.

Please see your administrator. To continue. check that the query converter class implements the report query converter interface. Problem with starting query conversion: stringContents. Report operation command is empty. check the report and report type forms on the server for valid report names and types. To continue. To continue. An initial failure occurred when the original query string was converted into a QualifierInfo structure that the report engine’s format can interpret. 9248 Error 9249 Error 9250 Error 9251 Error 9252 Error 9253 Error 9254 Error Security violation in creating directory directoryName: directoryName. This operation is no longer supported. Please see your administrator. Please see your administrator. There was an invalid data type for the query class field when the query string was converted from the AR System native format into the report engine’s format. 9247 Error Cannot find report type reportType. 9256 Error 9257 Error Chapter 2 Action Request System error messages 229 . ARSystemServer serverName does not have form with ID IDNumber. Cannot load query converter class classType. The report was not retrieved when the Report form was queried for the entry that matches the parameters in the request. There was a failure creating the report definition file from the Message Catalog. create. or edit. To continue. The report type was not retrieved when the Report form was queried for the entry that matches the parameters in the request. Please see your administrator. To continue. Please see your administrator. see AR System Java API documentation. Invalid report operation. To continue. 9255 Error Cannot instantiate query converter class className. For information about the QualifierInfo class. The query converter class was not loaded when the query string was converted from the AR System native format into the report engine’s format. verify that the query converter class implements the report query converter interface. Problem opening output stream: stringContents Please see your administrator. Please see your administrator. an invalid operation was used to post the report. check the report type form definition. fix the action to use a valid operation. Internal error: Bad data type for query class field. check the report and report type forms on the server for valid report names and types. verify that the query converter class is installed in your CLASSPATH. The only valid operations are run. During report creation in the Open Window action. There were permissions problems in creating a report directory. There was a failure because AR System server failed to retrieve the form with the specified ID needed to create the report. Bad data type for report operation command field. Please try again or see your administrator. Please see your administrator. Please see your administrator. The report operation command does not have a command specified for this report type. Please see your administrator. To continue. An instance of the query convertor class was not created when the query string was converted from the AR System native format into the report engine’s format. To continue.AR System error messages 9246 Error Cannot find report reportName of type reportType for form formName on server serverName. verify that the mid tier has write access to this directory. An inappropriate command was issued for the report because of an invalid data type.

There was a failure displaying the status history in a new window because no entry was selected. You tried to access a field that you have no permissions to. Required parameters include the following items: Form (or form alias) Server name 9263 Error 9264 Error 9265 Error 9266 Error 9267 Error 9268 Error Problem opening form in Direct Access. or check your permissions to continue. User has no access permission to the field fieldName. There was a failure retrieving the path of the JSP page that represents the form. for example. Please select an entry first. You also see this error if you are unable to “drill down” to a record in a table field using an Open Window active link action.5. There was a failure to validate the values for this field so that it can be properly formatted. This object (for example. The Modify operation failed when updating an AR System request. Check your permissions to continue. a simultaneous modification by another user or a failure in workflow. Required parameter(s) missing in Direct Access: parameterName. The location of the Crystal Reports Server XI engine is not specified in the BMC Remedy Mid Tier Configuration Tool. Error Messages Guide 230 . Error generating Status History information. Please see your administrator. Possible causes for this error include. The JSP path could not be constructed because some of the following data is missing: Form View Application Locale 9269 Error Unable to perform query because results list field not found.00 9259 Error 9260 Error 9261 Error 9262 Error No such object(s) in AR System server. The Submit operation failed when creating an AR System request. There was a failure in creating the form view because the required parameters either contain no value or a NULL value. The request retrieval failed because the entry ID does not exist in the database. Modify failed. Report location is missing from report settings configuration page. a schema. Please inform your AR System administrator. To continue. User has no access permission to the form formName. verify that the object exists on AR System server. The XML string containing the Status History field information was not created. You entered an incorrect user name or tried to access an AR System form that you have no permissions to. The query failed because the result list in the form could not be located. for example. Submit failed. You have entered an improperly formatted value for the field. or container) was not located in the server cache. Status history is displayed for the web in a separate window.BMC Remedy Action Request System 7. enter a value for the required field and retry the Submit operation. Try reentering your user name. 9270 Error 9271 Error Entry with ID IDNumber does not exist in database. There are many possible causes for a Submit failure. active link. In this particular case. a required field is left blank. The request was therefore ignored.

No results were returned. There was a failure in the process used by the Set Fields action. There was a failure because multiple matches were found in the form during a Set Field or Push Field action. All workflow processing is stopped. an integer field. If the server is a 5. To continue. to a more common multiple match or no match error. To continue. configure the workflow in BMC Remedy Developer Studio for a different multiple match response in AR System. this operation has been defined so that no match generates an error. not for submit or query. To continue. To continue. There was a failure to add the field to the query bar HTML input element because it is a displayonly field. There was an internal system failure during the execution of this active link. add a web view for the form. The server could not parse the query correctly.ARSystemServer. All workflow processing is stopped.x. Chapter 2 Action Request System error messages 231 . you must upgrade the server to 5. There is no valid web view for this form. To continue. There was a failure to validate the values for this field because they are out of the acceptable minimum and maximum range limits defined by the administrator. There was a failure because no matches were found in the form during a Set Field or Push Field action. Server not present in the configured servers list . A failure occurred because the name of the server is not present in the list of valid mid tier servers. A failure occurred because there is no server license for the mid tier. Only fields holding actual database values like. for example. and you can then open it. for example.x or later environment in which no web view was defined or a form on a pre-5. for example. This could be a form on a 5.x or later and then create a web view for the form before you can open it. however. Set Field to $NULL$. You tried to drill down on a table or to display.AR System error messages 9272 Error 9273 Error Value does not fall within the limits specified for the field. 9278 Error 9279 Error 9280 Error 9281 Error 9282 Error 9283 Error 9289 Error Not a valid license for web tier to access the server: ARSserver. for example. This error is not due. No item matches active link conditions. Set Field to $NULL$.x or later server. Failed to create the following menu: menuName. The system cannot open a form that does not have a valid web view on the web. verify that a valid server exists. because you entered an invalid server name. Status History operation valid only in modify mode. There was a failure during login. An internal error has occurred during workflow processing: errorMessageString. There was a failure to expand the query string for a dynamic menu. are included. or Use First Matching Request. If the server is pre-5. There was a failure to display the status history because it is valid only in modify mode. Set fields active link running a process failed.x AR System server. verify that a valid license exists. Invalid AR System Server Name. configure the workflow in BMC Remedy Developer Studio for a different multiple match response in AR System. by using an Open Window action. This is a display-only field. a search menu. verify that the process works independently of the Set Fields action. a form that does not have a web view defined. 9275 Error 9276 Error 9277 Error Found more entries than expected during workflow processing.

You also see this message if a list of selected requests contains too many nonconsecutive entry IDs. The Crystal engine does not recognize this method for checking NULL values. try re-entering your password or contact your AR System administrator for assistance. for example. Saving your changes will overwrite the changes made by that user. 9299 Warning 232 Error Messages Guide . Do you want to save your changes? A conflict exists because another user and you are retrieving the same request. for example. There was a failure converting a AR System query into a Crystal Report query because Crystal has a limitation in how many boolean operators can be used in a query. 9294 Error Your query has returned too many results. refine the qualification to make sure that it returns at least one matching request. 9298 Error The original table field/results list query will be used. No matches were found for your qualification. The AR System query format failed to convert into the report engine’s format because the converted query was too complex. Save your changes only if you are sure your changes will not destroy important information. Please rewrite your query. user. the converted query is replaced by the original AR System query string. There was a failure during login. 9297 Error The query is too complex for the report engine. The converted query is replaced by the original AR System query string. This record has been updated by another user since you retrieved it. To continue. To continue. Cancel your changes. Cannot convert AR System query into a Crystal query: you cannot use operatorInQuery to evaluate null. processing continues to display the zero matches label in the results list header. because the system does not recognize this user name as a valid administrator.00 9291 Error Not a valid administrator password on the server . specify a smaller maximum number of queries to return. To continue. Please add/modify the password for the server in configuration page. To continue. 9295 Error 9296 Error Incorrect login parameters. In this case.BMC Remedy Action Request System 7. Rewrite the query to use operators in the AR System query that the Crystal query understands. You can only test for = $NULL$ or != $NULL$. and then modify. An AR System query failed to convert into a Crystal report query. 9292 Error 9293 Error Not a valid administrator user on the server . In the same situation. perform one of the following tasks: Contact the other user (if you know who she is) to avoid overwriting her changes. No matching requests (or no permission to requests) for qualification criteria. To continue. To continue. The mid tier administrator password you specified is not recognized. Narrow your query criteria. “‘field’ = $NULL$”.ARSystemServer. similar messages are returned by web services and API programs (see message 302) and BMC Remedy User (see message 1200). enter a different login name. rewrite your query to return fewer requests. Web page. enter the missing parameters. There was a login failure because you did not enter certain parameters. You are running out of available memory because the query returned too many results. or ask your administrator to specify a smaller chunk size for the table or results list. However. form name or user name.ARSystemServer. Note: This message is returned by web clients. Requery.5. and/or server name(s) must be provided.

You have entered an improperly formatted value for a currency field. To continue. To continue. The report file cannot be retrieved from the server to the mid tier server. Using previous valid code. There was a failure retrieving the report file because the ReportServlet used by the Open Window active link action could not create a temporary directory in which to hold the report or extract the report to the directory. Cannot create Report file fileName. For example. Page has been updated. You cannot translate the group name in the Group List or Assignee Group Field.00 USD. To continue. You did not enter a valid currency value on a currency field. You entered a value for a date/time field that does not fall in the supported range. click the Refresh button on the page.AR System error messages 9300 Error 9301 Error 9303 Error 9304 Error Error occurred when executing process during an active link. Status History field does not exist in form. this error message was returned because the namespace was incorrectly formatted. You have entered an invalid currency code for a currency field. this error message was returned because no such web service exists on the server. use a different run process command. You did not enter an allowable currency code on a currency field. There was a failure in the Run Process active link action because this run process command is not supported. you entered 1. enter a date in the range between 1970 to 2037. The status history failed to appear in a new window because the Status History field is missing from the form. To continue. Contact your AR System administrator. Your form is outdated. 9305 Error 9306 Error 9307 Error 9308 Error 9309 Error 9310 Error 9325 Error 9326 Error 9327 Error 9329 Error 9330 Error Chapter 2 Action Request System error messages 233 . Cannot get embedded report. Please Refresh to get the updated page. Attempt to divide by zero (0) in arithmetic operation. When details about the web service request were extracted from the input document. Please enter time in this format: You entered the wrong time format into the Calendar popup window. The request to display the status history is ignored. The qualification failed because the system was unsuccessful in translating the group names into group IDs. A NULL value is returned. The form was recently updated in memory. rewrite the query so that you do not divide by zero. The qualification failed because of an illegal mathematical operation. Show Status History action ignored. No Web Service named webServiceName exists in server ARSystemServer. When a web service request was processed on the mid tier. Cannot communicate with less than version AR Servers There was a failure retrieving a user from the pool of available users. You have entered an invalid currency type. The location must include the server and the web service parameters. Date is out of allowed range of 1970 to 2037 for web client. The location does not have the required parameter server or webService. The specified currency value is a not an allowable currency type. The mid tier returns the field results based on the last previous valid currency code. Invalid time format. because a user pool does not work with this version of AR System.

Home Page needs a server. only addition is supported (string concatenation). No web service definition found: webServiceName A web service was requested. The Form Name field on the Home Page tab of the AR System User Preference form and the Default Home Form field on the Configuration tab of the Server Information dialog box are blank. No Preference form or ServerSetting Home Page form. 9341 Error 9342 Error 9343 Error 9344 Error 9345 Error 234 Error Messages Guide . Home Page needs a configured server. Specify a default home page form in the Server Information dialog box or specify a home page form for this user in the AR System User Preference form. Contact your AR System administrator. Your user name or password was not accepted by any AR System server configured in the BMC Remedy Mid Tier Configuration Tool. No Preference servers or Configuration Home Page Server. Invalid URL for accessing WSDL: requested_URL The WSDLServlet servlet could not generate the WSDL for a requested web service because the URL was invalid. No servers configured in Configuration.BMC Remedy Action Request System 7. Cannot connect to server ARSystemServer to access Home Page.5. or the arithmetic operation is not supported. The AR Server field on the Home Page tab of the AR System User Preference form and the Server Name field on the Home Page Settings page of the BMC Remedy Mid Tier Configuration Tool are blank. For example. Invalid Date Time Value: dateTimeString The mid tier could not parse the XML date/time string. Contact your AR System administrator. When a web service request was processed on the mid tier.Decimal2 = Character. In an active link arithmetic operation. Or you subtract Decimal1 . No AR System servers are configured in the BMC Remedy Mid Tier Configuration Tool. and anonymous user information is not specified in the BMC Remedy Mid Tier Configuration Tool. Home Page needs a form. the two operands cannot be made to match. you try to add two currency fields that have different currency codes. Specify a server in the BMC Remedy Mid Tier Configuration Tool or specify a server for this user in the AR System User Preference form. No authentication information is found: ARSystemServer Authentication information is not supplied in the web service request. and there are no matching functional currencies to add. such as USD and CAD. The mid tier could not make the necessary API call because an invalid operation type was specified for the web service. this error message was returned because no such operation was found in the web service. but the mid tier could not locate the web service definition. Home Page cannot connect to any Configuration servers with user name and password. Contact your AR System administrator.00 9331 Error 9332 Error 9334 Error 9335 Error 9336 Error 9337 Error 9338 Error 9339 Error No operation named operationName exists in web service webServiceName. A string value could not be substituted for the XPATH expression because the mid tier server could not find the corresponding mapping node. If the target field is a character. Invalid operation type operationType specified in web service container. Unable to connect to the server that contains the Home Page form. Data types are not appropriate for arithmetic operation. The XPATH expression xpathExpression is not found in input mapping. This can occur when the server is down or when the network is too slow (leading to a time-out).

formName and the view . An internal error occurred because parameters passed to the back channel were incorrect. The action failed because the mid tier is unavailable or could not be contacted. viewalias. Network protocol/data error when performing data operation. Unable to setup data connection. A user tried to load a form on the mid tier in an unsupported time zone. The operation cannot be completed because you are being logged out. see the BMC Remedy Mid Tier Guide. The form or view does not have an alias name.userName. A form definition has been changed. or appalias parameters. This can occur if a user opened multiple windows and is trying to do something in one window at almost the same time as logging out in another window. which is required for viewing the form on the Web. Unsupported locale locale. The mid tier implementation of global fields limits the amount of data that can be stored in all global fields to about 3. The view form servlet was used with user name and password parameters that differ from the ones used to create the current session. The locale is specified either in the languages selection in the browser or in the user preferences. so unable to retrieve data. This can occur if a form contains only relative views because relative views are no longer supported by the mid tier. The definition of a form that users have loaded was changed in such a way that a table on the form cannot be refreshed. Make sure the form . A user tried to load a form on the mid tier in an unsupported locale. An internal error occurred during a back channel request from the browser to the mid tier server. Log off the existing session and try again. No compatible (standard or web fixed) view for the requested form can be found . Use form.3 and later mid tier so the alias parameters to the view form servlet are no longer supported. The application specified in the URL does not exist. The form specified in the URL does not exist.5 KB. If this size is exceeded this error occurs. The current global field values are too large to be stored. or app parameters instead.viewName have an alias name. Unsupported timezone timeZone. 9357 Error 9358 Error 9359 Error 9360 Error 9361 Error 9362 Error 9363 Error Action canceled or unable to contact the web server. This error could also occur if the action was canceled by the user while it was being performed. Please contact administrator. If these parameters are missing this error occurs. For information about supported locales. Please contact administrator.ARSystemServer. ViewFormServlet requires server and form parameters on the URL.AR System error messages 9346 Error 9350 Error 9351 Error 9352 Error 9353 Error Failed to deploy.unable to display form. The view form servlet requires the server and form parameters to be in the URL (other parameters are optional). Chapter 2 Action Request System error messages 235 . view. Aliases are not supported by the AR System 6. Application does not exist on server . Contact your AR System administrator. 9354 Error 9355 Error 9356 Error The requested form formName cannot be found. ViewFormServlet no longer supports formalias. The time zone is determined at login time or from the user preferences. A current session exists for a different user . The mid tier could not find a view to display for the specified form. which is preventing the application from working correctly. A user who is logging out tried to make requests to the mid tier.

Active link run process not supported. 9365 Error 9366 Error 9367 Error No rows have been selected for ModifyAll. or you can omit the date and include only the time. If the guide name does not exist on the server. You can specify digits only for integer (numeric) fields. or the guide does not have a primary form. this error is generated. You entered a nondigit character for a numeric field. the If Any Requests Match field has Display ‘Any Match’ Error selected. Change the value to a legal integer value. The guide guideName is invalid for active links. Fix the format of the line. the format of the specified portion of time must match the rules for time stamps. and retry the operation. You can omit the time portion of a time stamp and include only the date. 9368 Error 9369 Error 9370 Error 9371 Error 9372 Error 9373 Error 9374 Error 9375 Error 9376 Error 236 Error Messages Guide .BMC Remedy Action Request System 7. Bad menu. The definition for the guide specified cannot be found and might be missing from the AR System server. and DECRYPT are supported only in filter workflow and not in active link workflow. However. Dynamic workflow allows an active link guide to be named at run time. Change the value to a legal decimal value. Format of date or time value is not recognized. The data types of the fields used in a relational operation are not consistent with the operations allowed for that operation. The format of a time value is not recognized. See the Workflow Objects Guide for information about the allowed data types of operations. Used by the Push Fields action when the administrator configures it to return an error when multiple matches are found. There was a failure in the Run Process active link action because this run process command was used incorrectly. The portion omitted defaults to an appropriate value. Change the value to a legal real value. and perform the search again. ENCRYPT. The guide or the primary form for the guide could not be determined. The guide guideName is invalid or not owned by any form. You have entered an improperly formatted value for a real field. AR System functions (used in assignments) such as CONVERT.5. The guide specified (via dynamic workflow) is invalid. Data types are not appropriate for relational operation. Function error in active link (bad function signature). such as using a run process that does not return a value in a Set Fields action. and retry the operation. This could be due to an active link change fields action that changed the menu for a character field. An AR System API function call was used with an invalid data type. The indicated value was entered as a value for a field with a data type of real. The value is not a legal decimal value. On the If Action page. A numeric field contains a nondigit value. and retry the operation. Function not supported. The value was entered in a field with a data type of decimal. this operation has been defined so that any match generates an error. The value is not a legal real value. The modify all action requires that at least one row is selected in the results list. This error occurs if the browser client requests a nonexistent menu. With dynamic workflow you can specify guide names from workflow instead of in BMC Remedy Developer Studio. You have entered an improperly formatted value for a decimal field. Select one or more entries in the results list and try again. The specified menu is invalid.00 9364 Error One or more items match active link conditions.

and modify the settings for Limit Number of Items Returned.AR System error messages 9377 Error 9378 Warning Time is out of allowed range of number and number. Please try opening the report again. Security Exception!! Possible insecured call is issued. To change the local setting in BMC Remedy User. Therefore. The maximum server name length is 64 characters and maximum form name length is 254 characters. Try again. the popup will be initialized to the current date. Narrow your search criteria or change the limit in user preferences. The call returned the number of entries specified as the maximum. The retrieval included a search that selected more than the maximum number of items allowed by the client or server. Authentication failed. A request to open a Crystal report through the web timed out. Click the icon to the right of the field to select the desired date. The requested plug-in does not exist in the list of plug-in servers in the BMC Remedy Mid Tier Configuration Tool. The supplied password is invalid. An authentication failure occurred. the popup will be initialized to the current time. Therefore. A user with the supplied login ID cannot be found on any AR System server. this error occurs. such as supplying the wrong administrator password on the configuration page for the AR System server. 9393 Error There is no jar file for the module “module” in the server “ARSystemServer”. choose Tools > Options > Behaviors. The plug-in JAR file is missing for a given data visualization module in the Data Visualization Module form. The mid tier should be able to create a directory so that it can download the plug-in information. No such user exists. The length of server name or form name passed to the viewformservlet is longer than the allowed length. If it cannot create a directory. Request timeout. 9392 Error Could not create the required module cache directory “directoryName” to download module “module” from server “ARSystemServer”. There is either no definition or the user “user” does not have permission for keys “keys” for the module “module” in the server “ARSystemServer”. AR System cannot process a time that is out of range. The date entered is invalid. 9379 Warning 9380 Warning 9381 Error 9382 Error 9386 Error 9387 Error 9388 Error 9389 Error The time entered is invalid. 9390 Error 9391 Error No module with name “moduleName” was found in the following configured module server(s) “servers”. Invalid password or authentication string for an existing user. Please try opening the report again. Click the icon to the right of the field to select the desired time. using a time within the allowed range. The requested plug-in definition does not exist in the Data Visualization Definition form. The query matched more than the maximum number of entries specified for retrieval. Only an administrator can change the server settings. ViewFormServlet required parameters server or form is too long. Chapter 2 Action Request System error messages 237 . or the user does not have correct permissions to access that data. A request was sent to open an unencrypted Crystal report.

The entry class specified for a module was not implemented. The module class “class” for the module “module” from server “ARSystemServer” made an illegal access and cannot be instantiated. The entry class specified for the module does not implement the plug-in interface provided in the GraphPlugin. This error occurs if a request is made for these modules and they are unavailable in the local plug-ins directory. The jar file “fileName” for local module “module” is not present. Could not read the properties file “fileName” for local module “module” In the available local plug-ins directory. 238 Error Messages Guide . The module “module” from the server “ARSystemServer” does not have the privileges to perform the call. Flashboards and reports are built on mid-tier local data visualization modules. Every view that needs to be deployed should have an alias.txt file that contains the information of these modules. Please see the log file for further details. The server “ARSystemServer” is not localized or not contactable. Nothing was changed. 9500 Warning 9501 Warning 9502 Warning 9503 Warning 9701 Error 9710 Error Nothing got deployed since the deployed Application is up-to-date. but the module requested the administrator anyway. so nothing was deployed. All forms and views must have an alias name specified to be deployed on the Web. this error occurs. No local copy found for module “module”.jar file. there should be a details. 9399 Error 9400 Error 9401 Error 9402 Error 9403 Error The module class “class” for the module “module” from server “ARSystemServer” is not found in the jar file. A JAR file is missing in the local plug-ins directory. The entry class was accessed incorrectly. Cannot retrieve Starting Active Link activeLinkName in Application applicationName on server ARSystemServer. or the string is not localized.5. The Entry Point Guide has no starting active link. An attempt was made to initiate a bulk entry transaction when one was in progress. The Currency form does not contain the correct number of required currency fields. If the file is missing.00 9394 Error 9395 Error 9396 Error 9397 Error 9398 Error Could not download the module jar file for module “module” from the server “ARSystemServer” due to an exception. The localized version of a given string is unavailable. The form contains no fields. Bulk entry transaction already in progress. Problem encountered during creation of a Currency form. The administrator login option was not selected when module information was created in the Data Visualization Module form. The mid tier cannot download a JAR file for a particular data visualization plug-in in a server. The module class “class” for the module “module” from server “ARSystemServer” does not have the required no arg constructor. Contact your AR System administrator.BMC Remedy Action Request System 7. The plug-in container in the mid tier cannot instantiate the specified entry class for a module. No fields available for the form: formName. The module class “class” for the module “module” from server “ARSystemServer” does not implement the required interface.

and restart the server.log file. The shared library is invalid because it violates one of the prerequisites When a shared extension library is loaded.log file. The shared library does not provide an Identification routine implementation When a shared extension library is loaded. The server continues to function. The library is then unloaded from memory. The updating of metadata through the Metadata view forms is not allowed.log file. Make sure that the shared library and all dependent libraries are specified correctly. An attempt was made to end a bulk entry transaction when no transaction was in progress. such as the CMDB engine.log file. The error message is logged in the arerror. The server continues to function. In this case. This error occurs when the shared library does not implement a required routine. To fix the problem. The library is then unloaded from memory. Error encountered while loading the shared library. the AR System server invokes callback routines to identify the library to the server. The RPC number is returned by the library through a callback routine invoked by the server. The error message is written to the arerror. Invalid action type for end of bulk entry transaction.conf. 9751 Error The shared library identification is invalid or duplicate When a shared extension library is loaded. The server continues to function. check the implementation of the callback routine and make any necessary corrections. This error occurs when the ar. The server loads a configuration management database (CMDB) shared library and assigns it a remote procedure call (RPC) identification number. but any functionality associated with the shared library is unavailable. The AR System Server could not load a shared extension library. The attempted bulk entry transaction failed due to an error in one of the individual operations. Check the library paths specified in ar. the AR System server invokes callback routines to identify the library to the server. The action type supplied for ending a bulk entry transaction was not one of the acceptable options. The error message is logged in the arerror. Check the return list for more detailed information about the individual operation failure. but any functionality associated with the shared library is unavailable.conf file. but any functionality associated with the shared library is unavailable. The shared library does not provide the RPC program number it is registered for.The library is then unloaded from memory.AR System error messages 9711 Error 9712 Error 9713 Error 9720 Error 9730 Error 9750 Error No bulk entry transaction is in progress. the routine returned an invalid RPC value. but any functionality associated with the shared library is unavailable. See the C API Reference for the list of acceptable values. The updating of object relationship data through the AR System Object Relationships form is not allowed. Bulk entry transaction has failed due to an error encountered during an individual operation. The error message is logged in the arerror. 9752 Error 9753 Error 9754 Error Chapter 2 Action Request System error messages 239 .conf file contains multiple registry entries for the same library or when the identification callback routine returns an error. the AR System server invokes callback routines to identify the library to the server. The server functions. This error occurs when the server invokes a routine that is not implemented by the shared library. Shared libraries are registered for loading in the ar.

An internal system error occurred. A required form for Email is missing. and then report it to Customer Support. A shared library tried to use an internal API exposed by AR Server. Contact Customer Support. This is an internal error. Identify the user activity and workflow associated with the error. An internal error occurred because a filter workflow extension library was called by a filter action that does not have a filter context. Verify that the role name is valid. This is an internal error. This version of internal API is not supported by the server. The AR System server is unable to open the file that contains the license audit data. In an email notification. Cannot locate mailbox. The initialization routine returned an error. The server tried to resolve a role name to a role ID. Error opening license audit file. Each time an audit is run. The server functions. Email Attachments. Role name was not found. Please verify the form gets imported or import it manually to make sure that the Email Engine will work properly formName. check the implementation of the routine and make any necessary corrections. Identify the user activity and workflow associated with the error. The identified form is missing and must be imported if necessary. and the shared library was unloaded from memory. Contact Customer Support. 9756 Error 9758 Error 9759 Error 9760 Error 9761 Error 9781 Error 9800 Error 9801 Error 9802 Error 9803 Error 9804 Error 9820 Error 240 Error Messages Guide . Problem encountered with an Email form. Workflow API function called from improper filter phase. Role names can be specified by a user or by workflow. but the API version is incompatible with the AR Server version. Unrecognized internal workflow API function. but the role does not exist. On server startup. Email attachment mapping structure is invalid. Couldn't locate the Email form. An extension library was called by a filter action that did not have a filter context. but any functionality associated with the shared library is unavailable. Invalid filter processing call made outside of filter context. AR System attempts to recreate the file if it is not found or inaccessible. or Email Association forms.00 9755 Error Error encountered while initializing (Initialization routine) the shared library. When an email message is sent to a specified user. To resolve the problem. either there is no default mailbox or the mailbox specified in the notification does not exist. this error message is returned if the server cannot find the Email Message. Extension library called with no filter context. an initialization routine runs for all shared extension libraries that are loaded. Error in the BMC Atrium CMDB extension library API.BMC Remedy Action Request System 7. Check the associated role name and make sure it is valid. Reserved fields are being created on the Email form that already exist on the form with the same field IDs. Server will attempt to import the form in place. Contact Customer Support.5. Error in the BMC Atrium CMDB extension library API. and then report it to Customer Support. This error can be caused by the AR System server not having read/write permission to the server log directory.

The AR System server received an error when attempting to write to the license audit data file. There is no such application user fixed license on the system: licenseType. Contact Customer Support. The following write application token has become available and has been allocated to you -access has been upgraded to write access. Try restarting AR System. corrupt license audit file. License information might be entered incorrectly. No additional application fixed license for this type of license is available for assigning. Either this user does not have an application write license for the application. Cannot modify or unlicense the Application or Form. Make sure that the application is a deployable application. The license information provided for this form does not match that in owning application. An internal system error occurred. The data in the license audit file is corrupt. Contact Customer Support. Get more licenses if necessary. The existing file is renamed and a new audit data file is created. A fixed license was returned to the system and is now available for assigning. This can be caused by the AR System server not having read/write permission to the server log directory. No more fixed licenses can be assigned until the number of fixed licenses is greater than the number of users who are assigned fixed licenses. This error can be caused by the AR System server not having read/write permission to the server log directory. contact Customer Support.). Application or Form already Licensable. Contact your AR System administrator. unable to initialize license audit mutex. If restarting AR System does not fix the problem. not a local application. You do not have application write license. A floating license was assigned for your use. 9822 Error 9823 Error 9824 Error 9850 Error 9851 Error 9852 Warning 9853 Note 9854 Note 9855 Note 9856 Error 9857 Error 9858 Error 9859 Error 9860 Error The following application fixed licenses have been returned to the system: licenseType. Either license information was entered incorrectly. The following application fixed licenses have been granted: licenseType. Error. An internal error occurred during the AR System server start up. There are no application fixed licenses of this type for assigning: licenseType. A fixed license was assigned. The application is not licensed. Chapter 2 Action Request System error messages 241 . For information about local and deployable applications. The application license format is not valid. The AR System server received an error when attempting to read the license audit data file. or the fixed license does not exist.AR System error messages 9821 Error Error reading license audit file. You cannot make an application license less restrictive. see the Form and Application Objects Guide. Make sure that license names end with User Fixed or User Floating and that each license for a user is separated by a semicolon (. Error writing license audit file. Error. or a floating license is unavailable for assigning. An Application fixed license of this type has been assigned to more users than the number of valid licenses you have: licenseType. Contact Customer Support.

9874 Error 9905 Error 9907 Error 9922 Error 9923 Error 9924 Error 242 Error Messages Guide . Check the documentation to verify that your parameters are legal and can be used together. The workflow debugger command was issued at an incorrect time. Try later to see whether a floating license becomes available. Enable auditing for the base forms and retry the operation. You can set the license properties after the form is created. Currently accessing the application form in read-only mode. Forms have to belong to deployable applications to be made licensable. 9863 Warning 9864 Error No license property can be set while creating a form. see the Form and Application Objects Guide. An internal system error occurred. Internal API call failed. if you have only breakpoints 1. Command not valid at this time. it might not be legal for this program or it might not be legal in combination with other parameters. You cannot audit the specified form types. You have read-only access to the application. Also.00 9861 Error 9862 Warning The form is missing application licensing information. Audit not possible on Dialog or Audit forms. A local application cannot be made licensable. or contact your AR System administrator. Breakpoints are identified by a numeric ID. this message is issued. Invalid Breakpoint ID. An internal system error occurred. Retry the operation. License properties for a form cannot be set when a form is created.BMC Remedy Action Request System 7. The same Log Key cannot be applied to more than one field in a schema. Contact Customer Support. Adding a field or changing the data type is not permitted when setting the field value list during workflow debugging. No free application user floating write license tokens are available. Illegal command line parameter. For example. Error in field value list (bad ID or datatype). For information about local and deployable applications. The Application or the Form cannot be made licensable. 2 and 3.5. Join form Audit cannot be enabled unless the base forms have audit enabled. issue the List Breakpoints or List Remote Breakpoints command. Specify a unique log key for each field. Issue the command when workflow is executing. This error typically indicates that the breakpoint specified in a command does not exist. because there is no field-value list at that time. 9871 Error 9872 Error 9873 Error Execution terminated by workflow debugger. Only deployable applications can be made licensable. and you issue a command to clear breakpoint 4. A filter or escalation execution was terminated with a forced error from the workflow debugger. A program was called with a command line parameter that cannot be used. For example. License will upgrade when one is available. To see the list of valid breakpoints (including ID). this error would result when you try to view the field-value list when the debug thread is idle (workflow is not executing).

Choose one of the following options to correct the problem: Make sure that the main form is linked to the correct archive/audit form. The audit qualification cannot have external references. if you are importing a form named “form_audit” that has audit enabled. The date calculated is invalid or a bad date format. Enter a month value between 1 and 12. and AR System automatically creates a form. You cannot disable the audit on this form until you disable the audit on dependent form. see Error 9925. audit on the base forms cannot be disabled. Cannot import only Archive/Audit form. For example. Set archive/audit to none in the main form. Check the arerror.log file. You must enable audit on the base forms first. The form for which you are disabling audit has a dependent form on which audit is enabled. if you have a base form that has audit disabled. To correct the problem. and then enable audit on the dependent forms.AR System error messages 9925 Error There are an incorrect number of reserved fields in the Archive or Audit form. Chapter 2 Action Request System error messages 243 9933 Error 9934 Error 9950 Error 9951 Error 9952 Error 9953 Error . Type of recurrence requested is invalid. and then disable audit on the base forms. Check the date and make any necessary corrections. and enable archive/audit again. The data types of the data fields in the Source and Archive/Audit form do not match. You cannot import only the source form. This warning is received when a form with audit or archive enabled is imported from a file and the audit or archive form is not present on the AR System server. or the main form and the corresponding archive/audit form. The input provided for calculating the next recurrence is bad. Either the Main form by itself or both Main and Archive/Audit can be imported. You can import the main form alone. see Error 9925. Choose a new name for the archive/audit form. and a form with the same name is not present on the AR System server. Daily. and Special Dates. audit is disabled on the imported form. To correct the problem. The form for which you are enabling audit has a base form on which audit is disabled. For example. You cannot enable the audit on this form until you enable the audit on base forms. 9931 Error 9932 Warning Qualification cannot contain EXTERNAL references. Archive or Audit form not found. Month of year selected is invalid. 9926 Error 9927 Error 9928 Error 9929 Error 9930 Warning The Archive or Audit form is already in use by another form. if you have a join form that has audit enabled. You must disable audit on the dependent (join) forms first. Valid recurrence types are Yearly. For example. correct the problem. To correct the problem. The number of data fields in the main form should be less than or equal to the data fields in the Archive or Audit form. Monthly. audit on the dependent forms cannot be enabled. Archive or Audit will be disabled. Field is missing from the Archive/Audit form. see Error 9925. see Error 9925. To correct the problem. Please make sure the date format is in the ARServer’s date format and separator. Weekly. An internal error occurred.

5. Only one form can contain the Application_Properties fields. Cannot find respective System Log Form.00 9954 Error 9955 Error 9956 Error 9957 Error 9958 Error 9959 Warning 9960 Error 9971 Error Week of Month selected is invalid. All the items in the list should be of that type. Each element in the daysOfWeek array cannot be greater than 1. Separate dates with semicolons. using the overwrite option if the form exists but is corrupted. The date is out of range of the 1970 . The log form is missing or corrupted. for example. but it failed because the recursion qualifier (recursionQual) was not specified. There is no recursion qualifier specified in the Recursive Query. For more information. The year of the calculated recurrence date is outside of the range allowed by the operating system. Make sure the dates are in the server’s date and separator format.12/25/07.BMC Remedy Action Request System 7. The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query. Enter a day value from 1 to 31. the date obtained is not valid for this month. Using the recurrence provided. Day of Month selected is invalid. Only one form can contain the Application_Interface fields. Recurrence of type Specific Dates has no dates.2038 allowed by the OS. Only one form can contain the fields reserved for respective System Log Forms. Skipping to next recurrence. 12/24/07. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaRecursiveQueryStruct structure 244 Error Messages Guide . The next recurring value will be tried. Day of the week selected is invalid. For more information. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaRecursiveQueryStruct structure 9972 Error 9973 Error 9974 Error 9975 Error 9976 Error Wrong schema type specified for a query from list item in the Recursive Query. Enter a week value from 1 to 5. Each element in the HoursOfDay array cannot be greater than 1. Hours of day selected is invalid. The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query. The recurrence date is not valid for this month.def file from the C:\Program Files\BMC Software\AR System\Arserver\systemforms\en folder. but it failed because one or more of the items in the query from list (queryFromList) of the recursive query structure were not of the type AR_MULTI_SCHEMA_SCHEMA_NAME. Import the LogForm*.

see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaRecursiveQueryStruct structure 9981 Error Wrong or missing join type. but it failed because more than one recursive query was included in its query from list (queryFromList). The query from list can contain only one item of the recursive query type. For more information. Use one of these integers to specify the joinType: 0—AR_MULTI_SCHEMA_JOIN_INNER (Inner join) 1—AR_MULTI_SCHEMA_JOIN_LEFT (Left outer join) 2—AR_MULTI_SCHEMA_JOIN_RIGHT (Right outer join) For more information. The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query. The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query. but it failed because the fields that the recursive query was instructed to retrieve were on more than one form. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaQueryFromStruct structure Chapter 2 Action Request System error messages 245 . For more information. but it failed because the recursive schema alias (recursiveSchemaAlias) does not match any alias or schema (form) in the recursive query’s query from list (queryFromList). see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaQueryFromStruct structure 9979 Error Can specify fields from only one schema in the Recursive Query fields list. All the fields must be on the form designated by the recursive schema alias (recursiveSchemaAlias). For more information. The ARGetListEntryWithMultiSchemaFields function tried to perform a dynamic join. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaRecursiveQueryStruct structure 9980 Error Wrong recursive schema specified in the Recursive Query. The ARGetListEntryWithMultiSchemaFields function tried to perform a dynamic join.AR System error messages 9977 Error Can not specify more than one Recursive Query. but it failed because the join type (joinType) of one of the items in the function’s query from list (queryFromList) is either invalid or not specified.

For more information. 254 characters). For more information. Ensure sure that the object specified in that element is valid. see these documents: C API Reference. These are the valid item types: Form = 0 (AR_MULTI_SCHEMA_SCHEMA_NAME) Recursive query = 2 (AR_MULTI_SCHEMA_RECURSIVE_QUERY) Verify the type and retry the operation. see these documents: C API Reference. The RegularQuery parameter of the getListEntryObjects function (Java API) is NULL. For more information. For more information. Character strings must be terminated by a \0.00 9982 Error Wrong query type specified for an item in the query from list. A call to the ARGetListEntryWithMultiSchemaFields function failed because the alias (queryFromAlias) of the form or recursive query associated with one of the fields specified in the call is either empty or exceeds the maximum length (AR_MAX_NAME_SIZE. The RegularQuery parameter of the getListEntryObjects function (Java API) contains a list of the query sources that is either NULL or empty. Ensure that the list has at least one element. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaQueryFromStruct structure 9983 Error Schema alias associated with the field is not valid.BMC Remedy Action Request System 7.5. which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram Java API online documentation 9986 Error Join qualifier is specified but join source is not valid. Verify the alias and retry the operation. Provide a valid instance of the RegularQuery object and retry the operation. For more information. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaQueryFromStruct structure 9984 Error RegularQuery cannot be NULL. One or more of the query source objects (IQuerySource) in the RegularQuery parameter of the getListEntryObjects function (Java API) contains a join qualification but does not specify a query source object to join with (getJoinedWith element). which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram Java API online documentation 246 Error Messages Guide . which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram Java API online documentation 9985 Error The list of query sources should contain one or more items. A call to the ARGetListEntryWithMultiSchemaFields function failed because one or more of the items in the function’s query from list (queryFromList) is of the wrong type. see these documents: C API Reference.

see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromStruct structure ARMultiSchemaQualifierStruct structure Chapter 2 Action Request System error messages 247 . A call to the ARGetListEntryWithMultiSchemaFields function failed because the user issuing the call did not have permission to any of the fields in the function’s getListFields parameter. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaRecursiveQueryStruct structure 9989 Error The list of the query fields must contain at least one regular field you have permission to. give the user permission to at least one field in that parameter. The definition of a field specified within a call to the getListEntryObjects function (Java API) is invalid. The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromStruct structure ARMultiSchemaQualifierStruct structure 9992 Error Dialog forms not allowed in a dynamic query. but it failed because although the recursive query type is specified in the function’s query from list (queryFromList). For more information. A call to the getListEntryObjects function (Java API) failed because the list of fields in the ValueSetQuery object contains more than one field. A call to the ARGetListEntryWithMultiSchemaFields function failed because the join criteria for one of the forms in the function’s query from list (queryFromList) did not reference a field in the preceding item in the list. give the user permission to all fields in that parameter. To enable the function to return data. which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram Java API online documentation 9988 Error Recursive query cannot be NULL. see these documents: C API Reference. To return all matching requests.AR System error messages 9987 Error Field definition not valid. see the C API Reference. such as a dialog box. Review the fieldId element in the join criteria (ARMultiSchemaQualifierStruct) and retry the operation. For more information. Fix this error and retry the operation. A call to the ARGetListEntryWithMultiSchemaFields function failed because the function’s queryFromList parameter contains a display-only form. For more information. which includes information about the ARGetListEntryWithMultiSchemaFields function and its Java class diagram Java API online documentation 9990 Error 9991 Error Invalid join qualifier for schema. For more information. For more information. the recursive query structure is missing. Either the field source object is NULL or the field ID is less than 0. The list of the value set query fields can contain one field only. For more information. see these documents: C API Reference.

BMC Remedy Action Request System 7. Incoming Mailbox configuration either does not contain a User Name or Server Name. you must select a date and time in the Expiration Date field. If you delete the default outgoing mailbox and do not specify a new default. you must specify a server in the Email Server Name/IP field. 11007 Error 11010 Error 11011 Error Email Action cannot be set to Parse if no Outgoing Mailbox is associated with this mailbox. you must specify an email address in the Email Addresses field. This means that you will no longer be able to send email notifications and/or reply to emails. you must specify a server in the Email Server Name/IP field and a user in the Email Server User field. 248 Error Messages Guide . A mailbox name is required. If you delete an associated incoming or outgoing mailbox. Mailbox Name is missing and no default Mailbox has been configured. ARGetListEntryWithMultiSchemaFields—Remove these field types from the join criteria (joinQual) of the items in the function’s query from list (queryFromList). You are removing the default mailbox.5. Please specify a new default mailbox. You must specify a mailbox name or request your AR System administrator to set up a default mailbox in the AR System Email Mailbox Configuration form. Outgoing Mailbox configuration does not contain a Server Name. the mailbox name must be entered when sending an outgoing email or replying to an incoming email message. Do not specify the join criteria in the first item in the list. If you select Yes in the Force For Mailbox field. If you select incoming for the Mailbox Function. Specify join criteria in the second item and each item thereafter to define the join with the previous item. If you select Parse in the Email Action field on the Advanced Configuration tab. Review the join criteria and retry the operation. If you select outgoing for the Mailbox Function. The ‘Force From Email Addresses’ has been enabled but no Email Addresses have been supplied. 11001 Error 11002 Error 11003 Error 11004 Error 11005 Error 11006 Error The ‘Force For Mailbox’ has been enabled but no Mailbox has been supplied. The ‘Expires’ has been enabled but no Expiration Date has been supplied. If you select Yes in the Expires field. you must select a mailbox in the Associated Mailbox Name field. A call to the ARGetListEntryWithMultiSchemaFields function failed because the first item in the function’s query from list (queryFromList) contained join criteria (joinType and joinQual). You are deleting a record that has an associated mailbox. you must specify or select a valid mailbox in the Mailbox Name field. see these topics in the C API Reference: ARGetListEntryWithMultiSchemaFields function ARMultiSchemaQueryFromList structure ARMultiSchemaQueryFromStruct structure 9994 Error Diary field or long char field not allowed in join criterion.00 9993 Error Join qualifier not allowed for the first query source in the list. An API call to one of the following functions failed because the join criteria associated with the function contains a diary field or a long character field: ARGetListEntryWithFields—Remove these field types from the predefined join criteria in the AR System join form specified by the function’s schema argument. you cannot send email notifications or reply to email using this mailbox. If you select Yes in the Force From Email Addresses field. For more information.

help with error messages 15 E error message custom 18 defined 8 N note informational message.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Index A AR System Error Messages form 15 AR System Message Catalog form 15 AR System messages help with 15 message catalogs 13 message reporting 12 UNIX server error reporting 12 H help with error messages 15 L localizing message catalogs 14 M message catalogs described 13 localizing 14 messages AR System Error Messages form 15 AR System Message Catalog form 15 custom 18 localizing 14 message catalogs 13 reporting 12 reserved ranges of message numbers 18 syslog daemon on UNIX 12 terminology 7 UNIX server error reporting 12 Windows server error reporting 13 B BMC Software. AR System 8 documentation. contacting 2 C catalogs. message on UNIX 13 custom error messages 18 customer support 3 D display data types 37 documentation. defined 7 O organization of this guide 17 F forms AR System Error Messages 15 AR System Message Catalog 15 P product support 3 Index 249 .

See diagnostic messages U UNIX message catalogs 13 server error reporting 12 syslog daemon 12 W warning message. defined 8 Windows. customer 3 syslog daemon on UNIX 12 T technical support 3 troubleshooting. messages by AR System clients 12 S support. server error reporting 13 250 Error Messages Guide .A B C D E F G H I J K L M N O P Q R S T U V W X Y Z R ranges of message numbers 18 reporting.

.

*77359* *77359* *77359* *77359* *95377* .