Error Messages

Action Request System 6.
3 Error Messages Guide
January 2005 Part No: 47837
Copyright 19912005 BMC Software, Inc. All rights reserved. BMC, the BMC logo, all other BMC product or service names, BMC Software, the BMC Software logos, and all other BMC Software product or service names, are registered trademarks or trademarks of BMC Software, Inc. All other trademarks belong to their respective companies. BMC Software, Inc. 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 or nondisclosure agreement for the product and the proprietary and restricted rights notices included in this documentation. For license information about the OpenSource files used in the licensed program, please read OpenSourceLicenses.pdf. This file is in the \Doc folder of the distribution CD-ROM and in the documentation download portion of the Remedy Electronic Software Distribution (ESD). 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.
Contacting Us If you need technical support for this product, contact Customer Support by email at support@remedy.com. If you have comments or suggestions about this documentation, contact Information Development by email at doc_feedback@remedy.com. This edition applies to version 6.3 of the licensed program.
BMC Software, Inc.
www.remedy.com
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 AR System Error Messages form. . . . . . . . . . . . . . . . . . . . . . 5 Action Request System documents . . . . . . . . . . . . . . . . . . . . 6 Terminology used in error messages . . . . . . . . . . . . . . . . . . . . 8 Chapter 1 AR System diagnostic messages . . . . . . . . . . . . . . . . . . . . . . 9 Message reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Server error reporting in UNIX . . . . . . . . . . . . . . . . . . . . 10 Server error reporting in Windows . . . . . . . . . . . . . . . . . . 11 Message catalogs in UNIX . . . . . . . . . . . . . . . . . . . . . . . 11 Message not in catalog . . . . . . . . . . . . . . . . . . . . . . . . 12 AR System Error Messages form. . . . . . . . . . . . . . . . . . . . . 13 Localizing error messages. . . . . . . . . . . . . . . . . . . . . . . . 13 Chapter 2 Action Request System error messages . . . . . . . . . . . . . . . . . . 15 Finding AR System error messages . . . . . . . . . . . . . . . . . . . 16 AR System error messages . . . . . . . . . . . . . . . . . . . . . . . 18 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Contents
Action Request System 6.3
4 Contents
Preface
This manual contains the complete catalog of error messages for the Remedy Action Request System 6.3 (AR System) software product.
Audience
This manual is written for administrators and users of AR System.
AR System Error Messages form

The information contained 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 displayed on the users screen, 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 13.
Preface
Action Request System documents

The following table lists the documentation available for Action Request System products. Unless otherwise noted, online documentation in Adobe Acrobat (PDF) format is available on AR System product installation CDs, on the Customer Support web site (http://supportweb.remedy.com), or both. You can access product Help through each products Help menu or by clicking on Help links.
Title Action Request System 6.3 Concepts Guide Description Overview of AR System architecture and features with in-depth examples; includes information about other AR System products as well as a comprehensive glossary for the entire AR System documentation set. Basic procedures for creating and modifying an AR System application for tracking data and processes. Advanced procedures for extending and customizing AR System applications. Audience Everyone Format PDF and Print
Action Request System 6.3 Developing AR System Applications: Basic Action Request System 6.3 Developing AR System Applications: Advanced Action Request System 6.3 Configuring AR System
Administrators
PDF and Print PDF and Print PDF and Print
Administrators
Administrators Server administration topics on configuring servers and the mid tier, maintaining AR System, and licensing AR System.
Administrators Server administration topics and Action Request System 6.3 Optimizing and Troubleshooting technical essays related to monitoring AR System and maintaining AR System for the purpose of optimizing performance and troubleshooting problems. Action Request System 6.3 Database Reference Guide Database administration topics and rules related to how AR System interacts with specific databases; includes an overview of the data dictionary tables. Administrators
PDF and Print
PDF and Print
6 Preface
Error Messages Guide
Title Action Request System 6.3 Remedy DSO Administrators Guide
Description
Audience
Format PDF and Print
Server administration and procedures Administrators for implementing a distributed AR System server environment with the Remedy Distributed Server Option (DSO). Administrators Flashboards administration and procedures for creating and modifying and Programmers flashboards and flashboards components to display and monitor AR System information. Information about AR System data structures, C API function calls, and OLE support. Quick reference to C API function calls. Information about Java classes, methods, and variables that integrate with AR System. Procedures for installing AR System. Administrators and Programmers Administrators and Programmers Administrators and Programmers Administrators
Action Request System 6.3 Remedy Flashboards Administrators Guide
PDF and Print
Action Request System 6.3 C API Reference Guide Action Request System 6.3 C API Quick Reference Guide Action Request System 6.3 Java API Action Request System 6.3 Installing AR System Action Request System 6.3 Remedy Email Engine Guide Action Request System 6.3 Error Messages Guide Action Request System 6.3 Master Index Action Request System 6.3 Release Notes Remedy User Help Remedy Import Help
PDF and Print PDF and Print HTML*
PDF and Print PDF and Print PDF and Print PDF and Print PDF and Print Product Help Product Help
Procedures for installing, configuring, Administrators and using the Remedy Email Engine. List and expanded descriptions of AR System error messages. Combined index of all books. New features list, compatibility lists, international issues, and open and fixed issues. Procedures for using Remedy User. Administrators and Programmers Everyone Everyone
Everyone
Procedures for using Remedy Import. Administrators
Action Request System documents
Title Remedy Administrator Help
Description
Audience
Format Product Help Product Help Product Help
Procedures for creating and modifying Administrators an AR System application for tracking data and processes. Procedures for using Remedy Alert. Procedures for configuring the Remedy Mid Tier. Everyone Administrators
Remedy Alert Help Remedy Configuration Tool Help

*.
A JAR file containing the Java API documentation is installed with the AR System server. Typically, it is stored in C:\ProgramFiles\AR System\Arserver\Api\doc\ardoc63.jar.
Terminology used in error messages

MessageText Note Warning The system displays a message in a dialog box that interrupts operations. Messages include notes, warnings, and errors. A purely informational message; no action is needed, and the system continues with normal operation. Notes are labeled ARNOTE in AR System. A 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. A 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.
Error
8 Preface
Chapter
AR System diagnostic messages
Diagnostic error and warning messages are included with AR System. Because error checking is built into how AR System clients (for example, Remedy Administrator) interact with AR System server, you might only see some of these messages with client applications that you create using the AR System API. When problems occur, the system usually reports one or more error or warning messages. These messages often provide you with information to determine the cause of a problem. This guide lists and describes these messages. There is also an online version of all of the messages and descriptions available in the Error Messages form. Occasionally, it may not be clear from the diagnostic messages what you need to do to correct a problem. This chapter describes common problems and outlines the process you must follow to resolve each of these problems. If you are still unable to resolve a problem or if you encounter a problem that is not covered in this chapter, contact your Customer Support Services representative. This chapter covers the following topics: Message reporting (page 10) Message catalogs in UNIX (page 11) AR System Error Messages form (page 13) Localizing error messages (page 13)
AR System diagnostic messages
Message reporting
All of the interactive AR System tools (Remedy User, Remedy Administrator, Remedy Alert, and Remedy Import) report errors directly to the terminal. If a tool fails during startup, the error messages are reported at the command line from which the program was started.
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 errors are sent to the syslog daemon where, depending on the configuration of your system, they are displayed or recorded. For a complete discussion of the syslog process, see the discussion about the syslogd process and the syslog.conf file in 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. Remove 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 you want all messages delivered to syslog that are of the type user.err written to the file /usr/ar/err.log: user.err/usr/ar/err.log To activate 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 read its configuration file again. AR System administrators can configure system logging options. For information, see the Configuring AR System guide.
10 Chapter 1AR System diagnostic messages
All errors are also written to the file arerror.log filed in the <ar_install_dir>/db directory. (See the discussion about log files and debug modes in the Optimizing and Troubleshooting AR System guide.)
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. Click on Event Viewer, which opens up the Event Viewer Application Log window; AR System messages have the Source column set to Remedy Action Request. All errors are also written to the arerror.log file in the <ar_install_dir>\db directory. (See the discussion about log files and debug modes in the Optimizing and Troubleshooting AR System guide.)
Message catalogs in UNIX

All of the 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:
Client Platform HP-UX AIX Solaris Linux Message Catalog Location
/usr/lib/nls/msg/%L/%N /usr/lib/nls/msg/en_US/%N /usr/lib/locale/%L/LC_MESSAGES/%N /usr/lib/locale/%L/LC_MESSAGES/%N
In the path names there are two variables: %L specifies the value of the LANG environment variable (C by default). %N specifies the name of the message catalog.
Message catalogs in UNIX
11
For example, the syntax for specifying AR System message catalog location (assuming the default language environment) on Solaris is: /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 located in the locale directory under AR System installation directory (by default, this is /usr/ar/locale). Use the NLSPATH environment variable to place the catalogs in a directory other than in 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
Note: Include the default directory in the NLSPATH environment variable to make sure that catalogs for other products are still accessible.
See the documentation supplied with your operating system for more information about internationalizing message catalogs.
Message not in catalog

Problem Action If you receive the Message not in catalog; Message number = <###> message, a process cannot access the message catalog. Make sure that the message catalogs exist, that they are located in the appropriate directory, and that the NLSPATH environment variable is set correctly. Make sure that the setting of your LANG environment variable is set to the correct language. You can unset 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.
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 may come from either the server or the client. Make sure that the proper settings of LANG and NLSPATH are in place on both the server and the client before running the process that is returning the error. Also, the arsystem.cat file must be 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 installation of 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 Remedy Administrator to import the
form definition file from this location: <ar_install_dir>\arserver\help\remerror.def (Windows) <ar_install_dir>/help/remerror.def (UNIX)
2 Use Remedy Import to import error message data from this file:
<ar_install_dir>\arserver\help\errars.arx (Windows) <ar_install_dir>/help/errars.arx (UNIX) The AR System Error Messages form is now ready for use. Select AR System in the product list to search for AR System error messages, including flashboards and notification error messages.
Localizing error messages

The AR System Message Catalog form is provided to enable administrators to provide localized versions of error messages, help text, menus, and other text strings displayed to users in applications that are customized by locale. The use of this form can be enabled or disabled. You can use this form in both UNIX and Windows environments. For more information, see the Developing AR System Applications: Basic guide.
13
Because these error messages can be modified for localization, the message text a user sees may not match the text in this guide if the message has been overridden in the AR System Message Catalog form. The meaning of the message will still be the same, but the text may not match exactly.
Chapter
Action Request System error messages

This chapter contains all the error messages in their numerical order for the client, server, and mid tier components of AR System. You can look up any error message quickly by turning to the number in its sequence. This chapter contains the following topics: Finding AR System error messages (page 16) AR System error messages (page 18)
Action Request System error messages
15
Finding AR System error messages

The Error Messages Guide documents only those error messages used in AR System 6.3. It makes no attempt to be backwards-compatible with previous versions of AR System if a feature has become obsolete, for example, administrator commands. The chapter is arranged according to the following general ranges of messages (See the following table). However, you should note that error messages for certain Remedy products are not documented in this chapter. These exceptions are noted. For those, you will need to see the appropriate product manual. For example, to find error messages for the Remedy Approval Server, see the documentation in that suite of products.
Start 1 1000 1800 2000 3000 3300 3350 3380 End 999 1799 1999 2999 3199 3349 3379 3499 Product AR System Server Remedy User Remedy User Description Server messages and notifications Remedy User errors, warnings, and notes Remedy User errors
Remedy Administrator Remedy Administrator errors and client (Windows) warnings AR System Server AR System Server AR System Server Discovery Remedy Distributed Server Option messages Remedy Import event messages Report ARDBC plug-in messages Discovery Services SMS, and Tally messages (not documented in this guide) Flashboards errors, warnings, and notes
3500 4000 4500
3999 4499 4899
Remedy Flashboards
Remedy Import client Remedy Import errors, warnings, and (Windows) notes Action Request System Action Request System applications application servers servers, including Remedy Approval Server (not documented in this guide) Remedy Email Engine Email errors and warnings
4900
4999
16 Chapter 2Action Request System error messages
Start 5000
End 5999
Product ARWeb and Remedy Web
Description ARWeb and Remedy Web errors and warnings (not documented in this guide)
6000
6999
Action Request System Errors for any Action Request System clients client, including Remedy User, Remedy Administrator, Remedy Email Engine, and web tools Remedy Administrator Remedy Administrator errors and client (Windows) warnings Action Request System Server messages Server Remedy Mid Tier Mid tier error messages
7000 8000 9200 9700 11000
7999 9199 9699 9999 11099
Action Request System Server messages Server Remedy Email Engine Email workflow messages
Warning: To make sure of future compatibility, do not create custom error messages for your own applications with numbers in these ranges.
Finding AR System error messages
17
AR System error messages

1 Error Message not in catalogmessage number = <message_number>. An error or warning occurred in the system, and the text corresponding to that error or warning could not be found. (The tag, ARERR, indicates that the condition is an error, while ARWARN indicates a warning, and ARNOTE indicates a note.) There are several possible causes of this problem. Most likely, the message catalog is not accessible to you. see the discussion of message catalogs in the Configuring AR System guide for details on how to correct this problem. If the message catalog is accessible (you are getting most error messages but not this message), an event occurred for which there may not be a corresponding error message in your catalog. If it is not present in this chapter, contact Remedy Customer Support, and provide the message number and the circumstances that prompted the message. 20 Note AR System server terminated when a signal or exception was received by the server. The server for AR System (arserverd) was terminated by a signal. The number following this error is the signal that was received. If the signal is 15, you can probably restart the server and continue to work. The process was killed either accidently or intentionally by a user in your environment. 21 Note AR System server terminatedfatal error encountered. A fatal error occurred within the arserverd process. The details about the error are in an associated message. A generic message indicates that the error was fatal, and the arserverd process is shutting down. Failure occurred during open or write to the filter or escalation log file. 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 23). Open or write action to the filter or escalation log file resumed successfully. 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. Failure while trying to run the filter or escalation process. An error occurred while AR System was executing a filter or escalation that runs a process. An associated message provides details about why the process could not be executed. Verify that the process definition is correct. If necessary, correct the process definition in the filter or escalation.
22 Error
23 Note
24 Error
25 Error
Fields in set fields action incompatible with form for filter or escalation. The filter or escalation being executed is attempting to set values in fields that do not exist in the target form. Correct 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 has been deleted since the definition was created.
26 Error
Administrator operations are disabled on this server. The AR System server has been 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. 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 www.remedy.com. This version of the 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 AR System without these limitations, contact your AR System sales representative, an authorized reseller, or visit www.remedy.com.
27 Note
28 Error
The AR System server does not have a license. Previous demo license has expired. This system can be used for evaluation but is not allowed for production use. Contact your distributor for license information. The demo license for the system on which you are attempting to run the AR System server has expired. The system is now running in an unlicensed mode (see Error 27). You must obtain a license to run AR System server in any mode other than evaluation mode.
29 Note 30 Error
The AR System server license is a demo license that expires <expiration_date>. You are currently operating with a demo license and the license will expire on the date indicated. Contact your distributor for information about upgrading your license. You are already at the limit of the number of fixed user licenses of the type <license_type>. You attempted to create a new user and assign this user a fixed license. Your current number of users is equal to your current number of fixed licenses. You can add the user with a read, none, or floating license, but not a fixed license. The <license_type> is replaced by write, full text, or flashboards, to indicate the type of fixed license. If you have no more fixed licenses, verify that the sample users were deleted. For a more detailed explanation, see the Configuring AR System guide. Contact your distributor for information about obtaining additional licenses.
19
31 Note
A fixed <license_type> license was issued for the new user: <x_of_y>. You have created a new user who is assigned a fixed license. This message is reporting the successful creation of a user and displays the current number of users having a fixed license and the total number of users that are allowed. The <license_type> is replaced by write, full text, or flashboards to indicate the type of fixed license.
32 Note 33 Error 34 Error
AR System server terminated normally. Server shut down without problems. Failure occurred during excel ( ). The AR System has failed to start a process. Make sure that your system has no resource problems that prevent new processes from starting. Error occurred while opening the AR System server lock file. 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 details about the problem. Correct the problem indicated by the message, and run the server again. Another copy of the server is already running on the same RPC socket. Only one instance of AR System server can be run (on a specific RPC socket) on a machine at one time. If there is already a server running in this RPC socket, no action is required. If the server is not running, you have probably encountered a known problem with the NFS lock manager on Sun 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 when this file has been removed.
35 Error
36 Error
The database is not the expected version. You may need to run an upgrade program. AR System server (arserverd) expects a different version of the AR System database than the version being referenced. AR System server cannot run against an unknown version of AR System database. Error occurred while accessing one of the debug trace files. The system debugging mode has been activated, and the system cannot access one of the debugging trace flags. The associated message provides details about the failure. To correct the problem, see the message. The system continues to run, but debug tracing to the file is disabled.
37 Error
38 Error
Filter or escalation set field process returned an 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 is displayed with this error. The error terminates the operation being performed, and the current transaction is rejected. No update to the database occurs. Filter or escalation set field process timed out before completion (value not changed). 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 filter continued, and the operation was performed in the database. The value for the associated field was not changed. The administrator has control over the time-out setting for the process. It can be configured, within Remedy Administrator, to be from one to 20 seconds with a default of five seconds.
39 Error
41 Warning
Unrecognized command line argumentignoring command line and continuing. 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. Server is not licensed to run with multiple-RPC socketsignoring setting and continuing. 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. A character field with a $MENU$ pattern is failing due to errors retrieving the character menu to validate against. 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 that is 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.
42 Warning 43 Error
44 Error
You are already at the limit of the number of forms allowed for your server license. 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 new form.
21
46 Error
Message action and Log action in else branch are not supported for escalations. 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. Email notification operation timed out before completion. The system was blocked while attempting 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. It is likely that the mail will be delivered when the mail system recovers. Internal error: The maximum response value in the control record is too small (minimum of 4096 bytes). This error is reporting an internal RPC failure. A client is accessing the server and has specified insufficient space for the response to be returned.
47 Warning
48 Error
49 Error 50 Warning
Internal error: The request ID for a multipiece RPC response is invalid. This error is reporting an internal RPC failure. A client is accessing the server and has specified an invalid identifier for the requested information. Only the administrator has access to this field. The field is accessible only to administrators. No permission settings have been 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 be able to access and manipulate this field, you must assign permissions to the field. Field ID specified does not exist in this form. A retrieval operation was attempted for the field identified by the indicated ID, but there is no field with that ID in the target form. The data for the correctly identified fields was retrieved. The field is a core system field and cannot be changed. You attempted 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. Administrator access required to get permission information. 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.
51 Warning
52 Warning
53 Warning
54 Warning
No changes have been specified for the update operation. You specified a Modify operation to the system, but there were no modifications specified. If the command is being executed programmatically and there is potential for set operations with no changes to be specified, this warning can be trapped and ignored within your program. The following item was not imported: <item>. You attempted 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. Correct the error, and try to import the item again. Entry does not exist on form. You attempted 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 may have been deleted by another user. One or more fields in the statistic operation had a NULL value. Those values are excluded from the statistics computation. 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 values that are not NULL are included in the computation.
55 Warning
56 Warning
57 Warning
59 Warning
User does not existsuccessfully connected as a guest user (type user name exactly including capitalization). You attempted 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 Warning 61 Warning
You do not have read access to this field. You attempted 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. You do not have read access (for this entry) to this field. You attempted 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.
23
62 Warning
You do not have access to the requested entry. You attempted 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 access control restrictions. Those values are excluded from the statistics computation. You attempted 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 or escalation action cannot write to the specified log fileaction created but file must be verified. 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 about why the file cannot be created. 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
The filter definition contains multiple form links. This is an older definition, and the filter is linked only to the first form in the list. 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 refer to a single form. If you need filters with the same actions, create multiple filters.
66 Warning
The search matched more than the maximum number of entries specified for retrieval returned entries are limited to the specified maximum. 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 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 Warning
Attempt to open menu file failedcharacter menu is incomplete. A character menu that references a file was being expanded, and the specified file could not be accessed. An associated message contains details about why the file could not be accessed. The character menu being expanded is incomplete, with no menu where the file was to be expanded. Correct the problem, and expand the menu again.
68 Warning
RPC environment variable is out of valid range (390600, 390603, 390619 - 390669, 390680 390695). NOTE: The value 390603 and the range 390619 - 390669 are specialty servers and may have restricted functionality. 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. Operation was completed successfully, but the SQL view is not in place. While attempting 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 an SQL view for this form, which is needed only if you are directly accessing the SQL database by using the SQL view.
One or more fields in this form reference character menus that no longer exist. The character menu referenced by one or more fields in this form does not exist. There is no character menu for the field, even though the system has a menu defined for it. Group Access is not definedonly the administrator has access to this active link. The active link is accessible only to Administrators. No permission settings have been 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 be able to perform this active link, administrators must assign permissions to the active link. The search matched more than the maximum number of entries specified by the server returned entries are limited to the specified maximum. The 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.
72 Warning
73 Warning
A value change is pending on the Submitter Mode settingchange will take effect the next time the server is started. A change to the Submitter mode setting will not take effect until the AR System is shut down and restarted. It is a pending change until the next restart.
25
74 Warning
A duplicate index has been specifiedduplicate was omitted and indexes were created. You specified the same index twice for a form. You cannot create duplicate indexes. This message is a warning about the duplicate, but processing has been 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 present on every form. You receive this error if you attempt 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 a token is available. You are assigned a floating write license, but there are no floating write license tokens 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 Note
A write token has become available and has been allocated to youaccess has been upgraded to write access. You have previously received Warning 75. A floating write token has become available, and it has been allocated to you. You now have full read and write access within your permissions.
77 Warning
No free-floating Full Text Search Option license tokens are available. Currently accessing the system without full text search (FTS) capability. License will upgrade when a token is available. You are assigned a floating, Full Text Search Option license, but there are no floating, Full Text Search Option tokens 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 will use the default database search capability on all fields, including the fields that are FTS indexed.
78 Note
A Full Text Search Option license token has become available and has been allocated to youaccess has been upgraded to allow full text searching. 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 has become available, and it has been allocated to you. You now have full text search (FTS) access within your permissions.
79 Warning
Request for unique setting on database index has been ignored for fields of this type. 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 Warning
Delete column failedcolumn contents set to NULL and column renamed. You attempted to delete a field from a form. The delete operation failed, and the 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 the data values to NULL. The field is a Distributed Server Option (DSO) reserved field that can be updated only by the DSO process. Some of the DSO reserved fields cannot be changed except by arservdsd. An attempt was made to change one of these reserved fields.
81 Warning
82 Warning
One or more indexes were updated to remove reference to the fieldlength was changed so that it is not allowed in an index. A change to the limits definition of a field has been made. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is used in one or more indexes for the current form. A field with a length of greater than 255 bytes cannot be used in an index. To prevent an error, the reference to the field that cannot be in an index has been removed from the index definition for the form, and the remaining indexes have been rebuilt.
83 Warning
The query list fields definition of the form has been updated to remove references to the fieldthe length was changed so that it is not allowed in the query list. A change to the limits definition of a field has been made. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (or unlimited). This field is used in the list of fields defined to be returned in the results list. A field with a length of greater than 255 bytes cannot be used in the results list. To prevent an error, the reference to the field that cannot be in the results list has been removed from the results list definition.
84 Warning
The sort list definition of the forms has been updated to remove reference to the fieldthe length was changed so that it is not allowed in the sort list. A change to the limits definition of a field has been made. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is used in the sort list. A field with a length of greater than 255 bytes cannot be used in the sort list. To prevent an error, the reference to the field that cannot be in the sort list has been removed from the sort list definition.
85 Warning
Indexes are ignored for join formsbuild the index on the base tables. You cannot create indexes on a join form. To index a field, define the index on the base form.
27
90 Error
Cannot establish a network connection to the AR System server. The server is inaccessible due to one of the following reasons: There is a connectivity problem with the network. Issue a ping command to the server. If the problem is with the network connection, you must solve all network connectivity problems before you can use the AR System server. When the network connection problem is corrected, you can successfully connect to the server. If there is no network connectivity problem, 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 (for UNIX) or Login Information window (for Windows) on your machine to verify that the server is registered as one of the servers you can access. If no entry is present in the file or window, add the entry. If the connection is still unsuccessful after you have eliminated the above causes, shut down and restart Remedy User. The server may have been temporarily inaccessible.
91 Error 92 Error
RPC call failed. This protocol error occurs when the client and the servers protocol definitions do not match. Time-out during database updatethe operation has been accepted by the server and will usually be completed successfully. A time-out occurred while data or structures in the database were being updated. In most cases, the operation will still be performed after the time-out; however, you may need to reattempt the operation.
93 Error
Time-out during data retrieval due to busy servertry the operation again. A time-out occurred while information was being retrieved from the data dictionary, because the server was busy performing other operations. Try the operation again when there is less activity on the server. Time-out during database searchconsider using more specific search criteria. A time-out occurred while data was being retrieved from the server. This error is often caused by poorly specified search criteria. Review and, if necessary, modify your search criteria, and try the operation again. RPC and sockets initialization failure. The attempt to initialize the RPC and sockets subsystems has failed. Make sure the proper sockets libraries are present. Feature not supported by this AR System client. Some features cannot be fully mapped from earlier versions of Remedy User and Remedy Administrator.
94 Error
95 Error 96 Warning
97 Error
Connection has been attempted to two unlicensed servers. You can connect to only one unlicensed server in a session. Connection to the second server is denied. The system allows you to connect to a single unlicensed server at any time. You can connect to any number of licensed servers. Either you have specified multiple unlicensed servers to connect to or workflow is accessing a second unlicensed server. You must license your servers to be able to connect to them at the same time from a single client tool.
98 Error
The Administrator Command feature is no longer supported. 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. Two servers have been encountered with the same AR System server IDneither will be accessible until one is shut down and the tools started again. Two servers in your environment have been encountered that have the same AR System server ID. Both servers are disabled until the license conflict is resolved.
99 Error
100 Error 101 Error
Request ID parameter is empty. The operation being performed requires the request ID to be specified, but the parameter was not supplied. Try the operation again, this time specifying the request ID for the entry. Request ID parameter value is longer than the maximum allowed length. The request ID specified for the Request ID parameter was longer than the maximum length allowed (AR_MAX_ENTRYID_SIZE, 15 characters). Verify the request ID of the entry, and try the operation again. Remember that character strings must be terminated by a 0 (zero) character. Name parameter (or name field in a parameter) is empty. The operation being performed requires a name specification for an item, but no name was specified. Specify a value for the name parameter, and try the operation again. Name parameter (or name field in a parameter) is longer than the maximum allowed length. The name specified was longer than the maximum length allowed (AR_MAX_NAME_SIZE, 30 characters). Verify the name of the item, and try the operation again. Remember that character strings must be terminated by a 0 (zero) character. Field or value list item is empty. 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. NULL pointer for result list. 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.
102 Error 103 Error
104 Error 105 Error
29
106 Error 107 Error 108 Error
Request ID list is empty. The list of requests selected to perform the statistical operation on is NULL or empty. Specify a list of one or more requests to perform the statistical operation. Statistics list is empty. The list of operations to be performed in this statistical operation is NULL or empty. Specify a list of one or more operations to be performed. Field display definition is incorrect. One or more of the fields in the display structure for the field is invalid. You may have specified an illegal display type, label positioning, or option. Verify that the include file ar.h has legal values for these fields. File name is longer than maximum allowed file name. The file name parameter 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. Unrecognized data type. 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. Unrecognized data type for default value. 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. Character menu definition is empty. 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. Name list parameter is empty. 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. Entry error in the name list. 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.
109 Error
110 Error
111 Error
112 Error
113 Error 114 Error
115 Error
Operation mask parameter is out of bounds. The filter operation set parameter is invalid. This parameter is a mask of one or more operations on which the filter will potentially execute. Either this parameter has an empty mask or has values outside the allowed limits on the mask. Verify that the #define statements in the include file ar.h have legal values for this field. Filter does not have an action defined. The action field for a filter is either NULL or empty. A filter must define at least one action. Command string is empty or longer than the maximum allowed length. 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 within an active link, filter, or escalation, the command string may contain parameters. When they are expanded, the command line may expand to 4,096 bytes. The unexpanded line is limited by the value defined by AR_MAX_COMMAND_SIZE.
116 Error 117 Error
118 Error
Unrecognized or inappropriate value for field option. 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_FIELDOPTION_DISPLAY. Unrecognized create mode. 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. Unsupported data type in this client. 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 try this request again. Entry error in the Request ID list. 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. ARServerInfoRequestList structure is empty. 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.
119 Error
120 Error 121 Error
122 Error
31
123 Error 124 Error 125 Error 126 Error 127 Error 128 Error 129 Error
Unrecognized server information tag. 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 the valid codes that can be specified. Entry error in the field/value list. One of the items specified in the field or value list contains an error. An associated error message contains details about the error. Entry error in the statistics list. One of the entries specified in the statistics operation list is invalid. An associated error message contains details about the error. Unrecognized statistics operation. 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 the valid operation codes. Entry error in the permission list. One of the items in the permission list is invalid. An associated error message contains details about the error. Unrecognized permission tag. 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. Field limit definition is invalid. The field limit specified for this field is invalid. For a numeric field, make sure that the high range is greater than the low range. For a character field, make sure that the pattern is within the size limit of the field. Also, verify that the specified character menu, the menu style setting, and the match operation setting are legal. For a selection field, verify that the value is a legal value for the field.
Entry error in the character menu. One of the entries in the character menu is invalid. A child menu tag was assigned but there is no child menu, or a leaf item was specified and there is no leaf string. Unrecognized character menu item type. 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 the valid character menu type tags. Structure item is empty. 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 Error 134 Error 135 Error 136 Error
Unrecognized structure item tag. One of the structure option tags is invalid. Verify that the #define statements in the include file ar.h have a list of all the valid structure tags. Entry error in the structure item list. One of the items specified in the structure list is invalid. An associated error message contains details about the error. Unrecognized filter action type. One of the filter action codes is not recognized. Verify that the #define statements in the include file ar.h have a list of all the filter action type tags. Unrecognized notify mechanism. 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 the allowed notify mechanisms. Unrecognized message type. 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 the valid message types. Filter, active link, or escalation message number must be greater than 10000. 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 have added to the system and ones that are from AR System. Option cannot change for core or reserved field that has a fixed options definition. The core fields of the system have restrictions on what changes are allowed. You are attempting a change to a characteristic of a core or reserved field that cannot be changed in the way you are requesting. Review the Developing AR System Applications: Basic guide for information about the restrictions for each of the core fields. A default must be active for the Status field. The Status field must have a default value. You are attempting to change the definition of the Status field, which will eliminate the default value and is not allowed. You can alter the number of states and change the default value, but you cannot eliminate it. Can use the Qualify None option only at the top level of a qualification. You have 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 is used to indicate no qualification. Restructure the call to remove the tag from the middle of the tree. Unrecognized operation in qualify conditions. The tag for one of the nodes in the qualify condition structure is invalid. Verify that the
137 Error 138 Error
139 Error
140 Error
141 Error
142 Error
#define statements in the include file ar.h have a list of all the valid tags.
33
143 Error 144 Error 145 Error 146 Error 147 Error 148 Error 149 Error 150 Error 151 Error 152 Error 153 Error
Relational operation is empty. The value portion of a relational operator qualification structure is NULL. Specify a value for a relational operation. Unrecognized relational operation. 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 the valid tags. Arithmetic operation is empty. The value portion of an arithmetic operator qualification structure is NULL. Specify information for an arithmetic operation. Unrecognized arithmetic operation. 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. ARFieldValueOrArithOp structure is empty. The value portion of a field, value, or arithmetic structure is NULL. Specify information for this structure. Unrecognized ARFieldValueOrArithOp structure tag. The tag for the type of the field, value, or arithmetic value is invalid. Verify the #define statements in the include file ar.h for a list of all the valid tags. A user name must be supplied in the control record. The name field of the ARControlStruct parameter is empty. Supply the name of an AR System user in this field. A server name must be supplied in the control record. The server field of the ARControlStruct parameter is empty. Supply the name of the server to reference in this field. Required form parameter is missing. 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. Entry error in the sort list. The value specified for the sort list parameter is invalid. An associated error message provides details about the error encountered. Unrecognized sort method. 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 Error
Malloc error in client library. The system encountered an error during a call to allocate memory space. The failure occurred on the client machine during processing of the call to or from the server. This error usually occurs when there are too many processes running or some processes have grown to occupy most or all of the available memory space on your client machine. You can recover that memory space by shutting down unneeded processes. Restart processes that have been running for a while to recover space those applications may have leaked over time. Return buffer is NULL. The buffer that holds the return value of the call was passed a NULL value. For the call to return the data requested, there must be a parameter specified to hold a pointer to the result. Supply a value for this parameter. Input buffer is NULL. The buffer to hold the input value to the call was passed a NULL value. For this call to perform the requested operation, there must be a value specified for this parameter. Supply a pointer to the input buffer for this parameter. Field IDs below 100 are reserved for core fields. You have 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 that is greater than 100. Request ID field must contain at least 5 non-defaulted spaces. You have 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 will act 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 have specified for the field and the default value prefix leave less than 5 spaces.
155 Error
156 Error
157 Error
158 Error
160 Error
Decompression has failed. There was a failure in decompressing the data being processed, for example, when saving an attachment in the Save-Attachment Run Process filter command. The format of the compressed data was not correct. Invalid session identifier supplied in the control record. 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. Notify text is empty or too long. 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.
161 Error
162 Error
35
163 Error 165 Error
Unrecognized notify field ID tag. 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. Items specified are NULL pointers. A parameter has been 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 there are items, the value field must point to the items. If there are no items, the numItems field must be initialized to 0. Field default type and data type do not match. 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.
166 Error
167 Error
Field limit type and data type do not match. 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 there is no limit for the field. All other combinations are illegal.
168 Error
Error in one of the field or value assignments in the set fields action of a filter, active link, or escalation definition. 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 about the failure. Usually, the problem is an attempt to define an assignment between incompatible data types or to nonexistent fields.
169 Error
Execution order value is out of range. The execution order field of the filter, active link, or escalation definition contains a value that is 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 Error
Unrecognized status history tag. 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. Status history selection value is out of range for status definition. 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. Service was not started. 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. Language specified in the control record not recognizedusing default language on server. 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 that is 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 one of AR System tools, 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).
171 Error 172 Error
173 Error
174 Error
Display type specified is inappropriate for the data type. The display type value specified for this field is not compatible for the data type of the field. You must choose a display type that is appropriate, as shown: Display type AR_DISPLAY_TYPE_CHECKBOX supports data type AR_DATA_TYPE_ENUM Display type AR_DISPLAY_TYPE_CHOICEsupports data type AR_DATA_TYPE_ENUM Display type AR_DISPLAY_TYPE_NUMTEXTsupports data type AR_DATA_TYPE_INTEGER Display type AR_DISPLAY_TYPE_TEXTsupports 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
37
175 Error
The length or numRows value of the display parameter is out of range. 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 Error
Duplicate selection value exists in the selection or bitmask value list. 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. Cannot specify change access for a view-only group. You have 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. Field ID parameter is NULL; must be a pointer to memory. 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 will assign a value and return the result in this field. Pattern in a character limit is invalid. The pattern specified for a limit to the character field is not legal. 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]). Default value for a character type is longer than the maximum allowed length AR_MAX_DEFAULT_SIZE. 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 try the operation again. Character strings must be terminated by a 0 (zero) character.
177 Error
178 Error
179 Error
180 Error
181 Error
The ID specified for this field is in the reserved field range. 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 will return the ID assigned.
182 Error
Too many actions have been specified for this filter, active link, or escalation. 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. Duplicate group ID was specified in permission list. 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. Cannot specify a quotation mark in default value for Request ID field. 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. Cannot assign default value to system-supported core or reserved fields (except Request ID). You have 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 systemcontrolled 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. Cannot assign character menu to system-supported core or reserved fields. You have 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 systemcontrolled core fields cannot be assigned values by the user, so a character menu is not needed or allowed. Execute mask parameter is out of bounds. The execute mask is a bitmask of the conditions under which an active link will execute. The value you have 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.
183 Error
184 Error
185 Error
186 Error
187 Error
39
188 Error
Execute mask setting requires a field choice. The active link you have defined has the On Return or On Menu choice condition set in the execute mask, but there is no setting to indicate to which field to attach the operation. Specify the field where you want to attach the active link action. Active link does not have an action defined. The action field for an active link is either NULL or empty. An active link must define at least one action to be performed. Unrecognized active link action type. One of the active link action codes is not recognized. View the #define statements in the include file ar.h for a list of all the active link action type tags. Unrecognized assign type. The assign type tag is not recognized. View the #define statements in the include file ar.h for a list of all the assign type tags. Field or assignment list item is empty. 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. Entry error in the field or assignment list. One or more fields, or assignment items in the field or assignment list, encountered an error. See the associated message for details about the error. Unrecognized tag for filter, active link, or escalation set field action. The ARAssignFieldStruct structure tag is not recognized. Verify the #define statements in the include file ar.h for a list of all the ARAssignFieldStruct tags. Filter, active link, or escalation set field definition is missing. The field definition in the field or assignment structure is set to NULL. Supply a field definition value in this structure. Macro branch of active link action must include both a name and macro text. 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. Unrecognized keyword. 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.
189 Error 190 Error 191 Error 192 Error 193 Error 194 Error 195 Error 196 Error 197 Error
198 Error
Cannot use the $DEFAULT$ keyword as a default value or in a qualification. 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 there is an arithmetic operation 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 within qualifications.
199 Error
Missing or blank name for a macro parameter in the active link action. 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. Macro value string is longer than the maximum length allowed. 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 try the operation again. Character strings must be terminated by a \0 character. Unrecognized or misused tag for field/value definition. 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. Notify user name is longer than the maximum size allowed for the name. The name specified for the user to be notified is too long (the maximum is defined by AR_MAX_NAME_SIZE, 30 bytes). Specify a name that is within the length restrictions. Value list is empty. The value list parameter for this call is NULL or contains 0 items. This operation requires at least one value item to be specified. Notify priority is out of range (must be 1 to 10). 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. Unrecognized character menu type. 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. Unrecognized character menu refresh code. 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.
200 Error
206 Error 207 Error
41
208 Error 209 Error
Unrecognized character menu file location. 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. File name for a character menu is NULL, empty, or too long. 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. Total length of all fields involved in an index is greater than maximum allowed length. The sum of the length of all fields that are specified for the index is greater than the maximum that is 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. Either zero or greater than the maximum number of allowed fields are specified in a single index. 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.
210 Warning
211 Warning
212 Warning
Display list is empty. 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. Qualifier parameter is NULLmust be a pointer to memory. 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. One of the structures in the list of fields to display in the query list is invalid. One of the items in the list of field definitions is invalid. This list of field definitions is for fields that are displayed in the query list. See the associated error message for details about the error. ARServerInfoList structure is empty. 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. Server information associated with this tag cannot be updated. The server information for the indicated tag is read-only data. You are not allowed to update this information. Try the operation again, setting only values that can be updated. Server information associated with this tag cannot be retrieved. The server information for the indicated tag is write-only data. You are not allowed to view this information. Try the operation again, requesting only values that can be retrieved (viewed).
216 Warning 217 Warning 218 Warning
219 Warning
Server information data associated with this tag uses an incompatible data type. The server information for the indicated tag represents information that has a different data type than the type specified in the update operation. Try the operation again, specifying the correct data type for the value. Local variable number is out of range (must be 0 to 10). The code specified for a local variable is outside the legal range for local variables. Specify a number between 0 and 10. Query value structure is empty. 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. Query value structure item contains an 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. Unrecognized value for the query value multimatch code. The tag specified for the action to take if there are multiple matches in the ARQueryValueStruct structure is not a legal tag. Cannot index a diary field, an unlimited length field, or a field with a maximum length over 255 bytes. Fields that have lengths longer than 255 bytes (including diary fields and unlimited length character fields) cannot be indexed. You have 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.
220 Error 221 Error
225 Error
Set fields actions that reference entries in other forms can only reference forms on the same server in a filter or escalation. A Set Fields action within 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 have defined a reference to a form on a different server. You must 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 Error
Type of field, value, or arithmetic operation is not supported on the GetListEntry operation. The type of value specified in the ARFieldValueOrArithStruct structure is not allowed within a query list. The tag refers to an operation that is supported only during a filter or active link operation. Unrecognized value for set focus characteristic. 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.
227 Error
43
228 Error 229 Error
Unrecognized value for set access option characteristic. 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. Function definition is empty. 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. Unrecognized function code specified. 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. Parameter list for a function is empty. 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 there are no parameters, the parameter list can be NULL, but the count of parameters must be set to 0. The types of the values in a value set are not compatible. The data types of the values in a value set are not compatible. All the types must be the same or compatible types. Wrong number of parameters or invalid parameter values specified in function for the field. 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. Value specified for the filter or escalation set fields process time-out is outside the valid range of 1 to 20 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 20 seconds. Try the operation again with the value in this range.
230 Error 231 Error
232 Error 233 Error
234 Error
235 Error 236 Error
Unrecognized code for user list type. 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. Value specified for the license time-out must be 1 or greater (in hours). 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 Error
Value specified for DDE service name or topic is missing or is larger than the maximum allowed length. 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.
Value for DDE item is larger than the maximum allowed length. The value specified in the DDE item field is larger than the maximum allowed (32767 bytes). Verify the value, and correct if necessary. Unrecognized value set for DDE action code. 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. Cannot specify a diary field, a character field with unlimited length or maximum length over 255 bytes (254 bytes for DB2), or Status History as a sort field. 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 have specified a sort that includes a field that meets these criteria. Specify a sort list that does not include this field. For DB2 databases, the limit is 254 bytes.
241 Error
Cannot specify a diary field, a character field with unlimited length (or maximum length over 255 bytes), or Status History as a field in a Get List description. 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 operation. You have specified a list that includes a field that meets these criteria. Remove this field from the list.
242 Error 243 Error
Type of field, value, or arithmetic operation is supported only for a filter qualification. The type of value specified in the ARFieldValueOrArithStruct structure is allowed only within a filter qualification. Specify a tag that is allowed outside of a filter qualification. DDE definition is empty. 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. Value specified for DDE path to program is missing or is larger than the maximum allowed length. 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.
244 Error
45
246 Error
Invalid day format. 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. Invalid interval time. The format specified for the time 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. Invalid day selection. 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. Invalid hour selection. The format specified for the hour 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. Invalid minute selection. The format specified for the minute 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. Invalid value for enabling or disabling a filter, active link, or escalation. 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. Unrecognized group in the Subadministrator group list for the form. 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. Inappropriate group in the Subadministrator group list for the form in import. 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 will be completed successfully. You can define groups with the missing IDs, or you can update the definition of the form to remove the undefined IDs.
247 Error
248 Error
249 Error
250 Error
251 Error 252 Error 253 Warning
254 Error
Subject line is longer than the maximum length allowed. 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 try the operation again. The character strings must be terminated by a 0 (zero) character.
Unrecognized submitter mode. 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. Unrecognized server statistics tag. 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. Duplicate tag used for several items within the display list. A display tag to identify the view desired is not unique. There are two or more instances where the same display tag is used. Each display tag must be unique. Correct the definition to supply unique tags. 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 390621 through 390634, 390636 through 390669, or 390680 through 390694 (private servers), inclusive. For more information about using RPC sockets with DSO, see the Remedy DSO Administrators Guide.
258 Error
259 Error
Unrecognized no match code. The code specified as the no match code (the action to take when there are no matches to the values within a Set Fields action) is not recognized. View the #define statements in the include file ar.h for a list of all the no match codes. Unrecognized multiple match code. The code specified as the multiple match code (the action to take when there are multiple matches to the values within a Set Fields action) is not recognized. Verify the #define statements in the include file ar.h for a list of all the multiple match codes. SQL command is NULL or empty. The SQL command pointer is NULL or points to an empty string. To define an operation that will execute an SQL command, specify the command, and set this structure to point to it. Cannot specify a diary field, a character field with unlimited length (or maximum length over 255 bytes), or Status History as a field to group by. Fields that have lengths over 255 bytes (including diary fields, unlimited length character fields, and the Status History field) cannot be specified as fields to group by. You have specified a grouping that includes a field that meets these criteria. Specify a grouping that does not include this field.
260 Error
261 Error 262 Error
47
263 Error
Unrecognized save login code. 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 not recognized. Verify the definitions in the include file ar.h for a list of the save login codes. Server name for a character menu is empty or is too long. 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. Compound form structure is empty. The compound form structure is empty or has missing pieces. When defining a join or view form, this structure is required. Invalid join member form name. 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. Invalid join form qualification. 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. Invalid view form definition. 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. Invalid form type in compound form structure. 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. Field mapping structure is empty. The field mapping structure is required when defining a data field on a join or view form. For this call, the structure is empty. Specify appropriate contents for this structure. Invalid base form index in a join field mapping structure. The index to which a form field is tied is invalid. When defining a join field reference within a join form, specify an index (of 0 or 1) indicating whether the field is tied to a field in the primary or the secondary form. The value of the index is not 0 or 1 in this case. Change the index to indicate the appropriate form.
267 Error
268 Error
269 Error
270 Error 271 Error
272 Error
Invalid external table name in a view field mapping structure. The table name identified in the view form definition is not a legal table name, or the table does not exist. The table referenced in a view form must exist before the view form can be created. Invalid field mapping type. The field type in the field mapping specified for a field in a compound form is not recognized. View the #define statements in the include file ar.h for a list of the recognized field types. Invalid compound form structure change. 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. Index not allowed in this type of form. 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. The form is referenced by a join form as a base form. 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 will delete the form despite the dependency. The join forms dependent on this form will also be deleted.
273 Error
274 Error 275 Error
276 Error
277 Error
The field is referenced by a join form as a base field. 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 will delete the field despite the dependency. The fields in the join forms that are dependent on this field will also be deleted.
278 Error
The field is referenced in the join qualifier of a join form of which this form is a member. 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 will delete the field despite the dependency. The fields in the join forms that are dependent on this field will also be deleted.
279 Error
Submit and Delete entry operations are not supported on join forms. If accessing a join form, the Delete and Submit operations on entries are not supported.
49
281 Error
AR System server does not support multiple links to the same button. In older versions of the AR System server, this error message was returned because you attempted to attach additional active links to a button that already had an active link associated with it. In these older versions, a button could only have one active link associated with it. A form can have only one default view and there is another view defined as the default for this form. 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 there is another view that is set as the default. Remove the default property setting from the view that currently contains the setting before giving it to another view.
282 Error
283 Error
AR System server does not support the specified dataType. This error message is returned due to a RPC procedure mapping error between the client and the server. You cannot create, get, or set this field on this version of the AR System server, as it is not supported. Escalation does not have an action defined. The action field for an escalation is either NULL or empty. An escalation must define at least one action. A field referenced in the qualification is not a data field. A qualification contains a reference to a non-data field that is 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. Display only fields cannot be included in a query to the database. 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. Status field must be created before status history field can be created. This error is returned because, when you create a status history field in a schema or a join schema, a status field must already be available. The requested operation is not supported on the server. A newer version of an AR System client is attempting an operation on an older version AR System Server that is not available 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.
284 Error 285 Error
286 Error
287 Error 288 Error
289 Error
Cannot create nested outer join form in Sybase or SQL Server. 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. Message text is empty or too long. 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 may contain parameter references that are expanded before the message is delivered. The expanded message can contain as many as 4096 characters.
291 Error
292 Error 293 Error
Invalid item list for entry existence. You must provide an array for server to return request existence information. Expected column data missing from multiple entries. This error is an internal error. This error message is returned only when there is a software bug in field value list processing in a GetMultipleEntries( ) call. As an input parameter to call GetMultipleEntries( ), the caller needs to provide a 2 dimension array to hold the request value. If the internal column index is greater than the array size, this error is returned. Requested number of multiple entries exceeds maximum allowed. Each GetMultipleEntries( ) call can only return a maximum of 100 requests. If there are more than 100 requests specified in the entryId list parameter of the GetMultipleEntries( ) call, this error message is returned. File pointer is NULL or not a valid file pointer. 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. Invalid support file type. The file type specified for a support file in a compound form is not recognized. View the
294 Error
#define statements in the include file ar.h for a list of the recognized file types.
Administrator released license too recently. The administrator has released this users license too recently. An administrator can release a users license only once every two hours. Too many filters processed during this operation. There is a 10,000 filter limit per operation. This error occurs when more than 10,000 filters are run from a single operation. This error may be caused by a push fields operation that runs recursive filters. See the Developing AR System Applications: Basic guide for more information about filters and push fields actions.
51
299 Error
Too many levels in filter processing. There is a limit of 25 levels for filter processing. This limit exists to protect against recursive filter actions. For example, a filter that includes a push fields action, with that action launching another filter with a push fields action, with that action launching another filter with a push fields action, and so on. See the Developing AR System Applications: Basic guide for more information about filter actions and push fields.
300 Error
Malloc failed on server. The system encountered an error during a call to allocate space. The failure occurred on the server machine during processing of a call from the client. In general, this error occurs when there are too many processes running or some processes have grown to occupy most or all of the available memory on your server machine. Recover that memory by shutting down unneeded processes. Restart processes that have been running for a while to help recover space those applications have leaked over time. Error while writing to a file. An error occurred while writing to the indicated file. An accompanying message from the operating system provides details about the failure. Determine why the write failed, and correct the problem before attempting the command again. Entry does not exist in database. No entry exists in the database with the Request ID you specified. The Request ID specified is invalid, or the entry has been deleted by another user during the time you were processing it. Form does not exist on server. There is no form with the indicated name on the server. The name specified is incorrect, or the desired form is on another server. Must have administrator permissions to perform this operation. 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, you must log in as a user who has administrative permission to the form you want to update.
301 Error
302 Error
303 Error 304 Error
305 Error
Next available ID produces a request ID that overflows Request ID fieldcontact the administrator. 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 have 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 there is a default value, you can change the default value to a shorter string. As a final option, contact Remedy Customer Support to help you reset the next request ID counter. Do not attempt this task yourself, because numerous actions must be performed, in sequence, to make this change successful.
306 Error
Value does not fall within the limits specified for the field. Limits are specified for the indicated field. These limits may 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 Error
Required field (without a default) not specified. During submission of an 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 the following 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 Error
Duplicate field in the definition. 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. Entry has been modified since the get time. The entry you are attempting to modify has been modified by another user since the last time you retrieved the definition. The changes made may impact your changes. You have the option of overriding this error and applying the changes. If you apply the changes (and override the error), all changes you make will take precedence over the changes made by the previous user. If you do not apply your changes, the previous users changes are retained.
309 Error
53
310 Error
Value has wrong data type for the field. 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 Error
Field ID is not related to this form. The field ID references a field that is not defined for the current form. The operation you are attempting is against the wrong form, against the wrong server, or the structure of the form has been changed to eliminate the field ID from the form. Change to the correct form, to the correct server, or remove the Field Name from the Field Sort Order list to complete the operation.
312 Error
Data types are not appropriate for arithmetic operation. The data types of the fields used in an arithmetic operation are not consistent with the operations allowed for that operation. Review the Developing AR System Applications: Basic guide for information about the allowed data types of operations. Data types are not appropriate for relational operation. The data types of the fields used in a relational operation are not consistent with the operations allowed for that operation. See the Developing AR System Applications: Basic guide for information about the allowed data types of operations. Field does not exist on current form. The field is not related to the current form. The operation you are attempting is against the wrong form, against the wrong server, or the structure of the form has been changed to eliminate the field ID from the form. Change to the correct form, to the correct server, or remove the ID from the field list to complete the operation.
313 Error
314 Error
315 Error
Must override form or field (where entries or data still exist) to delete. You are attempting to delete a form or field that contains data. You must explicitly override this error in order for the operation to succeed. By default, the system will delete structures only when no data is lost.
316 Error
Failure with a temporary file. During processing, an error occurred while attempting to use a temporary file. An associated error message contains operating system details about the failure. By default, temporary files used by the server are created in the directory /usr/tmp (for UNIX) or \tmp (for Windows). Verify that this directory is present and is writable by the user running the arserverd program. Also verify that the temporary directory has been redirected and that the directory specified 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 Error 318 Error
Duplicate form name. 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 so there is no conflict. Group does not exist on server. No group with the indicated ID exists on this server. The group ID specified is incorrect, or the group with this ID has been changed or deleted from the system. Determine what groups are available. If the group has had its ID 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. Request for length change of core or reserved field is out of limits. 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 Developing AR System Applications: Basic guide for information about the use and limits of the core fields. Character menu does not exist on server. The character menu is not defined on the current server. The operation you are attempting is against the wrong server, or there is no character menu by that name defined. Change to the correct server (if the former), or specify an existing character menu (if the latter).
319 Error
320 Error
321 Error 322 Error
Too many levels in character menu definition. Menus can contain a maximum of 15 levels. You have specified a menu that contains more than 15 levels at some point within its hierarchy. Invalid hierarchy in character menu definition. A character menu definition was encountered where the definition of menu items and children do not form a consistent tree structure. You have definitions where there is no parent item for some children items.
55
323 Error
Filter does not exist on server. The filter is not defined on the current server. The operation you are attempting is against the wrong server, or there is no filter defined by that name. Change to the correct server (if the former), or specify an existing filter (if the latter).
325 Error 326 Error
Duplicate filter name. 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. Required field cannot be reset to a NULL value. You are attempting 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. Cannot perform statistic operation on the data type of the target. 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 are attempting is not compatible with these limitations. Invalid password or authentication string for an existing user The password you have specified for the user name is not recognized. The problem can be either with the password or with the authentication string (if using NT authentication, the authentication string is the NT domain) or both. Enter the password defined for this user name to access the system as that user. You do not have write access to field. You do not have write (change) access to a field that you are attempting to change. You must have write access to write into that field. You do not have write access for this entry to this field. You do not have write (change) access to a field that you are attempting to change on this entry (request). You have write access to this field for requests that are assigned to you (or to a group you are a member of) or were 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. You do not have write access (at create time) to field. 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 that are assigned to you (or a group you are a member of), or were 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.
327 Error
329 Error
330 Error 331 Error
332 Error
333 Error 334 Error
You have no access to field. You do not have access (read or write) to the field that you are attempting to access. You must have access to a field to read or change its values. An AR System reserved field definition is incorrect. There are several reserved field definitions that are reserved for Remedy. You have specified one of these fields with settings that are incompatible with the limits set on the definition of those fields by Remedy. See the discussion of the AR System core and reserved fields in the Developing AR System Applications: Basic guide. Format for an AR System reserved field is invalid. 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 Developing AR System Applications: Basic guide for details on the allowed data format. Cannot assign a user to the special Submitter (3), Assignee (4), Assignee Group (7), Dynamic, or Computed groups. 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 per-instance 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.
335 Error
336 Error
337 Error
You have reached the maximum number of database entries permitted with this version of the Action Request System. To purchase the unrestricted version, contact your AR System sales representative or visit www.remedy.com. This version of AR System has a maximum limit of 2000 entries per form on an SQL database. To increase data storage capabilities, contact your AR System sales representative or authorized reseller, or visit www.remedy.com.
338 Error
Duplicate request ID for merged item, but Create New ID was not specified. You are merging requests into a form from another source. You have specified a request ID in the merge operation that conflicts with an existing ID in the system. You have not specified to create a new ID in case of conflict; therefore, the merge operation has failed. To merge the new request, specify the option to create new IDs, or delete the existing request before merging the new one.
57
339 Error
Incorrect format for a diary field. You specified a diary field in the merge operation, and the format for 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.
340 Error
Incorrect format for the Status History field. You specified the Status History field in the merge operation, and the format for 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. Cannot run the requested process. 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. There may be an associated error that contains more details. Determine why the process did not run, and, if possible, correct the circumstances. Then try the operation again.
341 Error
342 Error
Cannot find or open the directory file. AR System directory file could not be opened. An associated error message describes why the ar file (/etc/ar for UNIX or <ar_config_dir>\ar for Windows) could not be opened. This file contains the name of each AR System server that this client will try to connect to. The file must be present to identify which servers to use. Error in definition for a filter. An error occurred when loading a filter definition from the database. An internal error occurred, or manual changes have been made to the contents of the database. Group type or category conflict between two groups with the same group ID. Two groups have been 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 there are two groups with 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.
343 Error 344 Error
345 Error
Duplicate active link name. 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 Error
Active link does not exist on server. The active link is not defined on the current server. The operation you are attempting is against the wrong server, or there is no active link defined by that name. Change to the correct server (if the former), or specify an existing active link (if the latter). You have no access to active link. 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. Group cache structure is emptyno access to database is possible. 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. Cannot delete a core field. You have 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. Attempt to divide by zero (0) in arithmetic operation. During an arithmetic operation, the system detected a divide by 0. Restructure your queries to avoid this illegal operation. Cannot specify qualification on password field. The password field is a write-only field. To maintain security, you cannot specify a qualification on the password field. 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. During a filter or escalation action, there was an attempt to notify the submitter or assignee of the request. 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.
347 Error
348 Error
349 Error
353 Error
You have no access to form. 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.
59
355 Error 356 Error
Must be administrator to access the filter. Only users with administrator permission can access (for read or change) a filter definition. The current user does not have administrator permission. Duplicate character menu name. 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. Character menu contains too many items on one level (maximum 99). 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. Error while accessing a menu file on the server. An error occurred while trying to access a menu definition file that is located on the server. An associated error message contains information about the reason the file could not be accessed. After you correct the error, the menu will be available. Set, Create, and Delete operations to structures are supported only on RPC socket 390600. 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. No currency conversion ratio exists for the requested conversion. 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. An unqualified search was issued, and the server has been configured to disallow unqualified searches. Specify some search criteria to perform a search on this form. This server has been configured to not allow unqualified searches, and you have issued an unqualified search. Specify some qualifying criteria in one or more fields to limit the amount of data being returned from the server.
357 Error
358 Error
359 Error
360 Error
361 Error
363 Error
Required field assigned $DEFAULT$, but there is no default value for the field. 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: Supply a value for this field. 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 Error
Diary field cannot be set to a NULL value in a filter or escalation. The filter definition contains a Set Fields action where a diary field has been 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. Escalation does not exist on server. The escalation is not defined on the current server. The operation you are attempting is against the wrong server, or there is no escalation defined by that name. Change to the correct server (if the former), or specify an existing escalation (if the latter).
366 Error
Duplicate escalation name. 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. Error in definition for an escalation. An error occurred when loading an escalation definition from the database. An internal error occurred, or manual changes have been made to the contents of the database. Must be administrator to access the escalation. Only users with administrator permission may access (for read or change) an escalation definition. The current user does not have access to the escalation. No form ID for the form. There was no form ID found in the file form.ar. This is usually caused by a manual edit to the form.ar file or by a file that is 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. You cannot change the value of the Submitter fieldthe Submitter Mode of the system is configured to be locked. The system can be configured with a Submitter Mode of Locked or Changeable. You have 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).
371 Error
372 Error
Could not create alert event. The server was unable to create an alert event request in the database. An associated error message contains details about the failure. Possible causes are as follows: The server was unable to 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 could not be added to the database.
61
373 Error
Must be administrator to access the distributed mapping. Only users with administrator privileges can read or change a distributed mapping definition. The current user attempted to access a distributed mapping and does not have administrator privileges. Distributed mapping does not exist on server. The specified distributed mapping does not exist on the current server. One of these conditions exists: The operation you are attempting is against the wrong server. Change to the correct server, and try the operation again. No distributed mapping with the specified name could be found. Specify an existing distributed mapping, and try the operation again.
374 Error
375 Error 376 Error
Duplicate distributed mapping name. 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. Cannot update this entrythis distributed entry is not the master copy. In a distributed environment, you can update only one entry (marked as the current master) in a chain. You attempted to update a copy other than the master. Perform the update on the current master copy of the entry. The distributed or application operation specified in the filter Run Process action contains mismatched quotation marks. 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 amount of quotation marks exists (there is not an even number of open and closed single or double quotation marks). 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. Attempt the operation again, and use the correct command line syntax.
377 Error
378 Error
Must be Distributed Server to perform this operation. You must be the user (process) Distributed Server to run the specified delete operation against the Distributed Server Pending and Distributed Server Mapping forms. The distributed forms are part of the system structure and must not be deleted or modified. To delete one or both of these forms in Remedy Administrator, select the forms for deletion, and ignore the system warning related to the forms. Problem encountered during creation of one of the distributed forms. 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 about the problem. Correct the reason for the failure, and restart the arserverd process (or send a SIGHUP signal) to re-create the forms.
379 Error
380 Error
No item matches filter conditionsthis operation has been defined so that no match generates an error. 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 Error
Multiple entries match filter conditionsthis 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 Error
The values for this entry violate a unique index that has been defined for this form. The administrator has 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. File menu contains too many items on one level (maximum 1000). 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. The name specified contains an invalid character. Only printable characters are allowed. The name contains a control character. Object names can contain only printable characters. Change the name to remove the control characters. The same ID was specified several times in a multiple structure operation API calleach ID specified for this call must be unique. Multiple API callsthose that allow you to perform a set of operations in a single calldo not support specifying the same ID several times within the same call. If you specify two sets of changes or you specify to delete the same object several times, confusion about the desired operation can arise. Issue the operation again without specifying the same ID multiple times.
383 Error
384 Error 385 Error
386 Error
Exception occurred while handling previous exception. A nested filter exception error is returned because a filter exception condition is already being thrown.
63
387 Error
Updating this entry will violate join condition. When updating an entry in a join form, an option controls whether a field that is 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 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 will enforce the referential integrity and cause the update to be rejected. For more information, see the C API Reference Guide.
388 Error
VUI does not exist for the specified form. The VUI is not related to the specified form. The operation you are attempting is against the wrong form, against the wrong server, or the structure of the form has been changed to eliminate the VUI ID from the form. Change to the correct form, the correct server, or to a VUI ID that is associated with the form to complete the operation. Duplicate VUI for the form. 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 new 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.
389 Error
Cannot delete final VUI for a formall forms require at least one VUI. Every form must have at least one VUI defined. You are attempting to delete the only VUI for the form, and this is not allowed. Creation of VUI failed. A new VUI for the form could not be created. An associated error message contains details about the failure. Field or VUI name must be unique for the formthere is already a field or VUI using this name. The system requires that the name for all fields and VUIs on a form be unique. You have supplied a name that is already being used by another field or VUI. Change the name of this item, and try the operation again.
393 Error 394 Error
Status History field cannot be used as labelField or valueField in the query menu. Neither the Status History field nor any part of the Status History field can be used in a query style character menu. The administrator has set access for administrator users only. Please retry your operation later. AR System server has been 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 Error
The system has timed out while waiting for a process that is running on the server to return a value. An active link has specified that a process is to be run on the server to return a value to be assigned to a field. The server has 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 Error
Support file does not exist for the specified object. The support file is not related to the specified object. The operation you are attempting is against the wrong object, against the wrong server, or the structure of the form has been changed to eliminate the indicated support file ID from the object. Change to the correct object, the correct server, or to a support file ID that is associated with the object to complete the operation. Reserved field Group List has too many characters; must not contain more than 255 characters. The Group List field (field 104) is a reserved field with a restriction that the field cannot be more than 255 bytes in length. The definition being saved or imported has an unlimited length. Change the definition to be 255 bytes or less.
397 Error
Unable to allocate memory for cache. If the server is unable to allocate memory from the shared cache, this message appears, and the server terminates. Error in definition for an active link. The AR System server detected an active link definition integrity issue. Repair or replace the active link definition. The file specified for a form does not hold a form definition. 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 of AR System database definition files. If you have manually changed a file, the change is invalid. If you have not changed the file, this is an unexpected error. Form definition in the source file is not the expected definition. The file contains a form definition, but it is not the form definition that is expected. The error is usually caused by a manual change to one or more of AR System database definition files. If you have manually changed a file, the change is invalid. Incorrect format in the definition file. A format error was detected in a definition file. This error is usually caused by a manual change to one or more of AR System database definition files. The error message will contain the error. If you have manually changed a file, the change is invalid.
401 Error
402 Error
65
403 Error
The form definition file field count does not match number of fields in the file. The number of fields defined for the form does not match the count in the form header definition. This error is usually caused by a manual change to one or more of AR System database definition files. If you have manually changed a file, the change is invalid. If you have not changed the file, this is an unexpected error. Field ID is in the core field range but is not recognized. 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. A core definition from the definition file is incorrect. 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 has been changed, the change is invalid. One of the core fields is missing from the form file definition. 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 has been changed, the change is invalid. Duplicate field or VUI ID in the definition. 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 has been changed, the change is invalid. Selection data type requires a limit specification. 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 has been changed, the change is invalid. No definition is in the file. 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 has been deleted, it must be restored from a backup. The file specified for a filter does not hold a filter definition. A file that is 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 has been deleted, it must be restored from a backup. The import file is in an incorrect format. 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.
404 Error 405 Error
406 Error
407 Error
408 Error
409 Error
410 Error
412 Error
413 Error
The file specified for an active link does not hold an active link definition. A file that is 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 has been deleted, it must be restored from a backup. The file specified for a character menu does not hold a character menu definition. A file that is 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 has been deleted, it must be restored from a backup. The file specified for an escalation does not hold an escalation definition. A file that is 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 has been deleted, it must be restored from a backup. The file specified for a distributed mapping does not hold a distributed mapping definition. A file that is 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 has been deleted, it must be restored from a backup. Cannot translate the group name in either the Group List or Assign Group field. The system was translating the contents of the Group List (field ID 104) or Assignee Group (field ID 112) 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 currently defined group. Incomplete join form definition. 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 is dependent upon complete information about the join, so it cannot be created. Incomplete view form definition. 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 is dependent upon complete information about the view, so it cannot be created. Invalid field type. 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 there are no base data fields when you are working with a join form. Incomplete field mapping definition. The field mapping of this join or view form is not consistent with the type of the form.
414 Error
415 Error
416 Error
417 Error
418 Error
419 Error
420 Error
421 Error
67
Unrecognized escalation action type. The type of the action attached to the escalation is outside the allowed range of types. The file specified for a container does not hold a container definition. The file contains a container definition, but it is not the definition that is expected. Make sure that you have not changed the name of the file prior to import. Filter and escalation Push Fields actions can only affect forms on the same server as the filter or escalation. In filters and escalations, you cannot use a Push Fields action to push values to forms residing on different servers. See the Developing AR System Applications: Basic guide for more information about Push Fields actions, filters, and escalations.
The file specified for a VUI does not hold a VUI definition. The import file does not hold a view definition. Field ID is too large. The value supplied for the field identifier exceeds the maximum allowed value. Specify a value that is less than or equal to 2147483647. Fields of this type cannot be included in multi-column indexes. 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 Currency field has too many functional currencies to allow indexing. 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. Not a lock block definition. The definition file is not valid. It is possibly corrupted. Verify the validity of the export definition file and export it again if necessary. An invalid or a corrupt lock block definition was skipped. A portion of the definition file was skipped because it is invalid or corrupted. Verify the validity of the export definition file and export it again if necessary. Server information associated with this tag cannot be updated because Admin operations have been disabled. Administrative operations have been disabled. Administrative operations must be enabled before you can modify this server setting.
436 Error
Invalid format for server information setting. 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 Error 450 Warning
The file specified for the form data does not hold the form data definition. The import file does not hold a form definition. Cannot open a report definition file. Continuing the operation without the file identified in the associated message. 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 will be created or updated without the file. If it is replayed, the user will receive a warning about the missing file. Locate the file that is expected, 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 within the active link.
451 Warning
Failure during load of report definition file into server. View the associated messages. Continue with any other files. While attempting to read a report file referenced in a macro definition, which is embedded in the active link definition being created or modified, the system encountered an error, and the report file could not be retrieved. The operation continues without the report file. The file will not be saved as part of the definition.
460 Error
Missing audit information in the ar.conf/ar.cfg file. Application auditing has been enabled and the system attempted to load configuration information for the application auditing but was unable to locate it in the configuration file. Contact Remedy Customer Support. The AR Server version does not match the Lite license version. AR System on the server containing the application was updated to a different version. The licensed application is only supported on the version of AR System that is included with the application. Install the AR System that is included with the licensed application. The form is not a member of a Lite licensed application. A form was added to a licensed application that does not support added forms. You cannot add forms to this application. Cannot create a form in a Lite licensed AR Server. You attempted 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. Cannot change the form name in a Lite licensed AR Server. You attempted 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. Cannot change the form mapping criteria in a Lite licensed AR Server. 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.
461 Error
465 Error
69
Invalid or pre 6.0 AR Server license file. 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 Remedy Customer Support. Invalid AR Server license import option. Specify 0 or 1 for the license import option. For more information, see the C API Reference Guide. Too few arguments specified for upgrade program. 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. Too many arguments specified for upgrade program. 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. Oracle 8.0 is no longer supported by upgrade. The program that updates the database structure to the current structure no longer supports Oracle 8.0. Please upgrade your Oracle database to Oracle 8i or higher. Status History field is not supported on View forms. This error is returned because you cannot create a Status History field on a view form. Requested database table not found. Please check the spelling (table name is case-sensitive). This error is returned because the correct column information (for example, the right number of columns) for the external schema was not retrieved. This View Form contains Request IDs that are null. Make sure that the key field is set to a non-null, unique column to avoid data corruption. This error is returned because you cannot search the database for the entry ID in a view form if its value is NULL.
476 Error
504 Error
Missing or invalid form definition file. The server could not open the form data dictionary file (form.ar). This file is located 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 could not be 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.
550 Error
Failure while trying to connect to the SQL database. Ensure that the SQL database is running, or contact the database administrator for help. An error occurred while attempting to open a connection to the SQL database. An accompanying error message provides specific details about the failure. The ar.conf file (UNIX) or the ar.cfg file (Windows) contains definitions for the environment variables to set for each database. The value for Dbhome-directory, applicable to the UNIX setup only, is the directory of the database server or client installation on the UNIX machine 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 have moved your database or changed these parameters, you must update the requests in this file and then start the arserverd process again.
551 Error 552 Error
Cannot initialize contact with SQL database. Failure while trying to connect to the database. This is an internal error. Failure during SQL operation to the database. This generic message indicates that an SQL database error was returned during an operation against the database. An associated error message is the full text of the error message from the database that describes the failure encountered. The error is often a message about running out of space in the database log or data area. You can correct this by increasing the size of the data area or by flushing or increasing the size of the log area.
553 Error
Operation requested is too large for a single SQL command. The operation you are attempting generates an SQL command that is too large for the database to process. Break the operation into smaller pieces. For example, if you are modifying a request by changing many data values, modify it in two steps: first change half the values and apply them, then change the other half and apply them. AR System structure error in the SQL databasemissing control record. This is a serious error. The control record for the data dictionary in the database is missing. AR System structure error in the SQL databasemissing enumerated value. This is a serious error. One or more enumerated (selection) values are missing from the data dictionary in the database. Missing data in the SQL database. This is a serious error. Data that is expected to be found in the database cannot be found. This error is usually caused by data missing in an associated table to the base data table. When the data is managed through AR System, all appropriate cross-references are maintained. If you manually updated data in the database, you may have broken one of the required references. If you manually changed the database, undo the change you made to restore the database to a consistent state.
71
557 Error
Too much data in the SQL database (likely data corruption). 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 may have added data that conflicts with existing definitions. If you manually changed the database, undo the change you made to restore the database to a consistent state.
558 Error
Table entry defining form or field is missing. This is a serious error. One of the data dictionary entries defining a form or field is missing. If you have manually changed the database, undo the change you made to restore the database to a consistent state.
559 Error
Character string exceeds maximum size allowed. 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 are no longer able to 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.
560 Error
Multiple actions have the same internal index (likely data corruption). 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 diary fields and on character fields with a maximum length over 255 bytes. The SQL database engine being used does not allow qualification on diary fields or character fields with a maximum length over 255 bytes. You are not able to specify a qualification that includes a reference to these type fields.
562 Error
Table entry defining help text or change diary for a structure is missing. 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 there is no Help text or change diary, a NULL entry is present in these tables. If you manually changed the database, undo the change you made to restore the database to a consistent state.
563 Error
The underlying database does not support the modulo operator. 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. The underlying database does not support field references within a like operation. The SQL database engine being used does not support field references within a LIKE operation. You cannot specify a search that includes a field on the right side of a LIKE operator. Index for value in SQL command is greater than the number of values returned. An SQL command has been issued, and values are being retrieved from the database. A request has been made for a value from the command. However, the index of the column requested is greater than the number of columns that have been 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 values that is returned. If you are not using the SQL option of the Set Fields operation, this is an internal error.
564 Error
565 Error
566 Error
Deadlock during SQL operation to the database. A deadlock condition was detected within 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 Remedy Customer Support.
567 Error 569 Error
Failed to connect to database after multiple attempts. The system has attempted to establish a connection with the database and has received errors after multiple attempts. The number of database records affected by a SQL statement was not available from the database. The database has been configured to not supply the number of records affected by an SQL statement. Configure the database to supply this information. For example, on Microsoft SQL Server the No count connection option cannot be selected.
590 Note 591 Note
SQL database is not availablewill retry connection. The SQL database is not currently available. The process will periodically retry the connection until a connection is obtained or it encounters a fatal error. SQL database is still not availablecontinuing to attempt connection. This message periodically while the system is attempting to connect to an 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.
73
592 Note 600 Error
SQL database is now available. The previously unavailable SQL database is now available, and a connection has been established. This message will follow either message 590 or 591. Error while opening or reading from AR System directory file. Failure while trying to retrieve the list of AR System servers. This list is retrieved only when you are specifying 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. Unrecognized command line option. 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 will not execute with invalid arguments specified. Cannot specify both -G and -U, and cannot specify either more than once. The command line has both a -G and -U option (or either one) specified two or more times. One of the two options must be specified, and they cannot both be specified in the same command. You must break the operation into two commands. Must specify the options -u, -g, or both. 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. Must specify the operation to be performed (-G or -U). Specify either the -G or the -U option for this command. Indicate whether you are adding or deleting a group or user entry. One or more of the command line options is not appropriate for operation. A command line argument is not appropriate for the operation being performed. Review the documentation of the command for details about what options are allowed with which operations. An option required for the operation is missing. A required option for the specified operation is missing. Supply all of the required options. Review the documentation for the command for details about the options required with each operation. A value is expected for the command line option. The specified option expects a value but none was specified. Supply an appropriate value for this option. Invalid tag for Group or User operation. 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.
601 Error
602 Error
607 Error
608 Error 609 Error
610 Error
Error while accessing server cache file (server.ar). The server could not open the access control server cache file (server.ar). This file is located 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 could not be 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.
612 Error 613 Error
Specified user is not registered with this AR System server. The user specified as the administrator user to allow you to perform this command is not a recognized user in the system. You must connect with a valid user with administrator access. Unrecognized group typemust be 1 (view) or 2 (change). 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. Enter the command again, and specify an appropriate value. Unrecognized license typemust be 0 (none), 1 (fixed), or 2 (floating). 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. Enter the command again, and specify an appropriate value. No such user existscannot connect as a guest user because user name differs from a registered user only by capitalization. The user attempting to log in is not a registered user and although the system has been 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 only in capitalization.
614 Error
615 Error
616 Error
Group category is unrecognized or isn't appropriate. 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. Computed group includes circular reference. The computed group definition contains a circular reference. Remove the circular reference. Computed group qualification contains invalid content. The syntax of the computed group qualification is incorrect. Make sure that the syntax is correct. Two forms contain the same open license tag -- ignored for both forms. The system found two forms containing the same open license tag specified in the change history. The two forms are identified in an associated error message.
75
621 Error 622 Error 623 Error 625 Warning 626 Warning 635 Error
Problem processing the license tag filelicense tag file ignored. The system encountered an error while attempting to process the license tag file. Problem while preparing open write licensingopen write licensing may be incomplete. The system encountered an error while attempting to prepare open write licensing. An associated error message contains the details of the failure. Authentication failed. Make sure that your user name and password were entered correctly. Date in the holiday list is invalid. A date in the holiday list of the Business Time Holiday form is not a legal date. Illegal dates will be ignored and processing will continue. Time in the workday definition is invalid. A time specified in the Business Time Workday form is invalid. Invalid times will be treated as if no time was specified, and processing will continue. Two forms contain all the reserved holiday fields -- delete one to continue. The system found two forms containing the reserved holiday fields. You must delete one form for business time processing to continue. The two forms are identified in an associated error message. No Holiday form could be found on the server. 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. No holiday definition exists with the specified tag. 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. Two forms contain all the reserved workday fields -- delete one to continue. The system found two forms containing the reserved workday fields. You must delete one form for business time processing to continue. The two forms are identified in an associated error message. No Workday form could be found on the server. 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.
636 Error
637 Error
638 Error
639 Error
640 Error
No workday definition exists with the specified tag. 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. The workday schedule defines no open hours. The workday schedule does not contain any open hours. For a workday schedule to be valid, there must be at least one minute during the week that is defined as open. Correct the definition to specify open times for the schedule. ARFullTextInfoList structure is empty. 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. Full text search (FTS) information data associated with this tag has an incompatible data type or the value is out of range. The full text search (FTS) information for the indicated 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. Try the operation again, specifying the correct data type for the value.
641 Error
651 Error 652 Error
653 Error
Full text search (FTS) information data associated with this tag is invalid. 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. You must omit this value from the Set operation, or you must supply a value. The full text search (FTS) information tag is unrecognized. 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 the valid codes that can be specified. ARFullTextInfoRequestList structure is empty. The value you specified for the list of information to retrieve from the FTS value was NULL or empty. To retrieve information, you must specify what information you are trying to retrieve. Could not initialize the full text search (FTS) database. The server encountered an error while attempting to connect to the full text search (FTS) database. Review the associated error message for more details about why the attempted connection failed. Resolve the error indicated, and start the server process again. Failed to complete full text search (FTS) operation. 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 that describes the failure encountered.
654 Error
655 Error
656 Error
657 Error
77
658 Error
Failed to read full text search (FTS) documents. 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 that describes the failure encountered. Failed to open the Ignore Words list file. While attempting 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 that describes the failure encountered. This error is often caused by a permission problem with the Ignore Words list file. Search the FTS home directory and the FTS 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.
659 Error
660 Error
Failed to update the Ignore Words list file. While attempting to update the Ignore Words list, an error occurred while updating the Ignore Words list file. An associated error message contains the full text of the error message from the full text search (FTS) engine that describes the failure encountered. Failed to relocate full text search (FTS) index directory. 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 that describes the failure encountered. This error is commonly encountered when the target location does not exist, does not have appropriate permissions, or does not have enough disk space for the existing FTS index.
661 Error
662 Error
Operation requested is too large for a single full text search (FTS) command. The operation you are attempting 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. A full text search on a field that is not a character or diary field is not allowed. An error occurred during a full text search. An attempt was made to search on a field that is not a character or a diary field. This message indicates an error in the database structure tables. Contact Remedy Customer Support. No users are licensed for full text search (FTS) operations on this server. An attempt has been made to retrieve or set information about the full text search (FTS) environment on the server. However, there are no Full Text Search Option licenses defined for the server. If you are not using the full text search (FTS) capability of the product, this error can be ignored. If you want to use the full text search (FTS) capability, you must obtain a license.
663 Error
665 Error
666 Error
Full text search (FTS) operations are disabled. Turn on FTS operations, and try your operation again. You attempted to perform an operation that can only be performed when the full text search (FTS) state is set to Enabled. It is currently set to Disabled. To perform this operation, change the FTS state to Enabled, and try again.
667 Error
Full text search (FTS) operations are enabled. Turn off FTS operations, and try your operation again. You attempted to perform an operation that can only be performed when the full text search (FTS) state is set to Disabled. It is currently set to Enabled. To perform this operation, change the FTS state to Disabled, and try again.
668 Error
Invalid full text search (FTS) query. 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 Remedy Customer Support for assistance in resolving the error. Destination full text search (FTS) index directory already exists. You are attempting 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 not correct, change the name to the directory you want. If it is correct and there is an empty directory in place, remove the directory and try the operation again. Field is pending a full text search (FTS) operation. The field you are performing the search on is a full text search (FTS) enabled field; however, the index does not currently exist on this field. Its creation is pending. It may take from a few minutes to a few hours for the index to be created and put in place, depending on the amount of indexing that is pending. For now, the system will default to the search strategy supported by the underlying database. When the indexing has been completed, the field will be available for full text searches again.
669 Error
670 Warning
671 Error
Full text search (FTS) executable not found. AR System server attempted to start the full text search (FTS) indexing process, but it could not find the executable. The server assumes that there is a program named arservftd that is located in a directory named bin that is parallel to the directory identified by the Serverdirectory setting in the /etc/ar.conf file. Cannot perform a full text search (FTS) index on a Status History field. 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.
672 Error
79
673 Warning
The query compares two fields that involve full text search (FTS) indexed fields. The full text search capability does not support comparing two fields. The comparison will be made using the functionality of the database. The attempted query includes a relational operation between two full text search (FTS) indexed fields. The FTS index does not support this operation, because the underlying database is relied upon for the search.
The full text search (FTS) query is not sufficiently qualified. The attempted query involved a full text search (FTS) indexed field, and the search term matched too many words in the FTS dictionary. The full text search (FTS) home directory can be set only by the installer. You cannot use the API call arsetfulltextinfo to set the FTS information home directory. This directory is set during installation. Unrecognized license type -- should be 0 (none), 1 (fixed), 2 (floating), or 3 (restricted read). 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. Enter the command again, and specify an appropriate value. AR System NM Daemon: Cannot register with network manager. The system failed to connect to the network management platform. An associated error message contains details about why the connection failed. Correct the cause of the error (for example, run the network manager if the error is that the manager is not running), and run the daemon again. AR System NM Daemon: Cannot register with network manager event dispatcher. The system failed to connect to the event dispatcher of the network management platform. An associated error message contains details about why the connection failed. Correct the cause of the error (for example, if the event subsystem is not configured, configure it), and run the daemon again. AR System NM Daemon: Malloc failure. The system encountered an error during a call to allocate space. In general, this error occurs when there are too many processes running or when some processes have grown to occupy most or all of the available memory on your server machine. You can recover that memory by shutting down unneeded processes. You can also restart processes that have been running for a while to recover space those applications may have suffered memory leak over time. AR System NM Daemon: Cannot open the configuration file. An error occurred while trying to open the configuration file. Because this file contains the definition of all the mappings that will be performed, the system cannot run without this file. An associated error message contains details about why the file could not be opened. Correct the cause of the error, and run the daemon again.
700 Error
701 Error
702 Error
703 Error
704 Error
AR System NM Daemon: Failure checking whether configuration file has been accessed. An error occurred while verifying whether an update to the configuration file has occurred. Because this file contains the definition of all the mappings that will be performed, the system cannot run without this file. An associated error message contains details about why the file could not be opened. Correct the cause of the error and run the daemon again. AR System NM Daemon: Format error in configuration file. The format of one or more lines in the configuration file is not recognizable. If the file has been manually edited, restore it to its previous format. If the file is merely updated through AR System NM daemons, this error should not occur. AR System NM Daemon: Too many fields specified for one of the traps or events. The configuration has 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. AR System NM Daemon: Unrecognized command-line option. 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 Developing AR System Applications: Basic guide. AR System NM Daemon: A value is expected for the command-line option. The specified command-line option requires an additional value with this program. A complete definition of the allowed command-line options is in the Developing AR System Applications: Basic guide. AR System NM Daemon: Connection to trapd lost. The arxxxd process lost connection to the trapd process for the network management platform. This error is not expected. Changes to your event or trap mappings will be lost if you exit. You have not saved 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. The configuration file has been changed by another user while you have been modifying its contents. While you have been modifying the contents of the mapping file, the file has been changed by another user. If you save your changes, they will overwrite the changes made by the other user.
705 Error
706 Error
707 Error
708 Error
709 Error 750 Error
751 Error
81
752 Error
User does not exist on the server. The specified user does not exist on this server. If all the fields being mapped have an open create mode, an unknown (or guest) user is allowed to perform submissions. If guest users are allowed and create modes are open, you can ignore this error and continue. However, if any of the fields being mapped are protected fields, you must be a registered user with update permission to the field to perform the submission. Data in other fields truncated for entry. The total of all data being mapped causes an overflow of the definition in the mapping file. This message is a warning that one or more field definitions have been truncated and will be lost from the mapping specification in order to fit within the file line length limits. Changes on this screen will be lost if you continue. Changes you have made to this screen will be lost if you continue. If you want to discard the changes, simply continue. If you want to keep the changes, cancel the dismiss operation, and save the changes. You have not opened the file defined in this windowthe file will not be opened if you continue. You have specified a file name in this window. The file was not opened due to a previous error or because you have not clicked the Save button on the window. If you continue with this operation, the new file will not be opened.
753 Error
754 Error
758 Error
759 Error
You have not saved the changes you made; they will be lost if you exit. You have not saved 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. Out of memory. The system encountered an error during a call to allocate memory. In general, this error occurs when there are too many processes running or when some processes have grown to occupy most or all of the available memory on your server machine. You can recover memory by shutting down unneeded processes, or you can restart processes that have been running for a while to help recover space those processes may have leaked over time. No AR System servers registeredcannot validate user to allow configuration. 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. Cannot successfully connect to any server as special NM user. 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.
760 Error
761 Error
763 Error
764 Error
Invalid password for user on server. The password you specified is not the password that is recognized for you. Verify the password that you entered (remember that passwords are case-sensitive), and enter the corrected password. Cannot open the network management configuration file. The network management configuration file that you specified cannot be opened. An associated message contains details about why you could not open the file. Correct the reason for the failure, and attempt to open the file again. Cannot access the indicated file. The file indicated in the error message cannot be accessed. Review the associated error message for more details. A target form for the mapping must be supplied. You must specify a form that is the target of the trap being mapped. If there is no target form, no mapping is performed. Failure while writing to the file. An error occurred while attempting to save changes to the indicated file. An associated message contains more information about the failure. Correct the failure and save your changes again. Failure while building Set Fields screen. An error occurred while preparing the Set Fields screen. See the associated error message for details. You have entered a nondigit character for a numeric field. You can enter digits only in numeric fields. You have specified a character string in a numeric field. Change the contents of the indicated field to a legal number. You have entered an improperly formatted value for a real field. The value for the real field is not a recognized real format. The system will accept real values in decimal or scientific notation. Change the value into a legal real number format, and repeat the operation. Unrecognized selection value. 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. Invalid mapping of an SNMP varbind variable. An error occurred while trying to map an SNMP varbind variable. Verify the syntax specified in the mapping, and correct it as needed.
765 Error
772 Error
775 Error
83
791 Error
Cannot open the SNM configuration file. The program cannot open the specified SunNet Manager configuration file. An associated error message contains details of the failure. You cannot add new definitions until you can open the file. Correct the reason for the failure (for example, if you do not have read or write access to the file, change your file access permissions), and run the tool again. Failure while writing to the file. An error occurred while trying to write updates to the definition file. An associated error message contains details of the failure. Correct the reason for the failure (for example, if you are out of space, remove some files to create more space), and perform the operation again. Failure while trying to create a backup file; the operation is continuing. This is a warning message. An error occurred while trying to create a backup file for the SunNet Manager definition file. The system creates a backup of the definition file and names it <file_name>.bak; however, this time it failed. The system is continuing the operation and updating the definition file; however, there is no backup file. An associated error message contains details about the failure. A value is required for both the label and the command. You must 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. Cannot have a quotation mark in the label due to SunNet Manager syntax. The label you have specified contains a quotation mark. You cannot specify a quotation mark in the label, because it is a special character in the SunNet Manager definition syntax. You must change the label so that it does not include a quotation mark character. Cannot have a quotation mark in the command line due to SunNet Manager syntax. The command line you specified contains a quotation mark. You cannot specify a quotation mark in the command line, because it is a special character in the SunNet Manager definition syntax. You must change the command line so that it does not include a quotation mark character. Invalid mapping parameters. You defined a mapping (probably using varbind) where one of the mappings is wrong. Correct the mapping, and issue the mapping request again. AR System server terminated unexpectedlyrestarting. The server has detected that one of the child processes it is responsible for has terminated. The name of the process that is being restarted is reported in an associated message. The server process will relaunch the server that shut down.
792 Error
793 Error
794 Error 795 Error
796 Error
797 Error 802 Note
842 Error
Malloc failed on TC server. The system encountered an error during a call to allocate space. The failure occurred on the server machine during processing of a call from the client. In general, this error occurs when there are too many processes running or when some processes have grown to occupy most or all of the available memory on your server machine. You can recover that memory by shutting down unneeded processes or by restarting processes that have been running for a while. Failure during fork operationcannot launch child server. A failure was encountered while trying to launch a child process. An associated message provides details about the failure. The child process was not launched. Correct the reasons behind the failure, and try the operation again. Failure during exec operationcannot launch child server. A failure was encountered while trying to launch a child process. An associated message provides details about the failure. The child process was not launched. Correct the reason behind the failure, and try the operation again. Attempted to launch this server more than four times within 30 secondsabandoning attempt to start this server. The server process has attempted to launch a child process more than four times within 30 seconds. The name of the child process that could not be restarted is identified in an associated message. Because this process continues to fail, the server will stop trying to launch the process and will remove it.
843 Error
844 Error
845 Error
Failure during wait operationunable to wait for status change. A failure was encountered while trying to wait for a status change. An associated message provides details about the failure. This is an internal error. Pending list lock file exists. The work file must be locked by the arservftd process but is currently being held by another process. Pending list lock file does not exist The arservftd process cannot release the work file, because the file does not exist. Pending list file open action failed. A full text search (FTS) enabled field was updated. The file that holds the list of fields that have indexing pending could not be opened when you attempted to add a note about the updated field. An associated error message describes the details of the failure. Pending list file write action failed. A full text search (FTS) enabled field was updated. The file that holds the list of fields that have indexing pending could not be written to when you attempted to add a note about the updated field. An associated error message describes the details of the failure encountered.
858 Error
85
859 Error
Record does not exist in the pending list file. A full text search (FTS) enabled field was updated. The file that holds the list of fields that have indexing pending could not be written to when you attempted to add a note about the updated field, because the record associated with the updated field could not be found. An associated error message describes the details of the failure. Failed to truncate the pending list file. A full text search (FTS) enabled field was updated. The file that holds the list of fields that have indexing pending could not be truncated when you attempted to add a note about the updated field. An associated error message describes the details of the failure encountered. Failed to purge pending list file. During a re-index operation, an error occurred while attempting to purge the list of pending changes. An associated error message describes the details of the failure. Too few arguments for the full text search (FTS) indexer process. You have not provided the minimum set of arguments required by the full text search (FTS) indexer process (arservftd). See the Developing AR System Applications: Advanced guide for information about the expected arguments. Too many arguments for the full text search (FTS) indexer process. You have exceeded the limit of arguments allowed by full text search (FTS) indexer process (arservftd). See the Developing AR System Applications: Advanced guide for information about the expected arguments. Invalid action for the full text search (FTS) index process One of the arguments for the full text search (FTS) indexer process (arservftd) indicates the action for the program to take. The supplied action code is not recognized. See the Developing AR System Applications: Advanced guide for information about allowed routines. Full text search (FTS) indexer process terminated when a signal was received by the server. The server for the full text search (FTS) search feature (arservftd) was terminated by a signal. 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 Remedy Customer Support for assistance in determining the cause of the problem. The server most likely shut down due to a bug in the system.
860 Error
861 Error 862 Error
863 Error
864 Error
865 Error
866 Error
Another copy of the full text search (FTS) indexer process is already running. Only one instance of the full text search (FTS) indexer process can be run on any given machine. Determine if there is already a copy of arservftd running. If so, no action is required.
867 Error
Form ID or name, field ID, Request ID, and action are required together. 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. See the C API Reference Guide for more information. Too many arguments specified for optimize argument. The optimize argument has been specified for the full text search (FTS) indexer process. There is a limit to the other arguments allowed when this option is specified. In this case, one or more of the arguments have been specified that are not allowed. See the C API Reference Guide for more information. Too many arguments specified for the retry argument. The retry argument has been specified for the full text search (FTS) indexer process. There is a limit to the other arguments allowed when this option is specified. In this case, one or more of the arguments have been specified that are not allowed. See the C API Reference Guide for more information. The submitted mail message did not contain a form name. The mail message does not contain a line identifying which form is the target of the submission, and there is no default form 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. The submitted mail message did not contain a body providing details for the new entry. No text exists in the body of the mail message to specify values to be assigned for the new entry. To create a new entry by using the mail daemon, one or more values must be provided. The message can be submitted again with the additional information added. The submitted mail message had a format that was not recognized. 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 Configuring AR System guide. Missing value for command line parameter. A command line argument that requires a value was specified but no value was provided. You must supply an appropriate value for the argument. Failure occurred while accessing mail configuration file. The system encountered an error while attempting to access the configuration file indicated on the command line. An associated message contains more details about why the file could not be accessed. Most likely, the file specified does not exist (can be a misspelled file name, or the file has been moved). Correct the reported problem, and issue the command again.
868 Error
869 Error
951 Error
952 Error
87
957 Error
The submitted mail message specified a form that does not match the required form. 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 has been configured to support submissions to only a single, specific form. A user has attempted to submit a request to another form. The submitted mail message specified a server that does not match the required server. 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 has been configured to support submissions to only a single specific server. A user has attempted to submit a request to another server. The server specified for this message is not a recognized serveraccess was attempted, but no server was found. 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 successfully connect with at least one server.
958 Error
959 Error
961 Note 964 Error 965 Error 966 Error 967 Error 968 Error 971 Warning
Your submission was accepted by the AR System. ID for the new request is <Request_ID>. The submitted email message successfully created a request in AR System. Use the Request ID number for querying or modifying the request. The armail attempt to log on to the mail post office failed.
armail failed when trying to log on to the mail system. Verify that the Mail login and
password given during installation are valid and that the mail system is accessible. Could not resolve the armail address. The armail address specified is not considered unique within the mail system. Could not read mail from the mail post office.
armail could not read a mail message from the post office. Make sure that the mail system is
still accessible. Could not log off from the mail post office.
armail could not log off from the post office. Make sure that the mail system is still accessible.
Attempt to send mail to the mail post office failed. To: <destination>. The address indicated is either ambiguous, does not exist in the mail system, or is not accessible. Use a valid address, and make sure that the mail system is still accessible. The number of matches to your query request exceeded the configured limit of <limit>. 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.
No matches were found to your query request. When querying through the mail interface, no requests were found that match the query conditions specified. No fields in the query list are accessible to you for this form. 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. Required currency value not specified. The value portion of the currency structure was not provided. This error can only be encountered through an API program. Required currency code not specified. The currency code portion of the currency structure was not provided. This error can only be encountered through an API program. Bad currency value. When converting a character value to a currency value, this error message is returned if there is no numeric value contained in the string or if the decimal number is invalid. No common functional currency exists to use in relational operation. This error is returned because no common functional currency was found when comparing currency constants with functional currency data. No Currency Code form exists. A system error occurred or the AR System Currency Code form was deleted. Restart the AR System server, which will automatically re-create the form, if necessary. The currency code either does not exist in the Currency Code form or has not been marked as Active. An attempt was made to reference a currency code that does not exist or has been disabled. Add the currency code.
980 Error 981 Error 982 Error 983 Error 984 Error 985 Error
Currency value contains a currency code that is not allowed for this field. A currency code was entered that is not an allowable currency code for this field. Currency fields not allowed for grouping. A currency field was specified to be the group-by field in a statistical query, which is not allowed. Currency part must be specified to use currency field in this context. A currency field was specified in a context where only a specific currency field part is allowed. Specify a currency field part.
89
Unable to free shared or exclusive lock on user cache hash list. This is an internal error that probably indicates the system is low on resources. Restart the server. Unable to free shared or exclusive lock. This error is returned when a shared or exclusive lock cannot be released due to unexpected events in the server. You cannot allocate memory on startup. The system encountered an error during a call to allocate memory. In general, this error occurs when there are too many processes running or when some processes have grown to occupy most or all of the available memory on your server machine. You can recover memory by shutting down unneeded processes. In addition, restarting processes that have been running for a while will help by recovering space those processes may have leaked over time. The -e and -i options require a macro name. 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 that is to be run at start-up. Remove the option, or specify a macro to go with the option. The -p option requires a substitution parameter and a value. 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. The format for the -p option is -p name = value. 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. Unrecognized command line option. The specified command line option is not recognized. See the Developing AR System Applications: Basic guide for information about command line options. Parameters can be specified only if you specify a macro first. You have specified a -p command line option that specifies values for parameters in a macro that is to be run at startup. However, there is no macro defined (by using the -e or -i options). If you specify parameters to be used in a macro, specify the macro that uses them.
1001 Error
1002 Error
1003 Error
1004 Error 1005 Error
1006 Error
You cannot read the configuration fileARHOME variable may be set incorrectly. Configuration information for your session is stored in a configuration file named config that is located in the directory indicated by the ARHOME environment variable. If there is no ARHOME environment variable set, it 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 have 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 Error
You cannot connect to the X server. The aruser program on UNIX is an X program. It requires that an X windowing system be running to allow the program to operate. Currently, there is not a window system running in your environment. Start a windowing system, and restart the aruser program. The macro name in a parameter is longer than the maximum allowed length. 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. Two startup macros have been specified. Two or more startup macros have been specified on the command line. Remedy User allows a maximum of one macro to be specified at startup. You can specify a macro that runs other macros if desired. Both the -e and -i options specify macros to be run, so only one can be specified on the command line at any time. No servers are defined for the AR System in the directory file. No servers have been specified for the aruser program to connect to. There must be one or more servers defined in the /etc/ar file or, if starting the aruser program from the command line, one or more servers must be defined by using the -x command line option. Two directories for startup macros have been specified. The -d command line option has been specified two or more times. This option can be specified only once. Enter the command again, specifying only one -d command line option for the directory that contains the startup macro you want to run. The -d option requires a directory name. The -d command line option requires that you specify a directory. Enter the command again, omitting the -d option if not needed or supplying an appropriate directory name. The directory name in a parameter is longer than the maximum allowed length. 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 have not omitted required spaces between options.
1008 Error
1009 Error
1010 Error
1011 Error
91
1014 Error
A directory can be specified only if you specify a macro. You specified the -d command line option, but no startup macro was specified using the -e or -i command line option. Enter the command again, omitting the -d option or specifying a startup macro with the -e or -i option. The -x option requires a server name. The -x command line option requires that you specify a server name. Enter the command again, omitting the -x option (if not needed), or supplying an appropriate server name with the -x option. The server name in a parameter is longer than the maximum allowed length. 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 have not omitted required spaces between options. Server is not compatible with Remedy Alert. This error is returned because the Remedy Alert client only works with 5.x (or later) AR System servers. The process terminated unexpectedly. No description. The entry was successfully created with ID = <Entry_ID> The Save operation was completed successfully. This message displays the entry ID of the newly saved entry. The preceding error occurred during execution of active link <active_link>, action <action>. The error occurred while running an active link. This message gives the name of the active link and the specific action within the active link where the error occurred. This information is useful for debugging active links. In general, you can ignore this message. Additional errors were truncated. 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 have been suppressed. Attachments for the report are exported under <directory_name>. Include this directory in the export file if you choose to import the data. This message notifies user when the attachments are exported to a directory for reporting. No matching requests (or no permission to requests) for qualification criteria. No requests were found that match the qualification criteria you have specified. There are two possible reasons that requests are not returned: The criteria you specified do not match any requests. You do not have access to the request or to the fields you are specifying in the request.
1015 Error
1016 Error
1017 Error 1067 Error 1100 Note 1101 Note
1102 Note
1103 Note 1200 Warning
1201 Warning
New text is longer than the maximum allowed lengthtruncating to fit. The text you have specified is too long for the field you are trying to update. The field has a maximum length defined, and the text that you have entered is too long for the field. The extra text is truncated so that it fits in the target field. A recording operation is in progressyour current recording will be lost if you exit. You have specified that you want to exit 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. This record has been updated by another user since you retrieved it. The request you are attempting to save changes to has been modified by another user since you last changed it. You can Save your changes over the changes of the other user, or you can 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).
1202 Warning
1203 Warning
1204 Warning
Partial selections will become full selections on playback. 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 the items in the query list were selected. New fields added or made accessible by administratoradded as hidden fields to local view file. An administrator has updated the form being opened. One or more new fields have been 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 Remedy User to locate the new field, move it to an appropriate location, and make it visible if you want to use it.
1205 Warning
1207 Warning
A recording operation is in progresscurrent recording will be lost if you continue. 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. You have not saved changes on this screenthey will be lost if you continue. You have made changes to the data on the current screen. If you continue with the Dismiss operation, all of your changes will be lost. To keep your changes, click Cancel Dismiss, then save the changes. To discard the changes, click Continue.
1208 Warning
93
1209 Warning
You have not saved changes on this screenthey will be lost if you continue. You have made changes to the data on the current screen. If you continue with the Next or the Previous operation, all of your changes will be lost. To keep your changes, click Cancel Dismiss, then save the changes. To discard the changes, click Continue. You have not saved changes on the properties screenthey will be lost if you continue. You have made changes to the data on the form Item Properties associated with the Customize View window. If you continue with the Dismiss operation, all changes you have made will be lost. To keep your changes, click Yes, then save the changes. To discard the changes, click No. You have not saved changes on a diary or text edit windowthey will be lost if you continue. You have made changes to the data on a Diary or a Text Edit window. If you continue with the Dismiss operation, all changes you have made will be lost. To keep your changes, click Cancel Dismiss, and then save the changes. To discard the changes, click Continue. Search window is now connected to a different formcontinuing will change the current form. The Search window is connected to a different form than the form being referenced in the window where you are performing the operation. If you continue this operation, the window will change to the new form. If you cancel this operation, the operation is canceled and the window remains unchanged.
1210 Warning
1211 Warning
1212 Warning
1213 Error
Multiple requests match qualification criteriaInformation pulled from first matching request. More than one request matched your qualification, but Remedy Administrator defined AR System to display only the first matching request from the search.
1214 Warning
Macro recording is activeoperation recorded but no database operation performed. 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. Server cannot set the client locale. Locale-sensitive operation done on the server may not conform to the clients locale convention. Make sure that the server and client can use the clients locale convention. This operation will modify <number> entries. Do you want to continue? The operation you are performing modifies many entries in the database. The number of entries that will be modified is contained in the message. To continue with the modification, click Continue. If you do not want to modify multiple entries, click Cancel, and verify the operation you are performing. This message is issued only from the Modify All window.
1217 Warning
You have not saved changes on a diary or text edit windowthe changes will not be included in the current save action if you continue. You have made changes to the data on a Diary or Text Edit window. The data in these windows will not be included if you click Continue. If the data is important, click Cancel Dismiss, save the data in the Diary or Text Edit window by selecting Save in that window, and click Save on the current window again. To not save the data in the Diary or Text Edit window, click Continue, and continue with the Save operation. The data in the Text Edit or Diary windows may be overwritten by the existing text in the windows after the Refresh operation following a successful modification.
The specified file already exists. The file you specified as the target of your report already exists. You can choose to overwrite the file or to cancel the Report operation. Unable to find help for the specified field. A failure occurred while trying to retrieve Help text for the field. An associated error message provides details of the failure. Duplicate name for macro. Do you want to overwrite the existing macro? You specified a name for a new macro that is the same as the name of an existing macro. You can choose to overwrite the existing macro if you want the new definition to replace the old 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 Warning
Duplicate name for custom report. Do you want to overwrite the existing custom report? You have specified a name for a new custom report that is the same as the name of an existing custom report. You can choose to 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.
1225 Warning
Duplicate name for user command. Do you want to overwrite the existing user command? You have specified a name for a new user command that is the same as the name of an existing user command. You can choose to overwrite the existing user command if you want the new definition to replace the old 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.
95
Failure trying to expand the character menu. An error occurred while trying to expand the definition of a character menu. An associated error message contains the details of the failure. The selected macro definition will be deleted. This prompt is issued (when you attempt 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. The selected custom report definition will be deleted. This prompt is issued (when you attempt 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. The selected user command definition will be deleted. This prompt is issued (when you attempt 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. Macro recording is activemodifications will be made to the entry but will not be recorded in the macro. You are recording a macro in Remedy User. When the macro was processed, any operation that utilized 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.
1229 Warning
1230 Warning
1232 Warning
1233 Warning
Your disk drive is almost full; please remove unwanted files. The disk containing the file you are writing is approaching its maximum storage capacity. Create space for the file if you want to continue with the operation. Help text is too long; only the first 32,000 characters are shown here. Remedy User displays only 32,000 characters of help text. Text field is too long; only the first 32,000 characters are shown here. If you change this request, it will damage the record. Character fields display only 32,000 characters in Remedy User. If you add more characters to the field, you will lose all information over the 32,000 character limit and any changes that you have made.
1236 Warning
Your window resources are low; close unwanted windows or applications. You are currently 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.
File will be saved in Report File format. Default file extension is *.rep if none specified. 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. 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 are continuing with the view from a previous version of the tool, you cannot further customize without reloading an Admin view from the server. This means that all the customizations will be lost; but you can customize the view again and continue with this new view without problems. If you choose not to continue, the existing customized view will remain available.
1243 Warning
You cannot translate the group name in the Group List or Assignee Group field. 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. There was a problem expanding the EXTERNAL qualification. The supplied qualification or assignment statement has improper syntax. No such form existsmake a selection from the list. You have entered an unrecognized form name. The list contains all valid forms. Double-click a form from the list. The workflow logging file specified in the logging options dialog cannot be opened. This error is reported when the path, name (or both), of a workflow log file, as specified by the user in the workflow logging options dialog of Remedy User, cannot be opened. Verify that you have file or directory access permissions. You cannot open view file. 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 (files ending in.arv). Correct the access problem, and try the operation again. You cannot open definition file. 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 (files ending in .arf). Correct the access problem, and try the operation again. You cannot open default file. 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 (files ending in .ard). Correct the access problem, and try the operation again.
1244 Warning 1301 Error 1400 Error
1401 Error
1402 Error
1404 Error
97
1405 Error
You cannot open configuration file. The configuration file cannot be opened. Verify that you have read and write access to the ARHOME directory and to the configuration file (config). Correct the access problem, and try the operation again. You cannot open the specified file. The file indicated in the message cannot be opened. An associated error message provides additional information about the failure. Correct the problem, and try the operation again. You cannot open a temporary file. A failure was encountered trying to open a temporary file. These files are opened in the directory /tmp. An associated error message provides details about the failure. Correct the problem, and try the operation again. You cannot read from the specified file. An error occurred while attempting to read from the file identified in the error message. An associated error message provides details about the failure. Correct the problem, and try the operation again. You cannot write to the specified file. An error occurred while attempting to write to the file identified in the error message. An associated error message provides details about the failure. Correct the problem, and try the operation again. You cannot write to the definition file. An error occurred while attempting to write to the definition file for this form. These files are stored in your ARHOME directory (files ending in .arf). An associated error message provides details about the failure. Correct the problem, and try the operation again. You cannot write to the view file. An error occurred while attempting to write to the view file for this form. These files are stored in your ARHOME directory (files ending in .arv). An associated error message provides details about the failure. Correct the problem, and try the operation again. You cannot write to the default file. An error occurred while attempting to write to the user-defined defaults file for this form. These files are stored in your ARHOME directory (files ending in .ard). An associated error message provides details about the failure. Correct the problem, and try the operation again. You cannot reset user view. An error occurred while trying to reset your view. An associated message provides details about the failure. Correct the problem, and try the operation again. You cannot restore previous view. An error occurred while trying to restore your previous view. An associated message provides details about the failure. Correct the problem, and try the operation again.
1408 Error
1409 Error
1411 Error
1412 Error
1413 Error
You cannot make a backup view. An error occurred while trying to create a backup copy of the view file. An associated message provides details about the failure. The operation continues without creating a backup file. You cannot open support data or cache file. 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 (files ending in.arv). Correct the access problem, and try the operation again. You cannot write to the specified support data or cache file. An error occurred while attempting to write to the support file for this form. These files are stored in your ARHOME directory (files ending in .arv). An associated error message provides details about the failure. Correct the problem, and try the operation again. Fork operation failed. A failure was encountered while trying to start a child process. An associated message provides details about the failure. The child process was not started. Correct the reason for the failure, and try the operation again. Failure occurred while trying to run a process to load a field value. A failure was encountered while trying to start a child process that is retrieving data for a field. An associated message provides details about the failure. The child process was not started, so no data is changed in any fields. Correct the reason for the failure, and try the operation again. Out of memory. The system encountered an error during a call to allocate memory. The failure occurred on the client machine (the one running the aruser program, Remedy User). This error can occur when too many processes are running or when some processes have grown to occupy most or all of the available memory on your client machine. You can recover memory by shutting down unneeded processes. Or shut down and restart processes that have been running for awhile; this process may help recover space those applications have leaked over time.
1418 Error
1450 Error
1451 Error
1500 Error
1501 Error
You cannot record operation: <operation_type> An error occurred while trying to add the specified item to the list of recorded operations. The system is probably out of memory. The indicated operation will not be a part of 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 1500), and begin recording your macro again.
99
1502 Error
Only integer data types can be displayed by using numeric text (defaulting to text field type). 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 that is appropriate for the data type for this field. Only selection data types can be displayed using checkboxes (defaulting to text). 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 that is appropriate for the data type of the field. Only selection data types can be displayed using exclusive choice boxes (defaulting to text). 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 has been changed to text for this field. If a text field type is acceptable, you can ignore this message. Otherwise, specify a field type that is appropriate for the data type of the field. Unrecognized field type (defaulting to text). You have specified an unrecognized field type for a field. The field type has been changed to text for this field. If a text field type is acceptable, you can ignore this message. Otherwise, specify a field type that is appropriate for the data type of the field. Cannot create new field. An error occurred while attempting 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 1500). View file format error: invalid form name. The form name found in the view file does not match the name of the form in the definition file. The view file with the error is deleted and reloaded the next time you access the form. View file format error: missing form name. The view file for the form does not have a form name. The view file with the error will be deleted and reloaded the next time you access the form. View file format error: field clause. Because a field clause was not found where expected in the view file, the format of the view file is not what is expected. The view file with the error will be deleted and reloaded the next time you access the form. View file format error: field definition. Because an invalid clause was encountered in a field definition in the view file, the format of the view file is not what is expected. The view file with the error will be deleted and reloaded the next time you access the form.
1503 Error
1504 Error
1505 Error
1506 Error
1510 Error
1511 Error
View file format error: invalid form or active link end. 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 not what is expected. The view file with the error will be deleted and reloaded the next time you access the form. View file format error: begin active link. The only information expected after the end clause of a form is the definition of active links. When processing the file contents after the end clause, an entry was found that was not the start of an active link. Therefore, the format of the view file is not what is expected. The view file with the error will be deleted and reloaded the next time you access the form. View file format error: active link definition. Because an invalid clause was encountered in an active link definition in the view file, the format of the view file is not what is expected. The view file with the error will be deleted and reloaded the next time you access the form. Definition file format error: invalid form name. The form name found in the definition file does not match the name of the form. The definition file with the error will be deleted and reloaded the next time you access the form. Definition file format error: missing form name. The definition file for the form does not have a form name. The definition file with the error will be deleted and reloaded the next time you access the form. Definition file format error: field clause. Because a field clause was not found where expected in the definition file, the format of the definition file is not what is expected. The definition file with the error will be deleted and reloaded the next time you access the form. Definition file format error: field definition. Because an invalid clause was encountered in a field definition in the definition file, the format of the definition file is not what is expected. The definition file with the error will be deleted and reloaded the next time you access the form. Definition file format error: character menus. 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 present in the file, the format of the definition file is not what is expected. The definition file with the error will be deleted and reloaded the next time you access the form. Definition file format error: invalid form or active link end. 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 not what is expected. The definition file with the error will be deleted and reloaded the next time you access the form.
1512 Error
1513 Error
1518 Error
1519 Error
1520 Error
101
1521 Error
Definition file format error: begin active link. 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 definition file is not what is expected. The definition file with the error will be deleted and reloaded the next time you access the form. Definition file format error: active link. Because an invalid clause was encountered in an active link definition in the definition file, the format of the definition file is not what is expected. The definition file with the error will be deleted and reloaded the next time you access the form. Unrecognized selection value. 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. Total number of lines between margins less than minimum of five. 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. Total number of characters per line between margins less than minimum of 40. 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. Total number of characters per line including margins is greater than maximum of 4096. 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. Column headers will not fit within the space defined between top and bottom margins total number of lines increased to the following value. 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 has been increased to the indicated value to provide enough space for the column headers and five lines of data.
1522 Error
1526 Error
1529 Error
Status field is not accessiblecannot display Status History. 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 Error
Update of custom operation failed. The update of the custom operation failed. An associated error message contains details about the update failure. A failure when opening or writing to the file holding the custom operation is a common cause of this problem. X, Y, or both, coordinates are out of range. 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. Cannot format diary entry. An error occurred while formatting the diary text for a field. An associated error message contains details about the failure. Must specify a user name. You must specify a user name to log in. You can dismiss this window without changing the login information for the current user. To change the login information, specify a user name. Cannot query servers. An error occurred while trying to create a list of the forms that are available from each of the connected servers. An associated error message contains the details of the failure. Supply a name for your macro or custom report. You are requesting that a macro or custom report be saved. However, you have not specified 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. You cannot specify a COUNT operation with a column layout without specifying a field name. You have 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 will be printed under.
1531 Error
1539 Error
Attempt to create macro or custom report failedfile system error. The file system was not able to create or write to the file holding the definition of the operation. An associated error message contains details of the failure. You have entered an improperly formatted value for a date/time field. The format of the time value is not recognized. 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 perform the operation again.
103
1543 Error
A field name is required for all operations except COUNT. All of the statistics operations (except COUNT) require a field name. This name specifies the field the operation will be performed on. You must specify the field name (or arithmetic operation) on which the operation will be performed. Value specified for field name not numeric or not a field. 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. You have entered an improperly formatted value for a real field. 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 try the operation again. You entered a nondigit character for a numeric field. 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 try the operation again. You entered a value for a numeric field that is either smaller than the minimum size allowed or larger than the maximum size allowed. The value you specified for the numeric field is either smaller than the minimum size or larger than the maximum size. Use Remedy Administrator to confirm the size limits of the field properties.
1544 Error
You have entered an improperly formatted value for a decimal field. 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 perform the operation again. Modify All operation failed during operation on request with ID <number>. 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. Details about the error are in an associated error message. Correct the error, and try the operation again. No macros are defined. Because there are no macros defined, you cannot run or edit a macro. Define one or more macros before you open the Select Macro or Edit Macros windows. You cannot locate the selected command. The requested user command cannot be located. If you are selecting the command interactively, the command has probably been deleted or moved by another user since you started the program. If you are selecting the command from a macro, the command has probably been deleted since the macro was recorded.
1555 Error
Enter a command name. You are requesting that a user command be saved. However, you have not specified 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. Enter a command string to execute. You are requesting that a user command be saved. However, you have not specified 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. Cannot create user commandfile system error. An error occurred while trying to create a user command because the file system was not able to create or write to the file holding the definition of the operation. An associated error message contains details about the failure. Error in macro or custom report. An error occurred while trying to perform the operation specified in the macro or custom report. You might get this error message for the following reasons: The macro or custom report does not exist. It may have been deleted or moved to a new location. Or, a macro may 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. Record the macro or custom report operation again.
1557 Error
1558 Error
1559 Error
1562 Error
Second part of report operation missing or invalid. 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. Enter a directory to store the command in. You are requesting that a user command be saved. However, you have not specified 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 you want this user command definition to be stored in. Second part of statistics operation missing or invalid. 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.
1563 Error
1565 Error
105
No custom report formats are defined. There are no custom reports defined. Accordingly, you cannot manage a custom report. Define one or more custom reports before opening the Manage Custom Reports window. Unrecognized operation detected while loading a custom report format. 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. Empty macro definition. 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 have not performed any operations since you started recording. Perform the operations you want to record before saving the macro. You cannot create new item. An error occurred while trying to create the new definition on the Customize View window. An associated error message provides details about the error. Usually, the cause of the error is a lack of system resources. File name is longer than maximum allowed. 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. You cannot use a selection value name in Status Historyyou do not have access to the Status field. 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.
1569 Error
1572 Error
1574 Error
1579 Error
1580 Error
Missing closing quotation mark on a character string or name. A field name or character string has an opening quotation mark as required, but there is no corresponding closing quotation mark at the end of the string. You must supply the ending quotation mark. If the name or string contains a quotation mark that is the same type of quotation mark around the value, you must double the embedded quotation mark. Unexpected character at this location in the search line. 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 position that is marked. Correct the error, and perform the search again.
1581 Error
Logical operator expected at this position. The only legal operator at this position in a search line is a logical operator (AND, OR, or NOT). Correct the format for the line, and perform the search again. Relational operator expected at this position. The only legal operator at this position in a search line is a relational operator (=, !=, <, <=, >, >=, or LIKE). Correct the format for the line, and perform the search again. Field or value expected at this position. At this position in a search line, a field reference or value is expected. Correct the format for the line, and perform the search again. Too many nested levels of parentheses in command. There are too many open parentheses (maximum of 64 open parentheses active in the search line) at this position in the search line. The search operation has become too complex. You must have fewer levels of nested operations within the search operation. Correct the format for the line, and perform the search again. Closing parenthesis expected at this position. A closing parenthesis to match an open parenthesis specified in this command was expected at this position. There must be a balanced number of parentheses in the command. Correct the format for the line, and perform the search again. Unknown field referenced in search line. 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 Correct the format for the line, and perform the search again.
1586 Error
1587 Error
1589 Error
Format for status history reference is invalid. The format for 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). Correct the format for the line, and perform the search again.
107
1590 Error
Format of date or time value is not recognized. 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 will default to an appropriate value. However, the format of the portion of time that is specified must match the rules for time stamps. Correct the format for the line, and perform the search again. You cannot translate the group name in the Group List or Assignee Group field. 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. Overflow while expanding active link process (maximum expanded command is 4096 bytes). 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.
1592 Error
1600 Error
1601 Error
Overflow while expanding active link macro parameter (maximum expanded parameter is 4096 bytes). 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.
1603 Error
Set fields active link running a process failed. The process that was run to get a value for a field has failed. An associated error message contains details about the failure. Correct the situation causing the failure, and perform the operation again. Active link attempting to set nonexistent menuresetting to the default menu. An active link has 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. Correct the active link to refer to an existing character menu, or create the character menu needed by this active link.
1604 Error
Active link trying to set nonexistent field. An active link has specified a new character menu for a field that does not exist. Correct the active link to refer to an existing field for the form, or remove the active link. No user commands are defined. There are no user commands defined. Accordingly, you cannot run or edit a user command. Define one or more user commands before you open the Select User Commands window. Value exceeded report maximum length. A value exceeded the maximum size of a value that is allowed within 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 create the report again. The statistic operation is too complexit references more than 50 distinct fields. You have 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. 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. To use the online help system under the UNIX environment, set the environment variable ARHELP to point to the directory containing the help files for the AR System.
1609 Error
1610 Error
1611 Error
Found more entries than expected during workflow processing. An active link action was extracting data from another form or another 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. Source used in Push Fields active link not allowed: PROCESS, DDE, or SQL. 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. An internal error has occurred during workflow processing. This error message occurs when unexpected, incorrect, or inaccurate definitions are encountered during processing. This indicates a corrupted or incomplete definition. This message is usually accompanied by specific errors that explain the failure. Cannot find this macro name in macro list. This error message is returned when you attempt to access a macro that is not found in the macro list. To continue, verify that the macro exists.
1612 Error
1613 Error
1620 Error
109
Not all entries are displayed in the selection list. The selection list opened by an active link operation contains more items than can be displayed. The list contains the first 6000 matching items. An error occurred while updating the server. View has not been saved. During an export view operation, an error was encountered while attempting to update the view definition on the server. A message preceding this message contains details about the failure. Cannot access the active link debug file. Active link debugging is active. An error occurred attempting to open, close, or write to the active link debug file. An associated message contains additional information about the failure. Reporting to an external report writer is supported on the Windows platform only. A macro specified that a report is to be generated to an external report writer. This functionality is supported only on the Windows environment. Too many windows are open. Close some windows before opening another. There is insufficient memory available to open additional windows or applications. Your window resources are low; close unwanted windows or applications. There is insufficient memory available to perform basic Remedy User functions; for example, you cannot access a form because there are insufficient memory resources to open it. Servers with versions earlier than 3.0 are not supported by this client. This error is generated by Remedy User version 4.0 (or later) when attempting to connect to an AR System server version prior to 3.0. Only version 3.0 (or later) AR System servers can be used by Remedy User version 4.0 (or later). Incorrect format in the definition file. This error message is generated by Remedy User when loading a form. It usually indicates that the cached form definition files (the .arv and .arf files) contain unexpected content. Unable to read the recent search file. The system cannot read the recent search file. Attempt the search using the advanced search capabilities of Remedy User. Unable to read the saved search file. The system cannot read the saved search file. Attempt the search using the advanced search capabilities of Remedy User. Unable to write the recent search file. The system cannot save the recent search file. Reformat your search to continue.
1624 Error
1650 Error
1656 Error 1658 Error 1659 Error 1660 Error 1661 Error
Unable to write the saved search file. The system cannot save the search file. Reformat your search to continue. Error occurred in generating report. This message appears when there is an error during report generation. Click Show Details in the message box for more information. No report or an incomplete report will be generated. 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. Login macro action is not supported. You cannot record a macro that logs in to an AR System server. This action is not supported. One or more items match active link conditionsthis operation has been defined so that any match generates an 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 Warning 1800 Error 1801 Error 1802 Error 1803 Error 1805 Error 1806 Error 1807 Error
Run Macro was not executed because the macro contains statements that are not supported. In ARWeb 4.0, not all macro statements are supported. If the macro cannot be executed, this statement is displayed. Internal errorunable to create form information. There is insufficient memory available to allocate the form information structure. Close some open windows or applications, and log in again. Unable to connect to any servers. To operate Remedy User, you must have access to at least one server. Make sure that you have a network connection to a server and that it is running properly. You cannot create directory <directory_name>. While storing a macro or report, Remedy User failed to create a missing command directory on the local disk. Cannot open file <file_name>. Remedy User could not open or create a printer setup file for a custom report. System out of memory, executable file was corrupt, or relocation was invalid. During a Run Process active link action, WinExec returned Error 0. Executable not found. During a Run Process active link action, WinExec returned Error 2. Path not found. During a Run Process active link action, WinExec returned Error 3.
111
1808 Error 1809 Error 1810 Error 1811 Error 1812 Error 1813 Error 1814 Error 1815 Error 1817 Error 1818 Error 1819 Error 1820 Error 1821 Error 1823 Error 1825 Error
Insufficient memory to start application. During a Run Process active link action, WinExec returned Error 8. Invalid executable file format. During a Run Process active link action, WinExec returned Error 11. Incorrect version of Windows software. During a Run Process active link action, WinExec returned Error 10. Sharing or network protection error. During a Run Process active link action, WinExec returned Error 5. Application designed for different operating system. During a Run Process active link action, WinExec returned Error 12. Application developed for older version of Windows software. During a Run Process active link action, WinExec returned Error 15. Attempted to load second instance of application. During a Run Process active link action, WinExec returned Error 16. Attempted to load compressed executable. During a Run Process active link action, WinExec returned Error 19. Unknown executable format. During a Run Process active link action, WinExec returned Error 14. Invalid dynamic-link library. During a Run Process active link action, WinExec returned Error 20. Application requires Windows 32-bit extensions. During a Run Process active link action, WinExec returned Error 21. Unknown errorerror code = <error_code>. During a Run Process active link action, WinExec returned an unknown error code. WinExec failed for <action_type>. During a Run Process active link action, WinExec failed. Another error message documents the cause of failure. Failed to display all or some of the notification messages. Remedy User could not retrieve notification information from the Alert client. In general, this is because the Alert client is not responding. Unable to load Submit form. Form information could not be loaded. The form definition files may be unavailable or corrupt.
1826 Error 1827 Error 1828 Error 1829 Error 1830 Error 1831 Error 1832 Error 1833 Error 1834 Error 1835 Error 1836 Error 1837 Error
Unable to load Query form. Form information could not be loaded. The form definition files may be unavailable or corrupt. Unable to load Customize Default form. Form information could not be loaded. The form definition files may be unavailable or corrupt. Unable to load Customize View form. Form information could not be loaded. The form definition files may be unavailable or corrupt. Internal errorinvalid window description. An MDI child window could not be created because an internal windows function provided an unexpected result that was detected during window creation. Internal errorinvalid window description. An MDI child window could not be created because an internal windows function provided an unexpected result that was detected during window creation. Failed to create the dialog box. The status history modeless dialog box could not be created because of a Windows error. Memory failurecannot initialize the current statistics information. Remedy User has run out of memory while building the statistics list for the statistics report window. Invalid field nameattempt the operation again. You have entered an invalid field name in the report sort dialog box. Failed to create the AR System home directory <directory_name>. Could not create an AR System home directory while updating user login or server information. This usually indicates a serious disk problem. Internal error (1). An internal Windows error occurred while updating user login information. Specifically, Windows provided an invalid LB index. This usually indicates a serious Windows error. Internal error (2). An internal Windows error occurred while updating user login information. Specifically, Windows returned an LB error. This usually indicates a serious Windows error. Failed to create memory. Remedy User ran out of memory while building the user information list when updating the login information window.
113
1838 Error 1839 Error 1840 Error 1841 Error 1842 Error 1843 Error 1844 Error 1847 Error 1848 Error 1849 Error 1850 Error 1852 Error 1853 Error
Internal errorunable to initialize user information. Initialization of the user information in uiroot failed during user login. Internal errorunable to create form information. Remedy User ran out of memory while allocating the schemaInfo structure during user login. The X location and width of the symbol is greater than 1500. The X location of a field was made greater than 1500 in the Display Attributes dialog box. The Y location and height of the symbol is greater than 3000. The Y location of a field was made greater than 3000 in the Display Attributes dialog box. Failed to display the report. The report to file or screen failed to generate. Failed to get printer information. Printer driver initialization for the printer selected in printer setup has failed while printing a report. Report to file failed. Ensure that you have enough disk space. Remedy User could not open the specified report output file. Failed to create the user home directory <directory_name>. Creation of a home directory for the last user has failed during application startup. This usually indicates a serious disk problem. The user home directory in the ARuser section of the win.ini file cannot be located. 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. Not enough memory to initialize font. Remedy User ran out of memory while building the font preference structure when changing AR System font preferences. Not enough memory to initialize all fonts. Remedy User ran out of memory while building the font preference structures during font preference dialog box initialization. Action Request System requires Windows enhanced mode. During application startup, it was detected that Windows is not running in enhanced mode. The working directory must be the same as the program path in File > Properties. During application startup, it was detected that the Windows working directory has not been set to the AR System application directory.
Failed to initialize the system globals. During application startup, Remedy User globals could not be initialized. This usually indicates a serious Windows error. Failed to initialize the user information. During application startup, 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. Unable to register window class. You have encountered an unusual error condition. Unable to register submit window class. You have encountered an unusual error condition. Unable to register query window class. You have encountered an unusual error condition. Unable to register child window class. You have encountered an unusual error condition. Unable to register queryList window class. You have encountered an unusual error condition. Unable to register report window class. You have encountered an unusual error condition. Unable to register custom windows class. You have encountered an unusual error condition. Unable to register customize view class. You have encountered an unusual error condition. Unable to register customize default class. You have encountered an unusual error condition. Unable to register text viewer window class. You have encountered an unusual error condition. Unable to register text view class. You have encountered an unusual error condition. Unable to register Dialog2 class. You have encountered an unusual error condition.
115
Unable to create frame. Creation of the MDI frame window failed during Remedy User startup. This usually indicates a serious Windows error. Unable to initialize APIs. Windows API initialization has failed during Remedy User startup. This usually indicates a serious Windows error. Unable to load the menu accelerators. Remedy User for Windows failed to load menu accelerator tables during startup. Failed to initialize DDE. DDE API failed during Remedy User startup. Internal Errorunable to create form information. Remedy User ran out of memory while allocating the schemaInfo structure during startup. Internal ErrorLoadIniFile. User or password data is incorrect or irretrievable from win.ini file during Remedy User startup. Unable to load Submit form: <schema_name>. Form information could not be loaded. The form definition files may be unavailable or corrupt. Unable to load Query form: <schema_name>. Form information could not be loaded. The form definition files may be unavailable or corrupt. Failed to connect to application <DDE_application_name> using <specified_DDE_path> path. DDE connection failed due to incorrect application file path setting. Invalid DDE action specified. DDE action other than EXECUTE, POKE, or REQUEST DDE action was specified. Set Fields active link running a process through DDE failed. A DDE-invoked process failed and did not provide data to be used as the source of a Set Fields active link. The DDE application name is not defined in dde.ini file. DDE Target application entry was not found in the dde.ini file while building DDE file specification for a DDE operation.
1883 Error
The format for the application section in dde.ini is invalidyou can specify only CSV or TAB for format. While reporting to an application, the DDE entry for the target application in the dde.ini file does not specify CSV or TAB format.
The <item> item is missing from application section <section> in dde.ini. 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. Memory allocation failure during DDE process. Remedy User ran out of memory while allocating memory to support a DDE action. Error in reading the GetDetails Information for list item number <item>. While processing a notification get details DDE request, the specified item could not be found in the notification application. Grid width and height must be between 2 and 128. The customize view grid width and height parameters are not within the allowed range. Blanks and spaces are invalid in a view name. No description. Date is out of allowed range of 01/01/1970 to 01/19/2038 (GMT) for Windows client. If you enter a date outside of the listed range, based on Greenwich Mean Time (GMT), you will 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. For more information, see knowledge base article ID 5816 on the Remedy Customer Support web site.
1890 Error
Currently running MISCDLL.DLL version <old_version_number> is an old version. Version <current_version_number> of MISCDLL.DLL is required. This may be the result of installing an older version of Remedy User or Remedy Administrator in the same directory as a newer version. Reinstall the latest version of the Remedy User or Remedy Administrator.
Time is out of allowed range of <number> and <number>. AR System cannot process a time that is out of range. Try again, using a time within the allowed range. Date and time are out of allowed range of <number> through <number>. AR System cannot process dates and times that are out of range. Try again, using a date and time within the allowed range.
117
Cannot perform this operation in the current mode of the form. AR System cannot perform this operation in the current mode of the form. Try again with a different mode of the form. The system is out of memory or resources. The system is out of memory or resources while running active links. Terminate unused applications in order to make system resources available. You have entered an improperly formatted value for a currency field. A currency value has been 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. Date is out of allowed range of 01/01/4713 B.C. - 01/01/9999 A.D. A date value has been entered that is out of range. Date fields can accept values from January 1, 4713 B.C. to January 1, 9999. There is no Home Page form available. Please verify your user preferences or check with your administrator. The Home Page form name specified on the Home Page tab of the Options dialog box in Remedy User or on the Home Page tab of the AR System User Preferences form cannot be found. Verify that you have entered a valid AR System server and form name in your Remedy User options or contact your AR System administrator for assistance.
Cannot retrieve starting active link: <active_link_name>. An error occurred while loading the starting active link for an entry point guide. Contact your AR System administrator for assistance. Error generating application list field content. An error occurred while generating the dynamic content for the Application List field. Contact your AR System administrator. <entry_point> is not a valid entry point. The entry point chosen from File > Recent Entry Points and the form or guide is no longer a valid entry point. You have entered an invalid currency type. The specified currency value is a not an allowable currency type. Contact your AR System administrator. Failed to create the window. Could not create a new child window. There may be a resource or memory limit on the client.
1926 Error 1930 Error 1950 Error 1951 Error 1952 Error 1953 Error 1954 Error 1955 Error 1957 Error 1958 Error 1959 Error 1960 Error 1961 Error 1962 Error
Unable to initialize frame. Creation of the main MFC frame has failed during Remedy User startup. This usually indicates a serious Windows error. Login aborted. You cannot close all windows. The login was aborted because all open windows could not be closed. Error loading menu. 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. Failure trying to expand character menu. Character menu expansion failed in the symbols library; the menu did not load. Unable to load menu. Indicates a serious problem with menu loading. Error getting group information. Remedy User failed to get the group list from the server. Failure loading group information. Group list expansion has failed while trying to build the group list. Error creating a menumenu too large. Adding a submenu to a menu has failed and resulted in a Windows error. Unable to write to file <file_name>. The field editor could not open a file with write permissions. Unable to read file <file_name>. The field editor could not open a file with read permissions. Unable to create work buffer for file <file_name>. Allocation of global memory failed while performing edit operations. Cannot write file <file_name> to disk. Writing to a file failed in the field editor. You are trying to access a menu with more than <number_of_entries> entriesthe menu will be truncated. The number of items returned for a menu load exceeded the maximum allowed. Error creating menuout of resources. Failed to build the Windows popup menu. The application resource memory area is probably full.
119
Unable to load help. Windows Help system failed to load. This is usually caused by the failure to create a temporary file. Unable to commit changes. Cannot commit changes to a dialog box or to a submit or a modify record action. Functions MAX and MIN are not supported in Push Fields actions. Functions MAX and MIN are not supported in Push Fields actions. Currently Push Fields actions provide little information about the destination field. Without knowledge of the destination data type, these two functions cannot be evaluated correctly. Failed to initialize MAPI mail. This error occurs when 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. Send Mail failed. The message was not sent. This error occurs when the MAPI mail system failed to send the mail when sending an AR System object to a mail recipient. Due to the length limit of the SQL command by Crystal Reporting Engine, only the first <number> entries are reported. This error occurs when the Crystal Report Engine returns less data than requested. The Crystal report contains an invalid SQL statement. The SQL command passed to the Crystal Reporting Engine is invalid. Verify the syntax in the SQL command. The report format is reset to Record. The report type is being reset to Record mode. Too many columns (fields). Ensure that all column titles fit into one report line. Too many fields have been selected in a Column type report. The specified directory is not valid. The directory specified in a file path is not valid. The directory may not exist or the user may not have access rights. Failed to save file <file_name>. An I/O error occurred while generating a report to file. One or more active links failed when closing the form. Do you still want to exit the application? When exiting Remedy User, an active link failed on window close. This note gives the user a chance to abort Remedy User termination.
1966 Error 1967 Error 1968 Warning 1969 Error 1970 Warning 1971 Error 1972 Error 1973 Error 1974 Note
1975 Error
Report will not be displayed in specified external program because of the following error: <type_of_error>. There was a failure opening an external viewer (for example, Crystal Reports) during the print preview operation.
1976 Warning 1977 Error 1978 Warning 1979 Error 1980 Error 1986 Error 2001 Error
The given directory does not exist. Create the new directory? The directory specified while saving a macro does not exist. The directory cannot be created. The directory specified while saving a macro cannot be created. This is likely caused by a file system error. The given directory does not exist in the search path. Add the new directory? The directory specified does not exist. Printer error occurred. Verify the printer setup on your system. A report cannot be printed. This is usually caused by problems with your printer setup or with cables. A printer error occurred. The default page setup is used. Page setup could not be determined, so printer defaults are being used. You have entered an improperly formatted value for a currency field. This error message is returned because you did not enter a valid currency value on a currency field. For example, you entered 1,00 USD. Cannot allocate memory. The system encountered an error during a call to allocate memory. In general, this error occurs when there are too many processes running at one time or when some processes have grown to occupy most or all of the available memory on your client machine. You can recover that memory by shutting down unneeded processes. In addition, restarting processes that have been running for a while will help by recovering space those applications may have leaked over time. Cannot read the configuration file. 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, then restart the tool. You cannot connect to the X server. The aradmin program (Remedy Administrator) on UNIX is an X program. It requires that an X windowing system be running to allow the program to operate. Currently, there is not a window system running in your environment. Start a windowing system, and then restart the aradmin program.
2002 Error
2003 Error
121
You cannot initialize the AR System. Failure occurred during a call to initialize AR System client environment. An associated error message contains details about the failure. Correct the problem reported, and restart the tool. No servers are currently accessible. None of the servers specified in Remedy Administrator are currently accessible. Associated error messages provide information about why the tool could not connect. Try the operation again after the issues have been resolved. Failure while retrieving entries from the server directory file. An error occurred while retrieving entries from the server directory file. The error may have been caused by an inability to allocate memory to hold the list of servers encountered or by an inability to find or open the directory file (/etc/ar for UNIX or \<ar_home_dir>\ar for Windows). No servers are specified on the command line or in the AR System directory file. 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. 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 servers that are not currently accessible.
2006 Error
2009 Error
2100 Error
You have specified a field ID within the reserved range. You are attempting to assign an ID number to a form field, but that field number is within the range of reserved fields (100 to 536870911) in the AR System. You can create a field in this range, but be aware that the field may 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 536870912). If you are running Remedy Administrator, leave the field ID blank to automatically generate an available ID outside the reserved range.
2101 Error
Your filter definition and all associated actions will be deleted. You are deleting a filter. 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. No structures are in the import file. You specified a file to be used 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 there is nothing that can be imported. Make sure that you have specified the correct name for the file you are trying to import. The Import operation in Remedy Administrator is used for structure definitions only. If you are trying to import data, use Remedy Import, arimport.
2102 Error
2103 Error
Incorrect parameter specificationverify field name spelling. When specifying a field reference using the field name, the system could not find a field with the specified name for the current form. Correct the spelling of the field name in the reference, and make sure that the field exists for the target form. You have not saved changes on this screenthey will be lost if you continue. You have made one or more changes on the current window since changes were applied. You are now trying to close the window. If the window is closed, all changes since the last Save will be lost. Click Cancel to cancel the dismiss action and retain the window and its information. This server <server_name> is not licensed from Remedy and has limited capabilities. For unlimited capabilities, contact your Sales Representative or visit www.remedy.com. This error occurs when the server reports an invalid license during login verification. Your form definition and all associated data will be deleted. You are deleting a form. A Delete operation removes the definition, the workflow associated with the definition (such as filters and active links), and all the data associated with the definition. If you proceed, the definition will be removed. If you cancel, the operation will be terminated, and the definition will be retained. Your active link definition and all associated actions will be deleted. You are deleting an active link. A Delete operation removes the definition and the workflow associated with the definition. If you proceed, the definition will be removed. If you cancel, the operation will be terminated, and the definition will be retained. Language defined by LANG environment variable not recognizedusing default on server. The language defined in the LANG environment variable is not recognized by AR System. The default language of the server will be used instead. The following field labels are duplicated in your form. The field labels identified in the message are used for multiple fields on the form. Because fields are uniquely identified by field ID, duplicate labels are allowed. Because it can be confusing to have fields with duplicate labels, consider changing one of the labels. Changes on the following screens will be lost if you continue. Since changes were last applied, you have made one or more changes on a window that is a child of the current window. A request has been made to close or dismiss the parent window. If the window is dismissed, all changes since the last Save will be lost. Click Cancel to cancel the dismiss and retain the current window, its children, and their information. Your menu definition will be deleted. You are deleting a character menu. A Delete operation removes the definition. If you proceed, the definition will be removed. If you cancel, the operation will be terminated, and the menu definition will be retained.
2104 Error
2109 Error
2115 Warning
2117 Warning
123
2119 Warning
The following fields (including data), active links (or both), will be deleted. You have requested that one or more fields or active links be deleted. The fields and the active links affected are listed as part of the message. Deleting fields will delete the associated data for the fields and requires restructuring the table in the database. Deleting active links will remove the workflow associated with the active link. Proceed with the Delete operation to continue. Click Cancel to stop the Delete operation from being performed. Additional errors were truncated. The operation encountered a number of errorstoo many errors to fit in a single dialog box. The most critical errors are displayed in the current dialog box. Correct those errors, and repeat the operation to see if the other errors remain. Your filter action will be deleted. You are deleting a filter action. A Delete operation removes the action definition. If you proceed, the action definition will be removed. If you cancel, the operation will be terminated, and the action definition will be retained. Your active link action will be deleted. You are deleting an active link action. A Delete operation removes the action definition. If you proceed, the action definition will be removed. If you cancel, the operation will be terminated, and the action definition will be retained. Your form view will be deleted. You are deleting an administrator view of a form. A Delete operation removes the view definition. Users using this view will be reset to the default view the next time they connect to the system. If you proceed, the view will be removed. If you cancel, the operation will be terminated, and the view will be retained. Your form view name is not unique. The name of an administrator view must be unique for the form. Another view exists with the same name. Choose a unique name for the view. You currently have an escalation time specified. You are changing the timing setting for an escalation from calendar to interval and there is a calendar screen open on the system. The calendar screen is not appropriate when using an interval time setting. This prompt enables you to cancel the operation or to specify that the open window be closed. The full text search (FTS) reindex operation can take a long time. 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 may suffer, perform reindex operations during off hours whenever possible.
2120 Note
2121 Warning
2122 Warning
2123 Warning
2127 Warning
2128 Warning
Your escalation action will be deleted. You are deleting an escalation action. A Delete operation removes the action definition. If you proceed, the action definition will be removed. If you cancel, the operation will be terminated, and the action definition will be retained. Your escalation definition and all associated actions will be deleted. You are deleting an escalation. A Delete operation removes the definition and the workflow associated with it. If you proceed, the definition will be removed. If you cancel, the operation will be terminated, and the definition will be retained. You are logged in as a subadministratoraccess to some structures and functions has been disabled. You are logging in to the system as a user who is a subadministrator. A subadministrator does not have access to all of the functions on the tool. If you find that you are not allowed to perform a specific operation, it is probably because you do not have sufficient permissions. You can log in as an administrator to get full access.
2129 Warning
2130 Warning
2131 Warning
Incompatible data types in qualification line. The data types of a pair of values in a qualification line are not compatible. In the qualification line, make sure that operations are performed only between items with compatible types. Full text search (FTS) index operations will be started. You have activated the full text search (FTS) subsystem of AR System. Items that are pending indexing will begin indexing immediately. Full text search (FTS) index operations will be shut down. You are deactivating the full text search (FTS) subsystem of AR System. All operations that require updating the FTS index will be queued and performed when the system is activated again. You must be a member of the Administrator or Subadministrator group with a fixed license to use this tool. Administrative functions within AR System require a user who is a member of the Administrator group (with full functionality) or Subadministrator group (with limited functionality). In addition, the user must be assigned a fixed write license. The user attempting to obtain access does not meet these criteria.
2134 Warning
2135 Error
The selected distributed mapping will be deleted. You are deleting a distributed mapping. A Delete operation removes the mapping definition. If you proceed, the definition will be removed. If you cancel, the operation will be terminated, and the definition will be retained.
125
2136 Warning
The selected pending mappings will be deleted. You have selected one or more pending mapping definitions to be deleted. A Delete operation will remove them from the set of operations to be performed. The distributed operation that was initiated against these items will be removed. If you cancel, these items will be retained. Changes on the mapping fields screen will be lost if you continue. You have made one or more changes on the current window since changes have been applied. A request has just been made to close or dismiss the window. If the window is dismissed, all changes since the last Save will be lost. Click Cancel to cancel the dismiss and to retain the window and its information. You are attempting to delete a Distributed Server Option (DSO) form or fielddo you want to continue? The form you are trying to delete is one of the special DSO forms. Deleting the form may affect the functionality of DSO. When you restart the system, the server automatically recreates the form. Or, if you are deleting a field, the field you are deleting is one of the fields that make the current form a DSO form. Deleting this field will make this form unavailable as a DSO form. When the system is restarted, a new form that contains all the distributed fields will be created.
2137 Warning
2138 Error
2139 Warning 2140 Error
Changes in current view will be saved if you continue. You are trying to change views without having saved your changes to the current view. If you continue, your changes will be saved automatically. Other forms depend on the current form. Deleting this form will cause forms that depend on it to be deleted. Are you sure you want to continue? The form you are trying to delete is a base form for one or more join forms. Because join forms are dependent on this form, all such forms will be deleted if you delete the base form. Continue only if you want all dependent forms to be deleted.
The following field names or IDs have blank labels in your form. You have applied changes to a form that contains one or more fields with blank labels. Your guide will be deleted. You are deleting a guide. If you proceed, the guide will be removed. If you cancel, the operation will be terminated, and the guide will be retained. Your application will be deleted. You are deleting an application. If you proceed, the application will be removed. If you cancel, the operation will be terminated, and the application will be retained.
2144 Warning
Your packing list will be deleted. You are deleting a packing list. But because a packing list is really only a container of AR System objects, if you proceed, deleting the packing list does not delete any underlying forms, workflow, and so on, that are contained in the packing list. If you cancel, the operation will be terminated, and the packing list will be retained. Your web service will be deleted. You are deleting a web services object. If you proceed, you will only delete the AR System web service object and not any underlying XML schemas or WSDL handler URLs. If you cancel, the operation will be terminated, and the web service will be retained. 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. This warning is returned when you add a Form (Between open and close services) to an existing web view and try to save it. This is a limitation of the authoring environment that does not allow nested or intersecting FORM declarations. Open and close services are the start and end of a form respectively. The authoring environment will check to make sure that this situation is brought to the attention of the user if it exists.
2145 Warning
2146 Warning
2148 Warning
System does not ensure consistency if global elements/complex types in use are changed. Please choose 'embedded' option if you are not sure. This warning is returned when you select the Linked option from the Advanced Properties dialog box after clicking the Options button in the Web Service tab. Proceed at your own risk. The system does not guarantee any consistency.
'Public' access is not specified. This will force users to login before accessing wsdl. This warning is returned when you do not have access to that web service and you try to save a web service without public permissions. You cannot allocate memory. The system encountered an error during a call to allocate memory. In general, this error occurs when there are too many processes running or when some processes have grown to occupy more, or all, of the available memory on your client machine. You can recover that memory by shutting down unneeded processes. Additionally, restart processes that have been running for a while to help recover space those applications may have leaked over time. Only integer can use numeric text type. While defining properties for a field, you attempted to assign the field type Numeric Text to a field other than an integer field. Only fields with the data type Integer may be of numeric text type. Only selection type can use check box. While defining properties for a field, you attempted to put check boxes on a field other than a selection field. Only fields with the data type selection can use check boxes.
2202 Error
2203 Error
127
Unrecognized field type. Incompatible data types in qualification line. The type specified for the field is not recognized. Update the definition of the field to indicate a valid display type for the field. Set Up Search Database command failed during Import. Remedy Administrator failed to import the required forms while setting up the Search database. This error can occur if a server exits unexpectedly or fails to import because of some other server-related cause. Verify the server status, and try the Set Up Search Database command again. You can not perform Synchronization of Search databases for same or different servers at the same time from the same instance of the Remedy Administrator. More than one Sync Search Database command cannot be issued from the same instance of Remedy Administrator. Open another session of Remedy Administrator to perform these operations simultaneously.
2207 Error
2208 Error
Could not load the definition file from the resource. The definition file of the search database in Remedy Administrator did not load. Close and reopen Remedy Administrator before you try the operation again. If the error persists, contact Remedy Customer Support. Field <field_name> has a duplicate name. Please select a unique name for this field before saving the form. All other changes are not saved. This form cannot be saved, because two or more fields have the same database name. Make sure that each field has a unique database name, and save the form again.
2209 Error
2214 Error
You cannot open the export file. The file specified to receive the exported definitions cannot be opened by the tool. This error can be the result of an access problem or of a nonexistent directory. Review the associated error message for details. Try the operation again when the error has been corrected. Form definition problem: invalid field specification. A problem was encountered while trying to build the GUI structure to represent a field on a screen. An associated error message contains more details. Button field is missing an active link assignment. This compatibility error occurs when you use a 3.0 (or later) UNIX Administrator Tool or Remedy Administrator to connect to a pre-3.0 server. In the pre-3.0 AR System, all buttons in a form must have an assigned active link. You cannot open configuration file. An error occurred while attempting to open your configuration file. An associated message contains details about the error. Resolve the error, and repeat the operation.
2228 Error
2231 Error
X or Y (or both) coordinates are out of range. The X or Y coordinates you specified for the layout of a form field are not in the valid range. The range for the X coordinate is 0 to 1500. The range for the Y coordinate is 0 to 3000. Change the coordinate to a valid range. Enter a form name. Specify the name of a form so you can complete the specifications for the window. Enter a user name. Specify the name of a user so you can log in. Enter a name, and click Save. Cannot query servers. An error occurred while trying to retrieve the list of forms available to the new user. The system could not connect to the servers. An associated message contains more details. A selection is required. To perform an import or export operation, select one or more items to be imported or exported. You cannot open the specified file. An error occurred while attempting to open a file. An associated error message contains additional information about the failure. Correct the error, and try the operation again. Select an item. No field or active link is currently selected on the window; therefore, you cannot select the Delete operation. To delete a field or active link, select the item, and click Delete. Cannot delete the selected item from the list during a cut operation. An internal error occurred while attempting to remove an item from an internal list. Exit the tool and start the tool again. No data entered at selected menu level. There is no menu definition at the selected level in the menu. Save all work on the current window, and exit the window. The error message should be dismissed when you reopen the character menu definition. You must enter a label before selecting Insert or Modify. You must enter a label for a menu item that you are creating prior to selecting Insert or Modify. Enter a label, and reselect the desired operation. No data entered at previous menu level. There is no menu definition 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 no longer be displayed when you reopen the character menu definition.
2232 Error 2234 Error 2236 Error 2241 Error 2243 Error 2269 Error 2279 Error 2281 Error
129
Enter a filter name. You have not entered a name, which is required, for the filter you are creating. Enter a name, and click Save. The message number is invalid. When creating a message type action, the message number is outside of the allowed range. User messages have message numbers of 10000 or greater. Correct the message number, and click Save. You must select a form. You have not specified a form for the structure you are creating. You must specify the form to which the structure is attached. You must select at least one operation. You have not specified an operation for the filter or escalation to execute. You must specify one or more operations. Select an operation and click Save. Missing closing quotation mark on a character string or name. When parsing a line, an open quotation mark was encountered, but no corresponding closing quotation mark was found. Review the string for the missing quotation mark. If a quotation mark is contained within a string, you must double the contained quotation mark. Unexpected character found. When parsing a line, an unexpected character was encountered. An associated message contains information about the position within the line where the unexpected character was encountered. A conditional operation expected at this position. When parsing a line, a conditional operation was expected but not found. An associated message contains information about the position within the line where the operation was expected. A relational operation expected at this position. When parsing a line, a relational operation was expected but not found. An associated message contains information about the position within the line where the operation was expected. A field or value expected at this position. When parsing a line, a field or value reference was expected. An associated message contains information about the position within the line where the field or value was expected. Too many nested levels of parentheses in command. When parsing a line, the system supports a maximum of 64 levels of nested parentheses. The string being parsed has more than 64 levels of nested parentheses.
2291 Error
2292 Error
2293 Error
A closing parenthesis expected at this position. When parsing a line, a closing parenthesis was expected. An associated message contains information about the position within the line where the parenthesis was expected. Unknown field reference found. When parsing a line, a reference to a field was encountered, but it could not be translated to a known field for the current form. Make sure that you have used the correct type of quotation marks (for example, you placed a single quotation mark around a value that should have included double quotation marks). The message contains information about the position within the line where the field reference can be found. Value specified for selection not one of defined values for this field. When parsing a line, a value for a selection field that was specified was determined to be not one of the legal values for the field. An associated message contains information about the position within the line where the selection value can be found. You have entered too many parameters in a set fields assignment. 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 within the line where the function of the extra parameters can be found. Format of time value is not recognized. 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. Specify a directory and file name. You must specify a directory and file name to open a file. Specify both a directory and file name, and click Save. Please enter data. There is no data entered on the current screen. Make sure that you have 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. Selection fields require one or more values. A selection field requires that one or more values be specified. The field is not fully defined until it contains one or more values. Character menu Delete operation failed. An internal error occurred while removing an item from the menu. 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.
2298 Error
2299 Error
131
2308 Error
You have created the maximum number of filter actions allowed. A filter can contain a maximum of 25 actions. You are already at the maximum number of actions allowed. To perform additional actions, create a new filter with the same conditions, and add actions in the new filter. Specify an execution order that is greater than the current filter so the new actions run after the existing actions. Resulting file name is longer than maximum allowed. The file name specified is longer than the maximum file name supported by the system (up to 255 characters). Error encountered writing to file. An error occurred while trying to write to a file. An associated error message contains the details about why the write operation failed. Correct the problem, and try the operation again. You have created the maximum number of active link actions allowed. An active link can contain a maximum of 25 actions. You are already at the maximum number of actions allowed. To perform additional actions, create a new active link with the same conditions, and add actions in the new active link. Specify an execution order that is greater than the current active link, so the new actions run after the existing actions. You must select a form. You have not specified a form for the active link you are creating. You must specify the form to which the active link is attached. Enter an active link name. You have not specified a name for the active link you are creating. A name is required. Enter a name, and click Save. Select a field for your Execute On condition. 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. Select an execution condition for your active link. You have not specified when to execute the active link. You must specify one or more occasions for active link execution. Select an execution condition, and click Save. Unrecognized group in group list, or group list longer than maximum allowed. While parsing the contents of a Group List or Assignee Group field, a name was encountered that is not a recognized group name, or the total length of the field exceeds 255 bytes. Correct the problem, and continue with the operation. Assignment line error at position <location>. While parsing an assignment line, an error occurred. This message contains information about the position of the error in the line.
2311 Error
2319 Error
Qualification line error at position <location>. While parsing a qualification line, an error occurred. This message contains information about the position of the error in the line. You have entered an improperly formatted value for a real field. 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. Enter the value again in one of these formats, and click Save. You have entered a nondigit character for a numeric field. 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). Unrecognized arithmetic operation. The arithmetic operation specified is not legal in the current context. The internal field length may not be less than zero. The length specified by a character field must be greater than or equal to zero. Field IDs below 100 are reserved for core fields. You cannot create a new 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 Error
You have specified a field ID already in use. The ID for every field must be unique. You have specified an ID that is in use by another field. Change the ID to be unique. If you are using Remedy Administrator, you can leave the field ID blank for the new field, and a legal ID will be created automatically. You do not have a known server specified in your configuration filethe tool will default to the first server specified in your directory file. Your configuration file has 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.
2328 Error
2329 Error
There are no administrator macros defined. There are no macros 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. An error occurred while formatting your diary text. An error occurred while trying 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 not available.
2331 Error
133
2332 Error
One of the field names is invalid. 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 have specified legal fields. You must select a form. You have not specified a form for the filter you are creating. You must specify the form to which the filter is attached. Total width of your fields exceeds the maximum. The total width of all the fields specified for Get List fields is greater than the maximum of 128. 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. There are no If actions defined. Create at least one If action. No If actions have been defined for the filter, escalation, or active link. You must specify at least one If action. The field ID is illegal. 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 Remedy Administrator, you can leave the field blank, and a legal ID will be created automatically. You cannot change type of an existing action. You cannot change the type of an existing action. You must delete the existing action and create a new one. Delete operation failed. An error occurred while performing a Delete operation. An associated message contains additional information. Too many levels in nested macro. 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 within the same macro, but they cannot be nested more than 15 levels deep. Invalid parameter specification in the DDE assign line. The format of the DDE assignment line that is used within a Set Fields operation is not valid. Review the documentation for the expected format for the DDE line, and correct the line. Invalid macro definition file format. The macro specified is not in the correct format and is, therefore, unrecognized. You must specify a valid macro definition.
2343 Error
Selection values must be unique. The values specified for a selection type field must be unique. You have specified two or more values that are the same. The system cannot tell the difference between the two values if they are the same. You cannot expand menu <menu_name> for field <field_name>. An error occurred while attempting to retrieve and build the indicated menu for the specified field. An associated message contains more information. Field data type and assignment data type are not compatible. A value with an incompatible data type that cannot be converted has been assigned to a field. You must specify a value with a compatible (or at least convertible) data type. You have entered a value in your integer field that is outside of the legal range for integers. The value for an integer field is outside the range for a 4-byte integer value. Enter a value that is within the legal range for a 4-byte integer. Duplicate mapping namerename your distributed mapping. While creating a distributed mapping, you have assigned the mapping a name that is already used by another mapping. Mappings must have unique names. Return to the Modify Distributed Mapping window, and rename the mapping. Invalid mapping definitionrespecify your custom mapping. The tool could not decode the mapping definition for the custom mapping. The format of this definition has been manually changed, or there is a problem within the database with the storage of definitions. Create the custom mapping again. One of your mapping servers is not available or does not exist. Because the server specified as the source or the target of the mapping is not available, the system cannot retrieve the list of forms that are present on this server for menus (or a list of fields that are contained within a form) for a custom mapping specification. To specify a custom mapping or to view a menu of forms, wait until the server is available again. You do not have permission to perform Distributed Server Option (DSO) operations. You are connected to the system as a subadministrator, and you do not have access to the Distributed Mapping form to allow definition of Distributed Mappings. You must be an administrator or be given sufficient access by an administrator to create and modify distributed mappings. You have not entered data for any of your fieldsenter data for at least one field before clicking the Save button. The Set Fields action is not defined to assign values to fields. Specify the assignment of one or more fields.
2351 Error
2352 Error
2353 Error
2354 Error
135
An active link already exists in this form with the name: <active_link_name>. An active link with the same name already exists. The names of all active links must be unique. Change the name of the active link so that it is a unique name. You have entered a value in a real number field that is outside the valid range for real numbers. The value in a real field is outside the range for an 8-byte real value. Enter a value that is within the legal range for an 8-byte real field.
Get operation failed. An error occurred while the tool was attempting to retrieve a property from a field. Set operation failed. An error occurred while the tool was attempting to set a property for a field. <number> is not a valid number for the date <date>. The number must be between <number> and <number>. This is an out-of-range error. For example, the message is displayed if you entered 1/1/2075 as a date.
<name> is not a recognized <month_or_day>. This message is displayed if you misspell a month or day name. <name> is not recognized as a legal component of the date or time format string. This message is displayed if the format string you specified in the Control Panel is illegal. Date is out of allowed range of 01/01/1970 to 01/19/2038 (GMT) for Windows Client. If you enter a date outside of the listed range, you will receive this error message. GMT here is Greenwich Mean Time, the time zone from which all other time zones are adjusted. The table field <table_field_name> definition is corrupt. If you Save the form, you will delete this field. This message indicates the table field does not find a field ID referenced by a column in the table field. The qualifier for the table field may be improper. If you choose to proceed, the column representing the field ID will be removed from the table field. See the Developing AR System Applications: Basic guide for more information about table fields.
2366 Error
Table field <table_field_name> 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 Developing AR System Applications: Basic guide for more information about table fields.
2369 Error
The listed columns for the <table_field_name> table field do not have corresponding data fields. This message indicates that one or more columns in a table field do not match field IDs in the corresponding form. All columns with no matching field IDs will be removed from the table field when the table field is modified. See the Developing AR System Applications: Basic guide for more information about table fields.
2370 Error
Form <form_name> on table field <table_field_name> does not exist on server <server_name>. This error message is returned because the form has been deleted from the AR System server. For more information about table fields and forms, see the Developing AR System Applications: Basic guide For more information about servers, see the following AR System documentation: Configuring AR System Optimizing and Troubleshooting AR System Database Reference Guide
Enter an application name. This error occurs when you try to save an application without providing a name. Enter an application name before you save the application. Unable to save an image for the application. This message occurs when you select an invalid file type for the image you want to associate with an application. Valid file types include .bmp, .jpeg, .jpg, and .dib. Server <server_name> for table field <table_field_name> is not accessible at this time. The table field tried to connect with the listed server, but the AR System server is not running. Try again later. For more information about servers, see the following AR System documentation: Configuring AR System Optimizing and Troubleshooting AR System Database Reference Guide
2374 Error
Duplicate distributed mapping name. This message appears when you try to save a distributed mapping with an existing distributed mapping name. Change the name of the new mapping or delete the existing mapping. Page or Page Holder field cannot be set to a NULL Field ID. You cannot set the Database ID of the Page or Page Holder fields to a NULL value. You must supply a non-NULL value for the Database ID.
2380 Error
137
2381 Error
Error getting active links list. The error occurs when 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 try the operation again. Error getting filter list. The error occurs when Remedy Administrator is unable to complete an operation because it failed to obtain a filter list from the current server. Close the dialog and try the operation again. Error getting escalation list. The error occurs when Remedy Administrator is unable to complete an operation because it failed to obtain an escalation list from the current server. Close the dialog and try the operation again. The application state system form could not be found on the queried server. The AR System Application State form could not be found. Restart the AR System server, which will re-create the form, if necessary. The application roles system form could not be found on the queried server. The Roles form could not be found. Restart the AR System server, which will re-create the form, if necessary. The application roles system form did not contain any state fields. No state fields (fields with field IDs within 2000-2999) exist on the Roles form. A system failure occurred or you must add state fields to the form. The state fields included by default in the Roles form are the Test and Production fields. An entry in the state table could not be found for this application. The system failed to create an entry for the application in the AR System Application State form. Create an entry for the application manually. Could not query the application state table. A system error occurred or the AR System Application State form was deleted. Restart the AR System server, which will automatically re-create the form, if necessary. Unknown error code <error_number> encountered. The message with error code <error_number> is missing from the string table. Unable to initialize user information. Reading of user preferences from ar.ini failed. This can be due to an invalid or missing home directory for the selected user name. Make sure that the ar.ini file exists in the user home directory and that there is a home directory associated with the user in the aruser section of the win.ini file.
2382 Error
2383 Error
2404 Error
Unable to connect to any servers. While trying to log in and connect to the specified servers, Remedy Administrator failed to successfully connect to a server. This can occur when the server is down, when the network is too slow (leading to a time-out), or if you are not an administrator or subadministrator user for the server. Failed to initialize the system globals. You have encountered an unusual error condition. The user home directory is missing from the ARuser section in the win.ini file. While trying to initialize the user preferences, Remedy Administrator failed to read the home directory for the currently logged in user. The <directory_name> may be missing from the aruser section of the win.ini file or the specified directory may not exist. Currently running MISCDLL.DLL version <old_version_number> is an old version. Version <current_version_number> of MISCDLL.DLL is required. Installing an older Remedy User or Remedy Administrator in the same directory as a newer one may cause this error. Reinstall the latest version of the Remedy User or Remedy Administrator.
2412 Error
Failed to create memory. Remedy Administrator could not allocate memory for its data structure. Close one or more applications to continue. Failed to create the AR System home directory. Remedy Administrator failed to create the specified user home directory. Make sure that the path is valid and that the disk is not full. User Name is missing. You must specify a user name while trying to save user information in the Login Information dialog box. AR System home directory is missing. You must specify a home directory while trying to save user information in the Login Information dialog box. At least one field must have a value in a Set Fields action. You cannot save a Set Fields action without specifying a value for a field on the form. Specify a value for the field on the form to continue. You cannot delete an object that you are currently editing. You cannot delete an active link, filter, escalation, or form that is currently open. Close the window in question, and try the deletion again.
139
Failed to load the selected image file. The selected file is not a valid BMP (bitmap) file, or it is larger than the supported size of 15 x 16 pixels. Select an appropriate file to continue. You must specify a menu or button field for active links that execute on a menu or button. You selected Execute On: Menu Item/Button in an active link without associating it with a menu item or button on the form. Server <server_ name> not found in server list. You cannot access a server that is not specified in the list of servers you are logged in to. Add the server to your server list in the Login Information dialog box, and log in again. The following fields do not have valid values set: In an existing Set Fields action, Remedy Administrator found some fields whose values are no longer valid. This can occur if Remedy Administrator cannot allocate enough memory to get the fields value or if the fields data type is no longer valid. Specify an SQL command. To save an SQL Set Fields Action, you must specify an SQL command. This will not be validated in any way, but cannot be left blank. Enter an SQL command to continue. Could not remove all the specified pending operations. This message occurs when the server has a problem deleting the pending operation after you click Remove in the Pending Distributed Operations dialog. Supply a label index (greater than 0). In an SQL menu definition, you must specify the column number of the SQL query result that will be used to create the menu itself. Any number greater than 0 will be accepted. Supply a value index (greater than 0). In an SQL menu definition, you must specify the column number of the SQL query result that will be used as the value the menu choice inserts into its associated field. Supply an SQL command. To save an SQL menu definition, you must specify an SQL command. This will not be validated in any way, but cannot be left blank. Enter an SQL command to continue. Button field is missing an active link assignment. While saving a form using a 3.x (or later) Remedy Administrator into a 2.x AR System server, the specified button field was not associated with an active link. You must assign an active link to the button field (or delete the button) before you can save the form.
2437 Error
Cannot read forms for server. Remedy Administrator failed to read the list of forms on the current server. Remedy Administrator may have failed to allocate memory to save the list of forms, or there may be a network connection problem. You have selected more fields than will fit in the clipboard. Select fewer fields, and try again. If you have selected more than 300 fields on the screen, you cannot use the Edit > Copy operation. Select 300 or fewer fields to continue. The following field cannot be displayed in this view because it contains invalid properties. Remove it from this view by using the Fields In View dialog box. The specified field in the current view has missing or invalid display properties and cannot be displayed in the view. Remove the field from the view to continue.
Insufficient resources to create the palette. The floating palette tool bar used to create new fields could not be created because Windows has run out of memory. Close some applications, or restart your Windows session. Another view already exists with that name. The name you have specified is used by an existing view. Specify a new name for your view; remember that names are case-sensitive. You must specify the hours or minutes (or both) to retry a distributed operation. When defining a distributed mapping on the Options page, you have the option to specify the length of time to retry. If you have selected this option, you must enter this information. Get list of fields operation failed. Your attempt to get a list of fields from a server has failed. The server may have failed after you logged in to it. <value> is not a valid value for field <field_name>. Values set to <new_value>. When defining a Set Fields action in an active link, you have 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 will be set to the first member of the set of legal states. Note that <value> is outside the range for field <field_name>. When defining a Set Fields action in an Active Link, you have specified a numeric value that is out of range for that field. The Value field will not be set. You must enter a distributed mapping name. When creating a distributed mapping, you did not specify a name. Enter a distributed mapping name to continue.
141
You must enter an escalation name. When creating an escalation, you did not specify a name. Enter an escalation name to continue. The current custom mapping is not valid. Unable to display unmapped fields. You have tried to Show Unmapped Fields in a custom distributed mapping; one or more of the field mappings is incorrect. A value must be entered for the following fields: Request ID, Form, and Server. When specifying a Distributed Delete DSO Action for a filter, you must provide a request ID, form name, and server. The field can contain double quotation marks () or single quotation marks (), but it cannot contain both kinds of quotation marks. You have attempted to add or modify a DSO Action to a Filter with a field that contains a combination of double quotation marks 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 the To Server fields may 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 may not contain a combination of double and single quotation marks. These fields may not contain a combination of single and double quotation marks, because those values are stored already surrounded by either double quotation marks 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 attempted 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.
The width of a results list field and its separator combined is limited to 128 characters. This error occurs when the administrator attempts to make any column of the results list wider than 128 characters. You must have at least one field with a value in a push field action. This error occurs when you attempt 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 Error
This is a special object parameter in which you can only add another method which returns the same object. This error message occurs if you have defined an OLE method that has a parameter of type object (IDispatch), and you nest another method whose return type is incompatible to the object type or if you enter 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. This error message occurs if you have defined an OLE method that has a parameter of type pointer, and you nest another method whose return type is incompatible to the pointer type or if you try to enter a value for a parameter of type pointer. The parameter can only be filled by nesting another method whose return type is compatible. You can also use $fld$ to enter the value for a pointer parameter. AR Runtime will get or set the value of the $fld$ and will treat 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 have defined an OLE method that has a return type and you try to nest or call another method on this return type, 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.
Please select a matching function. This error occurs when you have defined an OLE method that returns a pointer and you try to nest an incompatible return type. The two pointer types do not match. Please select another one. You get this error message when you try to nest a method that returns a pointer, if the pointer is incompatible with the parameter pointer type you want to nest. You cannot call another method on the parent method. The Parent return type is not an Object. 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.
Please select a method that returns a pointer. When you nest a method to a parameter, the parameter must be of type pointer. You cannot add a method here. Type incompatible. This error occurs when you attempt to add or nest a method to a parameter, and the return value is incompatible with the parameter's native type. Cannot add the method. Incompatible objects. Try again. This error occurs when you attempt to add or nest a method, and the containing object of the child method differs from the return type object of the parent method.
143
2468 Error
The Constants and properties are for display only. Cannot be inserted by clicking the Add Method button. The constants, enums, and other data structures that are 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 Error
The Parameter or Return value is of wrong type. Please type in a proper value. When you provide a value for a parameter, Remedy Administrator will attempt to map it to the OLE methods parameter OLE type. If unsuccessful in the conversion, Remedy Administrator returns this error message explaining that the value cannot be converted to the native OLE parameter type. Please select a method to delete. This error occurs when you click Delete Method without first having selected a method. Can delete only methods at the root level. To be deleted, a method must be a nested parameter either at the parameter level or at the return level. You can't add methods to a return value. This error message occurs if you have defined an OLE method that has a return value, and you try to add a method by clicking Add Method when the selection is at the return node. A label must be unique and consist of one or more characters. Labels within guides must be unique. Rename the label, providing a name that has not yet been used in the guide. You have entered an improperly formatted value for a decimal field. The administrator defines the number of places to the right of the decimal point (precision) for a given field. The administrator may also define the high and low range for values entered into the field. The value you entered meet the criteria determined by the administrator. Please enter a server name. This message occurs when the Server Name field in an Open Dialog action is empty. Enter a server name to continue. Cannot edit return value. Right-click to select a Field. 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. You cannot have duplicate named predefined searches. Please give the entry a unique name. Predefined searches cannot have duplicate names. Enter a unique name to continue. Enter a packing list name. You must specify a name when creating or modifying a packing list.
No work space has been selected. You selected View > By Workspace, and you selected Enable Workspace; but you did not select a packing list. Select a packing list, and try the operation again. There is already another view with the same label, platform, and locale combination. 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.
Please enter a non-empty string in label and name fields. An error is returned because you attempted to create a view without a label or name. To continue, specify a view label and name. An unspecified error occurred. When deploying an application, an unspecified error was returned in generating HTML files that was not covered under errors 2483 to 2495. The file <file_name> could not be located. When deploying an application, the HTML file generation stopped because the HTML file could not be created. Bad Path: <path_directory> When deploying an application, the HTML file generation stopped because all or part of the path is invalid. The permitted number of open files was exceeded. When deploying an application, the HTML file generation stopped because the permitted number of open files was exceeded. You do not have the proper permissions to access the file <file_name>. When deploying an application, the HTML file generation stopped because the file could not be accessed. There was an attempt to use an invalid file handle. When deploying an application, the HTML file generation stopped because the file is either corrupted or the file is open in a non-shared mode. The current working directory cannot be removed. When deploying an application, the HTML file generation stopped because the current working directory cannot be removed. The number of directory entries for directory <path_directory> has been exceeded. When deploying an application, the HTML file generation stopped because there are no more directory entries.
145
There was an error trying to set the file pointer. When deploying an application, the HTML file generation stopped because there was an error trying to set the file pointer. There was a hardware error. When deploying an application, the HTML file generation stopped because there was a hardware error, for example, your drive is corrupted or you are trying to write to a network drive and the network is down. Attempted access to file <file_name> produced a sharing violation. When deploying an application, the HTML file generation stopped because a shared region was locked. There was an attempt to lock a region that was already locked. When deploying an application, the HTML file generation stopped because there was an attempt to lock a region that was already locked. The disk is full. When deploying an application, the HTML file generation stopped because the disk is full. The end of file was reached. When deploying an application, the HTML file generation stopped because the end of file was reached. Other forms depend on form <form_name>. If you delete this form, all other forms that depend on this form will be deleted. Do you want to continue? You are attempting to delete a form used as a member of a join form. If you continue, the join form will also be deleted.
2492 Error 2493 Error 2494 Error 2495 Error 2501 Warning
2502 Error
Warning: If you change the form, existing actions might be made invalid. Verify your existing actions. Your active link and filter actions may contain references to fields on this form. Those actions will be invalidated if you reattach them to a form that no longer contains those fields.
The following fields were not pasted, because they are already in this view. 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. You are removing these data fields from their only view: <field_names>. 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? This warning is to confirm that you want to remove data fields from their only view. If you continue and put the fields back into a view, they will have a default location and appearance.
2505 Warning
No integer or selection fields exist to cross-reference against. You specified Cross-Reference as the notification mechanism for a Filter Notify action, but there are no integer or selection fields that you can select to cross-reference against on this form. Try another notification mechanism. 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. A new window could not be opened because there are too many windows open or too many applications running. Close some windows or applications to continue.
2506 Error
2507 Error
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? This confirmation warns that you are deleting a value from a selection field that is the same as the default value. If you continue, the default value will also be deleted. You may want to specify a new default value.
2508 Error
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? The Status core field is special because a default value is required. If you delete the current default, it will be replaced by the first value in the list. If you continue, you may want to specify a new default value.
2509 Warning
Confirm that you want to save the form; the following fields will be deleted: <field_names>. You have deleted fields while editing the form, and those changes are about to take effect. This is a final confirmation and a chance to not save the form changes. If you save the changes, the fields will be deleted. Otherwise, you can close the form without saving any changes. You cannot add or modify the Default Login name. Changes are lost. 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. Login aborted. You cannot close all windows. While you tried to log back in, Remedy Administrator failed to close all the existing open windows, possibly because of a user request for an unsaved window. Character menus cannot exceed 14 levels. You can create a character menu only up to 14 levels deep. Failed to read field for form. Remedy Administrator failed to read a field for the form you selected for an active link or filter. Make sure that Remedy Administrator can still connect to the server that the form is on, then try again.
147
2516 Error 2517 Error 2518 Error 2519 Error 2520 Error 2521 Error 2522 Error 2523 Error 2524 Error 2525 Error 2526 Error 2527 Warning
The minimum and maximum values are the same. You have illegally specified a range of exactly one value. Save the form before renaming it. You must save the form before you can rename it. The minimum value is out of range. The range is 2147483647 to 2147483647. Integer fields require a number in the valid range. The maximum value is out of range. The range is 2147483647 to 2147483647. Integer fields require a number in the valid range. The default value is out of range. The range is 2147483647 to 2147483647. Integer fields require a number in the valid range. The minimum value is out of range. The range is <number> to <number>. Real number fields require a number in the valid range. The maximum value is out of range. The range is <number> to <number>. Real number fields require a number in the valid range. The default value is out of range. The range is <number> to <number>. Real number fields require a number in the valid range. The precision is out of bounds. Valid range is 0 to 30. Real numbers must have a precision (number of places to the right of the decimal point) within the specified range. This change will move the field out of bounds. You must give the field coordinates (X, Y location) such that the field will fit within the maximum dimensions of a view (1500 x 3000). This change will cause the field to be out of bounds. You must give the field coordinates (X, Y location) such that the field will fit within the maximum dimensions of a view (1500 x 3000). The following restored fields are no longer in this view: You have restored the selected fields from the database. Some of these fields may have been added to the current view since you last loaded the form; if so, they will no longer appear in the current view. Use the Fields in View dialog box to see which views the fields are in. Multiple views may be affected by this operation. Do you want to continue? The current operation can affect the display properties of one or more other views that are not currently loaded. 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.
2528 Warning
2531 Warning
Active link <active_link_name> is already used by <control_field_name>. Are you sure you want to move it to <control_field_name>? 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: <view_name>. 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 <form_name> to <form_name>. The operation most likely succeeded but the server is still busy. This warning occurs when using the Save Form As command 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 has 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. Remedy Administrator has 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 Warning
Copy and Paste of join fields is not supported; the selected join fields will not be copied. 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. There are no toolbar items on any of the menu items. No menu items in the current view have an associated toolbar item. Therefore, Remedy Administrator cannot display the Toolbar Layout dialog box. At least one trim, button, or menu item field will be deleted because you are deleting its only view. 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 <active_link_name> is already used by <button_name>. It can not be added to <button_name>. This version of AR System does not support moving an active link from one button to a different button. To continue, create a new active link.
149
2539 Warning
You have specified an ID within the reserved range. Do you want to save this field anyway? While creating a new field in a form, you specified a field ID that is less than 536870911. 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.
2540 Warning
None of the requested field deletions occurred on the server. Please close and reopen the form after the save operation has completed. 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. An inconsistent set of distributed fields is present in your form, perhaps because one or more fields was deleted. Distributed fields are system-generated and cannot be mixed-andmatched. Use the Distributed Fields dialog box to recreate a standard set of distributed fields in your form.
2542 Warning 2543 Warning 2544 Warning 2545 Warning
Distributed Fields will be deleted. Are you sure you want to have <number_of_fields> Distributed Fields instead of <number_of_fields>? This is a confirmation message when you want to delete DSO mapping fields. 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 there is an incorrect data type associated with distributed fields. Distributed Fields will be deleted. Are you sure you want to have <number_of_fields> Distributed Fields? This is a confirmation message when you want to delete DSO mapping fields. 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 sure of 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. This error occurs when you open a set field active link action, and some of the fields that are used in the setfield/value list box have been deleted from the form. To correct this problem, click Modify Action.
2548 Warning
Please enter a form prefix. When you selected the Form prefix option in the By Form dialog box, you did not enter a prefix before clicking OK.
Please add at least one form to the selected form list. You have selected the Selected Form option in the By Form dialog box but did not select any forms before clicking OK. Select a form, then click OK. A maximum of <number_of_forms> forms can be selected. Please remove some forms from the selected form list. You can select a maximum of 10 forms through the Selected Form option of the By Form Dialog Box. This message indicates that you have selected more than 10 forms.
2551 Warning 2552 Error 2553 Error 2554 Warning 2555 Error 2556 Warning
Warning: All the subsequent calls will be deleted. When you attempt to delete an OLE method, Remedy Administrator warns you that all of the subsequent methods (if nesting has been done) will be deleted. The minimum value has a bad value. You have entered an invalid value for the minimum value in the Field Properties Attributes page for a Decimal Field. The maximum value has a bad value. You have entered an invalid value for the maximum value in the Field Properties Attributes page for a Decimal Field. No image conversion will take place. Save anyway? If you attempt to change the extension of an image formats extension (for example, trying to save a JPEG file as something.gif), this warning appears. The precision is out of bounds. Valid range is 0 to 28. You have entered a value for a Decimal Field in the Attributes page of the Field Properties Dialog Box. The valid range is between 0 and 28. A duplicate server was detected in the server list for user <name_of_user>. Server Name in list: <name_of_server> Short Name of detected server: <short_name_of_server> Long Name of detected server: <long_name_of_server> This warning appears when you add the same server name, for both the short and long names, in the list of servers.
Warning: Form <name_of_form> not available in server <name_of_server>. 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. In order to improve this view so that it looks the same on all clients, Remedy Administrator will upgrade the layout information for this view when you save this form. This message appears when you attempt to import a pre-4.0 form with a 4.x (or later) version of Remedy Administrator. This changes all of the 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 form's views are changed.
151
The field type selected is not valid for global fields. You chose an invalid field type to become a global field. To continue, see the Developing AR System Applications: Basic guide for available field types. A maximum of <number> forms can be selected. 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. A global field has just been set to a regular field. The entry mode selection will be set to default. Global fields by design have no default values. By turning the field back into a regular field, you now can specify an entry mode.
2561 Warning
2562 Warning
Field ID 706 and 1020 are reserved for Alert and Results List respectively. Please choose another Field ID for field<type_of_field>. These field IDs are reserved for Alert Lists and Result lists. Choose another field ID 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 field<type_of_field>. This range of field IDs is reserved for columns in an Alert List. Choose another field ID not from this reserved range.
2564 Warning 2565 Warning 2566 Warning 2567 Warning
Some fields that are mapped will not be relevant for this form. This warning is returned because you changed the Form Name in the Open Window action and these field mappings may be invalid in the On Open or On Close modes. No field mappings have been defined for Open and Close dialog states. This warning is returned because you did not define any field mappings for Dialog window type. No field mappings have been defined. This warning is returned because, in Search or Submit mode, you did not define any field mappings. Exporting extension objects in XML is not supported. Selected extension objects will not be exported. This warning is returned because you cannot export extension objects (non-AR System objects) in XML format.
2569 Warning
Entry point guide does not have a starting active link. The guide will not be executed. An entry point guide has been created without specifying a starting active link. The entry point guide will not 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 Warning
Deleting this object, <object_name>, will delete all objects in the same lock group. Are you sure you want to continue? This warning is returned because 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 within the locked group are deleted.
2571 Warning
The form, <form_name>, 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? This warning is returned because locked workflow is attached to the form being deleted. To successfully delete this form, the attached workflow must also be deleted.
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, then click Modify Action. Unable to realloc memory. The system encountered an error during a call to allocate memory space when creating indexes. This error usually occurs when there are too many processes running or some processes have grown to occupy most or all of the available memory space on your client machine. You can recover that memory space by shutting down unneeded processes. Restart processes that have been running for a while to recover space those applications may have leaked over time. Unable to malloc memory. The system encountered an error during a call to allocate memory space when adding indexes. This error usually occurs when there are too many processes running or some processes have grown to occupy most or all of the available memory space on your client machine. You can recover that memory space by shutting down unneeded processes. Restart processes that have been running for a while to recover space those applications may have leaked over time. The maximum number of fields that can be specified in one index is <number_of_fields>. You exceeded the number of fields that can be added to a single index, which is 16. You may be attempting to index too many fields in your form anyway. Good candidates for indexing include fields that you search on frequently. If necessary, create multiple indexes for this form. You have reached the maximum limit of the fields in an index. You exceeded the number of fields that can be added to a single index, which is 16. You may be attempting to index too many fields in your form anyway. Good candidates for indexing include fields that you search on frequently. If necessary, create multiple indexes for this form.
2707 Error
2709 Error
2710 Error
153
One or more indexes does not have any fields specified. You created an index without any fields. To continue, add fields that you search on frequently to your index. Unable to realloc memory. The system encountered an error during a call to allocate memory space when creating query lists on your form. This error usually occurs when there are too many processes running or some processes have grown to occupy most or all of the available memory space on your client machine. You can recover that memory space by shutting down unneeded processes. Restart processes that have been running for a while to recover space those applications may have leaked over time. Unable to malloc memory. The system encountered an error during a call to allocate memory space when updating query lists on your form, for example, removing items from the list. This error usually occurs when there are too many processes running or some processes have grown to occupy most or all of the available memory space on your client machine. You can recover that memory space by shutting down unneeded processes. Restart processes that have been running for a while to recover space those applications may have leaked over time. Please supply a menu name. When creating or saving a menu, you did not enter a menu name. Enter a menu name to continue. Please select a menu type. When creating or saving a menu, you did not specify a menu type. Specify a menu type to continue. Please select a refresh code. When creating or saving a menu, you did not specify a refresh code. Specify a refresh code to continue. Please supply a server name. When creating or saving a Search menu type, you did not enter a server name. Enter a server name to continue. Please supply a form name. When creating or saving a Search menu type, you did not enter a form name. Enter a form name to continue. Please supply a label field. When creating or saving a Search menu type, you did not select a label field. Select a label field to continue.
2714 Error
Please supply a value field. When creating or saving a Search menu type, you did not select a value field. Select a value field to continue. Please select a file location. When creating or saving a File menu type, you did not enter a file location. Enter a file location to continue. Please supply a file name. When creating or saving a File menu type, you did not enter a file name. Enter a file name to continue. Menu definition is empty. When creating or saving a Character menu type, you did not add any menu items. Add menu items to continue. You cannot delete the following core field(s): When creating or modifying a form, you illegally attempted 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. Must be greater than 9999 and less than 2147483647. 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. Correct the message number, and click Modify Action. Missing message text. When creating a Message active link action, you did not enter any message text. Enter the missing message text, and click Modify Action. Missing field name. When creating a Change Field active link action, you did not select a field name. Select a field name, and click Add Action. DDE 'Service Name' is missing. When creating a DDE active link action, you did not enter a DDE service name. Enter a service name, and click Add Action. DDE 'Topic' is missing. When creating a DDE active link action, you did not enter a DDE topic. Enter a DDE topic, and click Add Action. DDE 'Item' is missing. 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.
2727 Error
155
DDE 'Path' is missing. When creating a DDE active link action, you did not enter a DDE path. Enter a DDE path, and click Add Action. DDE 'Command' is missing. When creating a DDE active link action, you did not enter a DDE command. Enter a DDE command, and click Add Action. The minimum value is greater than the maximum value. 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. The Default value is out of range with the minimum and/or maximum value. The default value: When creating a decimal field, you specified an illegal default value. To continue, create a default value within the minimum and maximum ranges.
The search database has been synchronized successfully. You successfully updated the search database. You now can search for any new objects added to your search database. Synchronization of the Search Database Failed. Try again. There was a failure in updating the search database. You will not be able to perform searches for new objects added to your search database. To continue, try performing the synchronization later. Server object <name_of_object> cannot be opened from here. Please open it from the Server Window. You cannot open server objects from the Related Workflow tab on the Field Properties window. Click OK, then open the server object from the Server Window.
2739 Error
Macro name is missing. 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. The named menu is not defined at this time, do you wish to continue? 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. Unable to Save/Update Form. You attempted changes to a form that were not accepted by AR System. The Default value is out of range with the minimum and/or maximum value. The minimum value <minimum_value> and the maximum value <maximum_value>. When creating an integer field, you specified an illegal default value. To continue, create a default value within the minimum and maximum ranges.
2744 Error
The Default value is out of range with the minimum and/or maximum value. The minimum value <minimum_value> and the maximum value <maximum_value>. When creating a real field, you specified an illegal default value. To continue, create a default value within the minimum and maximum ranges.
Do you wish to close the field property dialog before correcting the errors? You have specified field property settings that are incorrect. If you close the Field Property dialog box, your settings will not be saved. The field length must be between 0 and 4294967295. 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. Invalid View Name. You must select a defined name. 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. Alert text is missing. When creating a Notify filter action, you did not enter notify text. Enter notify text, and click Add Action. User text is missing. When creating a Notify filter action, you did not enter a user name. Enter a user name, and click Add Action. Reference Field is missing. When creating a Notify filter action, you did not select the reference field that is required when the notification Mechanism is Cross-Reference. Select a reference field, and click Add Action. Sorry, unable to locate your default browser. Feel free to visit our website for the latest information on Remedy products and services at http://www.remedy.com. This error message appears when you choose items from Help > Remedy on the Web > Remedy Home Page in Remedy Administrator. You must install a web browser to access this information.
2751 Error
2753 Error
Unable to log on to any server as administrator or sub-administrator. There was a failure during log in, for the following 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 Error
Please enter Qualification query for this action. When creating a Push Fields action, you did not enter a Push Field If qualification. Enter a qualification, and click Add Action.
157
Qualification line error at position <number>. When creating a Search type menu, you did not enter a valid qualification. Check your qualification, and click Add Action. Error Getting Font Data. 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
Error getting form list on server <server_name>. 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, run Remedy Administrator analyzer again. Error getting active links list on form <form_name>. 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, run Remedy Administrator analyzer again. Error getting filter list. Remedy Administrator analyzer could not find a list of filters 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, run Remedy Administrator analyzer again. Error getting escalation list. Remedy Administrator analyzer could not find a list of escalations 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, run Remedy Administrator analyzer again. Server <server_name> not found in list of servers. 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. Form <form_name> not found in list of forms. 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.
2760 Error
2761 Error
2762 Error
2768 Error
Warning: Some fields that are mapped will not be relevant for this form. When creating an Open Window action, you attempted to enter a set of field/value mappings that are invalid for the form you just selected. Enter a new set of mappings, or select the form that was used for these mappings. Error: No server has been selected. When creating or modifying an Open Window action, you did not specify a server. Enter or select a server name to continue. Error: No form has been selected. When creating or modifying an Open Window action, you did not specify a form. Enter or select a form name to continue. Warning: No field mappings have been defined for Open and Close dialog states. When creating or modifying an Open Window action, you did not specify a set of field/value mappings. Remedy Administrator will let you save the action, but the action will not function properly. Create a set of field/value mappings to continue. Assign line error at position <number>. 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. You will lose your existing <name_of_guide> assignments by changing the form. Do you want to continue? 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 may create unanticipated results in your guide. To continue, verify which form(s) you want to control the active links in your guide.
2777 Error
Error in export! Export aborted. There was an error while attempting to export mail templates. To continue, make sure that all fields that require 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 attempting the export operation. Error: No guide selected for CallGuide action. When creating or modifying a Call Guide action, you did not select a guide. Select a guide to continue. Error: Addition of guide <guide_name> addition to tree failed. A problem was encountered adding 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
Error: No Active Link specified for guide to go to. When creating or modifying a Go To Guide Label action, you did not enter a guide label. Enter a guide label to continue.
159
The Default value has a bad value. When creating a decimal field, you specified an illegal default value. To continue, create a default value within the minimum and maximum ranges. Error getting field list on form <form_name>. 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, run Remedy Administrator analyzer again. Failed to analyze field <field_name> in form <form_name>. Remedy Administrator analyzer could not find this field 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, run Remedy Administrator analyzer again. Failed to analyze escalation <escalation_name> in form <form_name>. 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, run Remedy Administrator analyzer again. Failed to analyze filter <filter_name> in form <form_name>. Remedy Administrator analyzer could not find a list of filters 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, run Remedy Administrator analyzer again. Error opening file <file_name>. When attempting to save a report of results from 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. Could not detect image type of <type_of_image>. There was an error because the image you attempted to save to a file is not from the following types:
2784 Error
2785 Error
2786 Error
2787 Error
2788 Error
.jpg .jpeg .bmp .dib

You can only use the formats listed above, and you can only save to a file of the same image type.
2789 Error
Errors were found. Please check the tab order to make sure that all shared fields are in the same order relative to each other. This error occurs only with multiple native views of a form in which you are creating the tab order. When you are attempting to 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.
Unable to open file. There was an error when testing the help file or saving it to disk. To continue, verify that you have the necessary permissions to access the file. Error getting application list. Remedy Administrator analyzer could not find a list of applications 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, run Remedy Administrator analyzer again. User <name_of_user> does not have admin or subadmin privileges on server <name_of_server>. Dropping connection. There was a failure during login because AR System did not recognize this user name as a valid administrator or subadministrator. To continue, enter a different login name.
2794 Error
2795 Warning
Some Fields could not be saved in this form. The server failed to save some of the fields you attempted to add to or modify on this form. Nevertheless, the form was still created on AR System server, along with other fields that were modified. This problem may be connected to the inability of your underlying RDBMS to create these fields. Failed to load <server_object> for form <form_name> from server <server_name>. During the login process, the server failed to load the different AR System objects connected to this form when you were viewing objects by workspace or by form. Verify in Remedy Administrator if you can view all forms and all objects. Failed to get related items. Export file will not be generated. When exporting an object, its related items were not loaded. The export operation will fail. Verify in Remedy Administrator if objects are related, for example, whether an active link is connected to a form, and so on. Unable to refresh field detail for field <field_name> in form <form_name> on server <server_name>. Any further operation on this form can cause unpredictable behavior. Remedy Administrator has issued an API call to refresh the fields on this form, but the call has failed due to instability in the client tool. To handle this problem, close both the form and the Remedy Administrator client. Then restart Remedy Administrator and open the form. If this does not work, you may need to reboot your system.
2796 Warning
2797 Error
2805 Error
161
2807 Error
Error: The Active Link <active_link_name> could not find the View <view_name> in Form <form_name>. The View will return to default. When creating an Open Window action, the Form View you selected could not be found on AR System server. Accordingly, the view used in the action will be the default administrator view. Open the form in Remedy Administrator and choose Form > Select a View to verify that the view you want to use exists.
2808 Error
Please select a Source Control Provider. 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, then click OK.
2809 Error
Please select a Source Control Project. 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, then click OK.
2810 Error
Object already exists in Source Control. You attempted 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 will overwrite the old object with a new one. Error getting definition file for object. You attempted to import the object definitions from source control but the operation failed. Object does not exist in Source Control. You attempted to perform an operation to an object that has not first been added to the source control system. Add the object to the source control project. Are you sure you want to remove the selected objects from Source Control, as you will lose history data along with them? 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.
Object is checked out by <user_name>. You attempted to check out an object that has already been checked out by another user. Contact the other user if possible to resolve any administrative issues. Error writing Registry values. You attempted to retrieve user information from source control but the properties could not be displayed in the User Info dialog box.
2816 Error
You are in Enforced mode of the Source Control Integration. You cannot modify this object because it does not exist in Source Control. In Enforced mode, you attempted to modify an object that does not exist in the source control database. First check the object in to source control.
2817 Error
You are in Enforced mode of the Source Control Integration. You cannot modify this object 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.
2818 Error
You are in Enforced mode of the Source Control Integration. You cannot modify this object because you did not check it out first. 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 have attempted to modify an object that is under source control in Enforced mode on AR System server. However, you do not have a source control client installed or you have not configured it properly with your Remedy Administrator client. Make sure that you have properly installed the source control client software, then configure it with Remedy Administrator in the Source Control tab in the Server Information window. You then will be allowed to modify objects under source control. For a detailed discussion on source control issues, see the Developing AR System Applications: Advanced 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 have attempted to perform a source control action, but your 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 have attempted to modify an object that is 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.
163
2822 Error
You are in Advisory mode of the Source Control Integration. Modifying an object could overwrite or conflict with someone elses work because it is already checked out to another user. You have attempted to modify an object that is 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
You are in Advisory mode of the Source Control Integration. Modifying an object could overwrite or conflict with someone elses work because you did not check it out first. You have attempted to perform an operation on an object that is 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.
Please enter a definition file name. 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. Please relogin to this server for the changes made to Source Control Integration to take effect. After you make any changes in your source control provider, project, and other configuration settings in the Server Information window, you must once again log in to Remedy Administrator. Then you can start using source control integration with the AR System server. Source Control operations can not be performed on Groups. You attempted 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. Source Control operations can not be performed on Distributed Mappings. You attempted 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. Error opening Source Control project. You attempted 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. You are in Enforced mode of the Source Control Integration. You cannot import this object because it is already checked out to another user. You attempted to perform an import operation of an object that is currently checked out to another user. Contact the other user if possible to resolve any administrative issues.
2826 Error
2827 Error
2830 Error
Error updating Source Control database. 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, then try the update operation again to continue. Error getting file from Source Control database. There was a failure to retrieve a definition file from source control. Verify that you have access to the file, for example, by opening it in the source control client, to continue. The object you are importing has been checked out to someone else. Import to server anyway? 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
Error importing some objects. During an import operation from source control, there was a failure importing some of the objects because the server name alias could not be resolved and show the server name. The operation is only partially successful. You will 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 Server Information window Server-Name: 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 attempting to access them in the source control client, to continue. If you are successful, log back in to Remedy Administrator, and try the import operation again. If you are using a server name alias, verify that it is valid.
Object is not checked out. You attempted 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. Do you wish to continue? During a bulk update to the source control database, an error was encountered in which you cannot modify the selected objects. Make sure that you have properly installed the source control client software, then configure it with Remedy Administrator in the Source Control tab in the Server Information window. You then will be allowed to modify objects under source control. For a detailed discussion on source control issues, see the Developing AR System Applications: Advanced guide.
165
2836 Error
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. You have attempted 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 have not configured it properly with your Remedy Administrator client. Make sure that you have properly installed the source control client software, then configure it with Remedy Administrator in the Source Control tab in the Server Information window. You then will be allowed to modify objects under source control. For a detailed discussion on source control issues, see the Developing AR System Applications: Advanced guide.
2839 Error
Min value should be less than Max value. When configuring the number of server threads in the Server Ports and Queue tab in the Server Information dialog box, you attempted 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. Min and Max value should be greater than 0. When configuring the number of server threads in the Server Ports and Queue tab in the Server Information dialog box, you attempted to set the number of Min and Max threads to zero. Do one of the following: 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.
2840 Error
The Form name has not changed. Please specify a new name. You attempted to save a form that is under source code control. To continue, change the name of the form. The specified file does not exist. Do you want to create it? You attempted to retrieve an object from the source control database that does not already exist on AR System server. Click Yes to create the object. The object will then be added to source control. You then will be able to manipulate the object as needed. Error creating the file. When retrieving the latest version of the file from source control, there was an error in creating the file on AR System server or in the location you specified. To continue, verify that the object exists in the source control database, and that both AR System server and the source control database are running. Also, if you are copying the file to a location, check your permissions.
2844 Error
2845 Error
The specified file already exists. Do you want to overwrite it? You attempted 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. Invalid refresh state returned. You attempted 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.
2846 Error
2847 Warning
Failed to load <server_objects> from server <name_of_server>. During the login process, there was a failure to load the server objects that the user is permitted to see. To continue, verify that the server is running. Also, verify the users access control settings. The number of rows exceeded the maximum allowed limit of 230. In the Display tab of the Field Properties window, you attempted to set the rows displayed in a form to a number larger than 230. Enter a number equal to or less than 230. Please enter a comment. Developer comments are required for this operation. 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 Error
No matches found in the database for the given query. When searching in the Search Objects window for an object, no results were returned. Objects may have been deleted or the names modified. Deleted objects will not appear even if the database is not synchronized. Please select a source code control provider. 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, then click OK. Duplicate distributed pool name. When attempting 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. Source Control operations cannot be performed on Distributed Pools. You attempted 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.
2851 Error
167
Missing target location text. When creating or modifying an Open Window action, you did not specify a target location. Enter or select a target location to continue. Error: No sample server has been selected. When using the Advanced functionality for an Open Window action, you did not specify a sample server name. Enter a sample server to continue. Error: No sample form has been selected. When using the Advanced functionality for an Open Window action, you did not specify a sample form name. Enter a sample form to continue. Error: No view has been selected. When creating or modifying an Open Window action, you did not specify a form view. Enter or select a form view to continue. Some items failed to import. During an import operation from source control, there was a failure importing some of the objects. The operation is only partially successful. To continue, verify that you have access to the objects in the source control database, for example, by attempting to access them in the source control client. If you are successful, log back in to Remedy Administrator, and try the import operation again. Warning: No field mappings have been defined. When creating or modifying an Open Window action, you did not specify a set of field/value mappings. Remedy Administrator will let you save the action, but the action will not function properly. Create a set of field/value mappings to continue. File already exists in the current directory. When creating an application object, you cannot add a support file to your application that already exists in the current directory. Cannot delete root element. When creating an application object, you cannot delete or change the name of the Resources Directory Structure level under the Support Files tab. Please select an item before creating the directory. 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 will be removed from the directory structure the next time you open the application object. Cannot add file. Directory depth exceeds the maximum allowed limit. When creating an application object, you cannot add more than 255 support files to the current directory.
2868 Error
2874 Error
2877 Warning
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 www.remedy.com. This version of the 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 AR System without these limitations, contact your Remedy sales representative, an authorized reseller, or visit www.remedy.com.
Alias values must be unique. When adding localized text in the Alias Value field, you need to specify a unique alias value. Modifying Packing List may result in loss of data. Your changes to this packing list in your role as a subadministrator may result in loss of data. To continue, contact your AR System administrator for assistance in modifying this packing list. Web view is created but not initialized! Please initialize the web view by opening and saving the web view. When you were saving the application to disk in Remedy Administrator, you did not first save the contents of the web view to the server.
2880 Error
2881 Error
Error in converting to Open Window action. AR System was unable to convert the existing macro functionality to its equivalent 5.x (or later) Open Window action. Your pre-5.x workflow will still function. However, as a workaround, you can manually create an Open Window action as a substitute for your Remedy User macro used in workflow. Error in converting to Run Process (Preferences) action. AR System was unable to 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 will still function. However, as a workaround, you can manually create an Run Process action as a substitute for your Remedy User macro used in workflow. Error in converting a macro command. AR System was unable to convert a keyword used in a macro command to its equivalent 5.x (or later) workflow action. Your pre-5.x workflow will still function. However, as a workaround, you can manually create a workflow action as a substitute for your Remedy User macro used in workflow. Error in converting to Run Process action. AR System was unable to convert the existing macro functionality to its equivalent 5.x (or later) Run Process action. Your pre-5.x workflow will still function. However, as a workaround, you can manually create a Run Process action as a substitute for your Remedy User macro used in workflow.
2882 Error
2883 Error
2884 Error
169
2885 Error
Error in converting modify to Push Fields action. AR System was unable to convert the existing macro functionality to its equivalent 5.x (or later) Push Fields action. Your pre-5.x workflow will still function. However, as a workaround, you can manually create a Push Fields action as a substitute for your Remedy User macro used in workflow. 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. AR System was unable to 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. If you want to use the 5.x (or later) macro conversion tool, divide the old active link functionality into multiple active links, then attempt the macro conversion again. Otherwise, you could create new active links that use the 5.x (or later) workflow functionality.
2886 Error
2887 Error
New Action cannot be inserted. AR System was unable to convert an existing macro to a new active link action. Your pre-5.x workflow will still function. As a workaround, create a new active link that uses the 5.x (or later) workflow functionality. Succeeded. AR System was successful in converting the existing macro functionality to a new set of active link actions. Server is referred by a keyword or field ID. Server name should be currently available to process QBE type of queries. AR System was unable to 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 will still function. As a workaround, create a new active link that uses the 5.x (or later) workflow functionality.
2890 Error
Could not connect to QBE referred server. Server name should be currently available to process QBE type of queries. AR System was unable to 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 may also affect your pre-5.x workflow. As a workaround, create a new 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 was unable to 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 may also affect your pre-5.x workflow. As a workaround, create a new active link that uses the 5.x (or later) workflow functionality.
2892 Error
Failed to convert QBE into equivalent qualifier structure. AR System was unable to convert the macro to an equivalent qualification used by the 5.x (or later) workflow actions. As a workaround, create a new active link that uses the 5.x (or later) workflow functionality. At least one macro command is not supported. AR System was unable to 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 a new active link that uses the 5.x (or later) workflow functionality. Conversion Complete. AR System was 100% successful in converting the existing macro functionality into a new set of active link actions. Alias should start with an English alphabet. Your web alias started with a characters that was not alphanumeric. Begin your alias with alphanumeric characters only. Alias must contain alphanumeric characters only. Your web alias contained characters that are not alphanumeric. Use only alphanumeric characters in your alias. There is already another view with the same alias, platform, and locale combination. In the View Properties window, you attempted 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.
2894 Error
2899 Error
You must first specify a server. In the Password Administration tab of the Server Information window, you attempted to enter a port, password, or RPC program number before you entered a server. To continue, enter a server name first. No key field specified. Please specify a key field for this form. When creating a View form, you did not specify a unique table column to be used as the key field. This key field will function 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. No table name specified. Please specify a table name for this form. When creating a Vendor or View form, you did not select a database table name. This database table provides the external data that will be used in the creation of an AR System form. To continue, select and load a table name. No vendor name specified. Please specify a vendor name for this form. 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.
2901 Error
2902 Error
2903 Error
171
Please enter field type. 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. Please select object type. When creating or saving a Data Dictionary menu type, you did not select an object type. Specify an object type to continue. Please specify web alias. You attempted 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. Some web views do not have WebAlias property. This may result in invalid .jsp file names after deployment. You attempted 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 the save operation, enter a web alias.
2910 Warning
2911 Warning
Form and some web views do not have WebAlias property. This may result in invalid .jsp file names after deployment. You attempted 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 the save operation, 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 may also see this error message when performing a command-line bulk conversion of the form layouts.
The selected <extension>s will be deleted. You are about to delete one or more custom server objects (for example, a Flashboards server object). Click Yes to continue the delete operation. You cannot create the following core fields in view or vendor forms. This error is displayed because you attempted 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 that is not allowed in the view or vendor forms. Directory <directory_name> creation failed. There was a failure to create a directory when making a link, for example, to the folder where an external image is stored. Verify that you have access to the file (for example, in the Explore window) to continue.
2916 Error
2917 Error
The file <file_name> does not exist. There was a failure to access a file when making a link, for example, to where an external image is stored. Verify that you have access to the file (for example, in the Explore window) to continue. Internet Explorer 5.5 or later cannot be found. Portions of the Remedy Administrator will not be available until it is installed. You do not have access to important functionality in 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.
2918 Error
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).
Form must have web alias to generate valid .jsp file name for its web views. You attempted to create a web view of a form without supplying a web alias. To continue, create a web alias. Administrator operations are disabled for this server. Cannot create new objects. In the Configuration tab on the Server Information window, the AR System administrator configured this server to disable admin operations. No new objects can be created. To continue, reset the configuration settings. Active link could not be converted successfully. Original Active Link is restored. When using the Macro Conversion utility, there was a failure converting the macro into its equivalent active link functionality. The conversion, however, will attempt 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 try the conversion process again. For a workaround, see error message 2927. Error in saving active link. When using the Macro Conversion utility, there was an error in saving the active link. The conversion however will attempt to convert the other macros. To continue, repair the macro appropriately, for example, remove the un-supported commands (login-related macro commands) or repair the incorrect syntax in the commands, and try the conversion process again. For a workaround, see Error 2927. CCSSchema could not be loaded. When using the Macro Conversion utility, there was an internal schema error converting the macro into its equivalent active link functionality. For a workaround, see Error 2927.
2922 Error
2923 Error
2924 Error
173
2925 Error
Field specified in assignment structure is missing in the schema. When using the Macro Conversion utility, an internal error occurred when transforming a string to its equivalent assignment structure (ARAssignStruct). For a workaround, see Error 2927. Value assigned to field cannot be converted to equivalent AR structure. When using the Macro Conversion utility, an internal error occurred when converting a value to its equivalent assignment structure (ARAssignStruct). For a workaround, see Error 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 attempt again. The following are frequently encountered errors when converting macros to active links: An error indicating that the qualifier could not be loaded may indicate that fields referred to are not present. It may also be that the labels of the fields are referred to in the macro query but the conversion process is expecting the database names of the fields. Verify that the conversion of the query string to a qualifier is correct. An error indicating that the QBE cannot be loaded may be due to the schema not being available. 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 may be replaced with specific values for conversion. After successful conversion, the administrator can refer to $field-id$ by directly editing the Open Window action. When editing the Open Window action, the administrator must choose the Advanced option, allowing for the schema and server names to be edited. Another error that occurs when converting macros is that the query is converted but some field/value pairs that were present in QBE part of query are not there. Workaround: Verify that the fields are display fields. Since your query is on field value in database and display fields, you do not have any associated value in the database. Display fields should not be present in a QBE, and are ignored during conversion.
2926 Error
2927 Error
Error in converting AR System Reports keyword. When using the Macro Conversion utility, an internal error occurred when converting the AR System report command in the macro. Error in finding reports end. When using the Macro Conversion utility, an internal error occurred when converting the end of the AR System report in the macro.
Error in creating or opening of temporary AR System Report file. When using the Macro Conversion utility, an internal error occurred when creating or opening the temporary AR System Report file in the macro. Field with ID <ID_number> is not present in this form. Looks like a corrupt field. Would you like to delete this field? When deploying an application, an error was returned in generating HTML files due to nonexistent fields in the web view of the form. This corruption may be due to the user hard coding a new field in the form. To continue, delete the field.
2932 Error
Source Control operations cannot be performed on Extension Objects. You attempted 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. Cannot find server <server_name>..... Possible server alias name problem. 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.
2933 Error
2934 Error
Could not open file: <name_of_file>. 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. Error from Source Control ProviderInitialize failed. This error message is returned by your source control application. The source control engine failed. To continue, verify that you can start the source control executable independently of Remedy Administrator. Error from Source Control ProviderUnknown project. This error message is returned by your source control application. The source control project could not be located. 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. Error from Source Control ProviderCould not create project. This error message is returned by your source control application. 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. Error from Source Control ProviderNot checked out. This error message is returned by your source control application. You cannot modify an object under source control unless you check it out first. To continue, check out the object.
2936 Error
2937 Error
2938 Error
2939 Error
175
2940 Error
Error from Source Control ProviderAlready checked out. This error message is returned by your source control application. You attempted to perform a source control operation on an object that is currently checked out to another user. To continue, wait until the object is checked in. Error from Source Control ProviderFile is locked. You attempted to perform a source control operation on a file that is currently locked. To continue, confirm whether some other user is accessing the file. Error from Source Control ProviderFile out exclusive. This error message is returned by your source control application. You attempted to perform a source control operation on a file that is exclusively locked by another user. To continue, confirm whether some other user is accessing the file. Error from Source Control ProviderAccess failure. This error message is returned by your source control application. You failed to access a file that is currently in use by another user. Error from Source Control ProviderCheck in conflict. This error message is returned by your source control application. 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. Error from Source Control ProviderFile already exists. This error message is returned by your source control application. You cannot add this file to source control because the file already exists. To continue, delete the file from the source control database first. Remember that when removing the object from the source control database, you will also lose history data. Error from Source Control ProviderFile not controlled. This error message is returned by your source control application. You failed to access a file because it is not under source control. To continue, add the file to the source control database. Error from Source Control ProviderFile is checked out. This error message is returned by your source control application. You failed to check out this file because it is currently checked out to another user. Contact the other user if possible to resolve any administrative issues. Error from Source Control ProviderNo specified version. This error message is returned by your source control application. 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.
2945 Error
2946 Error
2947 Error
2948 Error
Error from Source Control ProviderRequested operation not supported. This error message is returned by your source control application. You failed to access this file because this operation is not supported by your source control application. Error from Source Control ProviderNon-specific error. This error message is returned by your source control application. An unspecified error was returned in your source control provider that was not covered under any specific error conditions. Error from Source Control ProviderRequested operation not performed. This error message is returned by your source control application. You failed to access this file because this operation was not performed by your source control application. Error from Source Control ProviderType not supported. This error message is returned by your source control application. This file type is not supported under source control. Error from Source Control ProviderVerify merge. This error message is returned by your source control application. The file merge operation failed under source control. Error from Source Control ProviderFix merge. This error message is returned by your source control application. The file merge operation failed under source control. Use your source control application to repair the file merge. Error from Source Control ProviderShell Failure. This error message is returned by your source control application. An unspecified shell failure was displayed by the source control application. Error from Source Control ProviderInvalid user. This error message is returned by your source control application. You are not a recognized user in the source control database. Verify that an account has been created for you and that you have permission to access the source control database. Error from Source Control ProviderProject already open. This error message is returned by your source control application. You attempted to open a source control operation on an object that has already been opened by you or another user. Error from Source Control ProviderProject syntax error. This error message is returned by your source control application. There was an unspecified project syntax error displayed by the source control application. Error from Source Control ProviderInvalid file path. This error message is returned by your source control application. You could not access files in your source control project because of an invalid file path. To continue, verify the correct file path.
177
Error from Source Control ProviderProject not open. This error message is returned by your source control application. You attempted to access a file from a source control project that was not open. To continue, open the project first. Error from Source Control ProviderNot authorized. This error message is returned by your source control application. You attempted an operation not authorized by your source control engine. Error from Source Control ProviderFile syntax error. This error message is returned by your source control application. There was an unspecified file syntax error displayed by the source control application. Error from Source Control ProviderFile does not exist. This error message is returned by your source control application. You attempted to access a file that does not exist under source control. Error from Source Control ProviderConnection failure. This error message is returned by your source control application. There was a failure to connect to the source control application. Rename operation failed on the Source Control Provider. This error message is returned by your source control application. The rename operation failed. Format of date value is not recognized. This error message is returned when the value of a time stamp has been incorrectly converted for a date type field. Cannot create or modify a Currency Field without at least one selected Functional Currency. Please select at least one Functional Currency. This error message is returned if you do not select a functional currency list. Incorrect precision. Please enter a single digit numeric precision. This error message is returned if you did not define a single digit of numeric precision (for example, numbers 1 to 9) for the Currency Codes preferences. Incorrect currency code. Please enter a valid 3 digit Currency Code. This error message is returned if you entered an invalid currency code in the Currency Codes preferences, or left the currency code field blank. Duplicate Operation Name. Please enter a unique name for operation. This error message is returned if you created a duplicate operation name in the Operations List. All operation names must be unique. Duplicate Operation Name. The name will not be modified. This error message is returned if you modified an operation name but the operation name is not unique. All operation names must be unique.
One or both of the objects have already been mapped. Unmap and continue. This error message is returned if you accidentally created a duplicate mapping. Form should be mapped before the fields. This error message is returned if you attempted to map the fields before you have already mapped the form. Mapping cannot be defined. This error message is returned if your mapping is invalid Objects are not mapped. This error message is returned if no objects are mapped. Objects selected do not have the same map. This error message is returned if the web services mapping is not unique. Name should start with an English alphabet. This error message is returned if the web services name does not use English alphanumeric characters. Name must contain alpha numeric characters only. This error message is returned if the web services name is empty. WebService Handler is using an insecure (http) protocol. If username and password are mapped, they will be sent in plain-text. This error message is returned because the web service you are consuming is not secure. Any critical information (for example, passwords) will not be properly encrypted.
Web service cannot be saved without any operations. This error message is returned because you cannot create a web service that has no operations. Enter at least one operation in the operations list. This mapping object is corrupted. Please delete the current operation and continue. This error message is returned because the mapping you created for the web service operation has become corrupt. Delete this operation and try creating a new one. The XML element selected has maxoccurs greater than 1. This mapping is not supported. This error message is returned because a field cannot be mapped more than once. This mapping is not supported. This error message is returned because, 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. Cannot create or modify a data field without specifying a corresponding DB column name. Please specify a valid DB column name. When creating a view form, data fields must be linked to an underlying database column.
2988 Error
179
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, a display-only field cannot be linked to an underlying database column.
2992 Error 2993 Warning 2994 Error 2995 Error 2996 Error 2997 Error 2998 Error 2999 Error
The Database Name for a Flashboard field must not be NULL. When creating or modifying a Flashboard field, the Name field in the Database tab (in the Field Properties window) cannot be empty. Enter a name for the field. 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. This error message is returned if you did not map any of the choice nodes in a XML schema. Primary key is mapped. The primary key should not be mapped. This error message is returned if the primary key of the parent form has been mapped. Primary key is not mapped. If field ID is not 1, then the primary key should be mapped. This error message is returned if any field other than the Request ID (1) is used as the primary key but not mapped to any element in the XML schema. Distinguishing key(s) is not mapped. Map and continue. This error message is returned if the distinguishing key in a child form is not mapped. Foreign Key(s) is mapped. Unmap and continue. This error message is returned if any of the fields that are selected as foreign keys in the child forms are mapped. Form mapping under a choice node or a complex element of type all is not supported. This error message is returned if any of the immediate children under the choice/all node are mapped to a different form. Invalid mapping because of incompatible data types. AR Datatype - Character can only be mapped to XML Datatype - string, integer, nonPositiveInteger, negativeInteger, nonNegativeInteger, or positiveInteger. This error message is returned because you attempted to map data types that are incompatible.
3000 Note
AR System Distributed Server Option (DSO) process terminated when a signal was received by the server. 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, start the server again, 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 Remedy 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 Note 3002 Note
AR System Distributed Server Option (DSO) process terminatedfatal error encountered. A fatal error occurred within arservdsd and the process has been shut down. Details of the fatal error are contained in an associated message. Request pending transfer or update has been pending for longer than the specified retry time-out. A request pending transfer or update has been 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 Note
Pending distributed operation for this request canceled due to error. An error occurred while trying to transfer or update a request. If there is a Transfer or Update Status field on the request, the field is updated to the status Canceled. The details of the error are contained in an associated error message. AR System Server is not currently available -- will retry connection. The AR System Distributed Server Option is unable to connect to the AR System Server. The connection attempt will be retried periodically for several minutes. If repeated connection attempts fail, an associated error message will be output and no further attempts will be made. AR System Server is now available. 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.
3004 Note
3005 Note
3100 Error
The AR System is not licensed for the Distributed Server Option (DSO) process. 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. Error while opening the Distributed Server Option (DSO) process lock file. 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 about the problem with the file. Correct the problem indicated by the latter message, and run the server again.
3101 Error
181
3102 Error
Another copy of the Distributed Server Option (DSO) process is already running. A machine 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 have probably encountered a known problem with the NFS lock manager on Sun 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, then start arservdsd again.
3103 Error
Malloc failed on Distributed Server Option (DSO) process. The system encountered an error during a call to allocate space. The failure occurred on the server machine in the DSO process. In general, this error occurs when there are too many processes running, or when certain processes occupy most or all of the available memory on your server machine. To recover the memory, shut down all unneeded processes. Additionally, you can restart processes that have been running for a long time to recover space those processes may have leaked while running. The server being accessed is not licensed for the Distributed Server Option (DSO) process. The arservtcd process may be on a target server is not licensed to use the DSO process, or on a version 2.0 (or earlier) target server that does not interact with arservdsd. No Distributed Mapping form could be found on the server. A Distributed Mapping form is required for the system to support distributed operations. No form could be found that contains all the special reserved fields indicating it is a Distributed Mapping form. Load the Distributed Mapping form, and define the appropriate mappings. Two forms contain all the reserved distributed mapping fields -- delete one to continue. The system found two forms containing the reserved distributed mapping fields. You must delete one form, or change it so that it is not considered a Distributed Mapping form (remove fields in the 200 to 220 range). The two forms are identified in an associated error message. No Distributed Pending form could be found on the server. 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. Two forms contain all the reserved distributed pending fields -- delete one to continue. The system found two forms containing the reserved distributed pending fields. You must delete one form or change it so that it is not considered a Distributed Pending form (remove fields in the 250 to 260 range). The two forms are identified in an associated error message.
3108 Error
3109 Error
3110 Error
3111 Error
The From form in the mapping definition is different from the source form in the attempted mapping. 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 Error
The From server in the mapping definition is different from the source server in the attempted mapping. The server defined as the From server does not match the server 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.
3113 Error
The To form in the mapping definition is different from the target form in the attempted mapping. The form defined as the To form does not match the form that is the target 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.
3114 Error
The To server in the mapping definition is different from the target server in the attempted mapping. The server defined as the To server does not match the server that is the target 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.
3115 Error
The type assigned to a pending request is not recognized. A pending request with the pending operation tag set to an unrecognized value was encountered. This error should only occur if you have 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 encounter this error, contact Remedy Customer Support. Only the master copy of a request can be transferred. You can only transfer the master instance of a request. The system attempted to transfer the specified request, but the Master Flag field on the request is set to No. Update was unsuccessfulthe From Form field or the From Server field has no value. 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 manually change the Master Flag value, you must make sure that there are also values assigned for the From Form and the From Server fields (you can also change these by using ardist).
183
3118 Error
Failed to perform a distributed command.
arserverd received a request to record a distributed command or encountered a situation in which it attempted to automatically record a distributed command, and a failure occurred during recording. Thus, the distributed command was not performed. The command being attempted is displayed with this message, and an associated message contains more information about the failure.
A specific mapping was specified on the request -- the specified mapping is currently disabled. A transfer was being attempted with a specific 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.
3119 Error
3120 Error
The distributed operation being attempted expected additional information which is not present. 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 only occur if you have 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 Remedy Customer Support.
3121 Error
Create New is specified as the action if duplicate Request IDs are encountered during transferthe target form does not have the required From Request ID field. You attempted to transfer a request to the target form with ownership transferred to the new request, thus creating a new request due to ID conflict. However, the target form 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 ID of the request so the original can be updated when the copy changes. If you must retain ownership on the original, pass the request as data only.
3122 Error
A distributed operation cannot be specified while deleting a request -- the delete and the distributed operation are both canceled. A filter invoked a distributed process (Distributed-Transfer, Distributed-Update, Distributed-Return) 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
You must map the Request ID field to the target Request ID field, or the From Request ID field must be present on the target form. You attempted a distributed transfer operation to another form by using a custom mapping with a transfer mode of Data + Ownership, and one of these conditions exists: You did not map the Request ID field of the source form to the Request ID field of the target form. You did not map the Request ID field on the source form to a From Request ID field on the target form. You must map the Request ID field on the source form to one of the above fields on the target form. Correct the mapping, and try the transfer again.
3124 Error
Transfer with ownership requires that the target form contain a Master Flag field. You attempted a distributed transfer operation using a mapping to another form with a transfer mode of Data + Ownership, and the target form does not contain a Master Flag field. It is required that the target form (identified in the error) contain a Master Flag field if ownership is being transferred. Transfer with ownership requires that the target form contain a From Form field. You attempted 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. It is required that the target form (identified in the error) contain a From Form field if ownership is being transferred. Transfer with ownership requires that the target form contain a From Server field. You attempted 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. It is required that the target form (identified in the error) contain a From Server field if ownership is being transferred. Transfer with ownership requires that source form contain Master Flag field. 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. It is required that the source form (identified in the error) contain a Master Flag field if ownership is being transferred. Two forms contain all the reserved distributed pool fields -- delete one to continue. The system found two forms containing the reserved distributed pool fields. You must delete one form. The two forms are identified in an associated error message. Illegal value specified for -m optionlegal values are 0 (not master) and 1 (master). 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. Issue the command again, and specify a legal value for this argument.
3125 Error
3126 Error
3127 Error
185
Must specify the -e {Request ID} option. You must specify the -e argument to denote the ID of the request (entry) to be modified. Must specify the -s {form} option. You must specify the -s argument to denote the name of the form to be modified. Must specify the -x {server} option. You must specify the -x argument to denote the name of the server containing the form to be modified. A value is expected for the command line option. You included an argument with no specific value on the ardist command line. Reissue the command with values assigned to all arguments. Unrecognized command line option. The specified command line argument is not recognized by ardist. See the Remedy DSO Administrators Guide for more information about valid command line arguments. ardist will not execute with invalid arguments specified. No Alert Events form could be found on the server. The server was unable to locate a form containing the reserved alert events field. Two forms contain all the reserved alert event fields -- delete one to continue. The system found two forms containing the reserved alert events fields. You must delete one form. The two forms are identified in an associated error message. Problem encountered during creation of the Alert Events form. The server was unable to successfully import the Alert Events form at startup. An associated error message contains details about the failure. Must be AR_NOTIFIER user to perform this operation. The server will not allow the removal of the Alert Events form or its reserved fields. Error occurred attempting to communicate with alert client. A sockets error occurred while attempting to establish communication with an alert client. Turn on alert logging to view a trace of the communication activity. Timeout occurred attempting to communicate with alert client. 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. Failed to load the alert cleanup escalation. The server was unable to successfully import the CleanupAlertEvents escalation at startup. An associated error message contains details about the failure.
Invalid alert message format. A failure occurred while attempting to decode an alert message sent from the server to an alert client, indicating a data transmission error. Address in use error occurred attempting to communicate with alert client. When attempting to send an alert to a client, the AR System server encountered a socket address that was still in use by the system. This condition 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. Two forms contain all the reserved server group fields -- delete one to continue. The system found two forms containing the reserved server group fields, which makes both forms qualify as the AR System Server Group Operation Ranking form. You must delete one form. The two forms are identified in an associated error message. No server group operation ranking form could be found on the server. An error occurred during the automatic creation of the AR System Server Group Operation Ranking form. Contact your AR System administrator. Unrecognized server group operation encountered in the ranking form. A server group operation was encountered that is not recognizable by the AR System server. Use only the supplied operation names. Problem encountered during creation of the server group operation ranking form. The AR System Server Group Operation Ranking form definition could not be imported. Check the server error log for the cause of the problem. This configuration setting is not allowed when the server is a member of a server group. 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. Failed to send a server group related signal to another server. The AR System was unable to successfully run a signaling process. Make sure the arsignal utility program is present in the AR System directory. Unable to find a server group entry for this server. An error occurred during the creation of a server group entry in a data dictionary table. Contact your AR System administrator. The specified check interval is below the minimum value of 10 seconds and has been set to 10. A value of less than 10 seconds was specified for the check interval. You cannot set the check interval to a value of less than 10 seconds.
3320 Error
187
Failed to start a server group related agent process. Unable to launch an agent process to communicate with an external program. Make sure that the specified program is present in the AR System servers directory. A floating license specification was ignored because it requires a server group tag The AR System server encountered a floating license definition that was ignored because a server running as a member of a server group only accepts licenses that have a server group tag. Replace the license definition with a license that has a server group tag. A floating license specification was ignored because it is not allowed to have a server group tag. 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 only accepts licenses that do not have a server group tag. Replace the license definition with a license that does not have a server group tag.
3330 Error
3331 Error
A floating license specification was ignored because differing server group tags were encountered The AR System server encountered a floating license definition that was ignored because an AR System server running as a member of a server group only accepts floating licenses that have the same server group tag. Make sure that all floating license definitions have the same server group tag.
3332 Warning
A value change is pending on the Server Group Member setting -- change will take effect the next time the server is started. 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.
Invalid or missing server group operation definition. An internal table containing server group operation definitions has an invalid entry or is missing an expected entry. Contact your AR System administrator. Invalid or missing server group license entry. An internal table containing server group license entries has an invalid entry or is missing an expected entry. Contact your AR System administrator. A value change is pending on the Check Interval setting -- change will take effect when all servers in the group are restarted. This is a warning that Remedy AR System Server must be restarted on all the servers in the server group before a change in how often the server communicates with other servers in the group takes effect.
3350 Error
Unable to locate Report form. The report plug-in was unable to locate a form containing the reserved Report form fields.
Unable to get temporary file name for report definition file. A failure occurred while attempting to get a temporary file name for a report definition. Unable to create temporary file for report definition file. A failure occurred while attempting to create a temporary file for a report definition. Additional information contains the file name. Illegal field encountered in the field list. 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. Illegal field encountered in the sort list. The sort 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. Illegal field encountered in the qualifier. The qualifier 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. Invalid report definition encountered. While attempting 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. Required report field is missing. The field value list supplied to the report creation vendor form is missing a required field. Additional information contains the field number. Minimum server thread requirements for Report ARDBC plug-in have not been met. The minimum number of fast and list server threads must be one greater than the maximum number of plug-in threads. A configuration requirement for the Report plug-in has not been met. In order for the Report plug-in to successfully make requests of the server, there has to be more fast and list server threads running than there are Report plug-in threads running. Therefore, the required configuration is to have the minimum number of fast and list server threads be at least one greater than the maximum number of Report plug-in threads. An acceptable configuration is as follows: Fast thread typeminimum 3, maximum 5 List thread typeminimum 4, maximum 6 Plugin-ARDBC-threadsminimum 2, maximum 4
3354 Error
3355 Error
3356 Error
189
Cannot connect to the directory service. This error message appears when the host name or port number for the directory service are incorrect or when authentication with the directory service fails. The specified LDAP URL is not formatted correctly. This error message is returned when the LDAP search URL does not follow the standard format. The format is:
ldap[s]://host-name[:port-number]/
3377 Error The LDAP operation has failed. This error message appears if the LDAP operation is unsuccessful, for example, because proper attribute names are not specified or the operation would violate access privileges enforced by the directory service. At least one field on the form must reference the Distinguished Name attribute This error message appears because at least one field on the form must reference the distinguished name attribute. Empty or NULL value encountered for the Distinguished Name attribute during a create operation. This error message appears because the field associated with the distinguished name attribute has no value. The distinguished name must have a value in order to create objects. 3400 Error 3401 Error Unable to access server configuration file. The BMC Portal External Authentication plug-in was unable to access the AR System server's configuration file. Verify that the server's configuration file is present and accessible. External authentication endpoint URL not configured. The BMC Portal External Authentication plug-in was unable to locate an endpoint URL configuration item in the AR System server's configuration file. Verify that there is a line with the Ext-Auth-Endpoint-URL label in the configuration file. Unable to initialize web service interface. The BMC Portal External Authentication plug-in was unable to initialize a web service interface to perform authentication. See the supporting text for more information. Unable to terminate web service interface. The BMC Portal External Authentication plug-in was unable to terminate a web service interface that was performing authentication. See the supporting text for more information. Please provide a name for the alarm. This error message appears when you try to save an alarm for which you have not specified a name. You must provide a name to save an alarm.
3502 Error
The variable associated with this alarm has been deleted. A variable should be associated for this alarm to work. This error message appears when you try to open an alarm that references a variable that no longer exists. You must create a new variable for this alarm.
There are no variables in this server. Please create a variable before creating an alarm. This error message appears when you try to create an alarm before you create any variables on the server. Please select a variable. An alarm cannot be saved without selecting a variable. This error message appears when you try to save an alarm for which you have not selected a variable. You must create a variable before you save the alarm. You must enter a user name and message. Please enter them. This error message appears when you try to save an alarm if, in the Notify Properties area of the Configure Alarm tab, you select a notify mechanism value other than None and you do not specify a user name and message. Provide a name for the data source. This error message appears when you try to save a data source without specifying a name. You must add at least one variable to save a data source. This error message appears when you try to save a data source that does not contain any variables. Group access is not defined -- only the administrator has access to this data source. This error message appears when you try to save a data source without assigning public permissions to it. Please provide a name for the flashboard. This error message appears when you try to save a flashboard without specifying a name. You must associate a data source name with the flashboard. Select one from Configuration tab. This error message appears when you try to save a flashboard without first associating a data source with it.
3511 Error
The data source you selected does not contain any variables. Select a data source with variables. This error message appears when you try to save a flashboard that references a data source that has no variables.
3512 Error
No data source has been defined. At least one data source is required to define a valid flashboard. This error message appears when you open or create a flashboard without a data source.
191
End Date and Time should be greater than Start Date and Time. This error message appears when you try to save a flashboard that references a variable with collection interval end date and times that are greater than its start date and time. One of more variables have been deleted from the selected datasource since this flashboard was saved. This error message appears when you open a flashboard when the variable has been deleted. Maximum custom range can not be less than the minimum custom range. This error message appears when you try to save a flashboard with a maximum custom Y-axis value that is less than the minimum custom Y-axis value. You cannot select the start time greater than/same as end time. This error message appears when you are working with a variable and you try to change the data collection start time to be the same as or earlier than the end time. You will have only one data collection in the specified interval. This error message appears when you are working with a variable and you specify 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. You cannot select the end time less than/same as start time. This error message appears when you are working with a variable and you try to change the data collection end time to be the same as or later than the start time. Please select form before proceeding. This error message appears when you try to save a variable without specifying a form name. Please provide a name for the Variable. This error message appears when you try to save a variable without providing a name. You must type an expression for this operation. This error message appears when you try to save a variable for which you have specified an operation other than Count and an empty expression. Invalid schedule interval. This error message appears when the schedule interval is invalid, such as when you try to save a variable with an invalid schedule. Pie charts cannot be selected for History/Summary display type. This error message appears when you try to select a pie chart for a History/Summary display. Pie charts are valid only for real-time data. Internal error. A system error has occurred. Contact your AR System administrator.
Flashboard {flashboard} not found on server {server name}. The flashboard was never created, was renamed, or was deleted. Recreate the flashboard. No forms found containing Flashboards field ID: {field ID} Make sure that the form contains the correct fields. Multiple forms contain Flashboards field ID: {field ID} Do not modify the Flashboards forms. If you modified the forms, you will have the same field IDs in multiple forms. Work only with the forms provided. No forms found with the name: {form name} Check the name of the form and rename the form, if necessary. Invalid Flashboard Data Source: Statistic and History Variables should not be mixed together. Check the data source type and modify, if necessary. Invalid Flashboard type. The type of flashboard is not valid for the action. For example, you might have tried to use an active link to change a line chart to a stack chart. Enter the correct flashboard type. The following parameter(s) needed to display the chart are missing: {parameters}. You may need to relogin to view the chart. The required parameters might be missing from the flashboard definition. Check the flashboard definition.
3608 Error
You have exceeded the allowed usage of Flashboards. Please obtain a license if you wish to continue using Flashboards. Review the license information in the Remedy Flashboards Administrators Guide to make sure that you have purchased a license, or contact Remedy Customer Support.
Error encoding image: {image name}. A system error has occurred. Contact your AR System administrator. Error sending image: {image name}. A system error has occurred. Contact your AR System administrator. General exception creating Flashboard. Contact Remedy Customer Support with a copy of the log statements for the action. User has no access permission to Flashboards data source {data source}. Permissions problem. Contact your AR System administrator. There was no valid Datasource for this Flashboard. The data source is either not associated with the flashboards correctly or does not exist. Check the flashboard definition.
193
There was no valid Variable for this Flashboard. The variable is either not associated with the flashboards correctly or does not exist. Check the flashboard definition or create a new variable. Invalid chart type, valid numbers for a chart are from 0 to 5. Specify a chart type from 0 to 5. Internal error. A system error has occurred. Contact your AR System administrator. Internal error. Form meta data is invalid. A system error has occurred. Contact your AR System administrator. No history data was found in the AR System server to display this Flashboard. No history data has been collected in the FB:History form for this flashboard. History data can not be displayed on a pie chart. History data can be displayed in all chart types except pie charts. To display history data, specify a different chart type. No user-customizable parameters have been defined. User-customizable parameters have not been defined for the flashboard. See your AR System administrator. No summary data was found in the AR System server to display this Flashboard. No history summary data has been collected in the FB:History Summary form for this flashboard. There is no data available to display this chart. The AR System form defined for this flashboard contains no data. Summary data can not be displayed on a pie chart. History summary data can be displayed in all chart types except pie charts. To display history summary data, specify a different chart type. Cannot login to the AR System server. The flashboards mid tier system could not log in to the AR System server because the user does not have the required permissions, or the flashboards mid tier system could not connect with the AR System server. Contact your AR System administrator.
3625 Error
Cannot display a graph that contains more than {number} data points. The number of data points to be plotted on the flashboard exceeds the limit. The default limit is 3000 data points. An AR System administrator can increase this limit by adding the following property to the config.properties file located in the <mid_tier_ install_directory>/WEB-INF/classes directory:
flashboards.maxDataPoints
An example property that increases the limit to 4000 is:
flashboards.maxDataPoints=4000
4000 Note 4001 Note 4002 Note Import completed successfully -- <number> records imported. This message appears after a successful Import operation. No errors were encountered during import. Import of <import_file_name> started. System reports that the Import operation has begun. This message is logged only to the log file. Only one field title exists in import file -- ensure that you specified the import file correctly. System warns you that the specified import file has only one field. This is usually caused by an incorrect Import file format or separator string specified on the Open Import File dialog box. You have not added or saved your changes to the current fallback mapping -- if you continue, those changes will be lost. System dismisses the Fallback Mappings window before applying the changes. 4004 Note You have not saved nor imported data with the current mappings -- if you continue, the mappings will be lost. You have 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 warning. 4005 Note You have not added or saved your changes to the current mapping -- if you continue, those changes will be lost. The current mapping has been changed but not applied. Click the Modify or the Add button to avoid this warning. 4006 Note You have not saved your changes to the current mapping -- if you continue, those changes will not be used for this import. You will get this warning if the current mapping has been changed but not applied when the Import button is clicked. Click the Modify or Add button to avoid this warning. 4007 Note Are you sure you want to delete all mappings? System confirms the Delete All button is in both the main and Fallback mapping windows.
4003 Note
195
4008 Note 4009 Note 4010 Note 4011 Note 4012 Note 4013 Note 4014 Note
Record <number>: Field <field_name> truncated to <number> characters. This message is logged to the log file when a field is truncated during an Import operation. This message is logged only to the log file. Are you sure you want to start importing? System confirms that you really want to begin the Import operation. Mapping <mapping_name> not loaded. The specified mapping is not loaded. Earlier messages described why. Duplicate name for mapping. Do you want to overwrite the existing mapping? A mapping with the name you have specified already exists. If you choose to overwrite it, the earlier mapping will be replaced by the new one. Exit Import Tool? System confirms that you want to exit Remedy Import. Did not find any matching fields to add as new mappings. The Add All button operation did not find any matching form and import fields to add as mappings. Copy unprocessed import records to the log file? You have stopped the Import process before the tool has completed operation. Specify whether you want the remaining records to be copied to the log file. You have not saved your changes to the current fallback mappings. If you continue, your changes will not be used for this import. You are trying to start the Import operation without applying the changes they have made to the fallback mapping window. If you continue, any settings you have made to the fallback mappings window that have not been saved will be 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.
4015 Note
4016 Note
Save your current mappings before closing this window? You have made but not saved changes to the Save Mapping window. If you continue, your changes will be lost. To save changes you have made, click No to cancel closing the window. This file contains duplicate or empty field titles. A number has been appended to those titles. There are duplicate field titles in the .csv or .asc import data file. A number has been 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 has been changed so that Remedy Import can distinguish between the two fields during mapping of data values.
4017 Note
4018 Note
This file contains duplicate or empty field titles. Those titles have been replaced by their field ids. Duplicate field titles exist in the .arx import data file. When duplicate names are found in an .arx format file, both fields will be replaced with their IDs to eliminate confusion about the fields.
4019 Note
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 will be shown by their field IDs in the form fields list.
Invalid AR Export format, file: <import_file_name>. The specified import file is not in AR Export format, which you have specified it to be. Import completed with errors: <number> records were imported; <number> records were not. The Import operation has been completed. View the log file to see the error messages and records that did not get imported.
User did not wish to continue operation. The user terminated the Import operation after it has already started. Copying remaining records of <import_file_name> to log file. The second part of the message that appears after you stop the Import operation before it is completed and you choose to copy the remaining records to the log file. You should never see this message by itself. Stop broadcast. This error message is used in Remedy Import when there is a broadcast of messages within Windows. It occurs when the broadcast message is stopped. Cannot log record starting at <file_offset_of_record>. The record starting at the specified offset cannot be read. This error can be caused by not being able to perform Open or Seek operations in the import file. No mapping selected to delete. You tried to delete a fallback mapping in Remedy Import without first selecting one. No saved mappings specified in batch mode. The tool is running in batch mode, but you did not specify which mapping to use for import on the command line. Cannot get children widgets, or widget not a child. This error appears when adding, changing, or removing a mapping request (regular or fallback). It indicates a failure of the mapping or fallback mapping list box to add, remove, or change a request.
197
Cannot login to any AR Server. The tool is running in batch mode, but none of the servers specified on the command line or in the /etc/ar file are available. Two mappings have been specified on the command line. The tool is running in batch mode, but you specified two mappings to use for the Import operation on the command line. Only one mapping is allowed. The -m option requires a mapping name. You used the -m flag on the command line, but did not supply a mapping name following the flag. The mapping name is longer than the maximum allowed length. You specified a mapping name that is longer than 30 characters. A directory may be specified only if you specify a mapping. You used the -d flag on the command line, but did not also specify a mapping with the -m flag. <field_name> is not a Form Field. The field name specified in the Form Field text control is not a valid field name for the current form. Enter a valid field name. Try reselecting the form and redefining the mappings; it is possible that the definition of the form was changed by another user.
<field_name> is not an import field name, id, or keyword. You used the variable syntax ($) in the mapping value, but the string enclosed by the dollar signs ($) is not an Import field, an Import field ID, or a keyword. Cannot get the status of or cannot open log file. You have specified a log file name that cannot be opened for read and write. You may not have permission to use the log file. Verify the owner and the permissions for the file. A log file name is required. You have erased the log file name and clicked Save in the Preferences window. Log file <path_name> is a directory. You have specified a directory in the log file text field. Import log file name is longer than the maximum allowed length. You have specified a log file name longer than 255 characters. Log file <file_name> is not a regular text file. You have specified a log file that is a special file type instead of a normal text file. Choose another file as the log file.
Cannot write to log file. A system error occurred while writing the log file. The system error is the second part of this message. Cannot initialize the server API. Remedy Import cannot initialize the server API and so cannot establish a connection to AR System server. Cannot build the main import window. Remedy Import could not create the main window, and the tool could not be started. The system is probably out of memory. Bad parameters. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Bad globals. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Cannot add to mapping list. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Cannot set mapping list item. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. No tokens for a Direct Mapping. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Cannot open map file for specified mapping. The mapping file that contains the specified mapping cannot be opened. You may have moved the file or the directory that contained the mapping. Cannot find specified mapping. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Cannot read map file for specified mapping. The mapping file that contains the specified mapping cannot be read. The file probably has incorrect permissions set. The import option value is invalid. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation.
199
The mapping file has a syntax error. The mapping file contains invalid syntax. This is probably caused by a user who edited the mapping file manually. Correct the syntax as necessary. Bad Mapping or Compound mapping within Compound mapping. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Bad internal list. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Import fields' titles-list is invalid. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Bad Mapping list. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Bad Fallback Mapping list. This is an internal error. You may be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Bad Form Information UI Fields list. This is an internal error. You might be able to perform the operation by shutting down Remedy Import, restarting it, and performing your operation. Record <number> : Cannot parse record in import file The tool could not understand this record in the import file. This condition could result from low memory. Cannot parse import field titles in import file. The tool could not understand the field titles in the import file. This condition could result from low memory. Specified import file does not exist. You specified a nonexistent file as the import file, or you have removed the file since Remedy Import started. Syntax error in the mapping string. The tool was not able to understand the syntax in the mapping value string. Rewrite the mapping. Specified import file is a directory. You have specified a directory as the import file.
Specified import file is not a regular text file. You have specified an import file that is a special file type instead of a normal text file. Cannot get the status of import file. The import file, or the directory it is in, is no longer accessible. Specified import file is empty. The import file is of length zero. Specified import file has no data. The Import file contains only field titles (if that) and no data. An import file name is required. You tried to close the Open Import File window without specifying an Import file. Import file name is longer than the maximum allowed length. The specified Import file name is longer than 255 characters. The import field separator string is longer than the maximum allowed length. The specified Import field separator string is longer than 30 characters. A field separator string is required. For the ASCII file format, a field separator string is required for reading in the field titles. Cannot open specified import file. The specified import file cannot be opened due to a system error. The system error appears in the second part of this message. Cannot seek in import file. 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. AR Export file's Field ID string does not contain a number. 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.
Record <number> : Unrecognized tag in AR Export file: <file_name>. 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. Import file <file_name> is of an unknown type. This is an internal error. The import file type has not yet been set.
201
Cannot find form field with saved index. This error message appears when you fail to put the mapping at a given index into the form and into the mapping text field in Remedy Import. Bad Import file record. The specified import file contains a record that is improperly formatted. Record <number> : <value> is not a valid value for field <field_name>. The value in the import file is not valid for the form field it has been 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. Record <number> : Too many fields; found <number_found>, expected <number_expected>. The record has more fields than the number of field titles. Record <number> : Not enough fields; found <number_found>, expected <number_expected>. The record has fewer fields than the number of field titles. Import completed successfully: <number_imported> records imported; <number_truncated> records were truncated. After you choose the Truncate option in the Preferences dialog box and records have been truncated, this message indicates how many records have been truncated and imported.
End of <number_of_copied_records> records. Message printed in the log file at the end of all copied records from the Import file. You will never see this message in a dialog box. Import completed with errors: <number_imported> records were imported; <number_not_imported> records were not; <number_truncated> records were truncated. After you choose the Truncate option in the Preferences dialog box and records have been truncated (and some records not imported due to errors), this message indicates how many records have been truncated and not imported.
Two directories to look for saved mappings have been specified on the command line. Only one -d argument is allowed on the command line. Create of mapping failed. The mapping file could not be created. The error has already been displayed in previous dialog boxes. No mappings are defined. You chose the Load Mapping menu item, but there are no mappings files in $ARHOME/ arcmds or in any of the directories on the ARPATH environment variable.
Broadcast message not handled. This error message occurs in the Remedy Administrator when a window broadcasts a message to another window and that window cannot handle the message. Record <number>: a field exceeds the maximum size allowed. 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 Error
Cannot open the default log file. 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 there is enough disk space and that all the directories exist. User stopped import after <number_processed> records were processed, of which <number_imported> were imported. You decided to stop the import process before it has been completed. This message indicates how many records were processed and how many were imported.
4499 Warning
Invalid Value. 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. Already Bound. 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. NULL value. 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. Missing : in the parsed instruction. 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. Missing Field Label in parsed string. The field value was supplied without the field label in the email message. Supply the field label. Missing XML <> tag parsed instruction. An expected XML tag is missing in the email message. Supply the missing XML tag.
203
Invalid value. 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. Missing Instruction. The expected header instruction action is missing from the email message. Supply the action instruction. Error creating mail message. 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. Unable to locate the specified User Instruction. 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. Command Line Parameter already defined. 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. Command Line Parameter not defined. 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 information that is missing. Provide the missing parameter. Command Line Parameter Value is missing. 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. Command Line Parameter is not valid. 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. Invalid Email Daemon. Invalid configuration values in the EmailDaemon.properties file. Review the EmailDaemon.properties file to see if anything is missing. Missing Action Parameter. 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.
4914 Error
4919 Error
Field type does not allow the field to be modified. You cannot modify the form because an invalid value was supplied. The supplied data type does not match the data type that is required for the field. Provide the correct value for the field. Missing Attachment. An expected attachment was missing while processing an incoming email message. Provide the expected attachment. Security Key is disabled. The security key provided in the incoming email message is disabled. Contact your AR System administrator. Security Key has expired The security key provided in the incoming email message has expired. Contact your AR System administrator. Security Key not found on Form. An invalid security key was entered. Verify that the right security key was entered. If the problem still occurs, contact your AR System administrator. Security Key is not valid for the specified From Email Address. The security key does not match the originating email address. Verify that you specified the correct security key for the email address used. Missing AR System User Information. No login information was specified or the specified login information is invalid. Check the email sent. If login information has been specified, make sure that the email mailbox is set to use user supplied login information.
4928 Error
Unable to locate the specified User Instruction. 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. Missing Template. 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. Unable to encrypt. A problem occurred in encrypting the modify key. Contact Remedy Customer Support. Unable to decrypt. A problem occurred in decrypting the modify key. Contact Remedy Customer Support.
205
Unable to locate message with the specified Entry ID. The modify key contains an invalid entry ID. Make sure that the modify key has not been modified and that the original outgoing email message has not been deleted. Invalid Server Name. The modify key contains an invalid AR System server name. Make sure that the modify key has not been modified and that the original outgoing email message has not been deleted. Invalid Checksum. The modify key in the incoming email message with modify action is invalid. Make sure that the modify key has not been modified. Missing Modify Key, unable to execute Instructions. The modify key is missing from the email message with the modify action. Make sure that the modify key is not deleted from the message. Modifications are disabled on this mailbox. Modify actions have been disallowed for the incoming mailbox. Contact your AR System administrator. Unable to execute Modify Action due to missing security key. The email message with the modify action is missing a security key. You must provide the security key. Invalid Date/Time format for specified date. The correct format is <format>. 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. Internal Exception Caught. Reason: An unknown system error has occurred. Contact Remedy Customer Support Recipients have not been specified for this email. No email addresses have been specified for the email message. Verify that the email address was specified. No matching requests (or no permission to requests) for qualification criteria. No matching entries were found for the qualification. Verify your qualification or contact your AR System administrator Form is missing. Will retry connection to server in <no_minutes) minutes. The AR System Email Mailbox Configuration form does not exist or the AR System server is not available. Contact your AR System administrator. Invalid Enumerated Value supplied for selection field. The supplied value for an option (radio button) or a drop-down list item is invalid. Verify that you provided the correct value.
Sender address not found in original email. The email address of the sender of the modify email is not found in the original email message. Contact your AR System administrator. No field values supplied. No fields were specified for submit or modify operation. Specify values for the action. Missing currency code for the currency value specified. A currency value was specified without a currency code. Specify a currency code for the value. Attachment file size exceeds the limit set in emaildaemon.properties. The attachment is too large. See your AR System administrator. Email address contains invalid characters. Invalid characters were found in the email address for the email message. Verify that the email address that was specified correctly. Variable replacement with a qualification requires a form and a server. If you use variable replacement with a qualification, you must supply a form name and an AR System server name. None of the recipients have access to form: <form_name>. The required form access permissions are not available. See your AR System administrator. 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. This error message is returned because you attempted to map data types that are incompatible.
7002 Error
Invalid mapping because of incompatible data types. AR Datatype - Decimal can only be mapped to XML Datatype - decimal, long, or unsigned Long. This error message is returned because you attempted to map data types that are incompatible.
7003 Error
Invalid mapping because of incompatible data types. AR Datatype - View or Display can only be mapped to XML Datatype - string. This error message is returned because you attempted to map data types that are incompatible.
7004 Error
Invalid mapping because of incompatible data types. AR Datatype - DateTime can only be mapped to XML Datatype - dateTime. This error message is returned because you attempted to map data types that are incompatible.
207
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. This error message is returned because you attempted to map data types that are incompatible.
7006 Error
Invalid mapping because of incompatible data types. AR Datatype - TimeOfDay can only be mapped to XML Datatype - time. This error message is returned because you attempted to map data types that are incompatible.
7007 Error
Invalid mapping because of incompatible data types. AR Datatype - Real can only be mapped to XML Datatype - double or float. This error message is returned because you attempted to map data types that are incompatible.
7008 Error
Invalid mapping because of incompatible data types. AR Datatype - Diary can only be mapped to XML Datatype - string. This error message is returned because you attempted to map data types that are incompatible.
7009 Error
Invalid mapping because of incompatible data types. AR Datatype - Enum can only be mapped to XML Datatype - string. This error message is returned because you attempted to map data types that are incompatible.
7010 Error
Invalid mapping because of incompatible data types. AR Datatype - Attachment can only be mapped to XML Datatype - hexBinary or base64Binary. This error message is returned because you attempted to map data types that are incompatible.
7011 Error
A few warnings occurred while loading the xml schema. This error is returned when loading the external XML schema for the input and output mappings of the web services operation. You will also this error when you are opening a web service that is imported from another system but does not have all the forms associated with that web service. Failed to create internal mapping from wsdl. This error is returned when an invalid URL (or an URL that you have no permissions to access) is entered for loading Wsdl while creating the filter Set Fields web services action. Failed to generate wsdl from internal mapping. This internal error is returned when there are problems while importing the web service from a definition file or while saving the web service.
Failed to resolve existing mappings with the specified schema. This error is returned when a new XML schema is loaded which might be affecting the mappings which were already created in the web service. Failed to get top level elements from xml schema. Specified schema could not be imported. This error is returned when there is a problem with loading the external XML schema. For example, the dependencies of an element in a schema might be missing. Failed to create initial mapping from the specified top level element/type. This internal error is returned when retrieving the XML data type from the schema. Failed to initialize JRE and internal java module. This error is returned when the JRE dependencies are missing or corrupt. Check the required JRE configuration information in the Configuring AR System guide. Failed to load WSUtil63.dll (related to webservices). Please verify your installation procedure. The WSUtil60.dll file must be in the \Admin folder under AR System. If this file is not present, verify the Remedy Administrator installation logs.
Please enter statistics logging interval for form. The interval is blank or invalid. An integer value specifying the interval (in seconds) to collect statistics is required. Auto Layout Style Property must be available at application level or view level. Turning off the Auto Layout mode. No style sheet is available for the current view or the application, or the style sheet has been removed. Add the style sheet, then turn on Auto Layout.
There are no properties in the style sheet. When exporting a style sheet to an XML file, the style sheet must have properties defined. Can not switch to restricted list as selected form(s) do not belong to the application. Remove references to forms that are not in the application or in access points. The entry point order must be between 1 and 2147483647. Please enter a new order. 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. The dynamic field values must contain valid field / keyword references. A dynamic field value has been 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. Please enter statistics logging interval for application. The interval is blank or invalid. An integer value specifying the interval (in seconds) to collect statistics is required.
209
Application Statistics Configuration form not found on the server. The Application Statistics Configuration form is deleted or corrupted. Restart the AR System server and the form will be recreated automatically. The set field list did not contain a reference to a dynamic assignment. The active link cannot be saved because the Advanced option is selected and no advanced features are used. You must either create a dynamic field assignment or clear the Advanced option. XML export of locked objects is not supported in this version. The objects will be exported in def file format. 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.
7046 Error
Navigation area is greater than VUI area. 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. Left margin/Level Indent in the navigation properties is greater than the Navigation Area. 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. This operation may delete some fields, resulting in a loss of data and/or broken workflow. Do you wish to Continue? This is a warning that is a result of 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.
Permissions should be supplied to the owning application object. This is a warning message that you should supply valid corresponding permissions to the application object that owns the current server object. Moving a form into a deployable application will strip away all non-implicit groups from the form and its related workflow objects. You must assign roles to these objects for proper access control. Do you want to continue? This is a warning message 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 message 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. It is recommended that you back up your data and current definitions before continuing.
7054 Warning 7055 Warning 7056 Error 7058 Warning 7059 Warning
Once you have licensed an application, you cannot unlicense it. This is a warning message that the license for a licensed application cannot be made less restrictive. Licensing an application is not a reversible process. Do you wish to continue? This is a warning message that after licensing an application, the license cannot be made less restrictive. Can not delete an application which is open in an Application Window. You must close the application window before you can delete the application This is an archive form. Are you sure you want to delete it? This is a warning message that 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. Some forms had archive forms associated with them. These archive forms have been automatically licensed. This is an informational message that if you license a form any associated archive form is automatically licensed.
Unable to Save/Update Form due to an HTML processing error: <system_error_code>. An internal error occurred during HTML processing, which probably indicates that the system is low on resources. Restart the computer running AR System. Unable to Import web page due to an HTML processing error: <system_error_code>. An internal error occurred during HTML processing, which probably indicates that the system is low on resources. Restart the computer running AR System. Unable to merge template due to an HTML processing error: <system_error_code>. An internal error occurred during HTML processing, which probably indicates that the system is low on resources. Restart the computer running AR System. Please provide valid target directory for the following object type(s): <object type> A target directory is required for all object types when using the Remedy integration with ClearCase. One or more entries match filter conditionsthis operation has been defined so that any matches generate an error. This message occurs when the Any Match for a Push Fields filter action is defined as Error.
211
8031 Warning
Some of the fields and/or workflow in this form are not supported in this version of the client. When retrieving a list of field definitions for a form, there was a failure filtering certain field IDs (for example, attachment fields) into the destination structure. The copy operation failed due to problems with permissions.
8032 Warning
An admin group list was found in an owned container. The administrators access permissions are determined by the owning object. A warning was returned because an owned container cannot have a list of subadministrator groups. This list will be disregarded
8033 Warning
A value change is pending on the floating license timeoutchange will take effect the next time the server is started. The number of hours for the Write Floating License Timeout has been changed in the Timeouts tab of the Server Info window. These server configuration settings will not go into effect until the server is stopped, then re-started.
8034 Warning
A value change is pending on the full text floating license timeoutchange will take effect the next time the server is started. The number of hours for the Full Text Search Floating License Timeout has been changed in the Timeouts tab of the Server Info window. These server configuration settings will not go into effect until the server is stopped, then re-started.
Referenced character menu does not exist. 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. The RPC socket number specified is not one of the legal values (0, 390600, 390621 - 390634, 390636 - 390669, 390680 - 390694). 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
The RPC port specified is not one of the legal values (0, 1 - 65535). 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. The servers RPC version is not supported. There was an error creating an RPC connection, because this version of AR System server is no longer supported. To continue, upgrade to a later version of AR System.
8204 Error
RPC control failed to set non-blocking I/O mode. Continuing in blocked I/O mode. This error occurs when the RPC-Non-Blocking-IO parameter is set in the AR System configuration file and the AR System server continues in blocking mode. For more information, see the Configuring AR System guide. The number of rows exceeded the maximum allowed limit of 999. This error occurs in Remedy Administrator when you attempt to set the number of rows for a character field to less than 999. Please select a source code control provider. This error occurs in the Server Information Dialog, Source Control page, when you click the Browse button and no source control provider is selected in the Provider Name field. You must install a source control system and select it in the Provider Name pull-down menu before you click the Browse button. Bad attachment locator type. The only acceptable attachment locator types are the filename or the buffer. Use only these types. Invalid attachment size. AR System forms cannot store attachments of the size reported. This error is usually caused by an attachment that is too large. This error can also be generated when an attachment is erroneously reported with a negative size, for example, by an API program. Empty automation. The automation structure required when defining an OLE Automation active link action is empty. You must specify the appropriate contents for this structure. Empty COM method list. The method list required when defining an OLE Automation active link action is empty. You must provide at least one method for this structure. Invalid COM value. The value of an ARCOMValueStruct variable in a method or parameter of an OLE Automation active link action is invalid. Provide a valid value. Invalid COM name. 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). Correct the name to continue your work. Invalid class ID or interface ID. 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).
8708 Error
213
Invalid COM method. 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. Invalid COM method name. The name of a method in an OLE Automation is either empty or exceeds the maximum length allowed (128 characters). Empty COM method. The method structure required when defining an OLE Automation active link action is empty. You must provide at least one method for this structure. Empty COM parameter list. The parameter list required when defining an OLE Automation active link action is empty. You must provide at least one method for this structure. Empty COM parameter. The parameter structure of a method required when defining a method in an OLE Automation active link action is empty. You must specify the appropriate contents for this structure. Invalid COM parameter. 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. Invalid automation string. An automation action string required when defining an OLE Automation active link action is either empty or exceeds the maximum length allowed (2000 characters). The RPC socket number for the Approval Server process is not one of the legal values (390600, 390680 390694). 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.
The value for the Application Check Interval is not within the legal range of 0 to 3600 seconds. The value for Application Check Interval is not set properly. Set this to a legal value. Open dialog structure empty. This message occurs when you attempt to create an Open Dialog active link action without specifying an open dialog structure value. You must enter a value to create the Open Dialog active link action.
8721 Error
Call guide structure empty. This message occurs when you attempt to create a Call Guide active link action without specifying a Call Guide structure value. You must enter a value to create the Call Guide active link action. Guide name missing. This message occurs when you attempt to create a Call Guide active link action without specifying a Call Guide active link name. You must enter a name to create the Call Guide active link action. Go To guide label empty. This message occurs when you attempt to create a Go To active link action without specifying a Go To action label. You must enter a label to create the Go To active link action. Go To action tag is invalid. The tag must be a field or value. This message occurs when you attempt to create a Go To active link action without specifying a field or value for the Go To action tag. You must use a field or value to create the Go To active link action. Continuation button title is empty or too long. 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. Guide calling itself is not allowed. The guide cannot contain workflow that calls that same guide. Invalid external table name in a vendor field mapping structure. The name identified in the vendor field definition is empty or exceeds the defined length restriction. Invalid vendor form definition. The name identified in the vendor form definition is empty. Vendor forms not allowed in join forms. The join form definition includes a vendor form as one of its base forms. Vendor forms may not participate in joins. Specify only forms that are not Vendor forms. Changing the field mapping is not allowed for join fields. The field definition for a field on a join form may not be modified once the field has been defined. However, you can modify it without error by setting it to the existing mapping. Changing the type in the field mapping structure is not allowed. When modifying an existing field in a form, you attempted to change a field to a different type.
8722 Error
215
8732 Error 8733 Error 8734 Error 8735 Error 8736 Error 8737 Error 8738 Error 8739 Error 8747 Error 8750 Error 8751 Error 8752 Error 8754 Error
Bad client type. The value must be a non-negative integer. You attempted to define a disabled or non-existent client type in the client list, that is, by setting the client type to a number less than zero. Unrecognized currency part tag. This error message is returned if the currency part structure tag contains a value that is not legal. Invalid currency code string length. This error message is returned if the currency code is not a valid three character string, for example, USD. Invalid decimal value. 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. An arithmetic error was encountered in a decimal calculation. Your system is unable to complete the arithmetic operation. Contact your AR System administrator for assistance. Notify header name is over the maximum size allowed for the name. Enter a header name of 255 bytes or less for the email notification template. Notify footer name is over the maximum size allowed for the name. Enter a footer name of 255 bytes or less for the email notification template. Notify content name is over the maximum size allowed for the name. Enter a content name of 255 bytes or less for the email notification template. Unable to access thread local storage. The AR System server has encountered a serious error performing a fundamental operating system function. The most likely cause is that the system is out of memory. Create entry operations are not supported for this form. AR System database connectivity plug-in associated with the form does not support create operations and a creation was attempted. Set entry operations are not supported for this form. AR System database connectivity plug-in associated with the form does not support modify operations and a modification was attempted. Delete entry operations are not supported for this form. AR System database connectivity plug-in associated with the form does not support delete operations and a deletion was attempted. Retrieving attachment data is not supported for this form. AR System database connectivity plug-in does not support attachments.
The specified plug-in does not exist. AR System server has referenced a plug-in that the plug-in service has not loaded. An error has occurred while loading a plug-in. The plug-in service was unable to load the specified plug-in. An associated error message contains details of the failure. The plug-in name is empty, contains invalid characters, or is a reserved name. The plug-in will not load. Plug-in names may not be empty, may not contain space characters, and may not be a reserved name, such as AREA.
The plug-in does not implement ARPluginIdentify(). The plug-in will not load. All plug-ins must define the function ARPluginIdentify() and the specified plug-in does not do so. Cannot establish a network connection to the AR System Plug-In server. The plug-in server is either not running, or has been configured to run at a specific port number and has not registered with a portmapper. 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 has been established to restrict access to AR System servers that have been similarly configured. In this case, the password used by AR System server does not match that of the plug-in service.
The specified plug-in failed to initialize properly. Contact your AR System Administrator for assistance. The plug-in encountered an error while attempting to initialize, and failed to load. The specified plug-in failed to set properties. This error message reports the failure when the set property function of the specified plugin fails in any way. The RPC socket number for plug-in loopback is not one of the legal values (390621 - 390634, 390636 - 390669, 390680 - 390694). 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.
The specified container owner name is incorrect. This is likely caused by a programming error, for example, in an incorrect API program. The value of the specified reference is empty. This is likely caused by a programming error, for example, in an incorrect API program. The label of the specified reference is empty. This is likely caused by a programming error, for example, in an incorrect API program.
217
The description of the specified reference is empty. This is likely caused by a programming error, for example, in an incorrect API program. The specified container does not exist. 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. You do not have access to the specified container. You do not have permission to access this container. Contact your AR System administrator for assistance. The specified container is missing. 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. Illegal container type. You attempted 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 Error 8811 Error 8812 Error 8816 Error 8817 Error The specified container already exists. Enter a different name for the container. No name was specified for the owning object. No owner name was specified. This is likely caused when there is an error in a definition file you are attempting to import. Container cannot be owned by this type of object. This is likely caused by a programming error, for example, in an incorrect API program. Illegal reference type. This is likely caused by a programming error, for example, in an incorrect API program in which the reference list is invalid. The value of the external reference has an invalid format. This is likely caused by a programming error, for example, in an incorrect API program.
8818 Error 8830 Note 8831 Warning 8832 Error
The container is not supported by the server. This is likely caused by old server containers. Object cannot be locked. One of more objects being exported cannot be locked. Object locking is not supported for DSO or flashboards objects. Contact Remedy Customer Support for assistance, if necessary. Locking level cannot be decreased. A locked object can be exported only at the same lock level or a higher lock level. Contact Remedy Customer Support for assistance, if necessary. Unknown object lock level specified. 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 only be encountered through an API program.
8833 Warning 8834 Error 8835 Error 8836 Error 8837 Note 8838 Warning 8839 Error
Lock key cannot be changed, so the existing key will be kept. A locked object can only be exported with the same lock key. Changing the lock key is not allowed. Lock information mismatch. Locking properties of the object do not match the locking properties of the lock group. The definition file is possibly corrupted. Contact Remedy Customer Support. Unable to load object lock information into cache. A system error has occurred. Contact Remedy Customer Support. Specified lock block cannot be found. A non-critical error has occurred in the server cache. Restart the AR System server. End of file reached. An unexpected end of file has occurred during file processing. No information is returned for the hidden locked object. Information is not returned for hidden locked objects. Cannot delete a locked object -- must override to delete. You cannot delete just this single locked object. You must delete the group of objects that have the locked key. Use the AR_LOCK_BLOCK_DELETE option to delete all the objects in the lock group. This error can only be encountered through an API program. Attempt to modify a locked object failed -- inappropriate changes are discarded. You attempted to modify an object that has a read-only lock, such as by adding a form to a filter that is read-only. You cannot modify a locked object.
8840 Warning
219
Safeguard mismatch - potentially corrupted form. A system error has occurred. The object is possibly corrupted. The form might have been modified at the database level. Contact Remedy Customer Support. Safeguard mismatch - potentially corrupted container. A system error has 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 Remedy Customer Support. Safeguard mismatch - potentially corrupted active link. A system error has occurred. The object is possibly corrupted. The active link might have been modified at the database level. Contact Remedy Customer Support. Safeguard mismatch - potentially corrupted filter. A system error has occurred. The object is possibly corrupted. The filter might have been modified at the database level. Contact Remedy Customer Support. Safeguard mismatch - potentially corrupted escalation. A system error has occurred. The object is possibly corrupted. The escalation might have been modified at the database level. Contact Remedy Customer Support. Safeguard mismatch - potentially corrupted menu. A system error has occurred. The object is possibly corrupted. The menu might have been modified at the database level. Contact Remedy Customer Support. Field creation not allowed on a locked form. You cannot create fields on a locked form. Field deletion not allowed on a locked form. You cannot delete fields on a locked form. Setting object lock information is disallowed at this time. During set or create operations locked object properties are not expected. You must export the object as locked. A lock block must be exported entirely in xml or entirely in def format. In a single export call, all the objects must be exported in the same format, which can be .xml or .def. Setting BSM tag disallowed. This action is for internal use only. GetListFields not allowed with this type of form. This operation cannot be performed on a dialog form. A dialog has no data to query. GetListFields ignored for this type of form. This operation cannot be performed on a dialog form. A dialog has no data to query.
8843 Error 8844 Error 8845 Error 8846 Error 8847 Error 8848 Error 8849 Warning 8850 Error 8851 Warning 8900 Error 8901 Warning
8902 Error 8903 Warning 8905 Error 8907 Error 8908 Error 8909 Error 8910 Error
Sort list not allowed with this type of form. This operation cannot be performed on a dialog form. A dialog has no data to query. Sort list ignored for this type of form. This operation cannot be performed on a dialog form. A dialog has no data to query. Escalations cannot access fields in this type of form. This operation cannot be performed on a dialog form. A dialog has no data to query. This type of form can only have display-only fields. This operation cannot be performed on a dialog form. A dialog has no data to query. Windows logon fails due to unknown user or invalid password. 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. Dialog forms not allowed in join forms. 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. The field is referenced in the qualifier of a table field. This message occurs when you attempt to delete a field that is referenced in a table field qualification. You cannot delete fields that are referenced in table field qualifications. Remove the field name from the qualification if you want to delete the field. Some of the fields have been truncated from the results list because the total length of the fields and separators is greater than the maximum allowed. The 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.
8911 Warning
8912 Error
The ARGetListEntryWithFields call is not supported by the server. This error appears when active link workflow attempts to perform an ARGetListEntryWithFields call with a pre-4.0 AR System server. This API call is not possible with older servers. Error accessing semaphore. This error appears when a server is unable to get or lock a semaphore. Make sure that your machine is configured correctly for shared memory and semaphores. If it is, run arsystem stop, and then run arsystem start. Workflow logging active. This special message for logging appears when the request log type matches the current log. Unable to write logging to requested file. This logging error typically is returned if you have run out of disk space. To continue, free up space in the log directory by deleting old or unwanted files.
8913 Error
8914 Note 8915 Warning
221
8918 Error 8920 Error 8921 Error 8922 Error 8923 Error 8924 Error 8925 Error 8926 Note 8927 Error 8930 Error 8931 Error
Failure during attempt to update next available VUI ID. This error is returned when you are unable to update the next field ID column in the database for any new VUI in a form. Must specify a workflow connection structure to create an active link, filter, or escalation. This error is returned when you have not specified the form(s) for the workflow you are creating. You must specify the form(s) to which the workflow is attached. Workflow connection structure type of form list specified, but no form list was supplied. This error is returned if there are no forms in the form list. The workflow must be associated with a single form or a list of forms that currently exists on the server. The authentication service is not responding. Cannot connect to the system at this time. Contact your AR System Administrator for assistance. The external authentication server is not responding to calls from the AR System server. Unrecognized or misused tag for workflow connection structure. This error is returned if there is no form list for the workflow connection. The workflow must be associated with a list of forms that currently exist on the server. Form name specified multiple times in workflow connection structure form list. This error is returned if two or more forms in a form list have duplicate form names. The legal value for the RPC socket number for the External Authentication process is 390695. The user has attempted to set the value of the external authentication RPC socket to a different value than 390695. Specify this value only. Authentication Note: <note> The appended text is a message from the external authentication server. Authentication Error: <error> The appended text is a message from the external authentication server. The form was not found in the cache. This error is returned if an invalid form is found in the form list. Error in semaphore name. This error is returned if there is an error 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. You do not have write license. This error is returned if the user is modifying the contents of a field but does not have write access.
8932 Error
8933 Warning
No views were imported. This error is returned when your attempt to import views into the form failed. An associated message indicates why the view was not imported. Correct the error, and try to import the item again. Unable to communicate with arfork daemon. This error is returned because the proxy fork process was unable to write information to its log file. Upgrade of the server internal forms failed. This error is returned because only a valid internal form definition can be upgraded. Valid forms here include only the following: Distributed Mapping Distributed Pending Distributed Pool Application Pending
8936 Error
Compression of file failed. Compression failed when adding the attachment file to a request during the PerformAction-Add-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. Client operation was disabled. This error is returned if a client type operation is disabled for the current user, for example, if a user belongs to an excluded group. Error during Xerces-c Initialization. The Xerces library globals used in the XML parser failed to initialize. The AR System Plug-In server is not responding. Cannot connect to the system at this time. Contact your AR System Administrator for assistance. There was an RPC time-out when connecting to the arplugin service. To continue, make sure that the arplugin service and AR System plug-ins are running.
Error during XML definition parsing. This error is returned when parsing an XML document. The XML file, XML string, and XML object name cannot be parsed. XML Parsing error. Invalid element tag. The parser encountered an invalid element tag while parsing the XML document. XML Parsing error. Invalid attribute tag. The parser encountered an invalid attribute tag while parsing the XML document.
223
XML Parsing error. Invalid enumeration value. The parser encountered an invalid enumeration value while parsing the XML document. XML Parsing error. This parsing error was encountered while parsing the character data. No such object in the parsed XML stream. This parsing error is returned because no such XML object exists in the object list. EXTERNAL qualification contains a circular reference. This error is returned because an EXTERNAL qualification making a reference to itself is an illegal operation. The process stops and an error message is returned. Invalid license key. Please provide a valid license key. You were unable to create a license because the license key does not match the generated key based on the license information provided. The value for the session configuration option is not a valid value You were unable to set a valid public API session variable. This error can only be encountered through an API program. The value of the enumerated value style is not a valid value. This error is returned because there is an invalid value for an enumerated data type. Duplicate numeric values specified for a custom style enumerated value. The values must be unique for each choice. This error is returned because there were duplicate values in a custom style enumerated data type. Make sure all choices are unique.
The Status field cannot be a query style enumerated value. This error is returned because the Status History field of a Data Dictionary style character menu cannot be expanded as a query style enumerated value. An invalid XML document type was specified. The XML document was unable to be parsed by the server because you specified an invalid XML document type. Unable to load the arxmlutil library. This error is returned because the server failed to load the AR System XML shared library. The name of the library is arxmlutil. A failure occurred while trying to open the file. While attempting 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.
XML import and export is not supported. This error message is returned because XML import and export is not supported for this object contained in the file. The requested dateparts is not supported by this operation. This error message is returned because the requested dateparts is not supported by this operation. Either the dateparts value is invalid or this operation does not support the dateparts value. The date format is invalid. You see this error message if 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 (there are not 22 months in a year). The date value is invalid. When converting a ISO or US date string to Julian calendar format, you see this error message if the string contains a date value that is not valid. The XML data type is not supported. The XML data type being converted is not supported by AR System or the XML data type is invalid. Server information data is in an incorrect format. Server information data is not correctly formatted. This error can occur with commands that take as parameters multiple strings separated by semicolons. Required element expected in the input XML document. Verify that the XML input document is correct for the XML mapping document. A required element is missing from the XML input document. Unexpected element encountered in the input XML document. Verify that the XML input document is correct for the XML mapping document. An unexpected element is in the input document. The number of entries exceeds the XML element's maxOccurs value. The number of entries in the list must be equal to or less than the maxOccurs value. The number of entries is less than XML element's minOccurs value. The number of entries in the list must be equal to or greater than the minOccurs value. The default notification mailbox is not specified. No default mailbox has been configured so no default mailbox is available for the email notification. Required XML element is missing from the XML mapping. The format of the XML mapping document is incorrect and must be corrected.
8957 Error
225
Required XML attribute is missing from the XML mapping. The format of the XML mapping document is incorrect and must be corrected. Required attribute expected in the input XML document. Verify that the XML input document is correct for the XML mapping document. A required attribute is missing from the XML input document. The distinguishing key is not unique. The key for this entry must be unique in the XML input document. Two forms contain the reserved centralized user preference field -- delete one to continue. The system found two forms containing the reserved centralized user preference field. You must delete one form. Two forms contain the reserved centralized administrator preference field -- delete one to continue. The system found two forms containing the reserved centralized administrator preference field. You must delete one form.
8973 Error 8974 Error 8975 Error 8976 Error 8977 Error 8978 Error 8979 Error 8981 Warning
Two forms contain the reserved centralized file preference field -- delete one to continue. The system found two forms containing the reserved centralized file preference field. You must delete one form. Notify from is over the maximum size allowed for the name. Enter from information of 255 bytes or less for the email notification message. Notify replyto is over the maximum size allowed for the name. Enter reply to information of 255 bytes or less for the email notification message. Notify cc is over the maximum size allowed for the name. Enter CC information of 255 bytes or less for the email notification message. Notify bcc name is over the maximum size allowed for the name. Enter BCC information of 255 bytes or less for the email notification message. Notify organization name is over the maximum size allowed for the name. Enter organization information of 255 bytes or less for the email notification message. Notify mailboxname name is over the maximum size allowed for the name. Enter mailbox name information of 255 bytes or less for the email notification message. Setting application owner is disallowed. The application owner object property cannot be set.
8982 Error
Object is already owned by another application. This object has an application owner and cannot be added to this application. You must remove this object from the application that currently owns it before you can add it to this application. Changing the data type of the field is not allowed. 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. Group permissions have been removed from the object because the object is in a deployable application. A deployable application cannot have group permissions. Roles permissions have been removed from the object because the object is not in a deployable application. An object that is not in a deployable application cannot have role permissions. The alias for this object is not unique. It will be set to empty string. The web alias names for applications, forms, and views must be unique. The web alias names for views must be unique within all views for the form. Unrecognized option value for change field action. Please refer to manual for valid values for this option. 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.
8983 Error 8984 Warning 8985 Warning 8986 Warning 8987 Error
Archive information could not be set for this form. Please check the error log for errors. Archive information cannot be added to the form because of an internal error. Check the server error log for the cause of the problem. Cannot delete data fields from Archive form. An attempt was made to delete data fields (field type 1 to 14) from an archive form. To delete a field, clear the Enable option in the source form to disable archiving for the form. Cannot modify LimitInfo or Permission for a data field in an Archive form. These values will be made NULL before setting. This warning is returned when the LimitInfo or Permission property for a field that takes data (field type 1 to 14) in an archive form is modified. The system sets these properties to NULL before setting them. Set these values to NULL to avoid getting the warning message.
8991 Error
Both the source form and the Archive form go together in an Application. Removing or adding one of them is not possible. You cannot add or remove only the source form or only the associated archive form from an application. The source form and a corresponding archive form must be removed from an application together, or added to an application together.
227
8992 Error
Could not create the Archive Form specified. Archive for this form has been disabled. Please check the error log for errors. This warning is returned if an archive form cannot be created for a source form because of a lack of memory or a database error. The create or set on the source form will complete but archive will be disabled.
8993 Error
If any of the Copy options are chosen, form name should be present. The Archive Type selected is Copy To Archive And Delete From Source or the Delete From Source, but the archive form name has not been specified. Enter a form name in the Archive To Form field. Cannot create this field in Archive Form. If this is a main form, then a field with that field id exists in the Archive form and archive will be disabled. If this is an Archive form then fields of this type cannot be created. When a field is created in the source form, AR System attempts to create the same field in the corresponding archive form. This error is returned if another field with the same field ID but a different data type already exists in the archive form. Either create the field with the same ID and data type in the source form or clear the Enable option for archive on the source form. Data fields, such as fields with data type AR_DATA_TYPE_KEYWORD(1) to AR_DATA_TYPE_TIME_OF_DAY(14), cannot be created in an archive form.
8994 Error
8995 Error
Archive Type does not match the remaining archive information passed in. If archiveType is not one of the valid archive types or archiveType is AR_ARCHIVE_NONE, all the 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. Archive not possible on Dialog or Archive forms. For Vendor forms, only 'Copy to Archive' option is available. Forms with a Dialog or Archive form type cannot be archived. Only the Copy to Archive archive type is available for Vendor type forms.
8996 Error
8997 Error
Turn off the archive to this form in order to delete this form. If an archive form is being deleted and its source form has archive enabled, either disable archive on the source form or, if you are using the ARDeleteSchema API call, use the AR_SCHEMA_ARCHIVE_DELETE option. Cannot modify or create entries in an Archive form. You cannot create or modify existing entries in an archive form. If you are using the MergeEntry API call, entries can be added to the archive form, but existing entries cannot be overwritten or modified. Also, filters (Push field or Set field) cannot modify or create entries in an archive form.
8998 Error
8999 Error
The Archive form is invalid. Archive form should not be in use and it's data fields should match those in the main form. Please check the manual for requirements for a valid Archive form. The error is returned if an existing form that is not a valid archive form is specified as an archive form. Correct the archive form or specify the name of a form that does exist and AR System will automatically create a valid archive form. For more information about archive forms, see the Configuring AR System guide.
Encryption is disallowed by the AR System server. This error is returned because the RPC call failed and AR System server does not support encryption. Encryption is required by the AR System server. This error is returned because 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. Data encryption key exchanged failed. The actual key exchange between the client and the server failed due to a serious error by one or both of the RPC calls. Error during public key data decryption. Public key decryption failed due to no authentication between client and server. Error during symmetric key data decryption. The MAC (message authentication code) failed during the decryption routine, when comparing the MAC in the decrypted message against the locally generated MAC. An error occurred in the encryption library. There was a failure in generating the random number used during the encryption routine. Unrecognized encryption algorithm. This error is returned because an unknown encryption algorithm was used. XDR sizeof error during XDR encoding. This error is returned because the size of the memory buffer used in XDR (external data representation) is invalid. XDR xres error during XDR encoding. This error is returned because the XDR (external data representation) process was unable to present the result pointer into the memory buffer.
229
9009 Error
Client/server encryption is enabled but the encryption library was not found. Either install the encryption library or disable client/server encryption. This error is returned because encryption is required but the encryption shared library is not loaded.
The encryption library was not found and cannot be loaded. This error is returned because encryption is turned on but the required encryption shared library DLL could not be found or loaded. Loading of encryption library failed. This error is returned because the encryption shared library DLL could not be successfully loaded. Encryption is not licensed on the AR System server. This error is returned if no encryption licensing is present on the AR System server. The encryption license does not match the encryption library. This error is returned if no encryption licensing is invalid on the AR System server. Localization has been turned on but no Message Catalog exists. This error is returned because the Localize Server check box has been selected in the Advanced tab of the Server Information dialog box, yet no AR System Message Catalog form can be found on the server. There may be several reasons why you see this error: The form itself may have been accidentally deleted. A field on the Message Catalog form may have been deleted. Corrupt data may have been added. To continue, make sure the form exists. If it does not, stop and start the server. The form will be automatically recreated at system startup. If for some reason the form itself has become corrupted, you may 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 recreated at system startup.
9051 Error
Multiple Message Catalogs exist. There must only be one Message Catalog. This error is returned because 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. The VUI is not unique for the form. The label, locale, and platform properties of this VUI must be unique to the form. For localization purposes, VUIs for a form must be unique. To continue, create a unique VUI combination of label, locale, and platform.
9052 Error
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. This warning is returned because the default admin view of the form was not found during the import operation. Instead, the previously existing default admin view will be used.
9054 Warning
The specified field does not exist in the form. This warning is returned because 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 will not be imported, and the import process will continue. The VUI import file is in an incorrect format. This error is returned because no VUI definition from the file was retrieved during the import operation. For some reason, the format of the import file has been corrupted so that it contains no VUI information. The server is not localized. 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:
9055 Error
9056 Error
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 has been cleared in the Advanced tab of the Server Information dialog box.
To continue, make sure the Message Catalog Form exists, that its contents have not been corrupted, and that the Localize Server check box has been selected in the Advanced tab of the Server Information dialog box. 9057 Error 9058 Error 9059 Error 9060 Error 9061 Error Recursion of localized queries are not allowed. This error is returned because a query cannot retrieve more than one localized value of a message at a time. Update of Localized Active Link or Menu failed. This error is returned because the timestamp of the localized active link or menu was unable to be updated. The join form contains a circular reference. Fix the join form definition. Unable to create the Unicode Converter. A system error prevented the Unicode converter from being opened. Error encountered during string conversion to Unicode. Character data could not be converted to Unicode format.
231
Error encountered during string conversion from Unicode. Character data could not be converted from Unicode format. Error encountered during creation of the Server Schema form. On server startup, if the server events or server statistics form does not exist, the server will create them. The server encountered an error while attempting to create these forms and failed to create them. You may also see this warning when starting the server if you simply replace the server executable or do not overwrite the database on install. This is merely a warning and the server still starts okay. To get rid of this warning, delete the Server Events and Server Statistics forms. The next time you restart the server, these forms will be automatically recreated and the error will go away.
Cannot find the Server Events form. While server event recording was enabled, the server was unable to find the Server Events form to record an entry. Only one form can contain the Server Events fields. 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 already exists, the server will not allow creation of the new form. Cannot find the Server Statistics form. While server statistics recording was enabled, the AR System server was unable to find the Server Statistics form to record an entry. The form might have been deleted or there might have been a system failure. Restart the AR System server and form will be recreated automatically. Only one form can contain the Server Statistics fields. 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 already exists, AR System will not allow creation of the new form. Only one form can contain the Application Statistics fields. 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 already exists, AR System will not allow creation of the new form. Cannot find the Application Statistics form. While application statistics recording was enabled, the AR System server was unable to find the Application Statistics form to record an entry. The form might have been deleted or there might have been a system failure. Restart the AR System server and the form will be recreated automatically.
9078 Error
9079 Error
9080 Error
9081 Error
9082 Error
Only one form can contain the Application Statistics Configuration fields. 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 already exists, AR System will not allow creation of the new form. Cannot find the Application Statistics Configuration form. The AR System server was unable to find the Application Statistics Configuration form. The form might have been deleted or there might have been a system failure. Restart the AR System server and the form will be recreated automatically. User is currently connected from another machine. A user cannot log on to AR System from two computers at the same time. Host IP address not found. The AR System server did not find the client IP address in the API call. Contact Remedy Customer Support. The file specified for an application does not hold an application definition. The import file does not hold an application definition. User data is corrupted. User information in an internal database table is damaged or corrupted. Contact Remedy Customer Support. Cannot change license type of a user to Fixed more than 3 times in 1 week. An attempt has been made to change the license type of a user to fixed more than three times within one week. Obtain additional fixed licenses if necessary. User data is corrupted. License deleted. User information is being updated and information for the user is damaged or corrupted. The user license is deleted by the system. Contact Remedy Customer Support. User is currently connected from another machine. A user cannot log on to AR System from two computers at the same time. You have the option of terminating the connection to AR System from the other computer. Subadministrator group permissions have been removed from the object because the object is in a deployable application. A deployable application cannot have subadministrator group permissions. Subadministrator roles permissions have been removed from the object because the object is not in a deployable application. An object that is not in a deployable application cannot have subadministrator role permissions.
9083 Error
9084 Error 9085 Error 9088 Error 9089 Error 9090 Error 9091 Error 9093 Error 9094 Warning 9095 Warning
233
9096 Warning
Value specified for the Authentication Chaining Mode is outside the valid range of 0, 1, 2. This warning occurs when the authentication chaining mode parameter is set outside the valid range in the AR System configuration file. For more information, see the Configuring AR System guide. The command does not occur on the local server. This error is returned due to a non-local server execution error during the following operations: Executing a run process command on the server Retrieving a list of SQL values specified in the SQL command
9100 Error
9101 Error
The command is not a server-side command. This error is returned during import and export operations, because the direct SQL and run process commands are valid only as a server-side process, not as the client-side. In certain cases, the process will be exported as a client-side process. Error in parsing the Run Process or Direct SQL command. There was an error returning the fully substituted command from the database, for example, an invalid server-side run process command. To continue, verify if the SQL command or run process command works from a command line. Server does not have a valid host id. Please correct this error to enable licensing for this server. 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.
9102 Error
9110 Error
Error encountered while executing a Web Service. This error message is generated by the Web Service plug-in whenever an error occurs during the execution of a Web Service. Error while opening the armonitor lock file. This error occurs because 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) User has no access permission to <name_of_object>. You attempted to perform an operation (for example, opening a form) to which you have no permissions. Check with your administrator. Session is invalid or has timed out. Please reload page to log in again. Your session is no longer available, either because the session is invalid, has timed-out, or no session data was retrieved. Log in again to continue.
9202 Error
There are no available attachment fields. You attempted to attach an object to an attachment pool in which no fields are left available, for example, because all the fields are in use. Remove any un-necessary attachments if you have permissions, or ask your AR System administrator to add more attachment fields to the attachment pool. The form action request failed. There was an error in one of the form actions, for example, Submit, Search, Modify, or Delete Entry. Please select an attachment file first. You attempted a display, save, or delete operation but did not first select an attachment. No help available. A failure occurred while trying to retrieve Help text for this form or field. An associated error message provides details of the failure. Cannot get the fields in the form. A failure occurred while retrieving the list of fields that contain Help text. Illegal request parameter. You entered a set of incorrect parameters for this operation, for example, an invalid qualification statement. This is an unexpected error. Failed to get config property. A failure occurred in retrieving a property from the configuration properties file. Cannot find an empty attachment field large enough to hold this attachment. There is no field large enough in the attachment pool 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. The file size exceeds the maximum size allowed for this attachment field. You attempted 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. You have to specify a file to upload. You attempted to attach a file to an attachment field but did not enter a file name. To complete this process, enter or select a file. Failed to add attachment. The operation of adding an attachment file failed. Check your permissions. If that does not solve your problem, contact your AR System administrator.
9210 Error
235
Servlet does not support the doGet() method. There was a failure in loading the attachment file because the method attribute of the <form> tag in the servlet request was set to GET, not POST. The file does not exist or is empty. The operation of saving the attachment file to disk failed, either because the file does not exist or its value is NULL. Make sure that the file exists. Internal error. This all-purpose error occurs under a multitude of internal system failures, including the following: Name of a system object or field ID is NULL when trying 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 Error
Display or save attachment failed. Invalid request parameters. There was a failure in viewing or saving an attachment file, for example, a new window could not be opened to display the file. This error occurred here because the request parameters for the file were invalid, because the file path was NULL, or you did not enter a file path name. File not found. Either the file requested is not present or the URL supplied is bad. There was a failure in viewing or saving an attachment file because the file could not be found on the web server. Contact your administrator. Problem sending file. There was a problem viewing the file because, even though the system located the file, it was unable to be sent. There is no attachment file to delete. There was a failure to delete an attachment file because it could not be located on the web server. Make sure that the file exists. There is no attachment file to display. There was a failure displaying the attachment file in a new window because it could not be located on the web server. Make sure that the file exists. There is no attachment file to save. There was a failure saving the attachment file to the clients local file system because it could not be located on the web server. Make sure that the file exists.
Download attachment failed. There was a failure downloading the attachment file because it could not be located either on the web server or AR System server. Make sure that the file exists. Cannot convert AR System query into a Crystal query: no fieldname to match with NULL value. Please see your administrator. A valid AR System query that uses a $NULL$ value must be either in a field = $NULL$ or 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 Error
Crystal Report does not allow } in fieldname. Remove this character from the fieldname. An illegal field name not allowed by Crystal Reports was encountered when converting a AR System query into a Crystal Report web query. Rename AR System field so that it does not use a close brace, then attempt the conversion again. Cannot convert AR System query into a Crystal query: character value in QualifierInfo object is NULL. Please see your administrator. There was a failure during conversion because the field value is NULL and the field name is incorrect.
9225 Error
9226 Error
Cannot convert AR System query into a Crystal query: bad enum field type. Please see your administrator. There was a failure during conversion because the field for which an enum value was provided is not an enum field type.
9227 Error
Query conversion failure unknown: <name_of_query>. Try again or rewrite your AR System query in another way. There was a failure in converting the AR System query into a Crystal Report web query, but the specific reason for the failure is unknown. To continue, rewrite the AR System query into a format more easily understood by the Crystal Report engine.
9228 Error
Unsupported syntax in query conversion. Try to rewrite your AR System query in another way. There was a failure in converting the AR System query into a Crystal Report web query because of unsupported syntax. To continue, rewrite the AR System query into a format more easily understood by the Crystal Report engine.
9229 Error
Cannot convert AR System query into a Crystal query: invalid data type for enum value. Please see your administrator. 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 Error
Report filespec location not specified for native reports. Please see your administrator. The native report output failed because the file location was not specified.
237
9231 Error
Invalid AR System report definition. Re-attach the definition and try again or create a new report. The native report output failed because of an invalid report definition. To continue, try creating a different definition file or re-designing your report.
9233 Error
Field has no info in AR System report definition. 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 re-designing your report.
9234 Error
Cannot display AR System report <name_of_report>. Please try again or see your administrator. The native report failed to appear on your browser for unknown reasons. To continue, see the remainder of the message.
Bad report operation for AR System reports. Please see your administrator. An invalid operation was specified for a AR System report. See your administrator. Cannot open AR System report file <name_of_file>. Please try again or see your administrator. 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 Error
Problem in parsing AR System report definition: no 'Report: ' string found. Re-attach the definition and try again or create a new report. The report operation was unable to parse the field attributes in the definition file. To continue, try creating a different definition file or re-designing your report.
9238 Error
Cannot parse AR System report definition. Re-attach the definition and try again or create a new report. The report operation was unable to 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 re-designing your report.
Cannot decode URL. The URL supplied is invalid. Please see your administrator. The location (URL) of the native report cannot be decoded. Contact your AR System administrator. Cannot create report directory <name_of_directory>. Please see your administrator. Check the name of the configured report directory and try again. Bad data type for report attachment field. Please try again or see your administrator. There was a failure when extracting the report due to an invalid data type for the attachment field. Ask your administrator to check the report form definition.
9243 Error
No attachment info for report attachment. Please try again or see your administrator. There was a failure when extracting the report 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. No filename for report attachment. Please see your administrator. There was a failure when extracting the report 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. No base directory specified for reporting. Please see your administrator. There was a failure extracting the report definition file because no session-specific report directory could be retrieved from the configuration. To continue, use the Remedy Configuration Tool to specify a report directory. Cannot find report <name_of_report> of type <type_of_report> for form <name_of_form> on server <name_of_server>. Please see your administrator. There was a failure to retrieve the report when querying the Report form 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.
9244 Error
9245 Error
9246 Error
9247 Error
Cannot find report type <type_of_report>. Please see your administrator. There was a failure to retrieve the report type when querying the Report form 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. Internal error: Bad data type for query class field. Please see your administrator. There was an invalid data type for the query class field when converting the query string from the AR System native format into the report engines format. Cannot load query converter class <type_of_class>. Please try again or see your administrator. There was a failure to load the query converter class when converting the query string 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 Error
Invalid report operation. This operation is no longer supported. When creating a report 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. Bad data type for report operation command field. Please see your administrator. An inappropriate command was issued for the report because of an invalid data type. To continue, check the report type form definition.
9251 Error
239
Report operation command is empty. Please see your administrator. There was a failure because the report operation command does not have a command specified for this report type. ARServer <name_of_server> does not have form with ID <number_of_ID>. Please see your administrator. There was a failure because AR System server failed to retrieve the form with the specified ID needed to create the report.
9254 Error
Security violation in creating directory <name_of_directory>: <name_of_directory>. Please see your administrator. There were permissions problems in creating a report directory. To continue, verify that the mid tier has write access to this directory.
9255 Error
Cannot instantiate query converter class <name_of_class>. Please see your administrator. There was a failure to create an instance of the query convertor class when converting the query string 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. Problem with starting query conversion: <contents_of_string>. Please see your administrator. There was an initial failure when converting the original query string 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 AR System Java API documentation in HTML format.
9256 Error
Problem opening output stream: <contents_of_string> Please see your administrator. There was a failure creating the report definition file from the Message Catalog. No such object(s) in AR System server. There was a failure locating this object (for example, a schema, active link, or container) in the server cache. To continue, verify that the object exists on AR System server. Report configuration property <name_of_object> not found. Please see your administrator. There was a failure retrieving the configuration object and the report configuration property for this specific session. Error generating Status History information. There was a failure creating the XML string containing the Status History field information. Status history is displayed for the web in a separate window. Submit failed. The Submit operation failed when creating an AR System request. There are many possible causes for a Submit failure, for example, a required field is left blank. In this particular case, enter a value for the required field and re-try the Submit operation.
9263 Error
Modify failed. 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. User has no access permission to the form <name_of_form>. You entered an incorrect user name or attempted to access an AR System form that you have no permissions to. Try re-entering your user name or check your permissions to continue. User has no access permission to the field <name_of_field>. You attempted to access a field that you have no permissions to. Check your permissions to continue. Please select an entry first. There was a failure displaying the status history in a new window because no entry was selected. The request was therefore ignored. Required parameter(s) missing in Direct Access: <name_of_parameter> There was a failure in creating the form view because the required parameters either contain no value or a NULL value. Required parameters include the following: Form (or form alias) Server name
9268 Error
Problem opening form in Direct Access. There was a failure retrieving the path of the JSP page that represents the form. The JSP path could not be constructed because some of the following data is missing: Form View Application Locale
9269 Error
Unable to perform query because results list field not found. Please inform your AR System administrator. There was a failure in the query because the result list in the form could not be located. You will also see this error if you were unable to drill down to a record in a table field using an Open Window active link action.
Entry with ID <number_of_ID> does not exist in database. There was a failure to retrieve the request because that entry ID does not exist in the database. You have entered an improperly formatted value for the field. There was a failure to validate the values for this field so that it can be properly formatted.
241
Value does not fall within the limits specified for the field. There was a failure to validate the values for this field because they are out of the acceptable minimum and maximum range limits defined by the administrator. This is a display-only field. There was a failure to add the field to the query bar HTML input element because it is a display-only field. Only fields holding actual database values like, for example, an integer field, are included. Status History operation valid only in modify mode. There was a failure to display the status history because it is valid only in modify mode, not for submit or query. There is no valid web view for this form. You have selected to drill down on a table or to display, 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 where no web view was defined or a form that is located on a AR System server that is pre-5.x. The system cannot open a form on the web that does not have a valid web view. If the server is a 5.x (or later) server, add a web view for the form and you will be able to open it. If the server is pre-5.x, you must upgrade the server to 5.x (or later) and then create a web view for the form before you will be able to open it.
9277 Error
Found more entries than expected during workflow processing. There was a failure because multiple matches were found in the form during a Set Field or Push Field action. All workflow processing is stopped. To continue, configure the workflow in Remedy Administrator for a different multiple match response in AR System, for example, Set Field to $NULL$, or Use First Matching Request. No item matches active link conditions; this operation has been defined so that no match generates an error. There was a failure because no matches were found in the form during a Set Field or Push Field action. All workflow processing is stopped. To continue, configure the workflow in Remedy Administrator for a different multiple match response in AR System, for example, Set Field to $NULL$.
9278 Error
Not a valid license for web tier to access the server: <name_of_server>. A failure occurred because there is no server license for the mid tier. To continue, verify that a valid license exists. Server not present in the configured servers list - <name_of_server>. A failure occurred because the name of the server is not present in the list of valid mid tier servers. To continue, verify that a valid server exists.
Set fields active link running a process failed. There was a failure 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. Failed to create the following menu: <name_of_menu>. There was a failure to expand the query string for a dynamic menu, for example, a search menu. The server was unable to parse the query correctly. An internal error has occurred during workflow processing: <error_message_string>. There was an internal system failure during the execution of this active link. This error is not due, however, to a more common multiple match or no match error. Invalid AR System Server Name. There was a failure during login, because you entered an invalid server name. Not a valid administrator password on the server - <name_of_server>. Please add/modify the password for the server in configuration page. The mid tier administrator password you specified is not recognized. To continue, try reentering your password or contact your AR System administrator for assistance.
Not a valid administrator user on the server - <name_of_server>. There was a failure during login, because the system does not recognize this user name as a valid administrator. To continue, enter a different login name. Cannot convert AR System query into a Crystal query: you cannot use <operator_in_query> to evaluate null. Please rewrite your query. There was a failure converting a AR System query 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 will understand, 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, re-write your query to return fewer requests.
Incorrect login parameters. Web page, user, and/or server name(s) must be provided. There was a login failure because you did not enter certain parameters, for example, form name or user name. To continue, enter the missing parameters. No matching requests (or no permission to requests) for qualification criteria. No matches were found in your qualification. However, processing will continue 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.
243
9297 Error
The query is too complex for the report engine. There was a failure converting a AR System query into a Crystal Report query, because Crystal has a limitation in how many boolean operators can be used in a query. You will also see this message if a list of selected requests contains too many nonconsecutive entry IDs. In this case, the converted query will be replaced by the original AR System query string.
9298 Error
The original table field/results list query will be used. There was a failure converting the AR System query format into the report engines format because the converted query was too complex. The converted query will be replaced by the original AR System query string. 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? There is a conflict because another user and you are retrieving the same request. To continue, do one of the following: Contact the other user (if you know who they are) to avoid overwriting their changes. Cancel your changes. Perform query again, then modify. Save your changes only if you are sure your changes will not destroy important information.
9299 Warning
Error occurred when executing process during an active link. There was a failure in the Run Process active link action because this run process command is not supported. To continue, use a different run process command. CSV, ARExport, and XML formats are not supported for viewing on the web. There was a failure displaying the report in HTML on your browser because CSV, ARExport, and XML are not supported formats. Cannot communicate with less than <version> AR Servers There was a failure retrieving a user from the pool of available users, because a user pool does not work with this version of AR System. Cannot get embedded report. There was a failure retrieving the report file because the ReportServlet used by the Open Window active link action could not create a temporary directory in which to hold the report or extract the report to the directory. You cannot translate the group name in the Group List or Assignee Group Field. The qualification failed because the system was unsuccessful in translating the group names into group IDs.
9305 Error
Attempt to divide by zero (0) in arithmetic operation. 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. Date is out of allowed range of 1970 to 2037 for web client. There was a failure because you entered a value for a date/time field which does not fall in the supported range. To continue, enter a date in the range between 1970 to 2037. Page has been updated. Please Refresh to get the updated page. There was an error because your form is outdated. The form has been recently updated in memory. To continue, click the Refresh button on the page. Show Status History action ignored. Status History field does not exist in form. There was an error displaying the status history in a new window because the Status History field is missing from the form. The request to display the status history will be ignored. Invalid time format. Please enter time in this format: This error message is returned if you enter the wrong time format into the Calendar popup window. You have entered an improperly formatted decimal value for a currency field. This error message is returned because you did not enter a valid currency value on a currency field. For example, you entered 1,00 USD. You have entered an invalid currency type. The specified currency value is a not an allowable currency type. Contact your AR System administrator. You have entered an invalid currency code for a currency field. Using previous valid code. This error message is returned because you did not enter an allowable currency code on a currency field. The mid tier will return the field results based on the last previous valid currency code. The location does not have the required parameter server or webService. When extracting the details about the web service request from the input document, this error message is returned due to the wrong format of the namespace. The location must include the server and the webService parameters. No Web Service named <name_of_web_service> exists in server <name_of_server>. When processing a web service request on the mid tier, this error message is returned because no such web service exists on the server. No operation named <name_of_operation> exists in web service <name_of_web_service>. When processing a web service request on the mid tier, this error message is returned because no such operation was found in the web service.
9329 Error
245
Invalid operation type <name_of_operation_type> specified in web service container. This error message is returned because the mid tier was unable to make the necessary API call due to an invalid operation type that was specified for the web service. The XPATH expression <xpath_expression> is not found in input mapping. A string value was unable to be substituted for the XPATH expression because the mid tier server could not find the corresponding mapping node. Invalid Date Time Value: <date_time_string> This error message is returned because the mid tier was unable to parse the XML date/time string. Invalid URL for accessing WSDL: <requested_URL> The WSDLServlet servlet was unable to generate the WSDL for a requested web service due to an invalid URL. No web service definition found: <name_of_web_service> This error message is returned if a web service is requested but the mid tier cannot locate the web service definition. No authentication information is found: <name_of_server> This error messages is returned because neither authentication information is supplied in the web service request nor anonymous user information is specified in the Remedy Configuration Tool. Data types are not appropriate for arithmetic operation. This error message is returned for active links when there is some arithmetic operation and the two operands cannot be made to match or the arithmetic operation is not supported. For example, you would see this message if you want to add two currency fields and they both have different currency codes, such as USD and CAD, but there are no matching functional currencies to add. Another example would be when you subtract Decimal1 - Decimal2 = Character. If the target field is a character, then only addition is supported (string concatenation). No Preference servers or Configuration Home Page Server. Home Page needs a server. 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 Remedy Configuration Tool are blank. Specify a server in the Remedy Configuration Tool or specify a server for this user in the AR System User Preference form. No servers configured in Configuration. Home Page needs a configured server. No AR System servers have been configured in the Remedy Configuration Tool. Contact your AR System administrator.
9339 Error
9341 Error
9342 Error
9343 Error
No Preference form or ServerSetting Home Page form. Home Page needs a form. 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. Cannot connect to server <server_name> to access Home Page. 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. Home Page cannot connect to any Configuration servers with user name and password. Your user name or password was not accepted by any AR System server configured in the Remedy Configuration Tool. Contact your AR System administrator. Failed to deploy. Make sure the form - <form_name> and the view - <view_name> have an alias name. The form or view does not have an alias name, which is required for viewing the form on the Web. Contact your AR System administrator.
9344 Error
Network protocol/data error when performing data operation. Please contact administrator. An internal error occurred because parameters passed to the back channel were incorrect. Unable to set up data connection, which is preventing the application from working correctly. An internal error occurred during a back channel request from the browser to the mid tier server.
A form definition has been changed, so unable to retrieve data. Please contact administrator. The definition of a form that users have loaded has been changed in such a way that a table on the form cannot be refreshed. The operation cannot be completed because you are being logged out. A user who is logging out tried to make requests to the mid tier. This can occur if a user has opened multiple windows and is trying to do something in one window at almost the same time as logging out in another window. No compatible (standard or web fixed) view for the requested form can be found - unable to display form. 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.
9354 Error
9355 Error
The requested form <form name> cannot be found. The form specified in the URL does not exist.
247
9356 Error
Unsupported locale <locale>. This error occurs if a user tries 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 Developing AR System Applications: Advanced guide. Unsupported timezone <timezone>. This occurs if a user tries 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. Application does not exist on server - <AR_System_server_name>. The application specified in the URL does not exist. ViewFormServlet requires server and form parameters on the URL. 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. The current global field values are too large to be stored. 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. If this size is exceeded this error occurs. A current session exists for a different user - <user name>. Log off the existing session and try again. The view form servlet has been used with user name and password parameters that differ from the ones used to create the current session.
9362 Error
ViewFormServlet no longer supports formalias, viewalias, or appalias parameters. 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.
Action canceled or unable to contact the web server. The action failed because the mid tier is not available or could not be contacted. This error could also occur if the action was canceled by the user while it was being performed. One or more items match active link conditions; this operation has been defined so that any match generates an 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 Error
No rows have been selected for ModifyAll. 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 Error
Active link run process not supported. There was a failure in the Run Process active link action because this run process command was used incorrectly, such as using a run process that does not return a value in a Set Fields action. Data types are not appropriate for relational operation. The data types of the fields used in a relational operation are not consistent with the operations allowed for that operation. See the Developing AR System Applications: Basic guide for information about the allowed data types of operations. Function error in active link (bad function signature). An AR System API function call has been used with an invalid data type. Function not supported. AR System functions (used in assignments) such as CONVERT, ENCRYPT, and DECRYPT are supported only in filter workflow and not in active link workflow. The guide <guide name> is invalid or not owned by any form. 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. The guide <guide name> is invalid for active links. The guide specified (via dynamic workflow) is invalid. With dynamic workflow you can specify guide names from workflow instead of in Remedy Administrator. The definition for the guide specified cannot be found and might be missing from the AR System server. Bad menu. The specified menu is invalid. This error occurs if the browser client requests a non-existent menu. This could be due to an active link change fields action that has changed the menu for a character field. You have entered an improperly formatted value for a real field. 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 try the operation again. You have entered an improperly formatted value for a decimal field. 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 perform the operation again. You entered a nondigit character for a numeric field. 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 try the operation again.
9367 Error
9371 Error
9372 Error
249
9376 Error
Format of date or time value is not recognized. 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 will default to an appropriate value. However, the format of the portion of time that is specified must match the rules for time stamps. Correct the format for the line, and perform the search again. Time is out of allowed range of <number> and <number>. AR System cannot process a time that is out of range. Try again, using a time within the allowed range. The query matched more than the maximum number of entries specified for retrieval. 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 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 Warning 9380 Warning 9500 Warning 9501 Warning 9502 Warning 9503 Warning 9701 Error 9710 Error
The time entered is invalid. Therefore, the popup will be initialized to the current time. Click the icon to the right of the field to select the desired time. The date entered is invalid. Therefore, the popup will be initialized to the current date. Click the icon to the right of the field to select the desired date. Nothing got deployed since the deployed Application is up-to-date. Nothing was changed so nothing was deployed. Cannot retrieve Starting Active Link <active_link_name> in Application <application_name> on server <server_name>. The Entry Point Guide has no starting active link. Contact your AR System administrator. No fields available for the form: <form_name>. This warning message is returned if a form contains no fields. Every view that needs to be deployed should have an alias. All forms and views must have an alias name specified to be able to be deployed on the Web. Problem encountered during creation of a Currency form. This error message is returned if the Currency form does not contain the correct number of required currency fields. Bulk entry transaction already in progress. An attempt was made to initiate a bulk entry transaction when one was already in progress.
No bulk entry transaction is in progress. An attempt was made to end a bulk entry transaction when no transaction was in progress. Invalid action type for end of bulk entry transaction. The action type supplied for ending a bulk entry transaction was not one of the acceptable options. See the C API Reference Guide for the list of acceptable values. Bulk entry transaction has failed due to an error encountered during an individual operation. 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.
Problem encountered with an Email form. This error message is returned if reserved fields are being created on the Email form that already exists on the form with the same field IDs. Couldn't locate the Email form. When sending email to a specified user, this error message is returned if the server cannot find the Email Message, Email Attachments, or Email Association forms. Email attachment mapping structure is invalid. An internal system error has occurred. Contact Remedy Customer Support. Cannot locate mailbox. In an email notification, either there is no default mailbox or the mailbox specified in the notification does not exist. 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 make sure that the Email Engine will work properly <form_name>. The identified form is missing and must be imported if necessary. You do not have application write license. This user does not have an application write license for the application, or a floating license is not available for assigning. Contact your AR System administrator. There are no application fixed licenses of this type for assigning: <license_type>. No additional application fixed license for this type of license is available for assigning. Get more licenses if necessary. An Application fixed license of this type has been assigned to more users than the number of valid licenses you have: <license_type>. No more fixed licenses can be assigned until the number of fixed licenses is greater than the number of users who have been assigned fixed licenses.
251
9853 Note 9854 Note 9855 Note 9856 Error 9857 Error 9858 Error
The following application fixed licenses have been returned to the system: <license_type>. This informational message indicates that a fixed license has been returned to the system and is now available for assigning. The following application fixed licenses have been granted: <license_type>. This informational message indicates that a fixed license has assigned. The following write application token has become available and has been allocated to you -access has been upgraded to write access. This informational message indicates that a floating license has been assigned for your use. There is no such application user fixed license on the system: <license_type>. License information has been entered incorrectly or the fixed license does not exist. Contact Remedy Customer Support. Application or Form already Licensable. Cannot modify or unlicense the Application or Form. You cannot make an application license less restrictive. Contact Remedy Customer Support. The application is not licensed. Make sure that the application is a deployable application, not a local application. For information about local and deployable applications, see the Developing AR System Applications: Basic guide. The license information provided for this form does not match that in owning application. An internal system error has occurred. Contact Remedy Customer Support. The application license format is not valid. License information might have been 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 semi-colon (;). The form is missing application licensing information. An internal system error has occurred. Contact Remedy Customer Support. No free application user floating write license tokens are available. Currently accessing the application form in read-only mode. License will upgrade when one is available. You have read-only access to the application. Try later to see if a floating license becomes available or contact your AR System administrator.
9863 Warning
No license property can be set while creating a form. License properties for a form cannot be set when creating a form. You can set the license properties after the form has been created.
9864 Error
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. A local application cannot be made licensable. For information about local and deployable applications, see the Developing AR System Applications: Basic guide.
The 'Force For Mailbox' has been enabled but no Mailbox has been supplied. If you select Yes in the Force For Mailbox field, you must specify or select a valid mailbox in the Mailbox Name field. The 'Expires' has been enabled but no Expiration Date has been supplied. If you select Yes in the Expires field, you must select a date and time in the Expiration Date field. The 'Force From Email Addresses' has been enabled but no Email Addresses have been supplied. If you select Yes in the Force From Email Addresses field, you must specify an email address in the Email Addresses field.
11004 Error
Mailbox Name is missing and no default Mailbox has been configured. A mailbox name is required. You must specify a mailbox name or request your AR System administrator to set up a default mailbox in the AR System Email Mailbox Configuration form. You are removing the default mailbox. Please specify a new default mailbox. This is a warning that 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. 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. This is a warning that if you delete an associated incoming or outgoing mailbox you will not be able to either send email notifications or reply to email using this mailbox.
11005 Error
11006 Error
Email Action cannot be set to Parse if no Outgoing Mailbox is associated with this mailbox. If you select Parse in the Email Action field on the Advanced Configuration tab, you must select a mailbox in the Associated Mailbox Name field. Outgoing Mailbox configuration does not contain a Server Name. If you selected outgoing for the Mailbox Function, you must specify a server in the Email Server Name/IP field. Incoming Mailbox configuration either does not contain a User Name or Server Name. If you selected incoming for the Mailbox Function, you must specify a server in the Email Server Name/IP field and a user in the Email Server User field.
253
Index
A
AR System Error Messages form 13 AR System Message Catalog form 13 AR System messages help with 13 message catalogs 11 message reporting 10 UNIX server error reporting 10
L
localizing message catalogs 12
M
message catalogs described 11 localizing 12 message not in catalog 12 messages AR System Error Messages form 13 AR System Message Catalog form 13 custom 17 localizing 12 message catalogs 11 messages not in catalog 12 reporting 10 reserved ranges of message numbers 16 syslog daemon on UNIX 10 terminology 8 UNIX server error reporting 10 Windows server error reporting 11
C
catalogs, message on UNIX 11 custom error messages 17
D
display data types 37 documentation, help with error messages 13
E
error message custom 17 defined 8
F
forms AR System Error Messages 13 AR System Message Catalog 13
N
note informational message, defined 8
O
organization of this guide 15
H
help with error messages 13
R
ranges of message numbers 16 reporting, messages by AR System clients 10
Index
255
S
syslog daemon on UNIX 10
T
troubleshooting. See diagnostic messages
U
UNIX message catalogs 11 server error reporting 10 syslog daemon 10
W
warning message, defined 8 Windows, server error reporting 11
256 Index
*47837* *47837* *47837* *47837*

*47837*

Error Messages

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Error Messages

Încărcat de

Drepturi de autor:

Formate disponibile

Action Request System 6.

3 Error Messages Guide

January 2005 Part No: 47837

BMC Software, Inc.

Action Request System 6.3

AR System Error Messages form

Action Request System 6.3

Action Request System documents

PDF and Print PDF and Print PDF and Print

PDF and Print

PDF and Print

Error Messages Guide

Title Action Request System 6.3 Remedy DSO Administrators Guide

Format PDF and Print

Action Request System 6.3 Remedy Flashboards Administrators Guide

PDF and Print

PDF and Print PDF and Print HTML*

Procedures for using Remedy Import. Administrators

Action Request System documents

Action Request System 6.3

Title Remedy Administrator Help

Format Product Help Product Help Product Help

Remedy Alert Help Remedy Configuration Tool Help

Terminology used in error messages

AR System diagnostic messages

AR System diagnostic messages

Action Request System 6.3

Server error reporting in UNIX

10 Chapter 1AR System diagnostic messages

Error Messages Guide

Server error reporting in Windows

Message catalogs in UNIX

/usr/lib/nls/msg/%L/%N /usr/lib/nls/msg/en_US/%N /usr/lib/locale/%L/LC_MESSAGES/%N /usr/lib/locale/%L/LC_MESSAGES/%N

Message catalogs in UNIX

Action Request System 6.3

Message not in catalog

12 Chapter 1AR System diagnostic messages

Error Messages Guide

AR System Error Messages form

Localizing error messages

AR System Error Messages form

Action Request System 6.3

14 Chapter 1AR System diagnostic messages

Action Request System error messages

Action Request System error messages

Action Request System 6.3

Finding AR System error messages

3500 4000 4500

3999 4499 4899

16 Chapter 2Action Request System error messages

Error Messages Guide

Product ARWeb and Remedy Web

7000 8000 9200 9700 11000

7999 9199 9699 9999 11099

Finding AR System error messages

Action Request System 6.3

AR System error messages

18 Chapter 2Action Request System error messages

Error Messages Guide

AR System error messages

Action Request System 6.3

32 Note 33 Error 34 Error

20 Chapter 2Action Request System error messages