ErrorMsgs 7604

BMC Remedy Action Request System 7.6.
04
Error Messages Guide
January 2011
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
(01) 713 918 8000
Fax
713 918 8000
Outside United States and Canada

Telephone
(01) 713 918 8800
If you have comments or suggestions about this documentation, contact Information Design and Development by email at
doc_feedback@bmc.com.
Copyright 19912011 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, DB2, ClearCase, and AIX 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 and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
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. From this website, you can:
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:
Product information
Product name
Product version (release number)
License number and password (trial or permanent)
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
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:
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.
Contents
Preface
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AR System Error Messages form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminology used in error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AR System documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
8
8
Chapter 1
AR System diagnostic messages
11
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
12
13
13
14
15
15
Chapter 2
17
AR System error messages
Finding AR System messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

AR System messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 3
BMC Remedy Migrator error messages
285
About BMC Remedy Migrator error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

BMC Remedy Migrator error message types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
BMC Remedy Migrator error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Index
303
Contents
Preface
IMPORTANT
The compatibility information listed in the product documentation is subject to
change. See the compatibility matrix at http://www.bmc.com/support for the
latest, most complete information about what is officially supported. Read the
system requirements for your particular operating system carefully, especially the
necessary patch requirements.
Audience
This guide is written for developers, administrators, and users of BMC Remedy
Action Request System (AR System).
AR System Error Messages form

The information in this manual is also available through the AR System Error
Messages form. You can use this form to search for notes, warnings, and error
messages returned by AR System. You can also use this form to modify the
message contents that appears to users, to customize the detailed description in the
Description field, and to provide helpful notes in the Notes field.
For information about how to install the AR System Error Messages form, see To
set up the AR System Error Messages form on page 15.
Preface
BMC Remedy Action Request System 7.6.04
Terminology used in error messages
Message TextA message in a dialog box that interrupts operations. Messages

include notes, warnings, and errors.
NoteA purely informational message; requires no action, and the system continues
with normal operation. Notes are labeled ARNOTE in AR System.
WarningA message that warns you of facts you need to know, but that are
acceptable to the system. You can take action in response to this message, but the system
continues with normal operation. Warnings are labeled ARWARN in AR System.
ErrorA message that indicates a failure. You must correct the cause of this message
to perform the attempted operation; the system does not perform the current operation.
Errors are labeled ARERR in AR System.
AR System documents
The following table lists documentation available for AR System 7.6.04.
Unless otherwise noted, online documentation in Adobe Acrobat (PDF) format is
available on AR System product installation DVDs, on the Customer Support
website (http://www.bmc.com/support), or both.
You can access product help through each products Help menu or by clicking
Help links.
NOTE
The AR System product help has not been updated for version 7.6.04. The help
topics still apply to version 7.6.03. For the most recent content, refer to the PDF
documentation.
Title
Description
1
Audience
Concepts Guide
Overview of AR System architecture and features; includes Everyone

information about add-on products that extend AR System
functionality and a comprehensive glossary for the entire
AR System documentation set.
Installation Guide
Instructions for installing AR System.
Administrators
Introduction to Application
Development with BMC
Remedy Developer Studio
Information about the development of AR System

applications, including an introduction to using BMC
Remedy Administrator.
Developers2
Form and Application Objects Information about AR System applications and their user
Guide
interface components, including forms, fields, views,
menus, and images.
Workflow Objects Guide
Developers
Information about the AR System workflow objects (active Developers

links, filters, and escalations) and how to use them to create
processes that enforce business rules.
AR System documents
Title
Description
Audience
Configuration Guide
Information about configuring AR System servers and

clients, localizing, importing and exporting data, and
archiving data.
Administrators
BMC Remedy Mid Tier Guide Information about configuring the mid tier, setting up
applications for the mid tier, and using applications in
browsers.
Administrators
Integration Guide
Instructions for integrating AR System with external

Administrators/
systems by using web services, plug-ins, and other products, Developers/
including LDAP, OLE, and ARDBC.
Programmers3
Optimizing and
Troubleshooting Guide
Information about monitoring and maintaining AR System Administrators/

and AR System applications to optimize performance and Developers/
solve problems.
Programmers
Database Reference
Database administration topics and rules related to how

AR System interacts with specific databases; includes an
overview of the data dictionary tables.
Administrators/
Developers/
Programmers
BMC Remedy Distributed

Server Option Guide
Information about implementing a distributed AR System

server environment with BMC Remedy Distributed Server
Option (DSO).
Administrators
BMC Remedy Flashboards

Guide
Instructions for creating, modifying, and administering

Administrators/
flashboards to display and monitor AR System information. Developers
C API Reference
Information about AR System data structures, C API

function calls, and OLE support.
Programmers
C API Quick Reference
Quick reference to C API function calls.
Programmers
Java API
Programmers
Information about Oracle Java classes, methods, and
variables that integrate with AR System. For the location of
the JAR file containing this online documentation, see the
information about the Java API in the Integration Guide.
Java Plug-in API
Information about Java classes, methods, and variables used Programmers

to write plug-ins for AR System. For the location of the JAR
file containing this online documentation, see the
information about plug-ins in the Integration Guide.
BMC Remedy Email Engine

Guide
Instructions for configuring and using BMC Remedy Email Administrators

Engine.
Descriptions of AR System error messages.
Administrators/
Developers/
Programmers
Master Index
Combined index of all books.
Everyone
BMC Remedy Approval

Server Guide
Instructions for using BMC Remedy Approval Server to

automate approval and signature processes in your
organization.
Administrators
Release Notes
Information about new features, compatibility, and

international issues.
Everyone
Release Notes with Known

Issues
Information about new features, compatibility, international Everyone

issues, installation planning, and open issues.
BMC Remedy User Help
Instructions for using BMC Remedy User.
Everyone
Preface
Title
Description
Audience
BMC Remedy
Administrator Help
Instructions for using BMC Remedy Administrator to

develop AR System forms, workflow objects, and
applications.
Developers
BMC Remedy Import Help Instructions for using BMC Remedy Import.
Administrators
BMC Remedy Alert Help
Instructions for using BMC Remedy Alert.
Everyone
BMC Remedy Mid Tier

Configuration Tool Help
Instructions for configuring BMC Remedy Mid Tier.
Administrators
BMC Remedy Browser

Help
Instructions for using AR System forms in browsers.
Everyone

Outlines procedures for installing BMC Remedy
7.6.04 BMC Remedy Migrator Flashboards, setting options, and performing migration
Guide
tasks.
Administrators /
Developers

online help
Administrators /
Developers
Procedures for setting BMC Remedy Flashboards options

and performing migration tasks.
BMC Remedy Encryption

Provides an overview of the BMC Remedy Encryption
Administrators
Security 7.6.04 BMC Remedy Security products and explains how to install and configure
Encryption Security Guide
them.
1
The full title of each guide includes BMC Remedy Action Request System 7.6.04 (for
example, BMC Remedy Action Request System 7.6.04 Concepts Guide), except the
BMC Remedy Migrator Guide and BMC Remedy Encryption Security Guide.
2
Application developers who use BMC Remedy Administrator.
3
C and Java programmers who write plug-ins and clients for AR System.
10
Chapter
AR System diagnostic
messages
AR System includes diagnostic error and warning messages. Because error
checking is built into how AR System clients (for example, BMC Remedy User)
interact with the AR System server, you might see some of these messages only
with client applications that use the AR System API. When problems occur, the
system usually reports one or more error or warning messages. These messages
often provide information that helps you identify the cause of a problem. This
guide lists and describes the messages.
NOTE
An online version of all messages and descriptions is available in the Error
Messages form. See AR System Error Messages form on page 15.
Occasionally, it might not be clear from the messages how to correct a problem.
This chapter describes common problems and explains how to resolve them. If you
still cannot resolve a problem or if the problem is not covered in this chapter,
contact your Customer Support representative.
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
Message reporting
All interactive AR System tools (BMC Remedy User, BMC Remedy Developer
Studio, BMC Remedy Alert, and BMC Remedy Data Import) report errors directly
to the terminal. If a tool fails during startup, the error messages appear at the
command line from which the program was started.
NOTE
BMC Remedy User and BMC Remedy Mid Tier might display slightly different
error messages for the same problem. In BMC Remedy Mid Tier 7.5.00, a pure Java
qualification parser replaced the C-based qualification parser used in earlier
releases. Because of this change, the error messages cannot be synchronized.
Hence, you might find a few differences.
Server error reporting in UNIX

AR System daemons run in the background. These daemons are not associated
with a terminal and thus cannot report errors to a terminal. Instead, all AR System
daemon error messages are sent to the syslog daemon where, depending on your
system configuration, they are displayed or recorded. For more information about
the syslogd process and the syslog.conf file, see your operating system
reference manuals.
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.err. To receive these messages, configure your syslog
instance (using syslog.conf) to direct all messages of type user.err to one or
more locations that you define (for example, to direct all messages to the
console, specify the console device as /dev/console, or direct all messages to a
file by specifying a complete path name).
If a line in syslog.conf contains an entry of the form user.none, no messages

to class user are sent to the target on this line. Delete user.none or include a
separate line that explicitly locates user.err messages and sends them to a
target you specify.
For example, the following line specifies that all messages of the type user.err
intended for syslog are written to the /usr/ar/err.log file:
user.err/usr/ar/err.log
To start logging, add a line similar to the preceding line to the

/etc/syslog.conf file, and reset logging by sending a kill -1 signal to the
syslogd process to cause it to reread its configuration file.
AR System administrators can configure system logging options. For more

information, see the Configuration Guide.
All errors are also written to the arerror.log file in the ARServerInstallDir/db
directory. (See information about log files and debug modes in the Optimizing and
Troubleshooting Guide.)
12
Message catalogs in UNIX
Server error reporting in Windows

In Windows, AR Monitor sends server start and server stop messages to an event
log. To review the contents of the event log, open the group for Administrative
Tools. To open the Event Viewer Application Log window, click Event Viewer.
AR System messages have the Source column set to Remedy Action Request.
All error messages are also written to the arerror.log file in the
ARServerInstallDir\db directory. (See the discussion about log files and debug
modes in the Optimizing and Troubleshooting Guide.)
Message catalogs in UNIX

All messages returned by UNIX processes are stored in a message catalog. (All
messages returned by Windows processes are compiled into the software and are
not stored in an accessible catalog.)
This catalog is named arsystem.cat for AR System messages. The installation
process establishes a symbolic link in the default message catalog area to the
catalogs installed by the system.
By default, the message catalogs are stored in the following locations:
Table 1-1: Message catalog locations
Client Environment
Message Catalog Location
HP-UX and HP-UX Itanium
/usr/lib/nls/msg/%L/%N
IBM AIX
Oracle
Solaris
Linux
/usr/lib/nls/msg/en_US/%N
/usr/lib/locale/%L/LC_MESSAGES/%N
arSystemInstallPath/locale/%L
The path names contain these variables:
%L specifies the value of the LANG environment variable (C by default).
%N specifies the name of the message catalog.
For example, the following syntax specifies the AR System message catalog
location (assuming the default language environment) on Solaris:
/usr/lib/locale/C/LC_MESSAGES/arsystem.cat
On some systems, the directory holding the catalogs is mounted as read-only,

making it impossible to store a link to the message catalogs. You might want to
store the catalogs in another location. The catalog files are in the locale directory
under the AR System installation directory (by default, /usr/ar/locale).
Use the NLSPATH environment variable to place the catalogs in a directory other
than the default directory. For example, on Solaris, if the default catalog directory
is read-only, 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
13
NOTE
To ensure that catalogs for other products are still accessible, include the default
directory in the NLSPATH environment variable.
For more information about internationalizing message catalogs, see your
operating system documentation.
Message not in catalog

If you receive the following message, a process cannot access the message catalog:
Message not in catalog; Message number = messageNumber
Messages are returned by the server or the client. In general, messages with
numbers below 1000 are from the server, while messages 1000 or higher are from
the client. Errors above 10000 are defined by workflow (active links, filters, and
escalations) and might come from either the server or the client.
To troubleshoot this error
14
Ensure that the message catalogs exist, that they are in the appropriate directory,
and that the NLSPATH environment variable is set correctly on both the server
and the client.
Ensure that the setting of your LANG environment variable is set to the correct
language on both the server and the client. You can clear this variable, or you
can set it to the default value of C to cause the system to default to using the
English language catalog.
Ensure that the arsystem.cat file is readable by all. If you set up symbolic links,
each end of the link must be readable by all.

In addition to this guide, the AR System Error Messages form is available to search
for notes, warnings, and error messages. After installing AR System, use the
following procedure to import both the AR System Error Messages form and the
error message data.
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.def (UNIX)
2 Use BMC Remedy Data Import to import error message data from this file:
ARServerInstallDir\arserver\help\errars.arx (Windows)
ARServerInstallDir/help/errars.arx (UNIX)
The AR System Error Messages form is now ready for use. To search for
AR System error messages, including flashboards and notification error messages,
select AR System in the product list.
Localizing error messages

The AR System Message Catalog form enables administrators to provide localized
versions of error messages, Help text, menus, and other text strings that appear to
users in applications that are customized by locale. You can enable or disable the
use of this form and use this form in both UNIX and Windows environments. For
more information, see the Form and Application Objects Guide.
Because these error messages can be modified for localization, 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. The meaning of the message is still the
same, but the text might not match.
15
16
Chapter
AR System error messages
This chapter contains all the notes, warnings, and error messages in numerical
order for the client, server, and mid tier components of AR System. You can find
any message quickly by locating its number in Table 2-2.
Finding AR System messages (page 18)

AR System messages (page 19)
Chapter 2 AR System error messages
17
Finding AR System messages

This document includes only notes, warnings, and error messages used in
AR System. It is not backward-compatible with earlier versions of AR System and
thus does not include messages for obsolete features.
In this document, error messages are arranged in numerical order. In AR System,
error messages are classified according to the ranges in Table 2-1.
WARNING
Do not define custom error messages for your applications with numbers in these
ranges. If you do, they might be incompatible with future versions of AR System.
Table 2-1: AR System message ranges (Sheet 1 of 2)
Start
End
Product
Description
See
999
AR System server
Server messages and notifications
page 19
1000
1799
BMC Remedy User
BMC Remedy User errors, warnings, and notes
page 87
1800
1999
BMC Remedy User
BMC Remedy User errors
page 105
2000
2999
BMC Remedy
Administrator client
BMC Remedy Administrator errors and warnings

(release 7.1.00 and earlier only)
page 114
3000
3199
AR System server
BMC Remedy Distributed Server Option messages
page 162
3300
3349
AR System server
BMC Remedy Data Import event messages
page 167
3350
3379
AR System server
Report ARDBC plug-in messages
page 170
3380
3499
Reserved for AR System
page 171
3500
3999
4000
4499
BMC Remedy Flashboards Flashboards errors, warnings, and notes

BMC Remedy Data Import BMC Remedy Data Import errors, warnings, and
client (Windows)
notes
AR System application servers, including BMC
Remedy Approval Server
page 171
page 174
page 180
4500
4899
AR System application
servers
4900
4999
BMC Remedy Email Engine Email errors and warnings
page 187
5000
5399
BMC Remedy Developer

Studio
page 191
5400
5449
BMC Remedy Data Import BMC Remedy Data Import messages
page 213
5500
5999
BMC Remedy Developer

Studio
BMC Remedy Developer Studio messages
page 214
6000
6999
AR System clients
Errors for any AR System client, including BMC

Remedy User, BMC Remedy Developer Studio,
BMC Remedy Email Engine, and web tools
page 219
7000
7999
BMC Remedy
Administrator client
BMC Remedy Administrator errors and warnings

(release 7.1.00 and earlier only)
page 219
8000
9199
AR System server
Server messages
page 223
9200
9699
BMC Remedy Mid Tier
Mid tier messages
page 255
9700
9999
AR System server
Server messages
page 270
11000
11099
BMC Remedy Email Engine Email workflow messages
18
page 281
AR System messages
Table 2-1: AR System message ranges (Sheet 2 of 2)

Start
End
Product
Description
See
20000
20999
AR System server
Externally written plug-in messages
page 282
Reporting messages
page 282
140000 144999 AR System server
For information about BMC Remedy Migrator error messages, see Chapter 3,
BMC Remedy Migrator error messages.
AR System messages
AR System messages can take the form of errors, warnings, or notes. The tag ARERR
indicates that the condition is an error, ARWARN indicates a warning, and ARNOTE
indicates a note.
Table 2-2: AR System messages (Sheet 1 of 265)
Number
Description
AR System server messages and notifications

1
Message not in catalogmessage number = messageNumber.
Error
Text corresponding to that message number was not found.

The AR System server cannot find the message catalog file, which is arsystem.cat on UNIX
and is arcatalog_language.dll on Windows. The most common cause of this error is that
the path to the message catalog file is not correctly defined.
To resolve this problem:
For UNIX, see Message catalogs in UNIX on page 13, and follow the recommended steps to
configure the NLSPATH.
On Windows, the message catalog .dll file is installed in the same directory as the AR System
server. Make sure the ARSystemInstallDir is included in the PATH environment variable.
Note: If you get the text for other message numbers but not the one causing this error, then the
message catalog is accessible but does not include this error. In this case, check this document
for the message number and information. If the message number is not in this document,
contact Customer Support, and provide the message number and the circumstances that
prompted the message.
19

Number
Description
20
AR System server terminated when a signal/exception was received by the server.
Note
The error message includes the signal that was received.

(For UNIX) If the signal is 15, the AR System process was stopped due to a normal shut down
command. This signal indicates that the process terminated from a command to do so. If the signal
is not 15, AR System server terminated due to a system error.
If the shutdown signal is anything other than normal shutdown, the AR System server has failed
and the incident will generate stack output to the arerror.log file. To help resolve this
problem, contact BMC Remedy Support and provide the following information:
The arerror.log file that includes the time of the crash.

The armonitor.log file that includes the time of the crash. If other AR System processes
failed abnormally due to a shutdown of AR System server, or to a server crash, the
armonitor.log file will provide information about other processes that failed.
Note: Only those processes that are started with the AR System server by means of an entry in the
armonitor.conf file are included in armonitor.log output.
Any other AR System logs that cover the time of the crash.
The current version and patch level of the AR System server. 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.
21
AR System server terminated fatal error occurred in ARSERVER.
Note
A fatal error occurred in the arserverd process. Details about the error are in an associated
message. This generic message indicates that the error was fatal, and the process is shutting down.
22
Failure during open/write to the filter/escalation log file, logging to the log file is suspended.
Error
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). An associated message detailing the reason for
the failure appears with this message. Processing continues, but logging to the log file is
suspended until the problem is corrected (see error message 23).
23
Open/write to the filter/escalation log file resumed successfully.
Note
A failure was reported on an open or write action to the log file identified by Error 22. Additional
actions occurred to access this file, and the file is now accessible and can be written to. Any
operations between the message indicating a write failure (Error 22) and this message are not
included in the log file.
24
Failure while trying to run the filter/escalation process.
Error
An error occurred while AR System was executing a filter or escalation that runs a process. An
associated message provides details. Verify that the process definition is correct. If necessary,
correct the process definition in the filter or escalation.
25
Fields in set fields action do not exist in the target form.
Error
The filter or escalation being executed is trying to set values in fields that do not exist in the target
form. Fix the definition. Specify values only for fields that exist in the target form.
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.
26
Administrator operations are disabled on this server.
Error
The AR System server is configured to disallow administrator operations. If the server is part of a
group of servers sharing the same database, perform the server operations on the server in the
group that allows administrator operations.
20
AR System messages

Number
Description
27
This COPY of the Action Request System(R) does not have its authorization key set, but is
ready for use or evaluation. For unlimited capabilities, contact your sales representative.
Note
This version of BMC Remedy AR System has a maximum limit of 2000 requests per database
table, includes a maximum of three fixed licenses, and is configured for each client to access a
maximum of one server. To obtain a version of BMC Remedy AR System without these
limitations, contact your BMC sales representative, an authorized reseller, or visit
http://www.bmc.com.
28
Error
The demo license for this AR Server has expired. Please contact your distributor for license
information.
The demo license for the system on which you are trying to run the AR System server expired.
The system is now running in an unlicensed mode (see error message 27).
You must obtain a license to run AR System server in any mode other than evaluation mode.
29
The AR Server license is a Demo license that expires expirationDate.
Note
You are operating with a demo license, which expires on the specified date. Contact your
distributor for information about upgrading your license.
31
The new user was issued a fixed license of the following type: licenseType.
Note
You created a new user who is assigned a fixed license. A user was successfully created. 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, full text, or flashboards to indicate the type of fixed
license.
32
AR System server terminated normally.
Note
Server shut down without problems.
33
AR System failed to start a process. Make sure that your system is not low on resources.
Error
AR System failed to start a process. Make sure that your system has no resource problems that
prevent new processes from starting.
34
Error while opening the AR System server lock file.
Error
AR System server (arserverd, arservdsd, or arservftd) opens a lock file named ar.lck at
start-up, and ar.lck.rpcNum (ar.lck.390601 for arservdsd and ar.lck.390602 for
arservftd) for servers on alternate RPC sockets. These files are used to prevent multiple copies
of the AR System processes from being started on a single RPC socket simultaneously. An
associated file system error message supplies more details. Fix the problem, and rerun the server.
35
Another copy of the server is already running on the same RPC socket.
Error
Only one instance of AR System server can be run (on a specific RPC socket) on a computer at a
time. If a server is already running in this RPC socket, no action is required.
If the server is not running, you probably encountered a known problem with the NFS lock
manager on Oracle workstations. At times, the lock manager keeps a lock active even when the
process holding the lock is no longer running. If no arserverd process is running, free the lock
by deleting the lock file. Start the arserverd process after removing this file.
36
The database is not the expected version (may need to run upgrade program).
Error
AR System server (arserverd) expects a different version of the AR System database from the
version being referenced. AR System server cannot run against an unknown version of
AR System database.
21

Number
Description
37
Error while accessing one of the debug trace files. Debug tracing to the file is disabled.
Error
The system debugging mode was activated, and the system cannot access one of the debugging
trace flags. The associated message provides details. To correct the problem, see the message. The
system continues to run, but debug tracing to the file is disabled.
38
Filter/escalation set field process returned an error. The current transaction is rejected. No
update to the database occurred.
Error
A filter or escalation was performing a Set Fields action using the option to run a process and
return a value, but the process returned an error message. The text of the message returned
appears with this error. The error terminates the operation being performed, and the current
transaction is rejected. No update to the database occurs.
39
Filter/escalation set field process timed out before completion.
Error
A filter or escalation was performing a Set Fields action using the option to run a process and
return a value, but the process was not completed within the time-out interval specified for filter
processes.
The administrator has control over the timeout setting for the process. It can be configured, in
BMC Remedy Developer Studio, to be from one to 20 seconds with a default of five seconds.
41
Unrecognized command line argument ignoring command line and continuing.
Warning
The command-line argument displayed on the following line is not a legal command-line
argument for AR System server. The command-line argument is ignored and processing
continues.
42
Server not licensed to run with multiple-RPC sockets ignoring setting and continuing.
Warning
The server is configured to run multiple queues, but you do not have a multiple server license.
The RPC socket setting is being ignored, and processing continues.
43
Unable to retrieve the menu for character field "field name".
Error
A $MENU$ pattern is specified for a field with a character menu, and the server is encountering an
error while building the menu to verify the value against. 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. The server restricts access
locally to the same server process for performance and consistency reasons. You cannot use a
$MENU$ pattern verification for a remote search.
The menu is built from a search against a local form, but the search is encountering an error
during retrieval.
The menu is built from a file, and the file cannot be found.
The menu is built using a direct SQL command against another server. The server restricts
access locally to the same server process for performance and consistency reasons. You cannot
use a $MENU$ pattern verification for a remote SQL command.
The menu is built using direct SQL against a local database, but the command is encountering
an error during retrieval.
44
You have exceeded the maximum number of forms allowed under the current server license.
Error
The AR System server you are running against has a limited license. You are allowed to create
only a specified number of forms, and you are at that limit. Remove one or more of the existing
forms before you create a form.
22
AR System messages

Number
Description
46
Message action and Log action in else branch are not supported for escalations.
Error
You created an escalation and specified one or more message type actions or one or more log
actions in the else branch. Escalations do not have a message type action and do not support log
or set field in the else branch. Change the definition to eliminate the message type actions, and use
log actions in the action list only.
47
Email notification operation timed out before completion.
Warning
The system was blocked while trying to send a notification through email. To prevent the
arserverd process from hanging while waiting for the mail system, the process waits for 20
seconds. If arserverd receives no response, the process disconnects from the mail system and
issues this error.
The mail will probably be delivered when the mail system recovers.
48
Insufficient space for the response to be returned (minimum of 4,096 bytes).
Error
An internal RPC failure occurred. A client is accessing the server and has specified insufficient
space for the response to be returned.
49
Internal error: The request ID is invalid.
Error
An internal RPC failure occurred. A client is accessing the server and has specified an invalid
identifier for the requested information.
50
You have no permission to this field.
Warning
The field is accessible only to administrators. No permission settings were specified to allow
access to other users. This is expected if you are restricting access to the field. However, if you
want other users to access and manipulate this field, you must assign permissions to the field.
51
Field ID specified does not exist in this form.
Warning
A retrieval operation was attempted for the field identified by the indicated ID, but the target form
has no field with that ID. The data for the correctly identified fields was retrieved.
52
The field is a core system field and cannot be changed.
Warning
You tried to modify the contents of a core system field (Request ID, Create Date, Last Modified
By, Last Modified Date, or Status History). These fields are managed by AR System and cannot be
changed.
53
Administrator access required to get permission information.
Warning
You requested permission information about a field. Only a user with administrator access can
retrieve permission information. No permission information is returned, but all other requested
information is retrieved.
54
No changes have been specified for the update operation.
Warning
You specified a Modify operation to the system, but no modifications were specified. If the
command is being executed programmatically and set operations with no changes might be
specified, this warning can be trapped and ignored in your program.
55
The following item was not imported: item.
Warning
You tried to import one or more items (forms, filters, active links, escalations, or character menus)
to the current server. The listed item was not successfully imported. An associated message
indicates why the item was not imported. Fix the problem, and try to reimport the item.
56
Entry does not exist on form.
Warning
You tried to retrieve a request that does not exist. If this message is received when retrieving an
item that was reported in a preceding retrieval, the item might have been deleted by another user.
23

Number
Description
57
One or more fields in the statistic operation had a NULL value. Those values are excluded from
the statistics computation.
Warning
The requested statistical operation found one or more NULL values in the fields that were being
used for the calculation. Because NULL fields contain no meaningful data for the calculation being
performed, only those fields that contain non-NULL values are included in the computation.
59
Your login failed, but connected as a guest user.
Warning
You tried to log in with a user name that AR System did not recognize. AR System allowed you
to log in, but only as a guest user.
If you think the login name exists, verify spelling and capitalization to continue. Enter the login
name correctly (including case).
If the login name does not exist, ask the administrator to add the user as a valid login name to the
system.
60
You do not have read access to field.
Warning
You tried to access a field to which you do not have read access. If access to this field is required,
ask the administrator to extend your permissions to include this field.
61
You do not have read access to this field on this record.
Warning
You tried to access a field to which you do not have read access for the current AR System request.
If access to this field on this request is required, ask the administrator to include read access to this
field.
This message is issued (instead of Warning 60) when you may have access to this field on some
requests, such as when you are the Submitter or Assignee, or are a member of the Assignee Group
of the specific case.
62
You do not have access to the requested record.
Warning
You tried to access a request to which you do not have access. If access to this request is required,
ask the administrator to grant access to you.
This error results when you do not have access to the Request ID field (the unique key given to
each request in the system).
63
Warning
One or more values in the statistic operation cannot be retrieved due to permission restrictions.
Those values are excluded from the statistics computation.
You tried to perform a statistical operation that included values from fields that you are not
allowed to access. AR System completed the statistical operation, but the inaccessible values were
not included in the results. If it is necessary that those values be included in the computation, ask
the administrator to extend your permissions to include the fields.
64
Warning
The filter/escalation action cannot write to the specified log file action created but not
logged in the log file.
You created a filter or escalation action that logs to a file. The action was created, but the file you
specified does not exist and cannot be created. An associated message provides details. The action
does not perform an operation until the file system error is corrected. When the log file is created,
the action logs transactions.
65
Warning
Multiple form links are not supported in new filter definition syntax. Only the first link is
loaded.
The filter definition uses an older syntax in which filters could be linked to multiple forms. The
new definition allows only a single form link. The filter is loaded, but only with access to the first
form in the list of forms. Ask the administrator to restructure the filter definition to see a single
form. If you need filters with the same actions, create multiple filters.
24
AR System messages

Number
Description
66
The query matched more than the maximum number of entries specified for retrieval.
Warning
The retrieval included a search that selected more than the maximum number of items allowed
by the client or server. The call returned the number of entries specified as the maximum. Narrow
your search criteria or change the limit in user preferences.
To change the local setting in BMC Remedy User, choose Tools > Options > Behaviors, and modify
the settings for Limit Number of Items Returned. Only an administrator can change the server
settings.
67
Not able to open the menu.
Warning
The file associated with the menu is not accessible.
68
RPC environment variable is out of legal range (390600, 390603, 390619 - 390669, 390680 390694). NOTE: The value 390603 and the range 390619 - 390669 are specialty servers and may
have restricted functionality.
Warning
The value of the ARRPC environment variable is not a legal value. To use the default RPC socket,
clear this variable. To use the ARRPC environment variable, this value must be 390600 (the admin
daemon), 390603 (the escalation daemon), 390619 (the flashboard daemon), 390620 through
390634 (fast daemon), 390635 through 390669 (list daemon), or 390680 through 390694 (private
daemon).
The environment variable is being ignored, and processing continues.
69
Warning
Creation of one of the SQL views for the form failed within the SQL database. Form is created
successfully, but the SQL view is not in place.
While trying to create the SQL view for this form, the system encountered the associated SQL
error. This error prevented the creation of the SQL view. The table definition and the structure
needed by AR System server is complete and in place. Only the SQL view for this form is not in
place.
The definition of the form and associated fields are complete and in place. You can access the form
and continue with operation of the system. The only missing information is a SQL view for this
form, which is needed only if you directly access the SQL database by using the SQL view.
70
The character menu referenced by one or more fields in this form does not exist.
Warning
The character menu referenced by one or more fields in this form does not exist. No character
menu exists for the field, even though the system has a menu defined for it.
71
Only the Administrator has access to this active link.
Warning
The active link is accessible only to Administrators. No permission settings were specified to
allow access by other users. This is correct if you are restricting access to the active link. However,
if you want other users to perform this active link, administrators must assign permissions to the
active link.
72
The query matched more than the maximum number of entries specified by the server.
Warning
The retrieval being performed included a search that selected more than the maximum number
of items specified by the server. This number is less than the maximum specified by the server for
this call. The call returned the number of entries specified as the maximum by the server.
73
A change to the Submitter mode setting does not take effect until AR System is shut down and
restarted. It is a pending change until the next restart.
Warning
A change to the Submitter mode setting does not take effect until AR System is shut down and
restarted. It is a pending change until the next restart.
25

Number
Description
74
A duplicate index has been specified duplicate was omitted.
Warning
You specified the same index twice for a form. You cannot create duplicate indexes. This message
is a warning about the duplicate, but processing was completed with the index created only once.
AR System automatically creates a unique index on the Request ID field. Although this index does
not show in the list of indexes, it is on every form. You receive this error if you try to create an
index that contains only the Request ID field.
75
Warning
No floating write license tokens are available. Currently accessing the system in read-only
mode. License will upgrade when one is available.
You are assigned a floating write license, but no floating write license tokens are available at this
time. You are allowed access to the database for read-only use. The system will try to upgrade
your license type when a token is available.
76
A write token has become available and has been allocated to you access has been upgraded
to write access.
Note
You previously received Warning 75. A floating write token became available, and it is allocated
to you. You now have full read and write access within your permissions.
77
Warning
No free floating full text license tokens are available. Currently accessing the system without
full text search capability. License will upgrade when one is available.
You are assigned a floating Full Text Search Option license, but no floating Full Text Search
Option tokens are available at this time. You are allowed access to the database but without access
to the full text search (FTS) engine. The system will try to upgrade your license type when a token
is available.
The system uses the default database search capability on all fields, including the fields that are
FTS indexed.
78
A full text token has become available and has been allocated to you access has been
upgraded to allow full text searching.
Note
You previously received warning 77 indicating you could not get a Full Text Search Option license
token, but you were allowed to access the system by using the default database search strategy. A
floating Full Text Search Option license token became available, and it was allocated to you. You
now have full text search (FTS) access within your permissions.
79
Request for unique setting on database index has been ignored for fields of this type.
Warning
A unique index was requested for a field type that does not allow unique indexes, such as a
currency field. Request a unique index only for field types that allow it.
80
Delete field failed field contents set to NULL and field renamed.
Warning
You tried to delete a field from a form. The delete operation failed. Details are displayed in an
associated message. The system performed the next closest operation by logically deleting the
column, renaming it in the database to avoid naming conflicts, and setting all data values to NULL.
81
The field is a distributed server reserved field that can be updated only by the distributed
server process.
Warning
Some of the Distributed Server Option (DSO) reserved fields cannot be changed except by
arservdsd. An attempt was made to change one of those reserved fields.
26
AR System messages

Number
Description
82
A field with a length greater than 255 bytes cannot be in an index. To prevent an error, the field
was removed from the index definition.
Warning
A change to the limits definition of a field was made. The new limits cause the field length to
change from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is used in one or
more indexes for the current form. A field with a length greater than 255 bytes cannot be in an
index. To prevent an error, the field was removed from the index definition for the form, and the
remaining indexes were rebuilt.
83
Warning
A field with a length greater than 255 bytes cannot be in a result list. To prevent an error, the
field was removed from the result list.
change from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is in the list of
fields to be returned in the results list. A field with a length greater than 255 bytes cannot be in the
results list. To prevent an error, the field was removed from the results list definition.
84
Warning
A field with a length greater than 255 bytes cannot be in a sort list. To prevent an error, the field
was removed from the sort list.
change from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is in the sort list.
A field with a length greater than 255 bytes cannot be in the sort list. To prevent an error, the field
was removed from the sort list definition.
85
You cannot create indexes on a join form. To index a field, define the index on the base form.
Warning
You cannot create indexes on a join form. To index a field, define the index on the base form.
27

Number
Description
90
Cannot establish a network connection to the AR System server.
Error
The AR System server is inaccessible from the client computer where the error occurred. To
resolve this problem, 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 configuration is correct, check the network connectivity from the computer where the
error is reported.
Is the error reported to a group of computers or users or systemwide? If so:
Check the network connectivity from a computer where the error is reported.
Make sure the AR System server process is running.
Check the client computers configuration
To verify that the server is registered for client access, review the etc/ar file (utilities or other
server components) or the Login > Accounts dialog box (Windows clients).
If no entry is in the ar file or the server is not marked with a green check mark in the Accounts
dialog box, add the entry or (on Windows) select it.
Make sure the server name is spelled correctly in the ar file or the Accounts list in the Windows
client Login dialog box.
If access to the server requires a TCP port (for example, the server is behind a firewall or is not
using the portmapper), make sure the correct TCP port is included in the entry.
If the error was reported in BMC Remedy User, exit and restart BMC Remedy User. The server
might have been temporarily inaccessible.
Check the network connectivity
At a command prompt on a computer where the error is reported, issue a ping command to
the server. If the ping command does not return a successful reply, a problem exists with the
network connection to the AR System server.
You might need to test the connection to the server using its short name (for example,
serverName), its fully qualified domain name (serverName.domainName.com), and its IP
address (for example, nnn.nnn.nnn.nnn).
If necessary, work with a network administrator to resolve the problem.
Check the server process
Use operating system tools to make sure that the server process (arserverd or
arserver.exe) is running.
When the AR System server starts up, error 90 can appear while the server is loading
information into the cache. In this case, the server process is running. If this occurs:
(UNIX) Check the arforkd process. If it is running, the server has finished loading the cache.
(Windows) To determine whether the server port is assigned, use NETSTAT -a. The port is
set when the cache load is completed.
(UNIX and Windows) Review the arerror.log and armonitor.log files. If the server
failed during startup, errors reporting that the server terminated are in these logs.
If the AR System server is not running, restart it.
Check the UNIX server hosts file
28
If the server is configured to use a portmapper (TCP port = 0), make sure the localhost line
in the /etc/hosts file is above the hostName line. For example:
127.0.0.1
localhost
100.100.100.100
TestServer
AR System messages

Number
Description
91
RPC call failed.
Error
AR System clients use the RPC layer to connect to the AR System servers TCP port. This error
occurs when an RPC call fails. Causes of this error include but are not limited to
An invalid RPC packet was detected

(UNIX) The AR System server is low on file descriptors
On UNIX, the number of file descriptors allocated to the AR System server is determined by an
operating system setting in the shell where the server was started. If thread logging is on when
the AR System server starts, the number of file descriptors appears in the thread log. For example:
Limits found: current rlimit=8192
max rlimit=8192
BMC recommends a minimum file descriptor setting of 2048 or 2.5 to 4 times the number of
concurrent users, whichever is greater. Concurrent users include other server tier components
such a Email Engine, DSO, and custom API programs. To ensure that adequate file descriptors are
available in recent releases of AR System, running with file descriptors set to 8192 on UNIX is not
uncommon.
On Windows, the default setting of 10,000 file handles is generally sufficient. To see whether a
process is using a large number of handles, check Windows Task Manager.
If this is a recurring error and increasing the file descriptors or file handles for the AR System
server does not resolve it, turn on ARAPILOGGING for the client that receives the error to isolate
the API call that is failing with ARERR 91. For information about client-side API logging, see the
Optimizing and Troubleshooting Guide.
A less common cause of this error is running an API program that is incompatible with the
AR System server. In this case, recompiling the API program with the same API version used by
the AR System server might resolve the error.
92
Error
Timeout during database update the operation has been accepted by the server and will
usually complete successfully.
A time-out occurred while data or structures in the database were being updated. In most cases,
the operation is performed after the time-out. Verify that the updates were made, and retry the
operation if necessary. Because this error occurs on update, it can be associated with a filter action.
If this error recurs, use ARAPILOGGING and client workflow logging to identify the API call and
SQL statements associated with the error. If you contact Customer Support for assistance, provide
the filter, API, and SQL logs containing these SQL statements. (For logging information, see the
Optimizing and Troubleshooting Guide.)
Ask your database administrator to review the performance of the database. The performance of
the AR System server during database updates depends on the performance of the database. BMC
strongly recommends that AR System administrators work closely with database administrators
to ensure optimum database tuning.
29

Number
Description
93
Timeout during data retrieval due to busy server retry the operation.
Error
A time-out occurred during a retrieval operation because the server or database was busy
performing other operations. Causes include low system resources, such as CPU time, or server
resources, such as thread congestion.
To troubleshoot this error, first determine whether the time-out error is isolated to an operation
(for example, saving a form), a user, or a group of users or is reported systemwide. If the error is
isolated to an operation, a user, or a group of users, use client-side logging, including
ARAPILOGGING, along with server API and SQL logging to capture the API call associated with
error 93. The failed API call is marked in the log with a FAIL status. For example, this entry is for
an ARGetServerInfo call with a time-out error:
*/+GSI ARGetServerInfo -- as user . . .
*/-GSI FAIL -- RPC Client has timed out
For more information about logging, see the Optimizing and Troubleshooting Guide.
When contacting Customer Support for assistance, provide at least the following information:
94
Error
The server API and SQL logs that capture the time when ARERR 93 occurred.
If the error is isolated to an operation or user, provide the client workflow logging with API,
database, filter, active link, and macro output captured.
A copy of the server ar.conf or ar.cfg file.
AR System server environment information:
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.
Timeout during database query consider using more specific search criteria to narrow the
results, and retry the operation.
A time-out occurred while data was being retrieved from the server during an ARGetList call
(ARGetListEntry, ARGetListEntryWithFields, and so on). This can be caused by poorly
specified search criteria or by the database being too busy to respond within the time-out period.
If the error is reproducible, use client-side ARAPILOGGING to isolate the API call that fails with
ARERR 94. Then use the information in the client-side API log to isolate the API and SQL SELECT
statement associated with the error in the client workflow log or in the server API and SQL logs.
This error is often associated with a query to a form when a large number of records is returned.
You can resolve this error by modifying the search to return fewer records. If the error occurs
during a workflow search, you might need to modify the workflow actions or adjust the server
settings to return fewer records.
Ask your database administrator for help, and review performance of the database. The
performance of the AR System server during database updates depends on the performance of
the database. BMC strongly recommends that AR System administrators work closely with
database support to ensure optimum database tuning.
To check the database response time for the AR System API call that generates this error, run the
SELECT statement captured in the SQL log. To do so, log in at the database prompt as the database
owner of the AR System server in the environment where the server is running. To more
accurately gauge the time, run the statement from the command line, not from a database tool.
30
AR System messages

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

Number
Description
107
Type of statistical operation is not specified.
Error
The list of operations to perform in this statistical operation is NULL or empty. Specify a list of one
or more operations.
108
Field display definition is incorrect.
Error
One or more of the fields in the display structure for the field are invalid. You might have
specified an illegal display type, label positioning, or option. Verify that the include file ar.h has
legal values for these fields.
109
Filename is longer than maximum allowed filename.
Error
The file name you specified is longer than the maximum file name allowed by the system
(AR_MAX_FULL_FILENAME, 255 characters). Make sure that the file name you specified is a legal
name. Remember that character strings must be terminated by a 0 (zero) character.
110
Incorrect data type value for this parameter.
Error
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.h have legal values for this
field.
111
Incorrect data type value for this data type field.
Error
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. Verify that the #define
statements in the include file ar.h have legal values for this field.
112
Character menu definition is empty.
Error
The structure you specified for defining the character menu for a field is either NULL or empty. If
you are defining a character menu, you must supply a menu definition in this parameter.
113
Name list parameter is empty.
Error
In a field operation, the list containing the selection values for a selection type field is NULL or
empty. A selection field must contain one or more legal values.
114
One or more values in the names list is invalid.
Error
During processing of a list of names (such as selection value names), one or more of the values
was invalid. An associated message describes the problem. This error relates the associated error
to the name list instead of to another parameter in the call.
115
Operation mask parameter is out of bounds.
Error
The filter operation set parameter is invalid. This parameter is a mask of one or more operations
on which the filter might execute. This parameter either has an empty mask or has values outside
the limits on the mask. Verify that the #define statements in the include file ar.h have legal
values for this field.
116
Filter does not have an action defined.
Error
The action field for a filter is either NULL or empty. A filter must define at least one action.
117
Command string is empty or longer than the maximum allowed length.
Error
The command string that issues an external command to the operating system is empty or is too
long. If empty, you must supply a command. If too long, you must reduce the command to the
maximum length allowed (AR_MAX_COMMAND_SIZE, 255 characters).
Note that if the command being created is in an active link, filter, or escalation, the command
string might contain parameters. When they are expanded, the command line might expand to
4,096 bytes. The unexpanded line is limited by the value defined by AR_MAX_COMMAND_SIZE.
32
AR System messages

Number
Description
118
Unrecognized or inappropriate value for field option.
Error
The value you specified for the field option parameter is not one of the legal values recognized by
the system or is inappropriate for usage in this case. Verify that the #define statements in the
include file ar.h have legal values for this field. This message can result from a change to the
display optioneither setting it or removing itwhere this is not allowed. For example, if you
create a trim or a control field, you must set the option to AR_FIELD-OPTION_DISPLAY.
119
Unrecognized create mode.
Error
The value you specified for the create mode parameter is not one of the legal values recognized
by the system. Verify that the #define statements in the include file ar.h have legal values for
this field.
120
Unsupported datatype in this client.
Error
AR System server is a newer version than your client software. Your client is too old to display
one or more fields on this form. Install an updated client, and retry this request.
121
Invalid entry in the Entry ID list.
Error
During processing of a list of request IDs, one or more of the values was invalid. An associated
message describes the problem. This error connects the associated error to the ID list instead of to
another parameter in the call.
122
The value for the list of information to retrieve from the server is empty.
Error
The value you specified for the list of information to retrieve from the server was NULL or empty.
To retrieve information, specify what information you are trying to retrieve.
123
Unrecognized server information tag.
Error
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.
124
One of the items specified in the field or value list contains an error.
Error
One of the items specified in the field or value list contains an error. An associated error message
contains details.
125
One of the entries specified in the statistics operation list is invalid.
Error
One of the entries specified in the statistics operation list is invalid. An associated error message
contains details.
126
One of the statistical operation codes is not recognized.
Error
One of the statistical operation codes is not recognized. Verify that the #define statements in the
include file ar.h have a list of all valid operation codes.
127
One of the items in the permission list is invalid.
Error
One of the items in the permission list is invalid. An associated error message contains details.
128
One of the permission tags is not recognized.
Error
One of the permission tags is not recognized. Verify that the #define statements in the include
file ar.h have a list of the valid permission tags.
129
Field limit definition is invalid.
Error
The field limit specified for this field is invalid.
For a numeric field, the high range must be greater than the low range.
For a character field, the pattern must be within the size limit of the field. Verify that the
specified character menu, the menu style setting, and the match operation setting are legal.
For a selection field, the value must be a legal value for the field.
33

Number
Description
130
One of the entries in the character menu is invalid.
Error
One of the entries in the character menu is invalid. Either a child menu tag was assigned but no
child menu exists, or a leaf item was specified but no leaf string exists.
131
One of the character menu type tags is not recognized.
Error
One of the character menu type tags is not recognized. Verify that the #define statements in the
include file ar.h have a list of all valid character menu type tags.
132
The list parameter is an empty list.
Error
The structure list parameter is NULL or is an empty list. To perform a structure operation, you
must have a list of the options to get or set.
133
The list parameter is an invalid list.
Error
One of the structure option tags is invalid. Verify that the #define statements in the include file
ar.h have a list of all valid structure tags.
134
One of the items specified in the list is invalid.
Error
One of the items specified in the structure list is invalid. An associated error message contains
details.
135
One of the filter action codes was not recognized.
Error
One of the filter action codes was not recognized. Verify that the #define statements in the
include file ar.h have a list of all filter action type tags.
136
The code specified for the notify mechanism in one of the filter actions is invalid.
Error
The code specified for the notify mechanism in one of the filter actions is invalid. Verify that the
#define statements in the include file ar.h have a list of all allowed notify mechanisms.
137
Invalid message type.
Error
The code for the type of error message to return is invalid. Verify that the #define statements in
the include file ar.h have a list of all valid message types.
138
Filter/active link/escalation message number must be greater than 10000.
Error
The message number of a message you define through the Message action of a filter, active link,
or escalation must be greater than 10000. Numbers less than 10000 are reserved for AR System.
Restrict your errors to values greater than 10000 to avoid conflicts between errors you add to the
system and errors from AR System.
139
Option cannot be changed for a core or reserved field with a fixed options definition.
Error
The core fields of the system have restrictions on what changes are allowed. You are trying to
change a characteristic of a core or reserved field that cannot be changed in the way you are
requesting. Review the Form and Application Objects Guide for information about the restrictions
for each of the core fields.
140
The Status field must have a default value.
Error
The Status field must have a default value. You are trying to change the definition of the Status
field, which eliminates the default value and is not allowed. You can alter the number of states
and change the default value, but you cannot eliminate it.
141
The Qualify None option can only be used at the top level of a qualification.
Error
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. This tag indicates no qualification.
Restructure the call to remove the tag from the middle of the tree.
34
AR System messages

Number
Description
142
The tag for one of the nodes in the qualify condition structure is invalid.
Error
The tag for one of the nodes in the qualify condition structure is invalid. Verify that the #define
statements in the include file ar.h have a list of all valid tags.
143
The value portion of a relational operator qualification structure is NULL.
Error
The value portion of a relational operator qualification structure is NULL. Specify a value for a
relational operation.
144
The tag for the relational operation is invalid.
Error
The tag for the relational operation to perform is invalid. Verify that the #define statements in
the include file ar.h have a list of all valid tags.
145
The value portion of an arithmetic operator qualification structure is NULL.
Error
The value portion of an arithmetic operator qualification structure is NULL. Specify information
for an arithmetic operation.
146
The tag specified for the arithmetic operation is invalid.
Error
The tag specified for the arithmetic operation is invalid. Verify that the #define statements in
the include file ar.h have a list of the valid tags.
147
The value portion of a field, value, or arithmetic operation is empty.
Error
The value portion of a field, value, or arithmetic structure is NULL. Specify information for this
structure.
148
The tag for the type of the field, value, or arithmetic operation is invalid.
Error
The tag for the type of the field, value, or arithmetic value is invalid. Verify that the #define
statements in the include file ar.h have a list of all valid tags.
149
A user name must be supplied in the control record.
Error
The name field of the ARControlStruct parameter is empty. Supply the name of an AR System
user in this field.
150
A server name must be supplied in the control record.
Error
The server field of the ARControlStruct parameter is empty. Supply the name of the server to
reference in this field.
151
Required form parameter is missing.
Error
The form parameter is required, but the value passed is either NULL or an empty string. Load this
parameter with the name of the form you want to reference.
152
The value specified for the sort list parameter is invalid.
Error
The value specified for the sort list parameter is invalid. An associated error message provides
details.
153
The specified sort method is invalid on one of the entries in the sort list.
Error
The code for the specified sort method is invalid on one of the entries in the sort list. View the
#define statements in the include file ar.h for a list of the valid codes.
154
The system encountered an error during a call to allocate memory space.
Error
The system encountered an error during a call to allocate memory space. The failure occurred on
the client during processing of the call to or from the server. This error usually occurs when too
many processes are running or some processes have grown to occupy most or all available
memory space on the client. To recover the memory space, shut down unneeded processes. To
recover space applications might have leaked over time, restart processes that have been running
for a while.
35

Number
Description
155
The buffer for holding the return value is not specified.
Error
The buffer that holds the return value of the call was passed a NULL value. For the call to return
the data requested, a parameter must be specified to hold a pointer to the result. Supply a value
for this parameter.
156
The buffer for holding the input value is not specified.
Error
The buffer to hold the input value to the call was passed a NULL value. For this call to perform the
requested operation, a value must be specified for this parameter. Supply a pointer to the input
buffer for this parameter.
157
Field IDs below 100 are reserved for core fields.
Error
You specified a field ID of less than 100 for a new field. IDs of less than 100 are reserved for
AR System. You cannot specify IDs in this range for fields you create. Perform the call again,
specifying a field ID greater than 100.
158
Entry ID field cannot exceed 10 characters.
Error
You requested a modification to the length of the Request ID field. This field is a character string
containing from 5 to 15 characters. You are allowed to specify a default value of from 0 to 10
characters that acts as a prefix to the generated IDs.
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. If you receive this error, the combination of the
length you specified for the field and the default value prefix leave less than 5 spaces.
159
A server name is not supplied.
Error
This message occurs while creating or adding a workflow action, such as Open Window, Call
Guide, or Service, and a server name is not specified. The workflow or user must supply the
correct server name.
This error can occur when the workflow uses a dynamic design (SAMPLE DATA data source) that
supplies the server name at run time. In this case, review the appropriate workflow logs and the
workflow configuration to determine the cause of the problem.
160
Data Decompression has failed.
Error
An attempt to decompress the data being processed failed, for example, when an attachment in
the Save-Attachment Run Process filter command was saved. The format of the compressed
data was not correct.
161
The session identifier in the control record is invalid.
Error
The session identifier in the control record is invalid. The session identifier is set in the control
record by the ARInitialization() function and is valid until a call to ARTermination() is
made.
162
Notify Text is empty or too long.
Error
The notify text you can specify for a notification is limited to 255 characters before expansion. The
text you specified is over that limit. You must correct your text string to 255 characters or less.
Character strings must be terminated by a \0 character.
163
The tag for the notify fields is invalid.
Error
The tag for the notify fields structure is invalid. View the #define statements in the include file
ar.h for a list of the valid tags.
165
The numItems value for a parameter was not set.
Error
A parameter was specified that contains a numItems value that indicates one or more items for
the parameter, but the value field in the structure is a NULL pointer. If items exist, the value field
must point to the items. If no items exist, the numItems field must be initialized to 0.
36
AR System messages

Number
Description
166
The data type specified does not match the field's data type.
Error
The data type specified as the default value for the field does not match the data type defined for
the field. The data type of the default value must be compatible with the data type of the field.
A default value of the same type as the field is always compatible.

A default value of AR_DATA_TYPE_NULL is always compatible with any data type.
A keyword value is compatible with the data type that matches the type of the resulting
keyword (for example, 12/25/01 is compatible with AR_DATA_TYPE_TIME, but not with
AR_DATA_TYPE_CHAR).
All other combinations are illegal.
167
The limit specified for the field does not match the field's data type.
Error
The data type specified in the limit for the field does not match the data type defined for the field.
The data type in the limit structure must be compatible with the data type of the field.
A default value of the same type as the field is always compatible.

A default value of AR_FIELD_LIMIT_NONE is always compatible with any data type. It
indicates that the field has no limit.
All other combinations are illegal.
168
One of the field/value assignments in the set filter/active link/escalation definition is invalid.
Error
An error occurred with one of the field or value assignments in the Set Fields action of a filter,
active link, or escalation definition. An associated message provides details. Usually, the problem
is an attempt to define an assignment between incompatible data types or to nonexistent fields.
169
Execution order value is out of range.
Error
The execution order field of the filter, active link, or escalation definition contains a value out of
range. The legal range for the execution order is 0 to 1000, with items at lower values being
performed before items at higher values.
170
Status history tag is invalid.
Error
The tag that specifies whether you want the user name or time stamp for a status history value is
not a recognized value. The only supported values for the tag field are AR_STAT_HISTORY_USER
and AR_STAT_HISTORY_TIME.
171
The specified status field value is out of range.
Error
The status field value you specified does not match a defined status for this form. The selection
value specified is a 0-based, positional index into the list of states defined for Status.
172
The required service is not available.
Error
The Windows Service was not started. 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. Consult the Application Event Log for details concerning any errors that
occurred.
173
Language specified in the control record not recognized using default on server.
Error
The language you specified for the system is not recognized by the server.
If you are coding directly to the API, the language field is in the control record passed to each call.
To use the default language, leave the language buffer empty (set to an empty string). You can
also set the language to the default language of C to use the standard language defaults. You can
set this value to any language your environment supports.
If you are running an AR System tool, the language to use is picked up from the LANG
environment variable. Verify the setting of that variable and correct it if it is wrong (or delete it if
the default language is sufficient).
37

Number
Description
174
Display type specified is incompatible for the data type.
Error
The display type value specified for this field is incompatible with the fields data type. 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,
AR_DATA_TYPE_REAL, AR_DATA_TYPE_CHAR, AR_DATA_TYPE_DIARY,
AR_DATA_TYPE_ENUM, and AR_DATA_TYPE_TIME.
175
The Number of Rows value of the display parameter is out of range.
Error
The length or numRows (number of rows) value for the display parameter is not within the
allowed range.
For fields displayed as TYPE_TEXT, neither the length nor NumRows field should be zero (0).
The length field specifies the width of the control, and the NumRows field specifies the number
of rows of data that are displayed for the field.
For fields displayed as TYPE_NUMTEXT, the length field must not be zero (0). The length
specifies the width of the control, and the number of rows value is ignored.
For fields displayed as TYPE_CHECKBOX or TYPE_CHOICE, the numRows field must not be zero
(0). The numRows field specifies how many rows the check boxes or choices must be displayed in,
and the length value is ignored.
176
Duplicate name in the selection list.
Error
In the list of selection or bitmask values, the same name is used for two separate states. Rename
one of the duplicate selection values so that each selection or bitmask value has a unique label.
177
Change permission cannot be given to a view-only group.
Error
You specified that a group must be given change access to a field; however, the group is a View
group and cannot be granted change permission. You can assign only view permission to the field
for this group.
178
Field ID cannot be empty, please provide an field id or enter 0 for the system to assign a value.
Error
The field ID parameter is a NULL pointer. It must be a pointer to a field ID. To assign the ID for a
field, load this parameter with the value. If you want the system to assign an ID, assign this field
to 0, and the system assigns a value and returns the result in this field.
179
Pattern in a character limit is invalid.
Error
The pattern specified for a limit to the character field is illegal. Typically, 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, [c-a]).
180
Specified length for a character type is longer than the maximum allowed length.
Error
The value specified as the default value for a character field is longer than the maximum allowed
by AR_MAX_DEFAULT_SIZE (256 bytes). Verify the default value, and retry the operation.
Character strings must be terminated by a 0 (zero) character.
181
The ID specified for this field is in the reserved field range.
Error
The ID for the specified field falls within the reserved range of field IDs. This is likely caused by
a programming error. An API call did not set the flag indicating that it allows creation of fields in
this range.
API calls must set that flag to allow the creation of a field with this ID. Alternatively, an API call
can set the flag to 0 to have the system generate a unique ID. The system returns the assigned ID.
38
AR System messages

Number
Description
182
Too many actions have been specified for this filter/active link/escalation.
Error
The filter, active link, or escalation has more actions defined than the maximum allowed by the
system (25). Reduce the number of actions by combining several action steps into one or by
creating a second filter, active link, or escalation and separating some of the actions into the new
filter, active link, or escalation.
183
Duplicate group ID was specified in permission list.
Error
You specified a group ID more than once in the permission list you are sending to the system. Any
given ID can be specified only once with the permissions allowed for that group field. Remove the
duplicate reference.
184
Quotation mark cannot be used in Entry ID field.
Error
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. Specify a default value that does not
contain a quotation mark character.
185
Cannot assign default value to system core or reserved fields (except Entry ID).
Error
You assigned a default value to a system-controlled AR System core field (Request ID, Create
Date, Last Modified by, Modified Date, or Status History field). The only system-controlled core
field that can have a default value assigned to it is the Request ID field, where the default is used
as a prefix to the ID. The other AR System system-controlled core fields are automatically updated
by the system, so no default value is needed or allowed.
186
Cannot assign character menu to system core or reserved fields.
Error
You assigned a character menu to a system-controlled AR System core field (Request ID, Create
Date, Last Modified By, Modified Date, or Status History field). The system-controlled core fields
cannot be assigned values by the user, so a character menu is not needed or allowed.
187
Execute mask parameter is out of bounds.
Error
The execute mask is a bitmask of the conditions under which an active link executes. The value
you specified includes bit settings outside the legal range of conditions under which you can
execute an 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.
188
On Return or On Menu choice condition does not have a Field specified.
Error
The active link you defined has the On Return or On Menu choice condition set in the execute
mask, but no setting indicates which field to attach the operation to. Specify the field where you
want to attach the active link action.
189
Active link does not have an action defined.
Error
The action field for an active link is either NULL or empty. An active link must define at least one
action to be performed.
190
Unrecognized active link action type.
Error
One of the active link action codes is not recognized. Verify that the #define statements in the
include file ar.h have a list of all active link action type tags.
191
Unrecognized assign type.
Error
The assign type tag is not recognized. Verify that the #define statements in the include file ar.h
have a list of all assign type tags.
192
Field/assignment list item is empty.
Error
The field or assignment list for an active link Set Fields action is either NULL or empty. A Set Fields
action must define at least one field to be assigned a value.
39

Number
Description
193
One or more fields, or assignment items in the field or assignment list, encountered an error.
Error
One or more fields, or assignment items in the field or assignment list, encountered an error. See
the associated message for details.
194
The ARAssignFieldStruct tag for filter/active link/escalation is not recognized.
Error
The ARAssignFieldStruct structure tag is not recognized. Verify that the #define
statements in the include file ar.h have a list of all ARAssignFieldStruct tags.
195
Filter/active link/escalation 'set field' definition is missing.
Error
The field definition in the field or assignment structure is set to NULL. Supply a field definition
value in this structure.
196
Macro branch of active link action must include both a name and macro text.
Error
The definition of a macro action must include both a name and the text of the macro to execute.
One or the other is either NULL or an empty string.
197
Unrecognized keyword.
Error
A keyword type value was specified, but the keyword identifier was not recognized. View the
#define statements in the include file ar.h for a list of IDs for all supported keywords.
198
Cannot use the $DEFAULT$ keyword as a default value or in a qualification.
Error
The keyword $DEFAULT$ cannot be used when specifying the default value for a field. The
$DEFAULT$ keyword indicates that the default value must be used for the value; using it as the
default itself creates a self-reference that cannot be resolved.
The keyword $DEFAULT$ cannot be used when specifying a qualification, whether in an active
link, filter, or escalation, or on the qualification bar. If an arithmetic operation is involved or the
operation is a complex one, it is not clear which fields default value is being referenced under all
conditions. Therefore, the $DEFAULT$ keyword is disallowed in qualifications.
199
Missing name for a macro parameter in the active link action.
Error
A name field in the list of macro parameters is either NULL or blank. When specifying macro
parameters, supply the parameter name for the value you are specifying. You can omit
parameters from the list of parameters, but if they are included on the list, you must provide a
name.
200
Macro value string is longer than the maximum allowed length.
Error
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, and retry the operation.
Character strings must be terminated by a \0 character.
201
Unrecognized or misused tag for field/value definition.
Error
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.
202
The name specified for the user to be notified is too long.
Error
The name specified for the user to be notified is too long (the maximum length is defined by
AR_MAX_NAME_SIZE, 30 bytes). Specify a name within the length restrictions.
203
Value list is empty.
Error
The value list parameter for this call is NULL or contains 0 items. This operation requires at least
one value item to be specified.
40
AR System messages

Number
Description
204
Notify priority is out of range (0 to 10).
Error
The value specified for the notification priority is outside the legal bounds for this field. Specify a
value between 1 and 10 for the priority, where 1 indicates the highest priority and 10 indicates the
lowest priority.
206
Unrecognized character menu type.
Error
The ARCharMenuStruct structure tag is not recognized. View the #define statements in the
include file ar.h for a list of the recognized ARCharMenuStruct tags.
207
Unrecognized character menu refresh code.
Error
The code for the refresh interval for the character menu is not one of the defined choices. View the
include file ar.h for a list of the valid codes.
208
Unrecognized character menu file location.
Error
The code for the location of the file for the character menu is not one of the defined choices. View
the include file ar.h for a list of the valid codes.
209
Filename for a character menu is empty, or too long.
Error
The file name for a character menu is a pointer to NULL, is an empty string, or is longer than the
maximum allowed length for a file-name. Define a legal file name for the character menu file.
210
Total length of all fields in an index is greater than the maximum length allowed.
Warning
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). Remove one or more fields from the index
definition to reduce the total length of the index information.
211
Incorrect number of allowed fields is specified in a single index.
Error
An index definition must reference from 1 to the number defined by AR_MAX_INDEX_FIELDS

(10). Your index definition specifies an index on no fields or an index on more than the maximum
allowed number of fields.
212
Display list is empty.
Error
If you receive this error when doing a field operation, the display list containing information
about the display definition for the field is NULL or empty. A field must define at least one display
definition.
213
Qualifier parameter is empty must be a pointer to memory.
Error
The qualifier parameter must be a pointer to memory. This memory location is where the base of
the qualifier structure for the string being parsed is stored.
214
One of the items in the display list of field definitions is invalid.
Error
One of the items in the list of field definitions is invalid. This list of field definitions is for fields
displayed in the query list. See the associated error message for details.
215
The total length of the results list is greater than the maximum allowed.
Error
216
ARServerInfoList is empty.
Error
The server information list is either NULL or empty. To set one or more pieces of server
information, the settings with their values must be specified.
217
Update to Server information associated with this tag is not allowed.
Error
The server information for the specified tag is read-only data. You are not allowed to update this
information. Retry the operation, setting only values that can be updated.
41

Number
Description
218
Server information associated with this tag cannot be viewed.
Error
The server information for the specified tag is write-only data. You are not allowed to view this
information. Retry the operation, requesting only values that can be retrieved (viewed).
219
Incorrect Server information data type.
Error
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, specifying the correct data
type for the value.
220
Local variable number is out of range (must be 0 to 10).
Error
The code specified for a local variable is outside the legal range for local variables. Specify a
number between 0 and 10.
221
Query value is empty.
Error
The query value structure pointer is NULL. To define an assignment to a value from another form,
specify a query value structure definition that defines the form and conditions on that form.
222
Query contains an error.
Error
One or more of the fields in the query definition of an assignment operation contains an error. See
the associated error message for details.
223
The action tag for multiple match is invalid.
Error
The tag specified for the action to take if multiple matches exist in the ARQueryValueStruct
structure is not a legal tag.
224
Cannot index a diary field, an unlimited length field, or a field with a maximum length over
255 bytes.
Error
Fields that have lengths longer than 255 bytes (including diary fields and unlimited length
character fields) cannot be indexed. You specified an index that includes a field that meets these
criteria. If the index is a multiple-field index, you can still create the index if you remove the field
that is not allowed.
225
Error
Set fields actions in a filter/escalation that reference entries in other forms can only reference
forms on the same server.
A Set Fields action in a filter or escalation can reference other forms for pulling data to the current
request. However, the referenced form must be on the same server. You defined a reference to a
form on a different server. Choose another operation (for example, perform the operation in an
active link), or move the remote form to the server where the filter or escalation is being defined.
226
Type of field, value, or arithmetic operation is not supported on the GetListEntry operation.
Error
The type of value specified in the ARFieldValueOrArithStruct structure is not allowed in a

query list. The tag refers to an operation supported only during a filter or active link operation.
227
Unrecognized value for set focus characteristic.
Error
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. View the include file ar.h for a list of the valid codes.
228
Unrecognized value for set access option characteristic.
Error
The code for the set access option field, of the Set Fields characteristics action of a filter, is not one
of the defined choices. View the include file ar.h for a list of the valid codes.
229
Function to be performed is not defined.
Error
The function structure pointer is NULL. To define an assignment to a function result, specify a
function definition that defines which function is to be performed and that provides the
parameters to perform the function.
42
AR System messages

Number
Description
230
The specified function code is invalid.
Error
A function was defined, but the function code was not recognized. View the #define statements
in the include file ar.h for a list of valid function codes.
231
Parameter list for a function is empty.
Error
The parameter list for a function is NULL, but the number of items indicates one or more
parameters. If the number of items indicates parameters, the parameter list must contain the
parameter values. If no parameters exist, the parameter list can be NULL, but the count of
parameters must be set to 0.
232
Incompatible value types in a value list.
Error
The data types of the values in a value set are incompatible. All types must be the same or
compatible types.
233
Invalid parameter setting in function definition.
Error
In a Set Fields action for a filter, active link, or escalation, one of the settings assigned the result of
a function. A function definition that was specified has an error with the specified parameters.
Either the wrong number of parameters was specified, or one or more of the parameters is the
wrong data type. View the definition of the function to verify the parameters.
The ID of the field that the function is associated with is reported.
234
Error
Value specified for the filter/escalation 'set fields' process timeout exceeds the range of 1 to
60 seconds.
The filter Set Fields process time-out value is not in the legal range. The time-out value can be as
low as 1 second and as high as 60 seconds. Retry the operation with the value in this range.
235
Invalid user list type.
Error
The code for the type of user list to retrieve is not one of the legal codes. View the #define
statements in the include file ar.h for a list of supported codes.
236
License timeout cannot be less than 1 hour.
Error
The value specified for the license time-out value was 0 or a negative number. This value must be
greater than or equal to 1 hour. The value remains unchanged (defaults to 2 if nothing is set).
237
Value specified for DDE service name or topic is missing or larger than the maximum allowed
length.
Error
The DDE service name or topic field of the DDE active link action is missing or is too large. Both
of these fields are required, and both have an upper limit of 64 bytes. Verify the values, and correct
them as appropriate.
238
Value for DDE item is larger than the maximum allowed length.
Error
The value specified in the DDE item field is larger than the maximum allowed (32767 bytes).
Verify the value, and correct if necessary.
239
Invalid DDE action.
Error
The code for the DDE action to perform is not one of the legal codes. Verify the #define
statements in the include file ar.h for a list of supported codes.
240
Fields that have lengths over 255 bytes (including diary fields, unlimited length character
fields, and the Status History field) cannot be specified as sort fields.
Error
Fields that have lengths over 255 bytes (including diary fields, unlimited length character fields,
and the Status History field) cannot be specified as sort fields. You specified a sort that includes a
field that meets these criteria. Specify a sort list that does not include this field.
For IBM DB2 databases, the limit is 254 bytes.
43

Number
Description
241
Fields that have lengths over 255 bytes (including diary fields, unlimited length character
fields, and the Status History field) cannot be specified as fields in the list returned by the Get
List function.
Error
and the Status History field) cannot be specified as fields in the list returned by the Get List
operation. You specified a list that includes a field that meets these criteria. Remove this field from
the list.
242
Error
The specified field, value, or arithmetic operation type is not supported outside of a filter
qualification.
The type of value specified in the ARFieldValueOrArithStruct structure is allowed only in
a filter qualification. Specify a tag allowed outside a filter qualification.
243
DDE definition is empty.
Error
The DDE structure pointer is NULL. To define an assignment to a DDE result, specify a DDE
definition that defines which DDE operation is to be performed and that provides the values to
perform the operation.
244
The path to the program field of the DDE active link action is missing or is too large.
Error
The path to the program field of the DDE active link action is missing or is too large. This field is
required and has an upper limit of 255 bytes. Verify the value, and correct as appropriate.
246
Invalid day format.
Error
The format specified for the day portion of the time is not recognized. Review the structure
definitions in the include file (ar.h), and correct the definition to match the rules defined there.
247
Invalid interval time.
Error
The format specified for the time portion of the time is not recognized. Review the structure
248
Invalid day selection.
Error
The format specified for the day portion of the time is not recognized. Review the structure
249
Invalid hour format.
Error
The format specified for the hour portion of the time is not recognized. Review the structure
250
Invalid minute format.
Error
The format specified for the minute portion of the time is not recognized. Review the structure
251
Invalid value for enabling or disabling a filter/active link/escalation.
Error
The value specified for the flag to enable or disable a structure is not recognized. Set the value to
True (1) to enable the structure or False (0) to disable it.
252
One or more groups in the list of groups for the Subadministrator is not a group defined on this
Error
system.
One or more groups in the list of groups for the Subadministrator is not a group defined on this
system. The group must exist to be assigned Subadministrator access to the form.
44
AR System messages

Number
Description
253
One or more groups in the list of groups granted Subadministrator access to a form does not
exist.
Warning
One or more groups in the list of groups granted Subadministrator access to a form does not exist.
The operation being performed is an import. The problem is treated as a warning, and the import
is completed successfully.
You can define groups with the missing IDs, or you can update the definition of the form to
remove the undefined IDs.
254
Subject line is longer than the maximum allowed length.
Error
The value specified as the subject line for an email notification is longer than the maximum
allowed by AR_MAX_NOTIFY_SIZE (255 characters). Verify the subject line value, and retry the
operation. The character strings must be terminated by a 0 (zero) character.
255
Unrecognized submitter mode.
Error
The code specified for the submitter mode is not recognized. View the #define statements in
the include file ar.h for a list of the submitter modes.
256
Unrecognized server statistics tag.
Error
The tag specified for the server statistics structure is not recognized. View the #define
statements in the include file ar.h for a list of the server statistics tags supported.
257
A display tag to identify the view is not unique.
Error
A display tag to identify the view desired is not unique. The same display tag is used in two or
more instances.
Each display tag must be unique. Fix the definition to supply unique tags.
258
Error
The RPC socket number for the Distributed Server process is not one of the legal values
(390600, 390621 - 390634, 390636 - 390669, 390680 - 390694).
The value supplied as the RPC socket number, to be used by the DSO daemon for access to
AR System, is not a legal socket number. For the operations that the server must perform, specify
either 390600 (the Administrator server) or a value in the ranges 390621390634, 390636390669,
or 390680390694 (private servers), inclusive. For more information about using RPC sockets with
DSO, see BMC Remedy Distributed Server Option Guide.
259
Unrecognized no match action.
Error
The code specified as the no match code (the action to take when the values in a Set Fields action
have no matches) is not recognized. Verify that the #define statements in the include file ar.h
have a list of all no match codes.
260
Unrecognized multiple match action.
Error
The code specified as the multiple match code (the action to take when the values in a Set Fields
action have multiple matches) is not recognized. Verify that the #define statements in the
include file ar.h have a list of all multiple match codes.
261
SQL command is empty.
Error
The SQL command pointer is NULL or points to an empty string. To define an operation that
executes a SQL command, specify the command, and set this structure to point to it.
262
Field having length over 255 bytes (including diary fields, unlimited length character fields,
and the Status History field) cannot be used as fields to group by.
Error
and the Status History field) cannot be specified as fields to group by. You specified a grouping
that includes a field that meets these criteria. Specify a grouping that does not include this field.
45

Number
Description
263
Unrecognized save login code.
Error
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. Verify the definitions in the
include file ar.h for a list of the save login codes.
264
Server name for a character menu is empty or too long.
Error
The server name for a character menu is an empty string or is longer than the maximum allowed
length for a file name. Define a valid server name for the character menu file.
265
Join or View form definition is empty.
Error
The compound form structure is empty or has missing pieces. When a join or view form is
defined, this structure is required.
266
Invalid join member form name.
Error
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. You can only create a join between existing forms.
267
Invalid join form qualification.
Error
The qualification specified for a join form is invalid. Specify a join criteria for the join form; it must
be a legal qualification that associates the two forms. Verify the qualification, and update it so that
it is an acceptable join definition.
268
Invalid view form definition.
Error
The definition of the view form is invalid. One or more pieces of the view definition is missing
or invalid, so the system cannot create a clean interface to the non-AR System table. Make sure
that the definition of the view form is complete and accurate.
269
Invalid form type in join or view form definition.
Error
The form type tag specified for the compound form structure is not recognized. View the
#define statements in the include file ar.h for a list of the recognized form types. The form
structure is empty and is not allowed.
270
Field mapping is empty.
Error
The field mapping structure is required when you define a data field on a join or view form. For
this call, the structure is empty. Specify appropriate contents for this structure.
271
A form field is tied to an invalid index.
Error
A form field is tied to an invalid index. When defining a join field reference in a join form, specify
an index (of 0 or 1) indicating whether the field is tied to a field in the primary or secondary form.
The value of the index is not 0 or 1 in this case. Change the index to indicate the appropriate form.
272
The table name identified in the view form definition does not exist.
Error
The table name identified in the view form definition is illegal, or the table does not exist. The table
referenced in a view form must exist before the view form can be created.
273
Invalid field mapping type.
Error
The field type in the field mapping specified for a field in a join or view form is not recognized.
View the #define statements in the include file ar.h for a list of the recognized field types.
274
After a form (base, join, or view) is created, you cannot change the form type.
Error
After a form (base, join, or view) is created, you cannot change the form type. The compound
structure requested a change to the form type, and this action is not supported.
275
Index not allowed on join form.
Error
Because join forms are relational joins of base tables, you cannot define indexes on join forms. To
index one or more fields, specify the indexes on the base tables that underlie the join.
46
AR System messages

Number
Description
276
This form cannot be deleted because it is referenced by a join form as a base form with "No
Delete" flag set.
Error
When deleting a form, an option controls whether the form can be deleted if a join form depends
on this form. This error indicates that deletion of a form was attempted, but one or more join forms
depend on this form.
To override this error, specify the delete option AR_SCHEMA_FORCE_DELETE, which deletes the
form despite the dependency. The join forms dependent on this form are also deleted.
277
The field is referenced by a join form as a base field with No Delete flag set.
Error
When deleting a field, an option controls whether the field can be deleted if it is referenced by a
join form that depends on this field. This error indicates that an attempt was made to delete this
field, and one or more fields in some join forms depend on this field.
To override this error, specify the delete option AR_FIELD_FORCE_DELETE, which deletes the
field despite the dependency. The fields in the join forms that are dependent on this field are also
deleted.
278
This field is used in a join form qualification and with No Delete flag set.
Error
When deleting a field, an option controls whether the field can be deleted if it is used in the join
qualification of a join form. This error indicates that an attempt was made to delete this field, and
the field is used in the qualification of a join form.
To override this error, specify the delete option AR_FIELD_FORCE_DELETE, which deletes the
field despite the dependency. The fields in the join forms that are dependent on this field are also
deleted.
279
Selection Value ID too large.
Error
A value for a selection field cannot exceed 2,147,483,647.
281
Multiple links cannot be mapped to the same button.
Error
In older versions of the AR System server, this error occurs when you try to attach additional
active links to a button that already has an active link associated with it. In these older versions, a
button can have only one active link associated with it.
282
A default view for this form already exists.
Error
One of the properties of a view is whether the view is the default view for the form. Only one view
per form can have this property set to True. An attempt was made to set this property for the view,
but another view is set as the default.
Remove the default property setting from the view that contains the setting before giving it to
another view.
283
The specified data type is not supported.
Error
An RPC procedure mapping error between the client and the server occurred. You cannot create,
get, or set this field on this version of the AR System server because it is not supported.
284
Escalation does not have an action defined.
Error
The action field for an escalation is either NULL or empty. An escalation must define at least one
action.
285
A field referenced in the qualification is not a data field.
Error
A qualification contains a reference to a nondata field included in the message. Only data fields
can be included in qualifications. Because trim and control fields do not have associated data, they
cannot be used in qualifications.
47

Number
Description
286
Display Only fields cannot be included in a query to the database.
Error
A qualification being used to search the database contains a reference to a display-only field. The
field is included in the message. Display Only fields cannot be referred to in database searches,
because the database contains no data for them. They can, however, be included in workflow
qualifications.
287
Status field must be created before status history field can be created.
Error
When you create a status history field in a schema or a join schema, a status field must already be
available.
288
The requested operation is not supported on the server.
Error
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. Direct the request to an
AR System server with a version of AR System that supports the operation.
289
Nested outer join is not supported by Sybase /SQL database.
Error
The Sybase database supports outer joins for joins of two tables only. If you join more than two
tables, the database supports only inner joins. Therefore, if you create a join that includes a join
form, you cannot create it as an outer join if you are using Sybase.
290
Cannot access the join form with this version of the client.
Error
291
Message text is empty or too long.
Error
The text you can specify for a filter, active link, or escalation is limited to 255 characters before
expansion. The text you specified is over that limit. Correct your text string to 255 characters or
less. Character strings must be terminated by a 0 character.
The text string might contain parameter references that are expanded before the message is
delivered. The expanded message can contain as many as 4096 characters.
292
Invalid item list for entry existence.
Error
Provide an array for the server to return request existence information.
293
Expected column data missing from multiple entries.
Error
This is an internal error. A software bug exists in field value list processing in a
GetMultipleEntries( ) call. As an input parameter to call GetMultipleEntries( ), the
caller needs to provide a two-dimension array to hold the request value. If the internal column
index is greater than the array size, this error is returned.
294
Requested number of entries exceeds maximum allowed.
Error
Each GetMultipleEntries( ) call can return a maximum of 100 requests. If more than 100
requests are specified in the entryId list parameter of the GetMultipleEntries( ) call, this
error message is returned.
295
File pointer is NULL or invalid file pointer.
Error
The file pointer specified for an API call is NULL or is not a pointer to an open file. The parameter
must be a valid file pointer.
296
Invalid support file type.
Error
The file type specified for a support file in a join or view form is not recognized. View the
#define statements in the include file ar.h for a list of the recognized file types.
297
Admin released license too recently.
Error
The administrator released this users license too recently. An administrator can release a users
license only once every 24 hours.
48
AR System messages

Number
Description
298
Too many filters processed during this operation.
Error
Each operation has a 10,000 filter limit. This error occurs when more than 10,000 filters are run
from a single operation. This error might be caused by a push fields operation that runs recursive
filters.
For more information about filters and push fields actions, see the Workflow Objects Guide.
299
Too many levels in filter processing.
Error
Filter processing has a limit of 25 levels. This limit exists to protect against recursive filter actions,
such as a filter that has a push fields action that launches another filter with a push fields action
that launches another filter with a push fields action, and so on.
For more information about filter actions and push fields, see the Workflow Objects Guide.
300
Insufficient server memory for running this process.
Error
The system encountered an error during a call to allocate space. The failure occurred on the server
during processing of a call from the client. In general, 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. Recover the memory by shutting down unneeded processes or by restarting processes that
have been running for a while.
301
Error while writing to a file.
Error
An error occurred while writing to the indicated file. An accompanying message from the
operating system provides details. Determine why the write failed, and correct the problem
before retrying the command.
302
Entry does not exist in database.
Error
No entry exists in the database with the Request ID you specified. The specified Request ID is
invalid, or the entry was deleted by another user during the time you were processing it.
Note: This message is returned by web services and API programs. In the same situation, similar
messages are returned by BMC Remedy User (see error message 1200) and web clients (see error
message 9296).
303
Form does not exist on server.
Error
The server has no form with the specified name. Either the specified name is incorrect, or the form
is on another server.
304
Must have Administrative permissions to perform this operation.
Error
Some operations in the system are restricted to users with Administrative access. These
operations include the ability to restructure the database by adding forms, filters, and active links
and the ability to delete existing requests from the database.
To perform this operation, log in as a user who has administrative permission to the form you
want to update.
305
Next available ID length exceeds the Entry ID field length contact the Administrator.
Error
AR System automatically generates IDs for requests in the system. The next available ID will
overflow the definition for the Request ID field.
If you specified a length for the Request ID field that is less than the maximum allowed
(AR_MAX_ENTRYID_SIZE), you can increase the size of the field to eliminate this problem. If the
field is already at the maximum and a default value exists, you can change the default value to a
shorter string.
As a final option, contact Customer Support to help you reset the next request ID counter. Do not
try this task yourself because numerous actions must be performed, in sequence, to make this
change successful.
49

Number
Description
306
Value does not fall within the limits specified for the field.
Error
Limits are specified for the indicated field. These limits might be a low and high range limit if the
field is an integer or real field, or a maximum length or pattern if the field is a character field. The
actual limit and which field the limit is on are displayed with the error message.
Verify the value specified against the limits defined for this field. The value must be changed to
be within the limits, or the limits must be redefined to allow the value specified.
307
Required field cannot be blank.
Error
During submission of a request, no value was supplied for the required field. The field does not
have a default value, so a value must be supplied during the submit operation.
Perform one of these actions:
Supply a value for this 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.
308
Duplicate field in the field list.
Error
A field was specified twice in the field or value list. Each field can be assigned only a single value
and can be specified only a single time in the field or value list.
Remove the duplicate definition from the list, and reissue the command.
309
The entry you are working on was modified by another user after the last time you retrieved it.
Error
The entry you are trying to modify was modified by another user after the last time you retrieved
the definition. The changes made might impact your changes. You can override this error and
apply the changes. If you apply the changes (and override the error), all changes you make take
precedence over the changes made by the previous user. If you do not apply your changes, the
previous users changes are retained.
310
Value has wrong data type for the field.
Error
The value for a field in the field or value list is incompatible with the data type defined for that
field. The value of a field must be the same or compatible data type.
Change the value specified to be compatible with the data type of the field to which the value is
being assigned.
311
Field ID specified is not found on this form.
Error
The field ID references a field that is not defined for the current form.
You attempted an operation against the wrong form or server, or the structure of the form was
changed to eliminate the field ID from the form. Change to the correct form or server, or remove
the Field Name from the Field Sort Order list to complete the operation.
312
Incompatible data types for intended arithmetic operation.
Error
The data types of the fields used in an arithmetic operation are not consistent with the operations
allowed for that operation. Review the Form and Application Objects Guide for information about
the allowed data types of operations.
313
Incompatible data types for intended relational operation.
Error
The data types of the fields used in a relational operation are not consistent with the operations
allowed for that operation. See the Form and Application Objects Guide for information about the
allowed data types of operations.
50
AR System messages

Number
Description
314
Field does not exist on current form.
Error
The field is not related to the current form.

You attempted an operation against the wrong form or server, or the structure of the form was
changed to eliminate the field ID from the form. Change to the correct form or server, or remove
the ID from the field list to complete the operation.
315
Form/field to delete contains data, please confirm the deletion.
Error
You are trying to delete a form or field that contains data. You must explicitly override this error
for the operation to succeed. By default, the system deletes structures only when no data is lost.
316
Failed to create the temporary file.
Error
During processing, an error occurred while the server tried to use a temporary file. An associated
error message contains details.
By default, temporary files used by the server are created in the directory
/usr/tmp (UNIX) or \tmp (Windows). Verify that this directory is present and writable by the
user running the arserverd program. Also verify that the temporary directory was redirected
and that the specified directory exists and is writable by the user running the arserverd
program. The directory can be a link to another directory as long as the appropriate user can write
to it.
Review the reason for failure, and correct the problem. Then repeat the operation.
317
Duplicate form name.
Error
A form with the same name already exists on this server. Form names must be unique. Choose a
different name, or rename the existing form.
318
Group does not exist on server.
Error
No group with the indicated ID exists on this server. The group ID specified is incorrect, or the
group with this ID was changed or deleted from the system. Determine what groups are available.
If the group ID was changed, simply change the ID, and reissue the request. Otherwise, use the
ID of another group, or remove the reference to this group and reissue the request.
319
Specified field length exceeds the max limit.
Error
The operation you are performing requests a length change to one of the core fields. The field you
are changing has restrictions on its length. See the Form and Application Objects Guide for
information about the use and limits of the core fields.
320
Character menu does not exist on server.
Error
The character menu is not defined on the current server.

You attempted an operation against the wrong server, or no character menu is defined by that
name. Change to the correct server (if the former), or specify an existing character menu (if the
latter).
321
Too many levels in character menu definition.
Error
Menus can contain a maximum of 15 levels. You specified a menu that contains more than 15
levels at some point in its hierarchy.
322
Invalid hierarchy in character menu definition.
Error
A character menu definition was found in which the definition of menu items and children do not
form a consistent tree structure. Some children item definitions have no parent item.
51

Number
Description
323
Filter does not exist on server.
Error
The filter is not defined on the current server.

You attempted an operation against the wrong server, or no filter is defined by that name. Change
to the correct server (if the former), or specify an existing filter (if the latter).
324
Administrator command does not exist on server.
Error
325
Duplicate filter name.
Error
The name you are specifying for this filter is already in use by a filter on this server. Choose a
different name for the filter, or rename the existing filter.
326
Required field cannot be blank.
Error
You are trying to set a required field to a NULL value ($NULL$). Assign a legal value for the field,
leave the previous value in the field, or change the structure definition for the field so that it is no
longer required.
327
Incorrect data type for statistical operation.
Error
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 difference between two times). The
operation you attempted is incompatible with these limitations.
328
Duplicate command name.
Error
329
Invalid password or authentication string.
Error
The password you specified for the user name is not recognized. The problem can be with the
password or with the authentication string (for NT authentication, the authentication string is the
NT domain) or with both. Enter the password defined for this user name to access the system as
that user.
330
You do not have write access to this field.
Error
You do not have write (change) access to a field that you are trying to change. You must have
write access to write to that field.
331
You do not have write access to this record.
Error
You do not have write (change) access to a field that you are trying to change on this entry
(request). 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, depending on the permission settings. On this entry, you are not
serving in the role that allows you change access to the field, so you cannot change the field on
this particular entry.
332
You do not have write access to the field before the record is saved.
Error
You do not have write access to this field at create time. This indicates that you do not have
general write access to the field, and the create mode of the field is protected. You have access to
this field on requests assigned to you (or a group you are a member of) or submitted by you,
depending on the permission settings. Because this request does not exist yet, you are not serving
in any role yet, so you cannot set the field for this instance during a submit operation.
333
You have no access to field.
Error
You do not have access (read or write) to the field that you are trying to access. You must have
access to a field to read or change its values.
52
AR System messages

Number
Description
334
An AR System reserved field definition cannot be modified.
Error
Several reserved field definitions are reserved for AR System. You specified one of these fields
with settings that are incompatible with the limits set on the definition of those fields by
AR System. See the discussion of the AR System core and reserved fields in the Form and
Application Objects Guide.
335
Format for an AR System reserved field is invalid.
Error
The data contents of a reserved field do not meet the rules for the data in that field. 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.
336
Cannot assign a user to the special Submitter (3), Assignee (4), Assignee Group (7), Dynamic,
or Computed groups.
Error
You cannot assign a user to any of these groups using the User form. The Submitter (ID 3),
Assignee (ID 4), Assignee Group (ID 7) and Dynamic (IDs 60000 to 60999) groups define perinstance access rights. 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 are the Submitter if your login name appears in the
Submitter field, and you are the Assignee if your login name appears in the Assigned To field.
Membership in a computed group is determined by the contents of the Computed Group
Definition field on the Group form.
337
Error
You have reached the maximum number of database entries permitted with this version of the
Action Request System(R). To purchase the unrestricted version, contact your sales
representative.
http://www.bmc.com.
338
Duplicate Entry ID "found", and the current setting is "Do Not Create New".
Error
You are merging requests into a form from another source. You specified a request ID in the merge
operation that conflicts with an existing ID in the system. You did not specify to create another ID
in case of conflict; therefore, the merge operation failed.
To merge the new request, specify the option to create IDs, or delete the existing request before
merging the new one.
339
Incorrect format for a diary field.
Error
You specified a diary field in the merge operation, and the format of the diary data does not match
the expected format. A diary field is a formatted character string consisting of a set of user name,
time stamp, and character string triplets separated by valid separator characters. Separators are
defined in the include file arstruct.h.
If you receive this error during an import action, it is probably caused by a corrupt change diary.
Try importing without the change diary. You can do this by removing the lines beginning with
change-diary from the export file.
53

Number
Description
340
Incorrect format for the status history field.
Error
You specified the Status History field in the merge operation, and the format of the status history
value does not match the format expected. 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. Separators are defined in the
include file arstruct.h.
341
Set Fields process failed.
Error
Could not run a process as requested. The process was a filter or escalation Set Fields process
action. In either case, the process did not run. An associated error message might contain more
details.
Determine why the process did not run, and, if possible, correct the circumstances. Then retry the
operation.
342
The AR System directory file could not be opened.
Error
The AR System directory file could not be opened. An associated error message describes why the
ar file/etc/ar (UNIX) or ARConfigDir\ar (Windows)could not be opened. This file
contains the name of each AR System server that this client tries to connect to. The file must be
present to identify which servers to use.
343
Invalid filter definition.
Error
An error occurred when loading a filter definition from the database. An internal error occurred,
or manual changes were made to the contents of the database.
344
Group type or category conflict between two groups with the same group ID.
Error
Two groups were defined with the same group ID but with different access characteristics. All
groups are keyed by the group ID. Two or more groups with the same ID are actually a single
group definition with two names. If two groups have the same ID, both definitions must specify
the same group type and group category.
To correct the problem, change the group ID for the group being added to be unique, or change
the type and category of the new or existing group to be of the same type and category.
345
Duplicate active link name.
Error
The name you are specifying for this active link is already in use by an active link defined on this
server. Choose a different name for the active link, or rename the existing active link.
346
Active link does not exist on server.
Error
The active link is not defined on the current server. You attempted an operation against the wrong
server, or no active link is defined by that name. Change to the correct server (if the former), or
specify an existing active link (if the latter).
347
You have no access to active link.
Error
You are not allowed to access the specified active link. Permissions defined for the active link do
not allow you to get the definition of or execute the actions for the requested active link. Contact
your AR System administrator if you need access to the active link.
348
Group definition is empty no access to database is possible.
Error
At startup, the group cache for the database contains no group definitions. Without group
definitions, only AR System administrators can access the system. This error usually occurs due
to someone deleting data from the database. Re-establish the group structure for successful use of
the database.
54
AR System messages

Number
Description
349
Cannot delete a core field.
Error
You specified one of the core fields in a delete operation. Core fields cannot be deleted. If you do
not want to use the core field, you can ignore it by defining it as a hidden field. The obsoleted core
fields (IDs 9, 10, 11, 12, 13, and 14) can be deleted from your form.
350
Attempt to divide by zero (0) in arithmetic operation.
Error
During an arithmetic operation, the system detected a divide by 0. Restructure your queries to
avoid this illegal operation.
351
Cannot specify qualification on password field.
Error
The password field is a write-only field. To maintain security, you cannot specify a qualification
on the password field.
352
Notification to special Submitter or Assignee group specified. Reference to the Submitter or

Assignee group exists in the referenced Submitter or Assigned-to field. Notification canceled
to prevent a potential infinite loop.
Error
During a filter or escalation action, an attempt to notify the submitter or assignee of the request
occurred. However, the field holding this information contains a reference to the Submitter or
Assignee group. To prevent an infinite loop, the system is canceling the notification.
If you are receiving this error, reconfigure the notification targets in your system to eliminate this
condition.
353
You have no access to form.
Error
You are not allowed to access the specified form. Form permissions do not allow you to get the
definition of the form or of its fields or to access the data it contains. Contact your AR System
administrator if you need access to the form.
354
You have no access to administrator command.
Error
355
Must be administrator to access the filter.
Error
Only users with administrator permission can access (for read or change) a filter definition. The
current user does not have administrator permission.
356
Duplicate character menu name.
Error
The name you are specifying for this character menu is already in use by a character menu defined
on this server. Choose a different name for the character menu, or rename the existing character
menu.
357
Character menu contains too many items on one level (maximum 99).
Error
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. You can use multilevel menus to split large
menus into multiple smaller and more manageable menus.
358
Error while accessing a menu file on the server.
Error
An error occurred while the system tried to access a menu definition file on the server. An
associated error message contains details. After you fix the problem, the menu is available.
359
Set/Create/Delete operations to definition are only supported on RPC socket 390600.
Error
The server is running in a multiple-socket mode, and the socket in use for this client is not the
default socket of 390600. All structural changes must be made using the server connected to the
default socket. Use routines connected to the default socket, or restart this tool with the RPC
socket definition reset to the default value of 390600.
55

Number
Description
360
No currency conversion ratio exists for the requested conversion.
Error
A currency conversion between two different currency types was needed during the execution of
workflow, and the conversion ratio does not exist in the AR System Currency form. Supply
conversion ratios in the AR System Currency form for all possible conversions.
361
An unqualified search was issued and the server has been configured to disallow unqualified
searches. You must specify some search criteria to perform a search on this form.
Error
This server is configured not to allow unqualified searches, and you issued an unqualified search.
Specify some qualifying criteria in one or more fields to limit the amount of data being returned
from the server.
363
Required field assigned $DEFAULT$ but there is no default value for the field.
Error
During submission of a new request, a value specifying the keyword $DEFAULT$ was supplied
for the required field. The field does not have a default value specified so you cannot use the
$DEFAULT$ keyword during the submit operation.
Perform one of the following actions:

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.
364
Diary field cannot be set to a NULL value in a filter /escalation.
Error
The filter definition contains a Set Fields action where a diary field was assigned a value of
$NULL$. A diary field is append-only. Accordingly, it cannot be assigned a NULL value. Specify
an alternate value, or remove the assignment of NULL for the diary field.
366
Escalation does not exist on server.
Error
The escalation is not defined on the current server.

You attempted an operation against the wrong server, or no escalation is defined by that name.
Change to the correct server (if the former), or specify an existing escalation (if the latter).
367
Duplicate escalation name.
Error
The name you are specifying for this escalation is already in use by an escalation on this server.
Choose a different name for the escalation, or rename the existing escalation.
368
Error in definition for an escalation.
Error
An error occurred when loading an escalation definition from the database. An internal error
occurred, or manual changes were made to the contents of the database.
369
Must be administrator to access the escalation.
Error
Only users with administrator permission may access (for read or change) an escalation
definition. The current user does not have access to the escalation.
370
No form ID for the form.
Error
No form ID was found in the file form.ar. This is usually caused by a manual edit to the
form.ar file or by a file from a previous release of AR System. If the former, restore the file from
a backup before the manual change. If the latter, restore a file from the correct version or, if you
have not run the upgrade program after installing the new version, run the upgrade program to
bring the file up to date.
56
AR System messages

Number
Description
371
You cannot change the value of the Submitter field the Submitter Mode of the system is
configured to be locked.
Error
The system can be configured with a Submitter Mode of Locked or Changeable. You configured
the system with a value of Locked. In this mode, the value of the Submitter field cannot be
changed after submission (even by the administrator).
372
Could not create alert event.
Error
The server could not create an alert event request in the database. An associated error message
contains details. The following are possible causes:
The server could not find an Alert Events form.

More than one form with the reserved alert events fields was found. All but one form must be
removed.
The request was not added to the database.
373
Must be administrator to access the distributed mapping.
Error
Only users with administrator privileges can read or change a distributed mapping definition.
The current user tried to access a distributed mapping and does not have administrator privileges.
374
Distributed mapping does not exist on server.
Error
The specified distributed mapping does not exist on the current server. One of these conditions
exists:
You attempted an operation against the wrong server. Change to the correct server, and retry
the operation.
No distributed mapping with the specified name could be found. Specify an existing distributed
mapping, and retry the operation.
375
Duplicate distributed mapping name.
Error
You cannot assign the same name to more than one distributed mapping. Choose a different name
for the mapping, or rename the mapping with which the conflict exists.
376
Cannot update this entry this distributed entry is not the master copy.
Error
In a distributed environment, you can update only one entry (marked as the current master) in a
chain. You tried to update a copy other than the master. Perform the update on the current master
copy of the entry.
377
The distributed or application operation specified in the filter Run Process action contains
mismatched quotes.
Error
A distributed or application operation activated by a filter action includes one or more arguments
with single () or double quotation marks (). Somewhere in the command line, a mismatch in the
number of quotation marks exists (the number of open and closed single or double quotation
marks is not even). The command-line arguments cannot be processed.
The command line in which the mismatch exists is displayed and includes an error message. The
distributed or application operation is not performed. Retry the operation, and use the correct
command-line syntax.
378
Must be Distributed Server to perform this operation.
Error
To run the specified delete operation against the Distributed Pending and Distributed Mapping
forms, you must be the Distributed Server user (process). The distributed forms are part of the
system structure and must not be deleted or modified. To delete one or both of these forms in
BMC Remedy Developer Studio, select the forms for deletion, and ignore the system warning
related to the forms.
57

Number
Description
379
Problem encountered during creation of one of the distributed forms.
Error
When a system is licensed for the Distributed Server Option, a pair of forms is automatically
created by the server. During the creation of these forms, an error occurred. An associated error
message contains details. Fix the problem, and restart the arserverd process (or send a SIGHUP
signal) to re-create the forms.
380
No item matches filter conditions this operation has been defined so that "No Match"
generates an error.
Note
A filter action was extracting data from another form, or from another table in the database, and
found no rows that matched the qualification criteria. The administrator configured the action to
return an error if no matches were found.
381
Note
Multiple entries match filter conditions this operation has been defined so that "Multiple
Matches" generate an error.
A filter action tried to extract data from another form, or from another table in the database, and
found multiple rows that matched the qualification criteria. The administrator configured the
action to return an error if multiple matches were found.
382
The value(s) for this entry violate a unique index that has been defined for this form.
Error
The administrator defined one or more unique indexes on this form. The values on the entry you
are submitting or modifying duplicate the field (or fields) defined in the unique index. Review the
values for the entry to make sure that values that must be unique are unique.
383
File menu contains too many items on one level (maximum 1000).
Error
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. Large menus are unwieldy and can hurt
performance. If you need a large menu, consider breaking it into smaller pieces and connecting
the appropriate menu with the subset you are interested in.
384
The name specified contains an invalid character. Only printable characters are allowed.
Error
The name contains a control character. Object names can contain only printable characters.
Change the name to remove the control characters.
385
The same ID was specified several times in a multiple operation API call each ID
specified for this call must be unique.
Error
Multiple API callsthose enabling you to perform a set of operations in a single calldo not
support specifying the same ID several times in the same call. If you specify two sets of changes
or specify to delete the same object several times, confusion about the desired operation can arise.
Reissue the operation without specifying the same ID multiple times.
386
Exception occurred while handling previous exception.
Error
A nested filter exception error is returned because a filter exception condition is already being
thrown.
387
Updating this entry will violate join condition.
Error
When updating an entry in a join form, an option controls whether a field used in the join
qualification can be updated. To maintain data integrity of the record in the join form, this
operation is not allowed using BMC Remedy User.
To override this error using the AR System C API, specify the set option of
AR_JOIN_SETOPTION_NONE. A setting of AR_JOIN_SETOPTION_REF enforces the referential
integrity and causes the update to be rejected. See the C API Reference.
58
AR System messages

Number
Description
388
VUI does not exist for the specified form.
Error
The VUI is not related to the specified form. You attempted an operation against the wrong form
or server, or the structure of the form was changed to eliminate the VUI ID from the form. Change
to the correct form or server or use a VUI ID that is associated with the form to complete the
operation.
389
Duplicate VUI for the form.
Error
The VUI is already associated with the form. Both the VUI name and the VUI ID are unique
values. One or the other is already in use for this form.
To create a VUI, specify a unique name and IDor leave the name blank and the ID set to 0 to
have the system create a name and ID for you.
390
Cannot delete the default VUI for a form all forms require at least one VUI.
Error
Every form must have at least one VUI defined. You are trying to delete the only VUI for the form,
and this is not allowed.
391
Creation of VUI failed.
Error
A new VUI for the form could not be created. An associated error message contains details.
392
Field/VUI name must be unique for the form there is already a field or VUI using this name.
Error
The system requires that the name for all fields and VUIs on a form be unique. You supplied a
name already used by another field or VUI. Change the name of this item, and retry the operation.
393
Status-History field cannot be used as labelField or valueField in the query menu.
Error
Neither the Status History field nor any part of the Status History field can be used in a query style
character menu.
394
AR System is currently in Administrator Only mode. Please retry your operation later.
Error
AR System server was temporarily locked for use by users without administrator permissions; for
example, because updates are being performed. If you cannot wait to try your operation, consult
your AR System administrator.
395
The system has timed out while waiting for a process to return a value.
Error
An active link specified that a process is to be run on the server to return a value to be assigned to
a field. The server timed out waiting for the process to return the requested value. 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.
396
Support file for the specified object cannot be found.
Error
The support file is not related to the specified object. You attempted an operation against the
wrong object or server, or the structure of the form was changed to eliminate the indicated
support file ID from the object. Change to the correct object or server or use a support file ID
associated with the object to complete the operation.
397
Reserved field GroupList exceeds the 4000 character limit.
Error
The Group List field (field 104) is a reserved field with a restriction that the field cannot be more
than 4000 characters in length. The definition being saved or imported has an unlimited length.
Change the length to be 4000 or fewer characters.
398
Unable to obtain the memory for cache.
Error
If the server is unable to allocate memory from the shared cache, this message appears, and the
server terminates.
59

Number
Description
399
Error in definition for an active link.
Error
The AR System server detected an active link definition integrity issue. Repair or replace the
active link definition.
400
The file specified for a form does not hold a form definition.
Error
The file that was expected to hold the definition of a form does not hold a form definition or is
incorrectly formatted. The error is usually caused by a manual change to one or more AR System
database definition files. If you manually changed a file, the change is invalid. If you did not
changed a file, this is an unexpected error.
401
Form definition in the source file is invalid.
Error
The file contains a form definition, but it is not the expected form definition. The error is usually
caused by a manual change to one or more AR System database definition files. If you manually
changed a file, the change is invalid.
402
Incorrect format in the definition file.
Error
A format error was detected in a definition file. This error is usually caused by a manual change
to one or more AR System database definition files. The error message contains the error. If you
manually changed a file, the change is invalid.
403
The form definition file field count does not match number of fields in the file.
Error
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 you manually changed a file, the change is invalid. If you did not changed a file, this is an
unexpected error.
404
Field ID is in the core field range but is not a defined core field.
Error
A field ID in the core range was found, but this is not one of the defined core fields. The ID is,
therefore, an illegal ID and cannot be used.
405
A core definition from the definition file is incorrect.
Error
The definition of one of the core fields is inconsistent with the rules defined for that core field. This
error is usually caused by a manual change to the form definition file. If the definition file was
changed, the change is invalid.
406
One of the core fields is missing from the form file definition.
Error
The form definition being loaded is missing one or more of the required core fields. These fields
must be present as part of the definition of the form. You may or may not use them, but they must
be present. This error is usually caused by a manual change to the form definition file. If the
definition file was changed, the change is invalid.
407
Duplicate field/VUI ID in the form definition.
Error
The form definition contains a duplicate definition for one or more fields. A field or VUI ID must
be unique within a form. This error is usually caused by a manual change to the form definition
file. If the definition file was changed, the change is invalid.
408
Selection data type requires a selection specification.
Error
All fields with a Selection data type must define a list of one or more values that define the
selection for that field. A definition was found without that selection definition. This error is
usually caused by a manual change to the definition. If the definition was changed, the change is
invalid.
409
No definition is in the file.
Error
The structure file does not contain definitions. This error is usually caused by a manual deletion
of the contents of a structure file. If the file was deleted, it must be restored from a backup.
60
AR System messages

Number
Description
410
The filter definition cannot be found in the specified file.
Error
A file specified as holding the definition of a filter does not contain a filter definition. This error is
usually caused by a manual deletion of the contents of a structure file. If the file was deleted, it
must be restored from a backup.
411
The command definition cannot be found in the specified file.
Error
412
The import file is in an incorrect format.
Error
The import file contains data that is not part of a legal structure definition supported by
AR System. Remove the definition file of all lines that are not part of a legal definition, and then
retry the import operation.
413
The Active link definition cannot be found in the specified file.
Error
A file specified as holding the definition of an active link does not contain the definition. This error
is usually caused by a manual deletion of the contents of a structure file. If the file was deleted, it
414
The character menu definition cannot be found in the specified file.
Error
A file specified as holding the definition of a character menu does not contain the definition. This
error is usually caused by a manual deletion of the contents of a structure file. If the file was
deleted, it must be restored from a backup.
415
The escalation definition cannot be found in the specified file.
Error
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. If the file was deleted, it
416
The distributed mapping definition cannot be found in the specified file.
Error
A file specified as holding the definition of a distributed mapping does not contain the definition.
This error is usually caused by a manual deletion of the contents of a structure file. If the file was
deleted, it must be restored from a backup.
417
The group name is not a defined group.
Error
The system was translating the contents of a group (for example, from the Group List [field ID
104], Assignee Group [field ID 112], or a dynamic field) from a text string into the internal format
of a sequence of IDs. The operation was occurring during the processing of a filter or escalation.
During the conversion, an error occurred. The likely cause of the failure is that the system
encounters a name that is not a defined group.
418
Incomplete join form definition.
Error
During import, a form defined itself as a join form. However, one or more key pieces of
information (such as the type of join or the primary or secondary form) are missing. The join form
definition depends on complete information about the join, so it cannot be created.
419
Incomplete view form definition.
Error
During import, a form defined itself as a view form. However, one or more key pieces of
information (such as the table being referenced) are missing. The view form definition depends
on complete information about the view, so it cannot be created.
420
Invalid field type.
Error
With a join or view form, the field type specified in the field definition for a data field is not
appropriate for that form type. For example, if the form is a join form, all data fields must be
defined with a field type indicating that they are a join field because no base data fields exist when
you are working with a join form.
61

Number
Description
421
Incomplete field mapping definition.
Error
The field mapping of this join or view form is not consistent with the type of the form.
422
Unrecognized escalation action type.
Error
The type of the action attached to the escalation is outside the allowed range of types.
423
The container definition cannot be found in the specified file.
Error
The file contains a container definition, but it is not the expected definition. Make sure that you
did not changed the name of the file prior to import.
424
Push fields actions that affect entries in other forms can only affect forms on the same server
in a filter/escalation.
Error
In filters and escalations, you cannot use a Push Fields action to push values to forms residing on
different servers.
See the Form and Application Objects Guide for more information about Push Fields actions, filters,
and escalations.
429
The VUI definition can not be found in the specified file.
Error
The import file does not hold a view definition.
430
Field ID exceeds the maximum allowed value.
Error
The value supplied for the field identifier exceeds the maximum allowed value. Specify a value
less than or equal to 2147483647.
431
Field of this type cannot be included in a multi-column index.
Error
A multi-column index was specified that includes a field type that is not allowed, such as a
currency field. Remove any fields that are not allowed from the index specification
432
Currency field has too many functional currencies to allow indexing.
Error
A currency field selected for indexing has too many functional currencies to index each column
without exceeding the index limit of 16. Do not index the field, or remove some functional
currencies from the field definition.
433
Not a lock block definition.
Error
The definition file is invalid. It is possibly corrupted. Verify the validity of the export definition
file and re-export it if necessary.
434
An invalid or a corrupt lock block definition was skipped.
Error
A portion of the definition file was skipped because it is invalid or corrupted. Verify the validity
of the export definition file and re-export it if necessary.
435
Administrative operations must be enabled before you can modify this server setting.
Error
Administrative operations are disabled. Administrative operations must be enabled before you
can modify this server setting.
436
Invalid format for server information setting.
Error
The input value for this server setting is invalid. Verify that the input value for this server setting
is the correct type and is properly formatted.
437
The form data definition cannot be found in the specified file.
Error
The import file does not hold a form definition.
62
AR System messages

Number
Description
438
Cache reload failure.
Error
Indicates that a SQL error occurred during a certain stage of the AR System server initialization.
After the server cache has been loaded, patches can be provided to correct database problems.
This message indicates that an error occurred during the post-cache upgrade. Contact Customer
Support.
439
Error
Error changing field column length; ensure no existing data in the field exceeds the requested
length before retrying.
441
Invalid array index, out of range.
Error
The array index given to the AR System API is out of range for the specified array. Re-try the call
with a proper index value.
442
The required API input argument is empty.
Error
Supply a value for the input argument to the AR System API.
444
Could not resolve the JNI class.
Error
445
Could not resolve the JNI method.
Error
446
Changing the field option of the field is not allowed.
Error
You tried to modify a field option, but this option cannot be modified.
447
Server information associated with this tag has an invalid value.
Error
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. The error message
provides information about the valid values. Fix the invalid value in the AR System
Administration: Server Information form (recommended) or in the server configuration file, and
then retry the operation.
448
File size limit exceeded.
Error
The maximum log file size of 2GB was reached for the specified log file. Reset the log file before
reaching the limit or configure the log file to be circular.
450
Cannot find the report definition file. The operation will continue without the file identified.
Warning
When creating or updating an active link, a macro action or else definition contains a reference to
a report file that does not exist. The active link is created or updated without the file. If it is
replayed, the user receives a warning about the missing file. Locate the expected file, and put it in
the proper location; then, reselect the macro in the action, and update the active link definition to
have the file included in the active link.
451
Report definition file failed to load into server. The operation will continue without this file.
Warning
While trying to read a report file referenced in a macro definition embedded in the active link
definition being created or modified, the system encountered an error, and the report file was not
retrieved. The operation continues without the report file. The file is not saved as part of the
definition.
460
Audit Configuration information cannot be found in the ar.conf/ar.cfg file.
Error
Application auditing was enabled, and the system tried to load configuration information for the
application auditing but could not locate it in the configuration file. Contact Customer Support.
63

Number
Description
461
The AR Server version does not match the Lite license AR Server version included with the
licensed application.
Error
AR System on the server containing the application was updated to a different version. The
licensed application is supported only on the version of AR System included with the application.
Install the AR System included with the licensed application.
462
The form is not a member of a Lite licensed application.
Error
A form was added to a licensed application that does not support added forms. You cannot add
forms to this application.
463
Cannot create a form in a Lite licensed AR Server.
Error
You tried to create a form on an AR System server that was installed with an application that does
not support added forms. You cannot add forms on this AR System server.
464
Cannot change the form name in a Lite licensed AR Server.
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. You cannot change the name of a
form on this AR System server.
465
Cannot change the form mapping criteria in a Lite licensed AR Server.
Error
You cannot change the join criteria of a join form or the properties of a join, vendor, or view form
on this AR System server.
466
Invalid or pre 6.0 AR Server license file.
Error
The license file is corrupted, formatted incorrectly, or from a version of AR System prior to 6.0. Do
not edit the license file. Contact Customer Support.
467
AR Server license import option can only be 0 or 1.
Error
Specify 0 or 1 for the license import option. For more information, see the C API Reference.
468
Error reading license cache table.
Error
An error occurred in loading data from the license_cache table in the AR System database.
469
Warning, this key is not valid for this server.
Warning
This warning indicates that the entered key is not valid for the AR System server on which it was
entered. If the server is in a server group, the key might be valid for one of the other servers in the
group. In that case, ignore the warning. If this warning appears on a single server, a problem exists
with the license entry. Check the fields of the key for leading or trailing spaces, and make sure that
the correct Host ID was used when the key was generated.
470
User Cache utilities are disabled.
Error
The arcache utility was run on an AR System server that is configured to disallow the arcache
utility.
474
No licenses in supplied file.
Warning
Indicates that the file supplied during an ARImportLicense() API call does not contain valid
licenses. Supply the correct file name.
475
Too few arguments specified for upgrade program.
Error
The program that upgrades the database structure to the current structure requires more
arguments than you specified. The upgrade program is run automatically as part of the
installation operation. You need not run this program.
64
AR System messages

Number
Description
476
Too many arguments specified for upgrade program.
Error
The program that upgrades the database structure to the current structure requires fewer
arguments than you specified. The upgrade program is run automatically as part of the
installation operation. You need not run this program.
477
Oracle 8.0 is no longer supported by upgrade.
Error
The program that updates the database structure to the current structure no longer supports
version 8.0 of the Oracle database. Upgrade to Oracle 8i or higher.
478
This 6.3 Unicode database is not yet ready for upgrade. Please contact Customer Service for
details on how to prepare your database before attempting an upgrade to a 7.0 Unicode
database.
Error
When upgrading an AR System 6.3 Unicode server to an AR System 7.0 or later Unicode server,
you must first run a utility that prepares the database for this upgrade. If the utility has not been
run, the installer generates this error.
479
Warning
The temporary column control.unicode63handled, created for upgrading the 6.3 Unicode
database to a 7.0 database, could not be deleted. Please delete this column manually.
When upgrading a previous installation to AR System 7.0 or later, the installer creates temporary
tables to allow it to move and transform data types. After this data move is completed, the
installer attempts to delete these columns. If the delete fails, this error is generated.
480
Status History field is not supported on View forms.
Error
You cannot create a Status History field on a view form.
481
Requested database table not found. Please check the spelling (table name is case-sensitive).
Error
The correct column information (for example, the right number of columns) for the external
schema was not retrieved.
482
This View Form contains empty Request IDs. Ensure that the key field is set to a non-null,
unique column to avoid data corruption.
Error
You cannot search the database for the entry ID in a view form if its value is NULL.
483
Please restart the AR System Server for the changes to take effect.
Note
Restart AR System.
485
The reservedIdOKList parameter in the ARCreateMultipleFields() API function is blank. This

parameter must be either "Yes" or "No" or "1" or "0".
Error
The reservedIdOKList parameter in the ARCreateMultipleFields() API function was supplied

as a null pointer. This parameter must be supplied with a pointer to an ARBooleanList.
486
The list parameter does not have the same item count as in the Field ID list.
Error
A list parameter supplied in an ARCreateMultipleFields() or ARSetMultipleFields() API call does

not have the same number of elements as the fieldIdList parameter. All list parameters that
are supplied must have the same number of elements.
487
Set field status list cannot be empty.
Error
The setFieldStatusList parameter in the ARSetMultipleFields() API function was supplied

as a null pointer. This parameter must be supplied with a pointer to an ARStatusListList.
488
Field creation error occurred at the indicated list position.
Error
An error occurred during one of the individual field creations for an ARCreateMultipleFields()
API call. The specific error is reported as an item in the status list. This error supplies appended
text containing the zero based list position of the field the error occurred on. For example, if the
appended text is 2, the error occurred on the third field in the field list.
65

Number
Description
489
At least one set field failed in a multi-field operation.
Error
At least one error occurred during the operation of the ARSetMultipleFields() API call. If this error
is returned, the setFieldStatusList parameter supplies the details of the individual field
failures.
490
Invalid preference server option, out of range.
Error
Check preference server settings and make any necessary corrections.
504
Missing or invalid form definition file.
Error
The server could not open the form data dictionary file (form.ar). This file is in the database
directory referenced by the Server-directory setting in the ar.conf file (UNIX) or the
ar.cfg file (Windows).
Make sure that the directory setting is correct. If it is correct, look in that directory for the
definition file. An associated error message explains why the file was not opened. If the file is not
present, restore the file from a backup. Verify the permissions on the file to make sure that the user
running the arserverd process has read and write access. Update ownership or permissions as
needed.
524
This operation encountered an error and the transaction has been rolled back.
Error
Due to a workflow design error or an AR System internal error, the transaction is not committed.
To ensure database integrity, the transaction was rolled back.
550
Unable to connect to the SQL database. Please ensure the SQL database is running or contact
the Database Administrator for help.
Error
An error occurred when the system tried to open a connection to the SQL database. An
accompanying error message provides details.
The ar.conf file (UNIX) or the ar.cfg file (Windows) file contains definitions for the
environment variables to set for each database. The value for Dbhome-directory, applicable
only to UNIX, is the directory of the database server or client installation on the UNIX computer
where AR System is installed. The names of other needed settings begin with the name of the
database (for example, Sybase-Server-Name or Oracle-SID). Make sure that these values are
correct. If you moved your database or changed these parameters, update the requests in this file
and then restart the arserverd process.
551
Unable to connect to the SQL database.
Error
This error can have several causes, including:
During server start-up, the database was not accessible. Verify that the database is running and
is accessible to the AR System server.
During operation, this error can occur if AR System needs to contact an external database that
is not accessible, for example, when opening a view of an external table.
When ARERR 551 occurs, the database error is usually captured in the AR System SQL log. To
help diagnose the cause of this error, 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.
66
AR System messages

Number
Description
552
The SQL database operation failed.
Error
A SQL database error occurred during an operation against the database. An associated error
message contains the full text of the error message from the database. This error could be caused
by a direct SQL command in active link or filter workflow.
To identify the database error, turn on SQL and Filter logging on the AR System server. The
database error will appear in the SQL log. Also turn on client workflow logging as well as
ARAPILOGGING. Use the workflow logging to identify the SQL operation that causes the error,
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.
553
Operation requested is too large for a single SQL command.
Error
The operation you attempted generates a SQL command that is too large for the database to
process.
If the error occurs during execution of workflow, turn on filter logging and active link logging on
the AR System server to identify the workflow involved. In the case the resolution is to modify
the workflow to reduce the size of the operation.
If the error occurs when saving a form or other workflow object, the reason for the error might be
the size of the CREATE VIEW statement generated when the form is saved. You might need to
reduce the number of fields on the form. In this case, the CREATE VIEW statement in the
AR System SQL log might be truncated. To troubleshoot the error in this case, engage database
administration support to capture the full CREATE VIEW statement in the database logs and to
provide information about database limitations.
554
The Control record for the data dictionary in the database is missing.
Error
This is a serious error. The Control record for the data dictionary in the database is missing or
contains no records. This error usually indicates a failed installation or a permissions issue.
If the error occurred immediately after an installation, the installation might not have been
successfully completed. To identify the cause of the problem, use the installer logs. If the table
exists and contains a single valid record, work with the database administrator to determine
whether the database has a permissions problem.
555
One or more selection values are missing from the data dictionary in the database.
Error
This is a serious error. One or more enumerated (selection) values are missing from the data
dictionary in the database, or are corrupted. This error is most often generated when the AR
System server starts up.
To troubleshoot this error, gather and provide the following information and to BMC technical
support:
The arerror.log file.

In release 7.5 and later, if the error occurs during server startup, use the database consistency
checker (the -dbcheck server option) and capture the output to a log file. For more
information, see the Optimizing and Troubleshooting Guide.
On UNIX, also capture the UNIX console output during startup when the error is generated.
67

Number
Description
556
Missing data in the SQL database.
Error
This is a serious error. Data expected to be found in the database cannot be found. This error can
be caused by data missing in a table associated with a base data table. It can also be caused when
the data dictionary definition of a form or other object is corrupt or inconsistent.
When the data is managed through AR System, all appropriate cross-references are maintained.
If you manually updated data in the database, you might have broken a required reference.
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, gather and provide the following information to Customer Support:

The API and SQL logs, which help identify which forms or tables were involved.
(Release 7.5.00 and later) If the error occurs during server startup, use the database consistency
checker (-dbcheck server option) and capture the output to a log file. See the Optimizing and
Troubleshooting Guide.
(UNIX) The UNIX console output during startup when the error is generated.
557
More data was found in the database than was expected.
Error
This is a serious error. More data was found in the database than was expected. This error is
usually caused by inconsistent definitions in the data dictionary. When the definitions are
managed through AR System, all data is updated appropriately to avoid extra definitions. If you
manually updated the data dictionary definitions, you might have added data that conflicts with
existing definitions.
support:

The API log and the SQL log. These will help identify which forms or tables were involved.
checker and capture the output to a log file. For more information, see the Optimizing and
558
Form or field definition is missing.
Error
This is a serious error. One of the data dictionary entries defining a form or field is missing.
support:

checker and capture the output to a log file. For more information, see the Optimizing and
559
Character string exceeds maximum size allowed.
Error
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). If the field is a character string, edit the data to
less than the maximum allowed. If the field is a diary field, you cannot add data to the field for
this request.
Each database vendor has its own limitations for field sizes. If you have questions, ask your
database administrator.
68
AR System messages

Number
Description
560
Multiple actions have the same internal index (likely data corruption).
Error
This is a serious error. More than one action for a filter or active link contains the same internal
sequencing number. This number allows ordering of the actions in the proper sequence.
If you manually changed the database, undo the change you made to restore the database to a
consistent state.
561
Error
The underlying database does not support qualifications on fields with a length over 4000
bytes for Oracle or 255 bytes for all other databases.
Your SQL database engine does not allow qualifications on diary fields or character fields whose
maximum length is greater than 4000 bytes for Oracle or 255 bytes for all other databases. You
cannot specify a qualification that includes a reference to these types of fields.
562
Help text or change diary definition is missing.
Error
The SQL database engine being used stores Help text and change diary information in separate
tables from the structure definition. The Help text or change diary entry for a structure is missing.
Even when no Help text or change diary exists, a NULL entry is in these tables.
If you manually changed the database, undo the change you made to restore the database to a
consistent state.
563
% cannot be used to search for entries in SQL database.
Error
The SQL database engine being used does not support the modulo operator. You can use the
modulo operator in filter, active link, and escalation qualifications, but you cannot use it to search
for entries in the database.
564
Field references on the right side of the LIKE operation is not supported by SQL database.
Error
The SQL database engine being used does not support field references in a LIKE operation. You
cannot specify a search that includes a field on the right side of a LIKE operator.
565
The requested value is beyond the number of values returned.
Error
A SQL command was issued, and values are being retrieved from the database. A request was
made for a value from the command. However, the index of the column requested is greater than
the number of columns that were requested.
If you are using the SQL option of the Set Fields operation, correct the definition of the SQL
command used as the qualification to include sufficient columns, or correct the assignment to
include one of the returned values.
If you are not using the SQL option of the Set Fields operation, this is an internal error.
566
Requested record is locked by another user. Please retry.
Error
A deadlock condition was detected in the database. The operation for which this message was
received was canceled.
Because the deadlock condition should be trapped and the command automatically retried by the
server, you should not receive this error message. If you receive this message, continue by
reissuing the command. Record the operation you were performing (and the message received),
and contact Customer Support.
567
Failed to connect to database after multiple attempts.
Error
The system tried to establish a connection with the database and received errors after multiple
attempts.
69

Number
Description
569
The number of database records affected by a SQL statement was not available from the
database.
Error
The database was configured not to supply the number of records affected by a SQL statement.
Configure the database to supply this information. For example, on Microsoft SQL Server, the
No count connection option cannot be selected.
570
Incorrect format in the SQL command.
Error
This is an internal AR System server error that happens while creating a new SQL command from
another one. If this error occurs, check the SQL and API logs to help debug the issue.
590
SQL database is not available will retry connection.
Note
The SQL database is unavailable. The process periodically retries the connection until a
connection is obtained or it encounters a fatal error.
591
SQL database is still not available continuing to attempt connection.
Note
This message periodically appears while the system tries to connect to a SQL database that is not
responding. It is preceded by message 590. This message is issued as a reminder that the system
is not connected, but that it is continuing to retry the connection.
592
SQL database is now available.
Note
The previously unavailable SQL database is now available, and a connection was established. This
message follows either message 590 or 591.
600
Error while opening/reading from AR System directory file.
Error
The system failed to retrieve the list of AR System servers. This list is retrieved only when you
specify an update to all servers. 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, this error cannot occur because
no server list is accessed.
601
Unrecognized command line option.
Error
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. The program
does not execute with invalid arguments specified.
602
Cannot specify both -G and -U and cannot specify either more than once.
Error
The command line has both a -G and a -U option, or it has one or both options specified two or
more times. One of the two options must be specified, but they cannot both be specified in the
same command. You must break the operation into two commands.
603
Must specify one or both of the options -u and/or -g.
Error
Either the -u, the -g, or both options must be specified for the arreload program. Specify which
user or group form to use to reload the cache.
604
Must specify the operation to be performed (-G or -U).
Error
Specify either the -G or the -U option for this command. Indicate whether you are adding or
deleting a group or user entry.
605
One or more of the command line options is not appropriate for operation.
Error
A command-line argument is not appropriate for the operation being performed. Review the
documentation of the command for details about the options allowed with each operation.
607
An option required for the operation is missing.
Error
A required option for the specified operation is missing. Supply all required options. Review the
documentation for the command for details about the options required with each operation.
70
AR System messages

Number
Description
608
A required value for the command line option is missing.
Error
The specified option expects a value but none was specified. Supply an appropriate value.
609
Invalid tag for Group or User operation.
Error
The specified value is not one of the legal tags (a or d) for the -U or -G option. Specify whether
the system is adding or deleting the entry specified.
610
Error while accessing server cache file (server.ar).
Error
The server could not open the access control server cache file (server.ar). This file is in the
database directory referenced by the Server-directory setting in the ar.conf file (UNIX) or
the ar.cfg file (Windows).
Make sure that the directory setting is correct. If it is correct, look in that directory for the file. An
associated error message explains why the file was not opened. If the file is not present, restore
the file from a backup. Verify the permissions on the file to make sure that the user running the
arserverd process has read and write access. Update ownership or permissions as needed.
611
Dynamic group cannot be in a computed group definition.
Error
Dynamic groups are not permitted in the definition of a computed group.
612
No such user is registered with this server.
Error
The user specified as the administrator user to allow you to perform this command is not a
recognized user in the system. Connect with a valid user with administrator access.
613
Group type can only be 1 (view) or 2 (change).
Error
The value for the group type option must be an integer code 1 for a view group and 2 for a change
group. The value specified is not one of these values. Re-enter the command, and specify an
appropriate value.
614
License type can only be 0 (none), 1 (fixed), or 2 (floating).
Error
The value for the license type option must be an integer code (0 = no license, 1 = fixed license, 2 =
floating license). The value you specified is not one of these values. Re-enter the command, and
specify an appropriate value.
615
No such user exists.
Error
The user trying to log in is not a registered user. Although the system was configured to allow
guest users, the user is not allowed to log in as a guest user because the user name differs from a
registered user.
616
The specified Group ID is invalid for this group type.
Error
An incorrect group ID value was specified for a dynamic group, or a group ID in the dynamic
group range was specified for a regular group. Group IDs in the range from 60000 to 60999 must
be used only for groups in the dynamic group category.
617
Computed group includes circular reference.
Error
The computed group definition contains a circular reference. Remove the circular reference.
618
The syntax of the computed group qualification is incorrect.
Error
The syntax of the computed group qualification is incorrect. Make sure that the syntax is correct.
619
Computed group list contains invalid information.
Error
620
Two forms contain the same open license tag ignored for both forms.
Error
The system found two forms containing the same open license tag specified in the change history.
An associated error message identifies the forms.
71

Number
Description
621
Problem processing the license tag filelicense tag file ignored.
Error
The system encountered an error while trying to process the license tag file.
622
Problem while preparing open write licensingopen write licensing may be incomplete.
Error
The system encountered an error while trying to prepare open write licensing. An associated error
message contains details.
623
Authentication failed.
Error
Make sure that your user name and password were entered correctly.
624
User account locked out due to too many bad password attempts.
Error
Consecutive login attempts failed because of invalid passwords. The AR System server
administrator can configure the number of attempts to allow. To unlock your account, reset your
password or contact your administrator.
625
Date in the holiday list is invalid.
Warning
A date in the holiday list of the Business Time Holiday form is not a legal date. Illegal dates are
ignored and processing continues.
626
Time in the workday definition is invalid.
Warning
A time specified in the Business Time Workday form is invalid. Invalid times are treated as if no
time was specified, and processing continues.
635
The reserved holiday fields exist on multiple forms. They are only allowed to exist on one
form.
Error
The system found two forms containing the reserved holiday fields. For business time processing
to continue, delete one of the forms. An associated error message identifies the forms.
636
No Holiday form could be found on the server.
Error
The system could not find a form with the specified reserved holiday fields on it. Business time
processing involving holiday schedules cannot proceed without this form. During installation, a
definition file with copies of the business time forms was placed on the server system. The
Holiday form can be imported from that definition.
637
No holiday definition exists with the specified tag.
Error
The tag included in this message was specified as a holiday tag on a business time calculation.
However, this tag cannot be found in the Holiday form. Either correct the workflow to reference
a legal tag, or add a new tag to the Holiday form.
638
Two forms contain all the reserved workday fields delete one to continue.
Error
The system found two forms containing the reserved workday fields. For business time
processing to continue, delete one of the forms. An associated error message identifies the forms.
639
No Workday form could be found on the server.
Error
The system could not find a form with the specified reserved workday fields on it. Business time
processing involving workday schedules cannot proceed without this form. During installation,
a definition file with copies of the business time forms was placed on the server system. The
Workday form can be imported from that definition.
640
No workday definition exists with the specified tag.
Error
The tag included in this message was specified as a workday tag on a business time calculation.
However, this tag cannot be found in the Workday form. Either correct the workflow to reference
a legal tag, or add a new tag to the Workday form.
72
AR System messages

Number
Description
641
Open hours must be included in the workday schedule definition.
Error
The workday schedule does not contain any open hours. For a workday schedule to be valid, at
least one minute during the week must be defined as open. Fix the definition to specify open times
for the schedule.
642
The reserved Time Segment fields exist on multiple forms. They are only allowed to exist on
one form.
Error
The Business Time Segment form must be unique. You cannot have more than one copy of this
form.
643
No Time Segment form could be found on the server.
Error
The shared library you are using for the catalog is old or corrupted.
644
The specified Time Segment does not exist in the Business Time Segment form.
Error
You specified a time segment that does not exist in the Business Time Segment form. Make sure
that the associated tag name is correct, or create another Time Segment.
645
The level specified has to be from 1 to 1000.
Error
The level parameter of the Application-Bus-Time2-Get-Free-Window command is out of range.

Rerun the command, specifying a level of 1 to 1000.
646
The reserved Segment-Entity Association fields exist on multiple forms. They are only allowed
on one form.
Error
The Business Segment-Entity Association form must be unique. You cannot have more than one
copy of this form.
647
No Business Time Segment-Entity Association form could be found on the server.
Error
A Business Segment-Entity Association form was not found. This error can occur if the shared
library you are using for the catalog is old or corrupted.
648
Level 1 Time Segments must be Available and Level 2 must be Unavailable.
Error
Level 1 and Level 2 Time segments are special time segments. Level 1 can only be Available and
Level 2 can only be Unavailable.
649
Recurrence Start Time must be less than Recurrence End Time.
Error
For a recurrence time segment, the start time must be less than the end time.
651
ARFullTextInfoList structure is empty.
Error
The ARFullTextInfoList structure is either NULL or empty. To set one or more pieces of server
information, the settings and their values must be specified.
652
The Full text information data for this tag has an incompatible data type or the value is out of
range.
Error
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, or the value specified is
out of the legal range of values for the FTS information setting. Retry the operation, specifying the
correct data type for the value.
653
Full text information data for this tag is invalid.
Error
The data value specified for one of the full text search (FTS) values is an empty string. If a value
is specified, it must have a legal value assigned. Omit this value from the Set operation, or supply
a value.
73

Number
Description
654
Unrecognized full text information tag.
Error
You specified a code for a piece of full text search (FTS) information that was not recognized.
Review the #define statements in the include file ar.h for a list of all valid codes that can be
specified.
655
ARFullTextInfoRequestList list is empty.
Error
The value you specified for the list of information to retrieve from the FTS value was NULL or
empty. To retrieve information, specify what information you are trying to retrieve.
656
Unable to connect to the full text database.
Error
The server encountered an error while trying to connect to the full text search (FTS) database. An
associated error message contains details. Fix the problem, and restart the server process.
657
Unable to complete the full text search operation.
Error
This generic message indicates that an error occurred during a full text search (FTS) operation. An
associated error message contains the full text of the error message from the FTS engine.
658
Failed to read full text documents.
Error
While performing a full text search (FTS) operation, an error occurred while reading from the FTS
database. An associated message contains the full text of the error message from the FTS engine.
659
An error has occurred while opening the "Ignore Word" file.
Error
While the system tried to retrieve or set the Ignore Words list, an error occurred. An associated
message contains the full text of the error message from the full text search (FTS) engine.
This error is often caused by a permission problem with the Ignore Words list file. Search the FTS
home directory and index directory for a file named style/style.stp. The file must exist in
each directory, and the user running AR System server must have read and write access to the
files.
660
An error occurred while updating the "Ignore Word" file.
Error
While the system tried to update the Ignore Words list, an error occurred. An associated error
message contains the full text of the error message from the full text search (FTS) engine.
661
Unable to change the full text index directory.
Error
An error occurred during an attempt to change the location of the full text search (FTS) index
directory. An associated error message contains the full text of the error message from the FTS
engine.
This error commonly occurs when the target location does not exist, does not have appropriate
permissions, or does not have enough disk space for the existing FTS index.
662
Operation requested is too large for a single full text search command.
Error
The operation you attempted generates a full text search (FTS) command that is too large for the
database to handle. Break the operation into smaller pieces. For example, 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, reduce the number of operations being performed. Consider using the
accrue capability to combine searches for multiple values on the same field.
663
Full text search cannot be done on a field that is not a character, diary, or attachment field.
Error
An error occurred during a full text search (FTS). An attempt was made to search on a field that
is not a character, diary, or attachment field. This message indicates an error in the database
structure tables. Contact Customer Support.
74
AR System messages

Number
Description
665
This server does not have a Full Text Search license.
Error
An attempt was made to retrieve or set information about the full text search (FTS) environment
on the server, but no Full Text Search Option licenses are defined for the server. If you are not
using the products FTS capability, ignore this error. To use the FTS capability, obtain a license.
666
Full text operations are disabled turn on full text operations and retry your operation.
Error
You tried to perform an operation that can only be performed when the full text search (FTS) state
is set to Enabled. It is set to Disabled. To perform this operation, change the FTS state to Enabled,
and retry.
667
Full text operations are enabled turn off full text operations and retry your operation.
Error
You tried to perform an operation that can only be performed when the full text search (FTS) state
is set to Disabled. It is set to Enabled. To perform this operation, change the FTS state to Disabled,
and retry.
668
Invalid full text search query.
Error
The full text search (FTS) operation failed because the search criteria had syntax errors. An
associated error message contains complete information from the FTS engine. Contact Customer
Support for assistance in resolving the error.
669
The Destination full text index directory already exists.
Error
You tried to move the location of the full text search (FTS) index directory. The target directory
already exists. To move the index directory, the directory you will be using cannot already exist.
If the directory you specified is incorrect, change the name to the directory you want. If it is correct
and an empty directory is in place, remove the directory and retry the operation.
670
The full text search index on this field is being created but may take some time to finish.
Default search is used for now.
Warning
The field you are performing the search on is a full text search (FTS) enabled field; however, the
index does not exist on this field. Its creation is pending. It might take a few minutes or a few
hours for the index to be created and put in place, depending on the amount of indexing pending.
For now, the system defaults to the search strategy supported by the underlying database. When
the indexing is completed, the field will be available for full text searches again.
671
The indexer for running the Full Text Search indexing cannot be found.
Error
672
Status History field cannot be indexed for Full Text Search.
Error
The Status History field (core field ID 15) cannot be enabled for a full text search. You performed
an operation that attempted to index this field.
673
Warning
The query compares two fields that involve full text indexed fields. The full text search
capability does not support comparing two fields. The comparison will be made using the
functionality of the database.
674
The search query matched too many words in the FTS dictionary.
Error
The attempted query involved a full text search (FTS) indexed field, and the search term matched
too many words in the FTS dictionary.
675
FTS home directory can only be set by the installer, and not by using arsetfulltextinfo API call.
Error
You cannot use the API call arsetfulltextinfo to set the FTS information home directory.
This directory is set during installation.
75

Number
Description
677
License type can only be 0 (none), 1 (fixed), 2 (floating), or 3 (restricted read).
Error
The value for the license type option must be an integer code (0 = no license, 1 = fixed license, 2 =
floating license, or 3 = restricted read license). The value you specified is not one of these values.
Re-enter the command, and specify an appropriate value.
678
Full text indexing is disabled turn on full text indexing and retry your operation.
Error
A full text related operation was requested, but full text indexing is not enabled.
679
Form based search is not allowed without a full text license or while full text searching is
disabled.
Error
A search was requested using the special form-based search field in the qualification. To use this
feature, you need a current license of the specified type, and you must enable full text searching.
680
Full Text Search User Licenses are available but the Full Text Search engine is not installed or
installed incorrectly.
Error
If full text user licenses are on the system, the server tries to load the specified library. If the full
text search engine is installed, it is installed incorrectly. If the full text search engine is not
installed, install it to activate the full text search feature. If you do not want to use the full text
feature, remove the full text user licenses or ignore the error message.
681
Due to the field length change, the corresponding full text index is being rebuilt.
Error
682
Full text search service not available; a database search was performed.
Warning
The AR System search service is not available, so the search was performed against the database.
Contact your AR System administrator.
683
Warning
Full text search is disabled because it is not configured properly; a database search will be
performed.
An error occurred when the server attempted to initialize for full text search and did not find the
required configuration values for collection directory and configuration directory. Use the
AR System Administration: Server Information form to configure locations for the full text search
collection and configuration directories.
685
FTS Plugin is not available will retry connection.
Warning
The full text search plug-in is not responding. Check with your AR System administrator to verify
the status of the plug-in server.
686
A re-indexing will be performed for each full text indexed field on the form at the specified
time(s) in place of an update scan due to the absence of a last modified time field (field ID 6)
on the form.
Warning
A full text indexing scan for changes was defined for the current form. The form does not have a
Last Modified Time field that can support a scan for entries updated since the last scan. Therefore,
each scan performed on this form completely re-indexes the form.
Investigate whether you can add support for a Last Modified Time field to the form to provide
more efficient indexing.
687
Error
Table field cannot be indexed for multi-form search because the qualification contains an
external qualifier and/or display-only fields.
The table field qualification is not compatible with multi-form search indexing, so the field cannot
be selected for indexing. Create a shadow table field with a simpler qualification that can be used
for multi-form search indexing.
76
AR System messages

Number
Description
688
Only one form can contain the Multi-Form Search fields.
Error
An attempt was made to create a form with fields reserved for the existing multi-form search
system form. You cannot create a form with multi-form search fields.
689
At least one field in the forms being searched is in the process of being indexed which may
effect the search results
Warning
A multi-form search is being conducted against indexes that are in the process of a bulk field
update. Results might vary depending on the completion status of the operation.
690
No search term specified in the AR System Multi-Form Search form.
Error
A search term is required to perform a multi-form search. Specify at least one search term.
691
Either the Form List is empty or forms do not have any FTS fields in the AR System Multi-Form
Search form.
Error
The form lists contains no indexed fields on which to search. Specify forms that provide fields to
be searched.
692
Full text license is required for Multi-form search feature.
Error
An attempt was made to use the multi-form search feature without a full text system license.
Obtain a system license for full text search before attempting to use the multi-form search feature.
693
Update operation is not allowed on AR System Multi-Form Search form.
Error
An attempt was made to perform an update operation on the AR System Multi-Form Search form.
No type of update is allowed through this form.
694
The AR System Multi-Form Search form cannot be used for the specified operation.
Error
An attempt was made to perform an unsupported retrieval operation on the AR System

Multi-Form Search form. The retrieval operation name is appended. This type of retrieval is not
allowed through this form.
695
Full Text MFS Category Name property can only be specified for a Character field.
Error
An attempt was made to designate a non-character field as a multi-form search category field.
Only character fields may be designated as multi-form search category fields.
696
The field needs to have public permissions to be a full text Multi-Form Search Category or Title
field.
Error
An attempt was made to designate a non-public field as a multi-form search category or title field.
Only public fields may be designated as multi-form search category or title fields.
697
Error
You can only use the Full Text Indexed fields as the Weighted relevancy fields for Multi-Form
Search on a form.
An attempt was made to designate a non-indexed field as a weighted relevancy field on a form.
Only indexed fields may be designated as weighted relevancy fields on a form.
698
Error
Full Text MFS Category Name must be unique on a form -- there is already a field using this
name.
An attempt was made to specify a multi-form search category name that is already in use for the
current form. Specify a different name that is not already in use as a category name on the current
form.
699
Full text search attributes cannot be specified for multi-form search system form.
Error
An attempt was made to establish full text search properties on the AR System Multi-Form Search
form. Full text search properties are not allowed on the AR System Multi-Form Search form.
77

Number
Description
700
The system failed to connect to the network management platform.
Error
The system failed to connect to the network management platform. An associated error message
contains details. Fix the problem (for example, run the network manager if the manager is not
running), and rerun the daemon.
701
The system failed to connect to the event dispatcher of the network management platform.
Error
The system failed to connect to the event dispatcher of the network management platform. An
associated error message contains details. Fix the problem (for example, if the event subsystem is
not configured, configure it), and rerun the daemon.
702
The system encountered an error during a call to allocate memory space.
Error
The system encountered an error during a call to allocate space. In general, 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. Recover the memory by shutting down unneeded processes or
by restarting processes that have been running for a while.
703
Cannot open the configuration file.
Error
An error occurred while the system tried to open the configuration file. Because this file contains
the definition of all mappings to perform, the system cannot run without this file. An associated
error message contains details. Fix the problem, and rerun the daemon.
704
Unable to confirm whether the configuration file was updated successfully.
Error
An error occurred while the system verified whether the configuration file was updated. Because
this file contains the definition of all mappings to perform, the system cannot run without this file.
An associated error message contains details. Fix the problem, and rerun the daemon.
705
The format of one or more lines in the configuration file is unrecognizable.
Error
The format of one or more lines in the configuration file is unrecognizable. If the file was manually
edited, restore it to its previous format. If the file is updated through AR System NM daemons,
this error should not occur.
706
The configuration specified more fields than the maximum allowed.
Error
The configuration specified more fields to be mapped than the maximum amount allowed. The
system can map a maximum of 300 fields in any single trap mapping; more than this number are
defined.
707
Error
The specified command-line option is not a legal option for this program. A complete definition
of the allowed command-line options is in the Integration Guide.
708
An expected value is missing from the command line option.
Error
The specified command-line option requires an additional value with this program. A complete
definition of the allowed command-line options is in the Integration Guide.
709
The arxxxd process lost connection to the trapd process for the network management platform.
Error
The arxxxd process lost connection to the trapd process for the network management platform.
This error is not expected.
750
Changes to your event/trap mappings will be lost if you exit.
Error
You did not save your new or changed definitions. If you exit the tool, all changes will be lost.
Unless you are discarding invalid changes, do not ignore this messageacknowledge it and save
your changes before exiting.
78
AR System messages

Number
Description
751
The configuration file has been changed by another user since you retrieved it.
Error
While you were modifying the contents of the mapping file, the file was changed by another user.
If you save your changes, they overwrite the changes made by the other user.
752
The specified user does not exist on this server.
Error
The specified user does not exist on this server. If all fields being mapped have an open create
mode, an unknown (or guest) user can perform submissions. If guest users are allowed and create
modes are open, ignore this error and continue. If any fields being mapped are protected fields,
however, you must be a registered user with update permission to the field to perform the
submission.
753
The length of all data being mapped caused an overflow of the definition in the mapping file.
Error
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.
754
Changes on this screen will be lost if you continue.
Error
Changes you made to this screen will be lost if you continue. To discard the changes, simply
continue. To keep the changes, cancel the dismiss operation, and save the changes.
758
You have not opened the file defined in this window the file will not be opened if you
continue.
Error
You specified a file name in this window. The file was not opened because of a previous error or
because you did not click the Save button on the window. If you continue with this operation, the
new file will not be opened.
759
You have not saved your changes They will be lost if you exit.
Error
You did not save the changes you made to this file. If you continue to exit the tool, you will lose
the changes you made. To save the changes, cancel the exit operation, and save the changes by
using the Save command on the File menu. After the changes are saved, you can exit the tool
without losing them.
760
Out of memory.
Error
The system encountered an error during a call to allocate memory. In general, 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. Recover the memory by shutting down unneeded processes or
761
Cannot connect to any AR System server.
Error
Cannot connect to any AR System server. Accordingly, the system cannot verify permissions or
retrieve information about forms to map into. You cannot run this tool unless at least one
AR System server is accessible as a target for traps that are mapped.
763
Cannot successfully connect to any server as special Network Management user.
Error
Cannot connect to any AR System server as the current user. You (1) have not supplied a
password, or (2) your password is different from the one supplied, or (3) the server does not have
a registration for you and does not allow guest users. You cannot run this tool unless you can
access at least one AR System server to be the target for traps that are mapped.
764
Invalid password.
Error
The password you specified is not the password recognized for you. Verify the password that you
entered (remember that passwords are case-sensitive), and enter the corrected password.
79

Number
Description
765
Cannot open the network management configuration file.
Error
The specified network management configuration file cannot be opened. An associated message
contains details. Fix the problem, and try to reopen the file.
766
Cannot access the indicated file.
Error
The file indicated in the error message cannot be accessed. See the associated error message for
details.
767
Must supply a target form for the mapping.
Error
Specify a form that is the target of the trap being mapped. If no target form exists, no mapping is
performed.
768
Failure while writing to the file.
Error
An error occurred while the system tried to save changes to the specified file. An associated
message contains details. Fix the problem, and resave your changes.
769
Failure while building set fields screen.
Error
An error occurred while preparing the Set Fields screen. See the associated error message for
details.
770
You have entered a non-digit character for a numeric field.
Error
You can enter digits only in numeric fields. You specified a character string in a numeric field.
Change the contents of the indicated field to a legal number.
771
You have entered an illegal real number for a real number field.
Error
The value for the real field is not a recognized real format. The system accepts real values in
decimal or scientific notation. Change the value to a legal real number format, and repeat the
operation.
772
Specified selection value is not one of the legal selection values. Either specify a legal value or
change the specified value to a legal value.
Error
A selection value was specified that is not one of the legal selection values for the field. You can
add the value as a new option to the selection choices, or you can change the value to one of the
legal values.
775
Error
An error occurred while the system tried to map an SNMP varbind variable. Verify the syntax
specified in the mapping, and correct it as needed.
An error occurred while the system tried to map an SNMP varbind variable. Verify the syntax
specified in the mapping, and correct it as needed.
791
Cannot open the OracleNet Manager configuration file.
Error
The program cannot open the specified OracleNet Manager configuration file. An associated error
message contains details. You cannot add new definitions until you can open the file. Fix the
problem (for example, if you do not have read or write access to the file, change your file access
permissions), and rerun the tool.
792
Failure while writing to the definition file.
Error
An error occurred while the system tried to write updates to the definition file. An associated
error message contains details. Fix the problem (for example, if you are out of space, remove some
files to create more space), and perform the operation again.
80
AR System messages

Number
Description
793
Failure while trying to create a backup file operation continuing.
Error
This message indicates that an error occurred while the system tried to create a backup file for the
OracleNet Manager definition file. A failure occurred when system attempted to create a backup
of the definition file named fileName.bak. The system continues the operation and updates the
definition file; however, no backup file is created. An associated error message contains details.
794
Values are required for both the label and command.
Error
Supply both a label and a command. The label is the name displayed on the menu, and the
command is the operation performed when the label is selected.
795
Quotation mark cannot be used in the label due to OracleNet Manager syntax.
Error
The specified label contains a quotation mark. You cannot use a quotation mark in the label
because it is a special character in the OracleNet Manager definition syntax. Change the label so
that it does not include a quotation mark character.
796
Quotation mark cannot be used in the command line due to OracleNet Manager syntax.
Error
The command line you specified contains a quotation mark. You cannot use a quotation mark in
the command line because it is a special character in the OracleNet Manager definition syntax.
Change the command line so that it does not include a quotation mark character.
797
One of the mappings is wrong.
Error
You defined a mapping (probably using varbind) where one of the mappings is wrong. Fix the
mapping, and reissue the mapping request.
800
AR System TC server terminated by the server.
Note
801
AR System TC server terminated fatal error encountered.
Note
802
AR System server terminated unexpectedly restarting.
Note
The server detected that one of the child processes it is responsible for terminated. The name of
the process being restarted is reported in an associated message.
The server process relaunches the server that shut down.
803
AR System server terminated unexpectedly restarting.
Note
804
AR System TC server restarting.
Note
840
Error while opening the AR System TC server lock file.
Error
841
Another copy of the TC server is already running.
Error
842
Not enough memory to process the call from the client.
Error
during processing of a call from the client. In general, 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. Recover the memory by shutting down unneeded processes or by restarting processes that
have been running for a while.
81

Number
Description
843
Unable to launch the child process.
Error
A failure occurred while the system tried to launch a child process. An associated message
provides details. The child process was not launched. Fix the problem, and retry the operation.
844
Unable to launch the child process.
Error
A failure occurred while the system tried to launch a child process. An associated message
provides details. The child process was not launched. Fix the problem, and retry the operation.
845
Unable to start this server after 4 tries within 30 seconds abandoning attempt.
Error
The server process tried to launch a child process more than four times within 30 seconds. The
name of the child process that was not restarted is identified in an associated message. Because
this process continues to fail, the server stops trying to launch the process and removes it.
846
Exception occurred while handling previous exception.
Error
847
A failure occurred while the system tried to wait for a status change.
Error
A failure occurred while the system tried to wait for a status change. An associated message
provides details. This is an internal error.
848
Unable to start any servers TC server will be shut down.
Error
849
Unable to create the pipe.
Error
850
Unable to open the pipe.
Error
851
Unable to read from the pipe.
Error
855
Failed to lock arservftd process, it is held by another process.
Error
The work file must be locked by the arservftd process but is being held by another process.
856
Pending list lock file does not exist.
Error
The arservftd process cannot release the work file, because the file does not exist.
857
Unable to add note about the field updated due to the failure of opening the pending list
indexing file.
Error
A full text search (FTS)enabled field was updated. 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. An
associated error message provides details.
858
Error
Unable to add note about the field updated due to the failure of writing to the pending list
indexing file.
indexing pending could not be written to when you tried to add a note about the updated field.
An associated error message provides details.
859
Error
Unable to add note about the field updated due to the failure of locating the record associated
with the updated field.
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. An associated error message
provides details.
82
AR System messages

Number
Description
860
Unable to add note about the field updated due to the failure to truncate the file holding the
indexing pending list.
Error
indexing pending could not be truncated when you tried to add a note about the updated field.
An associated error message provides details.
861
Failed to delete unneeded entries while reindexing the pending list.
Error
During a reindex operation, an error occurred while the system tried to purge the list of pending
changes. An associated error message provides details.
862
Too few arguments for the full text indexer process.
Error
You did not provided the minimum set of arguments required by the full text search (FTS) indexer
process (arservftd). See the Configuration Guide.
863
Too many arguments for the full text indexer process.
Error
You exceeded the limit of arguments allowed by the full text search (FTS) indexer process
(arservftd). See the Configuration Guide.
864
Invalid action for full text index process.
Error
One of the arguments for the full text search (FTS) indexer process (arservftd) indicates the
action for the program to take. The supplied action code is not recognized. See the Configuration
Guide for information about allowed routines.
865
Full text indexer process terminated by user or a system error.
Error
The server for the full text search (FTS) search feature (arservftd) was terminated by a signal.
The number following this error is the signal that was received.
If the signal is 15, restart the server and continue to work. The process was stopped either
accidently or intentionally by a user in your environment.
If the signal is a number other than 15 or is one you sent directly to the process, contact Customer
Support for assistance in determining the cause of the problem. The server most likely shut down
due to a bug in the system.
866
Another instance of the full text indexer process is already running.
Error
Only one instance of the full text search (FTS) indexer process can be run on any given computer.
Determine whether a copy of arservftd is already running. If so, no action is required.
867
A form ID or name, a field ID, and a Request ID are all required for this operation. One or more
of these values is missing.
Error
When specifying an operation against a specific request, you must supply a form ID or name, a
field ID, and a Request ID. One or more of these values is missing. For more information, see the
C API Reference.
868
Too many arguments specified for the "optimize" argument.
Error
The optimize argument was specified for the full text search (FTS) indexer process. A limited
number of arguments is allowed when this option is specified. In this case, one or more of the
arguments that are not allowed were specified. For more information, see the C API Reference.
869
Too many arguments specified for the "retry" argument.
Error
The retry argument was specified for the full text search (FTS) indexer process. A limited
number of arguments is allowed when this option is specified. In this case, one or more of the
arguments that are not allowed were specified. For more information, see the C API Reference.
874
A required parameter is null or invalid.
Error
83

Number
Description
875
FTS Service could not complete the requested operation.
Error
881
Image definition is missing.
Error
A file specified as holding the definition of an image does not contain an image definition. This
error is usually caused by a manual deletion of the contents of a structure file. If the file was
deleted, restore it from a backup.
882
The specified image could not be found.
Error
The specified image is not in the AR System database. An operation was attempted against the
wrong server, or no image is defined by that name. Change to the correct server or specify an
existing image.
883
Duplicate image name.
Error
The specified image is already in the AR System database. Choose a different name for the image,
or rename the existing image.
884
No image specified.
Error
No image content has been specified for the image being created or updated. This argument is
required when creating or updating an image object.
885
No image type specified.
Error
No image type, such as jpg or bmp, has been specified for the image being created or updated.
This argument is required when creating or updating an image object.
897
Maximum number of client transactions already in use.
Error
898
Transaction handle supplied is invalid.
Error
899
Can not begin transaction because a transaction is already open.
Error
950
AR System error.
Note
951
The submitted mail message did not contain a form name.
Error
The mail message does not contain a line identifying which form is the target of the submission,
and no default form is configured for the armail daemon. The message can be resubmitted with
a form specified, or a default form must be configured for the armail process.
952
The submitted mail message did not contain a body providing details for the new entry.
Error
No text exists in the body of the mail message to specify values to be assigned for the new entry.
To create an entry by using the mail daemon, one or more values must be provided. The message
can be resubmitted with the additional information added.
953
The submitted mail message had a format that was not recognized.
Error
The format of the mail message does not match the expected format that. Review the message and
verify the format against the formats shown in the Configuration Guide.
954
The proper format for this command is: armaild [-f filename] [-n number-of-intervals] [-d].
Error
84
AR System messages

Number
Description
955
Missing value for command line parameter.
Error
A command-line argument that requires a value was specified, but no value was provided.
Supply an appropriate value for the argument.
956
Failure while accessing mail configuration file.
Error
The system encountered an error while attempting to access the configuration file indicated on the
command line. An associated message contains details. Most likely, the specified file does not
exist (file name was misspelled, or the file was moved). Fix the problem, and reissue the
command.
957
The submitted mail message specified a form that does not match the required form.
Error
The mail message specifies a submission to a form that is not the form specified as the required
form in the mail configuration file. This daemon was configured to support submissions to only
a single, specific form. A user tried to submit a request to another form.
958
The submitted mail message specified a server that does not match the required server.
Error
The mail message specifies a submission to a server that is not the server specified as the required
server in the mail configuration file. This daemon was configured to support submissions to only
a single specific server. A user tried to submit a request to another server.
959
The server specified for this message is not a recognized server access was attempted but no
server was found.
Error
The armail process was run, specifying the -x command-line option to connect to a specific
server. However, the server or AR System on that server is not active. The process must be able to
connect successfully with at least one server.
960
AR System New Entry.
Note
961
Your submission was accepted by the AR System. ID for the new entry is requestID.
Note
The submitted email message successfully created a request in AR System. Use the Request ID
number for querying or modifying the request.
962
AR System Query Response.
Note
963
Your query request was accepted by the AR System.
Note
964
"armail" failed when trying to log in to the mail system.
Error
armail failed when trying to log in to the mail system. Verify that the Mail login and password
given during installation are valid and that the mail system is accessible.
965
The "armail" address specified is a duplicate within the mail system.
Error
The armail address specified is not considered unique within the mail system.
966
"armail" could not read a mail message from the mail system.
Error
armail could not read a mail message from the post office. Make sure that the mail system is still
accessible.
967
"armail" could not log off from the mail system.
Error
armail could not log off from the post office. Make sure that the mail system is still accessible.
968
Invalid "send to" address.
Error
The address indicated is either ambiguous, does not exist in the mail system, or is inaccessible.
Use a valid address, and make sure that the mail system is still accessible.
85

Number
Description
969
--- AR Query Response ---.
Note
970
There are number matches to your query request.
Note
971
Warning
Your query matched more than the configured maximum: number. The maximum number of
allowable matches are returned.
When retrieving data through the mail query interface, the criteria specified matched more entries
than the limit configured for the armail process. The return includes this message and the data
for the specified maximum number of entries.
972
Your query has no matches.
Warning
When querying through the mail interface, no requests were found that match the query
conditions specified.
973
You don't have permission to the data on the results list.
Warning
You specified a quick report format, and one or more requests were found. However, you do not
have access to any of the fields in the report, so you cannot see any data returned from your
search. See your administrator to get the necessary permissions so you can see the data you are
trying to retrieve.
980
Required currency value not specified.
Error
The value portion of the currency structure was not provided. This error can be encountered only
through an API program.
981
Required currency code not specified.
Error
The currency code portion of the currency structure was not provided. This error can be
encountered only through an API program.
982
Bad currency value.
Error
When a character value is converted to a currency value, this error message is returned if the
string contains no numeric value or if the decimal number is invalid.
983
No common functional currency was found when currency constants were compared with
functional currency data.
Error
No common functional currency was found when currency constants were compared with
functional currency data.
984
No Currency Code form exists.
Error
A system error occurred, or the AR System Currency Code form was deleted. Restart the
AR System server, which automatically re-creates the form if necessary.
985
No active Currency Code found on the Currency Code form.
Error
An attempt was made to reference a currency code that does not exist or was disabled. Add the
currency code.
986
Currency fields cannot be used for grouping.
Error
A currency code was entered that is not an allowable currency code for this field.
987
Currency fields not allowed for grouping.
Error
A currency field was specified to be the group-by field in a statistical query, which is not allowed.
988
Currency part must be specified to use currency field in this context.
Error
A currency field was specified in a context where only a specific currency field part is allowed.
Specify a currency field part.
86
AR System messages

Number
Description
989
Cannot create or modify a currency field without specifying at least one functional currency.
Error
When a request that includes a currency value is submitted, AR System converts that value to a
functional currency type and stores it. Include at least one functional currency type.
998
Unable to free shared or exclusive lock on user cache hash list.
Error
This is an internal error that probably indicates the system is low on resources. Restart the server.
999
Unable to free shared or exclusive lock.
Error
A shared or exclusive lock cannot be released due to unexpected events in the server.
BMC Remedy User errors, warnings, and notes

1000
You cannot allocate memory on startup.
Error
when too many processes are running or when some processes grow to occupy most or all
available memory on your server. Recover the memory by shutting down unneeded processes or
1001
The -e and -i options require a macro name.
Error
The -e or the -i option was specified as the last option on the command line. Both of these
command-line options require the name of the macro to be run at start-up. Remove the option, or
specify a macro to go with the option.
1002
The -p option requires a substitution parameter and a value.
Error
The -p option was specified as the last option on the command line. This command-line option
requires that the name of a parameter and the value for that parameter be supplied. Remove the
option, or specify a parameter and value to go with the option.
1003
The format for the -p option is -p name = value.
Error
The -p option requires the name of a parameter followed by an equal sign followed by a value.
One or more parts of the definition are missing. If either the name or value contains spaces or
special characters, the value must be quoted to be treated as a single value on the command line.
1004
Error
The specified command-line option is not recognized. See the Integration Guide for information
about command-line options.
1005
Parameters can be specified only if you specify a macro first.
Error
You entered a -p command-line option that specifies values for parameters in a macro to run at
startup, but no macro is specified. If you specify parameters to be used in a macro, first use the -e
or -i options to specify the macro that uses them.
1006
You cannot read the configuration file - ARHOME variable may be set incorrectly.
Error
Configuration information for your session is stored in a configuration file named config in the
directory indicated by the ARHOME environment variable. If no ARHOME environment variable is
set, the file is in a directory named arHome under your UNIX login directory.
The program cannot read the contents of that file. Verify the setting of the ARHOME environment
variable if you defined an alternate directory. 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).
1007
You cannot connect to the X server.
Error
The aruser program on UNIX is an X program. It requires that an X windowing system be

running to allow the program to operate. No window system is running in your environment.
Start a windowing system, and restart the aruser program.
87

Number
Description
1008
The macro name in a parameter is longer than the maximum allowed length.
Error
The macro name specified on the command line is too long. The maximum length for a macro
name throughout AR System is 30 bytes. Specify a legal macro name defined in your system.
1009
Two startup macros have been specified.
Error
Two or more startup macros were specified on the command line. BMC Remedy User allows only
one macro to be specified at startup. You can, however, specify a macro that runs other macros.
Both the -e and -i options specify macros to run, so only one of those options can be specified
on the command line.
1010
No servers are defined for the AR System in the directory file.
Error
No servers were specified for the aruser program to connect to. One or more servers must be
defined in the /etc/ar file, or if you start the aruser program from the command line, one or
more servers must be defined by using the -x command-line option.
1011
Two directories for startup macros have been specified.
Error
The -d command-line option was specified two or more times. This option can be specified only
once. Re-enter the command, specifying only one -d command-line option for the directory that
contains the startup macro you want to run.
1012
The -d option requires a directory name.
Error
The -d command-line option requires that you specify a directory. Re-enter the command,
omitting the -d option if not needed or supplying an appropriate directory name.
1013
The directory name in a parameter is longer than the maximum allowed length.
Error
The directory name specified in the -d command-line option is longer than the maximum length
allowed for a directory name. Verify the syntax of the command line to make sure that you did
not omit required spaces between options.
1014
A directory can be specified only if you specify a macro.
Error
You specified the -d command-line option, but no startup macro was specified using the -e or
-i command-line option. Re-enter the command, omitting the -d option or specifying a startup
macro with the -e or -i option.
1015
The -x option requires a server name.
Error
The -x command-line option requires that you specify a server name. Re-enter the command,
omitting the -x option (if not needed), or supplying an appropriate server name with the -x
option.
1016
The server name in a parameter is longer than the maximum allowed length.
Error
The server name specified in the -x command-line option is longer than the maximum length
allowed for a server name. Verify the syntax of the command line to make sure that you did not
omit required spaces between options.
1017
Server is not compatible with AR System Alert.
Error
The BMC Remedy Alert client works only with 5.x or later AR System servers.
1067
The process terminated unexpectedly.
Error
No description.
1100
Request requestID was successfully created.
Note
The Save operation was completed successfully. This message displays the request ID of the
newly saved request.
88
AR System messages

Number
Description
1101
The preceding message occurred during the execution of active link activeLink action
action.
Note
The error occurred while running an active link. This message gives the name of the active link
and the specific action in the active link where the error occurred. This information is useful for
debugging active links. In general, you can ignore this message.
1102
Additional errors were truncated.
Note
The operation that was being performed generated a large number of error messages. The most
serious messages are displayed. However, to avoid overflowing the screen, some of the messages
were suppressed.
1103
Attachments for the report are exported under directoryName. Include this directory in the
export file if you choose to import the data.
Note
This message notifies user when the attachments are exported to a directory for reporting.
1200
No matching requests (or no permission to requests) for qualification criteria.
Warning
No requests were found that match the qualification criteria you specified. This might have
occurred for one of these reasons:
The criteria you specified do not match any requests.

You do not have access to the request or to the fields you specified in the request.
Note: This message is returned by BMC Remedy User. In the same situation, similar messages are
returned by web services and API programs (see error message 302) and web clients (see error
message 9296).
1201
New text is longer than the maximum allowed length - truncating to fit.
Warning
The text you specified is too long for the field you are trying to update. The field has a maximum
length defined, and the text that you entered is too long for the field. The extra text is truncated so
that it fits in the target field.
1202
A recording operation is in progress your current recording will be lost if you exit.
Warning
You specified that you want to exit BMC Remedy User; however, a macro recording operation is
in progress. To save the macro you are recording, click Cancel Exit, and then save the macro. After
the macro is saved, you can exit without losing the macro. If you do not want to save the macro
and you want to exit the program, click Exit.
1203
This record has been updated by another user since you retrieved it. Saving your changes will
overwrite the changes made by that user. Do you want to save your changes?
Warning
The request you tried to save changes to was modified by another user after you retrieved it. You
can take one of the following actions:
Save your changes, which will overwrite the changes of the other user.
Cancel the operation (not save your changes), retrieve the request again, and re-enter your
changes.
If you are updating a diary field, your changes do not overwrite changes made by the other user.
If you are changing fields where the data you enter is supposed to be the final value, continue with
the operation, saving your changes.
1204
Partial selections will become full selections on playback.
Warning
Macros cannot record operations continuing from partial selections in a query list. The contents
of the query list are likely to be different when the macro is replayed, so the macro cannot
reasonably record information about partial selections.
The macro records the operation as if all items in the query list were selected.
89

Number
Description
1205
New fields added or made accessible by administrator - added as hidden fields to local view
file.
Warning
An administrator updated the form being opened. One or more fields were added to the form.
However, you have a customized view of the form. To avoid possible conflict with your
customizations, the new field is added as a hidden field on your view. You can use the Customize
View operation in BMC Remedy User to locate the new field, move it to an appropriate location,
and make it visible if you want to use it.
1207
A recording operation is in progress current recording will be lost if you continue.
Warning
You started recording a macro and then requested that the macro recording be canceled. If you
click Cancel Recording, the recorded operations are lost. To continue with the recording, click
Continue Recording.
1208
You have not saved changes on this screen they will be lost if you continue.
Warning
You changed the data on the current screen. If you continue with the Dismiss operation, your
changes will be lost. To keep your changes, click Cancel Dismiss, and then save the changes. To
discard the changes, click Continue.
1209
You have not saved changes on this screen they will be lost if you continue.
Warning
You changed the data on the current screen. If you continue with the Next or the Previous
operation, your changes will be lost. To keep your changes, click Cancel Dismiss, and then save
the changes. To discard the changes, click Continue.
1210
You have not saved changes on the properties screen they will be lost if you continue.
Warning
You changed the data on the form Item Properties associated with the Customize View window.
If you continue with the Dismiss operation, your changes will be lost. To keep your changes, click
Yes, and then save the changes. To discard the changes, click No.
1211
You have not saved changes on a diary or text edit window they will be lost if you continue.
Warning
You changed the data on a Diary or a Text Edit window. If you continue with the Dismiss
operation, your changes will be lost. To keep your changes, click Cancel Dismiss, and then save
the changes. To discard the changes, click Continue.
1212
Query window is now connected to a different form continuing will change the current
form.
Warning
The Search window is connected to a form different from the form being referenced in the
window where you are performing the operation. If you continue this operation, the window
changes to the new form. If you cancel this operation, the operation is canceled and the window
remains unchanged.
1213
Multiple entries match qualification criteria Information pulled from first matching entry.
Warning
More than one request matched your qualification, but BMC Remedy Developer Studio defined
AR System to display only the first matching request from the search.
1214
Macro recording is active operation recorded but no database operation performed.
Warning
To avoid spurious submissions to the database and to prevent incorrect bulk modifications of
data, the Submit and Modify All operations are not performed when you are recording a macro.
This message is displayed to indicate that the operation is complete and would have been
performed if the macro recording was not in progress.
1215
Server cannot set to the client locale. Locale-sensitive operation done on the server may not
conform to the clients locale convention.
Warning
Make sure that the server and client can use the clients locale convention.
90
AR System messages

Number
Description
1216
This operation will modify number entries. Do you want to continue?
Warning
The operation you are performing modifies many entries in the database. The message specifies
the number of entries that will be modified. To continue with the modification, click Continue. To
avoid modifying multiple entries, click Cancel, and verify the operation you are performing. This
message is issued only from the Modify All window.
1217
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.
Warning
You changed the data in a Diary or Text Edit window. Your changes will not be saved if you click
Continue. If the changes are important, click Cancel Dismiss, save the data in the Diary or Text
Edit window by selecting Save in that window, and re-click Save on the current window. To
discard your changes in the Diary or Text Edit window, click Continue, and continue with the
Save operation.
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.
1219
You have not saved changes on the exploded help window they will be lost if you continue.
Warning
1220
Warning
You have not saved changes on the exploded help window they will not be included in the
current operation if you continue.
1221
The specified file already exists.
Warning
The file you specified as the target of your report already exists. You can overwrite the file or
cancel the Report operation.
1222
Unable to find help for the specified field.
Warning
A failure occurred while the system tried to retrieve Help text for the field. An associated error
message provides details.
1223
Duplicate name for macro. Do you want to overwrite the existing macro?
Warning
You specified a name for a new macro that matches the name of an existing macro. You can
overwrite the existing macro to replace the old definition with the new definition, or you can
cancel the operation and change the name for the new macro, leaving the existing macro
definition intact.
The name for a macro is a combination of the name and the directory it is stored in. You can have
a macro with the same name in different directories without conflict.
1224
Duplicate name for custom report. Do you want to overwrite the existing custom report?
Warning
You specified a name for a new custom report that matches the name of an existing custom report.
You can overwrite the existing custom report if you want the new definition to replace the old
definition, or you can cancel the operation and change the name for the new custom report,
leaving the existing custom report definition intact.
The name for a custom report is a combination of the name and the directory it is stored in. You
can have a custom report with the same name in different directories without conflict.
91

Number
Description
1225
Duplicate name for user command. Do you want to overwrite the existing user command?
Warning
You specified a name for a new user command that matches the name of an existing user
command. You can overwrite the existing user command to replace the old definition with new
definition, or you can cancel the operation and change the name for the new user command,
leaving the existing user command definition intact.
The name for a user command is a combination of the name and the directory it is stored in. You
can have a user command with the same name in different directories without conflict.
1226
Exit User Tool?
Warning
1227
Failure trying to expand the character menu.
Warning
An error occurred while the system tried to expand the definition of a character menu. An
associated error message contains details.
1228
The selected macro definition will be deleted.
Warning
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. Click Continue to continue with the
operation and delete the macro, or click Cancel to cancel the Delete operation and retain the macro
definition.
1229
The selected custom report definition will be deleted.
Warning
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. Click Continue to continue with
the operation and delete the custom report, or click Cancel to cancel the Delete operation and
retain the custom report definition.
1230
The selected user command definition will be deleted.
Warning
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. Click Continue to continue with
the operation and delete the user command, or click Cancel to cancel the Delete operation and
retain the user command definition.
1232
Macro recording is active modifications will be made to the entry but will not be recorded
in the macro.
Warning
You are recording a macro in BMC Remedy User. When the macro was processed, any operation
that used a global (Modify All) or unrecoverable (Delete) action was performed. No action was
taken, but the operation was recorded and will replay on later use.
1233
Your disk drive is almost full. Please remove unwanted files.
Warning
The disk containing the file you are writing is approaching its maximum storage capacity.
To continue with the operation, create space for the file.
1234
Help text is too long; only first 32,000 characters are shown here.
Warning
BMC Remedy User displays only 32,000 characters of Help text.
1235
Text field is too long; only first 2,000,000 characters are shown here. If you change this request,
it will damage the record.
Warning
Character fields display only 2,000,000 characters in BMC Remedy User. If you add more
characters to the field, you lose all information over the 2,000,000 character limit and any changes
that you made.
92
AR System messages

Number
Description
1236
Your window resources are low; close unwanted windows or applications.
Warning
You are running too many applications to operate AR System client tools efficiently. Shut down
all tools other than AR System tools. Consider adding more memory or reconfiguring your
system resources.
1237
File will be saved in Report File format. Default file extension is *.rep if none specified.
Warning
This message appears if you are saving a report and do not specify .arx, .rep, or .csv formats.
The report definition defaults to saving the report as a .rep file.
1239
Duplicate macro name.
Warning
1240
Warning
1241
Warning
1242
Warning
The customized view for this form has been updated to AR System 3.0 format. Because of
version translation limitations, you may need to reposition some buttons by using the
Customize View function.
The administrator has updated this form on an AR System 2.1 server. Your customized view
cannot be updated using this tool. If you continue, you may encounter some problems. Do you
want to continue?
You can continue with out-of-date customized view files, or they can be reloaded from the
server. Do you want to reload the form from the server? If you click Continue, you will lose
your customized view.
If you continue with the view from a previous version of the tool, you cannot further customize
without reloading an Admin view from the server. All customizations will be lost, but you can
recustomize the view and continue with the new view. If you do not continue, the existing
customized view remains available.
1243
You cannot translate the group name in the Group List or Assignee Group field.
Warning
A group name specified in the Group List field (ID 104) or Assignee Group field (ID 112) cannot
be translated. This means that the name is not recognized as one of the groups defined for the
system. Verify the spelling, capitalization, and spacing of the name to make sure that it is one of
the legal group names.
1244
There was a problem expanding the EXTERNAL qualification.
Warning
The supplied qualification or assignment statement has improper syntax.
1300
Warning
Error while processing selected entries. Continue processing, suppressing further errors or
cancel the operation.
1301
No such form exists - make a selection from the list.
Error
You entered an unrecognized form name. The list contains all valid forms. Double-click a form
from the list.
1400
The workflow logging file specified in the logging options dialog cannot be opened.
Error
The workflow log files path, name, or bothas specified by the user in the workflow logging
options dialog of BMC Remedy Usercannot be opened. Verify that you have file or directory
access permissions.
1401
You cannot open view file.
Error
The file containing the cached view for the form cannot be opened. This can be caused by
permission problems in your ARHOME directory. Verify that you have read and write access to the
ARHOME directory and to the view files (.arv files). Fix the problem, and retry the operation.
93

Number
Description
1402
You cannot open definition file.
Error
The file containing the cached definition for the form cannot be opened. Verify that you have read
and write access to the ARHOME directory and to the definition files (.arf files). Fix the problem,
and retry the operation.
1404
You cannot open default file.
Error
The file containing the user-defined defaults for the form cannot be opened. Verify that you have
read and write access to the ARHOME directory and to the default files (.ard files). Fix the
problem, and retry the operation.
1405
You cannot open configuration file.
Error
The configuration file cannot be opened. Verify that you have read and write access to the ARHOME
directory and to the configuration file (config). Fix the problem, and retry the operation.
1406
You cannot open the specified file.
Error
The file indicated in the message cannot be opened. An associated error message contains details.
Fix the problem, and retry the operation.
1407
You cannot open a temporary file.
Error
A failure occurred when the system tried to open a temporary file. These files are opened in the
directory /tmp. An associated error message provides details. Fix the problem, and retry the
operation.
1408
You cannot read from the specified file.
Error
An error occurred while the system tried to read from the file identified in the error message. An
associated error message provides details. Fix the problem, and retry the operation.
1409
You cannot write to the specified file.
Error
An error occurred while the system tried to write to the file identified in the error message. An
associated error message provides details. Fix the problem, and retry the operation.
1411
You cannot write to the definition file.
Error
An error occurred while the system tried to write to the definition file for this form. These files are
stored in your ARHOME directory (.arf files). An associated error message provides details. Fix
the problem, and retry the operation.
1412
You cannot write to the view file.
Error
An error occurred while the system tried to write to the view file for this form. These files are
stored in your ARHOME directory (.arv files). An associated error message provides details. Fix
1413
You cannot write to the default file.
Error
An error occurred while the system tried to write to the user-defined defaults file for this form.
These files are stored in your ARHOME directory (.ard files). An associated error message
provides details. Fix the problem, and retry the operation.
1414
You cannot reset user view.
Error
An error occurred while the system tried to reset your view. An associated message provides
details. Fix the problem, and retry the operation.
1415
You cannot restore previous view.
Error
An error occurred while the system tried to restore your previous view. An associated message
provides details. Fix the problem, and retry the operation.
94
AR System messages

Number
Description
1416
You cannot make backup view.
Error
An error occurred while the system tried to create a backup copy of the view file. An associated
message provides details. The operation continues without creating a backup file.
1417
You cannot open support data or cache file.
Error
The file containing the support file for the form cannot be opened. Verify that you have read and
write access to the ARHOME directory and to the view files (.arv files). Fix the problem, and retry
the operation.
1418
You cannot write to the specified support data or cache file.
Error
An error occurred while the system tried to write to the support file for this form. These files are
stored in your ARHOME directory (.arv files). An associated error message provides details. Fix
1450
Fork operation failed.
Error
A failure occurred while the system tried to start a child process. An associated message provides
details. The child process was not started. Fix the cause of the failure, and retry the operation.
1451
Failure occurred while trying to run a process to load a field value.
Error
A failure occurred while the system tried to start a child process that is retrieving data for a field.
An associated message provides details. The child process was not started, so no data is changed
in any fields. Fix the cause of the failure, and retry the operation.
1500
Out of memory.
Error
The system encountered an error during a call to allocate memory. The failure occurred on the
client (the one running the aruser program, BMC Remedy User). 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. Recover the memory by shutting down unneeded processes or
1501
You cannot record operation: operationType.
Error
An error occurred while the system tried to add the specified item to the list of recorded
operations. The system is probably out of memory. The indicated operation will not be in the
macro you are building if you continue. Cancel the recording operation, and treat the error as if
an Out of memory error occurred (see error message 1500), and rerecord your macro.
1502
Only integer data types can be displayed by using numeric text (defaulting to text field type).
Error
You requested a field type of numeric text for a field that is not an integer field. Only integer type
fields can have a field type of numeric text. The field type for this field is text. If a text field type
is acceptable, you can ignore this message. Otherwise, specify a field type appropriate for the data
type for this field.
1503
Only selection data types can be displayed using checkboxes (defaulting to text).
Error
You requested a field type of check box for a field that is not a selection field. Only selection type
fields can have a field type of check box. The field type for this field is text. If a text field type is
acceptable, you can ignore this message. Otherwise, specify a field type appropriate for the data
type of the field.
1504
Only selection data types can be displayed using exclusive choice boxes (defaulting to text).
Error
You requested a field type of exclusive choice (option buttons in UNIX) for a field that is not a
selection field. Only selection type fields can have a field type of exclusive choice. The field type
was changed to text for this field. If a text field type is acceptable, you can ignore this message.
Otherwise, specify a field type appropriate for the data type of the field.
95

Number
Description
1505
Unrecognized field type (defaulting to text).
Error
You specified an unrecognized field type for a field. The field type was changed to text for this
field. If a text field type is acceptable, you can ignore this message. Otherwise, specify a field type
appropriate for the data type of the field.
1506
Cannot create new field.
Error
An error occurred while the system tried to create a field on the form. This error usually indicates
a serious resource shortage for the application. Treat the error like an Out of memory error (see
error message 1500).
1507
View file format error: invalid form name.
Error
The form name found in the view file does not match the name of the form in the definition file.
The view file will be deleted and reloaded the next time you access the form.
1508
View file format error: missing form name.
Error
The view file for the form does not have a form name. The view file will be deleted and reloaded
the next time you access the form.
1509
View file format error: field clause.
Error
Because a field clause was not found where expected in the view file, the format of the view file
is unexpected. The view file will be deleted and reloaded the next time you access the form.
1510
View file format error: field definition.
Error
Because an invalid clause was found in a field definition in the view file, the format of the view
file is unexpected. The view file will be deleted and reloaded the next time you access the form.
1511
View file format error: invalid form or active link end.
Error
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. The view file will be deleted and reloaded the
next time you access the form.
1512
View file format error: begin active link.
Error
The only information expected after the end clause of a form is the definition of active links. When
the file contents after the end clause were processed, an entry was found that was not the start of
an active link. Therefore, the format of the view file is unexpected. The view will be deleted and
reloaded the next time you access the form.
1513
View file format error: active link definition.
Error
Because an invalid clause was found in an active link definition in the view file, the format of the
view file is unexpected. The view file will be deleted and reloaded the next time you access the
form.
1515
Definition file format error: invalid form name.
Error
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.
1516
Definition file format error: missing form name.
Error
The definition file for the form does not have a form name. The definition file will be deleted and
1517
Definition file format error: field clause.
Error
Because a field clause was not found where expected in the definition file, the format of the
definition file is unexpected. The definition file will be deleted and reloaded the next time you
access the form.
96
AR System messages

Number
Description
1518
Definition file format error: field definition.
Error
Because an invalid clause was found in a field definition in the definition file, the format of the
access the form.
1519
Definition file format error: character menus.
Error
An error occurred with the definition of a character menu. Because a menu definition that tries to
jump more than one level in the menu hierarchy is in the file, the format of the definition file is
unexpected. The definition file will be deleted and reloaded the next time you access the form.
1520
Definition file format error: invalid form or active link end.
Error
Because the end clause of a form or active link definition was not found where expected in the
definition file, the format of the definition file is unexpected. The definition file will be deleted and
1521
Definition file format error: begin active link.
Error
The only information expected after the end clause of a form is the definition of active links or of
character menus. When processing the file contents after the end clause, an entry was found that
was not the start of an active link and also not a character menu. Therefore, the format of the
access the form.
1522
Definition file format error: active link.
Error
Because an invalid clause was found in an active link definition in the definition file, the format
of the definition file is unexpected. The definition file will be deleted and reloaded the next time
you access the form.
1524
Unrecognized selection value.
Error
The specified selection value is not a legal selection value for the field. View the definition for the
field to verify the legal values. Remember, selection values are case-sensitive.
1525
Total number of lines between margins less than minimum of five.
Error
The total number of lines on the page between the top and bottom margins is fewer than the
minimum of five lines. A report requires space for at least five lines of text on the page. 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. Increase the page size, or decrease the size of the top or bottom margin so that
the total space available is at least five lines.
1526
Total number of characters per line between margins less than minimum of 40.
Error
The total number of spaces on the page between the right and left margins is fewer than the
minimum of 40 characters. A report requires space for at least 40 characters of text on a single line.
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. Increase the line length, or decrease the size of the right or left margin
so that the total space available is at least 40 characters.
1527
Total number of characters per line including margins is greater than maximum of 4096.
Error
A report cannot have lines with more than 4096 characters of text. Decrease the line length so that
the total space available is no more than 4096 characters.
1528
Column headers will not fit within the space defined between top and bottom margins - total
number of lines increased to the following value.
Error
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. 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.
97

Number
Description
1529
Status field is not accessible - cannot display Status History.
Error
No reference to a Status field can be found for this form. Accordingly, you cannot display Status
History information. This is an unexpected error.
1530
Update of custom operation failed.
Error
The update of the custom operation failed. 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.
1531
X, Y, or both, coordinates are out of range.
Error
The X or Y coordinate value specified is out of the legal range for the coordinate. The X coordinate
must be between 0 and 1500 inclusive, and the Y coordinate must be between 0 and 3000 inclusive.
Change the value of the X and Y parameters.
1533
Cannot format diary entry.
Error
An error occurred while formatting the diary text for a field. An associated error message contains
details.
1534
Must specify a user name.
Error
To log in, specify a user name. You can dismiss this window without changing the login
information for the current user. To change the login information, specify a user name.
1535
Cannot query servers.
Error
An error occurred while the system tried to create a list of the forms available from each of the
connected servers. An associated error message contains details.
1536
Supply a name for your macro or custom report.
Error
You requested that a macro or custom report be saved. However, you did not specify a name for
the operation. If you are saving a new operation, specify a new name in the Name field. If you are
saving an updated macro or custom report under an existing name, specify the name you are
updating, and click Continue when the prompt warning of duplicate names appears.
1539
You cannot specify a COUNT operation with a column layout without specifying a field name.
Error
You requested a count statistic with a column layout without specifying a field name to count on.
The field name is used to determine which column to display the result under in a column-style,
statistic result. Specify the field name to identify which column the result is printed under.
1540
Attempt to create macro or custom report failed - file system error.
Error
The file system could not create or write to the file holding the definition of the operation. An
1541
You have entered an improperly formatted value for a date/time field. The format of the time
value is not recognized.
Error
The value was entered in a field with a data type of date/time. The value is not a legal time value.
Change the value to a legal time value, and retry the operation.
1543
A field name is required for all operations except COUNT.
Error
All statistics operations except COUNT require a field name. This name specifies the field on
which the operation is performed. Specify the name of the field (or arithmetic operation) on which
the operation is performed.
98
AR System messages

Number
Description
1544
Value specified for field name not numeric or not a field.
Error
The value specified for the field name must be a field defined for the form, a numeric value, or
one of the numeric or date keywords. These are the only types of definitions allowed in the field
name for a statistical operation. Make sure that the spelling is correct, and update the field name
request to be a legal operation.
1545
You have entered an improperly formatted value for a real field.
Error
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. Change the value to a legal real value, and retry the operation.
1546
You entered a nondigit character for a numeric field.
Error
A numeric field contains a nondigit value. You can specify digits only for integer (numeric) fields.
Change the value to a legal integer value, and retry the operation.
1547
You entered a value for a numeric field that is either smaller than the minimum size allowed
or larger than the maximum size allowed.
Error
The value you specified for the numeric field is either smaller than the minimum size or larger
than the maximum size. Use BMC Remedy Developer Studio to confirm the size limits of the field
properties.
1548
You have entered an improperly formatted value for a decimal field.
Error
The value was entered in a field with a data type of decimal. The value is not a legal decimal value.
Change the value to a legal decimal value, and retry the operation.
1549
Modify All operation failed during operation on request with ID number.
Error
An error occurred in this request during a Modify All operation. All requests with IDs previous
to the specified ID (in the sort order) were updated, and all requests with IDs after the specified
ID are unchanged. An associated error message contains details. Fix the problem, and retry the
operation.
1550
No macros are defined.
Error
Because no macros are defined, you cannot run or edit a macro. Before you open the Select Macro
or Edit Macros windows, define one or more macros.
1553
You cannot locate the selected command.
Error
The requested user command cannot be found. If you are selecting the command interactively, the
command was probably deleted or moved by another user after you started the program. If you
are selecting the command from a macro, the command was probably deleted after the macro was
recorded.
1555
Enter a command name.
Error
You requested that a user command be saved. However, you did not specify a name for the
operation. If you are saving a new command, specify a new name in the Name field. If you are
saving an updated command under an existing name, specify the name you are updating, and
then click Continue when the prompt warning of duplicate names is issued.
1557
Enter a command string to execute.
Error
You requested that a user command be saved. However, you did not specify a command to be
performed for the operation. Specify the command you want to be executed when this user
command is performed, and then save the user command.
1558
Cannot create user command - file system error.
Error
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. An associated error message
contains details.
99

Number
Description
1559
Error in macro or custom report.
Error
An error occurred while the system tried to perform the operation specified in the macro or
custom report. You might get this message for the following reasons:
The macro or custom report does not exist. It might have been deleted or moved to a new
location. Or a macro might run another macro as one of the operations it performs, and that
embedded macro does not exist.
The format of the file holding the macro or custom report does not match the expected format.
A common cause is a missing end statement or incorrect formatting of one of the command
lines. The macro and custom report files cannot be edited.
Rerecord the macro or custom report operation.

1562
Second part of report operation missing or invalid.
Error
The report operation in a macro consists of several commands. The second part of the command
that provides the destination for the report is missing or is not recognized. This is a specific case
of Error 1559, Error in macro or custom report.
1563
Enter a directory to store the command in.
Error
You requested that a user command be saved. However, you did not specify a directory in which
to store the operation. If you are saving a new operation, specify a new name in the name field.
Specify the directory to store this user command definition in.
1565
Second part of statistics operation missing or invalid.
Error
The statistics operation in a macro consists of several commands. The second part of the command
that provides the destination for the statistics result is missing or is not recognized. This is a
specific case of Error 1559, Error in macro or custom report.
1566
No custom report formats are defined.
Error
Because no custom reports are defined, you cannot manage a custom report. Before opening the
Manage Custom Reports window, define one or more custom reports.
1567
Unrecognized operation detected while loading a custom report format.
Error
An unrecognized operation was detected in the custom report definition. A custom report
definition can contain only operations related to a custom report. 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.
1569
Empty macro definition.
Error
You are trying to save a macro that has no commands defined for it. You cannot create a macro
that does not perform an operation. Make sure that the correct options are set on the Stop
Recording window. If they are correct, you did not perform any operations after you started
recording. Perform the operations you want to record before saving the macro.
1572
You cannot create new item.
Error
An error occurred while the system tried to create the new definition on the Customize View
window. An associated error message provides details. Usually, a lack of system resources causes
the error.
1574
Filename is longer than maximum allowed.
Error
The file name specified is too long. The maximum size for a file name is 255 characters, including
the directory path and the name of the file. The file specified for this operation is longer than this
maximum. Define a file name that fits within the size limit.
100
AR System messages

Number
Description
1579
You cannot use a selection value name in Status History - you do not have access to the Status
field.
Error
You do not have access to the Status field for this form. Accordingly, you cannot use a status
selection value name as the middle portion of a Status History reference. To reference a specific
Status History value for this form, use the 0-based selection index for the selection value you
require.
1580
Missing closing quotation mark on a character string or name.
Error
A field name or character string has an opening quotation mark as required, but no corresponding
closing quotation mark is at the end of the string. Supply the closing quotation mark. If the name
or string contains a quotation mark that is the same type of quotation mark around the value,
double the embedded quotation mark.
1581
Unexpected character at this location in the search line.
Error
A parsing error was detected in the search line. This message indicates that an error occurred and
shows the portion of the string containing the error with a caret marking the location. The error is
usually at or just before the marked position. Fix the problem, and perform the search again.
1582
Logical operator expected at this position.
Error
The only legal operator at this position in a search line is a logical operator (AND, OR, or NOT).
Fix the format of the line, and perform the search again.
1583
Relational operator expected at this position.
Error
The only legal operator at this position in a search line is a relational operator (=, !=, <, <=, >, >=,
or LIKE). Fix the format of the line, and perform the search again.
1584
Field or value expected at this position.
Error
At this position in a search line, a field reference or value is expected. Fix the format of the line,
and perform the search again.
1585
Too many nested levels of parentheses in command.
Error
This position in the search line has too many open parentheses (up to 64 open parentheses can be
active in the search line). The search operation is too complexuse fewer levels of nested
operations. Fix the format of the line, and perform the search again.
1586
Closing parenthesis expected at this position.
Error
A closing parenthesis to match an open parenthesis specified in this command was expected at
this position. The command must have a balanced number of parentheses. Fix the format of the
line, and perform the search again.
1587
Unknown field referenced in search line.
Error
The field referenced in the search line is not a recognized field on the current form. 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.
1588
Value specified for selection is not one of the defined values for this field.
Error
101

Number
Description
1589
Format for status history reference is invalid.
Error
The format of a status history reference is incorrect. A reference must be the name or ID of the
Status History field, followed by a period, followed by the name or index (0-based) of the status
selection value, followed by a period followed by the keyword or index of a user or time reference
(for example, Status-History.Fixed.TIME or 15.2.1). Fix the format of the line, and perform
the search again.
1590
Format of date or time value is not recognized.
Error
The format of a time value is unrecognized. You can omit the time portion of a time stamp and
include only the date, or you can omit the date and include only the time. The portion omitted
defaults to an appropriate value. However, the format of the portion of time specified must match
the rules for time stamps. Fix the format of the line, and perform the search again.
1592
You cannot translate the group name in the Group List or Assignee Group field.
Error
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. Verify the
spelling, capitalization, and spacing of the name to make sure it is one of the legal group names.
1593
Must specify a filename.
Error
1594
Unrecognized import file type.
Error
1595
Format of contents of import file inconsistent with format type.
Error
1596
Import operation terminated on data row.
Error
1597
Import operation failed (but continuing) on data row.
Error
1598
Error
This application cannot customize the views of AR System forms created with versions prior
to 3.0. Such views can be customized by using previous versions of this application.
1600
Overflow while expanding active link process (maximum expanded command is 4096 bytes).
Error
Overflow occurred while expanding the command line for an active link. This could be the
command line for a Run Process action or for a $PROCESS$ operation in a Set Fields action. In
either case, the command line contains more than the maximum of 4096 characters after
expansion. Review the definition to make sure that the correct values are being specified.
1601
Overflow while expanding active link macro parameter (maximum expanded parameter is 4096
bytes).
Error
Overflow occurred while substituting a parameter value for a macro parameter in a Run Macro
action for an active link. When a parameter contains data that expands, the maximum expansion
of the values is 4096 characters. Revise the parameter values that are passed to be fewer than 4096
characters.
1602
Error
No item matches active link conditions; this operation has been defined so that no match
generates an error.
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. The administrator configured the action to
return an error if no matches were found.
102
AR System messages

Number
Description
1603
Set fields active link running a process failed.
Error
The process that was run to get a value for a field failed. An associated error message contains
1604
Active link attempting to set nonexistent menu - resetting to the default menu.
Error
An active link specified a new character menu for a field. However, the specified character menu
is not defined. The character menu for the field is being reset to the default menu for the field. Fix
the active link to see an existing character menu, or create the character menu needed by this
active link.
1605
Active link trying to set nonexistent field.
Error
An active link specified a new character menu for a field that does not exist. Fix the active link to
see an existing field for the form, or remove the active link.
1606
No user commands are defined.
Error
Because no user commands are defined, you cannot run or edit a user command. Before opening
the Select User Commands window, define one or more user commands.
1607
No administrator commands are defined.
Error
1608
Value exceeded report maximum length.
Error
A value exceeded the maximum size of a value that is allowed in a report. Because the value will
overflow the internal buffers used for reporting, it cannot be included in the report. Specify a
report that excludes the long field, and re-create the report.
1609
The statistic operation is too complex - it references more than 50 distinct fields.
Error
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. Simplify the statistics you are gathering, or divide the report into several
pieces, each of which references 50 or fewer fields in the statistical operations.
1610
You must set the environment variable ARHELP to point to the help directory. This is usually
the directory named help under the AR System install directory.
Error
To use the Help system under the UNIX environment, set the environment variable ARHELP to
point to the directory containing the Help files for the AR System.
1611
Found more entries than expected during workflow processing.
Error
An active link action was extracting data from another form or table in the database and
encountered multiple rows that matched the search criteria. The administrator configured the
action to return an error if multiple matches were found.
1612
Source used in Push Fields active link not allowed: PROCESS, DDE, or SQL.
Error
In a Push Fields active link action, the source expression cannot contain $PROCESS$, $DDE$, or
$SQL$. Data from these sources cannot be incorporated into a Push Fields source expression.
1613
An internal error has occurred during workflow processing.
Error
Unexpected, incorrect, or inaccurate definitions were encountered during processing. This

indicates a corrupted or incomplete definition. This message is usually accompanied by error
messages that explain the failure.
1614
Pick List was cancelled - Set Field active link has failed.
Error
103

Number
Description
1620
Cannot find this macro name in macro list.
Error
You tried to access a macro that is not found in the macro list. To continue, verify that the macro
exists.
1621
Not all entries are displayed in the selection list.
Error
The selection list opened by an active link operation contains more items than can be displayed.
The list contains the first 6000 matching items.
1622
An error occurred while updating the server. View has not been saved.
Error
During an export view operation, an error occurred while the system tried to update the view
definition on the server. A message preceding this message contains details.
1623
Unable to Export View.
Error
1624
Cannot access the active link debug file.
Error
Active link debugging is active. An error occurred when the system tried to open, close, or write
to the active link debug file. An associated message contains details.
1625
Reporting to an external report writer is supported on the Windows platform only.
Error
A macro specified that a report is to be generated to an external report writer. This functionality
is supported only on the Windows environment.
1626
Cannot generate a report to file or to application when using an external report writer.
Error
1627
The type of external report specified is not recognized.
Error
1628
A filename is required when generating a report to an external report writer.
Error
1629
Too many windows are open. Close some windows before opening another.
Error
Insufficient memory is available to open additional windows or applications.
1630
Your window resources are low; close unwanted windows or applications.
Error
Insufficient memory is available to perform basic BMC Remedy User functions. For example, you
cannot access a form because not enough memory resources exist to open it.
1650
Servers with versions earlier than 3.0 are not supported by this client.
Error
BMC Remedy User version 4.0 or later tried to connect to a pre-3.0 AR System server. Only
version 3.0 or later AR System servers can be used by BMC Remedy User version 4.0 or later.
1651
Incorrect format in the definition file.
Error
BMC Remedy User generated this error message while loading a form. It usually indicates that
the cached form definition files (the .arv and .arf files) contain unexpected content.
1653
Unable to read the recent search file.
Error
The system cannot read the recent search file. Try using the advanced search capabilities of
BMC Remedy User.
1654
Unable to read the saved search file.
Error
The system cannot read the saved search file. Try using the advanced search capabilities of
BMC Remedy User.
1655
Unable to write the recent search file.
Error
The system cannot save the recent search file. Reformat your search to continue.
104
AR System messages

Number
Description
1656
Unable to write the saved search file.
Error
The system cannot save the search file. Reformat your search to continue.
1657
AR System Report.
Error
1658
Error occurred in generating report.
Error
This message appears when an error occurs during report generation. Click Show Details in the
message box for more information.
1659
No report or an incomplete report will be generated.
Error
This message appears as a hint in the error message box when a report error occurs. Click Show
Details in the message box for more information.
1660
Login macro action is not supported.
Error
You cannot record a macro that logs in to an AR System server. This action is not supported.
1661
One or more items match active link conditionsthis operation has been defined so that any
match generates an error.
Error
Used by the Push Fields action when the administrator configures it to return an error when
multiple matches are found. On the If Action page, the If Any Requests Match field has Display
Any Match Error selected.
1662
Run Macro was not executed because the macro contains statements that are not supported.
Warning
In ARWeb 4.0, not all macro statements are supported. If the macro cannot be executed, this
statement is displayed.
BMC Remedy User errors

1800
Internal error - unable to create form information.
Error
Insufficient memory is available to allocate the form information structure. Close some open
windows or applications, and log in again.
1801
Unable to connect to any servers.
Error
To operate BMC Remedy User, you need access to at least one server. Make sure that you have a
network connection to a server and that it is running properly.
1802
You cannot create directory directoryName.
Error
While storing a macro or report, BMC Remedy User failed to create a missing command directory
on the local disk.
1803
Cannot open file fileName.
Error
BMC Remedy User could not open or create a printer setup file for a custom report.
1805
System out of memory, executable file was corrupt, or relocation was invalid.
Error
During a Run Process active link action, WinExec returned Error 0.
1806
Executable not found.
Error
1807
Path not found.
Error
1808
Insufficient memory to start application.
Error
105

Number
Description
1809
Invalid executable file format.
Error
1810
Incorrect version of Windows software.
Error
1811
Sharing or network protection error.
Error
1812
Application designed for different operating system.
Error
1813
Application developed for older version of Windows software.
Error
1814
Attempted to load second instance of application.
Error
1815
Attempted to load compressed executable.
Error
1816
Application designed for MS-DOS 4.0.
Error
1817
Unknown executable format.
Error
1818
Invalid dynamic-link library.
Error
1819
Application requires Windows 32-bit extensions.
Error
1820
Unknown error - error code = errorCode.
Error
During a Run Process active link action, WinExec returned an unknown error code.
1821
WinExec failed for actionType.
Error
During a Run Process active link action, WinExec failed. Another error message documents the
cause of failure.
1823
Failed to display all or some of the notification messages.
Error
BMC Remedy User could not retrieve notification information from the Alert client. In general,
this is because the Alert client is not responding.
1825
Unable to load Submit form.
Error
Form information was not loaded. The form definition files might be unavailable or corrupt.
1826
Unable to load Query form.
Error
Form information could not be loaded. The form definition files might be unavailable or corrupt.
1827
Unable to load Customize Default form.
Error
1828
Unable to load Customize View form.
Error
106
AR System messages

Number
Description
1829
Internal error - invalid window description.
Error
An MDI child window could not be created because an internal windows function provided an
unexpected result that was detected during window creation.
1830
Internal error - invalid window description.
Error
An MDI child window could not be created because an internal windows function provided an
unexpected result that was detected during window creation.
1831
Failed to create the dialog box.
Error
The status history modeless dialog box could not be created because of a Windows error.
1832
Memory failure - cannot initialize the current statistics information.
Error
BMC Remedy User ran out of memory while building the statistics list for the statistics report
window.
1833
Invalid field name - attempt the operation again.
Error
You entered an invalid field name in the report sort dialog box.
1834
Failed to create the AR System home directory directoryName.
Error
Could not create an AR System home directory while updating user login or server information.
This usually indicates a serious disk problem.
1835
Internal error (1).
Error
An internal Windows error occurred while updating user login information. Specifically,
Windows provided an invalid LB index. This usually indicates a serious Windows error.
1836
Internal error (2).
Error
An internal Windows error occurred while updating user login information. Specifically,
Windows returned an LB error. This usually indicates a serious Windows error.
1837
Failed to create memory.
Error
BMC Remedy User ran out of memory while building the user information list when updating the
login information window.
1838
Internal Error - unable to initialize user information.
Error
Initialization of the user information in uiroot failed during user login.
1839
Internal Error - unable to create form information.
Error
BMC Remedy User ran out of memory while allocating the schemaInfo structure during user
login.
1840
The X location and width of the symbol is greater than 1500.
Error
The X location of a field was made greater than 1500 in the Display Attributes dialog box.
1841
The Y location and height of the symbol is greater than 3000.
Error
The Y location of a field was made greater than 3000 in the Display Attributes dialog box.
1842
Failed to display the report.
Error
The report to file or screen failed to generate.
1843
Failed to get printer information.
Error
Printer driver initialization for the printer selected in printer setup failed while printing a report.
1844
Report to file failed. Ensure that you have enough disk space.
Error
BMC Remedy User could not open the specified report output file.
107

Number
Description
1847
Failed to create the user home directory directoryName.
Error
Creation of a home directory for the last user failed during application startup. This usually
indicates a serious disk problem.
1848
The user home directory in the ARuser section of the win.ini file cannot be located.
Error
A home directory path was not found in the win.ini file for the last user logged in to AR System.
This condition is detected during application startup.
1849
Not enough memory to initialize font.
Error
BMC Remedy User ran out of memory while building the font preference structure when
changing AR System font preferences.
1850
Not enough memory to initialize all fonts.
Error
BMC Remedy User ran out of memory while building the font preference structures during font
preference dialog box initialization.
1852
Action Request System requires Windows enhanced mode.
Error
During application startup, it was detected that Windows is not running in enhanced mode.
1853
The working directory should be the same as the program path in File -> Properties.
Error
During application startup, the Windows working directory was not set to the AR System
application directory.
1854
Failed to initialize the system globals.
Error
During application startup, BMC Remedy User globals could not be initialized. This usually
indicates a serious Windows error.
1855
Failed to initialize the user information.
Error
During application startup, BMC Remedy User could not initialize user information lists (macros,
reports, and so on) because memory allocations for lists failed. This usually indicates a serious
Windows error.
1856
Unable to register window class.
Error
You encountered an unusual error condition.
1857
Unable to register submit window class.
Error
1858
Unable to register query window class.
Error
1859
Unable to register child window class.
Error
1860
Unable to register queryList window class.
Error
1861
Unable to register report window class.
Error
1862
Unable to register custom windows class.
Error
1863
Unable to register customize view class.
Error
108
AR System messages

Number
Description
1864
Unable to register customize default class.
Error
1865
Unable to register text viewer window class.
Error
1866
Unable to register text view class.
Error
1867
Unable to register Dialog2 class.
Error
1868
Unable to create frame.
Error
Creation of the MDI frame window failed during BMC Remedy User startup. This usually
indicates a serious Windows error.
1869
Unable to initialize APIs.
Error
Windows API initialization failed during BMC Remedy User startup. This usually indicates a
serious Windows error.
1870
Unable to load the menu accelerators.
Error
BMC Remedy User for Windows failed to load menu accelerator tables during startup.
1871
Failed to initialize DDE.
Error
DDE API failed during BMC Remedy User startup.
1875
Internal Error - unable to create form information.
Error
BMC Remedy User ran out of memory while allocating the schemaInfo structure during
startup.
1876
Internal Error - LoadIniFile.
Error
User or password data is incorrect or irretrievable from win.ini file during BMC Remedy User
startup.
1877
Unable to load Submit form: formName.
Error
1878
Unable to load Query form: formName.
Error
1879
Failed to connect to application DDEApplicationName using specifiedDDEPath path.
Error
DDE connection failed due to incorrect application file path setting.
1880
Invalid DDE action specified.
Error
DDE action other than EXECUTE, POKE, or REQUEST DDE action was specified.
1881
Set Fields active link running a process through DDE failed.
Error
A DDE-invoked process failed and did not provide data to be used as the source of a Set Fields
active link.
1882
The DDE application name is not defined in dde.ini file.
Error
DDE Target application entry was not found in the dde.ini file while building DDE file
specification for a DDE operation.
109

Number
Description
1883
The format for the application section in dde.ini is invalid - you can specify only CSV or TAB
for format.
Error
While reporting to an application, the DDE entry for the target application in the dde.ini file
does not specify CSV or TAB format.
1884
The item item is missing from application section section in dde.ini.
Error
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.
1885
Memory allocation failure during DDE process.
Error
BMC Remedy User ran out of memory while allocating memory to support a DDE action.
1886
Error in reading the GetDetails Information for list item number item.
Error
While processing a notification get details DDE request, the specified item could not be found in
the notification application.
1887
Grid width and height must be between 2 and 128.
Error
The customize view grid width and height parameters are not within the allowed range.
1888
Blanks and spaces are invalid in a view name.
Error
No description.
1889
Date is out of allowed range of 01/01/1970 - 01/19/2038 (GMT) for Windows client.
Error
If you enter a date outside of the listed range, based on Greenwich Mean Time (GMT), you receive
this error message. GMT is the time zone from which all other time zones are adjusted.
This error also appears for dates that are within the hour that the time changes for the start of
daylight saving time.
1890
Error
Currently running MISCDLL.DLL version oldVersionNumber is an old version. Version

currentVersionNumber of MISCDLL.DLL is required.
This might be the result of installing an older version of BMC Remedy User in the same directory
as a newer version.
Reinstall the latest version of the BMC Remedy User.
1891
Time is out of allowed range of number and number.
Error
AR System cannot process a time that is out of range. Try again, using a time within the allowed
range.
1892
Date and time are out of allowed range of number through number.
Error
AR System cannot process dates and times that are out of range. Try again, using a date and time
within the allowed range.
1893
Cannot perform this operation in the current mode of the form.
Error
AR System cannot perform this operation in the current mode of the form. Try again with a
different mode of the form.
1894
The system is out of memory or resources.
Error
The system is out of memory or resources while running active links. Terminate unused
applications to make system resources available.
1895
JavaScript functionality is not supported on this platform.
Error
110
AR System messages

Number
Description
1896
You have entered an improperly formatted value for a currency field.
Error
A currency value was created with an incorrect format. You can enter the currency decimal value
and currency code directly into the field, or enter the decimal value and select a currency code
from the list. If you specify only a decimal value, the Primary Allowable currency type is used.
1897
Date is out of allowed range of 01/01/4713 B.C. - 01/01/9999 A.D.
Error
A date value was entered that is out of range. Date fields can accept values from January 1, 4713
B.C.E. to January 1, 9999.
1898
There is no Home Page form available. Please verify your user preferences or check with your
administrator.
Warning
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 Preference form cannot be found.
Verify that you entered a valid AR System server and form name in your BMC Remedy User
options, or contact your AR System administrator for assistance.
1899
Cannot retrieve starting active link: activeLinkName.
Error
An error occurred while loading the starting active link for an entry point guide. Contact your
AR System administrator for assistance.
1900
Error generating application list field content.
Error
An error occurred while generating the dynamic content for the Application List field. Contact
1901
entryPoint is not a valid entry point.
Error
The entry point chosen from File > Recent Entry Points and the form or guide is no longer a valid
entry point.
1902
You have entered an invalid currency type.
Error
The specified currency value is a not an allowable currency type. Contact your AR System
administrator.
1903
Function error in active link. Please verify number of function arguments and data types.
Error
One of the following errors occurred in a function used in an active link:
The number of parameters passed to the function did not match the number expected.
A parameter that requires a value had a NULL or unknown value.
A parameter had an incorrect value type. For example, a character value was passed when an
integer value was required.
A parameter had an incorrect field type. For example, the function requires a table field, but a
character field was specified at design time.
To troubleshoot this error, check the workflow log to identify the active link and the action in
which the error occurred (for information about workflow logging, see the Optimizing and
Troubleshooting Guide). Analyze the action for inconsistencies between the values specified for its
function parameters at design time and the values expected at runtime.
1904
An error occurred while generating the Crystal report: CrystalReportsError.
Error
See your Crystal Reports documentation for more information.
1905
numberString - ODBC data source: source.
Error
An invalid ODBC data source was found, or an error occurred when connecting to the specified
ODBC data source.
111

Number
Description
1906
errorNumber - CrystalReportsError.
Error
This is a Crystal Reports Engine exception. See your Crystal Reports documentation for more
information.
1907
Error generating navigation bar field content.
Error
An error occurred while generating content for the navigation bar field.
1908
Report to file failed. Ensure the directory does exist.
Error
1909
Required field (without a default) not specified.
Error
During submission of a request, no value was supplied for the required field. The field does not
have a default value, so a value must be supplied during the submit operation.
Perform one of these actions:

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.
This message was produced by either the mid tier or BMC Remedy User.
1925
Failed to create the window.
Error
Could not create a child window. The client might have a resource or memory limit.
1926
Unable to initialize frame.
Error
Creation of the main MFC frame failed during BMC Remedy User startup. This usually indicates
a serious Windows error.
1930
Login aborted. You cannot close all windows.
Error
The login was aborted because all open windows could not be closed.
1950
Error loading menu.
Error
Character menu expansion failed in the symbols library; the menu did not load. This is often
caused by a lack of space in the Windows resource heap when loading large menus.
1951
Failure trying to expand character menu.
Error
Character menu expansion failed in the symbols library; the menu did not load.
1952
Unable to load menu.
Error
Indicates a serious problem with menu loading.
1953
Error getting group information.
Error
BMC Remedy User failed to get the group list from the server.
1954
Failure loading group information.
Error
Group list expansion failed while the system tried to build the group list.
1955
Error creating a menu - menu too large.
Error
Adding a submenu to a menu failed and resulted in a Windows error.
1957
Unable to write to file fileName.
Error
The field editor could not open a file with write permissions.
1958
Unable to read file fileName.
Error
The field editor could not open a file with read permissions.
1959
Unable to create work buffer for file fileName.
Error
Allocation of global memory failed while performing edit operations.
112
AR System messages

Number
Description
1960
Can not write file fileName to disk.
Error
Writing to a file failed in the field editor.
1961
You are trying to access a menu with more than numberOfEntries entries - the menu will be
truncated.
Error
The number of items returned for a menu load exceeded the maximum allowed.
1962
Error creating menu - out of resources.
Error
Failed to build the Windows popup menu. The application resource memory area is probably full.
1963
Unable to load help.
Error
Windows Help system failed to load. This is usually caused by the failure to create a temporary
file.
1964
Unable to commit changes.
Error
Cannot commit changes to a dialog box or to a submit or a modify record action.
1965
Functions MAX and MIN are not supported in Push Fields actions.
Error
Functions MAX and MIN are not supported in Push Fields actions. Push Fields actions provide
little information about the destination field. Without knowledge of the destination data type,
these two functions cannot be evaluated correctly.
1966
Failed to initialize MAPI mail.
Error
The MAPI mail system failed to initialize when sending an AR System object to a mail recipient.
The failure usually indicates an incorrectly installed mail system.
1967
Send Mail failed. The message was not sent.
Error
The MAPI mail system failed to send the mail when sending an AR System object to a mail
recipient.
1968
Due to the length limit of the SQL command by Crystal Reporting Engine, only the first number
entries are reported.
Warning
The Crystal Report Engine returned less data than requested.

1969
The Crystal report contains an invalid SQL statement.
Error
The SQL command passed to the Crystal Reporting Engine is invalid. Verify the syntax in the SQL
command.
1970
The report format is reset to Record.
Warning
The report type is being reset to Record mode.
1971
Too many columns (fields). Ensure that all column titles fit into one report line.
Error
Too many fields were selected in a Column type report.
1972
The specified directory is not valid.
Error
The directory specified in a file path is invalid. The directory might not exist or the user may not
have access rights.
1973
Failed to save file fileName.
Error
An I/O error occurred while generating a report to file.
1974
One or more active links failed when closing the form. Do you still want to exit the application?
Note
When exiting BMC Remedy User, an active link failed on window close. This note gives the user
a chance to abort BMC Remedy User termination.
113

Number
Description
1975
Report will not be displayed in specified external program because of the following error:
errorType.
Error
An external viewer (such as Crystal Reports) failed to open during the print preview operation.
1976
The given directory does not exist. Create the new directory?
Warning
The directory specified while saving a macro does not exist.
1977
The directory cannot be created.
Error
The directory specified while saving a macro cannot be created. This is likely caused by a file
system error.
1978
The given directory does not exist in the search path. Add the new directory?
Warning
The directory specified does not exist.
1979
A printer error occurred. Verify the printer setup on your system.
Error
A report cannot be printed. This is usually caused by problems with your printer setup or with
cables.
1980
A printer error occurred. The default page setup is used.
Error
Page setup could not be determined, so printer defaults are being used.
1986
Error
You entered an invalid currency value on a currency field. For example, you entered 1,00 USD.
BMC Remedy Administrator errors and warnings (release 7.1.00 and earlier only)
2001
Cannot allocate memory.
Error
when too many processes are running or when some processes grow to occupy most or all
available memory on the client. Recover the memory by shutting down unneeded processes or by
restarting processes that have been running for a while.
2002
Cannot read the configuration file ARHOME environment variable may be set incorrectly.
Error
The UNIX configuration file (config) is missing, or the permission settings are such that you
cannot access it. Make sure that ARHOME is correctly set and that you can read and write to the
config file, and then restart the tool.
2003
Cannot connect to the X server.
Error
The aradmin program (BMC Remedy Administrator) on UNIX is an X program. It requires that
an X windowing system be running to allow the program to operate. No window system is
running in your environment. Start a windowing system, and then restart the aradmin program.
2004
Cannot initialize the AR System.
Error
Failure occurred during a call to initialize AR System client environment. An associated error
message contains details. Fix the problem, and restart the tool.
2005
No servers are currently accessible.
Error
None of the servers specified in BMC Remedy Administrator are accessible. Associated error
messages provide information about why the tool could not connect. Fix the problem, and retry
the operation.
2006
Failure while retrieving entries from the server directory file.
Error
An error occurred while the system retrieved entries from the server directory file. 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, /etc/ar (UNIX) or \ARHomeDir\ar (Windows).
114
AR System messages

Number
Description
2009
No servers are specified on the command line or in the AR System directory file.
Error
On UNIX, if you used the -x command-line option to identify one or more servers, the system
could not connect to any of the specified servers. BMC Remedy Administrator cannot start
without a server to connect to.
If you did not use the -x command-line option or are using Windows, the AR System directory
file is empty or contains references to inaccessible servers.
2100
You have specified a field ID within the reserved range.
Error
You tried to assign an ID number to a form field, but that field number is within the range of
reserved fields (100 to 536868911) in AR System. You can create a field in this range, but be aware
that the field might have a special meaning. If you are creating this field to have the special
meaning, ignore this message and proceed. If you do not want to create a specific reserved field,
choose an ID outside of the reserved range (greater than or equal to 536868912).
If you are running BMC Remedy Administrator, leave the field ID blank to automatically generate
an available ID outside the reserved range.
2101
Your filter definition and all associated actions will be deleted.
Error
You are deleting a filter. A Delete operation removes the definition and the workflow associated
with the definition. If you proceed, the definition is removed. If you cancel, the operation is
terminated, and the definition is retained.
2102
No structures are in the import file.
Error
You specified a file to use during an Import operation. When trying to load this file, the tool did
not find any AR System structure definitions in the file. This means that nothing exists to import.
Make sure you specified the correct name for the file that you are trying to import.
The import operation in BMC Remedy Administrator is used for structure definitions only. If you
are trying to import data, use BMC Remedy Data Import.
2103
Incorrect parameter specification check field name spelling.
Error
When specifying a field reference using the field name, the system could not find a field with the
specified name for the current form. Fix the spelling of the field name in the reference, and make
sure that the field exists for the target form.
2104
You have not saved changes on this screenthey will be lost if you continue.
Error
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.
2105
Your administrator command definition will be deleted.
Error
2107
Your form definition and all associated data will be deleted.
Error
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.
2109
Your active link definition and all associated actions will be deleted.
Error
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.
115

Number
Description
2112
Language defined by LANG environment variable not recognized using default on server.
Warning
The language defined in the LANG environment variable is not recognized by AR System. The
default language of the server is used instead.
2114
The following field labels are duplicated in your form.
Warning
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.
2115
Changes on the following screens will be lost if you continue.
Warning
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.
2117
Your menu definition will be deleted.
Warning
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.
2119
The following fields (including data) and/or active links will be deleted.
Warning
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.
2120
Additional errors were truncated.
Note
The operation encountered a number of errorstoo 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.
2121
Your filter action will be deleted.
Warning
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.
2122
Your active link action will be deleted.
Warning
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.
2123
Your form view will be deleted.
Warning
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.
2124
Your form view name is not unique.
Warning
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.
2125
Exit Administrator Tool?
Warning
116
AR System messages

Number
Description
2126
You currently have an escalation time specified.
Warning
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.
2127
This operation (FTS Re-index) could take a long time.
Warning
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.
2128
Your escalation action will be deleted.
Warning
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.
2129
Your escalation definition and all associated actions will be deleted.
Warning
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.
2130
You are logged in as a subadministrator access to some structures and functions has been
disabled.
Warning
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.
2131
Incompatible data types in qualification line.
Warning
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.
2132
Full text index operations will be started.
Warning
You activated the full text search (FTS) subsystem of AR System. Items that are pending indexing
begin indexing immediately.
2133
Full text index operations will be shut down.
Warning
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.
2134
You must be a member of the Administrator or Subadministrator group with a fixed license to
use this tool.
Warning
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.
2135
The selected distributed mapping will be deleted.
Error
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.
2136
The selected pending mappings will be deleted.
Warning
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.
117

Number
Description
2137
Changes on the mapping fields screen will be lost if you continue.
Warning
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.
2138
You are attempting to delete a Distributed Server form or field. Do you wish to continue?
Error
The form you are deleting is a special Distributed Server Option (DSO) form. Deleting the form
might affect the functionality of DSO. When you restart the system, the server automatically recreates 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.
2139
Changes in Current view will be Saved if You Continue!
Warning
You are changing views without saving your changes to the current view. If you continue, your
changes are saved automatically.
2140
Other forms depend on current form. Deleting this form will cause forms that depend on it to
be deleted. Are you sure you want to continue?
Error
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
The following field names/ids have blank labels in your form.
Warning
You applied changes to a form that contains one or more fields with blank labels.
2142
Your guide will be deleted.
Warning
You are deleting a guide. If you proceed, the guide is removed. If you cancel, the operation is
terminated, and the guide is retained.
2143
Your application will be deleted.
Warning
You are deleting an application. If you proceed, the application is removed. If you cancel, the
operation is terminated, and the application is retained.
2144
Your packing list will be deleted.
Warning
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.
2145
Your web service will be deleted.
Warning
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.
2146
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.
Warning
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.
118
AR System messages

Number
Description
2148
System does not ensure consistency if global elements/complex types in use are changed.
Please choose embedded option if you are not sure.
Warning
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
Public access is not specified. This will force users to login before accessing wsdl.
Warning
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.
2200
Cannot allocate memory.
Error
when too many processes are running or when some processes have grown to occupy more, or
all, of the available memory on your client computer. To recover that memory, shut down
unneeded processes. Additionally, to recover space that applications might have leaked over
time, restart processes that have been running for a while.
2202
Only integer type can use numeric text type.
Error
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.
2203
Only selection type can use radio buttons
Error
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.
2205
Unrecognized field type.
Error
The type specified for the field is not recognized. Update the definition of the field to indicate a
valid display type for the field.
2214
Cannot open export file.
Error
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.
2219
Form definition problem: invalid field specification.
Error
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.
2220
Button field is missing an Active Link assignment.
Error
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.
2223
Exporting . . .
Note
2224
Export complete.
Note
2227
Export complete for selected range.
Note
2228
Cannot open configuration file.
Error
An error occurred while the system tried to open your configuration file. An associated message
contains details. Fix the problem, and repeat the operation.
119

Number
Description
2230
Update of custom operation failed duplicate name?
Error
2231
X and/or Y coordinates are out of range.
Error
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.
2232
Enter a form name.
Error
Specify the name of a form so you can complete the specifications for the window.
2234
Enter a user name.
Error
Specify the name of a user so you can log in. Enter a name, and click Save.
2236
Problem querying servers.
Error
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.
2241
No selection made one is required.
Error
To perform an import or export operation, select one or more items to be imported or exported.
2243
Cannot open the specified file.
Error
An error occurred while the system tried to open a file. An associated error message contains
2255
Enter a command name.
Error
2257
Enter a command string to execute.
Error
2269
Select an item.
Error
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.
2279
Problem deleting selected item from list during cut operation.
Error
An internal error occurred while the system tried to remove an item from an internal list. Exit the
tool, and restart the tool.
2281
No data entered at selected menu level.
Error
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.
2283
You must enter a label before selecting Insert or Modify.
Error
Enter a label for a new menu item before selecting Insert or Modify. After entering the label,
reselect the desired operation.
2284
No data entered at previous menu level.
Error
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.
2285
Enter a filter name.
Error
You did not enter a name, which is required, for the filter you are creating. Enter a name, and click
Save.
120
AR System messages

Number
Description
2286
The message number is invalid.
Error
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.
2287
You must select a form.
Error
You did not specify a form for the structure you are creating. Specify the form to which the
structure is attached.
2288
You must select at least one operation.
Error
You did not specify an operation for the filter or escalation to execute. Specify one or more
operations. Select an operation and click Save.
2290
Missing close quote on a character string/name.
Error
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 within a string, double the quotation mark.
2291
Unexpected character.
Error
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.
2292
Expected a conditional operation at this point.
Error
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.
2293
Expected a relational operation at this point.
Error
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.
2294
Expected a field or value at this point.
Error
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.
2295
Too many nested levels of parentheses in command.
Error
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.
2296
Expected a closing parenthesis at this point.
Error
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.
2297
Unknown field reference.
Error
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.
2298
Value specified for selection not one of defined values for this field.
Error
When a line was parsed, a specified value for a selection field was determined not to be one of the
legal values for the field. An associated message contains information about the position in the
line where the selection value is located.
121

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

Number
Description
2314
Select a field for your Execute On condition.
Error
The execution condition requires that a field be selected to attach the operation of the active link
to. This is required when you execute on Return or on Menu Choice. Select a field to attach to, and
click Save.
2315
Select an execution condition for your active link.
Error
You did not specify when to execute the active link. Specify one or more occasions for active link
execution. Select an execution condition, and click Save.
2317
Unrecognized group in group list or group list longer than maximum allowed.
Error
When the contents of a Group List or Assignee Group field was parsed, an unrecognized group
name was found, or the total length of the field exceeds 255 bytes. Fix the problem, and continue
with the operation.
2319
Assign line error at position location.
Error
While parsing an assignment line, an error occurred. This message contains information about the
position of the error in the line.
2320
Qualification line error at position location.
Error
While parsing a qualification line, an error occurred. This message contains information about the
position of the error in the line.
2321
Error
The value entered where a real value is expected is not in legal format for a real value. Real values
can include a single decimal point or can be in scientific notation. Re-enter the value in one of these
formats, and click Save.
2322
You have entered a non-digit character for a numeric field.
Error
An integer or real field contains a nondigit character. Integer and real fields can contain only digits
(except for real values in legal scientific notation).
2323
Unrecognized arithmetic operation.
Error
The arithmetic operation specified is illegal in the current context.
2324
The internal field length cannot be less than zero.
Error
The length specified by a character field must be greater than or equal to zero.
2325
Field IDs below 100 are reserved for core fields.
Error
You cannot create a field with an ID less than 100. Fields in this range are reserved for the core
fields that are created and managed automatically by the system.
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. For compatibility, you can use those field IDs for fields
with compatible definitions.
2326
You have specified a field ID already in use.
Error
The ID for every field must be unique. You specified an ID in use by another field. Change the ID
to be unique. If you are using BMC Remedy Administrator, you can leave the field ID blank for
the new field, and a legal ID is automatically created.
2328
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.
Error
Your configuration file registered that you were last connected to a server to which you no longer
have contact. The system default connects to the first server listed in your configuration file.
123

Number
Description
2329
No administrator macros are defined.
Error
No macros are available to the administrator for creating a macro-type action for an active link.
Make sure that the macro you want to run is defined. Use the ARPATH environment variable to
point to alternate locations for macro definitions.
2331
An error has occurred while formatting your diary text.
Error
An error occurred while the system tried to format the change history information for the
structure. Review the definition stored in the database. You can change other aspects of the
definition, but the change history is unavailable.
2332
One of the field names is invalid.
Error
One or more of the names specified in the Get list or Index list is not a valid field name for the
current form. Verify the spelling of the names to make sure that you specified legal fields.
2334
Error
You did not specify a form for the filter you are creating. Specify the form to which the filter is
attached.
2335
Total width of your fields exceeds the maximum.
Error
The total width of all the fields specified for Get List fields is greater than the maximum of 128.
Review the width specified for each field and the width of the separators and adjust, as needed,
to be within the maximum width of 128 bytes.
2336
There are no If actions defined. Please create at least one If action.
Error
No If actions were defined for the filter, escalation, or active link. Specify at least one If action.
2337
The field ID is too big.
Error
The ID specified for the field is outside the legal range of field IDs. Change the value to be in the
legal range. If you are using BMC Remedy Administrator, you can leave the field blank, and a
legal ID is automatically created.
2338
You cannot change type of an existing action.
Error
You cannot change the type of an existing action. Delete the existing action and create another
action.
2339
Delete failed.
Error
An error occurred while performing a Delete operation. An associated message contains

additional information.
2340
Too many levels in nested macro.
Error
If a macro nests to include other macros, the maximum number of nested levels of macros is 15.
The macro you are using has more than 15 levels of nested macros. You can run the macros one
after another in the same macro, but they cannot be nested more than 15 levels deep.
2341
Invalid parameter specification in the DDE assign line.
Error
The format of the DDE assignment line used in a Set Fields operation is invalid. Review the
documentation for the expected format of the DDE line, and correct the line.
2342
Invalid macro definition file format.
Error
The macro specified is not in the correct format and is thus unrecognized. Specify a valid macro
definition.
2343
Selection values must be unique.
Error
The values specified for a selection type field must be unique. You specified two or more values
that are the same. The system cannot tell the difference between the identical values.
124
AR System messages

Number
Description
2344
Export errors.
Error
2345
Cannot expand menu menuName for field fieldName.
Error
An error occurred while the system tried to retrieve and build the indicated menu for the specified
field. An associated message contains details.
2346
Query menu not expanded.
Error
2347
Missing button data.
Error
2348
Field data type and assignment data type are not compatible.
Error
A value with an incompatible data type that cannot be converted was assigned to a field. Specify
a value with a compatible (or at least convertible) data type.
2349
You have entered a value in an integer field which is outside of the valid range for integers.
Error
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.
2350
Duplicate mapping name rename your distributed mapping.
Error
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.
2351
Invalid mapping definition respecify your custom mapping.
Error
The tool could not decode the mapping definition for the custom mapping. Either the format of
this definition was manually changed, or a problem exists in the database with the storage of
definitions. Re-create the custom mapping.
2352
One of your mapping servers is not available or does not exist.
Error
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.
2353
You do not have permission to perform Distributed Server operations.
Error
You are connected to the system as a subadministrator, so you do not have access to the
Distributed Mapping form to define distributed mappings. You must be an administrator or be
given sufficient access by an administrator to create and modify distributed mappings.
2354
You have not entered data for any of your fields enter data for at least one field before
pressing the Apply button.
Error
The Set Fields action is not defined to assign values to fields. Specify the assignment of one or
more fields.
2355
There is already an Active Link in this form with this name: activeLinkName.
Error
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.
2356
You have entered a value in an real number field which is outside of the valid range for real
numbers.
Error
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.
125

Number
Description
2357
Get Failed.
Error
An error occurred while the tool tried to retrieve a property from a field.
2358
Set Failed.
Error
An error occurred while the tool tried to set a property for a field.
2359
DateTime range error - client only.
Error
This is an out-of-range error. For example, the message is displayed if you entered 1/1/2075 as
a date.
2360
DateTime illegal string error - client only.
Error
This message is displayed if you misspell a month or day name.
2361
DateTime format error - client only.
Error
This message is displayed if the format string you specified in the Control Panel is illegal.
2362
Date is out of allowed range of 01/01/1970 to 01/19/2038 (GMT) for Windows Client.
Error
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.
2365
The table field tableFieldName definition is corrupt. If you Save the form, you will delete this
field.
Error
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.
2366
Error
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.
2369
The listed columns for the tableFieldName table field do not have corresponding data fields.
Error
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.
2370
Form formName on table field tableFieldName does not exist on server serverName.
Error
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
2371
Enter an application name.
Error
You tried to save an application without providing a name. Enter an application name before you
save the application.
2372
Unable to save an image for the application.
Error
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.
126
AR System messages

Number
Description
2373
Server serverName for table field tableFieldName is not accessible at this time.
Error
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
Duplicate distributed mapping name.
Error
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.
2380
Page or Page Holder field cannot be set to a NULL Field ID.
Error
You cannot set the database ID of the Page or Page Holder fields to a NULL value. Supply a nonNULL value for the database ID.
2381
Error getting active links list.
Error
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.
2382
Error getting filter list.
Error
it failed to obtain a filter list from the current server. Close the dialog, and retry the operation.
2383
Error getting escalation list.
Error
it failed to obtain an escalation list from the current server. Close the dialog, and retry the
operation.
2392
The application state system form could not be found on the queried server.
Error
The AR System Application State form was not found. Restart the AR System server, which recreates the form if necessary.
2393
The application roles system form could not be found on the queried server.
Error
The Roles form was not found. Restart the AR System server, which re-creates the form if
necessary.
2394
The application roles system form did not contain any state fields.
Error
No state fields (fields with field IDs from 2000 to 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.
2395
An entry in the state table could not be found for this application.
Error
The system failed to create an entry for the application in the AR System Application State form.
Create an entry for the application manually.
2396
Could not query the application state table.
Error
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.
2401
Unknown error code errorNumber encountered.
Error
The message with error code errorNumber is missing from the string table.
127

Number
Description
2403
Unable to initialize user information.
Error
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.
2404
Unable to connect to any servers.
Error
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.
2405
Failed to initialize the system globals.
Error
2408
The user home directory is missing from the ARuser section in the win.ini file.
Error
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.
2412
Currently running MISCDLL.DLL version oldVersionNumber is an old version. Version

currentVersionNumber of MISCDLL.DLL is required.
Error
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
2416
Failed to create memory.
Error
BMC Remedy Administrator could not allocate memory for its data structure. Close one or more
applications to continue.
2417
Failed to create the AR System home directory.
Error
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.
2418
User Name is missing.
Error
When saving user information in the Login Information dialog box, specify a user name.
2419
AR System home directory is missing.
Error
When saving user information in the Login Information dialog box, specify a home directory.
2420
At least one field must have a value in a Set Fields action.
Error
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.
2421
You cannot delete an object that you are currently editing.
Error
You cannot delete an active link, filter, escalation, or form that is open. Close the window in
question, and retry the deletion.
2422
Failed to load the selected image file.
Error
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.
2423
You must specify a menu or button field for active links that execute on a menu or button.
Error
You selected Execute On: Menu Item/Button in an active link without associating it with a
menu item or button on the form.
128
AR System messages

Number
Description
2426
Server serverName not found in server list.
Error
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.
2427
The following fields do not have valid values set:
Error
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.
2428
Specify an SQL command.
Error
To save a SQL Set Fields action, specify a SQL command. This is not validated but cannot be left
blank. To continue, enter a SQL command.
2431
Could not remove all the specified pending operations.
Error
The server had a problem deleting the pending operation after you clicked Remove in the Pending
Distributed Operations dialog.
2432
Supply a label index (greater than 0).
Error
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.
2433
Supply a value index (greater than 0).
Error
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.
2434
Supply an SQL command.
Error
To save a SQL menu definition, specify a SQL command. This is not validated but cannot be left
2435
Button field is missing an active link assignment.
Error
When you used BMC Remedy Administrator 3.x or later to save a form on a 2.x AR System server,
the specified button field was not associated with an active link.
To save the form, first assign an active link to the button field or delete the button.
2437
Cannot read forms for server.
Error
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 a network
connection problem might exist.
2438
You have selected more fields than will fit in the clipboard. Select fewer fields, and try again.
Error
If you selected more than 300 fields on the screen, you cannot use the Edit > Copy operation. To
continue, select 300 or fewer fields.
2439
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.
Error
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.
2440
Insufficient resources to create the palette.
Error
The floating palette tool bar used to create fields could not be created because Windows ran out
of memory. Close some applications, or restart your Windows session.
2441
Another view already exists with that name.
Error
The name you specified is used by an existing view. Specify a new name for your view; remember
that names are case-sensitive.
129

Number
Description
2442
You must specify the hours or minutes (or both) to retry a distributed operation.
Error
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.
2443
Get list of fields operation failed.
Error
Your attempt to get a list of fields from a server failed. The server might have failed after you
logged in to it.
2444
value is not a valid value for field fieldName. Values set to newValue.
Error
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.
2445
Note that value is outside the range for field fieldName.
Error
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.
2446
You must enter a distributed mapping name.
Error
When creating a distributed mapping, you did not specify a name. Enter a distributed mapping
name to continue.
2447
You must enter an escalation name.
Error
When creating an escalation, you did not specify a name. Enter an escalation name to continue.
2448
The current custom mapping is not valid. Unable to display unmapped fields.
Error
You tried to Show Unmapped Fields in a custom distributed mapping; one or more of the field
mappings is incorrect.
2449
A value must be entered for the following fields: Request ID, Form, and Server.
Error
When configuring a DSO Delete action for a filter, you must provide a request ID, form name, and
server.
2450
The field can contain double quotation marks () or single quotation marks (), but it cannot
contain both kinds of quotation marks.
Error
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. 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.
If the Distribute Transfer option button is selected, the Mapping, To Form, and To Server fields
might not contain a combination of double and single quotation marks. If the Distributed Delete
option button is selected, the Request ID, Form, and Server fields might not contain a combination
of double and single quotation marks.
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, so one of these
must not exist in the field.
2454
Error
A maximum of 1985 items can be exported at once. Select a fewer number of items, and try the
operation again.
You tried to export definitions for more than 1985 items. 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.
To avoid this error, export fewer than 1985 items at one time.
130
AR System messages

Number
Description
2455
The width of a results list field and its separator combined is limited to 128 characters.
Error
The administrator tried to make a column of the results list wider than 128 characters.
2458
You must have at least one field with a value in a push field action.
Error
You tried to save a Push Field action without specifying a push field value for a field on the form.
Specify a value for the field on the form and try again.
2459
This is a special object parameter in which you can only add another method which returns the
same object.
Error
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, or you entered a value for
a parameter of type IDispatch.
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 pointer and you nested another method
whose return type is incompatible with the pointer type, or you tried to enter a value for a
parameter of type pointer. The parameter can be filled only by nesting another method whose
return type is compatible.
You can also use $fld$ to enter the value for a pointer parameter. AR Runtime gets or sets the
value of the $fld$ and treats this field as an OLE pointer variable.
2461
Error
Please select a matching function. Looks like the return type of the method selected and the
method to be added are incompatible.
When you define an OLE method that has a return type and you try to nest or call another method
on this return type, BMC Remedy Administrator validates whether the return type is of type
object. You can call or nest another method out of this return type only if the return type is of type
object or object pointer.
2462
Please select a matching function.
Error
You defined an OLE method that returns a pointer, and you tried to nest an incompatible return
type.
2463
The two pointer types do not match. Please select another one.
Error
You tried to nest a method that returns a pointer, but the pointer is incompatible with the
parameter pointer type you want to nest.
2464
You cannot call another method on the parent method. The Parent return type is not an Object.
Error
When you nest a method, the parent methods return must be one of the following types:
IDispatch, VARIANT, or Compatible. If the parent methods return type is not one of these types,
this error is returned.
2465
Please select a method that returns a pointer.
Error
When you nest a method to a parameter, the parameter must be of type pointer.
2466
You cannot add a method here. Type incompatible.
Error
You tried to add or nest a method to a parameter, but the return value is incompatible with the
parameters native type.
2467
Cannot add the method. Incompatible objects. Try again.
Error
You tried to add or nest a method, but the containing object of the child method differs from the
return type object of the parent method.
131

Number
Description
2468
The Constants and properties are for display only. Cannot be inserted by clicking the Add
Method button.
Error
The constants, enums, and other data structures displayed in the type library tree are for display
purposes only. This error occurs when you place your selection on one of these data structures
and attempt an Add Method operation.
2469
The Parameter or Return value is of wrong type. Please type in a proper value.
Error
When you provide a value for a parameter, BMC Remedy Administrator tries to map it to the OLE
methods parameter OLE type. If unsuccessful in the conversion, BMC Remedy Administrator
returns this error message explaining that the value cannot be converted to the native OLE
parameter type.
2470
Please select a method to delete.
Error
You clicked Delete Method without first having selected a method.
2471
Can delete only methods at the root level.
Error
To be deleted, a method must be a nested parameter either at the parameter level or at the return
level.
2472
You cant add methods to a return value.
Error
You defined an OLE method that has a return value, and you tried to add a method by clicking
Add Method when the selection was at the return node.
2473
A label must be unique and consist of one or more characters.
Error
Labels in guides must be unique. Rename the label, providing a name that has not yet been used
in the guide.
2474
Error
The administrator defines the number of places to the right of the decimal point (precision) for a
given field. The administrator might also define the high and low range for values entered into
the field. The value you entered does not meet the criteria defined by the administrator.
2475
Please enter a server name.
Error
This message occurs when the Server Name field in an Open Dialog action is empty. Enter a server
name to continue.
2476
Cannot edit return value. Right-click to select a Field.
Error
You cannot enter a value in the return value node. Right-click and select a field. If the return type
is an object, you can nest another method.
2477
You cannot have duplicate named predefined searches. Please give the entry a unique name.
Error
Predefined searches cannot have duplicate names. Enter a unique name to continue.
2478
Enter a packing list name.
Error
When creating or modifying a packing list, specify a name.
2479
No work space has been selected.
Error
You selected View > By Workspace, and you selected Enable Workspace; but you did not select a
packing list. Select a packing list, and retry the operation.
2480
There is already another view with the same label, platform, and locale combination.
Error
An error is returned because the view you are creating contains the same combination of
information as another view. To continue, create this view with a different combination of label,
platform, and locale.
132
AR System messages

Number
Description
2481
Please enter a non-empty string in label and name fields.
Error
An error occurred because you tried to create a view without a label or name. To continue, specify
a view label and name.
2482
An unspecified error occurred.
Error
When an application was deployed, an unspecified error was returned during HTML file
generation. The error was not covered under errors 2483 to 2495.
2483
The file fileName could not be located.
Error
When an application was deployed, the HTML file generation stopped because the HTML file
could not be created.
2484
Bad Path: directoryPath.
Error
When deploying an application, the HTML file generation stopped because all or part of the path
is invalid.
2485
The permitted number of open files was exceeded.
Error
When an application was deployed, the HTML file generation stopped because the permitted
number of open files was exceeded.
2486
You do not have the proper permissions to access the file fileName.
Error
When an application was deployed, the HTML file generation stopped because the file could not
be accessed.
2487
There was an attempt to use an invalid file handle.
Error
When an application was deployed, the HTML file generation stopped because the file is either
corrupted or open in a nonshared mode.
2488
The current working directory cannot be removed.
Error
When an application was deployed, the HTML file generation stopped because the current
working directory cannot be removed.
2489
The number of directory entries for directory directoryPath has been exceeded.
Error
When an application was deployed, the HTML file generation stopped because no more directory
entries exist.
2490
There was an error trying to set the file pointer.
Error
When an application was deployed, the HTML file generation stopped because an attempt to set
the file pointer failed.
2491
There was a hardware error.
Error
When an application was deployed, the HTML file generation stopped because a hardware error
occurred. For example, your drive is corrupted, or you are trying to write to a network drive and
the network is down.
2492
Attempted access to file fileName produced a sharing violation.
Error
When an application was deployed, the HTML file generation stopped because a shared region
was locked.
2493
There was an attempt to lock a region that was already locked.
Error
When an application was deployed, the HTML file generation stopped because an attempt to lock
a region that was already locked occurred.
2494
The disk is full.
Error
When an application was deployed, the HTML file generation stopped because the disk is full.
133

Number
Description
2495
The end of file was reached.
Error
When an application was deployed, the HTML file generation stopped because the end of file was
reached.
2501
Other forms depend on form formName. If you delete this form, all other forms that depend on
this form will be deleted. Do you want to continue?
Warning
You are deleting a form used as a member of a join form. If you continue, the join form is also
deleted.
2502
Warning: If you change the form, existing actions might be made invalid. Verify your existing
actions.
Error
Your active link and filter actions might contain references to fields on this form. Those actions
are invalidated if you reattach them to a form that no longer contains those fields.
2503
The following fields were not pasted, because they are already in this view.
Warning
During a Copy or Paste operation from one view to another, you tried to add fields to the view
that already exist in the view. Any fields already in the view are unaffected.
2504
You are removing these data fields from their only view: fieldNames. These fields do not exist
on any other views. All display information, including label text and location, will be lost. Do
you want to continue?
Warning
You are removing data fields from their only view. If you continue and put the fields back into a
view, they have a default location and appearance.
2505
No integer or selection fields exist to cross-reference against.
Warning
You specified Cross-Reference as the notification mechanism for a Filter Notify action, but this
form has no integer or selection fields to cross-reference. Try another notification mechanism.
2506
Unable to open more windows, because Windows resources are low. User Heap: percentage%
free. GDI Heap: percentage% free. Close some windows or running applications to gain more
space.
Error
A new window could not be opened because too many windows are open or too many
applications are running. To continue, close some windows or applications.
2507
The value being deleted is the same as the default value. If you continue, the default value will
also be deleted. Do you want to continue?
Error
You are deleting a value from a selection field that matches the default value. If you continue, the
default value is also deleted. You might want to specify a new default value.
2508
The status field must have a default value. If you continue the default value will be changed
to the first entry. Do you want to continue?
Error
The Status core field is special because a default value is required. If you delete the current default,
it is replaced by the first value in the list. If you continue, you might want to specify a new default
value.
2509
Confirm that you want to save the form; the following fields will be deleted: fieldNames.
Warning
You deleted fields while editing the form, and those changes are about to take effect. This is a final
confirmation and a chance not to save the form changes. If you save the changes, the fields are
deleted. Otherwise, you can close the form without saving any changes.
2510
You cannot add or modify the Default Login name. Changes are lost.
Error
You tried to change the name or add a new Default Login user name to the login user list. The
Default Login name is a reserved name and cannot be added or changed.
134
AR System messages

Number
Description
2513
Login aborted. You cannot close all windows.
Error
When you tried to log back in, BMC Remedy Administrator failed to close all existing open
windows, possibly because of a user request for an unsaved window.
2514
Character menus cannot exceed 14 levels.
Error
You can create a character menu only up to 14 levels deep.
2515
Failed to read field for form.
Error
BMC Remedy Administrator failed to read a field for the form you selected for an active link or
filter. Make sure that BMC Remedy Administrator can still connect to the server that the form is
on, and then try again.
2516
The minimum and maximum values are the same.
Error
You illegally specified a range of exactly one value.
2517
Save the form before renaming it.
Error
You must save the form before you can rename it.
2518
The minimum value is out of range. The range is 2147483647 to 2147483647.
Error
Integer fields require a number in the valid range.
2519
The maximum value is out of range. The range is 2147483647 to 2147483647.
Error
2520
The default value is out of range. The range is 2147483647 to 2147483647.
Error
2521
The minimum value is out of range. The range is number to number.
Error
Real number fields require a number in the valid range.
2522
The maximum value is out of range. The range is number to number.
Error
2523
The default value is out of range. The range is number to number.
Error
2524
The precision is out of bounds. Valid range is 0 to 30.
Error
Real numbers must have a precision (number of places to the right of the decimal point) within
the specified range.
2525
This change will move the field out of bounds.
Error
Provide field coordinates (X, Y locations) that keep the field within the maximum dimensions of
a view (1500 x 3000).
2526
This change will cause the field to be out of bounds.
Error
Provide field coordinates (X, Y locations) that keep the field within the maximum dimensions of
a view (1500 x 3000).
2527
The following restored fields are no longer in this view:
Warning
You restored the selected fields from the database. If any of these fields were added to the current
view after you last loaded the form, they no longer appear in the current view. Use the Fields in
View dialog box to see which views the fields are in.
2528
Multiple views may be affected by this operation. Do you want to continue?
Warning
The current operation can affect the display properties of one or more unloaded views. If you
continue, you can switch to the other views that contain the affected fields to see the result before
applying the changes to the form.
135

Number
Description
2531
Active link activeLinkName is already used by controlFieldName. Are you sure you want to
move it to controlFieldName?
Warning
Active links can be attached to only one button or menu item. Attaching an active link detaches it
from its current button or menu item (if it has one).
2532
Warning
You are removing these trim or control (or both) fields from their only view: viewName. These
fields will be deleted from the database. Do you want to continue?
When trim or control fields are removed from all views, they are marked for deletion, just as if
you had explicitly deleted them.
2533
Warning
A time-out occurred while copying form formName to formName. The operation most likely
succeeded but the server is still busy.
This warning occurs when the Save Form As command is used to copy a form. The server is busy
and has timed out. Your form has probably been copied, but verify at a later time (when the
server is not busy) that the copy operation succeeded.
2534
Warning
The layering of some fields in this view was not valid. The problem has now been corrected,
and the changes will take effect when you save the form.
BMC Remedy Administrator detected and corrected a minor problem with the front-to-back
ordering of fields in this view, and all fields in the view will be saved to the database when form
changes are applied. This usually occurs because of direct API setting of field properties or
because of problems with the conversion of an old form definition.
2535
Copy and Paste of join fields is not supported; the selected join fields will not be copied.
Warning
Normally, the Copy operation is disabled when join fields are selected. This message indicates
that a mixture of join and trim fields was selected, and a Paste operation was attempted. Only the
Paste operation of trim fields will succeed. You cannot have a a join field appear more than one
time in a form.
2536
There are no toolbar items on any of the menu items.
Warning
No menu items in the current view have an associated toolbar item. Therefore, BMC Remedy
Administrator cannot display the Toolbar Layout dialog box.
2537
At least one trim, button, or menu item field will be deleted because you are deleting its only
view.
Warning
If you delete this element from this view, it will not exist on any view; it will be completely and
permanently deleted.
Select Cancel if you do not want to delete the selected item.
2538
Warning
Active link activeLinkName is already used by buttonName. It can not be added to

buttonName.
This version of AR System does not support moving an active link from one button to a different
button. To continue, create another active link.
2539
You have specified an ID within the reserved range. Do you want to save this field anyway?
Warning
While creating a new field in a form, you specified a field ID less than or equal to 536868911. Field
IDs in this range are reserved by AR System.
Unless you are intentionally using the AR System reserved field ID range, cancel this operation,
and choose a field ID outside of the reserved range.
136
AR System messages

Number
Description
2540
None of the requested field deletions occurred on the server. Please close and reopen the form
after the save operation has completed.
Warning
This warning is returned because, although the form is in the process of being saved, the delete
operation did not complete as expected. To continue, open the form after the save operation
completes and try deleting the fields again.
2541
Warning
This form contains a non-standard set of Distributed Fields. Select none, basic, full, or
advanced to return to a standard set of fields.
Your form has an inconsistent set of distributed fields, possibly because one or more fields were
deleted. Distributed fields are system-generated and cannot be mixed and matched. Use the
Distributed Fields dialog box to re-create a standard set of distributed fields in your form.
2542
Warning
Distributed Fields will be deleted. 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.
2543
Warning
This form contains a Distributed Field of the wrong data type. To delete Distributed Fields,
select None in the Distributed Fields dialog, and press OK.
This message occurs when an incorrect data type is associated with distributed fields.
2544
Warning
Distributed Fields will be deleted. Are you sure you want to have numberOfFields Distributed
Fields?
This is a confirmation message when you want to delete DSO mapping fields.
2545
Warning
Selecting this option could cause an infinite loop in the system. Do you want to continue with
overriding loop detection?
By shutting down loop protection, you run the risk of creating infinite loops and overwriting the
original record in a distributed transfer operation or a distributed return operation. Save the filter
or escalation only if you are understand the risk in what you are doing.
2546
Warning
One/more fields have been deleted from the form which will affect Setfield list. Please press
Modify Action button to rectify the problem.
You opened a Set Field active link action, and some of the fields used in the setfield/value list box
were deleted from the form. To correct this problem, click Modify Action.
2548
Please enter a form prefix.
Warning
When you selected the Form prefix option in the By Form dialog box, you did not enter a prefix
before clicking OK.
2549
Please add at least one form to the selected form list.
Warning
You selected the Selected Form option in the By Form dialog box but did not select any forms
before clicking OK. Select a form, and then click OK.
2550
A maximum of numberOfForms forms can be selected. Please remove some forms from the
selected form list.
Warning
You can select a maximum of 10 forms through the Selected Form option of the By Form Dialog
Box. This message indicates that you selected more than 10 forms.
2551
Warning: All the subsequent calls will be deleted.
Warning
When you try to delete an OLE method, BMC Remedy Administrator warns you that all
subsequent methods (if nesting was done) will be deleted.
2552
The minimum value has a bad value.
Error
You entered an invalid value for the minimum value in the Field Properties Attributes page for a
Decimal Field.
137

Number
Description
2553
The maximum value has a bad value.
Error
You entered an invalid value for the maximum value in the Field Properties Attributes page for a
Decimal Field.
2554
No image conversion will take place. Save anyway?
Warning
If you try to change the extension of an image formats extension (for example, trying to save a
JPEG file as something.gif), this warning appears.
2555
The precision is out of bounds. Valid range is 0 to 28.
Error
You entered an invalid value for a Decimal Field in the Attributes page of the Field Properties
Dialog Box. The valid range is between 0 and 28.
2556
A duplicate server was detected in the server list for user userName. Server Name in list:
serverName Short Name of detected server: serverShortName Long Name of detected server:
serverLongName.
Warning
This warning appears when you add the same server name, for both the short and long names, in
the list of servers.
2557
Warning: Form formName not available in server serverName.
Warning
This warning appears when you change a server name for an open dialog active link action. You
are given the option to reset the value to the previous server you selected.
2558
To improve this view so that it looks the same on all clients, BMC Remedy Administrator will
upgrade the layout information for this view when you save this form.
Warning
You tried to import a pre-4.0 form with a 4.x (or later) version of BMC Remedy Administrator.
This changes all fields bounding boxes so that they are compatible with 4.x or later. This warning
appears the first time a form is imported and when the forms views are changed.
2559
The field type selected is not valid for global fields.
Warning
You chose an invalid field type to become a global field. To continue, see the Form and Application
Objects Guide for available field types.
2560
A maximum of number forms can be selected.
Warning
When viewing a select number of forms in the Server Window, you selected more than 10 forms.
The maximum is 10. To continue, select a number less than 10. A workaround would be to create
a packing list and use it to view a larger number of forms.
2561
A global field has just been set to a regular field. The entry mode selection will be set to
default.
Warning
Global fields by design have no default values. By turning the field back into a regular field, you
now can specify an entry mode.
2562
Warning
Field ID 706 and 1020 are reserved for Alert and Results List respectively. Please choose another
Field ID for fieldfieldType.
These field IDs are reserved for alert lists and results lists. Choose another field ID that is not from
these reserved numbers.
2563
Warning
Field IDs from 711 to 718 are reserved for columns of Alert List. Please choose another Field ID
for fieldfieldType.
This range of field IDs is reserved for columns in an Alert List. Choose another field ID not from
this reserved range.
2564
Some fields that are mapped will not be relevant for this form.
Warning
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.
138
AR System messages

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

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

Number
Description
2719
Please supply a server name.
Error
When creating or saving a Search menu type, you did not enter a server name. Enter a server name
to continue.
2720
Please supply a form name.
Error
When creating or saving a Search menu type, you did not enter a form name. Enter a form name
to continue.
2721
Please supply a label field.
Error
When creating or saving a Search menu type, you did not select a label field. Select a label field to
continue.
2722
Please supply a value field.
Error
When creating or saving a Search menu type, you did not select a value field. Select a value field
to continue.
2723
Please select a file location.
Error
When creating or saving a File menu type, you did not enter a file location. Enter a file location to
continue.
2724
Please supply a file name.
Error
When creating or saving a File menu type, you did not enter a file name. Enter a file name to
continue.
2725
Menu definition is empty.
Error
When creating or saving a Character menu type, you did not add any menu items. Add menu
items to continue.
2726
You cannot delete the following core field(s):
Error
When creating or modifying a form, you illegally tried to delete a core field. These fields are
system-generated and must exist in any regular form. If necessary, you can hide these fields, but
you cannot delete them.
2727
Must be greater than 9999 and less than 2147483647.
Error
When creating a Message active link 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
Modify Action.
2728
Missing message text.
Error
When creating a Message active link action, you did not enter any message text. Enter the missing
message text, and click Modify Action.
2729
Missing field name.
Error
When creating a Change Field active link action, you did not select a field name. Select a field
name, and click Add Action.
2730
DDE Service Name is missing.
Error
When creating a DDE active link action, you did not enter a DDE service name. Enter a service
name, and click Add Action.
2731
DDE Topic is missing.
Error
When creating a DDE active link action, you did not enter a DDE topic. Enter a DDE topic, and
click Add Action.
141

Number
Description
2732
DDE Item is missing.
Error
When creating a DDE active link action, you did not enter a DDE item. DDE poke actions must
include a DDE item. Enter a DDE item, and click Add Action.
2733
DDE Path is missing.
Error
When creating a DDE active link action, you did not enter a DDE path. Enter a DDE path, and click
Add Action.
2734
DDE Command is missing.
Error
When creating a DDE active link action, you did not enter a DDE command. Enter a DDE
command, and click Add Action.
2735
The minimum value is greater than the maximum value.
Error
When creating a decimal field, you specified an illegal range of minimum and maximum values.
To continue, create a minimum value larger than the maximum value.
2736
The Default value is out of range with the minimum and/or maximum value. The default value:
Error
When creating a decimal field, you specified an illegal default value. To continue, create a default
value within the minimum and maximum ranges.
2737
The search database has been synchronized successfully.
Error
You successfully updated the search database. You now can search for any new objects added to
your search database.
2738
Synchronization of the Search Database Failed. Try again.
Error
An attempt to update the search database failed. You cannot perform searches for new objects
added to your search database. To continue, try performing the synchronization later.
2739
Server object objectName cannot be opened from here. Please open it from the Server Window.
Error
You cannot open server objects from the Related Workflow tab on the Field Properties window.
Click OK, and then open the server object from the Server Window.
2740
Macro name is missing.
Error
When creating a Run Macro active link action, you did not specify a run macro command. Specify
a run macro command, and click Add Action.
2741
The named menu is not defined at this time, do you wish to continue?
Error
When attaching a menu to a character field, you selected an illegal menu. To continue, select a
menu from the drop-down list of available menus.
2742
Unable to Save/Update Form.
Error
You attempted changes to a form that were not accepted by AR System.
2743
The Default value is out of range with the minimum and/or maximum value. The minimum
value minimumValue and the maximum value maximumValue.
Error
When creating an integer field, you specified an illegal default value. To continue, create a default
2744
Error
The Default value is out of range with the minimum and/or maximum value. The minimum
value minimumValue and the maximum value maximumValue.
When creating a real field, you specified an illegal default value. To continue, create a default
2745
Do you wish to close the field property dialog before correcting the errors?
Error
You specified incorrect field property settings. If you close the Field Property dialog box, your
settings are not saved.
142
AR System messages

Number
Description
2746
The field length must be between 0 and 4294967295.
Error
When creating a character field, you specified an input length outside the legal range of values.
To continue, specify an input length within the legal range.
2747
Invalid View Name. You must select a defined name.
Error
When choosing a default form view in the Manage Views dialog box, you can choose only from
the listed views in the drop-down menu.
2748
Alert text is missing.
Error
When creating a Notify filter action, you did not enter notify text. Enter notify text, and click Add
Action.
2749
User text is missing.
Error
When creating a Notify filter action, you did not enter a user name. Enter a user name, and click
Add Action.
2750
Reference Field is missing.
Error
When creating a Notify filter action, you did not select the reference field required when the
notification Mechanism is Cross-Reference. Select a reference field, and click Add Action.
2751
Sorry, unable to locate your default browser. Feel free to visit our website for the latest
information about BMC Remedy products and services at http://www.bmc.com.
Error
You choose items from Help > Remedy on the Web > Remedy Home Page in BMC Remedy
Administrator. To access this information, install a browser.
2753
Unable to log on to any server as administrator or sub-administrator.
Error
Login failed for one of these reasons:
AR System did not recognize this user name as a valid administrator.

You entered an invalid server name.
To continue, verify that the server and administrator names are correct.
2754
Please enter Qualification query for this action.
Error
When creating a Push Fields action, you did not enter a Push Field If qualification. Enter a
qualification, and click Add Action.
2755
Qualification line error at position number.
Error
When creating a Search type menu, you did not enter a valid qualification. Check your
qualification, and click Add Action.
2757
Error Getting Font Data.
Error
The fonts you selected in the Form Fonts tab in the Preferences dialog box were not accepted for
some internal reason.
You can troubleshoot this problem by verifying that you can select a different font as a preference.
If you can, the font you previously selected cannot be understood by AR System for some
unknown reason.
2759
Error getting form list on server serverName.
Error
BMC Remedy Administrator analyzer could not find a list of forms on the server. Possible
problems might be a memory allocation error, or AR System server might have stopped running.
After you verify that you have enough memory resources and that the server is running, rerun
BMC Remedy Administrator analyzer.
143

Number
Description
2760
Error getting active links list on form formName.
Error
BMC Remedy Administrator analyzer could not find a list of active links connected to this form
on the server. Possible problems might be a memory allocation error, or AR System server might
have stopped running. After you verify that you have enough memory resources and that the
server is running, rerun BMC Remedy Administrator analyzer.
2761
Error getting filter list.
Error
BMC Remedy Administrator analyzer could not find a list of filters on the server. Possible
2762
Error getting escalation list.
Error
BMC Remedy Administrator analyzer could not find a list of escalations on the server. Possible
2765
Server serverName not found in list of servers.
Error
When creating an Open Window action, you specified a server that the system could not find or
resolve. Enter or select a different server name to continue.
2766
Form formName not found in list of forms.
Error
When creating an Open Window action, you specified a server that the system could not find or
resolve. Enter or select a different server name to continue.
2768
Warning: Some fields that are mapped will not be relevant for this form.
Error
When creating an Open Window action, you tried to enter a set of field/value mappings that are
invalid for the form you selected. Enter a new set of mappings, or select the form used for these
mappings.
2770
Error: No server has been selected.
Error
When creating or modifying an Open Window action, you did not specify a server. Enter or select
a server name to continue.
2771
Error: No form has been selected.
Error
When creating or modifying an Open Window action, you did not specify a form. Enter or select
a form name to continue.
2772
Warning: No field mappings have been defined for Open and Close dialog states.
Error
When creating or modifying an Open Window action, you did not specify a set of field/value
mappings. BMC Remedy Administrator lets you save the action, but the action does not function
properly. Create a set of field/value mappings to continue.
2773
Assign line error at position number.
Error
While parsing a qualification line in the Open Window action, an error occurred. This message
contains information about the position of the error in the line.
2776
You will lose your existing guideName assignments by changing the form. Do you want to
continue?
Error
When modifying an active link or filter guide, 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. To continue, verify which form or forms you want to control the active links
in your guide.
144
AR System messages

Number
Description
2777
Error in export! Export aborted.
Error
An error occurred while the system tried to export mail templates. To continue, 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.
2778
Error: No guide selected for CallGuide action.
Error
When creating or modifying a Call Guide action, you did not select a guide. Select a guide to
continue.
2779
Error: Addition of guide guideName addition to tree failed.
Error
An error occurred when the system tried to add a complete list of guides to the tree.
Verify that the guides exist and try repeating the creation of the Call Guide action to continue.
2781
Error: No Active Link specified for guide to go to.
Error
When creating or modifying a Go To Guide Label action, you did not enter a guide label. Enter a
guide label to continue.
2782
The Default value has a bad value.
Error
When creating a decimal field, you specified an illegal default value. To continue, create a default
2783
Error getting field list on form formName.
Error
BMC Remedy Administrator analyzer could not find a list of fields connected to this form on the
server. Possible problems might be a memory allocation error, or AR System server might have
stopped running. After you verify that you have enough memory resources and that the server is
running, rerun BMC Remedy Administrator analyzer.
2784
Failed to analyze field fieldName in form formName.
Error
BMC Remedy Administrator analyzer could not find this field connected to this form on the
2785
Failed to analyze escalation escalationName in form formName.
Error
BMC Remedy Administrator analyzer could not find a list of escalations connected to this form
on the server. Possible problems might be a memory allocation error, or AR System server might
have stopped running. After you verify that you have enough memory resources and that the
server is running, rerun BMC Remedy Administrator analyzer.
2786
Failed to analyze filter filterName in form formName.
Error
BMC Remedy Administrator analyzer could not find a list of filters connected to this form on the
2787
Error opening file fileName.
Error
When attempting to save a report of results from BMC Remedy Administrator analyzer, you were
unable to open a new file. Make sure that you are using a .txt format for the file and that you
have write access to this directory path.
145

Number
Description
2788
Could not detect image type of imageType.
Error
An error occurred because the image you tried to save to a file is not one of the following types:
.jpg
.jpeg
.bmp
.dib
You can use only these formats, and you can save only to a file of the same image type.
2789
Errors were found. Please check the tab order to make sure that all shared fields are in the same
order relative to each other.
Error
This error occurs only with multiple native views of a form in which you are creating the tab
order.
When you create a tab order for shared fields across pages in a page holder, make sure that the
tab order is the same for each view of the form.
2791
Unable to open file.
Error
When you tested the Help file or saved it to disk, an error occurred. To continue, verify that you
have the necessary permissions to access the file.
2793
Error getting application list.
Error
BMC Remedy Administrator analyzer could not find a list of applications on the server. Possible
2794
User userName does not have admin or subadmin privileges on server serverName. Connecting
as a guest user.
Error
Login failed because AR System did not recognize this user name as a valid administrator or
subadministrator. You can continue as a guest user or enter a different login name.
2795
Some Fields could not be saved in this form.
Warning
The server failed to save some of the fields you tried to add to or modify on this form.
Nevertheless, the form was created on the AR System server, along with other modified fields.
This problem might be connected to the inability of your underlying RDBMS to create these fields.
2796
Failed to load serverObject for form formName from server serverName.
Warning
During the login process, the server failed to load the AR System objects connected to this form
when you viewed objects by workspace or by form. Verify in BMC Remedy Administrator
whether you can view all forms and all objects.
2797
Failed to get related items. Export file will not be generated.
Error
When an object was exported, its related items were not loaded. The export operation fails. Verify
in BMC Remedy Administrator whether objects are related, for example, whether an active link
is connected to a form, and so on.
2805
Unable to refresh field detail for field fieldName in form formName on server serverName. Any
further operation on this form can cause unpredictable behavior.
Error
BMC Remedy Administrator issued an API call to refresh the fields on this form, but the call failed
because of instability in the client tool.
To handle this problem, close both the form and the BMC Remedy Administrator client. Then
restart BMC Remedy Administrator and open the form. If this does not work, you might need to
reboot your system.
146
AR System messages

Number
Description
2807
Error: The Active Link activeLinkName could not find the View viewName in Form formName.
The View will return to default.
Error
When you created an Open Window action, the Form View you selected was not found on the
AR System server. Accordingly, the view used in the action is the default administrator view.
Open the form in BMC Remedy Administrator and choose Form > Select a View to verify that the
view you want to use exists.
2808
Please select a Source Control Provider.
Error
You did not select a source control application before you clicked OK in the Source Control tab.
To enable source control integration with AR System, first select a provider from the Provider
Name drop-down list, and then click OK.
2809
Please select a Source Control Project.
Error
You did not select a source control project before you clicked OK in the Source Control tab.
To enable source control integration with AR System, first click the Browse button to select a
project and location from the Project Name drop-down list, and then click OK.
2810
Object already exists in Source Control.
Error
You tried to create an object that has the same name as an object that already exists in the source
control system. Use a different name. Otherwise, you overwrite the old object with a new one.
2811
Error getting definition file for object.
Error
You tried to import the object definitions from source control, but the operation failed.
2812
Object does not exist in Source Control.
Error
You tried to perform an operation on an object that was not first added to the source control
system. Add the object to the source control project.
2813
Are you sure you want to remove the selected objects from Source Control, as you will lose
history data along with them?
Error
When you remove an object from source control, you lose the ability to track the history of any
changes made to the object. However, you are not deleting an object from AR System server. Click
OK to continue.
2814
Object is checked out by userName.
Error
You tried to check out an object that is checked out by another user. Contact the other user if
possible to resolve any administrative issues.
2815
Error writing Registry values.
Error
You tried to retrieve user information from source control, but the properties could not be
displayed in the User Info dialog box.
2816
You are in Enforced mode of the Source Control Integration. You cannot modify this object
because it does not exist in Source Control.
Error
In Enforced mode, you tried to modify an object that does not exist in the source control database.
First check the object in to source control.
2817
Error
because it is already checked out to another user.
In Enforced mode, only one user at a time can check out an object. Contact the other user if
possible to resolve any administrative issues.
147

Number
Description
2818
because you did not check it out first.
Error
If conflicts occur when two users are trying to check out an object at the same time that is in
Enforced mode, the user who checked it out first is its owner. Contact the other user if possible to
resolve any administrative issues.
2819
Error
You are in Enforced mode of the Source Control Integration. You cannot modify this object.
The server is configured for Source Control but you have not integrated it on your client.
You tried to modify an object under source control in Enforced mode on the AR System server.
However, you do not have a source control client installed, or you did not properly configure it
with your BMC Remedy Administrator client.
Make sure that you properly installed the source control client software, and then configure it in
the Source Control tab in the AR System Administration: Server Information form. You can then
modify objects under source control. For more information about source control, see the
Integration Guide.
2820
Error
You are in Advisory mode of the Source Control Integration. Your Integration is not initialized,
so modifying an object could overwrite or conflict with someone elses work.
You tried to perform a source control action, but your BMC Remedy Administrator client is not
properly initialized with the source control system.
Configure your system to have the proper source control integration with AR System. Otherwise,
you run the risk of conflicting with another users work.
2821
Error
You are in Advisory mode of the Source Control Integration. Modifying an object could
overwrite or conflict with someone elses work because it does not exist in Source Control.
You tried to modify an object under source control in Advisory mode on AR System server. In
Advisory mode, multiple users run the possible risk of accessing the same object at the same time.
Be careful not to overwrite some other users changes.
2822
Error
overwrite or conflict with someone elses work because it is already checked out to another
user.
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 run the
almost certain risk of overwriting another users changes or introducing inconsistencies. If your
development environment absolutely requires Advisory mode, contact the other user if possible
before making any changes to resolve any conflicts.
2823
Error
overwrite or conflict with someone elses work because you did not check it out first.
You tried to perform an operation on an object under source control in Advisory mode on
AR System server. In Advisory mode, multiple users run the risk of accessing the same object at
the same time. Check out the object before performing any further operations.
2824
Please enter a definition file name.
Error
When importing from source control into a file, you did not enter a file name before you clicked
OK. Enter a file name to continue.
2825
Please relogin to this server for the changes made to Source Control Integration to take effect.
Error
After you make changes in your source control provider, project, and other configuration settings
in the AR System Administration: Server Information form, relog in to BMC Remedy
Administrator. Then you can start using source control integration with the AR System server.
148
AR System messages

Number
Description
2826
Source Control operations can not be performed on Groups.
Error
You tried to perform a source control operation on a group, for example, checking a group name
in to source control. This functionality is disallowed with AR System integration.
2827
Source Control operations can not be performed on Distributed Mappings.
Error
You tried to perform a source control operation on a distributed mapping, for example, checking
a mapping in to source control. This functionality is disallowed with AR System integration.
2828
Error opening Source Control project.
Error
You tried to open a source control project but were unable to. To continue, verify that you have
access to the project, for example, by opening it in the source control client.
2829
You are in Enforced mode of the Source Control Integration. You cannot import this object
because it is already checked out to another user.
Error
You tried to perform an import operation on an object checked out to another user. Contact the
other user if possible to resolve any administrative issues.
2830
Error updating Source Control database.
Error
The operation to AR System server was successful but the update to the source control database
failed. Verify that the source control database is running, and then retry the update operation to
continue.
2831
Error getting file from Source Control database.
Error
A failure to retrieve a definition file from source control occurred. To continue, verify that you
have access to the file, for example, by opening it in the source control client.
2832
The object you are importing has been checked out to someone else. Import to server anyway?
Error
If the object is checked out to another user, that object is skipped and the import process continues.
Import the object to the server later.
2833
Error importing some objects.
Error
During an import operation from source control, some of the objects were not imported because
the server name alias could not be resolved to show the server name. The operation was only
partially successful.
You also see this error message if you import server objects from a .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 entry in the ar.cfg/ar.conf file.
To continue, verify that you have access to the objects in the source control database, for example,
by trying to access them in the source control client. If you are successful, log back in to BMC
Remedy Administrator, and retry the import operation.
If you are using a server name alias, verify that it is valid.
2834
Object is not checked out.
Error
You tried to manipulate an object (for example, checking it in to the source control project) that
was not first checked out. Check out the object from source control to continue.
149

Number
Description
2835
Do you wish to continue?
Error
During a bulk update to the source control database, an error occurred, preventing you from
modifying the selected objects. Make sure that you properly installed the source control client
software, and then configure it in the Source Control tab in the AR System Administration: Server
Information form. You can then modify objects under source control. For a detailed discussion on
source control issues, see the Integration Guide and the Configuration Guide.
2836
You are in Enforced mode of the Source Control Integration. You cannot modify the selected
objects. The server is configured for Source Control but you have not integrated it on your
client.
Error
You tried to modify objects that are under source control in Enforced mode on AR System server.
However, you do not have a source control client installed or you did not configure it properly
with your BMC Remedy Administrator client.
Make sure that you properly installed the source control client software, and then configure it in
the Source Control tab in the AR System Administration: Server Information form. You can then
modify objects under source control. For a detailed discussion on source control issues, see the
Integration Guide and the Configuration Guide.
2839
Min value should be less than Max value.
Error
When configuring the number of server threads in the Server Ports and Queue tab in the Server
Information dialog box, you tried to make the number of Min threads exceed the Max number.
Make sure that the number of Min threads is less than the number of Max threads.
2840
Min and Max value should be greater than 0.
Error
When configuring the number of server threads in the Server Ports and Queue tab in the Server
Information dialog box, you tried to set the number of Min and Max threads to zero.
Perform one of the following tasks:
Make sure that the number of Min and Max threads is greater than zero.
Ask yourself whether this type of server thread is necessary in your operation.
2842
The Form name has not changed. Please specify a new name.
Error
You tried to save a form under version control. To continue, change the name of the form.
2843
The specified file does not exist. Do you want to create it?
Error
You tried to retrieve an object from a source control database that does not exist on the AR System
server. Click Yes to create the object. The object is added to source control. You can then
manipulate the object as needed.
2844
Error creating the file.
Error
When you retrieved the latest version of the file from source control, an error occurred while the
file was being created on the AR System server or in the location you specified. To continue, verify
that the object exists in the source control database and that both the AR System server and the
source control database are running. If you are copying the file to a location, also check your
permissions.
2845
The specified file already exists. Do you want to overwrite it?
Error
You tried to retrieve the latest version of the file from the source control database, but the file
already exists either on AR System server or in the location you specified. Click Yes to overwrite
the existing file with the latest version from source control.
150
AR System messages

Number
Description
2846
Invalid refresh state returned.
Error
You tried to refresh the status of an object from the source control database, but an invalid status
was returned.
Verify that the objects exist in the source control database, and that both AR System server and
the source control database are running.
2847
Failed to load serverObjects from server serverName.
Warning
During the login process, the server objects that the user is permitted to see failed to load. To
continue, verify that the server is running. Also verify the users access control settings.
2848
The number of rows exceeded the maximum allowed limit of 230.
Error
In the Display tab of the Field Properties window, you tried to set the rows displayed in a form to
a number larger than 230. Enter a number equal to or less than 230.
2849
Please enter a comment. Developer comments are required for this operation.
Error
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. Add the required comment, or change
the configuration settings.
2850
No matches found in the database for the given query.
Error
When the system searched the Search Objects window for an object, no results were returned.
Objects might have been deleted or the names modified. Deleted objects do not appear even if the
database is not synchronized.
2851
Please select a source code control provider.
Error
You did not select a source control application before you clicked OK in the Source Control tab.
To enable source control integration with AR System, first select a provider from the Provider
Name drop-down list, and then click OK.
2861
Duplicate distributed pool name.
Error
When trying to create and name a Distributed Pool object, you used the name of an object that
already exists. Use a different name or rename the original object.
2862
Source Control operations cannot be performed on Distributed Pools.
Error
You tried to perform a source control operation on a distributed pool, for example, checking a
distributed pool in to source control. This functionality is disallowed with AR System integration.
2863
Missing target location text.
Error
When creating or modifying an Open Window action, you did not specify a target location. Enter
or select a target location to continue.
2864
Error: No sample server has been selected.
Error
When using the Advanced functionality for an Open Window action, you did not specify a
sample server name. Enter a sample server to continue.
2865
Error: No sample form has been selected.
Error
When using the Advanced functionality for an Open Window action, you did not specify a
sample form name. Enter a sample form to continue.
2866
Error: No view has been selected.
Error
When creating or modifying an Open Window action, you did not specify a form view. Enter or
select a form view to continue.
151

Number
Description
2867
Some items failed to import.
Error
During an import operation from source control, some of the objects were not imported. The
operation was only partially successful. To continue, verify that you have access to the objects in
the source control database, for example, by trying to access them in the source control client. If
you are successful, log back in to BMC Remedy Administrator, and retry the import operation.
2868
Warning: No field mappings have been defined.
Error
When creating or modifying an Open Window action, you did not specify a set of field/value
mappings. BMC Remedy Administrator lets you save the action, but the action does not function
properly. Create a set of field/value mappings to continue.
2871
File already exists in the current directory.
Error
When creating an application object, you cannot add a support file to your application that
already exists in the current directory.
2872
Cannot delete root element.
Error
When creating an application object, you cannot delete or change the name of the Resources
Directory Structure level under the Support Files tab.
2873
Please select an item before creating the directory.
Error
When creating an application object, you cannot create a directory before selecting a support file.
If you do not add support files to the new directory, the directory is removed from the directory
structure the next time you open the application object.
2874
Cannot add file. Directory depth exceeds the maximum allowed limit.
Error
When creating an application object, you cannot add more than 255 support files to the current
directory.
2876
Could not create the directory.
Error
The Create Directory function failed while deploying an application or a form. This error can error
because of one of several reasons, such as no disk space, duplicate directory name, or invalid
directory name.
2877
This version of the Action Request System is ready for use or evaluation without purchasing
or activating an authorization key. For unlimited capabilities, contact your sales representative
or visit http://www.bmc.com.
Note
This version of the BMC Remedy AR System has a maximum limit of 2000 requests per database
http://www.bmc.com.
2878
Alias values must be unique.
Error
When adding localized text in the Alias Value field, you need to specify a unique alias value.
2879
Modifying Packing List may result in loss of data.
Error
Your changes to this packing list in your role as a subadministrator might result in loss of data.
To continue, contact your AR System administrator for assistance in modifying this packing list.
2880
Web view is created but not initialized! Please initialize the web view by opening and saving
the web view.
Error
When you were saving the application to disk in BMC Remedy Administrator, you did not first
save the contents of the web view to the server.
152
AR System messages

Number
Description
2881
Error in converting to Open Window action.
Error
AR System could not convert the existing macro functionality to its equivalent 5.x (or later) Open
Window action. Your pre-5.x workflow still functions. However, as a workaround, you can
manually create an Open Window action as a substitute for your BMC Remedy User macro used
in workflow.
2882
Error in converting to Run Process (Preferences) action.
Error
AR System could not convert the existing macro command preferences (found in the Desktop
preferences) to its equivalent 5.x (or later) Run Process action. Your pre-5.x workflow still
functions. However, as a workaround, you can manually create an Run Process action as a
substitute for your BMC Remedy User macro used in workflow.
2883
Error in converting a macro command.
Error
AR System could not convert a keyword used in a macro command to its equivalent 5.x or later
workflow action. Your pre-5.x workflow still functions. However, as a workaround, you can
manually create a workflow action as a substitute for your BMC Remedy User macro used in
workflow.
2884
Error in converting to Run Process action.
Error
AR System could not convert the existing macro functionality to its equivalent 5.x or later Run
Process action. Your pre-5.x workflow still functions. However, as a workaround, you can
manually create a Run Process action as a substitute for your BMC Remedy User macro used in
workflow.
2885
Error in converting modify to Push Fields action.
Error
AR System could not convert the existing macro functionality to its equivalent 5.x or later Push
Fields action. Your pre-5.x workflow still functions. However, as a workaround, you can
manually create a Push Fields action as a substitute for your BMC Remedy User macro used in
workflow.
2886
Number of resultant actions exceeded the maximum; the active link will not be saved. To
enable successful conversion, please decompose the active link into multiple active links and
try again.
Error
AR System could not convert the existing macro functionality to a new set of active link actions.
The maximum number of new actions that can be created is 25.
To use the 5.x or later macro conversion tool, divide the old active link functionality into multiple
active links, and then retry the macro conversion. Alternatively, create active links that use the 5.x
or later workflow functionality.
2887
New Action cannot be inserted.
Error
AR System could not convert an existing macro to a new active link action. Your pre-5.x workflow
still functions. As a workaround, create an active link that uses the 5.x or later workflow
functionality.
2888
Succeeded.
Error
AR System was successful in converting the existing macro functionality to a new set of active link
actions.
2889
Server is referred by a keyword or field ID. Server name should be currently available to
process QBE type of queries.
Error
AR System could not convert a macro that contained the $Server$ keyword to an equivalent
qualification used by the 5.x or later workflow actions. Your pre-5.x workflow still functions. As
a workaround, create an active link that uses the 5.x or later workflow functionality.
153

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

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

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

Number
Description
2927
The following description lists active links and indicates nature of failure or success under
each RunMacro action. In case of failure, original active link will be restored. Users can see the
FAQ for resolutions and try again.
Error
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. Verify that the conversion of the query string to a
qualifier is correct.
An error indicating that the QBE cannot be loaded might indicate that the schema is
unavailable. See the following workaround.
The server is referred to by a keyword or field ID, and should be available to process QBE
queries. See the following workaround.
An error indicating that the QBE query could not connect to the server.
Workaround: The schema and server names are not available to queries and can be validated. The
schema and server names are represented by $field-id$. These values can be replaced with
specific values for conversion. After successful conversion, the administrator can see $fieldid$ by directly editing the Open Window action. When editing the Open Window action, the
administrator must choose the Advanced option, allowing the schema and server names to be
edited.
Another error that occurs when macros are converted is that the query is converted but some
field-value pairs that were in the QBE part of the query are missing.
Workaround: Verify that the fields are display fields. Because your query is on field values in
database and display fields, the database does not contain any associated values. Display fields
should not be in a QBE and are ignored during conversion.
2928
Error in converting AR System Reports keyword.
Error
When you used the Macro Conversion utility, an internal error occurred when the AR System
report command in the macro was converted.
2929
Error in finding reports end.
Error
When you used the Macro Conversion utility, an internal error occurred when the end of the
AR System report in the macro was converted.
2930
Error in creating or opening of temporary AR System Report file.
Error
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.
2931
Field with ID IDNumber is not present in this form. Looks like a corrupt field. Would you like
to delete this field?
Error
When an application was deployed, an error occurred during HTML file generation because of
nonexistent fields in the web view of the form. This corruption might be due to the user hard
coding a new field in the form. To continue, delete the field.
2932
Source Control operations cannot be performed on Extension Objects.
Error
You tried to perform a source control operation on a custom server object (for example, a
Flashboards server object). This functionality is disallowed with AR System integration.
157

Number
Description
2933
Cannot find server serverName. Possible server alias name problem.
Error
During import operation, the objects could not be imported because:
The object iteration was not constructed properly.

The server name alias embedded in the object could not be resolved properly.
If you are using a server name alias, verify that it is valid.

2934
Could not open file: fileName.
Error
When creating an application object, you cannot open the support file that you wanted to add to
your application. To continue, verify your permissions and that the support file exists and is not
corrupted.
2936
Error from Source Control ProviderInitialize failed.
Error
Source control applications return this error message. The source control engine failed. To
continue, verify that you can start the source control executable independently of BMC Remedy
Administrator.
2937
Error from Source Control ProviderUnknown project.
Error
Source control applications return this error message. The source control project could not be
found. The project name is a local directory of .def files on your system. To continue, start the
source control application and verify that the source control project exists on your system.
2938
Error from Source Control ProviderCould not create project.
Error
Source control applications return this error message. The source control project could not be
created. To continue, verify your permissions. Also, verify that you have access to the project, for
example, by opening it in the source control client.
2939
Error from Source Control ProviderNot checked out.
Error
Source control applications return this error message. You cannot modify an object under source
control unless you check it out first. To continue, check out the object.
2940
Error from Source Control ProviderAlready checked out.
Error
Source control applications return this error message. You tried to perform a source control
operation on an object checked out to another user. To continue, wait until the object is checked in.
2941
Error from Source Control ProviderFile is locked.
Error
You tried to perform a source control operation on a locked file. To continue, confirm whether
some other user is accessing the file.
2942
Error from Source Control ProviderFile out exclusive.
Error
Source control applications return this error message. You tried to perform a source control
operation on a file exclusively locked by another user. To continue, confirm whether some other
user is accessing the file.
2943
Error from Source Control ProviderAccess failure.
Error
Source control applications return this error message. You failed to access a file in use by another
user.
2944
Error from Source Control ProviderCheck in conflict.
Error
Source control applications return this error message. 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, set the source control project in AR System server to Enforced mode.
158
AR System messages

Number
Description
2945
Error from Source Control ProviderFile already exists.
Error
Source control applications return this error message. You cannot add this file to source control
because the file already exists. To continue, delete the file from the source control database first.
(When removing the object from the source control database, you lose history data.)
2946
Error from Source Control ProviderFile not controlled.
Error
Source control applications return this error message. You failed to access a file because it is not
under source control. To continue, add the file to the source control database.
2947
Error from Source Control ProviderFile is checked out.
Error
Source control applications return this error message. You failed to check out this file because it
is checked out to another user. Contact the other user if possible to resolve any administrative
issues.
2948
Error from Source Control ProviderNo specified version.
Error
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. To continue, examine the
version history of AR System objects under source control.
2949
Error from Source Control ProviderRequested operation not supported.
Error
Source control applications return this error message. You failed to access this file because this
operation is not supported by your source control application.
2950
Error from Source Control ProviderNon-specific error.
Error
Source control applications return this error message. An unspecified error was returned in your
source control provider that was not covered under any specific error conditions.
2951
Error from Source Control ProviderRequested operation not performed.
Error
Source control applications return this error message. You failed to access this file because this
operation was not performed by your source control application.
2952
Error from Source Control ProviderType not supported.
Error
Source control applications return this error message. This file type is not supported under source
control.
2953
Error from Source Control ProviderVerify merge.
Error
Source control applications return this error message. The file merge operation failed under
source control.
2954
Error from Source Control ProviderFix merge.
Error
Source control applications return this error message. The file merge operation failed under
source control. Use your source control application to repair the file merge.
2955
Error from Source Control ProviderShell Failure.
Error
Source control applications return this error message. An unspecified shell failure was displayed
by the source control application.
2956
Error from Source Control ProviderInvalid user.
Error
Source control applications return this error message. You are not a recognized user in the source
control database. Verify that an account was created for you and that you have permission to
access the source control database.
2957
Error from Source Control ProviderProject already open.
Error
Source control applications return this error message. You tried to open a source control operation
on an object that was already opened by you or another user.
159

Number
Description
2958
Error from Source Control ProviderProject syntax error.
Error
Source control applications return this error message. An unspecified project syntax error was
displayed by the source control application.
2959
Error from Source Control ProviderInvalid file path.
Error
Source control applications return this error message. You could not access files in your source
control project because of an invalid file path. To continue, verify the correct file path.
2960
Error from Source Control ProviderProject not open.
Error
Source control applications return this error message. You tried to access a file from a source
control project that was not open. To continue, open the project first.
2961
Error from Source Control ProviderNot authorized.
Error
Source control applications return this error message. You tried an operation not authorized by
your source control engine.
2962
Error from Source Control ProviderFile syntax error.
Error
Source control applications return this error message. An unspecified file syntax error was
displayed by the source control application.
2963
Error from Source Control ProviderFile does not exist.
Error
Source control applications return this error message. You tried to access a file that does not exist
under source control.
2964
Error from Source Control ProviderConnection failure.
Error
Source control applications return this error message. An attempt to connect to the source control
application failed.
2965
Rename operation failed on the Source Control Provider.
Error
Source control applications return this error message. The rename operation failed.
2966
Format of date value is not recognized.
Error
The value of a time stamp was incorrectly converted for a date type field.
2967
Cannot create or modify a Currency Field without at least one selected Functional Currency.
Please select at least one Functional Currency.
Error
You did not select a functional currency list.

2968
Incorrect precision. Please enter a single digit numeric precision.
Error
You did not define a single digit of numeric precision (for example, numbers 1 to 9) for the
Currency Codes preferences.
2969
Incorrect currency code. Please enter a valid 3 digit Currency Code.
Error
You entered an invalid currency code in the Currency Codes preferences, or left the currency code
field blank.
2970
Duplicate Operation Name. Please enter a unique name for operation.
Error
You created a duplicate operation name in the Operations List. All operation names must be
unique.
2971
Duplicate Operation Name. The name will not be modified.
Error
You modified an operation name but the operation name is not unique. All operation names must
be unique.
2972
One or both of the objects have already been mapped. Unmap and continue.
Error
You created a duplicate mapping.
160
AR System messages

Number
Description
2973
Form should be mapped before the fields.
Error
You tried to map the fields before you mapped the form.
2974
Mapping cannot be defined.
Error
Your mapping is invalid.
2975
Objects are not mapped.
Error
No objects are mapped.
2976
Objects selected do not have the same map.
Error
The web services mapping is not unique.
2977
Name should start with an English alphabet.
Error
The web services name does not use English alphanumeric characters.
2978
Name must contain alpha numeric characters only.
Error
The web services name is empty.
2979
WebService Handler is using an insecure (http) protocol. If username and password are
mapped, they will be sent in plain-text.
Error
The web service you are consuming is not secure. Any critical information (for example,
passwords) are not properly encrypted.
2984
Web service cannot be saved without any operations.
Error
You cannot create a web service that has no operations. Enter at least one operation in the
operations list.
2985
This mapping object is corrupted. Please delete the current operation and continue.
Error
The mapping you created for the web service operation is corrupt. Delete this operation, and try
creating a new one.
2986
The XML element selected has maxoccurs greater than 1. This mapping is not supported.
Error
A field cannot be mapped more than once.
2987
This mapping is not supported.
Error
In a multi-layered XML schema with a parent-child relationship, 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.
2988
Cannot create or modify a data field without specifying a corresponding DB column name.
Please specify a valid DB column name.
Error
When creating a view form, you must link data fields to an underlying database column.
2989
Error
Cannot create or modify a display-only field which has a valid DB column name. Please specify
a valid entry mode.
When creating a view form, you cannot link a display-only field to an underlying database
column.
2992
The Database Name for a Flashboard field must not be NULL.
Error
When creating or modifying a Flashboard field, you cannot leave the Name field in the Database
tab (in the Field Properties window) empty. Enter a name for the field.
2993
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.
Warning
You did not map any of the choice nodes in a XML schema.
161

Number
Description
2994
Primary key is mapped. The primary key should not be mapped.
Error
The primary key of the parent form was mapped.
2995
Primary key is not mapped. If field ID is not 1, the primary key should be mapped.
Error
A field other than the Request ID (1) is used as the primary key but not mapped to any element in
the XML schema.
2996
Distinguishing key(s) is not mapped. Map and continue.
Error
The distinguishing key in a child form is not mapped.
2997
Foreign Key(s) is mapped. Unmap and continue.
Error
One or more of the fields selected as foreign keys in the child forms are mapped.
2998
Form mapping under a choice node or a complex element of type all is not supported.
Error
One or more of the immediate children under the choice/all node are mapped to a different form.
2999
Invalid mapping because of incompatible data types. AR Datatype - Character can only be
mapped to XML Datatype - string, integer, nonPositiveInteger, negativeInteger,
nonNegativeInteger, or positiveInteger.
Error
You tried to map incompatible data types.

BMC Remedy Distributed Server Option messages
3000
If signal is 15: "AR System Distributed Server terminated by user or accidentally."
Note
If signal is not 15 "AR System Distributed Server terminated unexpectedly."

The server for the DSO process (arservdsd) was terminated by a signal. The number following
this error denotes the signal that was received.
If the signal is 15, restart the server, and continue to work. The process was stopped either
accidently or intentionally by a user in your environment.
If the signal is a number other than 15 or is one you sent directly to the process, contact Customer
Support for assistance in determining the cause of the problem. The server most likely shut down
due to a bug in the system.
3001
AR System Distributed Server terminated fatal error encountered.
Note
A fatal error occurred in arservdsd, and the process was shut down. An associated error
3002
Entry pending transfer or update has been pending for longer than the specified retry timeout.
Note
A request pending transfer or update was in the pending state for longer than the Maximum Time
to Retry interval, which is specified in the Modify Distributed Mappings form or overridden in
the distributed fields on the actual request. If the request has a Transfer or Update Status
distributed field, the field is updated to the status Time-out. The request is removed from the
pending list, and the operation is not performed.
3003
Pending distributed operation canceled due to error.
Note
An error occurred while the system tried to transfer or update a request. If a Transfer or Update
Status field is on the request, the field is updated to the status Canceled. An associated error
3004
AR System Server is not currently available will retry connection.
Note
The AR System Distributed Server Option cannot connect to the AR System server. The
connection attempt is retried periodically for several minutes. If repeated connection attempts
fail, an associated error message is generated and no further attempts are made.
162
AR System messages

Number
Description
3005
AR System Server is now available.
Note
The AR System Distributed Server Option was previously unable to connect to the AR System
server. A subsequent connection attempt succeeded.
This scenario is possible when the Distributed Server Option is started before the AR System
server is ready to accept connections.
3100
This AR System is not licensed for the Distributed Server Option.
Error
A license for the DSO process is required to use the distributed functionality of the system.
arservdsd cannot be run unless the system is licensed for it. Contact your distributor for
information about obtaining a DSO process license.
3101
Failed to open the Distributed Server lock file ar.lck.390601.
Error
AR System DSO process (arservdsd) opens a lock file named ar.lck.390601 at startup. This
file is used to prevent multiple copies of arservdsd from being started. An associated file system
error message contains details. Fix the problem, and rerun the server.
3102
An instance of the Distributed Server is already running.
Error
A computer can run only one instance of the DSO process at a time. If another DSO process is
running, no action is required.
If another DSO process is not running, you probably encountered a known problem with the NFS
lock manager on Oracle workstationsthe lock manager sometimes keeps a lock running even
when the process holding the lock is no longer running. If no arservdsd is running, delete the
lock file to free the lock, and then restart arservdsd.
3103
Memory allocation for the DSO process failed.
Error
in the DSO process. In general, this error occurs when too many processes are running or when
certain processes occupy most or all available memory on your server. Recover the memory by
3106
The server being accessed is not licensed for the Distributed Server Option.
Error
The arservtcd process might be on a target server that is not licensed to use the DSO process or
on a version 2.0 or earlier target server that does not interact with arservdsd.
3107
No Distributed Mapping form could be found on the server.
Error
A Distributed Mapping form is required for the system to support distributed operations. No
form containing all the special reserved fields indicating it is a Distributed Mapping form could
be found.
Load the Distributed Mapping form, and define the appropriate mappings.
3108
Two forms contain all the reserved distributed mapping fields delete one to continue.
Error
The system found two forms containing the reserved distributed mapping fields. Delete one form,
or change it so that it is not considered a Distributed Mapping form (remove fields in the 200 to
220 range). An associated error message identifies the forms.
3109
No Distributed Pending form could be found on the server.
Error
A Distributed Pending form is required for the system to support distributed operations. No form
containing all the special reserved fields indicating it is a Distributed Pending form could be
found.
Load the Distributed Pending form.
163

Number
Description
3110
Two forms contain all the reserved distributed pending fields delete one to continue.
Error
The system found two forms containing the reserved distributed pending fields. Delete one form,
or change it so that it is not considered a Distributed Pending form (remove fields in the 250 to 260
range). An associated error message identifies the forms.
3111
The "From" form in mapping definition must be the source form in the attempted mapping.
Error
The form defined as the From form does not match the form that is the source of this transfer.
Typically, this error occurs when a mapping specified in a transfer operation on the current server
differs from the same mapping on the original server.
3112
The "From" server in mapping definition must be the source server in the attempted mapping.
Error
The server defined as the From server does not match the server that is the source of this transfer.
3113
The "To" form in mapping definition must be the target form in the attempted mapping.
Error
The form defined as the To form does not match the form that is the target of this transfer.
3114
The "To" server in mapping definition must be the target server in the attempted mapping.
Error
The server defined as the To server does not match the server that is the target of this transfer.
3115
Unrecognized pending request type.
Error
A pending request with the pending operation tag set to an unrecognized value was found. This
error should occur only if you manually added requests to the Distributed Pending form, which
is a system form that should not be manually manipulated. If you made no manual requests to the
Distributed Pending form and encounter this error, contact Customer Support.
3116
Only the master copy of an entry can be transferred.
Error
You can only transfer the master instance of a request. The system tried to transfer the specified
request, but the Master Flag field on the request is set to No.
3117
Update unsuccessful "From" form or "From" Server field has no value.
Error
The From Form and From Server fields contain information about the previous copy of this
request (from where the request was transferred). If the Master Flag is set to Yes, the system
expects a value in the From Form and the From Server fields. If you used the ardist program to
change the Master Flag value manually, make sure that values are assigned for the From Form
and the From Server fields (you can also use ardist to change these).
3118
Failed to record a distributed command.
Error
arserverd received a request to record a distributed command or encountered a situation in

which it tried automatically to record a distributed command, and a failure occurred during
recording. Thus, the distributed command was not performed. The attempted command is
displayed in this message. An associated message contains details.
3119
The transfer or update cannot be performed because transfer mapping is currently disabled.
Error
A transfer was attempted with mapping defined in the To Mapping (or From Mapping for an
update) field. The specified mapping is disabled, so the transfer or update cannot be performed.
164
AR System messages

Number
Description
3120
The distributed operation failed because the additional information about the item to be
deleted is missing.
Error
The Distributed Delete operation requires information about the item being deleted. This
information is stored with the pending operation. If you encounter this message, the required
additional data is missing. Without this data, the operation cannot be performed. This error
should occur only if you manually added requests to the Distributed Pending form, which is a
system form that should not be manipulated manually. If you made no manual requests to the
Distributed Pending form and you encounter this error, contact Customer Support.
3121
Error
Duplicate entry IDs are encountered during transfer for specified action "Create New" - target
form is missing the required field "From Request ID".
You tried to transfer a request to the target form with ownership transferred to the new request,
thus creating a new request because of conflicting request IDs. The target form, however, does not
have a From Request ID field, which is required for this action. The From Request ID field
provides a place to store the original request ID so that the original can be updated when the copy
changes.
3122
Error
The target record for a distributed process (Distributed-Transfer, Distributed-Update,

Distributed-Return) no longer exists.
A filter invoked a distributed process (Distributed-Transfer, Distributed-Update, DistributedReturn) during the deletion of a request. If a delete operation is in progress, the distributed
process waits for the operation to be completed. When a distributed process begins, the error is
createdbecause the request against which the distributed process is run no longer exists.
Remove or disable the filter attempting the distributed operation, or reset the filter so it does not
execute on a delete operation.
3123
Error
Must map the Entry ID field to the target Entry ID field, or the From Entry ID field must be
present on the target form.
You tried a distributed transfer operation to another form by using a custom mapping with a
transfer mode of Data + Ownership, but you did not map the Request ID field on the source
form to one of these fields on the target form:
Request ID
From Request ID
Fix the mapping, and retry the transfer.

3124
Transfer with ownership requires that target form contain Master Flag field.
Error
You tried a distributed transfer operation by using mapping to another form with a transfer mode
of Data + Ownership, and the target form does not contain a Master Flag field. The target form
(identified in the error) must contain a Master Flag field if ownership is being transferred.
3125
Transfer with ownership requires that target form contain "From form" field.
Error
You tried a distributed transfer operation by using a mapping to another form with a transfer
mode of Data + Ownership, and the target form does not contain a From Form field. The target
form (identified in the error) must contain a From Form field if ownership is being transferred.
3126
Transfer with ownership requires that target form contain "From server" field.
Error
You tried a distributed transfer operation using a mapping to another form with transfer mode of
Data + Ownership, and the target form does not contain a From Server field. The target form
(identified in the error) must contain a From Server field if ownership is being transferred.
165

Number
Description
3127
Master Flag field is required on source form for transfer with ownership.
Error
A distributed transfer operation was attempted that included a mapping to another form with a
Data + Ownership transfer. 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.
3128
The reserved distributed pool fields can only exist on one form - delete duplicate to continue.
Error
The system found two forms containing the reserved distributed pool fields. Delete one of the
forms. An associated error message identifies the forms.
3129
No Distributed Pool form could be found on the server.
Error
A Distributed Pool form is required for the system to support distributed operations. No form
containing all the special reserved fields indicating it is a Distributed Pool form could be found.
3130
No Pending Errors form could be found on the server.
Error
A Distributed Pending Errors form is required for the system to log pending errors to that form.
No form containing all the special reserved fields indicating it is a Distributed Pending Errors
form could be found.
3131
The reserved distributed pending errors fields can only exist on one form -- delete duplicate to
continue.
Error
The system found two forms containing the reserved distributed pending errors fields. You must
delete one form or change it so that it is not considered a Distributed Pending Errors form. An
associated error message identifies the forms.
3132
Error
Two forms contain all the reserved distributed logical mapping fields delete one to
continue.
The system found two forms containing the reserved distributed logical mapping fields. Delete
one form, or change it so that it not considered a Distributed Logical Mapping form (remove fields
in the 290 to 292 range). An associated error message identifies the forms.
3133
No Distributed Logical Mapping form could be found on the server.
Error
A Distributed Logical Mapping form is required for the system to support logical name
replacement functionality. No form containing all the special reserved fields indicating it is a
Distributed Logical Mapping form could be found.
With this form, DSO continues to work without the logical name replacement functionality.
Load the Distributed Logical Mapping form, and define the appropriate mappings.
3134
Logical name %s is not found in logical mapping form.
Error
DSO could not find the logical name in the Distributed Logical Mapping form. Load the
Distributed Logical Mapping form, and define the appropriate mappings.
3194
Illegal value specified for -m option legal values are 0 (not master) and 1 (master).
Error
The value specified for the -m argument was not 0 (not master) or 1 (master), as required. The field
is a selection field and requires a numeric value. The value specified was either a character or an
integer other than 0 or 1. Reissue the command, and specify a legal value for this argument.
3195
Must specify the -e entryID option.
Error
To denote the ID of the request (entry) to be modified, specify the -e argument.
3196
Must specify the -s formName option.
Error
To denote the name of the form to be modified, specify the -s argument.
3197
Must specify the -x serverName option.
Error
To denote the name of the AR System server containing the form to modify, specify the -x
argument.
166
AR System messages

Number
Description
3198
A value is missing for one of the arguments for the command line option.
Error
You included an argument with no specific value on the ardist command line. Reissue the
command with values assigned to all arguments.
3199
Unrecognized command line argument.
Error
The specified command-line argument is not recognized by ardist. See the BMC Remedy
Distributed Server Option Guide for more information about valid command-line arguments.
ardist cannot execute with invalid arguments specified.
3200
Invalid dynamic permission inheritance object property format.
Error
3201
Object does not have a dynamic permission inheritance property.
Error
3202
Field defined in dynamic permission inheritance property not found.
Error
3203
Error parsing field pairs from dynamic permission inheritance property.
Error
3225
Form does not allow non-admin to delete.
Error
BMC Remedy Data Import event messages
3300
No Alert Events form could be found on the server.
Error
The server could not locate a form containing the reserved alert events field.
3301
The reserved alert event fields exist on multiple forms. They are only allowed to exist on one
form.
Error
The system found two forms containing the reserved alert events fields. Delete one of the forms.
An associated error message identifies the forms.
3302
Problem encountered during creation of the Alert Events form.
Error
The server could not successfully import the Alert Events form at startup. An associated error
3303
Must be AR_NOTIFIER user to perform this operation.
Error
The server does not allow the removal of the Alert Events form or its reserved fields.
3314
Failed to connect with alert client.
Error
A sockets error occurred while the system tried to establish communication with an alert client.
Turn on alert logging to view a trace of the communication activity.
3315
Attempt to communicate with alert client timed out.
Error
An attempted communication with an alert client did not succeed within the configured time
period. Turn on alert logging to view a trace of the communication activity.
3316
Failed to load the alert cleanup escalation.
Error
The server could not successfully import the CleanupAlertEvents escalation at startup. An
3317
Invalid alert message format.
Error
A failure occurred while the system tried to decode an alert message sent from the server to an
alert client, indicating a data transmission error.
167

Number
Description
3318
Attempt to communicate with alert client failed because the required port is in use by another
process.
Error
When attempting to send an alert to a client, the AR System server encountered a socket address
that the system was still using. This can occur on a system that is not releasing address/port
combinations in a timely manner. Turn on alert logging for more information about the server
actions taken.
3319
Unable to connect with alert client.
Error
An error occurred during an attempt to establish a connection with BMC Remedy Alert. The most
common reason for this error is a network connectivity issue. Retry the operation.
3320
The reserved server group fields can only exist on one form-- delete duplicates on other forms
to continue.
Error
The system found two forms containing the reserved server group fields, which qualifies both
forms as the AR System Server Group Operation Ranking form. Delete one of the forms. An
associated error message identifies the forms.
3321
No server group operation ranking form could be found on the server.
Error
An error occurred during the automatic creation of the AR System Server Group Operation
Ranking form. Contact your AR System administrator.
3322
Unrecognized server group operation encountered in the ranking form.
Error
A server group operation was found that the AR System server does not recognize. Use only the
supplied operation names.
3323
Creation of the server group operation ranking form failed.
Error
The AR System Server Group Operation Ranking form definition could not be imported. Check
the server error log for the cause of the problem.
3324
This configuration setting is not allowed when the server is a member of a server group.
Error
The setting of the configuration item is not allowed because it conflicts with server group
operation management. Do not set the configuration item while the server is a member of a server
group.
3325
Unable to send a server group related signal to another server.
Error
The AR System server could not successfully run a signaling process. Make sure the arsignal
utility program is in the AR System directory.
3326
Unable to find a server group entry for this server.
Error
An error occurred during the creation of a server group entry in a data dictionary table. Contact
3327
Check interval cannot be less than 30 seconds. A 30-second value is set by the system.
Warning
A value of less than 30 seconds was specified for the check interval. You cannot set the check
interval to a value of less than 30 seconds.
3328
Unable to launch an agent process to communicate with an external program.
Error
AR System was unable launch an agent process to communicate with an external program. Make
sure that the specified program is in the AR System servers directory, or if the operation is not
appropriate in the current environment, remove the ranking entry for the corresponding
operation from the AR System Server Group Operation Ranking form. Two restarts of the server
might be required to prevent the error from being reported when the operation is removed from
the ranking form.
168
AR System messages

Number
Description
3329
A floating license without server group tag cannot be used in a server group. This floating
license is ignored.
Error
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. Replace
the license definition with a license that has a server group tag.
3330
Error
A floating license with server group tag cannot be used on a stand-alone server. This floating
license is ignored.
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. Replace the license definition with a license that does not have a server
group tag.
3331
Error
A floating license with a different server group tag cannot be used on this server group. This
floating license is ignored.
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.
3332
The change of this setting will only take effect after AR System server restart.
Warning
The Server Group Member option was changed and the new value does not take effect
immediately. The AR System server must be restarted for the setting to take effect.
3333
Invalid or missing server group operation definition. Contact your AR System administrator.
Error
An internal table containing server group operation definitions has an invalid entry or is missing
an expected entry. Contact your AR System administrator.
3334
Invalid or missing server group license entry. Contact your AR System administrator.
Error
An internal table containing server group license entries has an invalid entry or is missing an
expected entry. Contact your AR System administrator.
3335
The Check Interval setting change will only take effect after all servers in the group are
restarted.
Warning
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.
3336
Warning
Duplicate server group ranking value encountered in the ranking form ordering cannot be
guaranteed.
A duplicate server group operation ranking was encountered during loading of the ranking data.
The name of the operation is supplied as appended text. The ordering of duplicate values is not
guaranteed to be consistent, therefore you should change the ranking values to be unique.
3340
Unable to start the arsignald process.
Error
Server group error indicating that the AR System server was unable to start the arsignald process.
Arsignald is a small process, managed by the AR System server, that is used for communication
between members of a server group. 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 that the arsignald executable is in the AR System server installation directory. If this does not
resolve the problem, make sure the AR System server has permission to run the arsignald
executable.
169

Number
Description
3341
Not enough memory to create arsignald start up info
Error
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. Although this is not a fatal server
error, it is unlikely that the server will successfully start up when memory cannot be allocated.
Give the server more memory.
3342
Unable to write to arsignal daemon.
Error
Indicates that the AR System server was unable to issue a command to the arsignald process. This
error is caused by a broken communication pipe between the AR System server and arsignald,
possibly caused by arsignald being killed or crashing. The situation should be corrected
automatically, because the AR System server attempts to restart arsignald if it detects a
communications problem.
Report ARDBC plug-in messages

3350
Unable to locate Report form.
Error
The report plug-in could not locate a form containing the reserved Report form fields.
3351
Unable to get temporary file name for report definition file.
Error
A failure occurred while the system tried to get a temporary file name for a report definition.
3352
Unable to create temporary file for report definition file.
Error
A failure occurred while the system tried to create a temporary file for a report definition.
Additional information contains the file name.
3353
Illegal field encountered in the field list.
Error
The field list in a list retrieval contains fields that are not part of the report creation vendor forms
list of reserved or core fields. Only fields that map to individual fields on the Report form are
allowed.
3354
Illegal field encountered in the sort list.
Error
The sort list in a list retrieval contains fields that are not part of the report creation vendor forms
allowed.
3355
Illegal field encountered in the qualifier.
Error
The qualifier in a list retrieval contains fields that are not part of the report creation vendor forms
allowed.
3356
Invalid report definition encountered.
Error
While the system tried to transfer data from a formatted report definition to the fields on the
report creation vendor form, an unexpected definition format prevented proper decoding. Inspect
the contents of the report definition file for the entry.
3357
Required report field is missing.
Error
The field value list supplied to the report creation vendor form is missing a required field.
Additional information contains the field number.
3375
Cannot connect to the directory service.
Error
The host name or port number for the directory service is incorrect, or authentication with the
directory service failed.
3376
The specified LDAP URL is not formatted correctly.
Error
The LDAP search URL does not follow the standard format. The format is:
ldap[s]://hostName[:portNumber]/
170
AR System messages

Number
Description
3377
The LDAP operation has failed.
Error
The LDAP operation was unsuccessful, for example, because proper attribute names were not
specified or the operation would violate access privileges enforced by the directory service.
3378
At least one field on the form must reference the Distinguished Name attribute.
Error
At least one field on the form must reference the distinguished name attribute.
3379
To create objects, the distinguished name must have a value.
Error
The field associated with the distinguished name attribute has no value. The distinguished name
must have a value to create objects.

3380
The DN Entry for this request has timed out. Re-enter Search request.
Error
3400
Unable to access server configuration file.
Error
The BMC Portal External Authentication plug-in could not access the AR System servers
configuration file. Verify that the servers configuration file is present and accessible.
3401
External authentication endpoint URL not configured.
Error
The BMC Portal External Authentication plug-in could not locate an endpoint URL configuration
item in the AR System servers configuration file. Verify that a line with the Ext-Auth-EndpointURL label is in the configuration file.
3402
Unable to initialize web service interface.
Error
The BMC Portal External Authentication plug-in could not initialize a web service interface to
perform authentication. See the supporting text for more information.
3403
Unable to terminate web service interface.
Error
The BMC Portal External Authentication plug-in could not terminate a web service interface that
was performing authentication. See the supporting text for more information.
BMC Remedy Flashboards errors, warnings, and notes

3501
Please provide a name for the alarm.
Error
You tried to save an alarm for which you did not specify a name. To save an alarm, provide a
name.
3504
Please select a variable. An alarm cannot be saved without selecting a variable.
Error
You tried to save an alarm for which you did not select a variable. Before you save the alarm,
create a variable.
3505
You must enter a user name and message. Please enter them.
Error
You tried to save an alarm, but in the Notify Properties area of the Configure Alarm tab, you
selected a notify mechanism value other than None and you did not specify a user name and
message.
3509
Please provide a name for the flashboard.
Error
You tried to save a flashboard without specifying a name.
3515
Maximum custom range can not be less than the minimum custom range.
Error
You tried to save a flashboard with a maximum custom Y-axis value less than the minimum
custom Y-axis value.
171

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

Number
Description
3607
The following parameter(s) needed to display the chart are missing: parameters. You may need
to relogin to view the chart.
Error
The required parameters might be missing from the flashboard definition. Check the flashboard
definition.
3609
Error encoding image: imageName.
Error
3610
Error sending image: imageName.
Error
3611
General exception creating Flashboard.
Error
Contact Customer Support with a copy of the log statements for the action.
3614
There was no valid Variable for this Flashboard.
Error
The variable either is incorrectly associated with the flashboards or does not exist. Check the
flashboard definition or create another variable.
3615
Invalid chart type, valid numbers for a chart are from 0 to 5.
Error
Specify a chart type from 0 to 5.
3616
Internal error.
Error
3617
Internal error. Form meta data is invalid.
Error
3618
No history data was found in the AR System server to display this Flashboard.
Error
No history data was collected in the FB:History form for this flashboard.
3619
History data can not be displayed on a pie chart.
Error
History data can be displayed in all chart types except pie charts. To display history data, specify
a different chart type.
3620
No user-customizable parameters have been defined.
Error
User-customizable parameters have not been defined for the flashboard. See your AR System
administrator.
3621
No summary data was found in the AR System server to display this Flashboard.
Error
No history summary data was collected in the FB:History Summary form for this flashboard.
3622
There is no data available to display this chart.
Error
The AR System form defined for this flashboard contains no data.
3623
Summary data can not be displayed on a pie chart.
Error
History summary data can be displayed in all chart types except pie charts. To display history
summary data, specify a different chart type.
3624
The flashboards mid tier system cannot login to the AR System server.
Error
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.
173

Number
Description
3625
The number of data points to be plotted on the flashboard exceeds the limit.
Error
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
BMC Remedy Data Import errors, warnings, and notes (Windows)

4000
Import completed successfully number records imported.
Note
This message appears after a successful Import operation. No errors occurred during import.
4001
Import of importFileName started.
Note
System reports that the Import operation started. This message is logged only to the log file.
4002
The specified import file has only one field ensure that you specified the import file
correctly.
Warning
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.
4003
Warning
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.
4004
Warning
You have not saved or 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
Warning
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
Warning
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
Are you sure you want to delete all mappings?
Warning
System confirms the Delete All button is in both the main and Fallback mapping windows.
4008
Record number: Field fieldName truncated to number characters.
Warning
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.
4009
Are you sure you want to start importing?
Warning
System confirms that you really want to begin the Import operation.
4010
Mapping mappingName not loaded.
Warning
The specified mapping is not loaded. Earlier messages described why.
174
AR System messages

Number
Description
4011
Duplicate name for mapping. Do you want to overwrite the existing mapping?
Warning
A mapping with the name you specified already exists. If you overwrite it, the earlier mapping is
replaced by the new one.
4012
Exit Import Tool?
Warning
System confirms that you want to exit BMC Remedy Data Import.
4013
Did not find any matching fields to add as new mappings.
Warning
The Add All button operation did not find any matching form and import fields to add as
mappings.
4014
Copy unprocessed import records to the log file?
Warning
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.
4015
Warning
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
Warning
You made but did not save changes to the Save Mapping window. If you continue, your
changes will be lost.
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.
4017
This file contains duplicate or empty field titles. A number has been appended to those titles.
Warning
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.
4018
This file contains duplicate or empty field titles. Those titles have been replaced by their field
ids.
Warning
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.
4019
Warning
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.
4102
Invalid AR Export format file: importFileName.
Error
The specified import file is not in AR Export format, which you specified it to be.
4104
Import completed with errors: number records were imported; number records were not.
Error
The Import operation was completed. View the log file to see the error messages and records that
did not get imported.
175

Number
Description
4105
The import operation was terminated by user.
Error
The user terminated the Import operation after it started.
4106
Copying remaining records of importFileName to log file.
Note
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.
4108
The message broadcast was stopped.
Error
During a broadcast of messages within Windows, the broadcast message was stopped.
4110
The record starting at the specified offset cannot be read.
Error
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.
4112
No mapping selected to delete.
Error
You tried to delete a fallback mapping in BMC Remedy Data Import without first selecting one.
4114
No saved mappings specified in batch mode.
Error
The tool is running in batch mode, but you did not specify which mapping to use for import on
the command line.
4116
Cannot get children widgets, or widget not a child.
Error
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.
4118
Cannot login to any AR Server.
Error
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.
4120
Two mappings have been specified on the command line. Only one mapping is allowed.
Error
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.
4122
The -m option requires a mapping name.
Error
You used the -m flag on the command line, but did not supply a mapping name following the
flag.
4124
The mapping name is longer than the maximum allowed length.
Error
You specified a mapping name that is longer than 30 characters.
4126
A directory may be specified only if you specify a mapping.
Error
You used the -d flag on the command line, but did not also specify a mapping with the -m flag.
4128
fieldName is not a Form Field.
Error
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.
4130
fieldName is not an import field name, id, or keyword.
Error
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.
176
AR System messages

Number
Description
4132
Cannot get the status of or cannot open log file.
Error
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.
4134
A log file name is required.
Error
You erased the log file name and clicked Save in the Preferences window.
4135
Log file pathName is not a valid filename.
Error
You specified a directory in the log file text field.
4136
Import log file name is longer than the maximum allowed length.
Error
You specified a log file name longer than 255 characters.
4137
Log file fileName is not a regular text file.
Error
You specified a log file that is a special file type instead of a normal text file. Choose another file
as the log file.
4138
Cannot write to log file.
Error
A system error occurred while writing the log file. The system error is the second part of this
message.
4140
Cannot initialize the server API.
Error
BMC Remedy Data Import cannot initialize the server API and so cannot establish a connection
to AR System server.
4142
Cannot open the main import window.
Error
BMC Remedy Data Import could not create the main window, and the tool could not be started.
The system is probably out of memory.
4144
Bad parameters.
Error
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.
4146
Bad global variables.
Error
4148
Cannot add to mapping list.
Error
4150
Cannot set mapping list item.
Error
4153
Cannot open mapping file for specified mapping.
Error
The mapping file that contains the specified mapping cannot be opened. You might have moved
the file or the directory that contained the mapping.
4154
Cannot find specified mapping.
Error
4155
Cannot read mapping file for specified mapping.
Error
The mapping file that contains the specified mapping cannot be read. The file probably has
incorrect permissions set.
177

Number
Description
4156
The import option value is invalid.
Error
4158
The mapping file has a syntax error.
Error
The mapping file contains invalid syntax. This is probably caused by a user who edited the
mapping file manually. Fix the syntax as necessary.
4160
Bad Mapping or Compound mapping within Compound mapping.
Error
4164
Import fields titles-list is invalid.
Error
4166
Bad Mapping list.
Error
4168
Bad Fallback Mapping list.
Error
4172
Record number: Cannot parse record in import file.
Error
The tool could not understand this record in the import file. This condition could result from low
memory.
4174
Cannot parse import field titles in import file.
Error
The tool could not understand the field titles in the import file. This condition could result from
low memory.
4175
Specified import file does not exist.
Error
You specified a nonexistent file as the import file, or you removed the file after BMC Remedy Data
Import started.
4176
Syntax error in the mapping string.
Error
The tool could not understand the syntax in the mapping value string. Rewrite the mapping.
4177
Specified import file is a directory.
Error
You specified a directory as the import file.
4178
Specified import file is not a regular text file.
Error
You specified an import file that is a special file type instead of a normal text file.
4179
Cannot get the status of import file.
Error
The import file, or the directory it is in, is no longer accessible.
4180
Specified import file is empty.
Error
The import file is of length zero.
4182
Specified import file has no data.
Error
The Import file contains only field titles (if that) and no data.
4184
An import file name is required.
Error
You tried to close the Open Import File window without specifying an Import file.
178
AR System messages

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

were truncated.
Note
After you choose the Truncate option in the Preferences dialog box and records are truncated, this
message indicates how many records were truncated and imported.
4214
End of numberOfCopiedRecords records.
Note
This message is printed in the log file at the end of all copied records from the Import file. You
never see this message in a dialog box.
179

Number
Description
4216
Import completed with errors: numberImported records were imported; numberNotImported

records were not; numberTruncated records were truncated.
Error
After you choose the Truncate option in the Preferences dialog box and records are truncated (and
some records not imported due to errors), this message indicates how many records were
truncated and not imported.
4218
Only one -d argument is allowed on the command line.
Error
Only one -d argument is allowed on the command line.
4220
The mapping file could not be created.
Error
The mapping file could not be created. The error was displayed in previous dialog boxes.
4222
No mappings are defined.
Error
You chose the Load Mapping menu item, but no mappings files exist in $ARHOME/arcmds or in
any of the directories on the ARPATH environment variable.
4224
The receiving window was not able to handle the message broadcasted.
Error
A window broadcast a message to another window, and that window could not handle the
message.
4226
Record number: a field exceeds the maximum size allowed.
Error
A field of the specified record exceeded 32,767 bytes (one byte less than 32 kilobytes). You can take
one of the following actions:
Exit the record to make the field shorter.

Turn on the truncate character fields value option if it is a character field.
4227
Cannot open the default import log file.
Error
The default import log file (/tmp/arimport_user.log on UNIX and arimport.log in the
ARHOME directory on Windows) cannot be opened. Verify the file path to make sure that enough
disk space exists and that all the directories exist.
4499
User stopped import after numberProcessed records were processed, of which numberImported
were imported.
Warning
You stopped the import process before it was completed. This message indicates how many
records were processed and how many were imported.
AR System application servers, including BMC Remedy Approval Server
4500
AR System Application server terminated when a signal/exception was received by the server.
Note
A signal terminated the approval engine. It was terminated either accidentally or intentionally by
a user in your environment. The number following this error is the signal that was received. If the
signal is 15, you should be able to restart the server and continue to work.
4501
AR System Application server terminated fatal error encountered.
Note
A fatal error occurred within the approval engine. Details are in an associated message. This
message indicates that the error was fatal and the approval engine is shutting down.
4502
Operation cancelled due to error.
Note
The command could not be performed because of an unspecified error. The command that failed
is included in this message.
4503
AR System Application server restarting.
Note
180
AR System messages

Number
Description
4510
Two or more roles have the same name.
Warning
The system encountered two or more entries in the Approval Role form for the specified name.
The system does not allow this. Delete or change one entry. The name is included in this message.
4511
No Approval Administration form was found.
Warning
The system could not locate the Approval Administration form. Generally, this means that the
Approval subsystem is not installed. The form is found by searching for a form with a specific tag
in the Change History field, so it is also possible that the Change History field is corrupted.
4512
No Approval Notification form was found.
Warning
The system could not locate the Approval Notification form. Generally, this means that the
4513
No Approval Form form was found.
Warning
The system could not locate the Approval Form form. Generally, this means that the Approval
subsystem is not installed. The form is found by searching for a form with a specific tag in the
Change History field, so it is also possible that the Change History field is corrupted.
4549
The supplied password is invalid for the user performing the operation.
Error
The approval process is configured to require users to enter their password to approve or reject a
request. Either the password was not supplied, or the supplied password was invalid for the user
performing the operation.
4550
Creation of an application form failed.
Error
During the creation of the Application Pending form, an error occurred. Details are in an
associated message. To re-create the form, correct the reason for the failure, and restart the
arserverd process (or send a SIGHUP signal).
4551
Must be Application Server user to perform this operation.
Error
To run the specified delete operation and mapping forms, you must be the AR System
Application Service user (process). The forms should be considered part of the system structure
and should not be deleted or modified. To delete one or both of the forms, use AR System
Developer Studio to select the forms for deletion, and ignore the system warning related to the
forms.
4552
The reserved application pending fields can only exist on one form. delete duplicates to
continue.
Error
The system encountered two forms that have all the reserved application pending fields. The
system cannot work correctly if two forms contain pending information. Delete one of the forms,
or change it so that it is not considered an Application Pending form by removing fields in the 250
to 260 range. An associated error message identifies the forms.
4553
No Application Pending form could be found on the server.
Error
An Application Pending form is required for the system to support application operations. No
form containing all the special reserved application pending fields was found. Load the
Application Pending form.
4554
An application command failed.
Error
The system received a request to record a command or encountered a situation in which it

attempted to record one automatically, and a failure was encountered during recording. Thus, the
command was not performed. The attempted command is displayed with this message. An
associated message contains more information.
181

Number
Description
4555
Command requires a form name be specified.
Error
The parsing or formatting command requires a form name. None was specified. Check the syntax
of the command, and enter a form name as required.
4556
Form name specified on command is not valid.
Error
The specified form name is invalid on the system. The specified form name must be the name of
an existing form.
4557
Parse set fields command requires two forms be specified.
Error
The parse set fields command requires that two forms be specified. Either none or only one was
specified.
4558
Qualification line error.
Error
An error was detected in the qualification line. Additional information identifies the error and the
position in the qualification where the error occurred.
4559
Assign line error.
Error
An error was detected in an assignment line. Additional information identifies the error and the
position in the assignment where the error occurred.
4560
No Approval Details form could be found on the server.
Error
A request was made for finding forms joined to the Approval Details form, but no Approval
Details form exists on the system. Generally, this means that the Approval subsystem is not
installed. The command is not valid without the Approval subsystem.
4561
Command requires a field name specified.
Error
The command requires that a field name be specified. Review the syntax and retry the command
with the appropriate field name specified.
4562
Field name specified on command is not valid.
Error
The field name specified for the command is invalid within the indicated form. The command
requires that a valid field name be specified.
4563
Command requires an entry ID specified.
Error
The command requires that a Request ID be specified. Review the syntax of the command, and
retry the operation.
4564
Entry ID specified on command is not valid.
Error
The Request ID specified for the command is invalid.
4565
No Approval Signature form could be found on the server.
Error
A request was made that requires access to the Approval Signature form, but no Approval
Signature form exists on the system. Generally, this means that the Approval subsystem is not
installed. The command is invalid without the Approval subsystem.
4566
No Approval Detail-Signature join form could be found on the server.
Error
A request was made that requires access to the Approval Detail-Signature form, but no Approval
Detail-Signature form exists on the system. Generally, this means that the Approval subsystem is
not installed. The command is invalid without the Approval subsystem.
4567
Command requires appropriate parameters.
Error
One or more expected parameters are missing from a process command.
4568
The start or end time provided for the command is not valid.
Error
182
AR System messages

Number
Description
4577
No Approval Server licensecannot run the approval engine.
Error
BMC Remedy Approval Server checks licensing to determine whether a server is licensed for
approval functionality. For an approval license to exist, a valid server license must exist because
the server license is the base license and the approval license is an option. Make sure that the
server license is valid and implemented.
4578
There are two forms with the same license tag.
Error
Limited licensing is in effect for approvals, and the system encountered two forms with the same
license tag. Only the first form found with the tag will be loaded.
4579
The Approval Server is in Limited licensing mode and no form associated with this limited
license tag is found.
Error
Limited licensing is in effect for approvals, and the system could not find any form with the tags
in the limited license tag list. This is an error condition.
4580
Error
The Approval Server is in Limited licensing mode and this form does not have the proper
limited license tag.
Limited licensing is in effect for approvals, and the system could not find a license in the limited
license tag list for the specified form. The form name is identified in the message.
4581
Memory allocation failed in Approval Server.
Error
4582
Error
Another instance of the Approval Server is already running or the Application Dispatcher is in
use.
4583
Unable to open the Approval Server lock file.
Error
The system encountered an error while attempting to open the Approval Server lock file
ARServerInstallDir\arserver\db\ar.lck.390609.
4584
Duplicate Approval Detail form found.
Error
The system encountered two forms designated as the Approval Detail form. 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.
4585
Duplicate Approval Signature Line form found.
Error
The system encountered two forms designated as the Approval Signature Line form. 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.
4586
No Approval Signature Line form was found.
Error
The system could not locate the Approval Signature Line form. Generally, this means that the
4587
Duplicate Approval Process Definition form found.
Error
The system encountered two forms designated as the Approval Process Definition form. 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.
4588
No Approval Process Definition form was found.
Error
The system could not locate the Approval Process Definition form. Generally, this means that the
183

Number
Description
4589
Command requires form and entry ID be specified.
Error
Parameters are missing from the command to the Approval Server. An associated message with
the actual command was sent to the Approval Process administrator.
4590
Duplicate Approval Rule Definition form found.
Error
The system encountered two forms designated as the Approval Rule Definition form. The system
4591
No Approval Rule Definition form was found.
Error
The system could not locate the Approval Rule Definition form. Generally, this means that the
4592
Duplicate Approval Alternate form found.
Error
The system encountered two forms designated as the Approval Alternate form. The system does
not allow this. One of the forms must be deleted for the Approval system to work correctly. An
4593
No Approval Alternate form was found.
Error
The system could not locate the Approval Alternate form. Generally, this means that the
4594
Duplicate Approval More Information form found.
Error
The system encountered two forms designated as the Approval More Information form. The
4595
No Approval More Information form was found.
Error
The system could not locate the Approval More Information form. Generally, this means that the
4596
Duplicate Approval Process Administrator form found.
Error
The system encountered two forms designated as the Approval Process Administrator form. The
4597
No Approval Process Administrator form was found.
Error
The system could not locate the Approval Process Administrator form. Generally, this means that
the Approval subsystem is not installed. The form is found by searching for a form with a specific
tag in the Change History field, so it is also possible that the Change History field is corrupted.
4598
Duplicate Approval Role form found.
Error
The system encountered two forms designated as the Approval Role form. The system does not
4599
No Approval Role form was found.
Error
The system could not locate the Approval Role form. Generally, this means that the Approval
subsystem is not installed. The form is found by searching for a form with a specific tag in the
Change History field, so it is also possible that the Change History field is corrupted.
184
AR System messages

Number
Description
4600
The approval process for the indicated entry ID is already in progress. New approval detail
entry cannot be created.
Error
An approval is in progress for the indicated approval process and entry ID, so a new approval
detail entry will not be created.
4601
Multiple Next Approvers found but the current setting only allows one.
Error
More than one Next Approver record was returned for the entry, and a Get Next Approver rule
for the approval process is configured to return an error when multiple rows are returned. The
operation has stopped. Either change the rule to allow multiple next approvers, or specify only
one next approver for this entry.
4602
AR System server does not support AR System Application Service user.
Error
This can occur when AR System 5.1 is used with Approval Server 4.x. Either upgrade your
Approval Server to 5.1, or remove your AR System Application Service password.
4603
Field specified for first approver is not defined on the form.
Error
The field defined to specify the first approver for the process does not exist on the application
form. The field ID is appended to this message. If the process is defined as Ad Hoc, the operation
stopped. If the process is defined so that Anyone can specify the next approver (see the BMC
Remedy Approval Server Guide), the operation will continue after this message.
4604
Sig-xxx command requires form to be the approval signature line form.
Error
The issued command (sig-approved, sig-rejected, sig-cancelled, sig-reassign,

sig-notify) must come from the AP:Signature form.
4605
Sig-xxx command requires process to match details if process is specified.
Error
The process specified in the issued command (sig-approved, sig-rejected,

sig-cancelled, sig-reassign, sig-notify) does not match the process specified in the
details record of this pending approval request.
4606
Multiple approval process are associated with this application, but none is specified for this
new approval process to use.
Error
Your application has two or more approval processes configured for it, but the issued command
(Add-sig or New-details) did not specify which one to use for the new approval.
4607
Process allows only one next approver but two or more were specified.
Error
The process was configured to allow only one approver, but more than one approver was entered
in the Next Approvers or Reassign To field.
4608
MoreInfo-xxx command can only be issued from the More Information form.
Error
The issued MoreInfo-Return command must come from the AP:More Information form.
4609
The specified process cannot be found.
Error
The process specified in the AP:Notification entry or in the issued command (Add-sig,
New-details, sig-approved, sig-rejected, sig-cancelled, sig-reassign, or
sig-notify) does not exist.
4610
No process is associated with this form.
Error
No process is associated with your approval application form, so the operation stopped. Before
using a form for approvals, configure a process for it.
4611
No join is defined between the form and the approval detail form.
Error
Before you use the Approval Server with your application, join your application form to the
AP:Detail form. For instructions, see the BMC Remedy Approval Server Guide.
185

Number
Description
4612
No join is defined between the approval detail and signature line forms.
Error
Before you use the Approval Server with your application, join your application form to the
AP:Detail-Signature form. For instructions, see the BMC Remedy Approval Server Guide.
4613
The issued Update-config command did not have a tag for the config parameter.
Error
The issued Update-config command did not have a tag for the config parameter. If you are
making approval configuration changes in the Server Settings form, try again.
4614
The field IDs for the fields specified in the Send to Other, Subject, and Message fields in the
AP:Notification entry could not be identified.
Error
The field names specified in the Send to Other, Subject, and Message fields in the AP:Notification
entry could not be converted to their field IDs. The actual error is appended to this message.
4615
A join form of the Detail-Signature form cannot be found.
Error
See error number 4612.
4616
Duplicate Approval Administration forms found. Only one is allowed.
Error
The system encountered two forms designated as the Approval Administration form. The system
4617
Duplicate Approval Notification form found. Only one is allowed.
Error
The system encountered two forms designated as the Approval Notification form. The system
4618
Duplicate Approval Form form found. Only one is allowed.
Error
The system encountered two forms designated as the Approval Form form. The system does not
4619
Duplicate Approval Preview Signature Line form found. Only one is allowed.
Error
Only one form can have this designation. This message appears when the approval engine starts.
To resolve this problem, designate only one Approval Preview Signature Line form.
4620
No Approval Preview Signature Line form was found.
Error
An Approval Preview Signature Line form is required, but no form was designated for this
purpose.
4650
The Completion field is required on Detail form but is missing.
Error
The Completed? field (ID 13004) is missing from the AP:Detail form.
4651
The Form field is required on Detail form but is missing.
Error
The Application field (ID 10050) is missing from the AP:Detail form.
4652
The Entry ID field is required on Detail form but is missing.
Error
The Entry ID field (ID 8) is missing from the AP:Detail form.
4653
The Next Approver field is required on Sig Line form but is missing.
Error
The Next Approvers field (ID 13205) is missing from the AP:Signature form.
4654
The Process field is required on Detail form but is missing.
Error
The Process field (ID 10000) is missing from the AP:Detail form.
4810
Duplicate category names found.
Warning
186
AR System messages

Number
Description
4820
Insufficient memory for Set Up and Move server.
Error
4830
Same tag is associated with more than one form. This is not allowed.
Error
4831
The tag is not associated with any form.
Error
4836
Entry ID (0 is top level) or category tag is required for this command.
Error
BMC Remedy Email Engine errors and warnings
4900
Invalid Value.
Error
An invalid value was supplied, such as a user name or a server name. Verify your input email
message. Contact your AR System administrator if necessary.
4901
An attempt was made to initialize a mail box that was already initialized.
Error
An attempt was made to initialize a mail box that was already initialized. Verify your email
configuration or review the email engine logs to diagnose the problem.
4902
One of the fields is empty.
Error
A NULL value was supplied, such as for a user name or a server name. Verify your input. Contact
your AR System administrator if necessary.
4903
A ":" is missing between the field label and the value in your input.
Error
A colon was not supplied after the label name in supplying field values. This error can occur while
parsing an instruction. Supply a colon (:) between the field label and the value in your input.
4904
Missing Field Label in field value.
Error
The field value was supplied without the field label in the email message. Supply the field label.
4906
Missing XML <> tag in the email message.
Error
An expected XML tag is missing in the email message. Supply the missing XML tag.
4907
Missing name value tag in HTML email message.
Error
An expected HTML tag is missing in the email message. Supply the value tag.
4908
Invalid field value.
Error
An invalid field value was supplied, such as a non-numeric value for an integer field. Supply the
correct value, depending on the field type in the incoming email message.
4909
Missing the action Instruction.
Error
The expected header instruction action is missing from the email message. Supply the action
instruction.
4910
Unable to create the outgoing mail message.
Error
An outgoing email message cannot be created because certain information is missing or an

internal error occurred. Review the email engine logs to diagnose the specific problem.
4911
Unable to locate the specified User Instruction.
Error
The user instruction specified in the email message does not exist. Verify that the specified user
instruction exists in AR System Email User Instruction Templates form. Contact your AR System
administrator if necessary.
187

Number
Description
4912
Command Line Parameter already defined.
Error
The command-line parameter is specified more than once. The message contains the parameter
that is specified more than once. Specify the parameter only once.
4913
Command Line Parameter not defined.
Error
A required command-line parameter, such as a server name, is not specified in the email engine
startup script. The message provides a description of the missing information. Provide the
missing parameter.
4914
Command Line Parameter Value is missing.
Error
A command-line parameter is specified without a value in the email engine startup script. The
message provides information about which parameter value is missing. Provide the missing
parameter value.
4915
Command Line Parameter is not valid.
Error
An invalid parameter or an invalid value for a parameter is specified in the email engine startup
script. The message provides information about which parameter is invalid.
4916
Invalid Email configuration values in the EmailDaemon.properties file.
Error
Invalid configuration values in the EmailDaemon.properties file. Review the

EmailDaemon.properties file to see if anything is missing.
4918
A required action parameter, such as a form name or a request ID, is missing in the incoming
email message. Please enter the parameter and continue.
Error
A required action parameter, such as a form name or a request ID, is missing in the incoming
email message. The message provides information about the missing parameter.
4919
The supplied data type does not match the data type required for the field.
Error
You cannot modify the form because an invalid value was supplied. The supplied data type does
not match the data type required for the field. Provide the correct value for the field.
4920
An expected attachment was missing while processing an incoming email message. Please
provide the expected attachment.
Error
An expected attachment was missing while processing an incoming email message. Provide the
expected attachment.
4922
The security key provided in the incoming email message is disabled.
Error
The security key provided in the incoming email message is disabled. Contact your AR System
administrator.
4923
The security key provided in the incoming email message has expired.
Error
The security key provided in the incoming email message expired. Contact your AR System
administrator.
4924
An invalid security key was entered. Verify that the security key entered is present on the
AR System Email Security Form. If the problem still occurs, contact your AR System
administrator.
Error
An invalid security key was entered. Verify that the right security key was entered. If the problem
still occurs, contact your AR System administrator.
4925
Error
The security key does not match the originating email address. Verify that you specified the
correct security key for the email address used.
The security key does not match the originating email address. Verify that you specified the
correct security key for the email address used.
188
AR System messages

Number
Description
4927
No login information was specified or the specified login information is invalid.
Error
No login information was specified or the specified login information is invalid. Check the email
sent.
If login information was specified, make sure that the email mailbox is set to use the user supplied
login information.
4928
Error
The specified instruction cannot be found in the AR System Email User Instruction Templates
form.
The specified instruction cannot be found in the AR System Email User Instruction Templates
form. Check the instruction specified or contact your AR System administrator if necessary.
4929
The specified template cannot be found in the AR System Email Templates form.
Error
The specified template cannot be found in the AR System Email Templates form. Verify that the
correct template was specified or contact your AR System administrator if necessary.
4930
Unable to encrypt the modify key. Contact Customer Support.
Error
A problem occurred in encrypting the modify key. Contact Customer Support.
4931
Unable to decrypt the modify key. Contact Customer Support.
Error
A problem occurred in decrypting the modify key. Contact Customer Support.
4932
The modify key contains an invalid entry ID. Make sure that the modify key was not modified
and that the original outgoing email message was not deleted.
Error
The modify key contains an invalid entry ID. Make sure that the modify key was not modified
and that the original outgoing email message was not deleted.
4933
The modify key contains an invalid AR System server name.
Error
The modify key contains an invalid AR System server name. Make sure that the modify key was
not modified and that the original outgoing email message was not deleted.
4934
The modify key in the incoming modify action email message is invalid. Make sure that the
modify key was not modified.
Error
The modify key in the incoming email message with modify action is invalid. Make sure that the
modify key was not modified.
4935
Error
The modify key is missing from the incoming modify action email message, unable to execute
Instructions.
The modify key is missing from the email message with the modify action. Make sure that the
modify key was not deleted from the message.
4936
Modifications are disabled on this mailbox. Contact your AR System administrator.
Error
Modify actions are disallowed for the incoming mailbox. Contact your AR System administrator.
4937
The email message with the modify action is missing a security key. Provide the security key.
Error
The email message with the modify action is missing a security key. Provide the security key.
4938
Invalid Date/Time format for specified date field. The correct format is format.
Error
An invalid format was used for the date/time fields. This error message gives details about the
correct date/time format. Supply values for the date/time fields in the suggested format.
4939
An unknown system error occurred. Contact Customer Support.
Error
An unknown system error occurred. Contact Customer Support
4940
No email address is specified for the email message.
Error
No email addresses are specified for the email message. Verify that the email address was
specified.
189

Number
Description
4941
No matching entries found for the qualification. Verify your qualification or contact your AR
System administrator.
Error
No matching entries were found for the qualification. Verify your qualification or contact your
AR System administrator
4942
Error
Problem with the connection to the AR System server. Wait for the email engine to reconnect
to the server and complete all pending actions. If the connection is not reestablished, then
check the AR System server and then check network connectivity.
A problem has occurred with the connection to the AR System server. Wait for the email engine
to reconnect to the server so that all pending actions can be completed. If the connection is not reestablished within timeInterval, then check whether the AR System server is running, and if it is,
then check the network connectivity.
4943
Form is missing. Will retry to verify existence of form in numberMinutes minutes.
Error
The AR System Email Mailbox Configuration form does not exist or the AR System server is
unavailable. Contact your AR System administrator.
4944
The supplied value for an option (radio button) or a drop-down list item is invalid. Verify that
you provided the correct value.
Error
The supplied value for an option (radio button) or a drop-down list item is invalid. Verify that you
provided the correct value.
4945
Sender address not found in originating email.
Error
The email address of the sender of the modify email is not found in the original email message.
Contact your AR System administrator.
4946
No field values were specified for submit or modify operation. Specify values for the action.
Error
No fields were specified for submit or modify operation. Specify values for the action.
4947
Missing currency code for the currency value specified.
Error
A currency value was specified without a currency code. Specify a currency code for the value.
4948
Attachment file size exceeds the limit set in emaildaemon.properties.
Error
The attachment is too large. See your AR System administrator.
4949
Email address contains invalid characters.
Error
Invalid characters were found in the email address for the email message. Verify that the email
address that was specified correctly.
4950
Variable replacement with a qualification requires a form and a server.
Error
If you use variable replacement with a qualification, supply a form name and an AR System
server name.
4951
None of the recipients have access to form: formName.
Error
The required form access permissions are unavailable. See your AR System administrator.
4952
Incoming Message's From Or Reply-To is same as Incoming MailBox's User configured in

AR System Email Mailbox Configuration form which may cause circular mails.
Error
The name in the From or Reply-To field of the current email message is the same as the incoming
mailbox user name; this may cause a message loop. Use a different name in the From or Reply-To
field of the current email message.
190
AR System messages

Number
Description
4953
Message will be deleted without logging in email messages form because there is an error on
submit.
Error
The Store entry has not been created for the current email message, because it was not saved in
the database. This problem may occur due to the AR System server being unavailable, a database
connectivity issue, or a connectivity issue between the AR System server and the email engine.
Check whether all of these are working and then resend the message.
5000
Cannot connect to serverName.
Error
The store is not connected. If the user is working against an AR System server, the user has not
logged in to the server. If the user is working against a different store implementation, the store
has not been initialized.
5001
The cache could not be updated for an object. For more information, see the log file.
Error
The cache could not be updated for an object. For more information, see the log file.
5002
Unable to retrieve field list for form formName.
Error
5003
Invalid store for objectName.
Error
The store attached to a specific model object is invalid. This is an error intended for Java
developers who are developing plug-ins for BMC Remedy Developer Studio, and does not effect
users. Assign a valid store instance to the object.
5004
No field limit information available for field fieldName type type.
Error
This is an internal error message used for debugging purposes.
5005
No metadata available for limit limit for field fieldName.
Error
5006
Object is not editable.
Error
5007
The property property for field fieldName is invalid expect value, got value.
Error
5008
Unable to set the value for the property ID ID of field fieldName.
Error
5009
Property property of field FieldName not described in metadata.
Error
5010
The property property of field fieldName has an unexpected enum value value.
Error
5011
Unable to update the enum value value of field fieldName.
Error
5012
The current object reservation setting requires Subadministrators to have permission for
accessing the form formName.
Error
Object reservations are stored as entries on a form on the AR System server. This error is
generated if subadministrators do not have permissions to the form. Modify the form to give
subadministrators permission to it.
5013
Unable to open the binary file fileName.
Error
191

Number
Description
5025
No field mappings have been defined.
Warning
You did not define any field mappings.
5026
The field label label is duplicated on this form.
Warning
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.
5027
The form cannot be saved. A dynamic field value in tableFieldType tableFieldName contains an
invalid field or keyword reference. Provide a correct dynamic value.
Error
A dynamic field value was specified that does not match a field reference on the current form or
a keyword. Enter a field reference or select a keyword from the list for the field.
5028
Unable to add a menu item because there are too many levels in the character menu. Character
menus cannot exceed 15 levels.
Error
Menus can contain a maximum of 15 levels. You specified a menu that contains more than 15
levels at some point in its hierarchy.
5029
The entry point guide will not be executed because it does not have a starting active link.
Warning
An entry point guide was created without a starting active link. The entry point guide cannot
execute correctly in an Application List field without a starting active link. Specify a starting active
link for the active link guide.
5030
The error handler does not exist to validate the property.
Error
The error handler does not exist to validate the property.
5031
Object is already owned by another application: objectName : applicationName.
Error
This object has an application owner and cannot be added to this application. To add the object to
this application, first remove it from the application that owns it.
5032
You cannot create or modify a view form data field without specifying a corresponding
database column name. Specify a valid database column name for field. fieldName.
Error
When creating a view form, you must link data fields to an underlying database column.
5033
The field on this form with the name or ID of name|ID needs a label.
Warning
You applied changes to a form that contains a field with a blank label.
5034
All subsequent calls will be deleted.
Warning
When you try to delete an OLE method, a warning is returned that all subsequent methods (if
nesting was done) will be deleted.
5035
You cant call another method on the parent method because parent return type is not an object.
Error
IDispatch, VARIANT, or Compatible. If the parent methods return type is not one of these types,
this error is returned.
5036
The return type of the method selected and method to be added appear to be incompatible.
Select a matching function.
Error
When you define an OLE method that has a return type and you try to nest or call another method
on this return type, BMC Remedy Developer Studio validates whether the return type is of type
object. You can call or nest another method out of this return type only if the return type is of type
object or object pointer.
5037
Empty COM method list. Add at least one COM method.
Error
The method list required when you define an OLE Automation active link action is empty.
Provide at least one method for this structure.
192
AR System messages

Number
Description
5038
The OLE method called has an incompatible return type.
Error
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, or you tried to enter a value for a
parameter of type pointer. The parameter can be filled only by nesting another method whose
return type is compatible.
You can also use $fld$ to enter the value for a pointer parameter. AR Runtime gets or sets the
value of the $fld$ and treats this field as an OLE pointer variable.
5039
The parameter or return value is incompatible. Enter a value with compatible type.
Error
When you provide a value for a parameter, BMC Remedy Developer Studio tries to map it to the
OLE methods parameter OLE type. If the conversion is unsuccessful, this error message is
returned explaining that the value cannot be converted to the native OLE parameter type.
5040
A network connection cannot be established to AR System server: serverName. errrorMessage/

Reason.
Error
The server is inaccessible for one of these reasons:
A network connectivity problem exists. Issue a ping command to the server. You must solve
all network connectivity problems before you can use the AR System server.
If no network connectivity problem exists, make sure that the server process (arserverd) is
running. If it is not running, ask your AR System administrator to start it.
If the server is 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. If no entry is in the file or window, add the entry.
If the connection is still unsuccessful after you eliminate these potential causes, shut down and
restart BMC Remedy User. The server might have been temporarily inaccessible.
5041
propertyName cannot be empty.
Error
Supply the missing value.
5042
The field length for fieldName cannot exceed number characters.
Error
Specify a field length that is within the listed number of characters.
5043
The value for fieldName must be in the range between value and value.
Error
Specify a value that is within the listed range.
5044
The referenced field fieldName does not exist.
Error
5045
Field fieldName is not found on form formName.
Error
5046
The value of field fieldName cannot be less than fieldValue.
Error
Specify a value that is equal to or greater than the listed value.
5047
The value of field fieldName cannot be greater than fieldValue.
Error
Specify a value that is equal to or less than the listed value.
5048
Unable to load the primary form formName.
Error
5049
Notify field can only have Integer or Selection.
Error
193

Number
Description
5050
The notification action cannot be saved.
Error
5051
Dynamic values for the sampleForm/sampleServer must contain valid field/keyword

references.
Error
5052
The specified color string is not a valid RGB color.
Error
The color string could not be parsed to a valid RGB color.
5053
Property propertyName of field fieldName is not described in metadata.
Error
The specified property is not defined for the field.
5054
The specified enum value for property propertyname of field fieldName is not a valid value.
Error
The value set for the property does not exist in the list of valid values.
5055
The value specified is not a valid value for the enum property of the field.
Error
The value submitted is not a valid value for the enum property of the field.
5056
The enum value for string cannot be blank.
Error
The value submitted is not a valid value for the enum property of the field.
5057
The dynamic value for {0} has an invalid field or keyword reference: {1}.
Error
5058
Invalid qualification: problemDescription.
Error
5059
Error
Invalid webServiceName : userSpecifiedName. The name must start with an alphabetical character or
_ and can have alphabetical characters, digits, _, ., or - only. Enter a valid name.
5060
Login failed for AR System server serverName. serverName errorMessage.
Error
The connection could not be made to the AR System server, the AR System server is not running,
or the port number is incorrect.
5061
The value for field fieldName cannot be more than number digits.
Error
Specify a value that is equal to or less than the listed number of digits.
5062
Hidden locked object cannot be edited: objectName.
Warning
You tried to modify a hidden object that has a read-only lock, such as by adding a form to a readonly filter. You cannot modify a locked object.
5063
Warning
objectName is locked as read-only. Adding associated forms and modifying permissions (if
applicable) are the only changes allowed. Any other changes will result in an error when the
object is saved.
5064
objectName is locked as read-only. Any changes will result in an error when the object is saved.
Warning
5065
Error
194
The objectType objectName has an open editor. Objects that are currently being edited cannot
be renamed.
AR System messages

Number
Description
5066
Error
Cannot release the reserved objects due to an AR System server error. Open the Reserved
Objects working list to view and release reservations.
5067
Cannot import applicationName because it is reserved by another user.
Error
5068
Error
Cannot add the following forms to the application as they are either not reserved for you or
reserved by other users. Only forms reserved by you can be added to deployable applications.
See the list of forms that follows this message.
5069
Cannot export to a file because creation of directory directoryName failed.
Error
The specified directory cannot be created. This might be due to a file system error or a hardware
problem.
5070
The selected file does not exist or does not contain applications.
Error
Application import failed. The file used to import applications does not contain any applications
or the file does not exist.
5071
The file does not exist or does not contain any object definitions.
Error
In Import Object definition, the def file does not contain any object definitions. The file is
incorrect or corrupted.
5072
Cannot import because all the objects are reserved by other users.
Error
5073
Cannot import because all the forms are reserved by other users.
Error
5074
The file does not contain any view definitions.
Error
The def file specified to import view definitions from does not contain any view definitions. An
incorrect file was specified.
5075
Invalid file. Errors encountered while parsing the file: fileName.
Error
An error occurred parsing the def file with view definitions. The file might be corrupted.
5076
Cannot export to file fileName. The file type must be in either def or xml format.
Error
5077
Cannot export to file. The file type must be arm format.
Error
5078
Unable to export mail template. errorMessage.
Error
An error occurred while the system tried to export mail templates. To continue, 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.
5079
Selected objects cannot be deleted. objectNames.
Error
A server exception occurred when deleting server objects.
5080
Error
All of the selected objects have editors open. Objects that are currently being edited cannot be
deleted.
5081
Some of the objects you want to edit are not reserved by you. Reserve them to edit.
Error
You must reserve all the objects you need to edit.
195

Number
Description
5082
Cannot export to file fileName. The file is read-only. Specify a writable file.
Error
5083
Error
5084
Error
5085
Error
Some of the selected objects have editors open. Objects that are currently being edited cannot
be released.
Some of the selected objects have editors open. Objects that are currently being edited cannot
be reserved.
The following objects could not be reserved: objectNames. Refresh the object list to see if any
of these objects are reserved by others.
The objects might be reserved by another person. Refresh the object list to get a fresh list from the
server and show the reason why the objects cannot be reserved.
5086
Unable to retrieve the object from the AR System server. errorMessage.
Error
5087
Unable to retrieve objectListType lists from serverName. errorMessage.
Error
5088
Unable to retrieve application from serverName. errorMessage.
Error
5089
Unable to populate the list information. errorMessage.
Error
5090
Error
5091
Error
5092
Some of the selected working lists are open. Working lists that are currently being viewed
cannot be deleted.
The selected packing list has an object list open. Packing lists that are currently being viewed
cannot be deleted.
Error
The selected application has an object list open. Applications that are currently being viewed
cannot be deleted.
5093
You must select one primary form for adding new action.
Error
5094
Error
Unable to add new action. There are already 25 actions, which is the maximum number of
allowed actions.
5095
Errors encountered while determining related objects. errorMessage.
Error
5096
No user name entered to log on. Enter a user name.
Error
To log in, specify a user name. You can dismiss this window without changing the login
information for the current user. To change the login information, specify a user name.
5097
No AR System servers selected to log on. Add at least one AR System server name.
Error
196
AR System messages

Number
Description
5098
Error connecting to preference server. serverName.
Error
The record for the user in the AR System User Preference form might contain bad data or be
corrupted.
5099
Error connecting to preference server. AR System User Preference form not found on the
server.
Error
The AR System User Preference form is automatically re-created when you restart the AR System
server.
5100
Error connecting to preference server. The AR System server might be down. errorMessage.
Error
This can occur when the preference server is down or when the network is slow (leading to a timeout). Contact your AR System administrator.
5101
There are no forms included in the application. To define statistics, you must add forms to the
application.
Error
5102
Error
5103
Error
The navigation fields you deleted had associated items. Use the Form > Edit Menu Bar
command to access these orphaned items.
fieldType fieldName reference a field that does not exist. Update the fieldType field to reference
a valid field before you save.
The table column field fieldName refers to a remote field that does not exist. Update the value to a
valid field by creating the missing field, or remove the column field.
5104
The form cannot be saved. {0} {1} has no cell fields. Add a cell field.
Error
5105
The database name will be used as the label.
Error
5106
fieldType Field fieldName has missing layout information. Modify its layout to display it.
Error
5107
Only one reservedFieldType field is allowed per form.
Error
5108
resultsListField field is not allowed in a display-only form.
Error
5109
Save successful with warnings.
Warning
5110
Error
Currency field fieldName has no functional currency values. Add at least one functional
currency value before you save.
5111
dataType Field fieldName has a minimum value equal to the maximum value.
Error
When creating a decimal, integer, real, or currency field, you specified an invalid range of
minimum and maximum values. To continue, create a minimum value that is smaller than the
maximum value.
197

Number
Description
5112
dataType Field fieldName has a minimum value greater than the maximum value.
Error
When creating a decimal, integer, real, or currency field, you specified an invalid range of
minimum and maximum values. To continue, create a minimum value that is larger than the
maximum value.
5113
dataType Field fieldName has a default value less than the minimum value.
Error
When creating a decimal, integer, real, or currency field, you specified an invalid default value.
To continue, create a default value that is within the minimum and maximum range.
5114
dataType Field fieldName has a default value greater than the maximum value.
Error
When creating a decimal field, you specified an invalid default value. To continue, create a default
value that is within the minimum and maximum range.
When creating a decimal, integer, real, or currency field, you specified an invalid default value.
To continue, create a default value that is within the minimum and maximum range.
5115
{0} is linked to a missing field. Link the cell field to a valid field before you save.
Error
5116
panel Field fieldName has a minimum size less than 25. Enter a value that is equal to or
greater than 25.
Error
For a panel field in a panel holder, you specified a minimum size of less than 25. This message
applies only to panel fields in collapsible or splitter holders.
5117
panel Field panelName has a minimum size equal to the maximum size.
Warning
For a panel field in a panel holder, you specified the same value for the minimum and maximum
size properties. This message applies only to panel fields in collapsible or splitter holders.
5118
panel Field panelName has a minimum size greater than the maximum size.
Error
For a panel field in a panel holder, you specified a minimum size greater than the maximum size.
To continue, specify a minimum size that is smaller than the maximum size. This message applies
only to panel fields in collapsible or splitter holders.
5119
panel Field fieldName has an initial size greater than the maximum size. Maximum size has
been increased to equal initial size.
Error
For a panel field in a panel holder, you specified an invalid initial size. To continue, specify an
initial size that is smaller than the maximum size. This message applies only to panel fields in
collapsible or splitter holders.
5120
Error
panel Field panelName has an initial size less than the minimum size. Initial size has been
increased to equal minimum size.
For a panel field in a panel holder, you specified an invalid initial size. To continue, specify an
initial size that is greater than the minimum size. This message applies only to panel fields in
collapsible or splitter holders.
5121
Table field fieldName must have at least one column.
Error
Table fields must have at least one column. For more information about table fields, see the Form
and Application Objects Guide.
5122
Table field fieldName must have at least one cell.
Error
Table fields must have at least one cell. For more information about table fields, see the Form and
5123
The following indexes are empty and will be ignored: indexNames.
Error
198
AR System messages

Number
Description
5124
Unable to add this form to application applicationName.
Error
The application could not be found on the AR System server. It might have been deleted.
5125
This form has Web - Legacy as the default view, which is not supported in this version of
Developer Studio.getInstance(). Switching to another supported view type.
Warning
You tried to open a Web - Legacy (Relative) view, which is not supported in AR System 7.0 and
later. The view is switched to the standard view.
5126
Internal error.
Error
5127
This view cannot be deleted because a form must have at least one view.
Error
5128
Warning
This form contains a non-standard set of distributed fields. Select None, Basic, Full, or
Advanced to return to a standard set of fields.
Your form contains an inconsistent set of distributed fields, possibly because one or more fields
were deleted. Distributed fields are system-generated and cannot be mixed and matched. To recreate a standard set of distributed fields in your form, choose Form > Add Distributed Fields. See
the BMC Remedy Distributed Server Option Guide.
5129
Error
This form contains a distributed field of the wrong datatype. To delete distributed fields, select
None in the Distributed Fields dialog box and click OK.
An incorrect data type is associated with one or more distributed fields.
5130
Cannot export to file fileName. The specified directory does not exist.
Error
5131
Specify an export destination file name.
Error
5132
Cannot export to file fileName. The specified directory contains invalid characters.
Error
The following characters are invalid in directory names:

Windows " \ [ ]
UNIX . " \ [ ] :
5133
Cannot export to file fileName. The specified file name contains invalid characters.
Error
The following characters are invalid in file names:

."/\[]:,
5134
Error
Cannot export to file fileName. The specified file name does not contain the proper extension
of either .DEF or .XML.
5135
Cannot export to file fileName. A file name must be supplied.
Error
5136
Display order cannot be empty or 0.
Error
Internal error. If this error is received, provide a non-zero value.
5137
The start active link is not allowed unless an application display order is also specified.
Error
5138
Start active link activeLinkName does not exist.
Error
The Entry Point Guide has no starting active link. Contact your AR System administrator.
199

Number
Description
5139
At least one field type must be selected for fieldType.
Error
5140
The character menu is empty and cannot be saved.
Error
5141
labelName cannot be empty.
Error
Provide the required value.
5142
labelIndexList cannot have more than 5 labelIndex values defined.
Error
5143
valueIndex cannot be empty.
Error
5144
valueIndex must be greater than 0 and less then a 10 digit number.
Error
5145
Mappings are not in the Mapping table in the Operations panel.
Error
Mappings are not in the Mapping table in the Operations panel.
5146
WSDL expected at least one operation element. Provide at least one operation node.
Error
WSDL expected at least one operation element. Provide at least one operation node.
5147
Unknown error: errorNumber.
Error
An unknown or unexpected error occurred. This message appears when Developer Studio
catches an unknown or unexpected exception. Use the reported error value to help identify the
root cause of the problem.
5148
Unable to locate or load the specified file fileName.
Error
The WSDL file that is being loaded is not valid because it requires mandatory elements and a
specific format.
5149
Form name cannot be found on the AR System server.
Error
An attempt was made to access a form that is not on the AR System server. This might have
occurred because workflow points to a form that no longer exists.
5150
{0} is not in the correct format.
Error
5151
{0} must have a minimum value of number.
Error
5152
{0} can only have a maximum value of number.
Error
5153
Load of model object objectName failed.
Error
Internal error.
5154
mappingName cannot be empty.
Error
Mapping is not in the field mapping table.
5155
mappingName cannot be empty.
Warning
Mapping is not in the field mapping table.
200
AR System messages

Number
Description
5156
item does not contain a valid selection.
Error
You did not enter a valid value for the item in question while working in a Developer Studio
selector dialog box, such as the Field Selector or the View Selector. Select an existing value, or
enter a valid value for the item.
5157
The field ID or field name is invalid. Verify the spelling of the name to make sure you
specified a legal field.
Error
The field ID or field name is invalid. Verify the spelling of the name to make sure you specified a
legal field.
5158
value is not a valid selection for propertyName.
Error
5159
Form does not exist on supplied AR System server serverName.
Error
The server has no form with the specified name. Either the specified name is incorrect, or the form
is on another server.
5160
The menu or a menu item has an empty label and cannot be saved. Supply the required label.
Error
5161
The specified name in executeONCondition is not a valid field name for the current form.
Error
The specified name is not a valid field name for the current form. Verify the spelling of the name
to make sure that you specified a legal field.
5162
You must select a valid option for the selected Execute Options field.
Error
In the Execute Option Panel of the active link, when a field is selected in the field selector, a valid
enabled option must be selected.
5163
The field field in the Execute Option Panel of the active link contains an invalid field selection.
Error
In the Execute Option Panel of the active link, a field selector for Field or Button/Menu Field
contains invalid selection.
5164
Undefined XML mapping item name.
Error
5165
Table fields must have at least one column.
Error
Table fields must have at least one column. For more information about tables, see the Form and
5166
The following fields already exist on the view. viewName.
Error
You tried to add fields to a view that already exists in the form. Any fields already in the view are
unaffected.
5167
Only administrators can edit objectName on serverName.
Error
5168
Only administrators can edit deployable applications on serverName.
Error
5169
A menu parent cannot be added as a child to a horizontal navigation field.
Error
5170
Error
A menu parent cannot be added as a child to a horizontal navigation field. Field: fieldName is
not added.
201

Number
Description
5171
Panel cannot be created without a name. Enter a panel name.
Error
5172
Error
serverName is not a recognized AR System server name. Either the server is down or the AR
System server version is less than 4.0.
5173
All objects are selected, and no additional objects are available for adding to the selection.
Warning
All objects are selected, and no additional objects are available for adding to the selection.
5174
The specified Message Number was greater than the maximum value allowed for this field and
is reset to 2147483647.
Error
5175
Error
5176
Error
5177
Error
The specified Entry Point Application List Display Order is greater than the maximum value
allowed for this field and is reset to 2147483647.
The objectType is reserved by user userName. Your changes cannot be saved. Use Save As to
save a copy of your changes.
objectType cannot be reserved due to error: errorNumber. Use Save As to save a copy of your
changes.
Object reservation failed for this object. Refresh the object list to see whether this object is
reserved.
5178
No groups selected. Select at least one group.
Error
5179
Buttons must have labels. Provide a label.
Error
5180
Buttons must have values. Provide a value.
Error
5181
Unable to Export Custom Button Configuration. errorNumber.
Error
The file is read-only, the file path is invalid, or an error occurred during an attempt to write to the
file.
5182
Unable to export column preferences. errorNumber.
Error
The file is read-only, the file path is invalid, or an error occurred during an attempt to write to the
file.
5183
Select a method to delete.
Error
5184
You can only delete methods.
Error
5185
Error
5186
Error
Connection to server serverName is denied You can connect to only one unlicensed server in a
session.
The selected image cannot be loaded because it could not be accessed, or is corrupted, or is too
large.
The selected image cannot be loaded because it could not be accessed, is corrupted, or is too large.
202
AR System messages

Number
Description
5188
At least one port must be added to this web service. WSDLPortsNumber.
Error
5189
BMC Remedy Developer Studio failed to connect the specified AR System server.
Error
BMC Remedy Developer Studio 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.
5190
Failed to export to the file. errorNumber.
Error
The file is read-only, the file path is invalid, an error occurred during a write-to-file operation, or
an error occurred on the AR System server.
5191
Failed to import objects from file. errorNumber.
Error
The file is read-only, the file path is invalid, an error occurred during a write-to-file operation, or
an error occurred on the AR System server.
5192
AR System server name is empty in a workflow action.
Error
AR System server name is empty in a workflow action, such as a Set Fields or Push Fields action.
5193
AR System Server name serverName is invalid.
Error
A failure occurred during login because you entered an invalid server name.
5194
A connection could not be established to serverName.
Error
A connection could not be established to the selected AR System server in a Set Fields action for
an unknown reason.
5195
serverName is not valid.
Error
5196
propertyName is not in the correct format.
Error
A property is invalid. For example, a string was provided for a numeric value.
5197
propertyName must have a minimum length of minimumSize.
Error
5198
propertyName can only have a maximum length of maximumSize.
Error
5199
Unable to transform propertyName due to an API error errorNumber.
Error
This is an internal error.
5200
string is not a valid qualification.
Error
5201
The label guideLabel is already being used in the guide. The label must be unique.
Error
Labels in guides must be unique. Rename the label, providing a name that has not yet been used
in the guide.
5202
No primary field is defined for form formName.
Error
5203
Specified primary field ID does not exist on the form formName.
Error
Specified primary field ID does not exist on the form.
5204
Unable to locate form formName.
Error
The form does not exist on the AR System server.
203

Number
Description
5205
Unable to locate field fieldName on form formName.
Error
The listed field could not be found on the listed form. It might have been deleted from the form.
5206
The parent form is missing from the web services field map for fieldName.
Error
The parent form is missing from the web services field map for fieldName.
5207
The Change Field menu menuName is empty or invalid.
Error
The Change Field menu is empty or invalid.
5208
Minutes value must be between 059.
Error
5209
Missing hour information. Hours must be specified.
Error
5210
Missing weekday information. A weekday or day in the month must be specified.
Error
5211
The escalation time interval cannot be 0.
Error
The escalation time interval is set to 0.
5212
With the Escalation Time Execution option, Run By = Time, and Time is not entered.
Error
With the Escalation Time Execution option, Run By = Time, and Time is not entered.
5213
The Cross-Reference Action in the Notify filter must have a reference field specified.
Error
When creating a Notify filter action, you did not select the reference field required when the
notification Mechanism is Cross-Reference. To continue, select a reference field.
5214
The Selected Fields option must have a field specified.
Error
5215
SQL Set Fields action must have a SQL command specified.
Error
To save a SQL Set Fields action, specify a SQL command. This is not validated but cannot be left
5216
Unable to convert the operations XML document.
Error
5217
Unable to convert the input mapping XML document.
Error
The mapping XML might be corrupted.
5218
Unable to convert the output mapping XML document.
Error
The mapping XML might be corrupted.
5219
Unable to parse the XML document. errorNumber.
Error
5220
Workflow must have at least one IF action.
Error
No If actions are defined for the filter, escalation, or active link. Specify at least one If action.
5221
fieldType Field fieldName has a minimum width greater than the maximum width.
Error
A composite field embedded in another composite field with the Fill layout has a Minimum
Width and a Maximum Width property. The Minimum Width value should not be greater than
the Maximum Width value. Specify a minimum width that is less than or equal to the maximum
width.
204
AR System messages

Number
Description
5222
fieldType Field fieldName has a minimum height greater than the maximum height.
Error
A composite field embedded in another composite field with the Fill layout has a Minimum
Height and a Maximum Height property. The Minimum Height value should not be greater than
the Maximum Height value. Specify a minimum height that is less than or equal to the maximum
height.
5223
BMC Remedy Action Request System is ready for use or evaluation without purchasing or
activating an authorization key. For unlimited capabilities, contact your sales representative or
visit www.bmc.com. Server: serverName.
Note
maximum of one server. To obtain a version of AR System without these limitations, contact your
BMC sales representative or an authorized reseller, or visit http://www.bmc.com.
5224
Forms cannot be moved from serverNameA to serverNameB.
Error
An attempt was made to drag a form from AR System server A to an application on AR System
server B. This is not allowed.
5225
Form already exists on applicationName application.
Error
5226
The field type fieldType of Field fieldName does not match the field type of the base field.
Error
A table column field is mapped to a remote field of a different type. For example, a column field
with a type of char is using a remote button field.
5227
Creating field is not allowed in Tab Order Increment on Click mode.
Error
5228
fieldType fieldType contains an invalid form name. Provide a correct remote form name.
Error
The remote form name is empty, or the specified form does not exists on the AR System server.
5229
fieldType fieldName is linked to an unreachable AR System server serverName.
Error
A network connection cannot be established to the AR System server. For troubleshooting steps,
see error message 90.
5230
Selecting the override loop option could cause an infinite loop in the system.
Warning
By shutting down loop protection, you run the risk of creating infinite loops and overwriting the
original record in a distributed transfer operation or a distributed return operation. Save the filter
or escalation only if you are understand the risk in what you are doing.
5231
filePath does not exist. The Log to File action will create the file.
Warning
5232
Z order for fieldType field fieldName has been modified to fix duplicate Z order.
Warning
5233
Core fields: fieldNames can not be deleted.
Error
5234
You cannot move a panel to its current parent.
Error
5235
Data fields cannot be added to audit forms.
Error
205

Number
Description
5236
Warning
Z order for fieldType field fieldName has been modified to make it consecutive with other
fields.
5237
{0} with this name {1} already exists. Choose a new name.
Error
5238
target field fieldName cannot be empty.
Error
Set Field actions and Service action assignments need an assignment value for each field added in
mapping.
5239
Port not defined for operation: operationName.
Error
WSDL operation in a web service is missing a port.
5240
Operation names must be unique. There is a duplicate operation: operationName in the

Operations List.
Error
You created a duplicate operation name in the Operations List. Operation names must be unique.
5241
Error
Invalid operation name operationName conflicts with output top level parent name for
operation: operationName.
Internal operations are saved with the suffix Response. Therefore, avoid using Response as a
suffix in the name of an operation. For example, this error occurs if an operation named
WSDLNameResponse is used when an operation named WSDLName already exists.
5242
Label label cannot be empty. Specify a label name.
Error
5243
Duplicate file names were found in the current directory. The duplicate files were not added.
Error
The file name being added already exists in the current directory.
5244
Vendor form table tableName does not have any available columns.
Error
5245
The web service Publishing Location must end with the web service name.
Error
The web service location must end with the web service name.
5246
The web service Publishing Location must be a non-empty string.
Error
The web service location must be a non-empty string.
5247
Invalid Web Services Publishing Location has been updated with correct name.
Note
5248
Error
5249
Error
Following Column fields for tableFieldType tableFieldName do not have referenced fields
columnFieldNames on the current form. Press OK to delete.
The view viewName specified in the active link activeLinkName does not exist on Form
formName.
When you created an Open Window action, the form view that you selected was not found on the
AR System server. Accordingly, the view used in the action is the default administrator view. To
verify that the view you want to use exists, open the form in BMC Remedy Developer Studio.
5250
Error
206
Exporting flashboard objects in XML is not supported. Selected flashboard objects will not be
exported.
AR System messages

Number
Description
5251
Your changes cannot be saved because objectName is reserved by user userName.
Error
5252
Unable to display image. It does not appear to be a supported image format.
Error
The image cannot be displayed. Valid file types for images are BMP, DIB, GIF, JPEG, JPG, and
PNG.
5253
Unable to display background image. It does not appear to be a supported image format.
Error
The background image cannot be displayed. Valid file types for images are BMP, DIB, GIF, JPEG,
JPG, and PNG.
5254
Changing the form might make existing actions invalid. Check existing actions.
Warning
When modifying an active link or filter, you changed which form controls the active link or filter.
Active links and filters can be attached to multiple forms. Verify your actions after you change the
form in an active link or filter.
5255
Cannot add a submenu because a menu in a character menu cannot have more than 99
submenus.
Error
The character menu definition contains too many items on one level of the menu tree. AR System
allows a maximum of 99 items on a menu level. Use multilevel menus to split large menus into
multiple smaller and more manageable menus.
5256
No allowable currency type has been specified. All currency types are now allowed.
Note
5257
Error
Cannot connect to server: serverName because its version is version. Only servers that are 7.0 or
later versions are supported.
5258
Search was aborted by the user. The results list might not be complete.
Warning
5259
Search did not match any objects.
Warning
When the system searched for an object, no results were returned. Objects might have been
deleted, or their names might have been modified. Deleted objects do not appear even if the
database is not synchronized.
5260
Error
Web Services Publishing location contains public within the URL, but permissions have not
been set to public for webServiceName.
5261
A panel or a page cannot be moved to its child page holder.
Error
A panel or a page cannot be moved to its child page holder.
5262
Error connecting to BMC Atrium Orchestrator server. Reason: errorNumber.
Error
5263
Closing current editor due to resource error. errorNumber.
Error
This is an internal error.
5264
You cannot add a method here. The type is incompatible.
Error
IDispatch, VARIANT, or Compatible. If it is not one of these types, this error is returned.
5265
A valid Web Services Port has not been selected.
Error
Select a valid web services port.
207

Number
Description
5266
A valid Web Services Operation has not been selected.
Error
Select a valid web services operation.
5267
A valid Operation has not been selected.
Error
Select a valid operation.
5268
A valid Configuration Name has not been selected.
Error
Select a valid configuration name.
5269
A valid Process has not been selected.
Error
Select a valid process name.
5270
A valid Web Services File has not been selected.
Error
Select a valid web services file.
5271
Column columnName used by Field fieldName is already referenced by another field.
Error
In the View form, columnName in the Column property of fieldName is already used in another
field. Use another available columnName.
5272
Unable to add an active link without primary form. Select a primary form.
Error
5273
Layout style for panel panelLabel is changed from XY to Fill.
Warning
5274
An integer field is needed on the primary form for this operation.
Error
An Execution Order From Field Value option cannot be used in a Goto action if the primary form
does not have an integer field. Add an integer field to the primary form.
5275
The configuration name name does not exist in the AR System Orchestrator Configuration
form.
Error
The entry might have been deleted from the form.

5276
Error
fieldType Field fieldName cannot refer to Column databaseColumnName of type

databaseColumnType.
The fieldType must match the databaseColumnType.
5277
The named menu menuName referenced by fieldName is not found.
Error
The menu might have been deleted.
5278
Output Mapping to a static value is not allowed for mapping item value.
Error
5279
Errors were encountered while accessing the file: fileName.
Error
5280
Error
Cannot create new object because application applicationName is reserved by another user
user.
Object reservation is in use on the server, and you tried to create an object in an application
reserved by another user. Wait until the reserved application is released. Alternatively, create the
object outside the application by using the All Objects node in the AR System Navigator. Add the
object to the application when the application is no longer reserved.
5281
You cannot create an Attachment Pool field in a view form.
Error
You cannot create an Attachment Pool field in a view form.
208
AR System messages

Number
Description
5282
Filter cannot be added without a primary form. Select one primary form.
Error
5283
Error
5284
Error
5285
Some Columns do not have matching Data Field in the Form: formName. They will be deleted.
Press OK to delete.
The file fileName has an unsupported file extension. The supported extensions are .ARX, .CSV,
.REP or .XML.
Error
Number of selection values listed in this dialog box does not match the number of selection
values in field ID fieldID on form ID formID. Make sure the number of images and alternative
texts correspond to the correct selection values.
5286
Image imageName is missing from the server. Select a different image in column columnName.
Error
5287
Error
5288
Image imageName in column columnName exceeds the maximum recommended size (32 x 32
pixels).
Error
Images in column columnName are different sizes. To make the table more readable, select
images that are the same size.
5289
Please enter a valid Label Name.
Error
5290
Error
5291
The field fieldName referred in Table Field fieldName cannot be found on the base form
formName. Save this form to fix this issue.
Error
No Mid Tier information is provided for AR System server : serverName. Enter Mid Tier
Information in the Preferences.
5292
Error displaying preview for form : formName.
Error
5293
Right-aligned field has negative X value: fieldName.
Error
When the Layout Style property of a form or panel is set to XY and a fields Alignment property
is set to Right, the fields X property, which specifies the number of pixels between the field and
the right side of the form or panel, must be a positive integer.
5294
Cannot create label labelName.
Error
5295
Cannot edit label labelName.
Error
5296
Warning
Label labelName created successfully. number objects labeled. Any objects that do not have a
baseline were not labeled.
If an object does not have at least one entry (a baseline) in the AR System Version Control:
Object Modification Log form, AR System cannot add a version control label to it. To add an entry
for an object to that form, enable the object modification log and then create, modify, delete, or
import the object. For more information, see Form and Application Objects Guide, Chapter 2, Using
version control.
209

Number
Description
5297
Error in retrieving objects for label labelName.
Error
5298
Because fieldName Field fieldID uses the advanced rich text property, the field must contain at
least 10 rows.
Error
5299
Error
Because fieldName Field fieldID uses the advanced rich text property, the field must have at
least 500 pt width.
5300
Label name cannot be blank.
Warning
The item has both a label name and a label description. You specified the label description, but
you did not specify the label name. If you specify the description, also specify the name.
5301
Task name cannot be blank.
Error
5302
File name already exists. Choose a new name.
Error
5303
Error
No definition (.def) files for the specified objects are attached to the object modification log. In
the Version Control tab on the AR System Administration: Server Information form, verify
that the Save Definition Files option is selected.
5304
There are no Attachment Pool Fields available for selection. Create a new one.
Error
5305
Attachment pool field fieldName for the Rich Text field fieldName was deleted.
Error
5306
Attachment pool field fieldName for the Rich Text field fieldName should not be visible.
Error
5307
Objects exported successfully.
Note
5308
The object is not reserved or is reserved by another user. Save As with same name is not
allowed.
Error
5309
Warning
Group having ID: groupID does not exist on the server. This group has been removed from the
permission list.
5310
Application applicationName, specified for Integration Workflow property, does not exists.
Error
5311
Z order for fieldName field fieldID has been modified to set it within acceptable limits.
Note
5312
nameOfOperation operation not allowed on specified object. reasonOperationIsNotAllowed.
Error
The change that you tried to perform is not permitted in Best Practice Customization mode
because it might not be preserved if the application is upgraded.
5317
Error
210
AR System messages

Number
Description
5318
Fields on View nameOfView has invalid Z order. Overlay of View required to modify it.
Error
When a form is opened in BMC Remedy Developer Studio, corrupt display properties (such as
incorrect Z-order, missing menus, and missing labels) are typically fixed. In Best Practice
Customization mode, however, such errors in nonoverlay form views are not fixed.
Instead, you must create an overlay of the form view that contains the invalid Z-order and then
fix the Z-order in that overlay.
5319
Field nameOfField has missing layout information. Overlay of View required to modify it.
Error
Instead, you must create an overlay of the form view that contains the specified field and then add
the missing information to that overlay.
5321
View nameOfView has no label. Overlay of View required to modify it.
Error
Instead, you must create an overlay of the form view whose label is missing and then add a label
to that overlay.
5322
Error
Can not use Form nameOfForm as remote form because it does not contain fields referred by
columns or cell fields in the overlaid form.
In an overlay of a list view, tree view, or cell-based table field, you cannot remove the columns or
fields in a cell that exist in the overlaid form, but you can add columns or cell fields. The new
columns or cell fields do not have to come from the same form that the columns or cell fields in
the overlaid table came from (that is, you can specify a new remote form in the Tree/Table
Property or Remote/Local Fields dialog box). But the new remote form must contain fields whose
IDs match the field IDs of all the existing columns or cell fields in the overlaid table.
The new remote form that you specified does not contain fields whose IDs match the field IDs of
all the existing columns or cell fields in the overlaid table. Specify a remote form that does contain
the required IDs.
5323
Error
Creating new object is not allowed in Best Practice Customization Mode since AR System
Server version is less than 7.6.04. Please use Base Development Mode to create new objects.
To create objects in Best Practice Customization mode, you must first install AR System server
7.6.04 or later.
To create objects in your current system, switch to Base Development mode.
Note: Base Development mode gives you unrestricted access to create, modify, and delete
AR System origin objects, such as out-of-the-box application objects, but your changes might
not survive upgrades.
5324
Error
Creating objectType is not allowed in Best Practice Customization Mode. Please use Full
Development Mode to create new objectType.
You cannot create the specified type of object in Best Practice Customization mode. To create that
type of object, you must switch to Base Development mode.
Note: Base Development mode gives you unrestricted access to create, modify, and delete
AR System origin objects, such as out-of-the-box application objects, but your changes might
not survive upgrades.
211

Number
Description
5327
Only custom fields can be added from a base form to an Overlay join form.
Error
You cannot add an origin field from a primary or secondary form to an overlay join form. You can
add only custom fields from the primary or secondary form to the overlay join form.
To create custom fields on the primary and secondary forms, you must create an overlay of those
forms in Best Practice Customization mode and then add the custom fields to the overlay.
5328
Error
The objectType objectName has an open editor. Overlay cannot be created for objects that are
currently opened in editor.
AR System does not allow you to create an overlay of an object that is open in the editor.
Close the relevant editor (save your changes if necessary) and then create the overlay.
5375
The duration for keeping data for a Flashboard variable before it expires must be an Integer.
Error
The expiry schedule for collecting data in a Flashboards variable when one of the expiry options
is chosen was incompletely specified. The amount to keep data before it expires must be an
Integer.
5376
Pie charts cannot be selected for History or Summary display type.
Error
5377
Group access is not defined -- only an administrator has access to this flashboard.
Error
5378
Group access is not defined -- only an administrator has access to this variable.
Error
5379
The threshold value must be greater than zero.
Error
Specify a value that is greater than zero for the threshold value.
5380
The threshold value must be a non-negative integer.
Error
Specify a non-negative integer for the threshold value.
5381
Specified alarm variable does not exist on the AR System for the alarm to monitor.
Error
Specify a variable that exists on the AR System server for the alarm to monitor.
5382
Specified alarm name does not exist on the AR System for the alarm to monitor.
Error
Specify an alarm name that exists on the AR System server.
5384
The alarm cannot be saved. Correct the following errors.
Error
See the following messages for the errors to correct.
5385
The alarm variable was not specified, or the specified variable name is invalid.
Error
Specify a variable that exists on the AR System server for the alarm to monitor.
5389
The specified alarm trigger cannot be found.
Error
Specify a trigger that exists on the AR System server for the alarm.
5390
A user and a message must be specified for the alarm notification.
Error
Specify a user and a message for the alarm notification.
5391
Variable variableName does not exist. It will be removed from Variables in next save.
Error
212
AR System messages

Number
Description
BMC Remedy Data Import messages

5400
Note
This version of BMC Remedy Action Request System is ready for use or evaluation without
purchasing or activating an authorization key. For unlimited capabilities, contact your sales
representative or visit www.bmc.com. Server: serverName.
maximum of one server. To obtain a version of AR System without these limitations, contact your
BMC sales representative, an authorized reseller, or visit http://www.bmc.com.
5401
Login failed for server serverName. error.
Error
This can occur when the AR System server is down or when the network is slow (leading to a timeout). Contact your AR System administrator.
5402
User name is required for login.
Error
You must enter a user name.
5403
No servers are selected to login. Select at least one server name.
Error
A server must be selected when logging in.
5404
Error connecting to preference server. serverName.
Error
The record for the user in the AR System User Preference form might contain bad data or be
corrupted.
5405
Error connecting to preference server. AR System User Preference form not found on the
server.
Error
The AR System User Preference form is automatically re-created when you restart the AR System
server.
5406
Error connecting to preference server. Server may be down. serverName.
Error
This can occur when the preference server is down or when the network is slow (leading to a timeout). Contact your AR System administrator.
5407
Form is not selected. Select a form.
Error
5408
Data file is not selected. Select a data file.
Error
You must select a data file.
5409
The fieldName fields length exceeded number characters.
Error
Specify a field length within the listed number of characters.
5410
Saving to .arm file is not supported. Use Save As and save file fileName to .armx file format.
Error
5411
Import failed.
Error
The import file cannot be accessed or the AR System server might be down.
5412
No mappings found to import. Create a mapping before doing the import.
Error
5413
Source form name is empty. Select a valid source data file.
Error
You must select a source data file.
5414
Target form is not selected. Select a target form name.
Error
You must select a target form name.
213

Number
Description
5415
Switching target form will clear all the existing mappings.
Warning
5416
No field is selected. Select a field.
Error
You must select a field.
5417
No fallback value is entered. Enter a value or select a keyword.
Error
You must enter a value or select a keyword.
5418
No mapping value was entered. Enter a value or select a field or a keyword.
Error
You must enter a value or select a field or a keyword.
5419
The specified file is not found. Reason: reason.
Error
5420
The specified file has unsupported encoding and cannot be read. Reason: reason.
Error
5421
Import engine encountered an error. Reason: reason.
Error
5422
The specified file cannot be read. Reason: reason.
Error
5423
The specified file cannot be parsed. Reason: reason.
Error
5424
The Mapping editor cannot be loaded.
Error
5425
Cannot save to the specified file. fileName.
Error
Saving the file failed, possibly because the file could not be accessed or a write to the file failed.
5426
Import failed. Reason: reason.
Error
5427
Error
This capability is only supported on AR System server version 7.0 or later. The current AR
System server version is version.

5525
Unknown error: exception.
Error
This error is reserved for a case where search cannot determine what went wrong.
5526
Empty search text. Please enter text in Search Text.
Error
5527
Invalid locations specified.
Error
5528
Error
5529
Error
214
Invalid search locations specified. For every selected object type, at least one location must be
selected.
Invalid field ID specified. If Treat as Field ID is selected, a numeric value must be entered in
Search Text.
AR System messages

Number
Description
5530
Treat as Field ID is selected, but none of the selected locations match any fields.
Error
5531
Error
5532
Error
The following locations string cannot be matched exactly or at the beginning: locationNames.
They will be matched with Match Anywhere in the Target Text option.
The search cannot be performed on the selected AR System server because the Record Object
Relationships setting is not enabled.
The search cannot be performed on the selected AR System server because the Record Object
Relationships setting is not enabled. To enable this setting, open the AR System Administration:
Server Information form, click the Configuration tab, select the Record Object Relationships
option, and restart the AR System server. After the server restarts, retry the search.
5533
Warning
5534
Error
Searching for a string in all locations is a time consuming task. Select this option only when
you are sure that the entered search text will not match many objects.
No objects were selected. If Only in Selected Objects is chosen then at least one object must be
selected.
This error occurs when Selected Objects is chosen as the search scope, but no objects have been
selected on which to perform the search. To resolve this error, use the Choose button to select at
least one object.
5535
Another search is already running in background. Only one search can be performed at a time.
Error
This error occurs when an attempt is made to search again when a previous search is still running
in the background.
5536
Error
No match found for this string constant in the selected locations. Your current setting is "Match
only String Constants".
5537
A working list with same name already exists. Please choose some other name.
Error
5538
Working List Name is empty. Please specify a name for the Working List.
Error
5539
Error
Label search cannot be performed on {0}. The server is not configured to support version
control labels.
5540
Task search cannot be performed on {0}. The server is not configured to support tasks.
Error
5541
Label search cannot be performed on {0}. The server does not support version control labels.
Error
5542
Error
Search cannot be performed on {0}. Modified Date format should be MM/dd/yyyy hh:mm:ss
aaa. Example: 06/25/2000 01:35:02 PM.
5543
No object types were selected in Search In. Please select at least one object type.
Error
5544
Error
No match was found for the specified keywords. The current setting is "Match Only
Keywords".
215

Number
Description
5545
Specified Search Text cannot be found at locationName: {1}.
Error
5546
Error
Some of the selected locations are not supported on server serverName. They will be removed
from Only these Locations.
5547
{0} must have a value of either Enable or Disable.
Error
5548
No Menu Type was specified for Menu. At least one Menu Type must be selected.
Error
5550
Analysis completed successfully.
Note
5551
Related Objects cannot be added. Record Object Relationships configuration is not set.
Error
Select the Record Object Relationships option on the Configuration tab of the AR System
Administration: Server Information form. For more information, see the Configuration Guide.
5575
Unknown error: {0}.
Error
5576
Error loading Event Navigator View. Form formName does not exist on server serverName.
Error
5577
Record Object Relationships is not enabled.
Error
5578
Error
Event Navigator View is currently loading events of form {0}. Only one form can be loaded at
a time.
5579
Operation was aborted by user!
Error
5580
Some objects were modified while initializing!
Error
5600
Store is not connected to serverName.
Error
5601
Unable to update item itemName in L10nItemStore.
Error
5602
Undefined location type: locationType.
Error
5603
Undefined translation state: translationState.
Error
5604
Error parsing definition file.
Error
5605
Unsupported target locale: targetLocale.
Error
216
AR System messages

Number
Description
5606
Error creating homograph for: {0}.
Error
5607
Error fetching definitions from root folder folderName.
Error
5608
Error saving {0} to file fileName. Error while writing to file.
Error
5610
Unable to update location for item itemName.
Error
5611
Location locationName was not found in item itemName.
Error
5612
Invalid definition location. locationName.
Error
5613
Invalid database location. locationName.
Error
5614
Error deleting {0}. Access was denied.
Error
5615
Duplicate package name: packageName.
Error
5617
Form formName was skipped as it is ineligible for data localization.
Warning
Configure the form so that its data can be localized. See the Localizing Your BMC Remedy Action
Request System Applications white paper.
5618
Field fieldID on form formName was skipped as the length of translation exceeds the field +
limit.
Warning
Increase the fields length on the form. Length of the translation string exceeds the field length
defined in the form by the user. See the Localizing Your BMC Remedy Action Request System
Applications white paper.
5625
L10N UI Preferences|Empty value specified. Please select an existing directory.
Error
The Root Folder field in the Preferences window is empty. Enter a valid directory path. See the
Localizing Your BMC Remedy Action Request System Applications white paper.
5626
L10N UI Preferences|Invalid value specified. Please select an existing directory.
Error
The Root Folder field in the Preferences window contains an invalid directory path. Enter a valid
directory path. See the Localizing Your BMC Remedy Action Request System Applications white
paper.
5627
L10N UI Preferences|You do not have read access to the specified directory.
Error
You do not have read access to the directory path entered in the Root Folder field in the
Preferences window. Enter a path to which you have read and write access. See the Localizing Your
BMC Remedy Action Request System Applications white paper.
5628
L10N UI Preferences|You do not have write access to the specified directory.
Error
You do not have write access to the directory path entered in the Root Folder field in the
Preferences window. Enter a path to which you have write access. See the Localizing Your BMC
Remedy Action Request System Applications white paper.
217

Number
Description
5629
Packages cannot be created or deleted while the localization process is running.
Error
You cannot create or delete packages while the localization process is running. Wait until the
process is completed. See the Localizing Your BMC Remedy Action Request System Applications white
paper.
5630
Invalid package name.
Error
5631
At least one deployable application or one form must be specified for localization.
Error
You must select an application or form while defining a package definition. See the Form and
Application Objects Guide, Using the localization toolkit to localize your applications, page 601.
5632
Invalid deployable applications list.
Error
The applications defined in the localization definition package no longer exist on the AR System
server. Remove those applications from the list. See the Form and Application Objects Guide, Using
the localization toolkit to localize your applications, page 601.
5633
Only deployable applications will be localized.
Error
Applications that were selected for the localization package definition are not deployable.
Remove those applications from the list. See the Form and Application Objects Guide, Using the
localization toolkit to localize your applications, page 601.
5634
Invalid independent forms list.
Error
Forms that were selected for the localization package definition are not independent. Remove
those forms from the list. See the Form and Application Objects Guide, Using the localization toolkit
to localize your applications, page 601.
5635
Invalid locales.
Error
No locales were entered in the Locales field for the localization package definition. Enter at least
one locale. See the Form and Application Objects Guide, Using the localization toolkit to localize
your applications, page 601.
5636
Error opening definition. See error log for more details.
Error
This is a runtime exception. See the error log. For more information, see the Form and Application
Objects Guide, Using the localization toolkit to localize your applications, page 601.
5637
Root Folder preference value cannot be changed when a Package Definition is being edited.
Error
See the Form and Application Objects Guide, Using the localization toolkit to localize your
applications, page 601.
5638
Invalid view id range values.
Error
Enter a valid ID range in the Start and End fields under the View ID Range section of the
localization package definition. See the Form and Application Objects Guide, Using the localization
toolkit to localize your applications, page 601.
5639
All of the selected package definitions have editors open. Package definitions that are
currently being edited cannot be deleted.
Error
You cannot delete a package definition when its editor is open. See the Form and Application Objects
Guide, Using the localization toolkit to localize your applications, page 601.
5640
Delete completed with some warnings.
Error
See the Form and Application Objects Guide, Using the localization toolkit to localize your
applications, page 601.
218
AR System messages

Number
Description
5641
Invalid XLIFF (.xlf) file.
Error
When you export or import strings, you must enter a valid .xlf file. See the Form and Application
Objects Guide, Using the localization toolkit to localize your applications, page 601.
5642
The selected AR System server must be set up so that the localization toolkit can use it. Click
the Set Up Database button.
Error
For information about setting up a database other than the default SQLite database, see the Form
and Application Objects Guide, Using the localization toolkit to localize your applications,
page 601.
Errors for any AR System client, including BMC Remedy User, BMC Remedy Developer Studio, BMC Remedy
Email Engine, and web tools
No messages exist in the 60006999 range.
BMC Remedy Administrator errors and warnings (release 7.1.00 and earlier only)
7001
Error
Invalid mapping because of incompatible data types. AR Datatype - Integer can only be
mapped to XML Datatype - int, boolean, short, byte, unsigned Int, unsigned Short, or unsigned
Byte.
7002
Error
Invalid mapping because of incompatible data types. AR Datatype - Decimal can only be
mapped to XML Datatype - decimal, long, or unsigned Long.
7003
Error
Invalid mapping because of incompatible data types. AR Datatype - View or Display can only
be mapped to XML Datatype - string.
7004
Error
Invalid mapping because of incompatible data types. AR Datatype - DateTime can only be
mapped to XML Datatype - dateTime.
7005
Error
Invalid mapping because of incompatible data types. AR Datatype - Date can only be mapped
to XML Datatype - date, gYearMonth, gYear, gMonthDay, gDay, or gMonth.
7006
Error
Invalid mapping because of incompatible data types. AR Datatype - TimeOfDay can only be
mapped to XML Datatype - time.
7007
Error
Invalid mapping because of incompatible data types. AR Datatype - Real can only be mapped
to XML Datatype - double or float.
7008
Error
Invalid mapping because of incompatible data types. AR Datatype - Diary can only be mapped
to XML Datatype - string.
7009
Error
Invalid mapping because of incompatible data types. AR Datatype - Enum can only be mapped
to XML Datatype - string.
7010
Error
Invalid mapping because of incompatible data types. AR Datatype - Attachment can only be
mapped to XML Datatype - hexBinary or base64Binary.
219

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

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

Number
Description
7055
Licensing an application is not a reversible process. Do you wish to continue?
Warning
This is a warning that after an application is licensed, the license cannot be made less restrictive.
7056
Can not delete an application which is open in an Application Window.
Error
To delete the application, first close the application window.
7058
This is an archive form. Are you sure you want to delete it?
Warning
This warning appears because deleting an archive form deletes the data on the form, which might
be needed as a backup copy of data on the source form.
7059
Some forms had archive forms associated with them. These archive forms have been
automatically licensed.
Warning
This informational messages explains that if you license a form, any associated archive form is
automatically licensed.
7060
Unable to Save/Update Form due to an HTML processing error: systemErrorCode.
Error
An internal error occurred during HTML processing, which probably indicates that the system is
low on resources. Restart the computer running AR System.
7061
Unable to Import web page due to an HTML processing error: systemErrorCode.
Error
7062
Unable to merge template due to an HTML processing error: systemErrorCode.
Error
7064
Please provide valid target directory for the following object type(s): objectType.
Error
A target directory is required for all object types when the BMC Remedy integration with IBM
ClearCase is used.
7065
Form does not have Web Alias. This may result in invalid .jsp file names after deployment. Do
you wish to continue saving?
Error
7069
Error
Since you retrieved this object from the server, it has been modified by userName. Do you want
to overwrite userNames changes with your changes?
This prompt appears when you try to modify an object that someone else is currently modifying.
7070
Can not add Menu types to Horizontal Navigation fields.
Error
You tried to add menu types to horizontal navigation fields.
7071
Please enter a non-empty string in NULL Values field.
Error
You tried to enter an empty string in the field. Enter a value.
7072
The default view of this form is Web - Legacy (Relative), which is not supported in version 7.0.
To view this form in version 7.0, open it in a previous version of Remedy Administrator. Then,
change the default view to Standard.
Error
The error occurs when you try to open a Web - Legacy (Relative) view, which is not supported in
AR System 7.0 and later.
7076
The specified application does not exist: applicationName.
Error
The error occurs when you try to open an application that was deleted after you logged in. For
example, another administrator might have logged in and deleted the application.
222
AR System messages

Number
Description
7077
Please enter Qualification query for this search.
Error
When you create a defined search (in the View Properties dialog box), enter a qualification for the
search.
7078
0 is not a valid value for statistics logging interval.
Error
You entered 0 as the statistics logging interval. Enter a number greater than 0.
7079
Tables may not be audited. Their audit status will not be changed.
Warning
If you change a table fields properties in the Multiple Field Properties dialog box, this warning
appears when you click OK to close the dialog box.
7080
Please enter a Name for this search.
Error
Enter a name for the administrator-defined search you are trying to save.
7081
Trailing spaces are not allowed in the form name. The trailing spaces will be trimmed.
Warning
You entered a form name when performing a Save or Save As operation, and the name has trailing
spaces.
7082
You must designate another field as key field before saving.
Warning
You deleted the key field in a vendor form, and you confirmed that deleting the key field was the
action you wanted to take.
7083
Audit Log Key key is already in use.
Warning
7084
The sub-administrator cannot create deployable applications.
Error
You tried to create a deployable application, but you are not an administrator with full access.
7085
The next request ID block size must be between 1 and 1000. Please enter a new size.
Error
You entered an incorrect number in the Next Request ID Block Size field in the Basic/Entry tab of
the Form Properties window.
7107
If you are working with a Unicode server, only the current view is modified and saved. Click
Display to display the view, and click Save to save your changes.
Error
7117
Error
The current view has been modified. Contents will be lost if you switch the view without
saving. Do you wish to continue? Click yes to continue to switch and click No to remain in
view.
AR System server messages

8000
The error handler cannot be found on this server.
Error
The specified error handler does not exist in the AR System database. You attempted an operation
against the wrong server, or no workflow object is defined by that name. Change to the correct
server, or specify the proper name.
8001
The error handler name cannot exceed 254 characters.
Error
The name of an error handler is limited to 254 characters.
8002
Filter error handlers exceeded the maximum number of levels.
Error
223

Number
Description
8003
Could not locate error handler in schema workflow list.
Error
For an error handler to function, it must be associated with the same schemas as the parent
workflow object. The parent workflow object is the workflow that has been designed to invoke an
error handler when an error occurs. 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.
8004
An error handler cannot use itself as its own error handler.
Error
To avoid recursive operations, a workflow object must not refer to itself as its own error handler.
8005
The context for the called filter is missing.
Error
Internal AR System server error. Contact Customer Support.
8029
One or more entries matched filter conditions your current setting considered any match as
an error.
Error
The Any Match for a Push Fields filter action is defined as Error.
8031
Some of the fields and/or workflow in this form are not supported in this version of the client.
Warning
When a list of field definitions for a form was retrieved, a failure filtering certain field IDs (for
example, attachment fields) into the destination structure occurred. The copy operation failed
because of problems with permissions.
8032
An owned container cannot have a list of subadministrator groups. The list is disregarded.
Warning
An owned container cannot have a list of subadministrator groups. The list is disregarded.
8033
Floating License Timeout change will only take effect after server restart.
Warning
The number of hours for the Write Floating License Timeout was changed in the Timeouts tab of
the Server Info window. These server configuration settings do not go into effect until the server
is stopped and restarted.
8034
Full Text floating license timeout change will only take effect after server restart.
Warning
The number of hours for the Full Text Search Floating License Timeout was changed in the
Timeouts tab of the Server Info window. These server configuration settings do not go into effect
until the server is stopped and restarted.
8035
Referenced character menu cannot be found.
Warning
The character menu listed in the message is referenced in a container, but no longer exists. Create
the character menu or remove the reference from the container.
8036
The system cannot recognize some characters. Unrecognized characters are ignored.
Warning
The server parsed the data you specified, but at least one additional character could not be
interpreted. Extraneous characters are ignored.
8037
Index length longer than 255 bytes may not work on all databases.
Warning
The operation proceeds. However, some database products do not support indexes exceeding 255
bytes in length. For more information, consult your database product documentation.
8038
Request to not fire filter workflow on merge was ignored because user is not an administrator.
Warning
224
AR System messages

Number
Description
8201
The RPC socket number specified is not one of the legal values (0, 390600, 390621 - 390634,
390636 - 390669, 390680 - 390694).
Error
When connecting the client to AR System server, you set the RPC socket number to a value outside
the legal range. The legal ranges of values are:
0
390600
390621 to 390634
390636 to 390669
390680 to 390694
8202
The RPC port specified is not one of the legal values (0, 1 - 65535).
Error
When connecting the client to AR System server, you set the TCP/IP port to a value outside the
legal range. The legal range of values are 0 and 1 to 65535.
8203
The servers RPC version is not supported.
Error
An error occurred during an attempt to create an RPC connection because this version of the
AR System server is no longer supported. To continue, upgrade to a later version of AR System.
8204
RPC control failed to set non-blocking I/O mode. Continuing in blocked I/O mode.
Warning
The RPC-Non-Blocking-IO parameter was set in the AR System configuration file, but the
AR System server continues in blocking mode. For more information, see the Configuration Guide.
8205
Port is busy -- check with netstat to view ports in use.
Warning
This message appears when a server is started on a port that is in use.
8301
The Server Version Control Reservation fields can only exist on one form.
Error
8302
Error
The data entered is invalid. The Server Version Control Reservation mode can only be 0 for
disabled mode or 10 for enabled mode.
Specify a value of 0 or 10. Verify the Object Reservation option on the Version Control tab of the
AR System Administration: Server Information form.
8303
The requested object is reserved by another user.
Error
8304
The operation failed because another user has reserved the form.
Error
8305
The operation failed because another user has reserved the filter.
Error
8306
The operation failed because another user has reserved the active link.
Error
8307
The operation failed because another user has reserved the character menu.
Error
8308
The operation failed because another user has reserved the escalation.
Error
8309
The operation failed because another user has reserved the container.
Error
225

Number
Description
8310
The operation failed because another user has reserved the application.
Error
8311
The operation failed because another user has reserved the image.
Error
8312
The operation failed because another user has reserved the dependent join form.
Error
8313
The operation failed because another user has reserved the related filter.
Error
8314
The operation failed because another user has reserved the related active link.
Error
8315
The operation failed because another user has reserved the related escalation.
Error
8316
The operation failed because another user has reserved the related container.
Error
8317
The operation failed because another user has reserved the related application.
Error
8318
The object cannot be reserved because it does not exist on the server. You must save an object
on the server before you can reserve it.
Error
8351
Version control object modification log mode must be either 0 for disabled mode or 10 for
enabled mode.
Error
Specify a value of 0 or 10. Verify the Object Modification Log option on the Version Control tab of
the AR System Administration: Server Information form.
8352
The Server Version Control Task fields can only exist on one form.
Error
8353
The Server Version Control Object Modification Log fields can only exist on one form.
Error
8354
The operation succeeded, but all or some of the corresponding log entries were not added to
the AR System Version Control: Object Modification Log form.
Error
The operation succeeded, but logging failed.

8355
The Defintion Files option on the Version control tab must be either 0 for save and 10 for not
save.
Error
Specify a value of 0 or 10. Verify the Definition Files option on the Version Control tab of the AR
System Administration: Server Information form.
8356
The Server Version Control Label fields can only exist on one form.
Error
8357
The Server Version Control Labeled Object fields can only exist on one form.
Error
8358
Warning
226
The operation succeeded, but label was not created to the AR System Version Control: Label
form.
AR System messages

Number
Description
8359
Warning
The operation succeeded, but all or some of the corresponding labeled object entries were not
added to the AR System Version Control: Labeled Object form.
8360
The operation failed because the form object is already reserved.
Error
8361
The operation failed because the filter object is already reserved.
Error
8362
The operation failed because the active link object is already reserved.
Error
8363
The operation failed because the character menu object is already reserved.
Error
8364
The operation failed because the escalation object is already reserved.
Error
8365
The operation failed because the container object is already reserved.
Error
8366
The operation failed because the application object is already reserved.
Error
8367
The operation failed because the image object is already reserved.
Error
8368
The operation failed because the dependent join form object is already reserved.
Error
8369
The operation failed because the related filter object is already reserved.
Error
8370
The operation failed because the related active link object is already reserved.
Error
8371
The operation failed because the related escalation object is already reserved.
Error
8372
The operation failed because the related container object is already reserved.
Error
8373
The operation failed because the related application object is already reserved.
Error
8400
Task not found.
Error
8401
Duplicate task.
Error
8402
Checkpoint not found.
Error
8403
Duplicate checkpoint.
Error
227

Number
Description
8404
Task creation failed.
Error
8405
Checkpoint creation failed.
Error
8406
Cannot delete open task.
Error
8407
Permission denied because the user is not the task owner.
Error
8459
The number of rows exceeded the maximum allowed limit of 999.
Error
You tried to set the number of rows for a character field in BMC Remedy Developer Studio to less
than 999.
8469
Please select a source code control provider application.
Error
In the Server Information forms Source Control tab, you clicked the Browse button, but no source
control provider is selected in the Provider Name field. Before you click the Browse button, install
a source control system and select it in the Provider Name drop-down list.
8700
Attachment locator types can only be filename or the buffer. Use only these types.
Error
The only acceptable attachment locator types are the filename or the buffer. Use only these types.
8701
Bad attachment locator buffer size.
Error
8702
Bad attachment locator buffer pointer.
Error
8703
Bad attachment size.
Error
8704
OLE Automation active link action cannot be empty.
Error
The automation structure required when you define an OLE Automation active link action is
empty. Specify the appropriate contents for this structure.
8705
OLE Automation active link action method list cannot be empty.
Error
The method list required when you define an OLE Automation active link action is empty.
8706
Bad ARCOMValueStruct variable value.
Error
The value of an ARCOMValueStruct variable in a method or parameter of an OLE Automation

active link action is invalid. Provide a valid value.
8707
Bad OLE server or parameter name.
Error
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). Fix the name to continue your work.
8708
Bad OLE class ID or method ID, or interface of an OLE automation active link.
Error
The name of an OLE class ID, a method ID, or an interface of an OLE Automation active link action
is either empty or exceeding the maximum length allowed (128 characters).
8709
Bad OLE Automation active link action Method.
Error
The method structure of the OLE Automation active link action is invalid. Detailed errors follow
that explain what part of the method structure is invalid.
228
AR System messages

Number
Description
8710
Bad OLE Automation active link action Method name.
Error
The name of a method in an OLE Automation either is empty or exceeds the maximum length
allowed (128 characters).
8711
Empty OLE Automation active link action Method.
Error
The method structure required when you define an OLE Automation active link action is empty.
8712
Empty OLE Automation active link action Parameter List.
Error
The parameter list required when you define an OLE Automation active link action is empty.
8713
Empty OLE Automation active link action Parameter.
Error
The parameter structure of a method required when you define a method in an OLE Automation
active link action is empty. Specify the appropriate contents for this structure.
8714
Bad OLE Automation active link action Parameter.
Error
The parameter structure of a method in this OLE Automation active link action is invalid. Detailed
error messages explain what part of the structure is invalid.
8715
Bad automation string in the OLE Automation active link action.
Error
An automation action string required when you define an OLE Automation active link action
either is empty or exceeds the maximum length allowed (2000 characters).
8716
The RPC socket number for the Approval Server process is not one of the legal values (390600,
390621 - 390634, 390636 - 390669, 390680 - 390694).
Error
The value for the RPC socket is not set properly. Use the Approval Server Admin-Server Settings
form to set this to a legal value.
8717
The value for the Application check interval is not within the legal range of 0 to 3600 seconds.
Error
The value for Application Check Interval is not set properly. Set this to a legal value.
8718
The signal %d is not valid and is ignored.
Warning
8720
Open dialog value is empty.
Error
This message occurs when you try to create an Open Dialog active link action without specifying
an open dialog structure value. To create the Open Dialog active link action, enter a value.
8721
Call guide ID is empty.
Error
This message occurs when you try to create a Call Guide active link action without specifying a
Call Guide structure value. To create the Call Guide active link action, enter a value.
8722
Guide name missing.
Error
This message occurs when you try to create a Call Guide active link action without specifying a
Call Guide active link name. To create the Call Guide active link action, enter a name.
8723
Goto active link action label empty or too long.
Error
This message occurs when you try to create a Go To active link action without specifying a Go To
action label. To create the Go To active link action, enter a label.
8724
Goto action tag must be a field or value.
Error
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. To create the Go To active link action, use a field or value.
229

Number
Description
8725
Continuation button title is empty or too long.
Error
The button title cannot be empty or longer than the defined size of the button. If the title is empty,
supply a title. If the title is too long, shorten the title or lengthen the button.
8726
Guide calling itself is not allowed.
Error
The guide cannot contain workflow that calls that same guide.
8727
Invalid external table name in a vendor field mapping definition.
Error
The name identified in the vendor field definition is empty or exceeds the defined length
restriction.
8728
Invalid vendor form definition.
Error
The name identified in the vendor form definition is empty.
8730
Changing the field mapping is not allowed for join fields.
Error
The field definition for a field on a join form may not be modified after the field is defined.
However, you can modify it without error by setting it to the existing mapping.
8731
Changing the type in the field mapping structure is not allowed.
Error
When modifying an existing field in a form, you tried to change a field to a different type.
8732
Client type must be a non-negative integer.
Error
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.
8733
Unrecognized currency part tag.
Error
The currency part structure tag contains an illegal value.
8734
Invalid currency code string length.
Error
The currency code is not a valid three character string, for example, USD.
8735
Bad decimal value.
Error
The decimal data is formatted incorrectly. Only numeric characters are valid as decimal data. For
example, 1.234 is a valid decimal value, while 1.abc##345 is an invalid decimal value.
8736
An arithmetic error was encountered in a decimal calculation.
Error
Your system is unable to complete the arithmetic operation. Contact your AR System
administrator for assistance.
8737
Notify header name cannot exceed 255 bytes.
Error
Enter a header name of 255 bytes or less for the email notification template.
8738
Notify footer name cannot exceed 255 bytes.
Error
Enter a footer name of 255 bytes or less for the email notification template.
8739
Notify content name cannot exceed 255 bytes.
Error
Enter a content name of 255 bytes or less for the email notification template.
8740
Unable to create a server thread.
Error
8741
Unable to create a mutex.
Error
8742
Unable to create a semaphore.
Error
230
AR System messages

Number
Description
8743
Unable to lock a mutex.
Error
8744
Unable to perform semaphore operation.
Error
8745
Unable to create a queue to process RPC requests.
Error
8746
Unable to allocate thread local storage.
Error
8747
Unable to access thread local storage.
Error
The AR System server encountered a serious error performing a fundamental operating system
function. The most likely cause is that the system is out of memory.
8748
Semaphore operation timed out.
Error
8749
Approaching physical stack limit.
Error
8750
Create entry operations are not supported for this form.
Error
AR System database connectivity plug-in associated with the form does not support create
operations and a creation was attempted.
8751
Set entry operations are not supported for this form.
Error
AR System database connectivity plug-in associated with the form does not support modify
operations and a modification was attempted.
8752
Delete entry operations are not supported for this form.
Error
AR System database connectivity plug-in associated with the form does not support delete
operations and a deletion was attempted.
8753
Error in plugin.
Error
A run-time exception occurred during a Java plug-in server call to a plug-in. AR System adds
detailed information about the error to the
ARServerInstallDir\Arserver\Db\arjavaplugin.log file.
8754
Retrieving attachment data is not supported for this form.
Error
AR System database connectivity plug-in does not support attachments.
8755
The specified plug-in does not exist.
Error
AR System server referenced a plug-in that the plug-in service has not loaded.
8756
An error has occurred while loading a plug-in.
Error
The plug-in service could not load the specified plug-in. An associated error message contains
details.
8758
The plug-in name is empty, contains invalid characters, or is a reserved name. The plug-in will
not load.
Error
Plug-in names may not be empty, may not contain space characters, and may not be a reserved
name, such as AREA.
8759
The plug-in does not implement ARPluginIdentify(). The plug-in will not load.
Error
All plug-ins must define the function ARPluginIdentify() and the specified plug-in does not
do so.
231

Number
Description
8760
Cannot establish a network connection to the AR System Plug-In server.
Error
Error 8760 and error 8939 can be caused by a plug-in operation that fails when the AR System
servers connection to the plug-in server fails. Either a configuration problem exists, or the plugin server is not running.
Some operations that can generate this error are initial login to the AR System server, an attempt
to create a vendor form, interaction with ITSM consoles, or any other operation supported by
plug-in functionality.
To diagnose the cause of this error, check these items:
Confirm that the plug-in server is running:

(UNIX) Confirm that the arplugin process is running.
(Windows) Check the Windows Task Manager to confirm that arplugin.exe is running.
If plug-in logging is turned on, check the output at the time the error occurred to verify the
state of the plug-in server.
Verify that plug-ins are correctly configured to load when the plug-in server starts and that each
is successfully loading:
View the contents of the ar.conf or ar.cfg file. For each entry with the format
Plugin:pathToPlug-inLibrary, verify that the plug-in library exists in the specified
location and has permissions and ownership consistent with other AR System server libraries
and binaries in the ARSystemInstallDir/bin directory.
Turn on Plug-in Server logging, and set the Plugin Log Level to All. Verify that each plug-in
listed in the ar.conf or ar.cfg file appears with a successful start in the log file.
Determine which plug-in is associated with the error and, if possible, the events that lead to the
error:
To help isolate the workflow or operation triggering the error, turn on server API and Filter
logging.
To identify the API call that results in the error, turn on client-side ARAPILOGGING on a
client computer where the error appears.
Although the plug-in server can use a portmapper to troubleshoot this error, consider setting a
plug-in port and a Server-Plugin-Alias setting in the configuration file to see whether it resolves
the problem. For information about these settings, see the Configuration Guide.
If the plug-in connection error is related to a BMC Remedy application, make sure that you have
applied the latest patches for the application.
For more troubleshooting information, see the BMC Remedy Support Knowledge Base at
http://www.bmc.com/support.
8761
Error
An invalid password has been used for access to the plug-in server. Contact your AR System
Administrator for assistance.
The plug-in server password was established to restrict access to AR System servers that are
similarly configured. In this case, the password used by AR System server does not match that of
the plug-in service.
8762
Error
The specified plug-in failed to initialize properly. Contact your AR System Administrator for
assistance.
The plug-in encountered an error while trying to initialize and failed to load.
8763
The specified plug-in failed to set properties.
Error
The set property function of the specified plug-in failed in some way.
232
AR System messages

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

Number
Description
8781
Invalid Command line arguments. Usage: java ARPluginServerMain -x hostname -t portnum

-i workingfolder.
Error
Invalid or missing values were supplied for the Java plug-in server startup. Make sure the
command-line arguments are valid.
8782
Error
Invalid port number. Usage: java ARPluginServerMain -x hostname -t

portnum -i workingfolder.
The TCP port number to which the plug-in server will bind must have a valid value. Specify a free
port in the range between 1 and 65000.
8783
Unknown host. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder.
Error
The host name used for the Java plug-in server is invalid. Supply a valid value.
8784
Data encryption error encountered.
Error
Depending on the encryption policy, all data flowing between the AR System server and the plugin server is encrypted unless the policy not to use encryption is chosen. An error occurred while
data was being encrypted to be sent to the server. Try using a different encryption policy or
algorithm.
8785
Data decryption error encountered.
Error
Depending on the encryption policy, all data flowing between the AR System server and the plugin server is encrypted, unless the policy is chosen not to use encryption. An error occurred while
data coming from the AR System server was being decrypted. Try using a different encryption
policy or algorithm.
8786
Error while setting up public/private key pair.
Error
The plug-in server sets up the encryption keys for key exchange between a client (the AR System
server in this case) and the server (plug-in server). An error occurred while these keys were being
set up. Try using a different encryption policy or algorithm.
8787
Error fetching private key.
Error
server in this case) and the server (plug-in server). An error occurred while a private key was
being fetched. Try using a different encryption policy or algorithm.
8788
Error fetching public key.
Error
server in this case) and the server (plug-in server). An error occurred while a public key was being
fetched. Try using a different encryption policy or algorithm.
8789
Error encountered while encoding string to bytes.
Error
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. An error was encountered while
encoding string to bytes using the AR System server character set. If you are unable to resolve the
problem, contact Customer Support.
8790
Unknown system error.
Error
This error most commonly occurs when an exception occurred while processing a call that is not
recognized by the plug-in server. The most common cause is uncaught exceptions encountered in
the plug-ins, like null pointer exceptions.
8791
AR System Plugin Server Version 7.1.0. Started up.
Note
234
AR System messages

Number
Description
8792
Exception occurred while loading the native plugin host library.
Error
This error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plugin server can host native and C plug-ins. It does this by first loading the arpluginjnia JNIbased library that hosts the C plug-ins. This error indicates that the plug-in server Java Virtual
Machine could not find or load this library, which results in none of the configured native plug-ins
being loaded. You can ignore this error if you are not using C plug-ins in the Java plug-in server.
The Java plug-ins still function without problems. The appended text indicates the problem, such
as if the file could not be found or dependencies could not be found. Make sure the arpluginjni
library and all its dependencies are in the system PATH.
8793
AR Plugin Server Startup Error.
Error
A fatal error was encountered during plug-in server startup. To resolve the issues, check the log
files for information about the reason for the failure.
8794
Plugin Termination Error.
Error
When a thread goes down in the plug-in server, the terminate method is called on all the plug-ins.
An error occurred during one of the terminate calls. See the log files for details.
8795
Plugin Create Instance Error.
Error
Create instance is called on each plug-in on a new thread startup so that plug-ins can create an
instance of any thread safe data and save it in the plug-in server threads context. An exception
occurred while an instance was being created. See the log file for details.
8796
Plugin Delete Instance Error.
Error
Delete instance is called on each plug-in on a thread shutdown so plug-ins can clean up any thread
safe data that was saved in the plug-in server threads context. An exception occurred while an
instance was being deleted. See the log file for details.
8797
Error encountered while encoding bytes to string string.
Error
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. An error was encountered while
encoding a string to bytes using the server character set. If you are unable to resolve the problem,
contact Support.
8800
The specified container owner name is incorrect.
Error
This is likely caused by a programming error, for example, in an incorrect API program.
8801
The value of the specified reference is empty.
Error
8802
The label of the specified reference is empty.
Error
8803
The description of the specified reference is empty.
Error
8804
The specified container does not exist.
Error
This is likely caused by a programming error, for example, in an incorrect API program. 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.
8805
You do not have access to the specified container.
Error
You do not have permission to access this container. Contact your AR System administrator for
assistance.
235

Number
Description
8806
The specified container is missing.
Error
A parameter is required, but the value passed is either NULL or an empty string. Load this
parameter with the name of the form you want to reference.
8807
Unable to open the specified container.
Error
8809
Illegal container type.
Error
You tried to define a container owner object that is not a supported container type. 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
The specified container already exists.
Error
Enter a different name for the container.
8811
No name was specified for the owning object.
Error
No owner name was specified. Typically, this occurs when a definition file you try to import
contains an error.
8812
Container cannot be owned by this type of object.
Error
8814
No container ID for the container.
Error
8815
Missing or invalid container definition file.
Error
8816
Illegal reference type.
Error
This is likely caused by a programming error, for example, in an incorrect API program in which
the reference list is invalid.
8817
The value of the external reference has an invalid format.
Error
8818
The container is not supported by the server.
Error
This is likely caused by old server containers.
8819
Application owner does not match whats defined in the schema.
Error
8830
Object cannot be locked.
Note
One of more objects being exported cannot be locked. Object locking is not supported for DSO or
flashboards objects. Contact Customer Support for assistance, if necessary.
236
AR System messages

Number
Description
8831
Locking level cannot be decreased.
Warning
A locked object can be exported only at the same lock level or a higher lock level. Contact
Customer Support for assistance, if necessary.
8832
Unknown object lock level specified.
Error
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.

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

Number
Description
8844
Safeguard mismatch - potentially corrupted filter.
Error
A system error occurred. The object is possibly corrupted. The filter might have been modified at
the database level. Contact Customer Support.
8845
Safeguard mismatch - potentially corrupted escalation.
Error
A system error occurred. The object is possibly corrupted. The escalation might have been
modified at the database level. Contact Customer Support.
8846
Safeguard mismatch - potentially corrupted menu.
Error
A system error occurred. The object is possibly corrupted. The menu might have been modified
at the database level. Contact Customer Support.
8847
Field creation not allowed on a locked form.
Error
You cannot create fields on a locked form.
8848
Field deletion not allowed on a locked form.
Error
You cannot delete fields on a locked form.
8849
Setting object lock information is disallowed at this time.
Warning
During set or create operations, locked object properties are not expected. Export the object as
locked.
8850
A lock block must be exported entirely in xml or entirely in def format.
Error
In a single export call, all objects must be exported in the same format, which can be .xml or .def.
8851
Setting BSM tag disallowed.
Warning
This action is for internal use only.
8852
Server setting out of range.
Error
Check server settings and make any necessary corrections.
8853
Invalid locale info supplied.
Error
This error occurs when you use the API to send initialized locale information in ARControlStruct.
Review your program and make sure the correct ARControlStruct parameter is passed.
8854
Child entries are not processed.
Warning
An XML Service Entry does not support processing of multiple entries. If the input XML
document holds multiple entries when executing an OpService web service operation, the XML
Service Entry will process only the first entry, Child entries will not be considered. This warning
indicates that the operation is successful but that the child entries are not considered.
8855
Safeguard mismatch - potentially corrupted image.
Error
A system error occurred. The object is possibly corrupted. The image might have been modified
at the database level. Contact Customer Support.
8856
An overlay and its corresponding overlaid object cannot belong to the same overlay group.
Error
To create an overlay of an object that belongs to an overlay group, you must assign the new
overlay to a different overlay group.
Note: Release 7.6.04 supports only one overlay group (group ID 1). All overlay and custom objects
must belong to that group. Therefore, you cannot create overlays of overlay and custom objects
in release 7.6.04 because their overlays cannot be assigned to another overlay group.
238
AR System messages

Number
Description
8857
Creating overlay is not supported for the type of object specified.
Error
You tried to create an overlay for a type of object that does not support overlays.
Overlays can be created for active links, active link guides, escalations, filters, filter guides, forms,
views, fields, images, local applications, menus, packing lists, and web services.
Overlays cannot be created for custom objects, deployable applications, overlaid objects, and
overlay objects.
Note: DSO mappings, DSO pools, flashboards, skins, and templates are stored as data in a form.
They are not AR System objects. Therefore, you cannot use overlays to customize them.
8858
Error
__C and __O are system reserved suffix and cannot be added manually.
You tried to include one of the following strings in the name of an object:
__c (reserved for future use)

__o (reserved for overlay object names)
AR System automatically adds those strings to custom or overlay object names. You cannot
manually add them to the names of other types of objects.
8859
Invalid operation on overlay or overlaid object.
Error
You tried to perform an operation that is not permitted on an overlay or overlaid object.
In Best Practice Customization mode, AR System restricts the operations that can be performed
on objects to ensure that you perform only changes that will be preserved during application
upgrades.
To perform the operation on an AR System origin object, switch to Base Development mode.
WARNING: Base Development mode gives you unrestricted access to create, modify, and delete AR
System origin objects, such as out-of-the-box application objects, but your changes might not
survive upgrades.
8860
Error
The Group ID for Overlay and custom objects can only be 0 (does not belong to an overlay
group) or 1 (belongs to the overlay group).
The specified overlay group is not supported by the server. In release 7.6.04, AR System supports
only one overlay group, overlay (group ID 1), which is a predefined level 1 group. Therefore,
all overlay and custom objects are automatically assigned to it.
If an operation requires you to specify an overlay group, provide one of the following values:
0 (does not belong to an overlay group)

1 (belongs to the overlay group)
For information about specifying design time and runtime overlay groups, see the following
variable descriptions for the ARSetSessionConfiguration function in the C API Reference
guide:
AR_SESS_CONTROL_PROP_DESIGN_OVERLAYGROUP
AR_SESS_CONTROL_PROP_API_OVERLAYGROUP
8861
Base and overlay object should be of same type.
Error
When converting an origin object to custom make sure that their types match. Otherwise, the
ARCreateOverlayFromObject API call returns this error.
8863
Before creating an overlay of a field or a form view, you must create an overlay of the objects
associated form.
Error
Before creating an overlay of a field or a view, you must create an overlay of the objects associated
form.
239

Number
Description
8864
Invalid value for overlay property.
Error
You are not permitted to assign the value that you specified to the property of an overlay object.
In Best Practice Customization mode, AR System restricts the values that can be assigned to
properties to ensure that you perform only changes that will be preserved during application
upgrades.
To assign this property value to an AR System origin object, switch to Base Development mode.
WARNING: Base Development mode gives you unrestricted access to create, modify, and delete AR
System origin objects, such as out-of-the-box application objects, but your changes might not
survive upgrades.
8865
Field/View overlay and the associated base form overlay must be in the same overlay group.
Error
You tried to assign a field or a view to a different overlay group from the group to which its
associated overlay form belongs to.
Field and views must belong to the same overlay group that their associated overlay form belongs
to.
8866
Error
Audit/Archive form overlay and the associated base form overlay must be in the same overlay
group.
You tried to assign an overlay audit or archive form to a different overlay group from the group
to which the forms associated overlay origin form belongs.
An overlay audit or archive form must belong to the same overlay group to which its overlaid
origin form belongs.
8867
Unable to find overlay for specified overlaid object.
Error
When you make a change on an overlaid object that should reflect on its overlay, the AR System
server searches for that overlay. If the overlay is not found, the AR System returns this error. The
occurrence of this error indicates that form definitions in the database, the server cache, or both
were corrupted.
8868
Field overlay and the associated view overlay must be in the same overlay group.
Error
You tried to assign an overlay field to a different overlay group from the group to which the fields
associated overlay view belongs.
An overlay field must belong to the same overlay group to which its overlay view belongs.
8869
To convert custom field to overlay, field ID of custom and base must be the same.
Error
The ARCreateOverlayFromObject API call returns this error when you try to convert custom
fields to overlays. Make sure that the custom fields ID is the same as the field ID of the origin field
that you want it to overlay.
Note: This operation is allowed only for special fields.
8870
Error
To convert custom field to overlay, custom form name and the base form name must be the
same.
The ARCreateOverlayFromObject API call returns this error occurs when you try to convert
custom fields to overlays. Make sure that the name of custom form (that contains the field you
want to overlay) matches that of the origin form.
Note: This operation is allowed only for special fields.
8871
Field must be of custom type on given form.
Error
To convert a field to overlay, it must be a custom field. If the Best Practice Conversion utility
encounters a non-custom field to be converted to overlay, it returns this error.
240
AR System messages

Number
Description
8872
Unable to find the overlaid object.
Error
The AR System server returns this error if the overlaid object is not found in the following
situations:
While loading overlay object information.

When overlay objects need access to overlaid objects.
This error indicates a problem with object definitions.

8873
Renaming of overlay object is not allowed.
Error
You cannot rename overlay objects.

Instead, you can create a matching object with the new name in either of the following ways:
In Best Practice Customization mode, use the Save As command to make a copy of the overlay
object and give the new custom object the name.
In Base Development mode, rename the corresponding overlaid object. AR System
automatically updates the name of the overlay object to match the overlaid objects new name.
8874
Object is not a valid custom object, hence cannot be converted to base.
Error
AR System allows only converting a custom object to an origin object. If the object you selected
for conversion to origin is not a custom object, BMC Remedy Developer Studio displays this error.
Select only a custom object to convert to origin.
8875
Audit or archive form must be custom for the specified overlay form.
Error
When enabling an overlay or custom form for auditing or archiving, if the audit or archive form
that you specify already exists, it must be a custom form with the same overlay group. Otherwise,
BMC Remedy Developer Studio displays this error.
To proceed, specify a custom audit or archive form that belongs to the same overlay group, or
specify a new form name.
8876
Error
The object is either custom or overlay object and converting it to custom or overlay in same
overlay group is not allowed.
AR System only allows converting an origin object, or an overlay or custom object of a different
overlay group, to overlay or custom. If you select a non-origin object and try to convert it to an
overlay or custom object with the same overlay group, BMC Remedy Developer Studio displays
this error.
To proceed, specify a different overlay group than that of the currently selected object.
AR System does not allow converting an overlay or custom object further to overlay or custom. If
you select an overlay or custom object and try to convert it to overlay or custom, BMC Remedy
Developer Studio displays this error.
Select only an origin object to convert to overlay or custom.
8879
Base object and custom object names are same. Conversion of custom to overlay is not allowed.
Error
8900
The GetListFields operation cannot be performed on a dialog form.
Error
This operation cannot be performed on a dialog form. A dialog has no data to query.
8901
The GetListFields operation cannot be performed on a dialog form.
Warning
8902
The Sort List operation cannot be performed on a dialog form.
Error
241

Number
Description
8903
The Sort List operation cannot be performed on a dialog form.
Warning
8904
Filters are not allowed on a dialog form.
Error
8905
Escalations are not allowed on a dialog form.
Error
8906
Dialog form cannot have core fields.
Error
8907
Dialog form can only have display-only fields.
Error
8908
Windows Logon fails.
Error
Either the user name or the password is invalid or does not exist on Windows Logon Server. Make
sure that the user name and the password exist and are correct.
8909
Dialog forms are not allowed in join forms.
Error
An attempt was made to create a join form and one of the forms in the join was a dialog form. You
cannot create joins with dialogs.
8910
Field referenced in the qualifier of a table field cannot be deleted.
Error
You tried to delete a field referenced in a table field qualification. You cannot delete fields
referenced in table field qualifications. To delete the field, remove the field name from the
qualification.
8911
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.
Warning
The maximum allowed length of AR_MAX_SDESC_SIZE is 128 bytes. Remove fields from the list,
specify shorter field widths, or reduce the separators between columns to reduce the total to less
than AR_MAX_SDESC_SIZE.
8912
The ARGetListEntryWithFields call is not supported by the pre-4.0 AR System server.
Error
Active link workflow tried to perform an ARGetListEntryWithFields call with a pre-4.0

AR System server. This API call is not possible with older servers.
8913
A server could not get or lock a semaphore. Make sure that your computer is correctly
configured for shared memory and semaphores. If it is, run arsystem stop, and then run
arsystem start.
Error
A server could not get or lock a semaphore. Make sure that your computer is correctly configured
for shared memory and semaphores. If it is, run arsystem stop, and then run arsystem
start.
8914
Workflow logging activated.
Note
The request log type matches the current log.
8915
Insufficient disk space for logging to requested file. Free up disk space before continue.
Warning
This logging error typically is returned when you run out of disk space. To continue, free up space
in the log directory by deleting old or unwanted files.
8916
Unable to update next available field ID.
Error
242
AR System messages

Number
Description
8917
Unable to get next available field ID.
Error
8918
Unable to update next available VUI ID.
Error
You were unable to update the next field ID column in the database for a new VUI in a form.
8919
Unable to get next available VUI ID.
Error
8920
Must specify a form for the workflow to create an active link, filter, or escalation.
Error
You did not specify the forms for the workflow you are creating. Specify the forms to which the
workflow is attached.
8921
The form list for the workflow contains no forms.
Error
The form list contains no forms. The workflow must be associated with a single form or a list of
forms that exist on the server.
8922
The authentication service is not responding. Cannot connect to the system at this time. Contact
your AR System Administrator for assistance.
Error
The external authentication server is not responding to calls from the AR System server.
8923
Unrecognized or misused tag for workflow connection structure.
Error
No form list exists for the workflow connection. The workflow must be associated with a list of
forms that exist on the server.
8924
Two or more forms in the workflow form list have duplicate form names.
Error
8925
The legal value for the RPC socket number for the External Authentication process is 390695.
Error
The user tried to set the value of the external authentication RPC socket to a value other than
390695. Specify 390695 only.
8926
The appended text is a message from the external authentication server: note.
Note
The appended text is a message from the external authentication server.
8927
The appended text is a message from the external authentication server: error.
Error
The appended text is a message from the external authentication server.
8928
Error opening the application audit file (<ar>/db/appl.aud).
Error
8929
Error opening the application violation file (<ar>/db/appl.vio).
Error
8930
The form was not found in the cache.
Error
An invalid form was found in the form list.
8931
Error in semaphore name.
Error
An error exists in the FTS handle (for example, it is greater than 255 characters), and therefore the
event semaphore could not be opened to enable signals from server.
8932
You do not have write license.
Error
A user is modifying the contents of a field but does not have write access.
8933
No views were imported.
Warning
Your attempt to import views into the form failed. An associated message indicates why the view
was not imported. Fix the problem, and reimport the item.
243

Number
Description
8934
The proxy fork process could not write information to its log file.
Error
The proxy fork process could not write information to its log file.
8935
Upgrade of the server internal forms failed. Only a valid internal form definition can be
upgraded.
Error
Only a valid internal form definition can be upgraded. Only the following forms are valid here:
Distributed Mapping
Distributed Pending
Distributed Pool
Application Pending
8936
Compression of file failed.
Error
Compression failed when adding the attachment file to a request during the Perform-ActionAdd-Attachment command used in a Run Process filter action. To continue, increase the size of
the buffer used in the attachment field.
This error also is returned if the size of the input buffer exceeds 57 bytes.
8937
You do not have permission to the client operation: operationName.
Error
A client-type operation was disabled for the current user, for example, if a user belongs to an
excluded group.
8938
Error during Xerces-c Initialization.
Error
The Xerces library globals used in the XML parser failed to initialize.
8939
The AR System Plug-In server is not responding. Cannot connect to the system at this time.
Contact your AR System Administrator for assistance.
Error
An RPC time-out occurred when connecting to the plug-in server. Make sure that the plug-in
server and AR System plug-ins are running.
For more information about troubleshooting plug-in server connectivity, see the entry for error
8760.
8940
Error during XML definition parsing.
Error
An error occurred when an XML document was parsed. The XML file, XML string, and XML
object name cannot be parsed.
8941
XML Parsing error. Invalid element tag.
Error
The parser found an invalid element tag while parsing the XML document.
8942
XML Parsing error. Invalid attribute tag.
Error
The parser found an invalid attribute tag while parsing the XML document.
8943
XML Parsing error. Invalid enumeration value.
Error
The parser found an invalid enumeration value while parsing the XML document.
8944
XML Parsing error. Invalid character data.
Error
This parsing error occurred while the character data was parsed.
8945
No such object in the parsed XML object list.
Error
This parsing error is returned because no such XML object exists in the object list.
8946
EXTERNAL qualification contains a circular reference.
Error
An EXTERNAL qualification making a reference to itself is an illegal operation. The process stops
and an error message is returned.
244
AR System messages

Number
Description
8947
Invalid license key. Please provide a valid license key.
Error
You were unable to create a license because the license key does not match the generated key
based on the license information provided.
8948
Invalid session configuration option.
Error
You were unable to set a valid public API session variable. This error can be encountered only
through an API program.
8949
Invalid enumerated value style.
Error
An enumerated data type has an invalid value.
8950
Custom style enumerated value must be unique for each choice. The specified value is a
duplicate.
Error
Duplicate values exist in a custom style enumerated data type. Make sure all choices are unique.
8951
The Status field cannot be a query style enumerated value.
Error
The Status History field of a Data Dictionary style character menu cannot be expanded as a query
style enumerated value.
8952
An invalid XML document type was specified.
Error
The server could not parse the XML document because you specified an invalid XML document
type.
8953
Unable to load the arxmlutil library.
Error
The server failed to load the AR System XML shared library. The name of the library is
arxmlutil.
8954
A failure occurred while trying to open the file.
Error
While trying to append the string contents to the end of the file, the operation failed because the
file could not be opened. To continue, verify that the file exists and that you have permissions to
access it.
8955
XML import and export is not supported.
Error
XML import and export is not supported for this object in the file.
8956
This operation does not support the specified date part.
Error
The requested date parts are not supported by this operation. Either the date parts value is invalid,
or this operation does not support the date parts value.
8957
The date format is invalid.
Error
The specified date string is invalid. For example, an invalid date format would be 22/15/02,
which would be converted to Month 22, Day 15, Year 2002 (a year has only 12 months).
8958
The date value is invalid.
Error
When converting a ISO or US date string to Julian calendar format, you see this error message if
the string contains an invalid date value.
8959
The XML data type being converted is not supported by AR System.
Error
The XML data type being converted is not supported by AR System or the XML data type is
invalid.
8960
Server information data is in an incorrect format.
Error
Server information data is not correctly formatted. This error can occur with commands that take
as parameters multiple strings separated by semicolons.
245

Number
Description
8961
A required element is missing from the XML input document.
Error
Verify that the XML input document is correct for the XML mapping document. A required
element is missing from the XML input document.
8962
Unexpected element encountered in the input XML document.
Error
Verify that the XML input document is correct for the XML mapping document. An unexpected
element is in the input document.
8963
The number of entries exceeds the XML elements maxOccurs value.
Error
The number of entries in the list must be equal to or less than the maxOccurs value.
8964
The number of entries is less than XML elements minOccurs value.
Error
The number of entries in the list must be equal to or greater than the minOccurs value.
8965
The default notification mailbox is not specified.
Error
No default mailbox was configured so no default mailbox is available for the email notification.
8966
Required XML element is missing from the XML mapping.
Error
The format of the XML mapping document is incorrect and must be corrected.
8967
Required XML attribute is missing from the XML mapping.
Error
The format of the XML mapping document is incorrect and must be corrected.
8968
Invalid process definition.
Error
8969
A required attribute is missing from the XML input document.
Error
Verify that the XML input document is correct for the XML mapping document. A required
attribute is missing from the XML input document.
8970
The key for this entry must be unique in the XML input document.
Error
The key for this entry must be unique in the XML input document.
8971
The reserved centralized user preference field can only exist on one form delete the
duplicate.
Error
The system found two forms containing the reserved centralized user preference field. Delete one
of the forms.
8972
Error
The reserved centralized administrator preference field can only exist on one form delete the
duplicate.
The system found two forms containing the reserved centralized administrator preference field.
Delete one of the forms.
8973
The reserved centralized file preference field can only exist on one form delete the duplicate.
Error
The system found two forms containing the reserved centralized file preference field. Delete one
of the forms.
8974
The from information of the email notification message cannot exceed 255 bytes.
Error
Enter from information of 255 bytes or less for the email notification message.
8975
The reply to information of the email notification message cannot exceed 255 bytes.
Error
Enter reply to information of 255 bytes or less for the email notification message.
8976
The CC list of the email notification message cannot exceed 255 bytes.
Error
Enter CC information of 255 bytes or less for the email notification message.
246
AR System messages

Number
Description
8977
The BCC list of the email notification message cannot exceed 255 bytes
Error
Enter BCC information of 255 bytes or less for the email notification message.
8978
The organization list of the email notification message cannot exceed 255 bytes.
Error
Enter organization information of 255 bytes or less for the email notification message.
8979
The mailbox name information of the email notification message cannot exceed 255 bytes.
Error
Enter mailbox name information of 255 bytes or less for the email notification message.
8980
Failed to open a system form definition file: fileName.
Error
The server failed to open a system form definition file that should be in a standard location. The
server needs to add the system form by importing the definition from the file. Make sure the file
specified in the error message is present and accessible.
8981
Setting application owner is disallowed.
Warning
The application owner object property cannot be set.
8982
Object is already owned by another application.
Error
This object has an application owner and cannot be added to this application. To add the object to
this application, first remove it from the application that owns it.
8983
Changing the data type of the field is not allowed.
Error
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.
8984
Group permissions have been removed from the object because the object is in a deployable
application.
Warning
A deployable application cannot have group permissions.

8985
Warning
Roles permissions have been removed from the object because the object is not in a deployable
application.
An object not in a deployable application cannot have role permissions.
8986
The alias for this object is not unique. It will be set to empty string.
Warning
The web alias names for applications, forms, and views must be unique. The web alias names for
views must be unique in all views for the form.
8987
Change field action can only be: 1 to indicate a field or 0 to indicate a value.
Error
The option value that was specified is invalid. It must be specified as 1 to indicate a field or to 0
to indicate a value. Contact your AR System administrator.
8988
Archive or Audit information could not be set for this form.
Error
This message is accompanied by more specific messages. Examine the associated messages to
diagnose the problem.
8989
Cannot delete data fields from Archive or Audit form.
Error
An attempt was made to delete data fields (field types 1 to 14 and 35 to 37) from an archive or
audit form. To delete a field, clear the Enable option in the source form to disable archiving or
auditing for the form first.
8990
Cannot modify Limit Info or Permission for a data field in an Archive or Audit form. These
values will be made NULL before setting.
Warning
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. The system sets these
properties to NULL before setting them. Set these values to NULL to avoid seeing the warning
message.
247

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

Number
Description
9000
Encryption is disallowed by the AR System server.
Error
The RPC call failed, and AR System server does not support encryption.
9001
Encryption is required by the AR System server.
Error
The AR System server does not disallow encryption. 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.
9002
Data encryption key exchange failed.
Error
The actual key exchange between the client and the server failed due to a serious error by one or
both of the RPC calls.
9003
Error during public key data decryption.
Error
Public key decryption failed due to no authentication between client and server.
9004
Error during symmetric key data decryption.
Error
The MAC (message authentication code) failed during the decryption routine, when comparing
the MAC in the decrypted message against the locally generated MAC.
9005
An error occurred in the encryption library.
Error
An attempt to generate the random number used during the encryption routine failed.
9006
The specified public key encryption algorithm is not supported by the encryption library.
Error
An unknown encryption algorithm was used.
9007
The specified data key encryption algorithm is not supported by the encryption library.
Error
9008
The size of the memory buffer used in XDR (external data representation) is invalid.
Error
The size of the memory buffer used in XDR (external data representation) is invalid.
9009
XDR xres error during XDR encoding.
Error
The XDR (external data representation) process could not present the result pointer into the
memory buffer.
9010
The encryption library was not found and cannot be loaded.
Error
Encryption is turned on, but the required encryption shared library DLL could not be found or
loaded.
9011
Loading of encryption library failed.
Error
The encryption shared library DLL could not be successfully loaded.
9012
Encryption is not licensed on the AR System server.
Error
No encryption licensing is on the AR System server.
9013
The encryption license does not match the encryption library.
Error
No encryption licensing is invalid on the AR System server.
9014
The encrypted string is greater than the maximum length allowed.
Error
The actual size of the string exceeds the size limit specified for the string. This error can occur
when the string becomes corrupted.
9015
To encrypt/decrypt a null string is not allowed.
Error
An internal error occurred because the string has a NULL value.
249

Number
Description
9016
An error occurred with the decryption because the CRC is invalid.
Error
The encrypted string could not be decrypted because the cyclic redundancy check (CRC) failed.
An invalid CRC indicates that the encrypted string is corrupted.
9017
FIPS encryption failed.
Error
To comply with FIPS 140-2 standards, the encryption library must enter FIPS mode. This error
indicates the encryption library failed to enter FIPS mode.
9018
Client cannot connect to this FIPS-compliant server because the client is connected to a server
that does not enforce FIPS.
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:
9019
Error
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)
Client cannot connect to this FIPS-noncompliant server because the client is connected to a
server that enforces FIPS.
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
FIPS mode requires the security policy to be encryption required.
Error
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).
Therefore, the AR System server or the Java plug-in server did not start. For more information, see
the AR System server arerror.log file or the Java plug-in server arplugin.log file.
To fix this error, set Encrypt-Security-Policy to 1 (encryption required).
250
AR System messages

Number
Description
9050
Localization has been turned on but no Message Catalog exists.
Error
The Localize Server check box is selected on the Advanced tab of the Server Information dialog
box, but an AR System Message Catalog form cannot be found on the server. This error can occur
for several reasons:
The form might have been deleted.

A field on the Message Catalog form might have been deleted.
Corrupt data might have been added.
To continue, make sure the form exists. If it does not exist, stop and start the server. The form is
automatically re-created at system startup. If the form itself is corrupted, you might need to delete
the form and start over. In this case, export any data into an .arx, .csv or .xml data file format so
that you can reimport it after the form is re-created at system startup.
9051
Multiple Message Catalogs exist. There must only be one Message Catalog.
Error
Two or more AR System Message Catalog forms were found on the same server. To continue, you
can have only one Message Catalog form on a server. Delete one of the Message Catalog Forms
and restart the server.
9052
The VUI is not unique for the form. The label, locale, and platform properties of this VUI must
be unique to the form.
Error
For localization purposes, VUIs for a form must be unique. To continue, create a unique VUI
combination of label, locale, and platform.
9053
Warning
The default VUI specified in the schema import file was not found. The default VUI was
redefined to a pre-existing VUI from the form.
The default admin view of the form was not found during the import operation. Instead, the
previously existing default admin view is used.
9054
The specified field does not exist in the form.
Warning
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. The field is not imported, and the import process
continues.
9055
The VUI import file is in an incorrect format.
Error
No VUI definition from the file was retrieved during the import operation. The format of the
import file was corrupted so that it contains no VUI information.
9056
The server is not localized.
Error
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. Possible reasons include:
Message Catalog Form was not found on the server.

No messages were found in the Message Catalog Form, not even defaults.
The Localize Server check box was cleared in the Advanced tab of the Server Information dialog
box.
To continue, make sure the Message Catalog Form exists, that its contents is not corrupted, and
that the Localize Server check box is selected in the Advanced tab of the Server Information dialog
box.
9057
Recursion of localized queries are not allowed.
Error
A query cannot retrieve more than one localized value of a message at a time.
9058
Update of Localized Active Link or Menu failed.
Error
The timestamp of the localized active link or menu could not be updated.
251

Number
Description
9059
The join form contains a circular reference.
Error
Fix the join form definition.
9060
A system error prevented the Unicode converter from being opened.
Error
A system error prevented the Unicode converter from being opened.
9061
Failed to convert the Character data to Unicode format.
Error
Character data could not be converted to Unicode format.
9062
Failed to convert from Unicode format to character data.
Error
Character data could not be converted from Unicode format.
9063
Server allows only Unicode clients (except Administrator and Alert tools).
Error
AR System server does not support non-Unicode clients such as BMC Remedy User, BMC
Remedy Data Import (GUI Version), the runmacro program, and version 6.3 of the Mid Tier. The
server provides limited Unicode support for BMC Remedy Administrator and BMC Remedy
Alert.
To contact this server, use a browser instead of BMC Remedy User. Use BMC Remedy Developer
Studio instead of BMC Remedy Administrator.
9075
Problem encountered during creation of one of the server system forms.
Error
On AR System server startup, if one of the AR System servers system forms does not exist,
AR System creates it. This message indicates that AR System failed to create the missing forms,
however, AR System still starts. 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. To eliminate the message, delete the Server Events and Server Statistics forms. The
next time you restart AR System, these forms are automatically re-created, and the message no
longer appears.
9076
Cannot find the Server Events form.
Error
While server event recording was enabled, the server could not find the Server Events form to
record an entry.
9077
Server Events fields can only exist on one form. Delete the duplicate.
Error
The Server Events form is defined from a unique combination of AR System reserved fields. If an
attempt is made to create a form that contains these fields while the Server Events form exists, the
server prevents creation of the new form.
9078
Cannot find the Server Statistics form.
Error
While server statistics recording was enabled, the AR System server could not find the Server
Statistics form to record an entry. The form might have been deleted or a system failure might
have occurred. To automatically re-created the form, restart the AR System server.
9079
Server Statistics fields can only exist on one form. Delete the duplicate.
Error
The Server Statistics form is defined from a unique combination of AR System reserved fields. If
an attempt is made to create a form that contains these fields while the Server Statistics form
exists, AR System prevents creation of the new form.
9080
Application Statistics fields can only exist on one form. Delete the duplicate.
Error
The Application Statistics form is defined from a unique combination of AR System reserved
fields. If an attempt is made to create a form that contains these fields while the Application
Statistics form exists, AR System prevents creation of the new form.
252
AR System messages

Number
Description
9081
Cannot find the Application Statistics form.
Error
While application statistics recording was enabled, the AR System server could not find the
Application Statistics form to record an entry. The form might have been deleted or a system
failure might have occurred. To automatically re-created the form, restart the AR System server.
9082
Application Statistics fields can only exist on one form. Delete the duplicate.
Error
The Application Statistics Configuration form is defined from a unique combination of

AR System reserved fields. If an attempt is made to create a form that contains these fields while
the Application Statistics Configuration form exists, AR System prevents creation of the new
form.
9083
Cannot find the Application Statistics Configuration form.
Error
The AR System server could not find the Application Statistics Configuration form. The form
might have been deleted, or a system failure might have occurred. To automatically re-created the
form, restart the AR System server.
9084
User is currently connected from another machine.
Error
A user cannot log in to AR System from two computers at the same time.
9085
Host IP address not found.
Error
The AR System server did not find the client IP address in the API call. Contact Customer
Support.
9088
The import file does not hold an application definition.
Error
The import file does not hold an application definition.
9089
User data is corrupted.
Error
User information in an internal database table is damaged or corrupted. Contact Customer

Support.
9090
Cannot change license type of a user to Fixed more than 3 times in 1 week.
Error
An attempt was made to change the license type of a user to fixed more than three times within
one week. Obtain additional fixed licenses if necessary.
9091
User data is corrupted. License deleted.
Error
User information is being updated and information for the user is damaged or corrupted. The user
license was deleted by the system. Contact Customer Support.
9092
The pending file is corrupt.
Error
9093
User is currently connected from another machine.
Error
A user cannot log in to AR System from two computers at the same time. You can terminate the
connection to AR System from the other computer.
9094
Subadministrator group permissions have been removed from the object because the object is
in a deployable application.
Warning
A deployable application cannot have subadministrator group permissions.

9095
Warning
Subadministrator roles permissions have been removed from the object because the object is
not in a deployable application.
An object not in a deployable application cannot have subadministrator role permissions.
9096
Value specified for the Authentication Chaining Mode is outside the valid range of 0 - 4.
Error
This error occurs when the authentication chaining mode parameter is set outside the valid range
in the AR System configuration file. For more information, see the Configuration Guide.
253

Number
Description
9097
Cannot find the Server License form.
Error
The AR System server is unable to locate a form containing the server licenses, which might have
been accidentally removed. The Server License form is automatically created when AR System is
started, so try restarting the server. If the problem still occurs, contact Customer Support. If
restarting fixes the problem, you might need to re-enter the server licenses. If the problem is not
fixed, AR System runs in evaluation mode.
9098
Server License fields can only exist on one form. Delete the duplicate form formName.
Error
The AR System server can contain only one form containing the license fields. Note that the
license form field IDs are in the restricted range. This error can be caused by creating a copy of the
license form.
9100
The command does not occur on the local server.
Error
A remote server execution error occurred during the following operations:
9101
Error
Executing a run process command on the server

Retrieving a list of SQL values specified in the SQL command
The direct SQL and run process commands are valid only as server-side processes, not as clientside.
During import and export operations, the direct SQL and run process commands are valid only
as server-side processes, not as client-side. In certain cases, the processes are exported as clientside processes.
9102
Invalid Run Process or Direct SQL command.
Error
An error occurred when the fully substituted command was returned from the database, for
example, an invalid server-side Run Process command was returned. To continue, verify that the
SQL command or Run Process command works from a command line.
9110
Server does not have a valid host id. Please correct this error to enable licensing for this server.
Error
The host ID you entered does not match the host ID in your license. Make sure that the host ID
you entered is the one you supplied when you requested the license.
9130
Error encountered while executing a Web Service.
Error
This error message is generated by the Web Service plug-in whenever an error occurs during the
execution of a Web Service.
Note: If you receive this error message while upgrading the AR System server, you can ignore it.
During the installation, this message is generated when Java 1.5 or 1.6 is used in both the old
and new versions of the server. When the AR System server is restarted after the upgrade, this
error message will not reappear.
9131
XML Output mapping cannot be empty.
Error
9132
The output default value of element does not match the input value.
Error
In web services, a field in the output mapping is set to a default value, but the incoming value does
not match it.
9141
Conversion of timestamp to a string failed.
Error
9142
Conversion of time value to a string failed.
Error
254
AR System messages

Number
Description
9143
Conversion of a datetime string to timestamp failed.
Error
9144
Upgrade of system form failed because the definition file is not the required version.
Error
At system startup, a system form was not upgraded because the expected version of the
corresponding definition file was not in the expected location. Locate the updated version of the
specified definition file and place it in the specified system form directory.
9145
Upgrade of system form failed because the definition file is missing an expected field.
Error
At system startup, a system form was not upgraded because the expected contents of the
corresponding definition file were not in the file. This is an unexpected system error. Contact
Customer Support.
9150
Error while opening the armonitor lock file.
Error
You cannot run multiple instances of armonitor from the same installation directory. However,
you can run another instance of armonitor from a different installation directory. (UNIX only)
BMC Remedy Mid Tier messages

9200
You have has no access permission to objectName. Check with your administrator.
Error
You tried to perform an operation (for example, opening a form) to which you have no
permissions. Check with your administrator.
9201
Session is invalid or has timed out. Please reload page to log in again.
Error
Your session is no longer available because either the session is invalid, the session timed-out, or
no session data was retrieved.
Log in again to continue.
9202
There are no available attachment fields.
Error
You tried to attach an object to an attachment pool in which no fields are available (all fields might
be in use). Remove any unnecessary attachments if you have permissions, or ask your AR System
administrator to add more attachment fields to the attachment pool.
9203
The form action request failed.
Error
An error occurred in one of the form actions, such as Submit, Search, Modify, or Delete Entry.
9204
Please select an attachment file first.
Error
You tried a display, save, or delete operation but did not first select an attachment.
9205
No help available.
Error
A failure occurred while the system tried to retrieve Help text for this form or field. An associated
error message provides details.
9206
Cannot get the Help text.
Error
A failure occurred while retrieving the list of fields that contain Help text.
9207
Illegal request parameter.
Error
You entered a set of incorrect parameters for this operation, for example, an invalid qualification
statement. This is an unexpected error.
9208
Failed to get config property.
Error
A failure occurred in retrieving a property from the configuration properties file.
255

Number
Description
9209
Cannot find an empty attachment field large enough to hold this attachment.
Error
No field in the attachment pool is large enough to contain this particular file. Contact your
administrator to enlarge the size of the attachment field so that you can attach it later, or try
zipping the file to make it smaller.
9210
The size of the attachment is too large. Maximum size of available slot is number bytes.
Error
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, or try
zipping the file to make it smaller. You can also try to attach to a different attachment field.
9211
You have to specify a file to upload.
Error
You tried to attach a file to an attachment field but did not enter a file name. To complete this
process, enter or select a file.
9212
Failed to add attachment.
Error
The operation of adding an attachment file failed. Check your permissions. If that does not solve
your problem, contact your AR System administrator.
9213
Failed to load the attachment because the request has no incorrect setting.
Error
The attachment file failed to load because the method attribute of the form tag in the servlet
request was set to GET, not POST.
9214
The file does not exist or is empty.
Error
The operation of saving the attachment file to disk failed either because the file does not exist or
because its value is NULL. Make sure the file exists.
9215
Internal error.
Error
This all-purpose error occurs during numerous internal system failures, 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
9216
Display or save attachment failed. Invalid request parameters.
Error
An attempt to view or save an attachment file failed, for example, a new window could not be
opened to display the file. This error occurred because the request parameters for the file were
invalid, because the file path was NULL, or because you did not enter a file path name.
9217
File not found. Either the file requested is not present or the URL supplied is bad.
Error
An attempt to view or save an attachment file failed because the file could not be found on the
web server. Contact your administrator.
9218
Unable to retrieve the file for viewing.
Error
An attempt to view the file failed because, although the system found the file, it could not be sent.
9219
There is no attachment file to delete.
Error
An attempt to delete an attachment file failed because it could not be found on the web server.
Make sure the file exists.
256
AR System messages

Number
Description
9220
There is no attachment file to display.
Error
An attempt to display the attachment file in a new window failed because it could not be found
on the web server. Make sure the file exists.
9221
There is no attachment file to save.
Error
An attempt to save the attachment file to the clients local file system failed because it could not
be found on the web server. Make sure the file exists.
9222
The attachment to be downloaded cannot be found.
Error
An attempt to download the attachment file failed because it could not be found on either the web
server or the AR System server. Make sure the file exists.
9223
Cannot convert AR System query into a Crystal query due to incorrect NULL value usage.
Please see your administrator.
Error
A valid AR System query that uses a $NULL$ value must be in either a

field = $NULL$ or a field != $NULL$ format. Because the AR System query did
not use this format, the attempt to convert it into a Crystal Report web query failed.
9224
Crystal Report does not allow } in fieldname. Remove this character from the fieldname.
Error
An illegal field name not allowed by Crystal Reports was found when an AR System query was
converted into a Crystal Report web query. Rename the AR System field so that it does not use a
close brace, and then retry the conversion.
9225
Cannot convert AR System query into a Crystal query: character value in QualifierInfo object
is NULL. Please see your administrator.
Error
A failure occurred during conversion because the field value is NULL and the field name is
incorrect.
9226
Error
Cannot convert AR System query into a Crystal query: bad enum field type. Please see your
administrator.
Conversion failed because the field for which an enum value was provided is not an enum field
type.
9227
Error
Query conversion failure unknown: queryName. Try again or rewrite your AR System query in
another way.
An attempt to convert the AR System query into a Crystal Report web query failed, but the
specific reason for the failure is unknown. To continue, rewrite the AR System query in a format
more easily understood by the Crystal Report engine.
9228
Unsupported syntax in query conversion. Try to rewrite your AR System query in another way.
Error
An attempt to convert the AR System query into a Crystal Report web query failed because of
unsupported syntax. To continue, rewrite the AR System query in a format more easily
understood by the Crystal Report engine.
9229
Cannot convert AR System query into a Crystal query: invalid data type for enum value. Please
see your administrator.
Error
The conversion failed because an invalid enum string value appeared in the AR System query. To
continue, rewrite the AR System query into a format more easily understood by the Crystal
Report engine.
9230
The report file location is not specified. Please see your administrator.
Error
The native report output failed because the file location was not specified.
257

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

Number
Description
9246
Cannot find report reportName of type reportType for form formName on server serverName.
Please see your administrator.
Error
The report was not retrieved when the Report form was queried for the entry that matches the
parameters in the request. To continue, check the report and report type forms on the server for
valid report names and types.
9247
Cannot find report type reportType. Please see your administrator.
Error
The report type was not retrieved when the Report form was queried for the entry that matches
the parameters in the request. To continue, check the report and report type forms on the server
for valid report names and types.
9248
Internal error: Bad data type for query class field. Please see your administrator.
Error
An invalid data type was applied to the query class field when the query string was converted
from the AR System native format into the report engines format.
9249
Cannot load query converter class classType. Please try again or see your administrator.
Error
The query converter class was not loaded when the query string was converted from the
AR System native format into the report engines format. To continue, verify that the query
converter class is installed in your CLASSPATH.
9250
Invalid report operation. This operation is no longer supported.
Error
During report creation in the Open Window action, an invalid operation was used to post the
report. The only valid operations are run, create, or edit. To continue, fix the action to use a valid
operation.
9251
Bad data type for report operation command field. Please see your administrator.
Error
An inappropriate command was issued for the report because of an invalid data type. To
continue, check the report type form definition.
9252
Report operation command is empty. Please see your administrator.
Error
The report operation command does not have a command specified for this report type.
9253
Form with ID IDNumber cannot be found on ARServer serverName. Please see your
administrator.
Error
A failure occurred because the AR System server failed to retrieve the form with the specified ID
needed to create the report.
9254
Error
Mid Tier does not have permission to create directory directoryName: directoryName. Please
see your administrator.
Permissions problems occurred when a report directory was created. To continue, verify that the
mid tier has write access to this directory.
9255
Cannot start query converter class className. Please see your administrator.
Error
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 engines format. To continue, verify that the
query converter class implements the report query converter interface.
9256
Unable to start query conversion: stringContents. Please see your administrator.
Error
An initial failure occurred when the original query string was converted into a QualifierInfo
structure that the report engines format can interpret. To continue, check that the query converter
class implements the report query converter interface.
For information about the QualifierInfo class, see the AR System Java API documentation.
9257
Problem opening output stream: stringContents Please see your administrator.
Error
An attempt to create the report definition file from the Message Catalog failed.
259

Number
Description
9259
Object(s) cannot be found on AR System server.
Error
This object (for example, a schema, active link, or container) was not in the server cache. To
continue, verify that the object exists on AR System server.
9260
Report location is missing from report settings configuration page. Please see your
administrator.
Error
The location of the Crystal Reports Server XI engine is not specified in the BMC Remedy Mid Tier
Configuration Tool.
9261
Error generating Status History information.
Error
The XML string containing the Status History field information was not created. Status history is
displayed for the web in a separate window.
9262
Submit failed.
Error
The Submit operation failed while a request was being created. A Submit failure has many
possible causes, for example, a required field is blank. (In that case, enter a value for the required
field, and retry the Submit operation.)
9263
Modify failed.
Error
The Modify operation failed when updating an AR System request. Possible causes for this error
include, for example, a simultaneous modification by another user or a failure in workflow.
9264
You have no access permission to the form formName.
Error
You entered an incorrect user name or tried to access an AR System form that you have no
permissions to. Try reentering your user name, or check your permissions to continue.
9265
You have no access permission to the field fieldName.
Error
You tried to access a field that you have no permissions to. Check your permissions to continue.
9266
Please select an entry first.
Error
An attempt to display the status history in a new window failed because no entry was selected.
The request was therefore ignored.
9267
Required parameter(s) missing for form view creation: parameterName.
Error
Creation of the form view failed because the required parameters contain either no value or a
NULL value. Required parameters include the following items:
Form (or form alias)

Server name
9268
Unable to generate the JSP page.
Error
An attempt to retrieve the path of the JSP page that represents the form failed. The JSP path
could not be constructed because some of the following data is missing:
9269
Error
Form
View
Application
Locale
Unable to perform query because results list field not found. Please inform your AR System
administrator.
The query failed because the results list in the form could not be found. This error message also
appears when you are unable to use an Open Window active link action to drill down to a
record in a table field.
260
AR System messages

Number
Description
9270
Entry with ID IDNumber does not exist in database.
Error
The request retrieval failed because the entry ID does not exist in the database.
9271
You have entered an improperly formatted value for the field.
Error
An attempt to validate the values for this field so that it can be properly formatted failed.
9272
Value does not fall within the limits specified for the field.
Error
An attempt to validate the values for this field failed because they are out of the acceptable
minimum and maximum range limits defined by the administrator.
9273
This is a display-only field.
Error
An attempt to add the field to the query bar HTML input element failed because it is a displayonly field. Only fields holding actual database values, such as an integer field, are included.
9275
Status History operation valid only in modify mode.
Error
An attempt to display the status history failed because it is valid only in modify mode, not for
submit or query.
9276
There is no valid web view for this form.
Error
You tried to drill down on a table or to display, by using an Open Window action, a form that does
not have a web view defined. This could be a form on a 5.x or later environment in which no web
view was defined or a form on a pre-5.x AR System server. The system cannot open a form that
does not have a valid web view on the web.
If the server is a 5.x or later server, add a web view for the form, and you can then open it. If the
server is pre-5.x, upgrade the server to 5.x or later and then create a web view for the form before
you can open it.
9277
Found more entries than expected during workflow processing.
Error
A failure occurred because multiple matches were found in the form during a Set Fields or Push
Fields action. All workflow processing is stopped. To continue, configure the workflow in BMC
Remedy Developer Studio for a different multiple match response in AR System, for example, Set
Field to $NULL$, or Use First Matching Request.
9278
No item matches active link conditions; this operation has been defined so that no match
generates an error.
Error
A failure occurred because no matches were found in the form during a Set Fields or Push Fields
action. All workflow processing is stopped. To continue, configure the workflow in BMC Remedy
Developer Studio for a different multiple match response in AR System, for example, Set Field to
$NULL$.
9280
Error
A failure occurred because the name of the server serverName is not in the list of valid mid tier
servers - serverName.
A failure occurred because the name of the server is not in the list of valid mid tier servers. To
continue, verify that a valid server exists.
9281
A failure occurred in the process used by the Set Fields action.
Error
A failure occurred in the process used by the Set Fields action. No results were returned. To
continue, verify that the process works independently of the Set Fields action.
9282
Failed to create the following menu: menuName.
Error
An attempt to expand the query string for a dynamic menu, such as a search menu, failed. The
server could not parse the query correctly.
261

Number
Description
9283
An internal error has occurred during workflow processing: errorMessageString.
Error
An internal system failure occurred during the execution of this active link. This error is not due,
however, to a more common multiple match or no match error.
9289
Invalid AR System Server Name.
Error
A failure occurred during login because you entered an invalid server name.
9291
Not a valid administrator password on the server - serverName. Please add/modify the
password for the server in configuration page.
Error
The mid tier administrator password you specified is not recognized. To continue, try re-entering
your password or contact your AR System administrator for assistance.
9292
Not a valid administrator user on the server - serverName.
Error
A failure occurred during login because the system does not recognize this user name as a valid
administrator. To continue, enter a different login name.
9293
Cannot convert AR System query into a Crystal query: you cannot use operatorInQuery to
evaluate null. Please rewrite your query.
Error
An AR System query failed to convert into a Crystal report query. The Crystal engine does not
recognize this method for checking NULL values. Rewrite the query to use operators in the
AR System query that the Crystal query understands, for example, field = $NULL$. You
can only test for = $NULL$ or != $NULL$.
9294
Error
Your query has returned too many results. Narrow your query criteria, specify a smaller
maximum number of queries to return, or ask your administrator to specify a smaller chunk
size for the table or results list.
You are running out of available memory because the query returned too many results. To
continue, rewrite your query to return fewer requests.
9295
Incorrect login parameters. Web page, user, and/or server name(s) must be provided.
Error
A login failure occurred because you did not enter certain parameters, for example, form name or
user name. To continue, enter the missing parameters.
9296
No matches were found for your qualification.
Error
No matches were found for your qualification. However, processing continues to display the zero
matches label in the results list header.
To continue, refine the qualification to make sure that it returns at least one matching request.
Note: This message is returned by web clients. In the same situation, similar messages are returned
by web services and API programs (see error message 302) and BMC Remedy User (see error
message 1200).
9297
The query is too complex for the report engine.
Error
An attempt to convert an AR System query into a Crystal Report query failed because Crystal
Reports limits the number of boolean operators that can be used in a query.
You also see this message if a list of selected requests contains too many nonconsecutive entry IDs.
In this case, the converted query is replaced by the original AR System query string.
9298
Unable to convert. Your query is too complex. The default results list query will be used.
Error
The AR System query format failed to convert into the report engines format because the
converted query was too complex. The converted query is replaced by the original AR System
query string.
262
AR System messages

Number
Description
9299
This record has been updated by another user since you retrieved it. Saving your changes will
overwrite the changes made by that user. Do you want to save your changes?
Warning
A conflict exists because another user and you are retrieving the same request. To continue,
perform one of the following tasks:
9300
Error
Contact the other user (if you know who she is) to avoid overwriting her changes.
Cancel your changes.
Requery, and then modify.
Save your changes only if you are sure your changes will not destroy important information.
The Run Process specified in the active link action failed because this Run Process command
is not supported.
The Run Process active link action failed because this Run Process command is not supported. To
continue, use a different Run Process command.
9301
The report file cannot be retrieved from the server to the mid tier: fileName.
Error
The report file cannot be retrieved from the server to the mid tier server.
9302
Throw Error - 9302.
Error
This generic message indicates an error occurred.
9303
Unable to retrieve a user from the user pool on this old version of AR System.
Error
An attempt to retrieve a user from the pool of available users failed because a user pool does not
work with this version of AR System.
9304
Unable to retrieve the report file.
Error
An attempt to retrieve the report file failed 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.
9305
Unable to translate the group names in the Group List or Assignee Group Field into group IDs.
Warning
The qualification failed because the system was unsuccessful in translating the group names into
group IDs.
9306
Attempt to divide by zero (0) in arithmetic operation.
Error
The qualification failed because of an illegal mathematical operation. A NULL value is returned.
To continue, rewrite the query so that you do not divide by zero.
9307
Date is out of allowed range of 1970 to 2037 for web client.
Error
You entered a value for a date/time field that does not fall in the supported range. To continue,
enter a date in the range between 1970 to 2037.
9308
Page has been updated. Please Refresh to get the updated page.
Error
Your form is outdated. The form was recently updated in memory. To continue, click the Refresh
button on the page.
9309
Show Status History action ignored. Status History field does not exist in form.
Error
The status history failed to appear in a new window because the Status History field is missing
from the form. The request to display the status history is ignored.
9310
Invalid time format. Please enter time in this format:
Error
You entered the wrong time format into the Calendar popup window.
9325
Error
You did not enter a valid currency value on a currency field. For example, you entered 1,00 USD.
263

Number
Description
9326
You have entered an invalid currency type.
Error
The specified currency value is a not an allowable currency type. Contact your AR System
administrator.
9327
You have entered an invalid currency code for a currency field. Using previous valid code.
Error
You did not enter an allowable currency code on a currency field. The mid tier returns the field
results based on the last previous valid currency code.
9329
The location does not have the required parameter server or webService.
Error
When details about the web service request were extracted from the input document, this error
message was returned because the namespace was incorrectly formatted. The location must
include the server and the web service parameters.
9330
No Web Service named webServiceName exists in server serverName.
Error
When a web service request was processed on the mid tier, this error message was returned
because no such web service exists on the server.
9331
No operation named operationName exists in web service webServiceName.
Error
When a web service request was processed on the mid tier, this error message was returned
because no such operation was found in the web service.
9332
Invalid operation type operationType specified on web service container.
Error
The mid tier could not make the necessary API call because an invalid operation type was
specified for the web service.
9334
The XPATH expression xpathExpression is not found in input mapping.
Error
A string value could not be substituted for the XPATH expression because the mid tier server
could not find the corresponding mapping node.
9335
Invalid Date Time Value: dateTimeString.
Error
The mid tier could not parse the XML date/time string.
9336
Invalid URL for accessing WSDL: requested_URL.
Error
The WSDLServlet servlet could not generate the WSDL for a requested web service because the
URL was invalid.
9337
No web service definition found: webServiceName.
Error
A web service was requested, but the mid tier could not locate the web service definition.
9338
No authentication information found: serverName.
Error
Authentication information is not supplied in the web service request, and anonymous user
information is not specified in the BMC Remedy Mid Tier Configuration Tool.
9339
Data types of the two operands do not match.
Error
In an active link arithmetic operation, the two operands cannot be made to match, or the
arithmetic operation is not supported. For example, you tried to add two currency fields that have
different currency codes, such as USD and CAD, and no matching functional currencies exist. Or
you subtract Decimal1 - Decimal2 = Character. If the target field is a character, only addition is
supported (string concatenation).
9341
No Preference server or Home Page Server specified. Home Page needs a server.
Error
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. 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.
264
AR System messages

Number
Description
9342
No servers configured in Mid Tier Configuration. Home Page needs a configured server.
Error
No AR System servers are configured in the BMC Remedy Mid Tier Configuration Tool. Contact
9343
No Preference form or ServerSetting Home Page form specified. Home Page needs a form.
Error
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.
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.
9344
Cannot connect to server serverName to access Home Page.
Error
Unable to connect to the server that contains the Home Page form. This can occur when the server
is down or when the network is too slow (leading to a time-out). Contact your AR System
administrator.
9345
Your user name or password was not accepted by any AR System server configured in the BMC
Remedy Mid Tier Configuration Tool.
Error
Your user name or password was not accepted by any AR System server configured in the BMC
Remedy Mid Tier Configuration Tool. Contact your AR System administrator.
9350
Network protocol/data error when performing data operation. Please contact administrator.
Error
An internal error occurred because parameters passed to the back channel were incorrect.
9351
Unable to setup data connection, which is preventing the application from working correctly.
Error
An internal error occurred during a back channel request from the browser to the mid tier server.
9352
A form definition has been changed, so unable to retrieve data. Please contact administrator.
Error
The definition of a form that users have loaded was changed in such a way that a table on the form
cannot be refreshed.
9353
The operation cannot be completed because you have logged out.
Error
A user who is logging out tried to make requests to the mid tier. 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.
9354
No compatible (standard or web fixed) view for the requested form can be found - unable to
display form.
Error
The mid tier could not find a view to display for the specified form. This can occur if a form
contains only relative views because relative views are no longer supported by the mid tier.
9355
The requested form formName cannot be found.
Error
The form specified in the URL does not exist.
9356
Unsupported locale locale.
Error
A user tried to load a form on the mid tier in an unsupported locale. The locale is specified either
in the languages selection in the browser or in the user preferences. For information about
supported locales, see the BMC Remedy Mid Tier Guide.
9357
Unsupported timezone timeZone.
Error
A user tried to load a form on the mid tier in an unsupported time zone. The time zone is
determined at login time or from the user preferences.
9358
Application does not exist on server - serverName.
Error
The application specified in the URL does not exist.
265

Number
Description
9359
Server and form names are required in the URL.
Error
The view form servlet requires the server and form parameters to be in the URL (other parameters
are optional). If these parameters are missing this error occurs.
9360
The size of the current global fields exceeded the allowable 3.5 KB size.
Error
The mid tier implementation of global fields limits the amount of data that can be stored in all
global fields to about 3.5 KB. To allow more storage, install a supported version of Flash Player.
9361
A current session exists for a different user - userName. Log off the existing session and try
again.
Error
The view form servlet was used with user name and password parameters that differ from the
ones used to create the current session.
9362
Error
Aliases are not supported by the AR System 6.3 and later. Use form, view, or app parameters
instead.
Aliases are not supported by the AR System 6.3 and later mid tier so the alias parameters to the
view form servlet are no longer supported.
9363
The action failed because the mid tier is unavailable or could not be contacted.
Error
The action failed because the mid tier is unavailable or could not be contacted. This error could
also occur if the action was canceled by the user while it was being performed.
9364
One or more items match active link conditions; this operation has been defined so that any
match generates an error.
Error
Used by the Push Fields action when the administrator configures it to return an error when
multiple matches are found. On the If Action page, the If Any Requests Match field has Display
Any Match Error selected.
9365
No rows have been selected for ModifyAll.
Error
The modify all action requires that at least one row is selected in the results list. Select one or more
entries in the results list and try again.
9366
The Run Process active link action failed because this Run Process command was used
incorrectly.
Error
The Run Process active link action failed because this Run Process command was used incorrectly,
such as using a Run Process command that does not return a value in a Set Fields action.
9367
Data types are not appropriate for relational operation.
Error
The data types of the fields used in a relational operation are not consistent with the operations
allowed for that operation. See the Workflow Objects Guide for information about the allowed data
types of operations.
9368
Invalid data type in active link.
Error
An AR System API function call was used with an invalid data type.
9369
Function not supported.
Error
AR System functions (used in assignments) such as CONVERT, ENCRYPT, and DECRYPT are
supported only in filter workflow and not in active link workflow.
9370
The guide guideName is invalid or not owned by any form.
Error
The guide or the primary form for the guide could not be determined. Dynamic workflow allows
an active link guide to be named at run time. If the guide name does not exist on the server, or the
guide does not have a primary form, this error is generated.
266
AR System messages

Number
Description
9371
The definition for the guide guideName cannot be found and might be missing from the AR
System server.
Error
The guide specified (via dynamic workflow) is invalid. With dynamic workflow you can specify
guide names from workflow instead of in BMC Remedy Developer Studio. The definition for the
guide specified cannot be found and might be missing from the AR System server.
9372
The specified menu is invalid.
Error
The specified menu is invalid. This error occurs if the browser client requests a nonexistent menu.
This could be due to an active link change fields action that changed the menu for a character field.
9373
Error
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. Change the value to a legal real value, and retry the operation.
9374
Error
The value was entered in a field with a data type of decimal. The value is not a legal decimal value.
Change the value to a legal decimal value, and retry the operation.
9375
You entered a nondigit character for a numeric field.
Error
A numeric field contains a nondigit value. You can specify digits only for integer (numeric) fields.
Change the value to a legal integer value, and retry the operation.
9376
Format of date or time value is not recognized.
Error
The format of a time value is not recognized. You can omit the time portion of a time stamp and
include only the date, or you can omit the date and include only the time. The portion omitted
defaults to an appropriate value. However, the format of the specified portion of time must match
the rules for time stamps. Fix the format of the line, and perform the search again.
9377
Time is out of allowed range of number and number.
Error
AR System cannot process a time that is out of range. Try again, using a time within the allowed
range.
9378
The query matched more than the maximum number of entries specified for retrieval.
Warning
The retrieval included a search that selected more than the maximum number of items allowed
by the client or server. The call returned the number of entries specified as the maximum. Narrow
your search criteria or change the limit in user preferences.
To change the local setting in BMC Remedy User, choose Tools > Options > Behaviors, and modify
the settings for Limit Number of Items Returned. Only an administrator can change the server
settings.
9379
The time entered is invalid. Therefore, the popup will be initialized to the current time.
Warning
Click the icon to the right of the field to select the desired time.
9380
The date entered is invalid. Therefore, the popup will be initialized to the current date.
Warning
Click the icon to the right of the field to select the desired date.
9381
No such user exists.
Error
A user with the supplied login ID cannot be found on any AR System server.
9382
Error
The supplied password is invalid.
9383
No forms found containing field ID: IDNumber.
Error
267

Number
Description
9384
Multiple forms contain field ID: IDNumber.
Error
9385
Unable to contact the web server to the complete action.
Error
9386
Security Exception!! Possible insecure call issued. Please try opening the report again.
Error
A request was sent to open an unencrypted Crystal report.
9387
Request timeout. Please try opening the report again.
Error
A request to open a Crystal report through the web timed out.
9388
Error
An authentication failure occurred, such as supplying the wrong administrator password on the
configuration page for the AR System server.
9389
The length of server name or form name exceeds the allowed length.
Error
The length of server name or form name passed to the viewformservlet is longer than the allowed
length. The maximum server name length is 64 characters and maximum form name length is 254
characters.
9390
There is either no definition or the user user does not have permission for keys keys for the
module module in the server serverName.
Error
The requested plug-in definition does not exist in the Data Visualization Definition form, or the
user does not have correct permissions to access that data.
9391
Error
The requested plug-in moduleName does not exist in the list of Data Visualization Module
Server(s) in the BMC Remedy Mid Tier Configuration Tool.
The requested plug-in does not exist in the list of plug-in servers in the BMC Remedy Mid Tier
Configuration Tool.
9392
Error
Could not create the required directory directoryName to download module module from
server serverName.
The mid tier should be able to create a directory so that it can download the plug-in information.
If it cannot create a directory, this error occurs.
9393
There is no jar file for the module module in the server serverName.
Error
The plug-in JAR file is missing for a given data visualization module in the Data Visualization
Module form.
9394
Could not download the module jar file for module module from the server serverName. Please
see the log file for further details.
Error
The mid tier cannot download a JAR file for a particular data visualization plug-in in a server.
9395
Unable to find the module module in the mid-tier plug-ins directory.
Error
Flashboards and reports are built on mid-tier local data visualization modules. This error occurs
if a request is made for these modules and they are unavailable in the local plug-ins directory.
9396
Unable to find the properties file fileName in the mid-tier plug-ins directory.
Error
The available local plug-ins directory should have a details.txt file that contains the
information of these modules. If the file is missing, this error occurs.
9397
Unable to find the JAR file fileName in the mid-tier plug-ins directory.
Error
A JAR file is missing in the local plug-ins directory.
268
AR System messages

Number
Description
9398
The module class class does not match the module module from server serverName.
Error
The entry class specified for the module does not implement the plug-in interface provided in the
GraphPlugin.jar file.
9399
The module class class for the module module from server serverName is not found in the jar
file.
Error
The entry class specified for a module was not implemented.

9400
Error
The module class class for the module module from server serverName does not have the
required no arg constructor.
The plug-in container in the mid tier cannot instantiate the specified entry class for a module.
9401
Error
The module class class for the module module from server serverName made an illegal access
and cannot be instantiated.
The entry class was accessed incorrectly.
9402
The server serverName is not localized or not contactable.
Error
The localized version of a given string is unavailable, or the string is not localized.
9403
The module module from the server serverName does not have the privileges to perform the
call.
Error
The administrator login option was not selected when module information was created in the
Data Visualization Module form, but the module requested the administrator anyway.
9421
Unable to reach Mid-Tier. If you are on SSO, please re-login to SSO service.
Error
9422
Error
You have exceeded the maximum allowable number of saved searches for this form. You need
to delete number searches using Manage My Searches dialog before you can save new search.
9423
Cross Site Scripting not allowed.
Error
9424
Required field (without a default) not specified.
Error
9425
The administrator has set access for administrator users only. Please retry your operation later.
Error
9426
An error had occurred. Please see your administrator.
Error
This generic message indicates an error occurred.
9500
Nothing got deployed since the deployed Application is up-to-date. Nothing is updated.
Warning
Nothing was changed, so nothing was deployed.
9501
The starting active link activeLinkName is missing from the Entry Point Guide on server
serverName.
Warning
The Entry Point Guide has no starting active link. Contact your AR System administrator.
9502
The form contains no fields: formName.
Warning
The form contains no fields.
9503
Every view that needs to be deployed should have an alias.
Warning
All forms and views must have an alias name specified to be deployed on the Web.
269

Number
Description
9504
Request requestID was successfully created.
Note
AR System server messages
9701
The Currency form does not contain the correct number of required currency fields.
Error
The Currency form does not contain the correct number of required currency fields.
9710
Bulk entry transaction already in progress.
Error
An attempt was made to initiate a bulk entry transaction when one was in progress.
9711
No bulk entry transaction is in progress.
Error
An attempt was made to end a bulk entry transaction when no transaction was in progress.
9712
Invalid action type for end of bulk entry transaction.
Error
The action type supplied for ending a bulk entry transaction was not one of the acceptable
options. See the C API Reference for the list of acceptable values.
9713
The attempted bulk entry transaction failed due to an error in one of the individual operations.
Error
The attempted bulk entry transaction failed due to an error in one of the individual operations.
Check the return list for more detailed information about the individual operation failure.
9720
Error
The updating of object relationship data through the AR System Object Relationships form is
not allowed.
9730
The updating of metadata through the Metadata view forms is not allowed.
Error
9735
Invalid full text scan information in form object properties.
Error
An invalid combination of form object properties was provided for a form's full text scan
information. Verify that interval or time properties were provided, but not both.
9750
Error encountered while loading the shared library.
Error
The AR System Server could not load a shared extension library, such as the CMDB engine.
Shared libraries are registered for loading in the ar.conf file. The server functions, but any
functionality associated with the shared library is unavailable. The error message is written to the
arerror.log file.
Check the library paths specified in ar.conf. Make sure that the shared library and all
dependent libraries are specified correctly, and restart the server.
9751
The shared library identification is invalid or duplicate.
Error
When a shared extension library is loaded, the AR System server invokes callback routines to
identify the library to the server. This error occurs when the ar.conf file contains multiple
registry entries for the same library or when the identification callback routine returns an
error.The library is then unloaded from memory. The server continues to function, but any
functionality associated with the shared library is unavailable. The error message is logged in the
arerror.log file.
9752
The shared library does not provide an Identification routine implementation.
Error
identify the library to the server. This error occurs when the server invokes a routine that is not
implemented by the shared library. The library is then unloaded from memory. The server
continues to function, but any functionality associated with the shared library is unavailable. The
error message is logged in the arerror.log file.
270
AR System messages

Number
Description
9753
The shared library is not loaded because it violates one of the prerequisites.
Error
identify the library to the server. This error occurs when the shared library does not implement a
required routine. The library is then unloaded from memory. The server continues to function, but
any functionality associated with the shared library is unavailable. The error message is logged in
the arerror.log file.
9754
The shared library has an invalid RPC program number.
Error
The server loads a configuration management database (CMDB) shared library and assigns it a
remote procedure call (RPC) identification number. The RPC number is returned by the library
through a callback routine invoked by the server. In this case, the routine returned an invalid RPC
value. To fix the problem, check the implementation of the callback routine and make any
necessary corrections.
9755
Error encountered while initializing (Initialization routine) the shared library.
Error
On server startup, an initialization routine runs for all shared extension libraries that are loaded.
The initialization routine returned an error, and the shared library was unloaded from memory.
The server functions, but any functionality associated with the shared library is unavailable. To
resolve the problem, check the implementation of the routine and make any necessary corrections.
9756
This version of internal API is not supported by the server.
Error
This is an internal error. A shared library tried to use an internal API exposed by AR Server, but
the API version is incompatible with the AR Server version.
9757
Invalid call made from within filter context.
Error
9758
Invalid filter processing call made outside of filter context.
Error
An internal error occurred because a filter workflow extension library was called by a filter action
that does not have a filter context. Identify the user activity and workflow associated with the
error, and then report it to Customer Support.
9759
Extension library called with no filter context.
Error
An extension library was called by a filter action that did not have a filter context. This is an
internal error. Identify the user activity and workflow associated with the error, and then report
it to Customer Support.
9760
Workflow API function called from improper filter phase.
Error
Error in the BMC Atrium CMDB extension library API. Contact Customer Support.
9761
Unrecognized internal workflow API function.
Error
Error in the BMC Atrium CMDB extension library API. Contact Customer Support.
9781
Role name was not found. Verify that the role name is valid.
Error
The server tried to resolve a role name to a role ID, but the role does not exist. Role names can be
specified by a user or by workflow. Check the associated role name and make sure it is valid.
9782
Invalid role format: %s.
Error
9800
The reserved fields already exist on this email form.
Error
Reserved fields are being created on the Email form that already exist on the form with the same
field IDs.
271

Number
Description
9801
Couldnt locate the Email form.
Error
When an email message is sent to a specified user, this error message is returned if the server
cannot find the Email Message, Email Attachments, or Email Association forms.
9802
Email attachment mapping is invalid.
Error
An internal system error occurred. Contact Customer Support.
9803
Cannot locate mailbox.
Error
Either no default mailbox is specified for an email notification, or the specified mailbox does not
exist.
9804
A required form for Email is missing. Server will attempt to import the form in place. Please
verify the form gets imported or import it manually to ensure the Email Engine will work
properly. formName.
Error
The identified form is missing and must be imported if necessary.

9820
Error opening license audit file.
Error
The AR System server cannot open the file containing the license audit data. Each time an audit
is run, AR System attempts to re-create the file if it is not found or inaccessible. This error can be
caused by the AR System server not having read/write permission to the server log directory.
9821
Error reading license audit file.
Error
The AR System server received an error when attempting to read the license audit data file. This
can be caused by the AR System server not having read/write permission to the server log
directory.
9822
Error writing license audit file.
Error
The AR System server received an error when attempting to write to the license audit data file.
This error can be caused by the AR System server not having read/write permission to the server
log directory.
9823
Corrupted license audit file.
Error
The data in the license audit file is corrupt. The existing file is renamed and a new audit data file
is created.
9824
Unable to initialize license audit mutex.
Error
An internal error occurred during the AR System server start up. Try restarting AR System. If
restarting AR System does not fix the problem, contact Customer Support.
9850
You do not have application write license.
Error
Either this user does not have an application write license for the application, or a floating license
is unavailable for assigning. Contact your AR System administrator.
9851
No additional application fixed license for this type of license is available: licenseType.
Error
No additional application fixed license for this type of license is available for assigning. Get more
licenses if necessary.
9852
An Application fixed license of this type has been assigned to more users than the number of
valid licenses you have: licenseType.
Warning
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.
9853
The following application fixed licenses have been returned to the system: licenseType.
Note
A fixed license was returned to the system and is now available for assigning.
272
AR System messages

Number
Description
9854
The following application fixed licenses have been granted: licenseType.
Note
A fixed license was assigned.
9855
The following write application token has become available and has been allocated to you
access has been upgraded to write access.
Note
A floating license was assigned for your use.

9856
There is no such application user fixed license on the system: licenseType.
Error
Either license information was entered incorrectly, or the fixed license does not exist. Contact
Customer Support.
9857
Application or Form already Licensable. Cannot modify or unlicense the Application or Form.
Error
You cannot make an application license less restrictive. Contact Customer Support.
9858
The application is not licensed.
Error
Make sure that the application is a deployable application, not a local application. For information
about local and deployable applications, see the Form and Application Objects Guide.
9859
The license information provided for this form does not match that in owning application.
Error
9860
The application license format is not valid.
Error
License information might be entered incorrectly. Make sure that license names end with User
Fixed or User Floating and that each license for a user is separated by a semicolon (;).
9861
The form is missing application licensing information.
Error
9862
No free application user floating write license are available. Currently accessing the
application form in read-only mode. License will upgrade when one is available.
Warning
You have read-only access to the application. Try later to see whether a floating license becomes
available, or contact your AR System administrator.
9863
No license property can be set while creating a form.
Warning
License properties for a form cannot be set when a form is created. You can set the license
properties after the form is created.
9864
The Application or the Form cannot be made licensable. Only deployable applications can be
made licensable. Also, Forms have to belong to deployable applications to be made licensable.
Error
A local application cannot be made licensable. For information about local and deployable
applications, see the Form and Application Objects Guide.
9870
Escalations must be disabled.
Error
9871
Execution terminated by workflow debugger.
Error
A filter or escalation execution was terminated with a forced error from the workflow debugger.
9872
Error in field value list (bad ID or datatype).
Error
Adding a field or changing the data type is not permitted when setting the field value list during
workflow debugging.
273

Number
Description
9873
Command not valid at this time.
Error
The workflow debugger command was issued at an incorrect time. For example, this error would
result when you try to view the field-value list when the debug thread is idle (workflow is not
executing) because no field-value list exists at that time. Issue the command when workflow is
executing.
9874
Invalid Breakpoint ID.
Error
Breakpoints are identified by a numeric ID. This error typically indicates that the breakpoint
specified in a command does not exist. For example, if you have only breakpoints 1, 2 and 3, and
you issue a command to clear breakpoint 4, this message is issued. To see the list of valid
breakpoints (including ID), issue the List Breakpoints or List Remote Breakpoints command.
9900
External Logging Note.
Note
9901
External Logging Error.
Error
9902
External Logging Not Handled.
Error
9905
Internal API call failed.
Error
An internal system error occurred. Retry the operation.
9906
Size of memory allocation for result exceeded configured limit on the server.
Error
9907
Illegal command line parameter.
Error
A program was called with a command-line parameter that cannot be used; it might not be legal
for this program or it might not be legal in combination with other parameters. Check the
documentation to verify that your parameters are legal and can be used together.
9908
Illegal operation for placeholder schema.
Error
9910
Admin operations are suspended because the number of open caches is at the configured limit.
Warning
9911
Admin operations are suspended because the number of open caches is at the configured limit.
Error
9922
Audit not possible on Dialog or Audit forms.
Error
You cannot audit the specified form types.
9923
Join form Audit cannot be enabled unless the base forms have audit enabled.
Error
Enable auditing for the base forms and retry the operation.
9924
The same Log Key cannot be applied to more than one field in a schema.
Error
Specify a unique log key for each field.
9925
There are incorrect number of reserved fields in the Archive or Audit form.
Error
Choose one of the following options to correct the problem:
274
Make sure that the main form is linked to the correct archive/audit form.
Set archive/audit to none in the main form, correct the problem, and enable archive/audit
again.
Choose a new name for the archive/audit form, and AR System automatically creates a form.
AR System messages

Number
Description
9926
The Archive or Audit form is already in use by another form.
Error
To correct the problem, see error message 9925.
9927
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.
Error

9928
The data types of the data fields in the Source and Archive/Audit form do not match.
Error
9929
Field is missing from the Archive/Audit form.
Error
9930
Cannot import only Audit form. Either the Main form by itself or both Main and Audit can be
imported.
Warning
You cannot import only the source form. You can import the main form alone or the main form
and the corresponding archive/audit form.
9931
Qualification cannot contain EXTERNAL references.
Error
The audit qualification cannot have external references.
9932
Archive or Audit form not found. Archive or Audit will be disabled.
Warning
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 on the AR System server. For example, if you are importing a form
named form_audit that has audit enabled, and a form with the same name is not on the
AR System server, audit is disabled on the imported form.
9933
You cannot disable the audit on this form until you disable the audit on dependent form.
Error
The form for which you are disabling audit has a dependent form on which audit is enabled. For
example, if you have a join form that has audit enabled, audit on the base forms cannot be
disabled. First disable audit on the dependent (join) forms, and then disable audit on the base
forms.
9934
You cannot enable the audit on this form until you enable the audit on base forms.
Error
The form for which you are enabling audit has a base form on which audit is disabled. For
example, if you have a base form that has audit disabled, audit on the dependent forms cannot be
enabled. First enable audit on the base forms, and then enable audit on the dependent forms.
9935
Fields in the range 5000 to 5999 are reserved for Audit use.
Error
275

Number
Description
9940
Time-out during plug-in callthe request has been accepted by the plug-in server, but the
plug-in has not yet responded.
Error
The plug-in did not respond to a call within the time period specified in the AR System server
configuration file (ar.conf on UNIX; ar.cfg on Windows). To determine the cause of the error,
check the AR System servers API log (by default, arapi.log). To avoid such errors in the future:
Increase the plug-in time-out settings in the AR System server configuration file:
Filter-Api-TimeoutSpecifies the time in which AR filter plug-in servers must respond
to a call before an error is returned. The default is 40 seconds, but it can be as long as 300
seconds (5 minutes).
Server-Plugin-Default-TimeoutSpecifies the time in which ARDBC plug-in servers
must respond to a call before an error is returned. The default is 60 seconds, but it can be as
long as 600 seconds (10 minutes).
For more information, see the Configuration Guide, ar.conf (ar.cfg), page 348.
Make sure the AR System server has a sufficient number of server threads. The default number
is often inadequate. For example, some plug-ins loop back to the server twice during a call,
requiring two server threads for one call. The threads also must often support concurrent plugin calls. In addition, if you increase the plug-in call time-out settings, the length of time a server
thread is held for a plug-in call might increase. To increase the number of threads dedicated to
plug-ins, use the Plugin-ARDBC-Threads, Plugin-AREA-Threads, and PluginFilter-API-Threads options in the AR System server configuration file (see the
Configuration Guide).
Do not run the AR System server in development cache mode (Cache-Mode: 1). In this mode,
calls are often blocked for long periods of time. See the Configuration Guide, Configuring a
servers cache mode, page 168.
9950
The input provided for calculating the next recurrence is bad.
Error
An internal error occurred. Check the arerror.log file.
9951
The date calculated is invalid or a bad date format. Please make sure the date format is in the
ARServers date format and separator.
Error
Check the date and make any necessary corrections.

9952
Type of recurrence requested is invalid.
Error
Valid recurrence types are Yearly, Monthly, Weekly, Daily, and Special Dates.
9953
Month of year selected is invalid.
Error
Enter a month value between 1 and 12.
9954
Week of Month selected is invalid.
Error
Enter a week value from 1 to 5.
9955
Day of Month selected is invalid.
Error
Enter a day value from 1 to 31.
9956
Hours of day selected is invalid.
Error
Each element in the HoursOfDay array cannot be greater than 1.
9957
Day of the week selected is invalid.
Error
Each element in the daysOfWeek array cannot be greater than 1.
9958
The date is out of range of the 1970 - 2038 allowed by the OS.
Error
The year of the calculated recurrence date is outside of the range allowed by the operating system.
276
AR System messages

Number
Description
9959
The recurrence date is not valid for this month. Skipping to next recurrence.
Warning
Using the recurrence provided, the date obtained is not valid for this month. The next recurring
value will be tried.
9960
Recurrence of type Specific Dates has no dates.
Error
Make sure the dates are in the servers date and separator format. Separate dates with semicolons,
for example, 12/24/07;12/25/07.
9971
Cannot find respective System Log Form.
Error
The log form is missing or corrupted. Import the LogForm*.def file from the C:\Program
Files\BMC Software\AR System\Arserver\systemforms\en folder, using the
overwrite option if the form exists but is corrupted.
9972
Error
The fields reserved for respective System Log Forms can exist only on one form. Delete the
duplicate.
9973
The Application_Properties fields can exist only on one form. Delete the duplicate.
Error
9974
The Application_Interface fields can exist only on one form. Delete the duplicate.
Error
9975
There is no recursion qualifier specified in the Recursive Query.
Error
The ARGetListEntryWithMultiSchemaFields function tried to perform a recursive query,

but it failed because the recursion qualifier (recursionQual) was not specified.
For more information, see these topics in the C API Reference:
ARGetListEntryWithMultiSchemaFields function
ARMultiSchemaQueryFromList structure
ARMultiSchemaRecursiveQueryStruct structure
9976
Wrong schema type specified for a query form list item in the Recursive Query.
Error

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. All the items
in the list should be of that type.
9977
Can not specify more than one Recursive Query.
Error
The ARGetListEntryWithMultiSchemaFields function tried to perform a dynamic join, 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.
ARMultiSchemaQueryFromStruct structure
277

Number
Description
9979
Can specify fields from only one schema in the Recursive Query fields list.
Error

but it failed because the fields that the recursive query was instructed to retrieve were on more
than one form. All the fields must be on the form designated by the recursive schema alias
(recursiveSchemaAlias).
9980
Wrong recursive schema specified in the Recursive Query.
Error

but it failed because the recursive schema alias (recursiveSchemaAlias) does not match any
alias or schema (form) in the recursive querys query from list (queryFromList).
9981
Wrong or missing join type.
Error
The ARGetListEntryWithMultiSchemaFields function tried to perform a dynamic join, but

it failed because the join type (joinType) of one of the items in the functions query from list
(queryFromList) is either invalid or not specified.
Use one of these integers to specify the joinType:
0AR_MULTI_SCHEMA_JOIN_INNER (Inner join)
1AR_MULTI_SCHEMA_JOIN_LEFT (Left outer join)
2AR_MULTI_SCHEMA_JOIN_RIGHT (Right outer join)
9982
Wrong query type specified for an item in the query form list.
Error
A call to the ARGetListEntryWithMultiSchemaFields function failed because one or more

of the items in the functions query from list (queryFromList) is of the wrong type. 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.

278
AR System messages

Number
Description
9983
Schema alias associated with the field is not valid.
Error
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, 254 characters).
Verify the alias and retry the operation. Character strings must be terminated by a \0.
9984
RegularQuery parameter cannot be empty.
Error
The RegularQuery parameter of the getListEntryObjects function (Java API) is NULL.

Provide a valid instance of the RegularQuery object and retry the operation.
For more information, see these documents:
C API Reference, which includes information about the

ARGetListEntryWithMultiSchemaFields function and its Java class diagram
Java API online documentation
9985
The list of query sources cannot be empty.
Error
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.

9986
Join qualifier is specified but join source is not valid.
Error
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). Ensure sure that the object
specified in that element is valid.

9987
Field definition not valid.
Error
The definition of a field specified within a call to the getListEntryObjects function (Java API)
is invalid. Either the field source object is NULL, or the field ID is less than 0.

279

Number
Description
9988
Recursive query cannot be empty.
Error

but it failed because although the recursive query type is specified in the functions query from
list (queryFromList), the recursive query structure is missing.
9989
The list of the query fields must contain at least one regular field you have permission to.
Error
A call to the ARGetListEntryWithMultiSchemaFields function failed because the user

issuing the call did not have permission to any of the fields in the functions getListFields
parameter. To enable the function to return data, give the user permission to at least one field in
that parameter. To return all matching requests, give the user permission to all fields in that
parameter. For more information, see the C API Reference.
9990
The ValueSetQuery property can only have one field.
Error
A call to the getListEntryObjects function (Java API) failed because the list of fields in the
ValueSetQuery object contains more than one field. Fix this error and retry the operation.

9991
Invalid join qualifier for this join form.
Error
A call to the ARGetListEntryWithMultiSchemaFields function failed because the join

criteria for one of the forms in the functions query from list (queryFromList) did not reference
a field in the preceding item in the list. Review the fieldId element in the join criteria
(ARMultiSchemaQualifierStruct) and retry the operation.
ARMultiSchemaQualifierStruct structure
9992
Dialog forms not allowed in a dynamic query.
Error
A call to the ARGetListEntryWithMultiSchemaFields function failed because the

functions queryFromList parameter contains a display-only form, such as a dialog box.
280
ARMultiSchemaQualifierStruct structure
AR System messages

Number
Description
9993
Join qualifier not allowed for the first query source in the list.
Error
A call to the ARGetListEntryWithMultiSchemaFields function failed because the first item

in the functions query from list (queryFromList) contained join criteria (joinType and
joinQual). Specify join criteria in the second item and each item thereafter to define the join with
the previous item. Do not specify the join criteria in the first item in the list. Review the join criteria
and retry the operation. For more information, see these topics in the C API Reference:
9994
Diary field or long char field not allowed in join criterion.
Error
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:
ARGetListEntryWithFieldsRemove these field types from the predefined join criteria in

the AR System join form specified by the functions schema argument.
ARGetListEntryWithMultiSchemaFieldsRemove these field types from the join
criteria (joinQual) of the items in the functions query from list (queryFromList).
BMC Remedy Email Engine workflow messages

11001
The Force For Mailbox has been enabled but no Mailbox has been supplied.
Error
If you select Yes in the Force For Mailbox field, specify or select a valid mailbox in the Mailbox
Name field.
11002
The Expires has been enabled but no Expiration Date has been supplied.
Error
If you select Yes in the Expires field, select a date and time in the Expiration Date field.
11003
The Force From Email Addresses has been enabled but no Email Addresses have been
supplied.
Error
If you select Yes in the Force From Email Addresses field, specify an email address in the Email
Addresses field.
11004
Mailbox Name is missing and no default Mailbox has been configured.
Error
A mailbox name is required. Specify a mailbox name or request your AR System administrator to
set up a default mailbox in the AR System Email Mailbox Configuration form.
11005
You are removing the default mailbox. Please specify a new default mailbox.
Error
If you delete the default outgoing mailbox and do not specify a new default, the mailbox name
must be entered when sending an outgoing email or replying to an incoming email message.
11006
You are deleting a record that has an associated mailbox. This means that you will no longer be
able to send email notifications and/or reply to emails.
Error
If you delete an associated incoming or outgoing mailbox, you cannot send email notifications or
reply to email using this mailbox.
11007
You must specify an Outgoing Mailbox for this mailbox if you set Email Action to Parse.
Error
If you select Parse in the Email Action field on the Advanced Configuration tab, select a mailbox
in the Associated Mailbox Name field.
11010
Outgoing Mailbox configuration does not contain a Server Name.
Error
If you select outgoing for the Mailbox Function, specify a server in the Email Server Name/IP
field.
281

Number
Description
11011
Incoming Mailbox configuration does not contain a User Name or Server Name.
Error
If you select incoming for the Mailbox Function, specify a server in the Email Server Name/IP
field and a user in the Email Server User field.
Extermally written plug-in messages

Use the 2000020999 range for externally written plug-in messages.
Note: To avoid confusion if multiple plug-ins choose the same error code, include some identification in the
associated text loaded into the status array of the externally written plug-in. For example, prefix the error
message with Employee Plug-in: or My Plug-in:.
AR System server Report Console messages
140001
A report already exists with this name. Specify a different name in the Name field.
Error
When creating a report in the Report Console, or when saving a report by using Save As in the
report designer, you entered the name of a report that already exists. Click OK to close the error
message, and then modify the name and click OK.
140002
Specify a new report name.
Error
When saving a report by using Save As in the report designer, you did not enter a name for the
new copy of the report, or you entered the same name as the original report. Click OK to close the
error message, and then enter a new name for the report and click OK.
140003
If you close the report designer now, your changes will not be saved. Do you wish to continue?
Error
You created or modified a report definition and then clicked Back in the report designer without
saving the report definition. To abandon the changes and return to the Report Console list of
reports, click Yes. To remain in the Report Designer screen, click No. To save the report, click Save
or Save As.
140004
Select a report type.
Error
When creating a report in the Report Console, you cleared the Report Type field and then clicked
OK without selecting a report type. Click OK to close the error message, and then select either AR
System or Web in the Report Type field.
For information about report types, see the Report Console Help or the BMC Remedy Mid Tier
Guide.
140005
You did not specify a form. In the Form field, select the form to use for the report.
Error
When creating a report in the Report Console, you did not specify a form to associate with the
report. Click OK to close the error message, and then enter the name of the form to use for the
report in the Form field. You can type the form name or select it from the Form drop-down list.
To show all forms on the server in the drop-down list, clear Forms Used in Existing Reports.
140006
You did not specify a report name. In the Name field, specify a report name.
Error
When creating a report in the Report Console, you did not specify a report name. Click OK to close
the error message, and then enter a name in the Name field and click OK.
140007
Form does not exist.
Error
When creating a report in the Report Console, you entered the name of a nonexistent form in the
Form field. Click OK to close the error message, and then select or type the name of an existing
form in the Form field.
282
AR System messages

Number
Description
140008
To access the AR System Report Console, you must use a browser. For browser login
information, contact your administrator.
Error
You tried to use BMC Remedy User to open the Report Console, but BMC Remedy User does not
support the Report Console. You must open the console in a browser that uses BMC Remedy Mid
Tier 7.6.04 or later.
140009
Error
To access the AR System Report Console, you must use BMC Remedy Mid Tier 7.6.00 or later.
The current mid tier version is midTierVersion.
Your version of the mid tier is earlier than 7.6.00. To open the Report Console in a browser, you
must use BMC Remedy Mid Tier 7.6.x or later.
140010
The report name is too long. Enter a report name of 128 characters or fewer.
Error
When creating a report in the Report Console, you entered a report name that is more than 128
characters. Click OK to close the error message, and then modify the report name in the Name
field so that it contains 128 or fewer characters.
283
284
Chapter
BMC Remedy Migrator error

messages
The tables in this chapter list error messages specific to BMC Remedy Migrator. For
AR System error messages, see Chapter 2, AR System error messages.
About BMC Remedy Migrator error messages (page 286)

BMC Remedy Migrator error message types (page 286)
BMC Remedy Migrator error messages (page 287)
Chapter 3 BMC Remedy Migrator error messages
285
About BMC Remedy Migrator error messages

This chapter contains error messages that are specific to BMC Remedy Migrator. It
includes the number associated with each error, a description of the error message,
and, where available, troubleshooting suggestions.
When an error does not apply specifically to BMC Remedy Migrator, Migrator
uses the same error messages as AR System. For information about AR System
error messages, see Chapter 2, AR System error messages.
NOTE
BMC Remedy Migrator and AR System use different error message numbering
systems. Hence, a Migrator error message and an AR System error message that
have the same number are not related.
If an error persists, contact Customer Support (see page 2).
BMC Remedy Migrator error message types

In BMC Remedy Migrator, error messages are classified according to the following
types:
Table 3-1: BMC Remedy Migrator message ranges (Sheet 1 of 2)
286
Start
End
Error type
See
1000
1999
Cache
page 287
2000
2999
Thread
page 289
3000
3099
Migration
page 289
3100
3199
Menu migration
page 290
3200
3299
Active link migration
page 290
3300
3399
Filter migration
page 291
3400
3499
Escalation migration
page 291
3500
3599
Container migration
page 291
3600
3699
Group migration
page 292
3700
3799
Field migration
page 292
3800
3899
Form migration
page 292
3900
3999
View migration
page 293
4000
4099
Distributed mapping migration
page 294
4100
4199
Data migration
page 294
4200
4299
Support file migration
page 295
4300
4399
Distributed pool migration
page 296
4400
4499
Flashboard variable migration
page 296
4500
4599
Flashboard data source migration
page 296
4600
4699
Flashboard migration
page 297
Table 3-1: BMC Remedy Migrator message ranges (Sheet 2 of 2)

Start
End
Error type
See
4700
4799
Flashboard alarm migration
page 297
4800
4899
Backup migration
page 298
4900
4999
Role migration
page 299
5000
5099
Application state migration
page 299
5100
5199
Locked object migration
page 300
5200
5299
Plug-in module
page 300
5300
5399
Plug-in definition
page 300
5400
5499
Image migration
page 300
6000
6299
Source code control and object reservation
page 300
7000
9000
Command-line
page 301

The error messages in the following table are specific to BMC Remedy Migrator.
They are arranged in numerical order.
Table 3-2: BMC Remedy MIgrator error messages (Sheet 1 of 16)
Error
Message and description
Cache errors
1000
An object accessed is missing from the cache file.

Retry the operation. BMC Remedy Migrator tries to repair the cache the next time a cache operation
occurs. If the error persists, contact BMC Customer Support.
1001
Unable to load the requested file. The file format might be incompatible or the file may be
corrupted.
Make sure that the files do not have Read Only attributes. If the error persists, contact Customer
Support.
1002
Unable to locate object in the cache file. This is a File Seek error.
The system will attempt to fix the error. However, the file might already be corrupted. If the error
persists, contact Customer Support.
1003
Unable to allocate storage space required by the object in the cache file.
Make sure that there is enough free disk space. If the error persists, contact Customer Support.
1004
Unable to add the object name to the binary tree.

This is an internal error. Contact Customer Support.
1005
Unable to replace the location value of the object in the binary tree.
1006
Duplicate entry found in cache.

You might need to delete the cache and try the migration again.
1007
Unable to load the Entry from the cache file.

If you are migrating from a server to a server or from a server to a file, you might need to delete the
cache and try the migration again.
287

Error
1009
Unable to load the Container from the cache file.

1010
Unable to load the Filter from the cache file.

1011
Unable to load the Escalation from the cache file.

cache file and try the migration again.
1012
Unable to load the Menu from the cache file.

1013
Unable to load the Schema from the cache file.

1014
Unable to load the Schema Field from the cache file.

1015
Unable to load the Schema View from the cache file.

1016
Unable to load the Flashboard from the cache file.

1017
Unable to load the Flashboard Alarm from the cache file.

1018
Unable to load the Flashboard Variable form the cache file.

1019
Unable to load the Flashboard DataSource form the cache file.

1020
Unable to load the DSO Map from the cache file.

1021
Unable to load the DSO Pool from the cache file.

1022
Unable to load the Support File from the cache file.

288

Error
1023
Requested Attachment not found in cache file.

A specified attachment was not found in the cache file. Try the migration again.
1024
Attachment is not valid and does not contain actual attachment data.
An attachment file was not recognized in a migration. Check the file format for the attachment, and
try the migration again.
1026
Unable to load the Plugin Module from the cache file.

If you are migrating between servers or from a server to a file, you might need to delete the cache
and try the migration again.
1027
Unable to load the Plugin Definition form the cache file.

1028
Unable to load the Image from the cache file.

Thread errors
2000
An invalid thread pointer occurred.

2001
An illegal access error occurred with the thread.

2002
An illegal internal thread error occurred.

2003
A required parameter is missing from the request object.

2004
The thread crashed because of an unknown error.

2005
The thread was cancelled.

2006
The thread was interrupted.

Migration errors
3003
You do not have the administrator privilege, which is required for this operation.
You are not recognized by the system as an administrator. You must update your profile on the
server to become part of the Administrator group, or obtain a new user name with Administrator
status.
3004
Connection to server timed out.

The connection to the server was lost because there was no user activity. You must log in again.
3006
Unable to expand the specified Deployed Application.
3007
Error occurred while calculating all objects to be migrated.

BMC Remedy Migrator was unable to calculate all objects to be migrated.
3008
Object mentioned for special migration is missing from the source.

A special migration object, such as a packing list, might be missing from the source.
289

Error
3009
Unable to synchronize the memory cache with the Server/Migrator File.

A function call that initializes the caching of objects in memory failed at some point.
3010
Missing source workflow.

Workflow objects to be migrated are missing from the source.
3011
Unable to Initialize server.

The system cannot initialize the connection to a source or a destination server for a migration.
3012
Unable to delete the specified AR System Item itemName.

When migrating CMDB metadata content, the specified object could not be deleted due to an API
issue.
Menu migration errors

3100
Unable to create character menu on server ARSystemServerName.

The object could not be created on the destination server. For example, the object could be
referencing a form that does not exist on the destination server.
3101
Unable to modify character menu on server ARSystemServerName.

An object that differs from the source to the destination could not be updated on the destination.
3102
Unable to retrieve character menu from server ARSystemServerName.

The object could not be retrieved from the source. Check the source to verify that the object exists.
If the problem persists, check your workflow to be sure that it does not reference a nonexistent
object.
3103
Unable to find the destination server for the parent form of this character menu.
The specified destination server cannot be found. Check the destination server name to be sure it
is correct. If the problem persists, the destination server might have been moved or shut down, or
the network might be down.
Active link migration errors

3200
Unable to create active link on server ARSystemServerName.

3201
Unable to modify active link on server ARSystemServerName.

3202
Unable to retrieve active link from server ARSystemServerName.

object.
3203
Unable to find the destination server for the parent form of this active link.
290

Error
Filter migration errors

3300
Unable to create filter on server ARSystemServerName.

3301
Unable to modify filter on server ARSystemServerName.

3302
Unable to retrieve filter from server ARSystemServerName.

object.
3303
Unable to find the destination server for the parent form of this filter.
Escalation migration errors

3400
Unable to create escalation on server ARSystemServerName.

3401
Unable to modify escalation on server ARSystemServerName.

3402
Unable to retrieve escalation from server.

object.
3403
Unable to find the destination server for the parent form of this escalation.
Container migration errors
Includes errors for applications, active link guides, filter guides, web services, and packing lists.
3500
Unable to create container on server ARSystemServerName.

3501
Unable to modify container on server ARSystemServerName.

3502
Unable to retrieve container from server ARSystemServerName.

object.
3503
Unable to find the destination server for the parent form of this container.
291

Error
Group migration errors

3600
Unable to create group on server ARSystemServerName.

3601
Unable to modify group on server ARSystemServerName.

3602
Unable to retrieve group from server ARSystemServerName.

object.
3603
Unable to retrieve group list from server ARSystemServerName.

object.
Field migration errors

3700
Unable to create field on server ARSystemServerName.

3701
Unable to modify field on server ARSystemServerName.

3702
Unable to retrieve field from server ARSystemServerName.

object.
3703
Unable to find destination server.

3715
Error deleting fields from server.

The destination server encountered a problem when removing excess fields not found on the
source.
3717
Unable to create fields where the field ID is in the following ranges: 200 to 212, 250 to 252 and
300 to 317 range. Fields in these ranges are reserved for the Distributed Server Option.
Form migration errors

3800
Unable to create form on server ARSystemServerName.

3801
Unable to modify form on server ARSystemServerName.

3802
Unable to retrieve form from server ARSystemServerName.

object.
292

Error
3803
Unable to find the destination server for the parent form of this form.
3812
Unable to retrieve form view list from server ARSystemServerName.

object.
3813
Unable to create a temporary view on destination form.

The server might be down, preventing creation of a temporary view for migration of views
between the source and the destination. If the migration continues to fail, contact Customer
Support.
3814
Unable to delete unwanted views on destination form.

The server might be down, preventing removal of unwanted views on the destination. If the
migration continues to fail, contact Customer Support.
3816
Unable to create archive forms. Archive form is maintained by the server.

If you are migrating a form that has an archive form associated with it, the archive form will be
created on the destination server.
3817
Unable to delete a temporary view on the destination form.

The server might be down, preventing deletion of the temporary view. Try migrating again, or use
BMC Remedy Developer Studio to delete the temporary view.
3819
Unable to create additional copies of the Alert Events form.

The Alert Events form is a system form. System forms cannot be copied.
3820
Dummy Forms are not migrated because they only contain data.
A dummy form is a special form used to contain data to be migrated. This form cannot be migrated.
3821
Unable to Migrate the Specified System Form.

System forms cannot be created; they can only be modified.
3822
Cannot add destination form to application definition applicationName.

A form was reassigned to a different application on the destination but the assignment was not
changed during the migration process.
3823
Cannot remove destination form from existing application definition.

A form was not removed from a specified application during the migration process.
View migration errors

3900
Unable to create view on server ARSystemServerName.

The view could not be created on the destination server. For example, the view could be
3901
Unable to modify view on server ARSystemServerName.

A view that differs from the source to the destination could not be updated on the destination.
293

Error
3902
Unable to retrieve view from server ARSystemServerName.

The view could not be retrieved from the source. Check the source to verify that the view exists. If
the problem persists, check your workflow to be sure that it does not reference a nonexistent object.
3903
Unable to find the destination server for the parent form of this view.
Distributed mapping migration errors

4000
Unable to create distributed mapping on server ARSystemServerName.

The distributed mapping could not be created on the destination server. For example, the
distributed mapping could be referencing a form that does not exist on the destination server.
4001
Unable to modify distributed mapping on server ARSystemServerName.

A distributed mapping that differs from the source to the destination could not be updated on the
destination.
4002
Unable to retrieve distributed mapping from server ARSystemServerName.

The distributed mapping could not be retrieved from the source. Check the source to verify that
the object exists. If the problem persists, check your workflow to be sure that it does not reference
a nonexistent object.
4003
Unable to find the destination server for the parent form of this distributed mapping.
Data migration errors

4100
Unable to create entry on server ARSystemServerName.

The entry could not be created on the destination server. For example, the entry could be
4101
Unable to modify entry on server ARSystemServerName.

An entry that differs from the source to the destination could not be updated on the destination.
4102
Unable to retrieve entry from server ARSystemServerName.

The entry could not be retrieved from the source. Check the source to verify that the entry exists.
object.
4103
Unable to find the destination server for the parent form of this entry.
4111
Unable to merge entry on server.

The system could not perform a merge during data migration.
4112
An entry specified in a data migration could not be found.

An entry specified in a data migration could not be found.
294

Error
4113
Unable to load qualification from server ARSystemServerName.

Data specifying a qualification could not be loaded from the source.
4114
Unable to retrieve entry list.

An entry list could not be retrieved from the source.
4115
Unable to retrieve entry attachment.
4116
A filter that was disabled could not be re-enabled on the destination.

A filter that was disabled could not be re-enabled on the destination.
4117
A filter could not be disabled on the source.

A filter could not be disabled on the source.
4119
An escalation that was disabled could not be re-enabled on the destination.

An escalation that was disabled could not be re-enabled on the destination.
4120
Unable to obtain all the related Escalations for Form.

All of the related escalations for a form being migrated could not be migrated to the destination.
4121
Unable to obtain all the related Forms for Form.

All of the related Forms for the form being migrated could not be migrated to the destination.
4122
Unable to initialize Fast Server Port Connection on Server.

BMC Remedy Migrator was unable to use the Fast server port connection option for this migration.
4123
Unable to initialize List Server Port Connection on Server.

BMC Remedy Migrator was unable to use the List server port connection option for this migration.
4124
A filter that was disabled for the migration process was not re-enabled upon completion of the
migration.
A filter that was disabled for the migration process was not re-enabled upon completion of the
migration.
4125
An escalation that was disabled for the migration process was not re-enabled upon completion
of the migration.
An escalation that was disabled for migration was not re-enabled after completion of the migration
due to an API issue.
Support file migration errors

4200
Unable to create Support File on server ARSystemServerName.

The support file could not be created on the destination server. For example, the support file could
be referencing a form that does not exist on the destination server.
4201
Unable to modify Support File on server ARSystemServerName.

A support file that differs from the source to the destination could not be updated on the
destination.
4202
Unable to retrieve Support File from server ARSystemServerName.

The support file could not be retrieved from the source. Check the source to verify that the support
file exists. If the problem persists, check your workflow to be sure that it does not reference a
nonexistent object.
4203
Unable to find the destination server for the parent form of this support file.
295

Error
Distributed pool migration errors

4300
Unable to create distributed pool on server ARSystemServerName.

The distributed pool could not be created on the destination server. For example, the object could
4301
Unable to modify distributed pool on server ARSystemServerName.

A distributed pool that differs from the source to the destination could not be updated on the
destination.
4302
Unable to retrieve distributed pool from server ARSystemServerName.

The distributed pool could not be retrieved from the source. Check the source to verify that the
object exists. If the problem persists, check your workflow to be sure that it does not reference a
nonexistent object.
4303
Unable to find the destination server for the parent form of this distributed pool.
Flashboard variable migration errors

4400
Unable to create Flashboard Variable on server ARSystemServerName.

4401
Unable to modify Flashboard Variable on server ARSystemServerName.

4402
Unable to retrieve Flashboard Variable from server ARSystemServerName.

object.
4403
Unable to find the destination server for the parent form of this flashboard.
Flashboard data source migration errors

4500
Unable to create Flashboard Data Source on server ARSystemServerName.

The Flashboard data source could not be created on the destination server. For example, the object
could be referencing a form that does not exist on the destination server.
4501
Unable to modify Flashboard Data Source on server ARSystemServerName.

A Flashboard data source that differs from the source to the destination could not be updated on
the destination.
296

Error
4502
Unable to retrieve Flashboard Data Source from server ARSystemServerName.

The Flashboard data source could not be retrieved from the source. Check the source to verify that
the object exists. If the problem persists, check your workflow to be sure that it does not reference
a nonexistent object.
4503
Unable to find the destination server for the parent form of this flashboard data source.
Flashboard migration errors

4600
Unable to create Flashboard on server ARSystemServerName.

The Flashboard could not be created on the destination server. For example, the object could be
4601
Unable to modify Flashboard on server ARSystemServerName.

A Flashboard that differs from the source to the destination could not be updated on the
destination.
4602
Unable to retrieve Flashboard from server ARSystemServerName.

The Flashboard could not be retrieved from the source. Check the source to verify that the object
exists. If the problem persists, check your workflow to be sure that it does not reference a
nonexistent object.
4603
Unable to find the destination server for the parent form of this flashboard.
Flashboard alarm migration errors

4700
Unable to create Flashboard Alarm on server ARSystemServerName.

The Flashboard Alarm could not be created on the destination server. For example, the object could
4701
Unable to modify Flashboard Alarm on server ARSystemServerName.

A Flashboard Alarm that differs from the source to the destination could not be updated on the
destination.
4702
Unable to retrieve Flashboard Alarm on server ARSystemServerName.

The Flashboard Alarm could not be retrieved from the source. Check the source to verify that the
object exists. If the problem persists, check your workflow to be sure that it does not reference a
nonexistent object.
4703
Unable to find the destination server for the parent form of this flashboard alarm.
297

Error
Backup migration errors

4800
Unable to back up Form on server ARSystemServerName.

The object could not be backed up on the specified server. Check the Backup options to verify that
backing up is enabled for the object. For more information about backup options, see the BMC
Remedy Migrator Guide.
4801
Unable to back up Active Link on server ARSystemServerName.

4802
Unable to back up Container on server ARSystemServerName.

4803
Unable to back up DSO Mapping on server ARSystemServerName.

4804
Unable to back up DSO Pool on server ARSystemServerName.

4805
Unable to back up Escalation on server ARSystemServerName.

4806
Unable to back up Flashboard Alarm on server ARSystemServerName.

4807
Unable to back up Flashboard Data Source on server ARSystemServerName.

4808
Unable to back up Flashboard on server ARSystemServerName.

4809
Unable to back up Flashboard Variable on server ARSystemServerName.

298

Error
4810
Unable to back up Field on server ARSystemServerName.

4811
Unable to back up Filter on server ARSystemServerName.

4812
Unable to back up Character Menu on server ARSystemServerName.

4813
Unable to back up VUI on server ARSystemServerName.

4814
Unable to create backup file.

A backup file could not be created. Check the Backup options to verify that backing up is enabled
for the objects you want backed up. Also, be sure that you have specified a valid backup directory
path. For more information about backup options, see the BMC Remedy Migrator Guide.
4815
Unable to backup Plug-in Module moduleName.

The plug-in module could not be backed up on the specified server. The plug-in definition could
not be backed up on the specified server. Check the Backup options to verify that backing up is
enabled for this object. Also, be sure that you have specified a valid backup directory path.
4816
Unable to backup Plug-in Definition on server ARSystemServerName.

The plug-in definition could not be backed up on the specified server. Check the Backup options
to verify that backing up is enabled for this object. Also, be sure that you have specified a valid
backup directory path.
4817
Unable to back up Image imageName.

The specified image could not be backed up.
Role migration errors

4901
Unable to create Role on server ARSystemServerName.

The role could not be created on the destination server. For example, the role could be referencing
a form that does not exist on the destination server.
4902
Unable to retrieve Role from server ARSystemServerName.

The role could not be retrieved from the source. Check the source to verify that the role exists. If
the problem persists, check your workflow to be sure that it does not reference a nonexistent role.
Application state migration errors

5001
Unable to create Application State on server ARSystemServerName.

299

Error
5002
Unable to retrieve Application State from server ARSystemServerName.

object.
Locked object migration errors

5100
Locked objects cannot be renamed through migration.

The object cannot be renamed on the destination server because it is locked.
Plug-in module errors

5201
Unable to create plugin Module.

The module could not be created on the destination server. For example, the module could be
5202
Unable to retrieve Plugin Module.

The module could not be retrieved from the source. Check the source to verify that the module
exists. If the problem persists, check your workflow to be sure that it does not reference a
nonexistent module.
5205
Unable to modify Plugin Module.

A module that differs from the source to the destination could not be updated on the destination.
Plug-in definition errors

5301
Unable to create Plugin Definition.

5302
Unable to retrieve Plugin Definition.

object.
5305
Unable to modify Plugin Definition.

Image migration errors

5401
Unable to create Image imageName.

The image could not be created on the destination server.
5402
Unable to retrieve Image imageName.

The image could not be retrieved from the source. Check the source to verify that the image exists.
image.
5405
Unable to modify Image imageName.

An image that differs from the source to the destination could not be updated on the destination.
Source code control and object reservation errors

6000
Unable to migrate object. Object currently checked out by userName.

The specified object could not be migrated because the source code control indicates that it is
currently checked out.
6001
Unable to migrate object. Object currently reserved by userName.

The specified object could not be migrated because it is currently reserved.
300

Error
Command-line errors
The following errors might occur when BMC Remedy Migrator performs these operations:
Expands the metadata mapping document to obtain instructions

Obtains data from the source and destination for each of the form mappings
Obtains the source object names to which some form items map
7000
Unable to locate identifying form Mapping.

No identifying form mapping is defined in the mapping document. At least one form mapping
must be present.
7001
Unable to load attachments for fieldName.

One or more fields contain attachment data that could not be loaded.
7002
Unable to load entries for formName.

One or more fields in a form contain entries that could not be loaded for comparison.
7003
Missing Form Mapping Item for form: formName.

The mapping document includes a reference to a form that does not have its own mapping.This
issue does not typically apply to CMDB migrations.
7005
Mapping Item is not mapped to any form.

A mapping was defined, but the form being mapped to was not specified. This issue does not
typically apply to CMDB migrations.
7006
Missing Local Key Fields for mapping to form.

The metadata mapping document includes a mapping to a form but does not specify the local fields
used to identify the entries being mapped to in the form. This issue does not typically apply to
CMDB migrations.
7007
Multi-Mapping Item is not mapped to any intermediate form for mapping to form:
The intermediate form required for use with many-to-many mappings could not be found. This
issue does not apply to CMDB migrations, which do not use many-to-many mappings.
7008
Multi-Mapping Item is missing Local Key Fields for intermediate form:

The intermediate form required to identify local key fields cannot be found. This issue does not
apply to CMDB migrations, which do not use many-to-many mappings.
7009
Multi-Mapping Item is missing Destination Key Fields for intermediate form:

The intermediate form required to identify entries on the destination form cannot be found. This
issue does not apply to CMDB migrations, which do not use many-to-many mappings
7010
Missing Object Name Definition for mapping from:

The mapping document includes information that defines how a form maps to an actual object, but
does not have information about how the object name was created. This issue does not apply to
CMDB migrations, which do not use many-to-many mappings.
7012
Missing Data when building Unique Search Key, please verify meta-data mappings.
Some unique fields do not exist on the form being migrated, or are not data fields. All fields
specified as unique fields must be data fields.
7013
Missing Parent Object Mapping for Form Mapping item.

BMC Remedy Migrator cannot find the parent form on the source for specified fields and views.
301

Error
7014
Unable to determine Parent Object Name for Form Mapping items.

BMC Remedy Migrator cannot determine the parent form name for mappings to fields and views
specified in a metadata mapping document. The defined mapping requires the name of the form
that includes the specified fields and views.
This issue does not apply to CMDB migrations.
7015
Missing Source Meta Data Item(s).

Non-existent CMDB classes have been specified in the instruction file or in the command line.
302
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
active link migration errors 290

application state migration errors 299
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
field migration errors 292

filter migration errors 291
flashboard data source migration errors 296
flashboard migration errors 297
form migration errors 292
forms
AR System Error Messages 15
AR System Message Catalog 15
B
backup migration errors 298
BMC Software, contacting 2
G
group migration errors 292
help with error messages 15
cache error messages 287

catalogs, message on UNIX 13
command-line errors 301
container migration errors 291
custom error messages 18
customer support 3
D
data migration errors 294
display data types 38
distributed mapping migration errors 294
distributed pool migration errors 296
documentation, AR System 8
documentation, help with error messages 15
E
error message
custom 18
defined 8
escalation migration errors 291
image migration errors 300
L
localizing message catalogs 14
locked object migration errors 300
M
menu migration errors 290
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
Index
303
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
reporting 12
reserved ranges of message numbers 18
syslog daemon on UNIX 12
terminology 8
UNIX server error reporting 12
Windows server error reporting 13
migration errors 289
Migrator
about error messages 286
active link migration error 290
application state migration errors 299
backup migration errors 298
cache error messages 287
command-line errors 301
container migration errors 291
data migration errors 294
distributed mapping migration errors 294
distributed pool migration errors 296
error message types 286
error messages 287
escalation migration errors 291
field migration errors 292
filter migration errors 291
flashboard data source migration errors 296
flashboard migration errors 297
flashboard variable migration errors 296
form migration errors 292
group migration errors 292
menu migration errors 290
migration errors 289
plug-in definition errors 300
plug-in module errors 300
role migration errors 299
source code control and object reservation 300
source control errors 300
support file migration errors 295
thread error messages 289
view migration errors 293
N
note informational message, defined 8
O
organization of this guide 17
P
plug-in definition errors 300
plug-in module errors 300
304
product support 3
R
ranges of message numbers 18
reporting, messages by AR System clients 12
role migration errors 299
S
source code control and object reservation 300
support file migration errors 295
support, customer 3
syslog daemon on UNIX 12
T
technical support 3
thread error messages 289
troubleshooting. See diagnostic messages
types, Migrator error message 286
U
UNIX
message catalogs 13
server error reporting 12
syslog daemon 12
V
view migration errors 293
W
warning message, defined 8
Windows, server error reporting 13
**183977**
**183977**
**183977**
**183977**
*183977*

ErrorMsgs 7604

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ErrorMsgs 7604

Transféré par

Droits d'auteur :

Formats disponibles

BMC Remedy Action Request System 7.6.

Error Messages Guide

Contacting BMC Software

United States and Canada

BMC SOFTWARE INC

713 918 8800 or

(01) 713 918 8000

713 918 8000

Outside United States and Canada

(01) 713 918 8800

Copyright 19912011 BMC Software, Inc.

Restricted rights legend

Support by telephone or email

Before contacting BMC Software

Operating system and environment information

Sequence of events leading to the problem

Commands and options that you used

Product error messages

License key and password information

E-mail customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>,

Submit a new issue at http://www.bmc.com/support.

AR System diagnostic messages

AR System error messages

Finding AR System messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

BMC Remedy Migrator error messages

About BMC Remedy Migrator error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Error Messages Guide

AR System Error Messages form

BMC Remedy Action Request System 7.6.04

Terminology used in error messages

Message TextA message in a dialog box that interrupts operations. Messages

Overview of AR System architecture and features; includes Everyone

Instructions for installing AR System.

Information about the development of AR System

Error Messages Guide

Information about the AR System workflow objects (active Developers

Information about configuring AR System servers and

Instructions for integrating AR System with external

Information about monitoring and maintaining AR System Administrators/

Database administration topics and rules related to how

BMC Remedy Distributed

Information about implementing a distributed AR System

BMC Remedy Flashboards

Instructions for creating, modifying, and administering

Information about AR System data structures, C API

C API Quick Reference

Quick reference to C API function calls.

Java Plug-in API

Information about Java classes, methods, and variables used Programmers

BMC Remedy Email Engine

Instructions for configuring and using BMC Remedy Email Administrators

Error Messages Guide

Descriptions of AR System error messages.

Combined index of all books.

BMC Remedy Approval

Instructions for using BMC Remedy Approval Server to

Information about new features, compatibility, and

Release Notes with Known

Information about new features, compatibility, international Everyone

BMC Remedy User Help

Instructions for using BMC Remedy User.

BMC Remedy Action Request System 7.6.04

Instructions for using BMC Remedy Administrator to