Error Messages Guide English[1]

May 25, 2018 | Author: Sandeep Parihar | Category: Database Index, Portable Document Format, Server (Computing), Command Line Interface, Application Programming Interface
Share
Report this link


Comments



Description

Action Request System 5.1 Error Messages Guide PART NO: AR-510-EMG-01 Copyright © 1991-2002 Peregrine Remedy, Inc. All rights reserved. Information contained in this document is proprietary to Peregrine Remedy, Inc., and may be used or disclosed only with written permission from Peregrine Remedy, Inc. This book, or any part thereof, may not be reproduced without the prior written permission of Peregrine Remedy, Inc. This document refers to numerous products by their trade names. In most, if not all, cases these designations are claimed as Trademarks or Registered Trademarks by their respective companies. Remedy, the Remedy Corporation logo and design, Action Request System, and AR System are registered or other trademarks of Peregrine Remedy, Inc., Mountain View, CA, USA. This document and the related software described in this manual are supplied under license or nondisclosure agreement and may be used or copied only in accordance with the terms of the agreement. The information in this document is subject to change without notice and does not represent a commitment on the part of Peregrine Remedy, Inc. Contact Peregrine Customer Support to verify the date of the latest version of this document. The names of companies and individuals used in the sample database and in examples in the manuals are fictitious and are intended to illustrate the use of the software. Any resemblance to actual companies or individuals, whether past or present, is purely coincidental. If you need technical support for this product, or would like to request documentation for a product for which you are licensed, contact Peregrine Customer Support by email at [email protected]. If you have comments or suggestions about this documentation, contact Information Development by email at [email protected]. This edition applies to version 5.1 of the licensed program. U.S. GOVERNMENT RIGHTS. Use, duplication, or disclosure by the Government is subject to Peregrine Remedy, Inc.’s commercial software license(s). If you are the U.S. government, you agree that these written materials are “commercial computer software”-related documentation licensed pursuant to the terms of Peregrine Remedy, Inc.’s commercial computer software license(s) in accordance with 48 C.F.R. 12.212 of the Federal Acquisition Regulations and its successors and 48 C.F.R. 227.7202-1 of the DoD FAR Supplement and its successors. Unpublished rights are reserved under the copyright laws of the United States. Remedy Corporation 1585 Charleston Road, Mountain View, CA 94043 Tel 650.903.5200 Fax 650.903.9001 www.remedy.com Error Messages Guide Table of 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 on UNIX . . . . . . . . . . . . . . . . . . . 10 Server Error Reporting in Windows NT . . . . . . . . . . . . . . . . 11 Message Catalogs in UNIX . . . . . . . . . . . . . . . . . . . . . . . 11 Message Not in Catalog . . . . . . . . . . . . . . . . . . . . . . . 12 Help with Error Messages . . . . . . . . . . . . . . . . . . . . . . . 13 AR System Error Messages Form . . . . . . . . . . . . . . . . . . . 13 Error Message File (UNIX) . . . . . . . . . . . . . . . . . . . . . . 13 Localizing Error Messages . . . . . . . . . . . . . . . . . . . . . . . 14 Chapter 2 Action Request System Error Messages . . . . . . . . . . . . . . . . . 15 Finding AR System Error Messages . . . . . . . . . . . . . . . . . . . 16 Action Request System Error Messages. . . . . . . . . . . . . . . . . . 18 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Contents ! 3 Action Request System 4 " Contents For information about how to install the AR System Error Messages form. Audience This manual is written for administrators and users of AR System. You can also use this form to modify the message contents displayed on the user’s screen. and error messages returned by AR System.Preface This manual contains the complete catalog of error messages for the Action Request System® (AR System®) software product. and to provide helpful notes in the Notes field. AR System Error Messages Form The information contained in this manual is also available through the AR System Error Messages form. refer to Setting Up the AR System Error Messages Form on page 13. warnings. You can use this form to search for notes. Preface ! 5 . to customize the detailed description in the Description field. includes an overview of the data dictionary tables. includes information about other AR System products as well as a comprehensive glossary for the entire AR System documentation set. PDF Server administration topics on Administrators Print and configuring servers and the mid tier. Administrators HTML and variables that integrate with and AR System.1 Action Request System Documents Title and Part Number AR System Concepts Guide AR-510-CG-01 Description Audience Format Print and PDF Overview of AR System architecture and Everyone features with in-depth examples. Optimizing and Troubleshooting Server administration topics and Administrators Print and AR System technical essays related to monitoring PDF and maintaining AR System for the AR-510-OTG-01 purpose of optimizing performance and troubleshooting problems. PDF Administrators Print by and special Programmers order and PDF AR System C API Reference Guide Information about AR System data structures. methods.Action Request System 5. Programmers Procedures for installing and licensing AR System. and OLE AR-510-CAPI-01 support. Advanced procedures for extending and Administrators Print and customizing AR System applications. Developing AR System Applications: Basic AR-510-DABG-01 Developing AR System Applications: Advanced AR-510-DAAG-01 Configuring AR System AR-510-CFG-01 Basic procedures for creating and Administrators Print and modifying an AR System application for PDF tracking data and processes. AR System Database Reference Guide AR-510-DRG-01 AR System Distributed Server Option Administrator’s Guide AR-510-DSOG-01 Database administration topics and rules Administrators Print and related to how AR System interacts with PDF specific databases. Administrators Print and PDF Installing AR System AR-510-IG-01 6 " Preface . AR System Java API Information about Java classes. and PDF maintaining AR System. Server administration and procedures for Administrators Print by implementing a distributed AR System special server environment with the Distributed order and Server Option. API function calls. and using the AR System email engine. online documentation is available in Adobe Acrobat (PDF) format on AR System product installation CDs and/or on the Customer Support web site. New features list. Everyone Procedures for using AR System Import. Audience Format Administrators Print by special order and PDF Administrators Print by and special Programmers order and PDF Everyone Everyone Print only Print and PDF Help menu AR System Error Messages Guide List and expanded descriptions of AR System error messages. Procedures for using AR System Alert. Administrators Help menu Everyone Help Menu AR System Alert Help Unless otherwise noted. Procedures for using AR System Windows User Tool. configuring. open and fixed issues. AR-510-EMG-01 AR System Master Index AR-510-MI-01 AR System Release Notes AR-510-RN-01 AR System Windows User Tool Help AR System Import Help AR System Administrator Help Combined index of all books. international issues. Administrators Help menu Procedures for creating and modifying an AR System application for tracking data and processes.Error Messages Guide Title and Part Number AR System Email Engine Guide AR-510-EEG-01 Description Procedures for installing. compatibility lists. Action Request System Documents ! 7 . Error 8 " Preface . Notes are labeled ARNOTE in AR System. Errors are labeled ARERR in AR System. no action is needed. A purely informational message. the system does not perform the current operation. and errors. Messages include notes. You must correct the cause of this message to perform the attempted operation. but the system continues with normal operation. warnings. A message that warns you of facts you need to know but that are acceptable to the system. Warnings are labeled ARWARN in AR System. You can take action in response to this message.1 Terminology Used in Error Messages MessageText Note Warning The system displays a message in a dialog box that interrupts operations. and the system continues with normal operation. A message that indicates a failure.Action Request System 5. There is also an online version of all of the messages and descriptions available in the Error Messages form. This chapter describes common problems and outlines the process you must follow to resolve each of these problems. the system usually reports one or more error or warning messages. Occasionally. This guide lists and describes these messages.CHAPTER 1 AR System Diagnostic Messages Diagnostic error and warning messages are included with AR System. These messages often provide you with information to determine the cause of a problem. contact your Customer Support Services representative. If you are still unable to resolve a problem or if you encounter a problem that is not covered in this chapter. AR System Administrator) interact with AR System server. you may only see some of these messages with client applications that you create using the AR System API. Because error checking is built into how AR System clients (for example. it may not be clear from the diagnostic messages what you need to do to correct a problem. This chapter covers the following topics: ! ! ! Message Reporting on page 10 Message Catalogs in UNIX on page 11 Help with Error Messages on page 13 AR System Diagnostic Messages ! 9 . When problems occur. err/usr/ar/err. Remove user. they are displayed or recorded. and reset logging by sending a kill -1 signal to the syslogd process to cause it to read its configuration file again.none or include a separate line that explicitly locates user.1 Message Reporting All of the interactive AR System tools (AR System Windows User Tool.conf file.err to one or more locations that you define (for example. all AR System daemon errors are sent to the syslog daemon where.log To activate logging.) 10 "Chapter 1—AR System Diagnostic Messages .err messages and sends them to a target you specify. (See the discussion about log files and debug modes in the Optimizing and Troubleshooting AR System guide.conf file in your operating system reference manuals. Instead.log: ! ! user. For a complete discussion of the syslog process. AR System Alert.Action Request System 5. If a line in syslog. no messages to class user are sent to the target on this line. If a tool fails during startup.conf contains an entry of the form user. For example. and AR System Import) report errors directly to the terminal. the following line specifies that you want all messages delivered to syslog that are of the type user. add a line similar to the preceding line to the /etc/syslog.err. Server Error Reporting on UNIX AR System daemons run in the background. 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. specify the console device as /dev/console. to direct all messages to the console. depending on the configuration of your system. the error messages are reported at the command line from which the program was started.none. These daemons are not associated with a terminal and thus cannot report errors to a terminal. AR System Administrator. configure your syslog instance (using syslog. see the discussion about the syslogd process and the syslog.conf) to direct all messages of type user. or direct all messages to a file by specifying a complete path name). To receive these messages.log filed in the <ar_install_dir>/db directory. All errors are also written to the file arerror.err written to the file /usr/ar/err. For example. (All messages returned by Windows and Windows NT processes are compiled into the software and are not stored in an accessible catalog. %N specifies the name of the message catalog.Error Messages Guide Server Error Reporting in Windows NT In Windows NT.cat Message Catalogs in UNIX ! 11 . To review the contents of the event log. open the group for Administrative Tools. By default. All errors are also written to the arerror. (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. the syntax for specifying AR System message catalog location (assuming the default language environment) on Solaris is: /usr/lib/locale/C/LC_MESSAGES/arsystem.) This catalog is named arsystem. Click on Event Viewer. which opens up the Event Viewer Application Log window.log file in the <ar_install_dir>\db directory. 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).cat for Action Request System messages. messages are sent to an event log. The installation process establishes a symbolic link in the default message catalog area to the catalogs installed by the system. AR System messages have the Source column set to Remedy Action Request. Action Request System 5. 12 "Chapter 1—AR System Diagnostic Messages .cat file must be readable by all. You might want to store the catalogs in another location. For example. making it impossible to store a link to the message catalogs. Ensure 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. Ensure that the setting of your LANG environment variable is set to the correct language. if the default catalog directory is read-only. that they are located in the appropriate directory. If you set up symbolic links. The catalog files are located in the locale directory under AR System installation directory (by default. Errors above 10000 are defined by workflow (active links. See the documentation supplied with your operating system for more information about internationalizing message catalogs. In general. this is /usr/ar/locale). filters. messages with numbers below 1000 are from the server. the arsystem. You can unset this variable. a process cannot access the message catalog. 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 ensure that catalogs for other products are still accessible. on Solaris. and that the NLSPATH environment variable is set correctly. Use the NLSPATH environment variable to place the catalogs in a directory other than in the default directory. and escalations) and may come from either the server or the client. Ensure that the message catalogs exist. Message number = <###> message. the directory holding the catalogs is mounted as read-only. while messages 1000 or higher are from the client. Message Not in Catalog Problem Action If you receive the Message not in catalog.1 On some systems. Messages are returned by the server or the client. Also. each end of the link must be readable by all. or you can set it to the default value of C to cause the system to default to using the English language catalog. After installation of AR System.Error Messages Guide Help with Error Messages If you receive an unclear error message that you need help resolving. Help with Error Messages ! 13 . look up the error message for the message number in this file.def (UNIX) 2 Use AR System Import to import server and client error message data from this file: ! ! <ar_install_dir>\arserver\help\errars.arx (Windows) <ar_install_dir>/help/errars. warnings. is available to search online for notes. you must use the following procedure to import both the AR System Error Messages form and the server and client error message data. Setting Up the AR System Error Messages Form 1 An AR System Administrator must use AR System Administrator to import the form definition file from this location: ! ! <ar_install_dir>\arserver\help\remerror. examine the error message file. Error Message File (UNIX) If the message catalog is not available. If the message catalog is not available. AR System Error Messages Form A special resource. and error messages.def (Windows) <ar_install_dir>/help/remerror. This file contains a listing of all of the error numbers and their associated message text. the AR System Error Messages form. documentation is available in several places to help with the message. This file is named errors and is stored in the help directory under AR System installation directory (by default. this is /usr/ar/help/errors).arx (UNIX) The AR System Error Messages form is now ready for use. Because these error messages can now be modified for localization. but the text may not match exactly. 14 "Chapter 1—AR System Diagnostic Messages . The use of this form can be enabled or disabled. and other text strings displayed to users in applications that are customized by locale. the message text a user sees may not match the text in the Action Request System Error Messages Guide if the message has been overridden in the AR System Message Catalog form. For more information. in the 5. the AR System Message Catalog form is provided to enable administrators to provide localized versions of error messages.x versions of AR System.cat in UNIX) enabled administrators to “localize” AR System messages.x release. the message catalogs (for example. However. You can use this form in both UNIX and Windows NT environments. The meaning of the message will still be the same. help text. refer to the Developing AR System Applications: Basic guide.1 Localizing Error Messages In pre-5. arsystem.Action Request System 5. menus. 1. Now you can look up any error message quickly by simply turning to the number in its sequence. wondering whether the error message belongs to the server or client chapters. rather than having to flip through multiple chapters.CHAPTER 2 Action Request System Error Messages In the 5. Action Request System Error Messages ! 15 . this chapter consists of one very large table that contains all the error messages in their numerical order for the client. You should find this 5. server.x release of AR System.x reference guide much easier to use than previous editions of the Action Request System Error Messages Guide.1. and mid tier components of AR System. and Notes 3000 3300 3350 3380 3199 3349 3379 3499 3500 4000 3999 4499 ARWeb AR System Import client (Windows) 16 "Chapter 2—Action Request System Error Messages .) AR System Import Errors. Warnings.) ARWeb Errors. Warnings. and Notes (Not documented in this guide. Start 1 1000 1800 2000 End 999 1799 1999 2999 Product AR System Server AR System Windows User Tool AR System Windows User Tool AR System Administrator client (Windows) AR System Server AR System Server AR System Server Discovery Description Server messages and notifications AR System Windows User Tool Errors. The chapter is arranged according to the following general ranges of messages (See the following table). you will need to refer to the appropriate product manual. you should note that error messages for certain Remedy products are not documented in this chapter. It makes no attempt to be backwards-compatible with previous versions of AR System if a feature has become obsolete.1 Finding AR System Error Messages The Action Request System Error Messages Guide documents only those error messages used in the 5.1. for example. Warnings. you will need to refer to the documentation in that suite of products. For example. administrator commands. and Notes AR System Windows User Tool for Windows errors AR System Administrator Errors and Warnings Distributed Server Option messages Alert Event Messages Report ARDBC Plug-In Messages Discovery Services SMS.x version of AR System. For those.Action Request System 5. However. These exceptions are noted. and Tally messages (Not documented in this guide. to find error messages for the AR System Approval Server. ) Errors for any AR System client.) Not applicable Remedy Web Errors and Warnings (Not documented in this guide. including Approval Server and RAPP services (Not documented in this guide. including AR System Windows User Tool. and Web Tools AR System Administrator Errors and Warnings Server messages Reserved Mid tier infrastructure error messages Server messages 4900 5000 6000 4999 5999 6999 Reserved Remedy Web 4.x AR System Client 7000 7999 AR System Administrator client (Windows) AR System Server Reserved Mid Tier AR System Server 8000 9000 9200 9700 8999 9199 9699 9999 Warning: To ensure future compatibility. do not create custom error messages for your own applications with numbers in these ranges.Error Messages Guide Start 4500 End 4899 Product AR System Application Server Description AR System Applications Server. AR System Administrator. Finding AR System Error Messages ! 17 . 21 AR System server terminated—fatal error encountered. AR System server terminated when a signal or exception was received by the server. Open or write action to the filter or escalation log file resumed successfully. (The tag. Additional actions occurred to access this file. An error occurred while AR System was executing a filter or escalation that runs a process.) There are several possible causes of this problem.1 Action Request System Error Messages 1 Message not in catalog—message number = <message_number>. you can probably restart the server and continue to work. If it is not present in this chapter. indicates that the condition is an error. and the arserverd process is shutting down. If the signal is 15. An associated message provides details about why the process could not be executed. and the file is now accessible and can be written to. the message catalog is not accessible to you. An associated message detailing the reason for the failure appears with this message. If the message catalog is accessible (you are getting most error messages but not this message). ARERR.Action Request System 5. 22 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). The process was killed either accidently or intentionally by a user in your environment. and the text corresponding to that error or warning could not be found. If necessary. Most likely. correct the process definition in the filter or escalation. Failure while trying to run the filter or escalation process. The details about the error are in an associated message. Processing continues. The number following this error is the signal that was received. and ARNOTE indicates a note. The server for AR System (arserverd) was terminated by a signal. A generic message indicates that the error was fatal. contact your Remedy Customer Support Services representative. Refer to the discussion of message catalogs in the Configuring AR System guide for details on how to correct this problem. A fatal error occurred within the arserverd process. 20 23 24 18 "Chapter 2—Action Request System Error Messages . Verify that the process definition is correct. but logging to the log file is suspended until the problem is corrected (see Error 23). an event occurred for which there may not be a corresponding error message in your catalog. while ARWARN indicates a warning. Any operations between the message indicating a write failure (Error 22) and this message are not included in the log file. A failure was reported on an open or write action to the log file identified by Error 22. and provide the message number and the circumstances that prompted the message. An error or warning occurred in the system. verify that the sample users were deleted. The demo license for the system on which you are attempting to run the AR System server has expired. This version of the Action Request System has a maximum limit of 2000 requests per database table.Error Messages Guide 25 Fields in set fields action incompatible with form for filter or escalation. You are currently operating with a demo license and the license will expire on the date indicated. Contact your distributor for license information. an authorized reseller. Specify values only for fields that exist in the target form. full text. 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. This version of the Action Request System is ready for use or evaluation without purchasing or activating an authorization key. Previous demo license has expired. 27 28 29 30 31 A fixed <license_type> license was issued for the new user: <x_of_y>. Contact your distributor for information about upgrading your license. For unlimited capabilities. and is configured for each client to access a maximum of one server. full text.remedy. Correct the definition. The <license_type> is replaced by write. The AR System server does not have a license. The system is now running in an unlicensed mode (see Error 27). or flashboards to indicate the type of fixed license.com. You can add the user with a read. see the Configuring AR System guide. To obtain a version of the AR System without these limitations. The AR System server license is a demo license that expires <expiration_date>. to indicate the type of fixed license. You must obtain a license to run AR System server in any mode other than evaluation mode. This system can be used for evaluation but is not allowed for production use. or floating license. You have created a new user who is assigned a fixed license. If you have no more fixed licenses. 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. The filter or escalation being executed is attempting to set values in fields that do not 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. contact your AR System sales representative. none. contact your sales representative or visit www.com. but not a fixed license. You are already at the limit of the number of fixed user licenses of the type <license_type>. The <license_type> is replaced by write. For a more detailed explanation. or flashboards. or visit www. Action Request System Error Messages ! 19 .remedy. Contact your distributor for information about obtaining additional licenses. includes a maximum of three fixed licenses. and the system cannot access one of the debugging trace flags.lck. AR System server (arserverd) expects a different version of the AR System database than the version being referenced. The system continues to run.x. No update to the database occurs. no action is required.390602 for arservftd) for servers on alternate RPC sockets.lck. but the process returned an error message. The associated message provides details about the failure. If there is already a server running in this RPC socket. 38 20 "Chapter 2—Action Request System Error Messages . the lock manager keeps a lock active even when the process holding the lock is no longer running.lck at start-up. AR System server cannot run against an unknown version of AR System database. AR System server (arserverd. and run the server again. 34 35 Another copy of the server is already running on the same RPC socket.Action Request System 5. refer to the message. and ar. You may need to run an upgrade program.lck. These files are used to prevent multiple copies of the AR System processes from being started on a single RPC socket simultaneously.<rpcnum> (ar. Server shut down without problems. Since 5. free the lock by deleting the lock file. At times.1 32 33 AR System server terminated normally.390601 for arservdsd and ar. Error occurred while opening the AR System server lock file. Only one instance of AR System server can be run (on a specific RPC socket) on a machine at one time. If no arserverd process is running. If the server is not running. Correct the problem indicated by the message. An associated file system error message supplies details about the problem. To correct the problem. The error terminates the operation being performed. Start the arserverd process when this file has been removed. but debug tracing to the file is disabled. A filter or escalation was performing a Set Fields action using the option to run a process and return a value. Failure occurred during excel ( ). 36 37 Error occurred while accessing one of the debug trace files. The database is not the expected version. The AR System has failed to start a process. The system debugging mode has been activated. Ensure that your system has no resource problems that prevent new processes from starting. or arservftd) opens a lock file named ar. you have probably encountered a known problem with the NFS lock manager on Sun workstations. Filter or escalation set field process returned an error. and the current transaction is rejected. arservdsd. The text of the message returned is displayed with this error. The error can be due to one of the following reasons: ! 41 42 43 The menu is built from a search against a form that is on a different server. A $MENU$ pattern is specified for a field with a character menu. It can be configured. A character field with a $MENU$ pattern is failing due to errors retrieving the character menu to validate against. Action Request System Error Messages ! 21 . AR System server you are running against has a limited license. Server is not licensed to run with multiple-RPC sockets—ignoring setting and continuing. The filter continued. You cannot use a $MENU$ pattern verification for a remote SQL command. You cannot use a $MENU$ pattern verification for a remote search. The server is configured to run multiple queues. and the file cannot be found. The command line argument displayed on the following line is not a legal command line argument for AR System server. The menu is built from a file.Error Messages Guide 39 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. but the command is encountering an error during retrieval. to be from one to 20 seconds with a default of five seconds. The server restricts access locally to the same server process for performance and consistency reasons. and you are at that limit. Unrecognized command line argument—ignoring command line and continuing. The command line argument is ignored and processing continues. The administrator has control over the time-out setting for the process. You are allowed to create only a specified number of forms. but the search is encountering an error during retrieval. The value for the associated field was not changed. The menu is built using a direct SQL command against another server. The menu is built using direct SQL against a local database. and processing continues. and the operation was performed in the database. ! ! ! ! 44 You are already at the limit of the number of forms allowed for your server license. but you do not have a multiple server license. Remove one or more of the existing forms before you create a new form. The RPC socket setting is being ignored. within AR System Administrator. The server restricts access locally to the same server process for performance and consistency reasons. and the server is encountering an error while building the menu to verify the value against. The menu is built from a search against a local form. You attempted to modify the contents of a core system field (Request ID.Action Request System 5. and use log actions in the action list only. if you want other users to be able to access and manipulate this field. If arserverd receives no response. Only the administrator has access to this field.1 46 Message action and Log action in else branch are not supported for escalations. but all other requested information is retrieved. A client is accessing the server and has specified an invalid identifier for the requested information. No permission information is returned. Last Modified By. A retrieval operation was attempted for the field identified by the indicated ID. The field is accessible only to administrators. but there were no modifications specified. or Status History). Internal error: The request ID for a multipiece RPC response is invalid. You created an escalation and specified one or more message type actions or one or more log actions in the else branch. but there is no field with that ID in the target form. Change the definition to eliminate the message type actions. However. No changes have been specified for the update operation. The data for the correctly identified fields was retrieved. A client is accessing the server and has specified insufficient space for the response to be returned. 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. To prevent the arserverd process from hanging while waiting for the mail system. If the command is being executed programmatically and there is potential for set operations with no changes to be specified. No permission settings have been specified to allow access to other users. You requested permission information about a field. Email notification operation timed out before completion. Escalations do not have a message type action and do not support log or set field in the else branch. It is likely that the mail will be delivered when the mail system recovers. The system was blocked while attempting to send a notification through email. the process disconnects from the mail system and issues this error. You specified a Modify operation to the system. 47 48 49 50 51 52 53 54 22 "Chapter 2—Action Request System Error Messages . This is expected if you are restricting access to the field. This error is reporting an internal RPC failure. The field is a core system field and cannot be changed. Administrator access required to get permission information. this warning can be trapped and ignored within your program. Create Date. Last Modified Date. Field ID specified does not exist in this form. Only a user with administrator access can retrieve permission information. you must assign permissions to the field. the process waits for 20 seconds. These fields are managed by AR System and cannot be changed. ask the administrator to include read access to this field. active links. Because NULL fields contain no meaningful data for the calculation being performed. If you think the login name exists. You attempted to access a field to which you do not have read access for the current AR System request. ask the administrator to add the user as a valid login name to the system. Entry does not exist on form. You attempted to log in with a user name that AR System did not recognize. You attempted to import one or more items (forms. Correct the error. escalations. 56 57 59 60 61 62 Action Request System Error Messages ! 23 . but only as a guest user. AR System allowed you to log in. Enter the login name correctly (including case). You do not have read access to this field. filters. verify spelling and capitalization to continue. If access to this field on this request is required.Error Messages Guide 55 The following item was not imported: <item>. You do not have access to the requested entry. such as when you are the Submitter or Assignee. This error results when you do not have access to the Request ID field (the unique key given to each request in the system). only those fields that contain values that are not NULL are included in the computation. You attempted to retrieve a request that does not exist. or are a member of the Assignee Group of the specific case. User does not exist—successfully connected as a guest user (type user name exactly—including capitalization). The requested statistical operation found one or more NULL values in the fields that were being used for the calculation. One or more fields in the statistic operation had a NULL value. The listed item was not successfully imported. You attempted to access a request to which you do not have access. or character menus) to the current server. You attempted to access a field to which you do not have read access. ask the administrator to extend your permissions to include this field. An associated message indicates why the item was not imported. and try to import the item again. You do not have read access (for this entry) to this field. Those values are excluded from the statistics computation. If this message is received when retrieving an item that was reported in a preceding retrieval. If access to this request is required. the item may have been deleted by another user. If access to this field is required. This message is issued (instead of Warning 60) when you may have access to this field on some requests. ask the administrator to grant access to you. If the login name does not exist. and the specified file could not be accessed. and expand the menu again. Attempt to open menu file failed—character menu is incomplete. An associated message provides details about why the file cannot be created. To use the ARRPC environment variable. You created a filter or escalation action that logs to a file. Only an administrator can change the server settings. To use the default RPC socket. Ask the administrator to restructure the filter definition to refer to a single form.390669 are specialty servers and may have restricted functionality. The new definition allows only a single form link.1 63 One or more values in the statistic operation cannot be retrieved due to access control restrictions.390669. 390619 (the flashboard daemon). 390635 through 390669 (list daemon). The filter is loaded.Action Request System 5. You attempted to perform a statistical operation that included values from fields that you are not allowed to access. Correct the problem. but only with access to the first form in the list of forms. or 390680 through 390694 (private daemon). An associated message contains details about why the file could not be accessed. AR System completed the statistical operation. The environment variable is being ignored. with no menu where the file was to be expanded. NOTE: The value 390603 and the range 390619 . choose Tools > Options > Behaviors. and processing continues. but the inaccessible values were not included in the results. The search matched more than the maximum number of entries specified for retrieval—returned entries are limited to the specified maximum. The action does not perform an operation until the file system error is corrected. The action was created. To change the local setting. The filter definition uses an older syntax in which filters could be linked to multiple forms. The character menu being expanded is incomplete. this value must be 390600 (the admin daemon). If it is necessary that those values be included in the computation. RPC environment variable is out of valid range (390600. the action logs transactions. and the filter is linked only to the first form in the list. Those values are excluded from the statistics computation. and modify the settings for Limit Number of Items Returned. A character menu that references a file was being expanded. The retrieval included a search that selected more than the maximum number of items allowed by the client or server. create multiple filters. 390620 through 390634 (fast daemon). The call returned the number of entries specified as the maximum. The filter or escalation action cannot write to the specified log file—action created but file must be verified. 390680 . 390619 . The value of the ARRPC environment variable is not a legal value. This is an older definition. When the log file is created. If you need filters with the same actions. ask the administrator to extend your permissions to include the fields. 64 65 66 67 68 24 "Chapter 2—Action Request System Error Messages . but the file you specified does not exist and cannot be created.390695). 390603. 390603 (the escalation daemon). clear this variable. The filter definition contains multiple form links. even though the system has a menu defined for it. No floating write license tokens are available. 70 71 72 73 74 75 Action Request System Error Messages ! 25 . It is a pending change until the next restart. The definition of the form and associated fields are complete and in place. You receive this error if you attempt to create an index that contains only the Request ID field. it is present on every form. This number is less than the maximum specified by the server for this call. You are assigned a floating write license. However. The table definition and the structure needed by AR System server is complete and in place. This is correct if you are restricting access to the active link. but there are no floating write license tokens available at this time. This message is a warning about the duplicate. Currently accessing the system in read-only mode. The search matched more than the maximum number of entries specified by the server—returned entries are limited to the specified maximum. Group Access is not defined—only the administrator has access to this active link. One or more fields in this form reference character menus that no longer exist. A value change is pending on the Submitter Mode setting—change will take effect the next time the server is started. but the SQL view is not in place. You can access the form and continue with operation of the system. This error prevented the creation of the SQL view. Operation was completed successfully. You are allowed access to the database for read-only use. The active link is accessible only to Administrators. AR System automatically creates a unique index on the Request ID field. There is no character menu for the field. A change to the Submitter mode setting will not take effect until the AR System is shut down and restarted. No permission settings have been specified to allow access by other users. which is needed only if you are directly accessing the SQL database by using the SQL view. You cannot create duplicate indexes.Error Messages Guide 69 Creation of one of the SQL views for the form failed within the SQL database. but processing has been completed with the index created only once. Although this index does not show in the list of indexes. The only missing information is an SQL view for this form. The retrieval being performed included a search that selected more than the maximum number of items specified by the server. The character menu referenced by one or more fields in this form does not exist. administrators must assign permissions to the active link. A duplicate index has been specified—duplicate was omitted and indexes were created. Only the SQL view for this form is not in place. License will upgrade when a token is available. You specified the same index twice for a form. the system encountered the associated SQL error. if you want other users to be able to perform this active link. While attempting to create the SQL view for this form. The call returned the number of entries specified as the maximum by the server. The system will try to upgrade your license type when a token is available. 26 "Chapter 2—Action Request System Error Messages .Action Request System 5. Some of the DSO reserved fields cannot be changed except by arservdsd. The field is a Distributed Server Option (DSO) reserved field that can be updated only by the DSO process. To prevent an error. The delete operation failed. A field with a length of greater than 255 bytes cannot be used in an index. Full Text Search Option license. and setting all the data values to NULL. You now have full text search (FTS) access within your permissions. A change to the limits definition of a field has been made. You attempted to delete a field from a form. Currently accessing the system without full text search (FTS) capability. The system performed the next closest operation by logically deleting the column. but you were allowed to access the system by using the default database search strategy. The system will try to upgrade your license type when a token is available. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (unlimited). You are assigned a floating. renaming it in the database to avoid naming conflicts. and the details are displayed in an associated message. 77 78 80 81 82 One or more indexes were updated to remove reference to the field—length was changed so that it is not allowed in an index. but there are no floating. Full Text Search Option tokens available at this time. An attempt was made to change one of these reserved fields. the reference to the field that cannot be in an index has been removed from the index definition for the form. A floating.1 76 A write token has become available and has been allocated to you—access has been upgraded to write access. The system will use the default database search capability on all fields. You now have full read and write access within your permissions. A Full Text Search Option license token has become available and has been allocated to you—access has been upgraded to allow full text searching. A floating write token has become available. including the fields that are FTS indexed. License will upgrade when a token is available. Delete column failed—column contents set to NULL and column renamed. and the remaining indexes have been rebuilt. You are allowed access to the database but without access to the full text search (FTS) engine. No free-floating Full Text Search Option license tokens are available. Full Text Search Option license token has become available. You previously received Warning 77 indicating you could not get a Full Text Search Option license token. You have previously received Warning 75. and it has been allocated to you. This field is used in one or more indexes for the current form. and it has been allocated to you. Indexes are ignored for join forms—build the index on the base tables. ! ! If the connection is still unsuccessful after you have eliminated the above causes. the reference to the field that cannot be in the sort list has been removed from the sort list definition. This field is used in the sort list. ensure that the server process (arserverd) is running. define the index on the base form. If there is no network connectivity problem. This protocol error occurs when the client and the server’s protocol definitions do not match.Error Messages Guide 83 The query list fields definition of the form has been updated to remove references to the field—the length was changed so that it is not allowed in the query list. you must solve all network connectivity problems before you can use the AR System server. shut down and restart AR System Windows User Tool. Cannot establish a network connection to the AR System server. 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. To prevent an error. Action Request System Error Messages ! 27 . A change to the limits definition of a field has been made. If it is not running. A field with a length of greater than 255 bytes cannot be used in the sort list. 91 RPC call failed. A field with a length of greater than 255 bytes cannot be used in the results list. This field is used in the list of fields defined to be returned in the results list. The server is inaccessible due to one of the following reasons: ! 84 85 90 There is a connectivity problem with the network. To index a field. If no entry is present in the file or window. You cannot create indexes on a join form. ask AR System administrator to start it. When the network connection problem is corrected. The server may have been temporarily inaccessible. you can successfully connect to the server. If the server is running. the reference to the field that cannot be in the results list has been removed from the results list definition. Issue a ping command to the server. If the problem is with the network connection. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (unlimited). A change to the limits definition of a field has been made. The sort list definition of the forms has been updated to remove reference to the field—the length was changed so that it is not allowed in the sort list. add the entry. The new limits cause the length of the field to be changed from fewer than 256 bytes to 256 bytes or greater (or unlimited). To prevent an error. A time-out occurred while data or structures in the database were being updated. however. Try the operation again. A time-out occurred while information was being retrieved from the data dictionary. Both servers are disabled until the license conflict is resolved. You must license your servers to be able to connect to them at the same time from a single client tool. Make sure the proper sockets libraries are present. Two servers in your environment have been encountered that have the same AR System server ID. Two servers have been encountered with the same AR System server ID—neither will be accessible until one is shut down and the tools started again. The Administrator Command feature is no longer supported. if necessary. You can connect to any number of licensed servers. and try the operation again. Review and. Connection has been attempted to two unlicensed servers. Feature not supported by this AR System client. Its functionality is no longer supported. The operation being performed requires the request ID to be specified. because the server was busy performing other operations. Either you have specified multiple unlicensed servers to connect to or workflow is accessing a second unlicensed server. you may need to reattempt the operation. which enable you to define a running process in which the process runs on the server. but the parameter was not supplied. the operation will still be performed after the time-out. Request ID parameter is empty. Time-out during data retrieval due to busy server—try the operation again. this time specifying the request ID for the entry. In most cases. Time-out during database search—consider using more specific search criteria.Action Request System 5. modify your search criteria. RPC and sockets initialization failure. The Administrator Command feature was removed from the product. Some features cannot be fully mapped from earlier versions of AR System Windows User Tool and AR System Administrator. Try the operation again when there is less activity on the server. The system allows you to connect to a single unlicensed server at any time. 93 94 95 96 97 98 99 100 28 "Chapter 2—Action Request System Error Messages .1 92 Time-out during database update—the operation has been accepted by the server and will usually be completed successfully. You can connect to only one unlicensed server in a session. The attempt to initialize the RPC and sockets subsystems has failed. A time-out occurred while data was being retrieved from the server. This error is often caused by poorly specified search criteria. Connection to the second server is denied. A comparable functionality is available through active links. this parameter cannot be NULL. Statistics list is empty. NULL pointer for result list. Verify that the include file ar. The operation being performed requires a name specification for an item. and try the operation again. Ensure that the file name you specified is a legal name. The name specified was longer than the maximum length allowed (AR_MAX_NAME_SIZE. but no name was specified. The request ID specified for the Request ID parameter was longer than the maximum length allowed (AR_MAX_ENTRYID_SIZE. Name parameter (or name field in a parameter) is empty. The list of requests selected to perform the statistical operation on is NULL or empty. 102 103 104 105 106 107 108 109 Action Request System Error Messages ! 29 . Verify the request ID of the entry. Field or value list item is empty. Remember that character strings must be terminated by a 0 (zero) character. One or more of the fields in the display structure for the field is invalid. File name is longer than maximum allowed file name. Specify a list of one or more operations to be performed. Verify the name of the item.Error Messages Guide 101 Request ID parameter value is longer than the maximum allowed length. 15 characters). and try the operation again. The file name parameter you specified is longer than the maximum file name allowed by the system (AR_MAX_FULL_FILENAME. Field display definition is incorrect.h has legal values for these fields. Request ID list is empty. Specify a list of one or more requests to perform the statistical operation. 255 characters). Remember that character strings must be terminated by a 0 (zero) character. Specify a value for the name parameter. The list of operations to be performed in this statistical operation is NULL or empty. or option. Name parameter (or name field in a parameter) is longer than the maximum allowed length. The parameter meant to hold the data that is the result of this operation is a NULL pointer. label positioning. Remember that character strings must be terminated by a 0 (zero) character. 30 characters). To return the requested data. and try the operation again. You may have specified an illegal display type. 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. Either this parameter has an empty mask or has values outside the allowed limits on the mask. 111 112 Character menu definition is empty. When they are expanded. Verify that the #define statements in the include file ar. one or more of the values was invalid. The command string that issues an external command to the operating system is empty or is too long.096 bytes. Entry error in the name list. A selection field must contain one or more legal values.h have legal values for this field. Verify that the #define statements in the include file ar. filter. Command string is empty or longer than the maximum allowed length. or escalation. the command string may contain parameters. Filter does not have an action defined.h have legal values for this field. If empty.1 110 Unrecognized data type. This parameter is a mask of one or more operations on which the filter will potentially execute. The value you specified for the data type parameter is not one of the legal values recognized by the system. you must supply a command. The filter operation set parameter is invalid. The structure you specified for defining the character menu for a field is either NULL or empty. If too long. Unrecognized data type for default value. If you are defining a character menu. Operation mask parameter is out of bounds. you must reduce the command to the maximum length allowed (AR_MAX_COMMAND_SIZE. During processing of a list of names (such as selection value names). This error relates the associated error to the name list instead of to another parameter in the call. Note that if the command being created is within an active link. In a field operation. the list containing the selection values for a selection type field is NULL or empty. Name list parameter is empty. A filter must define at least one action. 255 characters). 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. 113 114 115 116 117 30 "Chapter 2—Action Request System Error Messages . Verify that the #define statements in the include file ar. The action field for a filter is either NULL or empty. An associated message describes the problem.h have legal values for this field. the command line may expand to 4.Action Request System 5. you must supply a menu definition in this parameter. The unexpanded line is limited by the value defined by AR_MAX_COMMAND_SIZE. Action Request System Error Messages ! 31 .Error Messages Guide 118 Unrecognized value for field option. Entry error in the Request ID list. One of the items specified in the field or value list contains an error.h have a list of all the valid operation codes. Verify that the #define statements in the include file ar. The value you specified for the field option parameter is not one of the legal values recognized by the system. An associated error message contains details about the error. The value you specified for the create mode parameter is not one of the legal values recognized by the system. AR System server is a newer version than your client software. The value you specified for the list of information to retrieve from the server was NULL or empty. Unsupported data type in this client. You specified a code for server information that was not recognized. Install an updated client. An associated error message contains details about the error.h have legal values for this field. Unrecognized server information tag. To retrieve information. Entry error in the statistics list. Unrecognized statistics operation.h have legal values for this field. One of the statistical operation codes is not recognized. you must set the option to AR_FIELD-OPTION_DISPLAY. Verify that the #define statements in the include file ar. and try this request again. ARServerInfoRequestList structure is empty. An associated error message contains details about the error. One of the entries specified in the statistics operation list is invalid. An associated message describes the problem. One of the items in the permission list is invalid. For example. specify what information you are trying to retrieve. Your client is too old to display one or more fields on this form. During processing of a list of request IDs. Verify that the #define statements in the include file ar. This error connects the associated error to the ID list instead of to another parameter in the call. if you create a trim or a control field. Entry error in the field/value list. 119 120 121 122 123 124 125 126 127 Entry error in the permission list. Unrecognized create mode. Verify that the #define statements in the include file ar. one or more of the values was invalid.h have a list of all the valid codes that can be specified. This message can result from a change to the display option—either setting it or removing it—where this is not allowed. To perform a structure operation. For a selection field. and the match operation setting are legal.h have a list of all the allowed notify mechanisms. 133 134 Entry error in the structure item list. Verify that the #define statements in the include file ar.Action Request System 5. Verify that the #define statements in the include file ar. Verify that the #define statements in the include file ar.1 128 Unrecognized permission tag.h have a list of the valid permission tags. Unrecognized filter action type. The structure list parameter is NULL or is an empty list. One of the entries in the character menu is invalid. Unrecognized structure item tag.h have a list of all the filter action type tags. For a character field. One of the permission tags is not recognized. 129 Field limit definition is invalid. 137 32 "Chapter 2—Action Request System Error Messages . An associated error message contains details about the error. ensure that the pattern is within the size limit of the field. Verify that the #define statements in the include file ar. verify that the value is a legal value for the field. Unrecognized character menu item type. you must have a list of the options to get or set. The code specified for the notify mechanism in one of the filter actions is invalid. 135 136 Unrecognized notify mechanism. A child menu tag was assigned but there is no child menu. verify that the specified character menu. Verify that the #define statements in the include file ar. Unrecognized message type. The code for the type of error message to return is invalid. One of the items specified in the structure list is invalid.h have a list of all the valid character menu type tags. ! ! 130 Entry error in the character menu. the menu style setting. ! For a numeric field.h have a list of all the valid structure tags.h have a list of all the valid message types. or a leaf item was specified and there is no leaf string. One of the character menu type tags is not recognized. One of the structure option tags is invalid. 131 132 Structure item is empty. Also. The field limit specified for this field is invalid. ensure that the high range is greater than the low range. Verify that the #define statements in the include file ar. One of the filter action codes is not recognized. Action Request System Error Messages ! 33 . or arithmetic structure is NULL. 139 140 141 142 Unrecognized operation in qualify conditions. which will eliminate the default value and is not allowed. The tag for the relational operation to perform is invalid. Relational operation is empty. Specify a value for a relational operation. Unrecognized arithmetic operation. The core fields of the system have restrictions on what changes are allowed. Verify that the #define statements in the include file ar. Verify that the #define statements in the include file ar. or escalation must be greater than 10000. You are attempting a change to a characteristic of a core or reserved field that cannot be changed in the way you are requesting. The value portion of a relational operator qualification structure is NULL. 146 147 ARFieldValueOrArithOp structure is empty. The value portion of an arithmetic operator qualification structure is NULL.h have a list of all the valid tags. The value portion of a field. Restructure the call to remove the tag from the middle of the tree. Specify information for an arithmetic operation. Can use the Qualify None option only at the top level of a qualification.h have a list of all the valid tags. A default must be active for the Status field. You can alter the number of states and change the default value. The message number of a message you define through the Message action of a filter. This tag is used to indicate no qualification. You are attempting to change the definition of the Status field. or escalation message number must be greater than 10000. Verify that the #define statements in the include file ar. 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 itself. Specify information for this structure. value. but you cannot eliminate it. active link. 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. Unrecognized relational operation. Numbers less than 10000 are reserved for AR System. The tag for one of the nodes in the qualify condition structure is invalid. active link.Error Messages Guide 138 Filter. 143 144 145 Arithmetic operation is empty.h have a list of the valid tags. Review the Developing AR System Applications: Basic guide for information about the restrictions for each of the core fields. Option cannot change for core or reserved field that has a fixed options definition. The tag specified for the arithmetic operation is invalid. The Status field must have a default value. A user name must be supplied in the control record. Supply a value for this parameter. The failure occurred on the client machine during processing of the call to or from the server. Supply a pointer to the input buffer for this parameter. value. An associated error message provides details about the error encountered. The system encountered an error during a call to allocate memory space. Return buffer is NULL. there must be a value specified for this parameter. You can recover that memory space by shutting down unneeded processes. View the #define statements in the include file ar. Supply the name of the server to reference in this field. specifying a field ID that is greater than 100. The name field of the ARControlStruct parameter is empty. 151 Required form parameter is missing. The form parameter is required. The tag for the type of the field.h for a list of the valid codes. The buffer to hold the input value to the call was passed a NULL value. For the call to return the data requested. or arithmetic value is invalid. IDs of less than 100 are reserved for AR System. The buffer that holds the return value of the call was passed a NULL value. 152 153 154 155 156 157 34 "Chapter 2—Action Request System Error Messages . Supply the name of an AR System user in this field. Restart processes that have been running for a while to recover space those applications may have leaked over time. Input buffer is NULL.Action Request System 5. You have specified a field ID of less than 100 for a new field. For this call to perform the requested operation. The server field of the ARControlStruct parameter is empty. You cannot specify IDs in this range for fields you create. Load this parameter with the name of the form you want to reference. but the value passed is either NULL or an empty string. Unrecognized sort method. there must be a parameter specified to hold a pointer to the result. The code for the specified sort method is invalid on one of the entries in the sort list. Field IDs below 100 are reserved for core fields. Entry error in the sort 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. Verify the #define statements in the include file ar. Malloc error in client library. Perform the call again.h for a list of all the valid tags. The value specified for the sort list parameter is invalid. 149 150 A server name must be supplied in the control record.1 148 Unrecognized ARFieldValueOrArithOp structure tag. If there are no items. All other combinations are illegal. 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 length you have specified for the field and the default value prefix leave less than 5 spaces.h for a list of the valid tags. The text you specified is over that limit. You have requested a modification to the length of the Request ID field. Decompression has failed. but the value field in the structure is a NULL pointer. The format of the compressed data was not correct. The notify text you can specify for a notification is limited to 255 characters before expansion. 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. If there are items. ! ! 166 A default value of the same type as the field is always compatible. A keyword value is compatible with the data type that matches the type of the resulting keyword (for example. The session identifier is set in the control record by the ARInitialization() function and is valid until a call to ARTermination() is made. 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. for example. Unrecognized notify field ID tag. the value field must point to the items.Error Messages Guide 158 Request ID field must contain at least 5 non-defaulted spaces. This field is a character string containing from 5 to 15 characters. 12/25/01 is compatible with AR_DATA_TYPE_TIME. when saving an attachment in the Save-Attachment Run Process filter command. There was a failure in decompressing the data being processed. Invalid session identifier supplied in the control record. Character strings must be terminated by a \0 character. 160 161 162 163 165 Items specified are NULL pointers. A default value of AR_DATA_TYPE_NULL is always compatible with any data type. The tag for the notify fields structure is invalid. the numItems field must be initialized to 0. but not with AR_DATA_TYPE_CHAR). ! ! Action Request System Error Messages ! 35 . A parameter has been specified that contains a numItems value that indicates one or more items for the parameter. The session identifier in the control record is invalid. Notify text is empty or too long. View the #define statements in the include file ar. The data type of the default value must be compatible with the data type of the field. If you receive this error. You must correct your text string to 255 characters or less. with items at lower values being performed before items at higher values. Consult the Application Event Log for details concerning any errors that occurred. Status history selection value is out of range for status definition. An error occurred with one of the field or value assignments in the Set Fields action of a filter. The legal range for the execution order is 0 to 1000. All other combinations are illegal. Service was not started. The data type in the limit structure must be compatible with the data type of the field. This could be due to the service being stopped by the administrator prior to completion of its startup tasks or an error occurred that prevented the service from starting. or escalation definition contains a value that is out of range. The tag that specifies whether you want the user name or time stamp for a status history value is not a recognized value. The selection value specified is a 0-based. ! 168 Error in one of the field or value assignments in the set fields action of a filter. It indicates that there is no limit for the field. The status field value you specified does not match a defined status for this form. positional index into the list of states defined for Status. An associated message provides details about the failure. ! ! A default value of the same type as the field is always compatible. Unrecognized status history tag. the problem is an attempt to define an assignment between incompatible data types or to nonexistent fields. active link. The data type specified in the limit for the field does not match the data type defined for the field. or escalation definition. 169 170 171 172 36 "Chapter 2—Action Request System Error Messages . The only supported values for the tag field are AR_STAT_HISTORY_USER and AR_STAT_HISTORY_TIME.1 167 Field limit type and data type do not match.Action Request System 5. The Windows NT Service was not started. A default value of AR_FIELD_LIMIT_NONE is always compatible with any data type. or escalation definition. Execution order value is out of range. The execution order field of the filter. active link. Usually. active link. and the NumRows field specifies the number of rows of data that are displayed for the field. For fields displayed as TYPE_NUMTEXT. You must choose a display type that is appropriate. The length field specifies the width of the control.Error Messages Guide 173 Language specified in the control record not recognized—using default language on server. and the number of rows value is ignored. the length field must not be zero (0). The numRows field specifies how many rows the check boxes or choices must be displayed in. To use the default language. Display type specified is inappropriate for the data type. as shown: Data Type Display Type 174 AR_DATA_TYPE_INTEGER AR_DATA_TYPE_REAL AR_DATA_TYPE_CHAR AR_DATA_TYPE_DIARY AR_DATA_TYPE_ENUM AR_DISPLAY_TYPE_TEXT AR_DISPLAY_TYPE_NUMTEXT AR_DISPLAY_TYPE_TEXT AR_DISPLAY_TYPE_TEXT AR_DISPLAY_TYPE_TEXT AR_DISPLAY_TYPE_TEXT AR_DISPLAY_TYPE_CHECKBOX AR_DISPLAY_TYPE_CHOICE AR_DISPLAY_TYPE_TEXT AR_DATA_TYPE_TIME 175 The length or numRows value of the display parameter is out of range. Action Request System Error Messages ! 37 . neither the length nor NumRows field should be zero (0). You can also set the language to the default language of C to use the standard language defaults. For fields displayed as TYPE_TEXT. If you are running one of AR System tools. For fields displayed as TYPE_CHECKBOX or TYPE_CHOICE. leave the language buffer empty (set to an empty string). the numRows field must not be zero (0). You can set this value to any language your environment supports. and the length value is ignored. The length or numRows (number of rows) value for the display parameter is not within the allowed range. the language field is in the control record that is passed to each call. Verify the setting of that variable and correct it if it is wrong (or delete it if the default language is sufficient). the language to use is picked up from the LANG environment variable. The display type value specified for this field is not compatible for the data type of the field. The length specifies the width of the control. The language you specified for the system is not recognized by the server. If you are coding directly to the API. You have specified that a group must be given change access to a field. You specified a group ID more than once in the permission list you are sending to the system. To assign the ID for a field. [c-a]). Reduce the number of actions by combining several action steps into one or by creating a second filter. or escalation has more actions defined than the maximum allowed by the system (25). The field ID parameter is a NULL pointer. The value specified as the default value for a character field is longer than the maximum allowed by AR_MAX_DEFAULT_SIZE (256 bytes). If you want the system to assign an ID. must be a pointer to memory. active link. and the system will assign a value and return the result in this field. You can assign only view permission to the field for this group. and try the operation again. however. Default value for a character type is longer than the maximum allowed length AR_MAX_DEFAULT_SIZE. Character strings must be terminated by a 0 (zero) character. The system will return the ID assigned. Duplicate group ID was specified in permission list. and separating some of the actions into the new filter. load this parameter with the value. This is likely caused by a programming error. Too many actions have been specified for this filter. Alternatively. It must be a pointer to a field ID. Field ID parameter is NULL. API calls must set that flag to allow the creation of a field with this ID. The ID specified for this field is in the reserved field range. assign this field to 0. Cannot specify change access for a view-only group. Verify the default value. 177 178 179 180 181 182 183 38 "Chapter 2—Action Request System Error Messages . the same name is used for two separate states. Typically. The filter. In the list of selection or bitmask values. Remove the duplicate reference. Rename one of the duplicate selection values so that each selection or bitmask value has a unique label. the group is a View group and cannot be granted change permission. Pattern in a character limit is invalid. Any given ID can be specified only once with the permissions allowed for that group field. or escalation. 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. active link. or escalation. or escalation.1 176 Duplicate selection value exists in the selection or bitmask value list. An API call did not set the flag indicating that it allows creation of fields in this range. The pattern specified for a limit to the character field is not legal. an API call can set the flag to 0 to have the system generate a unique ID.Action Request System 5. active link. The ID for the specified field falls within the reserved range of field IDs. active link. The field or assignment list for an active link Set Fields action is either NULL or empty. One of the active link action codes is not recognized. where the default is used as a prefix to the ID. The active link you have defined has the On Return or On Menu choice condition set in the execute mask. View the #define statements in the include file ar. 185 186 187 188 189 190 191 Unrecognized assign type. An active link must define at least one action to be performed. 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. Execute mask setting requires a field choice. You have assigned a character menu to a system-controlled AR System core field (Request ID. View the #define statements in the include file ar.h for a list of all the active link action type tags. The only system-controlled core field that can have a default value assigned to it is the Request ID field.Error Messages Guide 184 Cannot specify a quotation mark in default value for Request ID field. Cannot assign character menu to system-supported core or reserved fields. The execute mask is a bitmask of the conditions under which an active link will execute. so no default value is needed or allowed. Execute mask parameter is out of bounds. A Set Fields action must define at least one field to be assigned a value. The assign type tag is not recognized. The other AR System system-controlled core fields are automatically updated by the system. Active link does not have an action defined. but there is no setting to indicate to which field to attach the operation. You have assigned a default value to a system-controlled AR System core field (Request ID.h for a list of all the assign type tags. 192 Field or assignment list item is empty. Specify the field where you want to attach the active link action. Unrecognized active link action type. The value you have specified includes bit settings outside the legal range of conditions under which you can execute an active link. Create Date. The action field for an active link is either NULL or empty. The bitmask can be created by totalling the set of defines that represent the conditions under which you want the active link to execute. Modified Date. Last Modified By. Cannot assign default value to system-supported core or reserved fields (except Request ID). or Status History field). Last Modified by. Create Date. or Status History field). so a character menu is not needed or allowed. Action Request System Error Messages ! 39 . The system-controlled core fields cannot be assigned values by the user. Specify a default value that does not contain a quotation mark character. Modified Date. One or more fields. 194 195 Filter. Macro branch of active link action must include both a name and macro text. If there is an arithmetic operation involved or the operation is a complex one. or assignment items in the field or assignment list. or escalation. but the keyword identifier was not recognized. Unrecognized tag for filter. active link. The field definition in the field or assignment structure is set to NULL. or escalation set field action. Therefore. you must provide a name. A keyword type value was specified.Action Request System 5.h for a list of IDs for all supported keywords. whether in an active link. Verify the default value. 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. Supply a field definition value in this structure. the $DEFAULT$ keyword is disallowed within qualifications.1 193 Entry error in the field or assignment list. The ARAssignFieldStruct structure tag is not recognized. or escalation set field definition is missing. active link. When specifying macro parameters. Refer to the related messages for details about the error. Verify the #define statements in the include file ar. A name field in the list of macro parameters is either NULL or blank. 196 197 198 199 Missing or blank name for a macro parameter in the active link action. Macro value string is longer than the maximum length allowed. Character strings must be terminated by a \0 character. supply the parameter name for the value you are specifying. View the #define statements in the include file ar. The keyword $DEFAULT$ cannot be used when specifying the default value for a field. but if they are included on the list. encountered an error.h for a list of all the ARAssignFieldStruct tags. 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 tag for indicating the type of field or value reference is undefined or is not allowed in the current context for the ARFieldValueOrArith structure. it is not clear which field’s default value is being referenced under all conditions. The value specified as the default value for a character field is longer than the maximum allowed by AR_MAX_MACRO_VALUE (255 bytes). 200 201 40 "Chapter 2—Action Request System Error Messages . Unrecognized or misused tag for field/value definition. You can omit parameters from the list of parameters. and try the operation again. or on the qualification bar. The keyword $DEFAULT$ cannot be used when specifying a qualification. Unrecognized keyword. Cannot use the $DEFAULT$ keyword as a default value or in a qualification. filter. Error Messages Guide 202 Notify user name is longer than the maximum size allowed for the name. File name for a character menu is NULL. 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). Value list is empty. where 1 indicates the highest priority and 10 indicates the lowest priority. View the include file ar. The code for the refresh interval for the character menu is not one of the defined choices. Total length of all fields involved in an index is greater than maximum allowed length.h for a list of the valid codes. The value specified for the notification priority is outside the legal bounds for this field. Remove one or more fields from the index definition to reduce the total length of the index information. The name specified for the user to be notified is too long (the maximum is defined by AR_MAX_NAME_SIZE. The value list parameter for this call is NULL or contains 0 items. The file name for a character menu is a pointer to NULL. empty. This operation requires at least one value item to be specified. The code for the location of the file for the character menu is not one of the defined choices. If you receive this error when doing a field operation. Specify a name that is within the length restrictions. Either zero or greater than the maximum number of allowed fields are specified in a single index. 30 bytes). or is longer than the maximum allowed length for a file-name. 208 209 210 211 212 Action Request System Error Messages ! 41 .h for a list of the valid codes. The ARCharMenuStruct structure tag is not recognized. Display list is empty. Define a legal file name for the character menu file. Unrecognized character menu file location. 203 204 206 207 Unrecognized character menu refresh code. Unrecognized character menu type. A field must define at least one display definition. View the include file ar. Specify a value between 1 and 10 for the priority. is an empty string.h for a list of the recognized ARCharMenuStruct tags. or too long. 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. the display list containing information about the display definition for the field is NULL or empty. View the #define statements in the include file ar. Notify priority is out of range (must be 1 to 10). The qualifier parameter must be a pointer to memory. requesting only values that can be retrieved (viewed). The server information for the indicated tag is write-only data. Server information associated with this tag cannot be retrieved. Server information associated with this tag cannot be updated. Try the operation again. Try the operation again. ARServerInfoList structure is empty. the settings with their values must be specified. Query value structure item contains an error. The server information for the indicated tag is read-only data. You are not allowed to update this information. Refer to the associated error message for details. One of the items in the list of field definitions is invalid. One of the structures in the list of fields to display in the query list is invalid.1 213 Qualifier parameter is NULL—must be a pointer to memory.Action Request System 5. See the associated error message for details about the error. This memory location is where the base of the qualifier structure for the string being parsed is stored. The code specified for a local variable is outside the legal range for local variables. Local variable number is out of range (must be 0 to 10). The server information for the indicated tag represents information that has a different data type than the type specified in the update operation. Specify a number between 0 and 10. One or more of the fields in the query definition of an assignment operation contains an error. To define an assignment to a value from another form. Try the operation again. You are not allowed to view this information. Server information data associated with this tag uses an incompatible data type. Query value structure is empty. setting only values that can be updated. To set one or more pieces of server information. The server information list is either NULL or empty. 214 216 217 218 219 220 221 222 223 42 "Chapter 2—Action Request System Error Messages . The query value structure pointer is NULL. This list of field definitions is for fields that are displayed in the query list. 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. specify a query value structure definition that defines the form and conditions on that form. specifying the correct data type for the value. specify a function definition that defines which function is to be performed and that provides the parameters to perform the function. but the count of parameters must be set to 0. Set fields actions that reference entries in other forms can only reference forms on the same server in a filter or escalation. Unrecognized value for set access option characteristic. The tag refers to an operation that is supported only during a filter or active link operation. or a field with a maximum length over 255 bytes.h for a list of the valid codes. A function was defined. the parameter list must contain the parameter values. If the number of items indicates parameters. Unrecognized function code specified. The type of value specified in the ARFieldValueOrArithStruct structure is not allowed within a query list. is not one of the defined choices. or arithmetic operation is not supported on the GetListEntry operation. You have defined a reference to a form on a different server. value. The function structure pointer is NULL. 228 229 230 231 Parameter list for a function is empty. of the Set Fields characteristics action of a filter. perform the operation in an active link) or move the remote form to the server where the filter or escalation is being defined. If there are no parameters. Type of field. an unlimited length field. However. View the #define statements in the include file ar. 225 226 227 Unrecognized value for set focus characteristic. The parameter list for a function is NULL. View the include file ar. If the index is a multiple-field index. You must choose another operation (for example. you can still create the index if you remove the field that is not allowed. the parameter list can be NULL. 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. To define an assignment to a function result. but the function code was not recognized. Action Request System Error Messages ! 43 . The code for the set access option field.Error Messages Guide 224 Cannot index a diary field.h for a list of valid function codes. but the number of items indicates one or more parameters. Function definition is empty. the referenced form must be on the same server.h for a list of the valid codes. Fields that have lengths longer than 255 bytes (including diary fields and unlimited length character fields) cannot be indexed. View the include file ar. You have specified an index that includes a field that meets these criteria. A Set Fields action within a filter or escalation can reference other forms for pulling data to the current request. h for a list of supported codes. View the definition of the function to verify the parameters. In a Set Fields action for a filter. 233 234 235 236 237 238 239 44 "Chapter 2—Action Request System Error Messages . Unrecognized value set for DDE action code. The filter Set Fields process time-out value is not in the legal range. This value must be greater than or equal to 1 hour.Action Request System 5. active link. one of the settings assigned the result of a function. Verify the #define statements in the include file ar. View the #define statements in the include file ar. Verify the value. or escalation. Both of these fields are required. All the types must be the same or compatible types. The DDE service name or topic field of the DDE active link action is missing or is too large. Value specified for the license time-out must be 1 or greater (in hours). The code for the DDE action to perform is not one of the legal codes. The data types of the values in a value set are not compatible. Unrecognized code for user list type. The value specified for the license time-out value was 0 or a negative number. Value for DDE item is larger than the maximum allowed length. The ID of the field that the function is associated with is reported. and correct if necessary. Wrong number of parameters or invalid parameter values specified in function for the field. Value specified for DDE service name or topic is missing or is larger than the maximum allowed length. Try the operation again with the value in this range.1 232 The types of the values in a value set are not compatible. Either the wrong number of parameters was specified or one or more of the parameters is the wrong data type.h for a list of supported codes. Verify the values. The time-out value can be as low as 1 second and as high as 20 seconds. A function definition that was specified has an error with the specified parameters. The value remains unchanged (defaults to 2 if nothing is set). Value specified for the filter or escalation set fields process time-out is outside the valid range of 1 to 20 seconds. and both have an upper limit of 64 bytes. The value specified in the DDE item field is larger than the maximum allowed (32767 bytes). The code for the type of user list to retrieve is not one of the legal codes. and correct them as appropriate. and the Status History field) cannot be specified as sort fields. specify a DDE definition that defines which DDE operation is to be performed and that provides the values to perform the operation. unlimited length character fields. Specify a sort list that does not include this field. Value specified for DDE path to program is missing or is larger than the maximum allowed length. Cannot specify a diary field. a character field with unlimited length (or maximum length over 255 bytes). The format specified for the day portion of the escalation time is not recognized. Fields that have lengths over 255 bytes (including diary fields. unlimited length character fields. Fields that have lengths over 255 bytes (including diary fields. the limit is 254 bytes. The path to the program field of the DDE active link action is missing or is too large.h).h). Review the structure definitions in the include file (ar. or Status History as a sort field. You have specified a list that includes a field that meets these criteria.Error Messages Guide 240 Cannot specify a diary field. and the Status History field) cannot be specified as fields in the list returned by the Get List operation. For DB2 databases. Remove this field from the list.h). Specify a tag that is allowed outside of a filter qualification. or arithmetic operation is supported only for a filter qualification. Invalid escalation interval time. Verify the value. Review the structure definitions in the include file (ar. value. and correct the definition to match the rules defined there. a character field with unlimited length or maximum length over 255 bytes (254 bytes for DB2). Invalid escalation day selection. Type of field. This field is required and has an upper limit of 255 bytes. To define an assignment to a DDE result. and correct the definition to match the rules defined there. Review the structure definitions in the include file (ar. The type of value specified in the ARFieldValueOrArithStruct structure is allowed only within a filter qualification. and correct as appropriate. 241 242 243 DDE definition is empty. The DDE structure pointer is NULL. The format specified for the day portion of the escalation time is not recognized. The format specified for the time portion of the escalation time is not recognized. Invalid escalation day format. 244 246 247 248 Action Request System Error Messages ! 45 . and correct the definition to match the rules defined there. or Status History as a field in a Get List description. You have specified a sort that includes a field that meets these criteria. The format specified for the hour portion of the escalation time is not recognized. and correct the definition to match the rules defined there. Duplicate tag used for several items within the display list. Set the value to True (1) to enable the structure or False (0) to disable it. Subject line is longer than the maximum length allowed. Review the structure definitions in the include file (ar.h). and the import will be completed successfully. Verify the subject line value. The problem is treated as a warning. One or more groups in the list of groups granted Subadministrator access to a form does not exist. Inappropriate group in the Subadministrator group list for the form in import. Unrecognized group in the Subadministrator group list for the form. active link. There are two or more instances where the same display tag is used. You can define groups with the missing IDs. and correct the definition to match the rules defined there.Action Request System 5. Invalid escalation minute selection.h).h for a list of the server statistics tags supported. or you can update the definition of the form to remove the undefined IDs. The operation being performed is an import. 257 46 "Chapter 2—Action Request System Error Messages . View the #define statements in the include file ar. The format specified for the minute portion of the escalation time is not recognized. Unrecognized submitter mode. A display tag to identify the view desired is not unique. Correct the definition to supply unique tags. The group must exist to be assigned Subadministrator access to the form. Review the structure definitions in the include file (ar. View the #define statements in the include file ar. The character strings must be terminated by a 0 (zero) character. The tag specified for the server statistics structure is not recognized. The code specified for the submitter mode is not recognized.1 249 Invalid escalation hour selection. Each display tag must be unique. and try the operation again. One or more groups in the list of groups for the Subadministrator is not a group defined on this system. Invalid value for enabling or disabling a filter.h for a list of the submitter modes. The value specified as the subject line for an email notification is longer than the maximum allowed by AR_MAX_NOTIFY_SIZE (255 characters). 250 251 252 253 254 255 256 Unrecognized server statistics tag. or escalation. The value specified for the flag to enable or disable a structure is not recognized. 390621 . Unrecognized no match code. is not a legal socket number. 390636 . For the operations that the server must perform. or 390680 through 390694 (private servers). 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. this structure is required. 390636 through 390669. To define an operation that will execute an SQL command. The server name for a character menu is an empty string or is longer than the maximum allowed length for a file name.h for a list of all the no match codes. Server name for a character menu is empty or is too long.h for a list of the save login codes. a character field with unlimited length (or maximum length over 255 bytes). refer to the Action Request System Distributed Server Option Administrator’s Guide.Error Messages Guide 258 The RPC socket number for the Distributed Server process is not one of the legal values (390600. 263 264 265 Action Request System Error Messages ! 47 . Fields that have lengths over 255 bytes (including diary fields. The SQL command pointer is NULL or points to an empty string. Compound form structure is empty. and the Status History field) cannot be specified as fields to group by.390694). unlimited length character fields. Define a valid server name for the character menu file. 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. Unrecognized save login code.h for a list of all the multiple match codes. specify either 390600 (the Administrator server) or a value in the ranges 390621 through 390634. SQL command is NULL or empty. 259 260 261 262 Cannot specify a diary field. The value supplied as the RPC socket number. The compound form structure is empty or has missing pieces. Specify a grouping that does not include this field. and set this structure to point to it. to be used by the DSO daemon for access to AR System. View the #define statements in the include file ar. 390680 . For more information about using RPC sockets with DSO. When defining a join or view form.390669. or Status History as a field to group by. Verify the #define statements in the include file ar. specify the command. 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. Unrecognized multiple match code.390634. Verify the definitions in the include file ar. inclusive. You have specified a grouping that includes a field that meets these criteria. and this action is not supported. The form type tag specified for the compound form structure is not recognized. The field mapping structure is required when defining a data field on a join or view form. Field mapping structure is empty. The qualification specified for a join form is invalid. Ensure that the definition of the view form is complete and accurate. The compound structure requested a change to the form type. The table referenced in a view form must exist before the view form can be created. or view) is created. The definition of the view form is invalid. specify an index (of 0 or 1) indicating whether the field is tied to a field in the primary or the secondary form. Specify appropriate contents for this structure. When defining a join field reference within a join form. One or more “pieces” of the view definition is missing or invalid. The value of the index is not 0 or 1 in this case. Invalid field mapping type. Invalid join form qualification. View the #define statements in the include file ar.Action Request System 5. Verify the qualification. and update it so that it is an acceptable join definition. 267 268 269 270 271 272 273 274 48 "Chapter 2—Action Request System Error Messages . You can only create a join between existing forms. Invalid base form index in a join field mapping structure. or the table does not exist. The form structure is empty and is not allowed. the structure is empty. so the system cannot create a “clean” interface to the non-AR System table. Specify a join criteria for the join form. Invalid form type in compound form structure.1 266 Invalid join member form name. The field type in the field mapping specified for a field in a compound form is not recognized. The table name identified in the view form definition is not a legal table name. it must be a legal qualification that associates the two forms.h for a list of the recognized field types. join. 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.h for a list of the recognized form types. After a form (base. The index to which a form field is tied is invalid. Change the index to indicate the appropriate form. View the #define statements in the include file ar. you cannot change the form type. Invalid compound form structure change. For this call. Invalid view form definition. Invalid external table name in a view field mapping structure. specify the delete option AR_FIELD_FORCE_DELETE. a button could only have one active link associated with it. and the field is used in the qualification of a join form. which will delete the field despite the dependency. In older versions of the AR System server. you cannot define indexes on join forms. The fields in the join forms that are dependent on this field will also be deleted. When deleting a form. If accessing a join form. 281 Action Request System Error Messages ! 49 . When deleting a field. specify the indexes on the base tables that underlie the join. 279 Submit and Delete entry operations are not supported on join forms. and one or more fields in some join forms depend on this field. specify the delete option AR_FIELD_FORCE_DELETE. AR System server does not support multiple links to the same button. To override this error. The fields in the join forms that are dependent on this field will also be deleted. 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. To override this error. which will delete the field despite the dependency. 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. The join forms dependent on this form will also be deleted. To override this error. In these older versions. 278 The field is referenced in the join qualifier of a join form of which this form is a member. 276 277 The field is referenced by a join form as a base field. The form is referenced by a join form as a base form. the Delete and Submit operations on entries are not supported. Because join forms are relational joins of base tables. an option controls whether the field can be deleted if it is referenced by a join form that depends on this field. To index one or more fields. which will delete the form despite the dependency. but one or more join forms depend on this form. When deleting a field. specify the delete option AR_SCHEMA_FORCE_DELETE. This error indicates that an attempt was made to delete this 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.Error Messages Guide 275 Index not allowed in this type of form. The text you specified is over that limit. The field is included in the message.1 282 A form can have only one default view and there is another view defined as the default for this form. a status field must already be available. Character strings must be terminated by a 0 character. Only one view per form can have this property set to True.0 clients cannot access join forms. Pre-3. because the database contains no data for them. Therefore. A qualification being used to search the database contains a reference to a display-only field. active link. Cannot access the join form with this version of the client. as it is not supported. You cannot create. The text string may contain parameter references that are expanded before the message is delivered. but there is another view that is set as the default. A field referenced in the qualification is not a data field. The Sybase database supports outer joins for joins of two tables only. be included in workflow qualifications. Display-only fields cannot be referred to in database searches. Status field must be created before status history field can be created. Escalation does not have an action defined. An attempt was made to set this property for the view. you cannot create it as an outer join if you are using Sybase. AR System server does not support the specified dataType. the database supports only inner joins. when you create a status history field in a schema or a join schema. They can. An escalation must define at least one action. if you create a join that includes a join form. 283 284 285 286 287 289 290 291 50 "Chapter 2—Action Request System Error Messages . or set this field on a pre-5. Moving to a later client will allow you to access the join forms. If you join more than two tables. or escalation is limited to 255 characters before expansion. This error message is returned due to a RPC procedure mapping error between the client and the server. Message text is empty or too long.1 server. Only data fields can be included in qualifications. they cannot be used in qualifications. however. The text you can specify for a filter. This error is returned because. One of the properties of a view is whether the view is the default view for the form. A qualification contains a reference to a non-data field that is included in the message. Correct your text string to 255 characters or less. get. Display only fields cannot be included in a query to the database. The action field for an escalation is either NULL or empty. Remove the default property setting from the view that currently contains the setting before giving it to another view.Action Request System 5. The expanded message can contain as many as 4096 characters. Because trim and control fields do not have associated data. Cannot create nested outer join form in Sybase or SQL Server. Invalid support file type. this error message is returned.000 filter limit per operation. 296 297 298 299 Action Request System Error Messages ! 51 . Requested number of multiple entries exceeds maximum allowed. The file pointer specified for an API call is NULL or is not a pointer to an open file. Too many levels in filter processing. There is a limit of 25 levels for filter processing. You must provide an array for server to return request existence information. This limit exists to protect against recursive filter actions. See the Developing AR System Applications: Basic guide for more information about filters and push fields actions. This error occurs when more than 10. For example. a filter that includes a push fields action. This error message is returned only when there is a software bug in field value list processing in a GetMultipleEntries( ) call. See the Developing AR System Applications: Basic guide for more information about filter actions and push fields. and so on.000 filters are run from a single operation. An administrator can release a user’s license only once every two hours. The file type specified for a support file in a compound form is not recognized. 294 295 File pointer is NULL or not a valid file pointer. The parameter must be a valid file pointer. Too many filters processed during this operation. There is a 10. this error is returned. Administrator released license too recently. If the internal column index is greater than the array size. with that action launching another filter with a push fields action. This error may be caused by a push fields operation that runs recursive filters.h for a list of the recognized file types. the caller needs to provide a 2 dimension array to hold the request value. This error is an internal error. The administrator has released this user’s license too recently. View the #define statements in the include file ar. Expected column data missing from multiple entries. As an input parameter to call GetMultipleEntries( ).Error Messages Guide 292 293 Invalid item list for entry existence. If there are more than 100 requests specified in the entryId list parameter of the GetMultipleEntries( ) call. with that action launching another filter with a push fields action. Each GetMultipleEntries( ) call can only return a maximum of 100 requests. To perform this operation. 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. AR System automatically generates IDs for requests in the system. you must log in as a user who has administrative permission to the form you want to update. The system encountered an error during a call to allocate space. The next available ID will overflow the definition for the Request ID field. The name specified is incorrect. Some operations in the system are restricted to users with Administrative access. Error while writing to a file. Determine why the write failed. because numerous actions must be performed. call Remedy Customer Support Services to help you reset the next request ID counter. There is no form with the indicated name on the server. The failure occurred on the server machine during processing of a call from the client. or the entry has been deleted by another user during the time you were processing it. in sequence. The Request ID specified is invalid. you can increase the size of the field to eliminate this problem. In general. An error occurred while writing to the indicated file. 301 302 303 304 305 52 "Chapter 2—Action Request System Error Messages . Do not attempt this task yourself. Must have administrator permissions to perform this operation. If the field is already at the maximum and there is a default value. or the desired form is on another server.Action Request System 5. filters. 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. and correct the problem before attempting the command again. Next available ID produces a request ID that overflows Request ID field—contact the administrator. As a final option. you can change the default value to a shorter string. These operations include the ability to restructure the database by adding forms. If you have specified a length for the Request ID field that is less than the maximum allowed (AR_MAX_ENTRYID_SIZE). No entry exists in the database with the Request ID you specified. to make this change successful. and active links and the ability to delete existing requests from the database.1 300 Malloc failed on server. Form does not exist on server. Entry does not exist in database. An accompanying message from the operating system provides details about the failure. and reissue the command. 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. The value must be changed to be within the limits. During submission of an request. A field was specified twice in the field or value list. Value has wrong data type for the field. or the structure of the form has been changed to eliminate the field ID from the form. or a maximum length or pattern if the field is a character field. Remove the duplicate definition from the list. Each field can be assigned only a single value and can be specified only a single time in the field or value list. The actual limit and which field the limit is on are displayed with the error message. Perform one of the following actions: ! ! 307 Supply a value for this field. or remove the Field Name from the Field Sort Order list to complete the operation. to the correct server. Field ID is not related to this form. Required field (without a default) not specified. Limits are specified for the indicated field. Change to the correct form. The operation you are attempting is against the wrong form. so a value must be supplied during the submit operation. If you apply the changes (and override the error). The value for a field in the field or value list is incompatible with the data type defined for that field. You have the option of overriding this error and applying the changes. The field ID references a field that is not defined for the current form. These limits may be a low and high range limit if the field is an integer or real field. Change the value specified to be compatible with the data type of the field to which the value is being assigned. 308 Duplicate field in the definition. Verify the value specified against the limits defined for this field. The field does not have a default value. The value of a field must be the same or compatible data type. The entry you are attempting to modify has been modified by another user since the last time you retrieved the definition. the previous user’s changes are retained.Error Messages Guide 306 Value does not fall within the limits specified for the field. The changes made may impact your changes. against the wrong server. 309 310 311 Action Request System Error Messages ! 53 . or the limits must be redefined to allow the value specified. If you do not apply your changes. all changes you make will take precedence over the changes made by the previous user. no value was supplied for the required field. Entry has been modified since the get time. or the group with this ID has been changed or deleted from the system. and correct the problem. the system will delete structures only when no data is lost. By default. You are attempting to delete a form or field that contains data. or rename the existing form so there is no conflict. Otherwise. The operation you are attempting is against the wrong form. By default. an error occurred while attempting to use a temporary file. to the correct server. Choose a different name. Change to the correct form. During processing.1 312 Data types are not appropriate for arithmetic operation. Group does not exist on server. temporary files used by the server are created in the directory /usr/tmp (for UNIX) or \tmp (for Windows NT). If the group has had its ID changed. Field does not exist on current form. Must override form or field (where entries or data still exist) to delete. You must explicitly override this error in order for the operation to succeed. Review the Developing AR System Applications: Basic guide for information about the data types of operations that are allowed. Then repeat the operation. The directory can be a link to another directory as long as the appropriate user can write to it. The data types of the fields used in a relational operation are not consistent with the operations allowed for that operation. Duplicate form name. against the wrong server. or remove the reference to this group and reissue the request. 313 314 315 316 317 318 54 "Chapter 2—Action Request System Error Messages . and reissue the request. An associated error message contains operating system details about the failure. use the ID of another group. or remove the ID from the field list to complete the operation. The field is not related to the current form. Determine what groups are available. The data types of the fields used in an arithmetic operation are not consistent with the operations allowed for that operation. 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. or the structure of the form has been changed to eliminate the field ID from the form. Review the reason for failure. The group ID specified is incorrect.Action Request System 5. No group with the indicated ID exists on this server. Form names must be unique. Review the Developing AR System Applications: Basic guide for information about the data types of operations that are allowed. A form with the same name already exists on this server. Failure with a temporary file. Data types are not appropriate for relational operation. simply change the ID. Verify that this directory is present and is writable by the user running the arserverd program. Character menu does not exist on server. The password you have specified for the user name is not recognized. 320 321 322 323 325 326 327 Cannot perform statistic operation on the data type of the target. 329 Action Request System Error Messages ! 55 . or there is no character menu by that name defined. Menus can contain a maximum of 15 levels. The field you are changing has restrictions on its length. You have definitions where there is no parent item for some children items. or change the structure definition for the field so that it is no longer required. Choose a different name for the filter. The operation you are performing requests a length change to one of the core fields. Enter the password defined for this user name to access the system as that user. Invalid hierarchy in character menu definition. or specify an existing character menu (if the latter). Filter does not exist on server. The operation you are attempting is against the wrong server. A character menu definition was encountered where the definition of menu items and children do not form a consistent tree structure. The operation you are attempting is against the wrong server. The operation you are attempting is not compatible with these limitations. Assign a legal value for the field. The name you are specifying for this filter is already in use by a filter on this server. You have specified a menu that contains more than 15 levels at some point within its hierarchy. Change to the correct server (if the former). 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 authentication string is the NT domain) or both. or rename the existing filter. The problem can be either with the password or with the authentication string (if using NT authentication. Invalid password for an existing user. The character menu is not defined on the current server. the difference between two times). Change to the correct server (if the former). or there is no filter defined by that name. Duplicate filter name. Too many levels in character menu definition. Refer to the Developing AR System Applications: Basic guide for information about the use and limits of the core fields.Error Messages Guide 319 Request for length change of core or reserved field is out of limits. Required field cannot be reset to a NULL value. You are attempting to set a required field to a NULL value ($NULL$). The filter is not defined on the current server. leave the previous value in the field. or specify an existing filter (if the latter). You are the Submitter if your login name appears in the Submitter field. Because this request does not exist yet. so you cannot set the field for this instance during a submit operation. 331 332 333 334 335 336 56 "Chapter 2—Action Request System Error Messages .Action Request System 5. On this entry. so you cannot change the field on this particular entry. You do not have write access to this field at create time. You do not have write access for this entry to this field. The three special groups (IDs 3. you are not serving in any role yet. An AR System reserved field definition is incorrect. You must have access to a field to read or change its values. depending on the permission settings.1 330 You do not have write access to field. 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. There are several reserved field definitions that are reserved for Remedy. Cannot assign a user to the special Submitter (3). This indicates that you do not have general write access to the field. you are not serving in the role that allows you change access to the field. or Assignee Group (7) groups. or were submitted by you. Assignee (4). and the create mode of the field is protected. See the discussion of the AR System Core and Reserved fields in the Developing AR System Applications: Basic guide for details on the data format allowed. You do not have write access (at create time) to field. You do not have access (read or write) to the field that you are attempting to access. You cannot assign a user to any of these groups. You must have write access to write into that field. 4. and 7) 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 for the request being displayed. 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. You do not have write (change) access to a field that you are attempting to change on this entry (request). You do not have write (change) access to a field that you are attempting to change. depending on the permission settings. You have access to this field on requests that are assigned to you (or a group you are a member of). See the discussion of the AR System Core and Reserved fields in the Developing AR System Applications: Basic guide. You have specified one of these fields with settings that are incompatible with the limits set on the definition of those fields by Remedy. and you are the Assignee if your login name appears in the Assigned To field. You have no access to field. There may be an associated error that contains more details.com.Error Messages Guide 337 You have reached the maximum number of database entries permitted with this version of the Action Request System. the process did not run. or visit www. Determine why the process did not run. If you receive this error during an import action. In either case. You specified a diary field in the merge operation. You are merging requests into a form from another source. specify the option to create new IDs. but Create New ID was not specified. To increase data storage capabilities. or manual changes have been made to the contents of the database. therefore. The file must be present to identify which servers to use. if possible. Separators are defined in the include file arstruct. Then try the operation again. 338 339 340 341 342 343 Action Request System Error Messages ! 57 . To purchase the unrestricted version. The process was a filter or escalation Set Fields process action. This file contains the name of each AR System server that this client will try to connect to. An internal error occurred. and the format for the diary data does not match the expected format. This version of AR System has a maximum limit of 2000 entries per form on an SQL database. A diary field is a formatted character string consisting of a set of user name. An associated error message describes why the ar file (/etc/ar for UNIX or <ar_config_dir>\ar for Windows) could not be opened. Try importing without the change diary. Error in definition for a filter. Incorrect format for the Status History field. Cannot run the requested process. You can do this by removing the lines beginning with change-diary from the export file. and. You have not specified to create a new ID in case of conflict.h. and the format for the status history value does not match the format expected. Cannot find or open the directory file. Could not run a process as requested. 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. Incorrect format for a diary field. and character string triplets separated by valid separator characters.remedy.remedy. or delete the existing request before merging the new one. You specified the Status History field in the merge operation. the merge operation has failed. Separators are defined in the include file arstruct. You have specified a request ID in the merge operation that conflicts with an existing ID in the system. correct the circumstances.com. AR System directory file could not be opened. To merge the new request.h. contact your AR System sales representative or visit www. Duplicate request ID for merged item. An error occurred when loading a filter definition from the database. time stamp. it is probably caused by a corrupt change diary. contact your AR System sales representative or authorized reseller. change the group ID for the group being added to be unique. Choose a different name for the active link. or specify an existing active link (if the latter). You have no access to active link. Duplicate active link name. and 14) can be deleted from your form. Restructure your queries to avoid this illegal operation. 10.Action Request System 5. The password field is a write-only field. If there are two groups with the same ID. To maintain security. 11. Cannot specify qualification on password field. To correct the problem. the group cache for the database contains no group definitions.1 344 Group type conflict between two groups with the same group ID. Contact your AR System administrator if you need access to the active link. You are not allowed to access the specified active link. Re-establish the group structure for successful use of the database. You have specified one of the core fields in a delete operation. This error usually occurs due to someone deleting data from the database. both definitions must specify the same group type. The obsoleted core fields (IDs 9. the system detected a divide by 0. Attempt to divide by zero (0) in arithmetic operation. Group cache structure is empty—no access to database is possible. Two groups have been defined with the same group ID but with different access permissions. you can ignore it by defining it as a hidden field. or rename the existing active link. Core fields cannot be deleted. During an arithmetic operation. Permissions defined for the active link do not allow you to get the definition of or execute the actions for the requested active link. The active link is not defined on the current server. 345 346 347 348 349 350 351 58 "Chapter 2—Action Request System Error Messages . 12. Active link does not exist on server. 13. All groups are keyed by the group ID. only AR System administrator can access the system. At startup. If you do not want to use the core field. Cannot delete a core field. or change the type of the new or existing group to be of the same type. The operation you are attempting is against the wrong server. you cannot specify a qualification on the password field. Two or more groups with the same ID are actually a single group definition with two names. Without group definitions. or there is no active link defined by that name. The name you are specifying for this active link is already in use by an active link defined on this server. Change to the correct server (if the former). there was an attempt to notify the submitter or assignee of the request. the system is canceling the notification. Duplicate character menu name. The current user does not have administrator permission. The server is running in a multiple-socket mode. This server has been configured to not allow unqualified searches. An associated error message contains information about the reason the file could not be accessed. After you correct the error. The name you are specifying for this character menu is already in use by a character menu defined on this server. Only users with administrator permission can access (for read or change) a filter definition. However. An error occurred while trying to access a menu definition file that is located on the server. During a filter or escalation action. AR System allows a maximum of 99 items on any one menu level. Must be administrator to access the filter.Error Messages Guide 352 Notification to special Submitter or Assignee group specified. You are not allowed to access the specified form. You have no access to form. the field holding this information contains a reference to the Submitter or Assignee group. Form permissions do not allow you to get the definition of the form or of its fields or to access the data it contains. reconfigure the notification targets in your system to eliminate this condition. Create. To prevent an infinite loop. and you have issued an unqualified search. Character menu contains too many items on one level (maximum 99). or restart this tool with the RPC socket definition reset to the default value of 390600. Choose a different name for the character menu. and the server has been configured to disallow unqualified searches. You can use multilevel menus to split large menus into multiple smaller and more manageable menus. An unqualified search was issued. or rename the existing character menu. and the socket in use for this client is not the default socket of 390600. Specify some search criteria to perform a search on this form. Use routines connected to the default socket. All structural changes must be made using the server connected to the default socket. Reference to the Submitter or Assignee group exists in the referenced Submitter or Assigned To field. the menu will be available. Error while accessing a menu file on the server. If you are receiving this error. Notification canceled to prevent a potential infinite loop. and Delete operations to structures are supported only on RPC socket 390600. Contact your AR System administrator if you need access to the form. 353 355 356 357 358 359 361 Action Request System Error Messages ! 59 . Specify some qualifying criteria in one or more fields to limit the amount of data being returned from the server. The character menu definition contains too many items on one level of the menu tree. Set. The name you are specifying for this escalation is already in use by an escalation on this server. No form ID for the form. Duplicate escalation name. The escalation is not defined on the current server. Perform one of the following actions: ! ! Supply a value for this field. There was no form ID found in the file form. or remove the assignment of NULL for the diary field. restore a file from the correct version or. if you have not run the upgrade program after installing the new version. a value specifying the keyword $DEFAULT$ was supplied for the required field. Error in definition for an escalation. This is usually caused by a manual edit to the form. A diary field is append-only. or specify an existing escalation (if the latter).ar. Only users with administrator permission may access (for read or change) an escalation definition. but there is no default value for the field.ar file or by a file that is from a previous release of AR System. 366 367 368 369 370 60 "Chapter 2—Action Request System Error Messages . run the upgrade program to bring the file up to date. it cannot be assigned a NULL value. 364 Diary field cannot be set to a NULL value in a filter or escalation. Accordingly.Action Request System 5. Must be administrator to access the escalation. The filter definition contains a Set Fields action where a diary field has been assigned a value of $NULL$. The operation you are attempting is against the wrong server. 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. The current user does not have access to the escalation.1 363 Required field assigned $DEFAULT$. If the latter. or rename the existing escalation. During submission of a new request. or manual changes have been made to the contents of the database. or there is no escalation defined by that name. If the former. Escalation does not exist on server. The field does not have a default value specified so you cannot use the $DEFAULT$ keyword during the submit operation. Specify an alternate value. Change to the correct server (if the former). restore the file from a backup before the manual change. Choose a different name for the escalation. An internal error occurred. An error occurred when loading an escalation definition from the database. One of these conditions exists: ! 374 The operation you are attempting is against the wrong server. More than one form with the reserved alert events fields was found. All but one form must be removed. You cannot assign the same name to more than one distributed mapping. No distributed mapping with the specified name could be found. ! 373 Must be administrator to access the distributed mapping. Change to the correct server. you can update only one entry (marked as the current master) in a chain. The server was unable to create an alert event request in the database. In this mode. or rename the mapping with which the conflict exists. You attempted to update a copy other than the master. An associated error message contains details about the failure. ! 375 Duplicate distributed mapping name. 376 Action Request System Error Messages ! 61 . Choose a different name for the mapping. Possible causes are as follows: ! ! 372 The server was unable to find an Alert Events form. the value of the Submitter field cannot be changed after submission (even by the administrator). The request could not be added to the database. and try the operation again. The current user attempted to access a distributed mapping and does not have administrator privileges. Distributed mapping does not exist on server. Cannot update this entry—this distributed entry is not the master copy. and try the operation again. The system can be configured with a Submitter Mode of Locked or Changeable. In a distributed environment.Error Messages Guide 371 You cannot change the value of the Submitter field—the Submitter Mode of the system is configured to be locked. Perform the update on the current master copy of the entry. Specify an existing distributed mapping. Only users with administrator privileges can read or change a distributed mapping definition. The specified distributed mapping does not exist on the current server. Could not create alert event. You have configured the system with a value of Locked. unique. or from another table in the database. 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. 378 379 380 381 382 62 "Chapter 2—Action Request System Error Messages . A filter action was extracting data from another form. You must be the user (process) Distributed Server to run the specified delete operation against the Distributed Server Pending and Distributed Server Mapping forms. indeed. The administrator configured the action to return an error if multiple matches were found. A distributed or application operation activated by a filter action includes one or more arguments with single (') or double quotation marks ("). Review the values for the entry to ensure that values that must be unique are. The values for this entry violate a unique index that has been defined for this form. or from another table in the database. and found multiple rows that matched the qualification criteria. and ignore the system warning related to the forms. Somewhere in the command line. Must be Distributed Server to perform this operation. and use the correct command line syntax. an error occurred. Attempt the operation again. The command line arguments cannot be processed. select the forms for deletion. No item matches filter conditions—this operation has been defined so that no match generates an error.1 377 The distributed or application operation specified in the filter Run Process action contains mismatched quotation marks. When a system is licensed for the Distributed Server Option. a mismatch in the amount of quotation marks exists (there is not an even number of open and closed single or double quotation marks). Problem encountered during creation of one of the distributed forms. The distributed or application operation is not performed. The administrator configured the action to return an error if no matches were found.Action Request System 5. 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 AR System Administrator. The command line in which the mismatch exists is displayed and includes an error message. A filter action tried to extract data from another form. During the creation of these forms. and found no rows that matched the qualification criteria. An associated error message contains details about the problem. Correct the reason for the failure. a pair of forms is automatically created by the server. and restart the arserverd process (or send a SIGHUP signal) to re-create the forms. Multiple entries match filter conditions—this operation has been defined so that multiple matches generate an error. Change the name to remove the control characters.Error Messages Guide 383 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. To override this error. an option controls whether a field that is used in the join qualification can be updated. One or the other is already in use for this form. The name specified contains an invalid character. If you need a large menu. To create a new VUI. A setting of AR_JOIN_SETOPTION_REF will enforce the referential integrity and cause the update to be rejected. Cannot delete final VUI for a form—all forms require at least one VUI. The same ID was specified several times in a “multiple” structure operation API call—each ID specified for this call must be unique. or to a VUI ID that is associated with the form to complete the operation. Every form must have at least one VUI defined. The name contains a control character. 384 385 386 387 388 VUI does not exist for the specified form. Only printable characters are allowed. the correct server. specify a unique name and ID—or leave the name blank and the ID set to 0 to have the system create a name and ID for you. Multiple API calls—those that allow you to perform a set of operations in a single call—do not support specifying the same ID several times within the same call. Object names can contain only printable characters. or the structure of the form has been changed to eliminate the VUI ID from the form. The VUI is already associated with the form. Change to the correct form. If you specify two sets of changes or you specify to delete the same object several times. and this is not allowed. The operation you are attempting is against the wrong form. The VUI is not related to the specified form. Both the VUI name and the VUI ID are unique values. consider breaking it into smaller pieces and connecting the appropriate menu with the subset you are interested in. Issue the operation again without specifying the same ID multiple times. This error indicates that such an update was attempted. 389 390 Action Request System Error Messages ! 63 . A “nested filter exception” error is returned because a filter exception condition is already being thrown. confusion about the desired operation can arise. You are attempting to delete the only VUI for the form. When updating an entry in a join form. specify the set option of AR_JOIN_SETOPTION_NONE. Large menus are unwieldy and can hurt performance. against the wrong server. Updating this entry will violate join condition. Exception occurred while handling previous exception. Duplicate VUI for the form. for example. this message appears. If the server is unable to allocate memory from the shared cache. the correct server.Action Request System 5. The operation you are attempting is against the wrong object. The Group List field (field 104) is a reserved field with a restriction that the field cannot be more than 255 bytes in length. or to a support file ID that is associated with the object to complete the operation. 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.1 391 Creation of VUI failed. The system has timed out while waiting for a process that is running on the server to return a value. The system requires that the name for all fields and VUIs on a form be unique. Reserved field Group List has too many characters. must not contain more than 255 characters. or the structure of the form has been changed to eliminate the indicated support file ID from the object. against the wrong server. The support file is not related to the specified object. Change to the correct object. consult your AR System administrator. If you cannot wait to try your operation. Unable to allocate memory for cache. Please retry your operation later. and try the operation again. The administrator has set access for administrator users only. Field or VUI name must be unique for the form—there is already a field or VUI using this name. The server has timed out waiting for the process to return the requested value. 392 393 394 395 396 397 398 64 "Chapter 2—Action Request System Error Messages . 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. Neither the Status History field nor any part of the Status History field can be used in a query style character menu. You have supplied a name that is already being used by another field or VUI. An associated error message contains details about the failure. Status History field cannot be used as labelField or valueField in the query menu. because updates are being performed. and the server terminates. Change the definition to be 255 bytes or less. A new VUI for the form could not be created. Support file does not exist for the specified object. AR System server has been temporarily locked for use by users without administrator permissions. The definition being saved or imported has an unlimited length. Change the name of this item. The file that was expected to hold the definition of a form does not hold a form definition or is incorrectly formatted. The form definition being loaded is missing one or more of the required core fields. A field ID in the core range was found. One of the core fields is missing from the form file definition. 401 402 403 404 405 406 407 Action Request System Error Messages ! 65 . If you have manually changed a file. If the definition file has been changed. This error is usually caused by a manual change to one or more of AR System database definition files. the change is invalid. If you have manually changed a file. This error is usually caused by a manual change to the form definition file. You may or may not use them. but it is not the form definition that is expected. but they must be present. this is an unexpected error. this is an unexpected error. The ID is. A field or VUI ID must be unique within a form. therefore. the change is invalid. Field ID is in the core field range but is not recognized. the change is invalid. an illegal ID and cannot be used. These fields must be present as part of the definition of the form. The number of fields defined for the form does not match the count in the form header definition. the change is invalid. A core definition from the definition file is incorrect. This error is usually caused by a manual change to one or more of AR System database definition files. Incorrect format in the definition file. A format error was detected in a definition file. the change is invalid. The error message will contain the error. The definition of one of the core fields is inconsistent with the rules defined for that core field. If the definition file has been changed. If you have not changed the file. The form definition file field count does not match number of fields in the file. This error is usually caused by a manual change to the form definition file. 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 error is usually caused by a manual change to one or more of AR System database definition files. Duplicate field or VUI ID in the definition. Form definition in the source file is not the expected definition.Error Messages Guide 400 The file specified for a form does not hold a form definition. the change is invalid. the change is invalid. This error is usually caused by a manual change to the form definition file. If you have manually changed a file. The file contains a form definition. but this is not one of the defined core fields. The form definition contains a duplicate definition for one or more fields. If the definition file has been changed. If you have not changed the file. If the file has been deleted. If the file has been deleted. This error is usually caused by a manual deletion of the contents of a structure file. This error is usually caused by a manual deletion of the contents of a structure file. The file specified for a character menu does not hold a character menu definition. it must be restored from a backup. Remove the definition file of all lines that are not part of a legal definition. it must be restored from a backup. A file that is specified as holding the definition of a character menu does not contain the definition. A file that is specified as holding the definition of a filter does not contain a filter definition. The file specified for an active link does not hold an active link definition. The file specified for an escalation does not hold an escalation definition. and then retry the import operation. If the definition has been changed. This error is usually caused by a manual deletion of the contents of a structure file. This error is usually caused by a manual change to the 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. The import file contains data that is not part of a legal structure definition supported by AR System. If the file has been deleted. A definition was found without that selection definition. If the file has been deleted. The import file is in an incorrect format. All fields with a Selection data type must define a list of one or more values that define the selection for that field. 409 410 412 413 414 415 416 66 "Chapter 2—Action Request System Error Messages . The file specified for a distributed mapping does not hold a distributed mapping definition. The file specified for a filter does not hold a filter definition.1 408 Selection data type requires a limit specification. If the file has been deleted. 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. A file that is specified as holding the definition of an escalation does not contain the definition. If the file has been deleted. the change is invalid. it must be restored from a backup. it must be restored from a backup. The structure file does not contain definitions. it must be restored from a backup. it must be restored from a backup. No definition is in the file.Action Request System 5. This error is usually caused by a manual deletion of the contents of a structure file. However. Incomplete join form definition. During import. The file specified for a container does not hold a container definition.Error Messages Guide 417 Cannot translate the group name in either the Group List or Assign Group field. so it cannot be created. 418 419 420 421 422 423 424 Action Request System Error Messages ! 67 . 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 field mapping of this join or view form is not consistent with the type of the form. a form defined itself as a join form. Ensure that you have not changed the name of the file prior to import. The operation was occurring during the processing of a filter or escalation. The likely cause of the failure is that the system encounters a name that is not a currently defined group. a form defined itself as a view form. Unrecognized escalation action type. but it is not the definition that is expected. one or more key pieces of information (such as the table being referenced) are missing. you cannot use a Push Fields action to push values to forms residing on different servers. In filters and escalations. During import. For example. During the conversion. However. if the form is a join form. The file contains a container definition. filters. one or more key pieces of information (such as the type of join or the primary or secondary form) are missing. See the Developing AR System Applications: Basic guide for more information about Push Fields actions. The type of the action attached to the escalation is outside the allowed range of types. so it cannot be created. all data fields must be defined with a field type indicating that they are a join field. 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. Filter and escalation Push Fields actions can only affect forms on the same server as the filter or escalation. because there are no base data fields when you are working with a join form. and escalations. Incomplete view form definition. The join form definition is dependent upon complete information about the join. The view form definition is dependent upon complete information about the view. an error occurred. Incomplete field mapping definition. Invalid field type. the right number of columns) for the external schema was not retrieved. The upgrade program is run automatically as part of the installation operation. When creating or updating an active link. The program that updates the database structure to the current structure no longer supports Oracle 8. Ensure that the key field is set to a non-null. and the report file could not be retrieved. which is embedded in the active link definition being created or modified. This error is returned because the correct column information (for example. The program that upgrades the database structure to the current structure requires more arguments than you specified. The active link will be created or updated without the file. Continue with any other files. You need not run this program. the system encountered an error. You need not run this program. then reselect the macro in the action. and put it in the proper location. the user will receive a warning about the missing file. This View Form contains Request IDs that are null. If it is replayed. View the associated messages. Too few arguments specified for upgrade program. Status History field is not supported on View forms. 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. The file will not be saved as part of the definition. Continuing the operation without the file identified in the associated message. Failure during load of report definition file into server.cfg file. Please upgrade your Oracle database to Oracle 8i or higher. Missing audit information in the ar. 451 460 475 476 477 480 481 482 68 "Chapter 2—Action Request System Error Messages . and update the active link definition to have the file included within the active link.0 is no longer supported by upgrade. Oracle 8. Locate the file that is expected.Action Request System 5.1 450 Cannot open a report definition file. While attempting to read a report file referenced in a macro definition. Please check the spelling (table name is case-sensitive). The program that upgrades the database structure to the current structure requires fewer arguments than you specified. unique column to avoid data corruption. Too many arguments specified for upgrade program.conf/ar. a macro action or else definition contains a reference to a report file that does not exist. This error is returned because you cannot search the database for the entry ID in a view form if its value is NULL.0. Requested database table not found. The operation continues without the report file. Contact Remedy Customer Support. This error is returned because you cannot create a Status History field on a view form. The upgrade program is run automatically as part of the installation operation. Error Messages Guide 504 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 NT). Ensure 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 the user running the arserverd process has read and write access. Update ownership or permissions as needed. 550 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 NT) 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). Ensure 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 552 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. 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 database—missing control record. This is a serious error. The control record for the data dictionary in the database is missing. 553 554 Action Request System Error Messages ! 69 Action Request System 5.1 555 AR System structure error in the SQL database—missing 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. 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. 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. 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. 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. 556 557 558 559 560 70 "Chapter 2—Action Request System Error Messages Error Messages Guide 561 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. 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. 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. 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 Services for assistance. 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. 562 563 564 565 566 567 Action Request System Error Messages ! 71 Action Request System 5.1 590 SQL database is not available—will 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 available—continuing to attempt connection. This message is issued every 15 seconds while the system is attempting to connect to an SQL database that is not responding. Up to 4 attempts to connect will be made. 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. 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. 591 592 600 601 602 603 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. 604 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. 605 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. 607 72 "Chapter 2—Action Request System Error Messages No such user exists—cannot connect as a guest user because user name differs from a registered user only by capitalization. Specify whether the system is adding or deleting the entry specified. The server could not open the access control server cache file (server. 1 = fixed license. Supply an appropriate value for this option. If it is correct. 609 610 Error while accessing server cache file (server. Update ownership or permissions as needed. The two forms are identified in an associated error message.cfg file (Windows NT). The user specified as the administrator user to allow you to perform this command is not a recognized user in the system. 2 = floating license). Verify the permissions on the file to make sure the user running the arserverd process has read and write access.conf file (UNIX) or the ar.ar). 612 Specified user is not registered with this AR System server. 1 (fixed). Unrecognized license type—must be 0 (none). The value specified is not one of these values.ar). the user is not allowed to log in as a guest user because the user name differs from a registered user only in capitalization. The user attempting to log in is not a registered user and although the system has been configured to allow guest users. An associated error message explains why the file could not be opened. 613 614 615 620 621 Action Request System Error Messages ! 73 . If the file is not present. look in that directory for the file. Enter the command again. and specify an appropriate value. Enter the command again. The specified option expects a value but none was specified. The value for the group type option must be an integer code 1 for a view group and 2 for a change group. You must connect with a valid user with administrator access. restore the file from a backup. Ensure that the directory setting is correct. Problem processing the license tag file—license tag file ignored. Unrecognized group type—must be 1 (view) or 2 (change). The specified value is not one of the legal tags (a or d) for the -U or -G option.Error Messages Guide 608 A value is expected for the command line option. Two forms contain the same open license tag—ignored for both forms. The system found two forms with the same open license tag specified in the change history. The value you specified is not one of these values. The system encountered an error while attempting to process the license tag file. Invalid tag for Group or User operation. This file is located in the database directory referenced by the Server-directory setting in the ar. The system does not allow this to exist. The value for the license type option must be an integer code (0 = no license. and specify an appropriate value. or 2 (floating). Business time processing involving holiday schedules cannot proceed without this form. The system could not find a form with the specified reserved holiday fields on it. Invalid times will be treated as if no time was specified. The tag included in this message was specified as a holiday tag on a business time calculation. The system encountered two forms with identical reserved workday fields.The two forms are identified in an associated error message. this tag cannot be found in the Holiday form. a definition file with copies of the business time forms was placed on the server system. Business time processing involving workday schedules cannot proceed without this form. Two forms containing all the reserved holiday fields encountered—delete one to continue. A date in the holiday list of the Business Time Holiday form is not a legal date. Either correct the workflow to reference a legal tag or add a new tag to the Holiday form. During installation. The Workday form can be imported from that definition. During installation. Illegal dates will be ignored and processing will continue. The two forms are identified in an associated error message. Date in the holiday list is invalid. No Holiday form could be found on the server. The system does not allow this to exist and is unable to continue business time processing.1 622 Problem while preparing open write licensing—open write licensing may be incomplete. Time in the workday definition is invalid. No holiday definition exists with the specified tag. The system could not find a form with the specified reserved workday fields on it. Two forms containing all the reserved workday fields encountered—delete one to continue.Action Request System 5. One form must be deleted for processing to continue. The system encountered an error while attempting to prepare open write licensing. The system does not allow this to exist and is unable to continue business time processing. 625 626 635 636 637 638 639 74 "Chapter 2—Action Request System Error Messages . The Holiday form can be imported from that definition. a definition file with copies of the business time forms was placed on the server system. However. No Workday form could be found on the server. A time specified in the Business Time Workday form is invalid. An associated error message contains the details of the failure. One form must be deleted for processing to continue. and processing will continue. The system encountered two forms with identical reserved holiday fields. or the value specified is out of the legal range of values for the FTS information setting. Full text search (FTS) information data associated with this tag is invalid. Resolve the error indicated. However. The workday schedule does not contain any open hours. Review the #define statements in the include file ar. there must be at least one minute during the week that is defined as open. 653 654 655 656 657 Action Request System Error Messages ! 75 . An associated error message contains the full text of the error message from the FTS engine that describes the failure encountered. For a workday schedule to be valid. You must omit this value from the Set operation. ARFullTextInfoList structure is empty. You specified a code for a piece of full text search (FTS) information that was not recognized. Correct the definition to specify open times for the schedule. To retrieve information.h for a list of all the valid codes that can be specified. specifying the correct data type for the value. Could not initialize the full text search (FTS) database. ARFullTextInfoRequestList structure is empty. and start the server process again. The ARFullTextInfoList structure is either NULL or empty. the settings and their values must be specified. 641 651 652 Full text search (FTS) information data associated with this tag has an incompatible data type or the value is out of range. you must specify what information you are trying to retrieve. The full text search (FTS) information tag is unrecognized. 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. If a value is specified. Failed to complete full text search (FTS) operation. The workday schedule defines no open hours. The value you specified for the list of information to retrieve from the FTS value was NULL or empty. To set one or more pieces of server information. Try the operation again. This generic message indicates that an error occurred during a full text search (FTS) operation. this tag cannot be found in the Workday form. The tag included in this message was specified as a workday tag on a business time calculation. The server encountered an error while attempting to connect to the full text search (FTS) database. Either correct the workflow to reference a legal tag or add a new tag to the Workday form. The data value specified for one of the full text search (FTS) values is an empty string. it must have a legal value assigned. Review the associated error message for more details about why the attempted connection failed.Error Messages Guide 640 No workday definition exists with the specified tag. or you must supply a value. A full text search on a field that is not a character or diary field is not allowed. Contact Remedy Customer Support Services for assistance. An associated error message contains the full text of the error message from the full text search (FTS) engine that describes the failure encountered. While attempting to retrieve or set the Ignore Words list. However. Search the FTS home directory and the FTS index directory for a file named style/style. does not have appropriate permissions. An attempt has been made to retrieve or set information about the full text search (FTS) environment on the server. or does not have enough disk space for the existing FTS index.1 658 Failed to read full text search (FTS) documents. An associated error message contains the full text of the error message from the FTS engine that describes the failure encountered. Break the operation into smaller pieces. an error occurred. While attempting to update the Ignore Words list. If you are not using the full text search (FTS) capability of the product. Consider using the accrue capability to combine searches for multiple values on the same field. an error occurred while updating the Ignore Words list file. An attempt was made to search on a field that is not a character or a diary field. While performing a full text search (FTS) operation. The operation you are attempting generates a full text search (FTS) command that is too large for the database to handle. Failed to relocate full text search (FTS) index directory. 659 660 661 662 663 665 76 "Chapter 2—Action Request System Error Messages .stp. there are no Full Text Search Option licenses defined for the server. This error is often caused by a permission problem with the Ignore Words list file. and the user running AR System server must have read and write access to the files. An error occurred during a full text search. Failed to update the Ignore Words list file. An error occurred during an attempt to change the location of the full text search (FTS) index directory. For example. No users are licensed for full text search (FTS) operations on this server. An associated message contains the full text of the error message from the FTS engine that describes the failure encountered. this error can be ignored.Action Request System 5. This message indicates an error in the database structure tables. If you want to use the full text search (FTS) capability. An associated message contains the full text of the error message from the full text search (FTS) engine that describes the failure encountered. Operation requested is too large for a single full text search (FTS) command. you must obtain a license. The file must exist in each directory. an error occurred while reading from the FTS database. Failed to open the Ignore Words list file. 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. This error is commonly encountered when the target location does not exist. reduce the number of operations being performed. You attempted to perform an operation that can only be performed when the full text search (FTS) state is set to Disabled. It may take from a few minutes to a few hours for the index to be created and put in place. You are attempting to move the location of the full text search (FTS) index directory. It is currently set to Disabled. An associated error message contains complete information from the FTS engine. To move the index directory. change the FTS state to Disabled. 667 668 669 670 671 672 Action Request System Error Messages ! 77 . If it is correct and there is an empty directory in place. When the indexing has been completed. Cannot perform a full text search (FTS) index on a Status History field. Contact Remedy Customer Support Services for assistance in resolving the error. Its creation is pending. To perform this operation. Invalid full text search (FTS) query. and try your operation again. and try your operation again. remove the directory and try the operation again. the directory you will be using cannot already exist. AR System server attempted to start the full text search (FTS) indexing process. Full text search (FTS) operations are enabled.conf file. It is currently set to Enabled.Error Messages Guide 666 Full text search (FTS) operations are disabled. The field you are performing the search on is a full text search (FTS) enabled field. the index does not currently exist on this field. You performed an operation that attempted to index this field. and try again. the system will default to the search strategy supported by the underlying database. the field will be available for full text searches again. 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 Server-directory setting in the /etc/ar. The full text search (FTS) operation failed because the search criteria had syntax errors. but it could not find the executable. To perform this operation. depending on the amount of indexing that is pending. change the FTS state to Enabled. Field is pending a full text search (FTS) operation. If the directory you specified is not correct. Full text search (FTS) executable not found. Turn off FTS operations. You attempted to perform an operation that can only be performed when the full text search (FTS) state is set to Enabled. change the name to the directory you want. The target directory already exists. For now. Turn on FTS operations. The Status History field (core field ID 15) cannot be enabled for a full text search. and try again. Destination full text search (FTS) index directory already exists. however. The FTS index does not support this operation. The comparison will be made using the functionality of the database. and the search term matched too many words in the FTS dictionary. Because this file contains the definition of all the mappings that will be performed. AR System NM Daemon: Malloc failure. An associated error message contains details about why the connection failed. the system cannot run without this file. An associated error message contains details about why the file could not be opened.1 673 The query compares two fields that involve full text search (FTS) indexed fields. The system failed to connect to the network management platform. because the underlying database is relied upon for the search. The system failed to connect to the event dispatcher of the network management platform. 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. run the network manager if the error is that the manager is not running). AR System NM Daemon: Cannot register with network manager event dispatcher. configure it). Because this file contains the definition of all the mappings that will be performed. An associated error message contains details about why the connection failed. and run the daemon again. You cannot use the API call arsetfulltextinfo to set the FTS information home directory. AR System NM Daemon: Failure checking whether configuration file has been accessed. Correct the cause of the error (for example. if the event subsystem is not configured. AR System NM Daemon: Cannot open the configuration file. You can also restart processes that have been running for a while to recover space those applications may have suffered “memory leak” over time. Correct the cause of the error. The full text search (FTS) home directory can be set only by the installer. 701 702 703 704 78 "Chapter 2—Action Request System Error Messages . In general. The full text search capability does not support comparing two fields. The system encountered an error during a call to allocate space. Correct the cause of the error and run the daemon again. The attempted query involved a full text search (FTS) indexed field. You can recover that memory by shutting down unneeded processes. the system cannot run without this file. An error occurred while trying to open the configuration file. The attempted query includes a relational operation between two full text search (FTS) indexed fields. Correct the cause of the error (for example. An associated error message contains details about why the file could not be opened. An error occurred while verifying whether an update to the configuration file has occurred. 674 675 700 AR System NM Daemon: Cannot register with network manager. This directory is set during installation. and run the daemon again. and run the daemon again.Action Request System 5. The full text search (FTS) query is not sufficiently qualified. you must be a registered user with update permission to the field to perform the submission. This error is not expected. The configuration has specified more fields to be mapped than the maximum amount allowed. 706 707 708 709 750 Changes to your event or trap mappings will be lost if you exit. The specified command-line option requires an additional value with this program. The arxxxd process lost connection to the trapd process for the network management platform. AR System NM Daemon: Too many fields specified for one of the traps or events. this error should not occur. A complete definition of the allowed command-line options can be found in the Developing AR System Applications: Basic guide. A complete definition of the allowed command-line options can be found in the Developing AR System Applications: Basic guide. AR System NM Daemon: A value is expected for the command-line option. If guest users are allowed and create modes are open. While you have been modifying the contents of the mapping file. The total of all data being mapped causes an overflow of the definition in the mapping file. more than this number are defined. restore it to its previous format. you can ignore this error and continue.Error Messages Guide 705 AR System NM Daemon: Format error in configuration file. The configuration file has been changed by another user while you have been modifying its contents. If you save your changes. The specified user does not exist on this server. The specified command-line option is not a legal option for this program. an unknown (or guest) user is allowed to perform submissions. the file has been changed by another user. 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. Data in other fields truncated for entry. You have not saved your new or changed definitions. If all the fields being mapped have an “open” create mode. all changes will be lost. do not ignore this message—acknowledge it and save your changes before exiting. If the file is merely updated through AR System NM daemons. User does not exist on the server. If the file has been manually edited. they will overwrite the changes made by the other user. Unless you are discarding invalid changes. However. The system can map a maximum of 300 fields in any single trap mapping. if any of the fields being mapped are “protected” fields. AR System NM Daemon: Connection to trapd lost. The format of one or more lines in the configuration file is not recognizable. AR System NM Daemon: Unrecognized command-line option. 751 752 753 Action Request System Error Messages ! 79 . If you exit the tool. Out of memory. The password you specified is not the password that is recognized for you. Correct the reason for the failure. 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. Cannot connect to any AR System server as the current user. and attempt to open the file again. Verify the password that you entered (remember that passwords are case-sensitive). you will lose the changes you made. You have not saved the changes you made. cancel the exit operation. You (1) have not supplied a password. In general. you can exit the tool without losing them. and enter the corrected password. the new file will not be opened. 758 759 760 761 763 764 765 80 "Chapter 2—Action Request System Error Messages . and save the changes by using the Save command on the File menu. the system cannot verify permissions or retrieve information about forms to map into. If you want to keep the changes. You have not opened the file defined in this window—the file will not be opened if you continue.1 754 Changes on this screen will be lost if you continue. Cannot open the network management configuration file. Cannot connect to any AR System server. An associated message contains details about why you could not open the file.Action Request System 5. or (2) your password is different from the one supplied. Cannot successfully connect to any server as special NM user. cancel the dismiss operation. If you continue with this operation. If you continue to exit the tool. If you want to discard the changes. they will be lost if you exit. You cannot run this tool unless at least one AR System server is accessible as a target for traps that are mapped. No AR System servers registered—cannot validate user to allow configuration. You can recover memory by shutting down unneeded processes. The network management configuration file that you specified cannot be opened. You have specified a file name in this window. simply continue. To save the changes. You cannot run this tool unless you can access at least one AR System server to be the target for traps that are mapped. The file was not opened due to a previous error or because you have not clicked the Save button on the window. Accordingly. or (3) the server does not have a registration for you and does not allow guest users. Invalid password for user on server. You have not saved the changes you made to this file. Changes you have made to this screen will be lost if you continue. and save the changes. The system encountered an error during a call to allocate memory. or you can restart processes that have been running for a while to help recover space those processes may have leaked over time. After the changes are saved. Verify the syntax specified in the mapping. 792 Action Request System Error Messages ! 81 . If there is no target form. See the associated error message for details. You can add the value as a new option to the selection choices. An error occurred while trying to map an SNMP varbind variable. Change the value into a legal real number format. A target form for the mapping must be supplied. The program cannot open the specified SunNet Manager configuration file. and repeat the operation. An associated error message contains details of the failure. You cannot add new definitions until you can open the file. Review the associated error message for more details. if you do not have read or write access to the file. Correct the reason for the failure (for example. You have entered an improperly formatted value for a real field. The value for the real field is not a recognized real format. You can enter digits only in numeric fields. Change the contents of the indicated field to a legal number. You have entered a nondigit character for a numeric field. Invalid mapping of an SNMP varbind variable. An associated error message contains details of the failure. if you are out of space. 767 768 769 770 771 772 775 791 Cannot open the SNM configuration file. Unrecognized selection value. An error occurred while trying to write updates to the definition file.Error Messages Guide 766 Cannot access the indicated file. You have specified a character string in a numeric field. Failure while writing to the file. change your file access permissions). You must specify a form that is the target of the trap being mapped. and correct it as needed. and run the tool again. and perform the operation again. An error occurred while preparing the Set Fields screen. An associated message contains more information about the failure. Failure while building Set Fields screen. Correct the failure and save your changes again. Failure while writing to the file. Correct the reason for the failure (for example. The file indicated in the error message cannot be accessed. remove some files to create more space). A selection value was specified that is not one of the legal selection values for the field. The system will accept real values in decimal or scientific notation. An error occurred while attempting to save changes to the indicated file. no mapping is performed. or you can change the value to one of the legal values. Cannot have a quotation mark in the command line due to SunNet Manager syntax. Malloc failed on TC server. You cannot specify a quotation mark in the command line. the operation is continuing.Action Request System 5. The system creates a backup of the definition file and names it <file_name>. and issue the mapping request again.1 793 Failure while trying to create a backup file. Cannot have a quotation mark in the label due to SunNet Manager syntax. 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. however. A failure was encountered while trying to launch a child process. and the command is the operation performed when the label is selected. You cannot specify a quotation mark in the label. The server has detected that one of the child processes it is responsible for has terminated. You defined a mapping (probably using varbind) where one of the mappings is wrong. The system encountered an error during a call to allocate space. The command line you specified contains a quotation mark. The server process will relaunch the server that shut down. there is no backup file. however. The name of the process that is being restarted is reported in an associated message. The system is continuing the operation and updating the definition file. 842 843 82 "Chapter 2—Action Request System Error Messages . 794 795 796 797 802 AR System server terminated unexpectedly—restarting. and try the operation again. Correct the mapping. because it is a special character in the SunNet Manager definition syntax. This is a warning message. The label is the name displayed on the menu. The failure occurred on the server machine during processing of a call from the client. this time it failed. An associated error message contains details about the failure. The label you have specified contains a quotation mark. Invalid mapping parameters. because it is a special character in the SunNet Manager definition syntax. The child process was not launched. An error occurred while trying to create a backup file for the SunNet Manager definition file. A value is required for both the label and the command. You can recover that memory by shutting down unneeded processes or by restarting processes that have been running for a while. You must change the command line so that it does not include a quotation mark character.bak. In general. You must supply both a label and a command. Correct the reasons behind the failure. Failure during fork operation—cannot launch child server. You must change the label so that it does not include a quotation mark character. An associated message provides details about the failure. 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. The server process has attempted to launch a child process more than four times within 30 seconds. A failure was encountered while trying to launch a child process. The name of the child process that could not be restarted is identified in an associated message. The child process was not launched. The work file must be locked by the arservftd process but is currently being held by another process. An associated error message describes the details of the failure encountered. Pending list lock file exists. 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. 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. Failed to truncate the pending list file. An associated message provides details about the failure. Pending list file open action failed. A full text search (FTS) enabled field was updated. This is an internal error. 858 859 860 Action Request System Error Messages ! 83 . An associated error message describes the details of the failure. the server will stop trying to launch the process and will remove it. A full text search (FTS) enabled field was updated. because the record associated with the updated field could not be found. 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. Because this process continues to fail. and try the operation again. Correct the reason behind the failure. An associated error message describes the details of the failure encountered. Attempted to launch this server more than four times within 30 seconds—abandoning attempt to start this server. An associated message provides details about the failure. Failure during wait operation—unable to wait for status change. A full text search (FTS) enabled field was updated. 845 847 855 856 857 Pending list lock file does not exist The arservftd process cannot release the work file. Pending list file write action failed.Error Messages Guide 844 Failure during exec operation—cannot launch child server. An associated error message describes the details of the failure. because the file does not exist. Record does not exist in the pending list file. A failure was encountered while trying to wait for a status change. The full text search (FTS) indexer process (arservftd) has a maximum number of arguments allowed. field ID. Only one instance of the full text search (FTS) indexer process can be run on any given machine. 866 Another copy of the full text search (FTS) indexer process is already running. The action code supplied is not recognized. Refer to the Developing AR System Applications: Advanced for information about allowed routines. The optimize argument has been specified for the full text search (FTS) indexer process. Request ID. The full text search (FTS) indexer process (arservftd) requires a minimum set of arguments. If the signal is a number other than 15 or is one you sent directly to the process. a field ID. 867 868 84 "Chapter 2—Action Request System Error Messages . and a Request ID. 864 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. one or more of the arguments that are not allowed have been specified. no action is required. During a re-index operation. Refer to the Developing AR System Applications: Advanced for information about the expected arguments. One or more of these values is missing. 865 Full text search (FTS) indexer process terminated when a signal was received by the server. If so. The process was stopped either accidently or intentionally by a user in your environment. The server most likely shut down due to a bug in the system. Too many arguments specified for optimize argument. 862 863 Too many arguments for the full text search (FTS) indexer process. If the signal is 15. The number following this error is the signal that was received. you must supply a form ID or name. Refer to the AR System C API Reference Guide for more information. Too few arguments for the full text search (FTS) indexer process. restart the server and continue to work. There is a limit to the other arguments allowed when this option is specified. Form ID or name. and action are required together.1 861 Failed to purge pending list file. contact Remedy Customer Support Services for assistance in determining the cause of the problem. The server for the full text search (FTS) search feature (arservftd) was terminated by a signal. Refer to the AR System C API Reference Guide for more information. an error occurred while attempting to purge the list of pending changes. Refer to the Developing AR System Applications: Advanced guide for information about the expected arguments. Determine if there is already a copy of arservftd running. When specifying an operation against a specific request. In this case. An associated error message describes the details of the failure.Action Request System 5. You have not provided the minimum set of arguments. You have exceeded the limit. The mail message specifies a submission to a form that is not the form specified as the required form in the mail configuration file. and there is no default form configured for the armail daemon. The system encountered an error while attempting to access the configuration file indicated on the command line. Failure occurred while accessing mail configuration file. A command line argument that requires a value was specified but no value was provided. The retry argument has been specified for the full text search (FTS) indexer process. 956 957 Action Request System Error Messages ! 85 . Review the message and verify the format against the formats shown in the Configuring AR System guide. Correct the reported problem. the file specified does not exist (can be a misspelled file name. An associated message contains more details about why the file could not be accessed. In this case. You must supply an appropriate value for the argument. one or more of the arguments that are not allowed have been specified.1. or a default form must be configured for the armail process. and issue the command again. Otherwise. armaild is supported only on IBM AIX platforms. 952 953 954 955 Missing value for command line parameter. There is a limit to the other arguments allowed when this option is specified. one or more values must be provided. 951 The submitted mail message did not contain a form name. Refer to the AR System C API Reference Guide for more information. For the 5. or the file has been moved). The submitted mail message did not contain a body providing details for the new entry. The submitted mail message had a format that was not recognized. The submitted mail message specified a form that does not match the required form.Error Messages Guide 869 Too many arguments specified for the retry argument. Usage: armaild [ -f filename] [ -n number-of-intervals ] [ -d ]. No text exists in the body of the mail message to specify values to be assigned for the new entry. These are the UNIX command line options for running armail manually. To create a new entry by using the mail daemon. The message can be resubmitted with a form specified. this error message is now obsolete for 5. The format of the mail message does not match the format that is expected.1 release. A user has attempted to submit a request to another form. The mail message does not contain a line identifying which form is the target of the submission. This daemon has been configured to support submissions to only a single. The message can be submitted again with the additional information added. specific form. Most likely. does not exist in the mail system. Use the Request ID number for querying or modifying the request. The maximum number of allowable matches are returned. armail could not log off from the post office. Use a valid address. specifying the -x command line option to connect to a specific server. 959 961 Your submission was accepted by the AR System. The submitted email message successfully created a request in AR System. The process must be able to successfully connect with at least one server. Ensure that the mail system is still accessible. 967 Could not log off from the mail post office. This daemon has been configured to support submissions to only a single specific server. no requests were found that match the query conditions specified. the server or AR System on that server is not active.Action Request System 5. but no server was found. The return includes this message and the data for the specified maximum number of entries. Could not read mail from the mail post office. 968 Attempt to send mail to the mail post office failed. The armail address specified is not considered unique within the mail system. Ensure that the mail system is still accessible. The armail attempt to log on to the mail post office failed. The server specified for this message is not a recognized server—access was attempted. armail could not read a mail message from the post office.1 958 The submitted mail message specified a server that does not match the required server. However. No matches were found to your query request. the criteria specified matched more entries than the limit configured for the armail process. The mail message specifies a submission to a server that is not the server specified as the required server in the mail configuration file. The number of matches to your query request exceeded the configured limit of <limit>. The address indicated is either ambiguous. 964 armail failed when trying to log on to the mail system. When querying through the mail interface. To: <destination>. Verify that the Mail login and password given during installation are valid and that the mail system is accessible. or is not accessible. A user has attempted to submit a request to another server. ID for the new request is <Request_ID>. 965 966 Could not resolve the armail address. 971 972 86 "Chapter 2—Action Request System Error Messages . and ensure that the mail system is still accessible. When retrieving data through the mail query interface. The armail process was run. or specify a parameter and value to go with the option. Remove the option. No common functional currency exists to use in relational operation. You cannot allocate memory on startup. 1003 Action Request System Error Messages ! 87 . One or more parts of the definition are missing. this error message is returned if there is no numeric value contained in the string or if the decimal number is invalid. When converting a character value to a currency value. The -e or the -i option was specified as the last option on the command line. and one or more requests were found. The -p option was specified as the last option on the command line. However. In general. Both of these command line options require the name of the macro that is to be run at start-up. You can recover memory by shutting down unneeded processes. 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. Restart the server. This is an internal error that probably indicates the system is low on resources. See your administrator to get the necessary permissions so you can see the data you are trying to retrieve. 982 983 998 999 1000 1001 1002 The -p option requires a substitution parameter and a value. The format for the -p option is -p name = value. Unable to free shared or exclusive lock on user cache hash list. restarting processes that have been running for a while will help by recovering space those processes may have leaked over time. so you cannot see any data returned from your search. you do not have access to any of the fields in the report. or specify a macro to go with the option. This command line option requires that the name of a parameter and the value for that parameter be supplied. The system encountered an error during a call to allocate memory. You specified a quick report format. 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. This error is returned when a shared or exclusive lock cannot be released due to unexpected events in the server. This error is returned because no common functional currency was found when comparing currency constants with functional currency data. Remove the option. In addition. Bad currency value. The -p option requires the name of a parameter followed by an equal sign followed by a value. The -e and -i options require a macro name. Unable to free shared or exclusive lock.Error Messages Guide 973 No fields in the query list are accessible to you for this form. so only one can be specified on the command line at any time. Parameters can be specified only if you specify a macro first. it is in a directory named arHome under your UNIX login directory.Action Request System 5. 1007 You cannot connect to the X server. View the permissions on the file to ensure that you have read access (and write access if you intend to update the configuration file). Verify the setting of the ARHOME environment variable if you have defined an alternate directory. one or more servers must be defined by using the -x command line option. Two startup macros have been specified. there is not a window system running in your environment. there is no macro defined (by using the -e or -i options). If there is no ARHOME environment variable set. and restart the aruser program. Start a windowing system. specify the macro that uses them. The program cannot read the contents of that file. 1008 The macro name in a parameter is longer than the maximum allowed length. 1009 1010 88 "Chapter 2—Action Request System Error Messages . Specify a legal macro name defined in your system. 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. The macro name specified on the command line is too long. The maximum length for a macro name throughout AR System is 30 bytes. However. Currently. Refer to the Developing AR System Applications: Basic guide for information about command line options. 1005 1006 You cannot read the configuration file—ARHOME variable may be set incorrectly. No servers are defined for the AR System in the directory file. The aruser program on UNIX is an X program. Both the -e and -i options specify macros to be run. AR System Windows User Tool allows a maximum of one macro to be specified at startup. You can specify a macro that runs other macros if desired. You have specified a -p command line option that specifies values for parameters in a macro that is to be run at startup. 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.1 1004 Unrecognized command line option. The specified command line option is not recognized. If you specify parameters to be used in a macro. It requires that an X windowing system be running to allow the program to operate. if starting the aruser program from the command line. Two or more startup macros have been specified on the command line. This information is useful for debugging active links. The preceding error occurred during execution of active link <active_link>. Enter the command again. Verify the syntax of the command line to ensure that you have not omitted required spaces between options. The -d command line option has been specified two or more times. 1016 The server name in a parameter is longer than the maximum allowed length. 1017 1067 1100 Server is not compatible with AR System Alert. No description. Enter the command again. This option can be specified only once. but no startup macro was specified using the -e or -i command line option. This message gives the name of the active link and the specific action within the active link where the error occurred. The server name specified in the -x command line option is longer than the maximum length allowed for a server name. This error is returned because the AR System Alert client only works with 5. action <action>. The -d command line option requires that you specify a directory. Enter the command again. 1012 The -d option requires a directory name. In general. or supplying an appropriate server name with the -x option. specifying only one -d command line option for the directory that contains the startup macro you want to run. You specified the -d command line option. you can ignore this message. 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 ensure that you have not omitted required spaces between options. 1014 A directory can be specified only if you specify a macro. Enter the command again. The process terminated unexpectedly. The Save operation was completed successfully. 1015 The -x option requires a server name. 1013 The directory name in a parameter is longer than the maximum allowed length. This message displays the request ID of the newly saved request. omitting the -d option if not needed or supplying an appropriate directory name. omitting the -x option (if not needed). The -x command line option requires that you specify a server name. The error occurred while running an active link. Request <Request_ID> was successfully created.Error Messages Guide 1011 Two directories for startup macros have been specified. omitting the -d option or specifying a startup macro with the -e or -i option. 1101 Action Request System Error Messages ! 89 .x servers. You do not have access to the request or to the fields you are specifying in the request. No matching requests (or no permission to requests) for qualification criteria. After the macro is saved. and re-enter your changes. you can exit without losing the macro. To save the macro you are recording. however.Action Request System 5. 1202 1203 1204 90 "Chapter 2—Action Request System Error Messages . The operation that was being performed generated a large number of error messages. The request you are attempting to save changes to has been modified by another user since you last changed it. Macros cannot record operations continuing from partial selections in a query list. This record has been updated by another user since you retrieved it. The contents of the query list are likely to be different when the macro is replayed. If you are updating a diary field. If you are changing fields where the data you enter is supposed to be the final value. click Exit. Include this directory in the export file if you choose to import the data. You have specified that you want to exit AR System Windows User Tool. This message notifies user when the attachments are exported to a directory for reporting. a macro recording operation is in progress. your changes do not overwrite changes made by the other user. click Cancel Exit. The text you have specified is too long for the field you are trying to update. No requests were found that match the qualification criteria you have specified. A recording operation is in progress—your current recording will be lost if you exit. Attachments for the report are exported under <directory_name>. retrieve the request again. The macro records the operation as if all the items in the query list were selected. 1201 New text is longer than the maximum allowed length—truncating to fit. There are two possible reasons that requests are not returned: ! ! 1103 1200 The criteria you specified do not match any requests. or you can cancel the operation (not save your changes). some of the messages have been suppressed. The most serious messages are displayed.1 1102 Additional errors were truncated. so the macro cannot reasonably record information about partial selections. However. The field has a maximum length defined. You can Save your changes over the changes of the other user. continue with the operation (saving your changes). Partial selections will become full selections on playback. If you do not want to save the macro and you want to exit the program. and the text that you have entered is too long for the field. and then save the macro. to avoid overflowing the screen. The extra text is truncated so that it fits in the target field. To keep your changes. and make it visible if you want to use it. To keep your changes. click Continue. then save the changes. You have made changes to the data on a Diary or a Text Edit window. You have made changes to the data on the form Item Properties associated with the Customize View window. One or more new fields have been added to the form. the window will change to the new form. 1207 1208 1209 1210 1211 1212 Action Request System Error Messages ! 91 . the operation is canceled and the window remains unchanged. To continue with the recording.Error Messages Guide 1205 New fields added or made accessible by administrator—added as hidden fields to local view file. If you cancel this operation. You have not saved changes on this screen—they will be lost if you continue. If you continue with the Dismiss operation. then save the changes. click No. A recording operation is in progress—current recording will be lost if you continue. If you continue with the Dismiss operation. all of your changes will be lost. click Yes. click Continue Recording. To discard the changes. You have made changes to the data on the current screen. However. click Cancel Dismiss. you have a customized view of the form. click Continue. The Search window is connected to a different form than the form being referenced in the window where you are performing the operation. You started recording a macro and then requested that the macro recording be canceled. If you continue with the Dismiss operation. all changes you have made will be lost. click Cancel Dismiss. then save the changes. You have made changes to the data on the current screen. Search window is now connected to a different form—continuing will change the current form. If you continue with the Next or the Previous operation. If you click Cancel Recording. To discard the changes. You have not saved changes on a diary or text edit window—they will be lost if you continue. all changes you have made will be lost. To avoid possible conflict with your customizations. An administrator has updated the form being opened. To discard the changes. To discard the changes. click Cancel Dismiss. and then save the changes. move it to an appropriate location. all of your changes will be lost. click Continue. You have not saved changes on this screen—they will be lost if you continue. the recorded operations are lost. You have not saved changes on the properties screen—they will be lost if you continue. the new field is added as a hidden field on your view. If you continue this operation. You can use the Customize View operation in AR System Windows User Tool to locate the new field. To keep your changes. To keep your changes. This message is issued only from the Modify All window. This operation will modify <number> entries. To avoid spurious submissions to the database and to prevent incorrect bulk modifications of data.1 1213 Multiple requests match qualification criteria—Information pulled from first matching request. and verify the operation you are performing. You have not saved changes on a diary or text edit window—the changes will not be included in the current save action if you continue. You can choose to overwrite the file or to cancel the Report operation. 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. To continue with the modification.Action Request System 5. leaving the existing macro definition intact. but AR System administrator defined AR System to display only the first matching request from the search. You have made changes to the data on a Diary or Text Edit window. click Continue. If the data is important. click Cancel. The name for a macro is a combination of the name and the directory it is stored in. Ensure that the server and client can use the client’s locale convention. Unable to find help for the specified field. and click Save on the current window again. A failure occurred while trying to retrieve Help text for the field. 1214 1215 1216 1217 1221 1222 1223 92 "Chapter 2—Action Request System Error Messages . The specified file already exists. More than one request matched your qualification. This message is displayed to indicate that the operation is complete and would have been performed if the macro recording was not in progress. click Continue. To not save the data in the Diary or Text Edit window. the Submit and Modify All operations are not performed when you are recording a macro. save the data in the Diary or Text Edit window by selecting Save in that window. Locale-sensitive operation done on the server may not conform to the client’s locale convention. You can choose to overwrite the existing macro if you want the new definition to replace the old definition. 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. Do you want to continue? The operation you are performing modifies many entries in the database. Macro recording is active—operation recorded but no database operation performed. You can have a macro with the same name in different directories without conflict. The data in these windows will not be included if you click Continue. The number of entries that will be modified is contained in the message. The file you specified as the target of your report already exists. and continue with the Save operation. Server cannot set the client locale. click Cancel Dismiss. If you do not want to modify multiple entries. Duplicate name for macro. or you can cancel the operation and change the name for the new macro. An associated error message provides details of the failure. Click Continue to continue with the operation and delete the macro. An error occurred while trying to expand the definition of a character menu. 1225 1227 1228 1229 1230 Action Request System Error Messages ! 93 . 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. You can choose to overwrite the existing user command if you want the new definition to replace the old definition. This prompt is issued (when you attempt to delete a user command definition) to ensure that you do not accidentally and permanently delete the wrong definition. The selected macro definition will be deleted. An associated error message contains the details of the failure. or you can cancel the operation and change the name for the new custom report. Failure trying to expand the character menu. This prompt is issued (when you attempt to delete a custom report definition) to ensure that you do not accidentally and permanently delete the wrong definition. or click Cancel to cancel the Delete operation and retain the user command definition. 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. Click Continue to continue with the operation and delete the custom report. You can choose to overwrite the existing custom report if you want the new definition to replace the old definition. or click Cancel to cancel the Delete operation and retain the macro definition.Error Messages Guide 1224 Duplicate name for custom report. The name for a user command is a combination of the name and the directory it is stored in. The selected custom report definition will be deleted. This prompt is issued (when you attempt to delete a macro definition) to ensure that you do not accidentally and permanently delete the wrong definition. Duplicate name for user command. leaving the existing custom report definition intact. or click Cancel to cancel the Delete operation and retain the custom report definition. You can have a user command with the same name in different directories without conflict. Click Continue to continue with the operation and delete the user command. 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. The selected user command definition will be deleted. or you can cancel the operation and change the name for the new user command. leaving the existing user command definition intact. The customized view is recognized and handled appropriately. The administrator has updated this form on an AR System 2. Your disk drive is almost full. You are running a 3.000 characters in AR System Windows User Tool for Windows. No action was taken.csv formats. but the operation was recorded and will replay on later use.0. close unwanted windows or applications. AR System Windows User Tool for Windows displays only 32. you will encounter Error 1242. If you change this request. any operation that utilized a global (Modify All) or unrecoverable (Delete) action was performed. You are currently running too many applications to operate AR System client tools efficiently. 1233 1234 1235 1236 1237 1240 The customized view for this form has been updated to AR System 3. you may encounter some problems.Action Request System 5. The disk containing the file you are writing is approaching its maximum storage capacity. When the macro was processed. If you add more characters to the field. it will damage the record.000 characters of help text. or . you cannot further customize this view.1 1232 Macro recording is active—modifications will be made to the entry but will not be recorded in the macro. only the first 32.rep file.x version of AR System Windows User Tool (the User Tool). Reset to the Admin view. File will be saved in Report File format. Your customized view cannot be updated using this tool. Character fields display only 32. If you continue with this mixed environment. Create space for the file if you want to continue with the operation. you will lose all information over the 32.000 characters are shown here. Text field is too long. . Consider adding more memory or reconfiguring your system resources.1 server. 1241 94 "Chapter 2—Action Request System Error Messages .000 characters are shown here. but the home directory you are accessing has a customized view created by a version 2. or create a new customized view with the current User Tool to correct the problem. you may experience positioning problems with buttons. please remove unwanted files. only the first 32. However. Your window resources are low. Do you want to continue? The current form is using a view customized with a AR System Windows User Tool (User Tool) version earlier than version 3. You are recording a macro in AR System Windows User Tool. This is not a recommended configuration.rep if none specified. This message appears if you are saving a report and do not specify . Help text is too long. If you choose to continue. Because of version translation limitations. The report definition defaults to saving the report as a .rep.arx. Default file extension is *.000 character limit and any changes that you have made.1 (or earlier) User Tool.0 format. you may need to reposition some buttons by using the Customize View function. If you continue. Shut down all tools other than AR System tools. This can be caused by permission problems in your ARHOME directory. the existing customized view will remain available. The file containing the cached definition for the form cannot be opened. and try the operation again. Verify that you have read and write access to the ARHOME directory and to the view files (files ending in. The file containing the user-defined defaults for the form cannot be opened. but you can customize the view again and continue with this new view without problems. No such form exists—make a selection from the list. cannot be opened. of a workflow log file. You cannot open definition file. you cannot further customize without reloading an Admin view from the server. Correct the access problem. 1243 1301 1400 1401 1402 1404 1405 Action Request System Error Messages ! 95 . Correct the access problem.arv). You cannot translate the group name in the Group List or Assignee Group field. You cannot open default file. and try the operation again. Verify the spelling. Verify that you have file or directory access permissions. you will lose your customized view. You cannot open view file. and spacing of the name to ensure that it is one of the legal group names. Correct the access problem. Verify that you have read and write access to the ARHOME directory and to the default files (files ending in . or they can be reloaded from the server. The workflow logging file specified in the logging options dialog cannot be opened. name (or both). and try the operation again. This error is reported when the path. This means that the name is not recognized as one of the groups defined for the system. The configuration file cannot be opened. Do you want to reload the form from the server? If you click Continue. as specified by the user in the workflow logging options dialog of AR System Windows User Tool.ard). Correct the access problem.Error Messages Guide 1242 You can continue with out-of-date customized view files. If you are continuing with the view from a previous version of the tool. Double-click a form from the list. The file containing the cached view for the form cannot be opened. You cannot open configuration file. The list contains all valid forms. capitalization. Verify that you have read and write access to the ARHOME directory and to the configuration file (config). You have entered an unrecognized form name. A group name specified in the Group List field (ID 104) or Assignee Group field (ID 112) cannot be translated. Verify that you have read and write access to the ARHOME directory and to the definition files (files ending in . If you choose not to continue. and try the operation again.arf). This means that all the customizations will be lost. These files are stored in your ARHOME directory (files ending in . Correct the problem. These files are stored in your ARHOME directory (files ending in . Correct the problem. and try the operation again. An error occurred while attempting to write to the view file for this form. A failure was encountered trying to open a temporary file. and try the operation again. An error occurred while attempting to read from the file identified in the error message. These files are opened in the directory /tmp. Correct the problem. An associated error message provides details about the failure. Correct the problem. Correct the problem.ard). An error occurred while trying to restore your previous view. and try the operation again. You cannot restore previous view. These files are stored in your ARHOME directory (files ending in . Correct the problem. An associated error message provides details about the failure. An error occurred while trying to reset your view. An error occurred while attempting to write to the user-defined defaults file for this form. You cannot reset user view. An error occurred while attempting to write to the definition file for this form. You cannot write to the view file. and try the operation again. 1407 1408 1409 1411 1412 1413 1414 1415 96 "Chapter 2—Action Request System Error Messages . You cannot open a temporary file. An associated error message provides details about the failure.1 1406 You cannot open the specified file. and try the operation again. You cannot write to the default file. You cannot write to the specified file. and try the operation again. An associated error message provides details about the failure. You cannot write to the definition file. The file indicated in the message cannot be opened.arf). You cannot read from the specified file. Correct the problem.Action Request System 5. An associated message provides details about the failure. An associated error message provides additional information about the failure. Correct the problem. An associated message provides details about the failure. and try the operation again. An associated error message provides details about the failure. and try the operation again. An error occurred while attempting to write to the file identified in the error message. and try the operation again. An associated error message provides details about the failure.arv). Correct the problem. An associated error message provides details about the failure. so no data is changed in any fields. Correct the reason for the failure. Fork operation failed. Correct the problem. The system is probably out of memory. You cannot open support data or cache file. A failure was encountered while trying to start a child process that is retrieving data for a field. 1417 1418 1450 1451 1500 1501 Action Request System Error Messages ! 97 .Error Messages Guide 1416 You cannot make a backup view.arv). The indicated operation will not be a part of the macro you are building if you continue. Failure occurred while trying to run a process to load a field value. and try the operation again. Cancel the recording operation. Correct the access problem. The system encountered an error during a call to allocate memory. Or shut down and restart processes that have been running for awhile. Correct the reason for the failure. An associated message provides details about the failure. 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. and try the operation again. An associated message provides details about the failure. An associated message provides details about the failure. and treat the error as if an Out of memory error occurred (see Error 1500). Out of memory. You cannot record operation: <operation_type> An error occurred while trying to add the specified item to the list of recorded operations. and begin recording your macro again. The child process was not started.arv). You can recover memory by shutting down unneeded processes. AR System Windows User Tool). An error occurred while trying to create a backup copy of the view file. The failure occurred on the client machine (the one running the aruser program. These files are stored in your ARHOME directory (files ending in . You cannot write to the specified support data or cache file. Verify that you have read and write access to the ARHOME directory and to the view files (files ending in. An error occurred while attempting to write to the support file for this form. The file containing the support file for the form cannot be opened. A failure was encountered while trying to start a child process. The child process was not started. The operation continues without creating a backup file. this process may help recover space those applications have leaked over time. and try the operation again. and try the operation again. Only selection type fields can have a field type of check box. specify a field type that is appropriate for the data type of the field. You requested a field type of check box for a field that is not a selection field. The view file for the form does not have a form name. Otherwise. An error occurred while attempting to create a field on the form. Only selection data types can be displayed using exclusive choice boxes (defaulting to text). specify a field type that is appropriate for the data type of the field. This error usually indicates a serious resource shortage for the application.Action Request System 5. The view file with the error will be deleted and reloaded the next time you access the form. The view file with the error will be deleted and reloaded the next time you access the form. Otherwise. The view file with the error is deleted and reloaded the next time you access the form. If a text field type is acceptable. You have specified an unrecognized field type for a field. you can ignore this message. Because a field clause was not found where expected in the view file. you can ignore this message. you can ignore this message. If a text field type is acceptable. specify a field type that is appropriate for the data type of the field. specify a field type that is appropriate for the data type for this field. You requested a field type of numeric text for a field that is not an integer field. View file format error: field clause. the format of the view file is not what is expected. Treat the error like an Out of memory error (see Error 1500). Only selection data types can be displayed using checkboxes (defaulting to text). you can ignore this message. If a text field type is acceptable. The field type for this field is text. Otherwise. The field type for this field is text.1 1502 Only integer data types can be displayed by using numeric text (defaulting to text field type). Only selection type fields can have a field type of exclusive choice. The form name found in the view file does not match the name of the form in the definition file. The field type has been changed to text for this field. 1503 1504 1505 1506 1507 1508 1509 98 "Chapter 2—Action Request System Error Messages . You requested a field type of exclusive choice (option buttons in UNIX) for a field that is not a selection field. Otherwise. If a text field type is acceptable. The field type has been changed to text for this field. View file format error: invalid form name. Only integer type fields can have a field type of numeric text. Unrecognized field type (defaulting to text). Cannot create new field. View file format error: missing form name. When processing the file contents after the end clause. Definition file format error: field clause. Definition file format error: invalid form name. Because the end clause of a form or active link definition was not found where expected in the view file. the format of the definition file is not what is expected. Definition file format error: character menus. Therefore. The definition file with the error will be deleted and reloaded the next time you access the form. the format of the view file is not what is expected. the format of the definition file is not what is expected. the format of the view file is not what is expected. View file format error: begin active link. Because an invalid clause was encountered in a field definition in the definition file. The definition file with the error will be deleted and reloaded the next time you access the form. The form name found in the definition file does not match the name of the form. 1511 1512 1513 1515 1516 1517 1518 1519 Action Request System Error Messages ! 99 .Error Messages Guide 1510 View file format error: field definition. The view file with the error will be deleted and reloaded the next time you access the form. Because a field clause was not found where expected in the definition file. an entry was found that was not the start of an active link. The view 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 with the error will be deleted and reloaded the next time you access the form. The view file with the error will be deleted and reloaded the next time you access the form. The only information expected after the end clause of a form is the definition of active links. The definition file with the error will be deleted and reloaded the next time you access the form. Because a menu definition that tries to jump more than one level in the menu hierarchy is present in the file. The view file with the error will be deleted and reloaded the next time you access the form. the format of the definition file is not what is expected. Because an invalid clause was encountered in an active link definition in the view file. The definition file with the error will be deleted and reloaded the next time you access the form. View file format error: invalid form or active link end. View file format error: active link definition. the format of the view file is not what is expected. The definition file for the form does not have a form name. 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. An error occurred with the definition of a character menu. Definition file format error: field definition. Total number of characters per line including margins is greater than maximum of 4096. an entry was found that was not the start of an active link and also not a character menu. Definition file format error: begin active link. A report cannot have lines with more than 4096 characters of text. Increase the page size. Definition file format error: active link. When processing the file contents after the end clause. Because the end clause of a form or active link definition was not found where expected in the definition file. View the definition for the field to verify the legal values. the format of the definition file is not what is expected. Total number of lines between margins less than minimum of five. or decrease the size of the right or left margin so that the total space available is at least 40 characters. The total number of spaces on the page between the right and left margins is fewer than the minimum of 40 characters. The specified selection value is not a legal selection value for the field. Unrecognized selection value. A report requires space for at least five lines of text on the page. Total number of characters per line between margins less than minimum of 40. 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. The total number of lines on the page between the top and bottom margins is fewer than the minimum of five lines. Therefore. 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. selection values are case-sensitive.Action Request System 5.1 1520 Definition file format error: invalid form or active link end. A report requires space for at least 40 characters of text on a single line. the format of the definition file is not what is expected. Increase the line length. The definition file with the error will be deleted and reloaded the next time you access the form. 1521 1522 1524 1525 1526 1527 100 "Chapter 2—Action Request System Error Messages . the format of the definition file is not what is expected. The only information expected after the end clause of a form is the definition of active links or of character menus. Because an invalid clause was encountered in an active link definition in the definition file. The definition file with the error will be deleted and reloaded the next time you access the form. or decrease the size of the top or bottom margin so that the total space available is at least five lines. Decrease the line length so that the total space available is no more than 4096 characters. The definition file with the error will be deleted and reloaded the next time you access the form. Remember. A failure when opening or writing to the file holding the custom operation is a common cause of this problem. Change the value of the X and Y parameters. 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. However. coordinates are out of range. and click Continue when the prompt warning of duplicate names appears. The X coordinate must be between 0 and 1500 inclusive. 1529 1530 1531 1533 1534 1535 1536 1539 Action Request System Error Messages ! 101 . No reference to a Status field can be found for this form. Cannot format diary entry. statistic result. Must specify a user name. If you are saving a new operation. You can dismiss this window without changing the login information for the current user. An error occurred while formatting the diary text for a field. You have requested a count statistic with a column layout without specifying a field name to count on. specify a user name. you have not specified a name for the operation. 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. Y. An associated error message contains details about the update failure. An associated error message contains details about the failure. You cannot specify a COUNT operation with a column layout without specifying a field name. The field name is used to determine which column to display the result under in a column-style. An associated error message contains the details of the failure. If you are saving an updated macro or custom report under an existing name. specify the name you are updating. Status field is not accessible—cannot display Status History. you cannot display Status History information. The X or Y coordinate value specified is out of the legal range for the coordinate. specify a new name in the Name field. An error occurred while trying to create a list of the forms that are available from each of the connected servers. The update of the custom operation failed. You must specify a user name to log in. Update of custom operation failed.Error Messages Guide 1528 Column headers will not fit within the space defined between top and bottom margins—total number of lines increased to the following value. You are requesting that a macro or custom report be saved. or both. X. Accordingly. Supply a name for your macro or custom report. Cannot query servers. and the Y coordinate must be between 0 and 3000 inclusive. This is an unexpected error. Specify the field name to identify which column the result will be printed under. To change the login information. Make sure that the spelling is correct. and perform the operation again. An error occurred in this request during a Modify All operation. a numeric value. The value specified for the field name must be a field defined for the form. Change the value to a legal decimal value. A field name is required for all operations except COUNT. Change the value to a legal time value. A numeric field contains a nondigit 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. and try the operation again. or one of the numeric or date keywords. The indicated value was entered as a value for a field with a data type of real. Use AR System Administrator to confirm the size limits of the field properties. 1541 1543 1544 1545 1546 1547 1548 1549 102 "Chapter 2—Action Request System Error Messages .Action Request System 5. Modify All operation failed during operation on request with ID <number>. These are the only types of definitions allowed in the field name for a statistical operation. You entered a nondigit character for a numeric field. You have entered an improperly formatted value for a date/time field. The value was entered in a field with a data type of decimal. The file system was not able to create or write to the file holding the definition of the operation. The value you specified for the numeric field is either smaller than the minimum size or larger than the maximum size. and all requests with IDs after the specified ID are unchanged. Value specified for field name not numeric or not a field. The value is not a legal decimal value. Details about the error are in an associated error message. Change the value to a legal real value. Correct the error. You have entered an improperly formatted value for a real field. and perform the operation again. The format of the time value is not recognized. An associated error message contains details of the failure. The value is not a legal real value. All requests with IDs previous to the specified ID (in the sort order) were updated.1 1540 Attempt to create macro or custom report failed—file system error. This name specifies the field the operation will be performed on. The value is not a legal time value. You have entered an improperly formatted value for a decimal field. Change the value to a legal integer value. You must specify the field name (or arithmetic operation) on which the operation will be performed. and update the field name request to be a legal operation. and try the operation again. You can specify digits only for integer (numeric) fields. All of the statistics operations (except COUNT) require a field name. The value was entered in a field with a data type of date/time. However. If you are saving an updated command under an existing name. specify the name you are updating. You are requesting that a user command be saved. Enter a command name. specify a new name in the Name field. You might get this error message for the following reasons: ! 1553 1555 1557 1558 1559 The macro or custom report does not exist. The second part of the command that provides the destination for the report is missing or is not recognized. The macro and custom report files cannot be edited. Cannot create user command—file system error. and then save the user command. You are requesting that a user command be saved. The report operation in a macro consists of several commands. Error in macro or custom report. 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. Define one or more macros before you open the Select Macro or Edit Macros windows. 1562 Second part of report operation missing or invalid. ! Record the macro or custom report operation again. An associated error message contains details about the failure. and then click Continue when the prompt warning of duplicate names is issued. If you are selecting the command from a macro. you have not specified a command to be performed for the operation. It may have been deleted or moved to a new location. Enter a command string to execute. Or. The requested user command cannot be located. Because there are no macros defined. An error occurred while trying to perform the operation specified in the macro or custom report.Error Messages Guide 1550 No macros are defined. Action Request System Error Messages ! 103 . the command has probably been deleted or moved by another user since you started the program. A common cause is a missing end statement or incorrect formatting of one of the command lines. However. you cannot run or edit a macro. This is a specific case of Error 1559. a macro may run another macro as one of the operations it performs. Error in macro or custom report. You cannot locate the selected command. the command has probably been deleted since the macro was recorded. and that embedded macro does not exist. The format of the file holding the macro or custom report does not match the expected format. you have not specified a name for the operation. If you are selecting the command interactively. If you are saving a new command. Specify the command you want to be executed when this user command is performed. You do not have access to the Status field for this form. you have not specified a directory in which to store the operation. Ensure that the correct options are set on the Stop Recording window. If they are correct. An unrecognized operation was detected in the custom report definition. The file specified for this operation is longer than this maximum. However. You cannot use a selection value name in Status History—you do not have access to the Status field. The maximum size for a file name is 255 characters.1 1563 Enter a directory to store the command in.Action Request System 5. Usually. The second part of the command that provides the destination for the statistics result is missing or is not recognized. You are requesting that a user command be saved. Define one or more custom reports before opening the Manage Custom Reports window. you have not performed any operations since you started recording. To reference a specific Status History value for this form. There are no custom reports defined. You cannot create new item. Accordingly. You cannot create a macro that does not perform an operation. the cause of the error is a lack of system resources. Perform the operations you want to record before saving the macro. use the 0-based selection index for the selection value you require. An associated error message provides details about the error. you cannot manage a custom report. A custom report definition can contain only operations related to a custom report. You are trying to save a macro that has no commands defined for it. The file name specified is too long. including the directory path and the name of the file. 1565 1566 1567 1569 1572 1574 1579 104 "Chapter 2—Action Request System Error Messages . you cannot use a status selection value name as the middle portion of a Status History reference. This is a specific case of Error 1559. No custom report formats are defined. Define a file name that fits within the size limit. specify a new name in the name field. Specify the directory you want this user command definition to be stored in. Unrecognized operation detected while loading a custom report format. Accordingly. If you are saving a new operation. Second part of statistics operation missing or invalid. The statistics operation in a macro consists of several commands. Empty macro definition. File name is longer than maximum allowed. Error in macro or custom report. An error occurred while trying to create the new definition on the Customize View window. 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. Unknown field referenced in search line. and perform the search again. A parsing error was detected in the search line. You must have fewer levels of nested operations within the search operation. The error is usually at or just before the position that is marked. and perform the search again. The only legal operator at this position in a search line is a relational operator (=. Closing parenthesis expected at this position. and perform the search again. Relational operator expected at this position. <. <=. Logical operator expected at this position. At this position in a search line.Error Messages Guide 1580 Missing closing quotation mark on a character string or name. you must double the embedded quotation mark. Action Request System Error Messages ! 105 . Correct the format for the line. or NOT). This message indicates that an error occurred and shows the portion of the string containing the error with a caret marking the location. There must be a balanced number of parentheses in the command. Correct the error. !=. Correct the format for the line. Correct the format for the line. a field reference or value is expected. This error often has one of the following causes: ! 1581 1582 1583 1584 1585 1586 1587 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. A closing parenthesis to match an open parenthesis specified in this command was expected at this position. and perform the search again. Correct the format for the line. The only legal operator at this position in a search line is a logical operator (AND. >=. Too many nested levels of parentheses in command. >. You must supply the ending quotation mark. and perform the search again. If the name or string contains a quotation mark that is the same type of quotation mark around the value. and perform the search again. There are too many open parentheses (maximum of 64 open parentheses active in the search line) at this position in the search line. or LIKE). The field referenced in the search line is not a recognized field on the current form. A field name or character string has an opening quotation mark as required. Unexpected character at this location in the search line. The search operation has become too complex. Correct the format for the line. OR. but there is no corresponding closing quotation mark at the end of the string. Field or value expected at this position. and perform the search again. and perform the search again. When a parameter contains data that expands. and ensure that it matches one of the legal selection values. and perform the search again. followed by a period. Correct the format for the line. Correct the format for the line. However.1). In either case. Overflow occurred while expanding the command line for an active link.Action Request System 5. Format of date or time value is not recognized. Overflow while expanding active link macro parameter (maximum expanded parameter is 4096 bytes). This application cannot customize the views of AR System forms created with versions prior to 3. A reference must be the name or ID of the Status History field. and spacing of the name to ensure it is one of the legal group names. Overflow occurred while substituting a parameter value for a macro parameter in a Run Macro action for an active link.2. 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. Correct the format for the line. This could be the command line for a Run Process action or for a $PROCESS$ operation in a Set Fields action. The value specified for a selection field is not one of the defined selection values for the field. 1589 1590 1592 1598 1600 1601 106 "Chapter 2—Action Request System Error Messages .TIME or 15. Verify the spelling and capitalization of the value specified. The portion omitted will default to an appropriate value. followed by a period followed by the keyword or index of a user or time reference (for example.Fixed. the format of the portion of time that is specified must match the rules for time stamps. Overflow while expanding active link process (maximum expanded command is 4096 bytes). the maximum expansion of the values is 4096 characters. Revise the parameter values that are passed to be fewer than 4096 characters. and perform the search again. Such views can be customized by using previous versions of this application. followed by the name or index (0-based) of the status selection value. Status-History. The format of a time value is not recognized. capitalization.0. Verify the spelling. The format for a status history reference is incorrect.1 1588 Value specified for selection is not one of the defined values for this field. Review the definition to ensure that the correct values are being specified. the command line contains more than the maximum of 4096 characters after expansion. 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. Format for status history reference is invalid. Use a previous version of the application to customize the view. Accordingly. There are no user commands defined. A value exceeded the maximum size of a value that is allowed within a report. Correct the active link to refer to an existing character menu. or divide the report into several pieces. Because the value will overflow the internal buffers used for reporting. To use the online help system under the UNIX environment. Set fields active link running a process failed. An active link has specified a new character menu for a field that does not exist. and create the report again. Active link attempting to set nonexistent menu—resetting to the default menu. An active link has specified a new character menu for a field. Value exceeded report maximum length. each of which references 50 or fewer fields in the statistical operations. Define one or more user commands before you open the Select User Commands window. The statistic operation is too complex—it references more than 50 distinct fields. you cannot run or edit a user command. 1603 1604 1605 1606 1608 1609 1610 Action Request System Error Messages ! 107 . or create the character menu needed by this active link. this operation has been defined so that no match generates an error. An associated error message contains details about the failure. The administrator configured the action to return an error if no matches were found. No user commands are defined. it cannot be included in the report. Correct the situation causing the failure. The reporting system supports a maximum of 50 unique fields referenced in statistical operations. The process that was run to get a value for a field has failed. However.Error Messages Guide 1602 No item matches active link conditions. and perform the operation again. the specified character menu is not defined. This is usually the directory named help under the AR System install directory. Specify a report that excludes the long field. You must set the environment variable ARHELP to point to the help directory. You have defined a set of statistical operations for a report that includes more than 50 distinct fields in the reporting criteria. or remove the active link. 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. Active link trying to set nonexistent field. The character menu for the field is being reset to the default menu for the field. set the environment variable ARHELP to point to the directory containing the help files for the AR System. Correct the active link to refer to an existing field for the form. Simplify the statistics you are gathering. This error message occurs when unexpected. or $SQL$.1 1611 Found more entries than expected during workflow processing. Cannot find this macro name in macro list. View has not been saved. The administrator configured the action to return an error if multiple matches were found. This functionality is supported only on the Windows environment. Data from these sources cannot be incorporated into a Push Fields source expression. $DDE$. close. Source used in Push Fields active link not allowed: PROCESS. Too many windows are open. 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. an error was encountered while attempting to update the view definition on the server. or write to the active link debug file. close unwanted windows or applications.Action Request System 5. An error occurred attempting to open. 1620 1621 1622 1624 1625 1629 1630 108 "Chapter 2—Action Request System Error Messages . An error occurred while updating the server. A macro specified that a report is to be generated to an external report writer. The list contains the first 6000 matching items. incorrect. Reporting to an external report writer is supported on the Windows platform only. To continue. The selection list opened by an active link operation contains more items than can be displayed. or SQL. 1612 1613 An internal error has occurred during workflow processing. Close some windows before opening another. There is insufficient memory available to open additional windows or applications. Your window resources are low. the source expression cannot contain $PROCESS$. or inaccurate definitions are encountered during processing. DDE. you cannot access a form because there are insufficient memory resources to open it. Not all entries are displayed in the selection list. This error message is returned when you attempt to access a macro that is not found in the macro list. Active link debugging is active. An associated message contains additional information about the failure. This message is usually accompanied by specific errors that explain the failure. During an export view operation. for example. This indicates a corrupted or incomplete definition. A message preceding this message contains details about the failure. In a Push Fields active link action. Cannot access the active link debug file. verify that the macro actually exists. There is insufficient memory available to perform basic AR System Windows User Tool functions. The system cannot read the recent search file. You cannot record a macro that logs in to an AR System server. This action is not supported. Incorrect format in the definition file.arf files) contain unexpected content. No report or an incomplete report will be generated. this statement is displayed. Login macro action is not supported.0 when attempting to connect to an AR System server version prior to 3. The system cannot save the search file. It usually indicates that the cached form definition files (the . Attempt the search using the advanced search capabilities of AR System Windows User Tool.0. Unable to write the saved search file.0. 1651 1653 1654 1655 1656 1658 1659 1660 1661 1662 Action Request System Error Messages ! 109 . Reformat your search to continue. This message appears as a hint in the error message box when a report error occurs. not all macro statements are supported.0 and later AR System servers can be used by AR System Windows User Tool version 4. This message appears when there is an error during report generation. This error message is generated by AR System Windows User Tool when loading a form. Attempt the search using the advanced search capabilities of AR System Windows User Tool. Only version 3. Run Macro was not executed because the macro contains statements that are not supported. Used by the Push Fields action when the administrator configures it to return an error when multiple matches are found. Unable to read the saved search file. Unable to read the recent search file. Reformat your search to continue.0.arv and . Error occurred in generating report. The system cannot read the saved search file.0 are not supported by this client. One or more items match active link conditions—this operation has been defined so that any match generates an error. Click Show Details in the message box for more information.Error Messages Guide 1650 Servers with versions earlier than 3. In ARWeb 4. the If Any Requests Match field has Display ‘Any Match’ Error selected. The system cannot save the recent search file. On the If Action page. Click Show Details in the message box for more information. This error is generated by AR System Windows User Tool version 4. If the macro cannot be executed. Unable to write the recent search file. Application designed for different operating system. You cannot create directory <directory_name>. AR System Windows User Tool could not open or create a printer setup file for a custom report. WinExec returned Error 12. and log in again. WinExec returned Error 0. During a Run Process active link action. Insufficient memory to start application. Ensure that you have a network connection to a server and that it is running properly. To operate AR System Windows User Tool. WinExec returned Error 2. WinExec returned Error 10. WinExec returned Error 15. System out of memory. Application developed for older version of Windows software. Unable to connect to any servers. AR System Windows User Tool failed to create a missing command directory on the local disk. During a Run Process active link action. WinExec returned Error 3. Path not found. During a Run Process active link action.Action Request System 5. WinExec returned Error 11. you must have access to at least one server. WinExec returned Error 8. WinExec returned Error 19. Attempted to load second instance of application. Executable not found. WinExec returned Error 5. During a Run Process active link action. 1801 1802 1803 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 110 "Chapter 2—Action Request System Error Messages . While storing a macro or report. Attempted to load compressed executable. There is insufficient memory available to allocate the form information structure. executable file was corrupt. During a Run Process active link action. During a Run Process active link action. WinExec returned Error 16. Incorrect version of Windows software. During a Run Process active link action. Close some open windows or applications. Cannot open file <file_name>. Invalid executable file format.1 1800 Internal error—unable to create form information. During a Run Process active link action. or relocation was invalid. During a Run Process active link action. During a Run Process active link action. Sharing or network protection error. During a Run Process active link action. The form definition files may be unavailable or corrupt. Invalid dynamic-link library. An MDI child window could not be created because an internal windows function provided an unexpected result that was detected during window creation. Form information could not be loaded. WinExec returned Error 21. 1823 1825 1826 1827 1828 1829 1830 Action Request System Error Messages ! 111 . An MDI child window could not be created because an internal windows function provided an unexpected result that was detected during window creation. AR System Windows User Tool could not retrieve notification information from the Alert client. Internal error—invalid window description. Form information could not be loaded. Form information could not be loaded. During a Run Process active link action.0. Unable to load Submit form. Form information could not be loaded. WinExec returned Error 13. Another error message documents the cause of failure. During a Run Process active link action. The form definition files may be unavailable or corrupt. this is because the Alert client is not responding. Unknown error—error code = <error_code>. WinExec failed. Internal error—invalid window description. During a Run Process active link action. WinExec returned Error 20. WinExec returned an unknown error code. WinExec returned Error 14. Unknown executable format. The form definition files may be unavailable or corrupt. The form definition files may be unavailable or corrupt. WinExec failed for <action_type>.Error Messages Guide 1816 1817 1818 1819 1820 1821 Application designed for MS-DOS 4. During a Run Process active link action. In general. Unable to load Customize Default form. Unable to load Customize View form. Unable to load Query form. Failed to display all or some of the notification messages. Application requires Windows 32-bit extensions. During a Run Process active link action. During a Run Process active link action. Invalid field name—attempt the operation again. Windows returned an LB error. The Y location and height of the symbol is greater than 3000.1 1831 Failed to create the dialog box. Internal error (1). The report to file or screen failed to generate. Initialization of the user information in uiroot failed during user login. An internal Windows error occurred while updating user login information. Internal error—unable to initialize user information. This usually indicates a serious disk problem. Specifically. This usually indicates a serious Windows error. AR System Windows User Tool ran out of memory while building the user information list when updating the login information window. You have entered an invalid field name in the report sort dialog box. Failed to display the report. Windows provided an invalid LB index. The status history modeless dialog box could not be created because of a Windows error. AR System Windows User Tool has run out of memory while building the statistics list for the statistics report window. Memory failure—cannot initialize the current statistics information. Could not create an AR System home directory while updating user login or server information. The X location of a field was made greater than 1500 in the Display Attributes dialog box. Specifically. An internal Windows error occurred while updating user login information. 1832 1833 1834 1835 1836 1837 1838 1839 1840 The X location and width of the symbol is greater than 1500. Internal error (2).Action Request System 5. AR System Windows User Tool ran out of memory while allocating the schemaInfo structure during user login. This usually indicates a serious Windows error. Internal error—unable to create form information. 1841 1842 112 "Chapter 2—Action Request System Error Messages . Failed to create the AR System home directory <directory_name>. Failed to create memory. The Y location of a field was made greater than 3000 in the Display Attributes dialog box. Unable to register submit window class. reports. During application startup. This usually indicates a serious Windows error. it was detected that Windows is not running in enhanced mode. During application startup. This usually indicates a serious Windows error.ini file cannot be located. Ensure that you have enough disk space. AR System Windows User Tool could not initialize user information lists (macros. The user home directory in the ARuser section of the win. and so on) because memory allocations for lists failed. AR System Windows User Tool globals could not be initialized. You have encountered an unusual error condition. AR System Windows User Tool could not open the specified report output file.ini file for the last user logged in to AR System.Error Messages Guide 1843 Failed to get printer information. During application startup. 1850 1852 1853 1854 1855 1856 1857 1858 Action Request System Error Messages ! 113 . You have encountered an unusual error condition. You have encountered an unusual error condition. 1844 1847 1848 1849 Not enough memory to initialize font. Action Request System requires Windows enhanced mode. Unable to register window class. it was detected that the Windows working directory has not been set to the AR System application directory. AR System Windows User Tool ran out of memory while building the font preference structures during font preference dialog box initialization. During application startup. Printer driver initialization for the printer selected in printer setup has failed while printing a report. Report to file failed. Unable to register query window class. This condition is detected during application startup. Failed to initialize the system globals. The working directory must be the same as the program path in File > Properties. Not enough memory to initialize all fonts. This usually indicates a serious disk problem. A home directory path was not found in the win. Failed to create the user home directory <directory_name>. Creation of a home directory for the last user has failed during application startup. AR System Windows User Tool ran out of memory while building the font preference structure when changing AR System font preferences. Failed to initialize the user information. Unable to register queryList window class. You have encountered an unusual error condition. Creation of the MDI frame window failed during AR System Windows User Tool startup. Unable to register custom windows class. User or password data is incorrect or irretrievable from win. Unable to register text viewer window class. You have encountered an unusual error condition. Windows API initialization has failed during AR System Windows User Tool startup. 1869 1870 1871 1875 1876 Internal Error—LoadIniFile.1 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 Unable to register child window class. AR System Windows User Tool for Windows failed to load menu accelerator tables during startup.ini file during AR System Windows User Tool startup. You have encountered an unusual error condition. You have encountered an unusual error condition. 114 "Chapter 2—Action Request System Error Messages . Unable to register customize default class. DDE API failed during AR System Windows User Tool startup. AR System Windows User Tool ran out of memory while allocating the schemaInfo structure during startup. Failed to initialize DDE. Unable to create frame. Unable to register Dialog2 class. Unable to register report window class.Action Request System 5. This usually indicates a serious Windows error. Internal Error—unable to create form information. You have encountered an unusual error condition. You have encountered an unusual error condition. You have encountered an unusual error condition. You have encountered an unusual error condition. You have encountered an unusual error condition. Unable to register customize view class. This usually indicates a serious Windows error. Unable to register text view class. Unable to load the menu accelerators. Unable to initialize APIs. Form information could not be loaded. the specified item could not be found in the notification application. The customize view grid width and height parameters are not within the allowed range. the DDE entry for the target application in the dde. While reporting to an application. Form information could not be loaded.ini file. Blanks and spaces are invalid in a view name.ini. DDE action other than EXECUTE.ini is invalid—you can specify only CSV or TAB for format. The <item> item is missing from application section <section> in dde. Error in reading the GetDetails Information for list item number <item>. Set Fields active link running a process through DDE failed. DDE connection failed due to incorrect application file path setting. DDE Target application entry was not found in the dde. 1884 1885 Memory allocation failure during DDE process. The specified item is missing from the DDE target application entry in the dde. 1886 1887 1888 Action Request System Error Messages ! 115 .ini file while building DDE file specification for a DDE operation. Unable to load Query form: <schema_name>. The form definition files may be unavailable or corrupt. POKE. Grid width and height must be between 2 and 128. The form definition files may be unavailable or corrupt.ini file does not specify CSV or TAB format.ini file while building DDE file specification for a DDE operation. The DDE application name is not defined in dde. 1878 1879 1880 1881 1882 1883 The format for the application section in dde. or REQUEST DDE action was specified. No description. AR System Windows User Tool ran out of memory while allocating memory to support a DDE action. While processing a notification get details DDE request. Invalid DDE action specified.Error Messages Guide 1877 Unable to load Submit form: <schema_name>. A DDE-invoked process failed and did not provide data to be used as the source of a Set Fields active link. Failed to connect to application <DDE_application_name> using <specified_DDE_path> path. using a time within the allowed range. AR System cannot process dates prior to 01/01/1970 or after 02/05/2036. AR System cannot process dates and times that are out of range.Action Request System 5. There may be a resource or memory limit on the client. Unable to load menu. Cannot perform this operation in the current mode of the form.DLL is required. Failed to create the window. The system is out of memory or resources while running active links. Date and time are out of allowed range of <number> through <number>.1 1889 Date is out of allowed range of 01/01/1970—02/05/2036 for Windows client. The system is out of memory or resources. Time is out of allowed range of <number> and <number>.DLL version <old_version_number> is an old version. Unable to initialize frame. The login was aborted because all open windows could not be closed. Indicates a serious problem with menu loading. Try again with a different mode of the form. Terminate unused applications in order to make system resources available. AR System cannot perform this operation in the current mode of the form. You cannot close all windows. the menu did not load. Creation of the main MFC frame has failed during Windows user tool startup. AR System cannot process a time that is out of range. Login aborted. Reinstall the latest version of the AR System Windows User Tool or AR System Administrator. Character menu expansion failed in the symbols library. Version <current_version_number> of MISCDLL. Character menu expansion failed in the symbols library. This is often caused by a lack of space in the Windows resource heap when loading large menus. Try again. Enter a date within the allowed range. Try again. This usually indicates a serious Windows error. Error loading menu. Could not create a new child window. the menu did not load. Failure trying to expand character menu. Currently running MISCDLL. using a date and time within the allowed range. 1890 1891 1892 1893 1894 1925 1926 1930 1950 1951 1952 116 "Chapter 2—Action Request System Error Messages . This may be the result of installing an older version of AR System client tool (User or Administrator) in the same directory as a newer version. Functions MAX and MIN are not supported in Push Fields actions. The application resource memory area is probably full. The failure usually indicates an incorrectly installed mail system. Error creating a menu—menu too large. Cannot commit changes to a dialog box or to a submit or a modify record action. Without knowledge of the destination data type. Unable to commit changes. This error occurs when the MAPI mail system failed to initialize when sending an AR System object to a mail recipient. Failed to build the Windows popup menu. these two functions cannot be evaluated correctly. Failure loading group information. Cannot write file <file_name> to disk. Adding a submenu to a menu has failed and resulted in a Windows error. Unable to load help. AR System Windows User Tool failed to get the group list from the server. The field editor could not open a file with write permissions. Group list expansion has failed while trying to build the group list. Functions MAX and MIN are not supported in Push Fields actions. Unable to create work buffer for file <file_name>. Windows Help system failed to load. Error creating menu—out of resources. Failed to initialize MAPI mail. Writing to a file failed in the field editor. Unable to read file <file_name>. Currently Push Fields actions provide little information about the destination field.Error Messages Guide 1953 1954 1955 1957 1958 1959 1960 1961 Error getting group information. Unable to write to file <file_name>. You are trying to access a menu with more than <number_of_entries> entries—the menu will be truncated. The number of items returned for a menu load exceeded the maximum allowed. The field editor could not open a file with read permissions. Allocation of global memory failed while performing edit operations. 1962 1963 1964 1965 1966 Action Request System Error Messages ! 117 . This is usually caused by the failure to create a temporary file. There was a failure opening an external viewer (for example. Verify the syntax in the SQL command. A report cannot be printed. The specified directory is not valid. The directory specified while saving a macro cannot be created. Failed to save file <file_name>. Add the new directory? The directory specified does not exist. Too many fields have been selected in a Column type report. The given directory does not exist. This is likely caused by a file system error. Crystal Reports) during the print preview operation. This error occurs when the Crystal Report Engine returns less data than requested. Ensure that all column titles fit into one report line. The SQL command passed to the Crystal Reporting Engine is invalid. The directory may not exist or the user may not have access rights. Due to the length limit of the SQL command by Crystal Reporting Engine. This error occurs when the MAPI mail system failed to send the mail when sending an AR System object to a mail recipient. The message was not sent. Printer error occurred. 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 118 "Chapter 2—Action Request System Error Messages . This is usually caused by problems with your printer setup or with cables. only the first <number> entries are reported.Action Request System 5. Create the new directory? The directory specified while saving a macro does not exist. The directory specified in a file path is not valid.1 1967 Send Mail failed. Report will not be displayed in specified external program because of the following error: <type_of_error>. Too many columns (fields). This note gives the user a chance to abort AR System Windows User Tool termination. One or more active links failed when closing the form. The directory cannot be created. The given directory does not exist in the search path. an active link failed on window close. Do you still want to exit the application? When exiting AR System Windows User Tool. Verify the printer setup on your system. The report format is reset to Record. The report type is being reset to Record mode. An I/O error occurred while generating a report to file. The Crystal report contains an invalid SQL statement. the system could not connect to any of the specified servers. Associated error messages provide information about why the tool could not connect. No servers are currently accessible. 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. then restart the tool. and restart the tool. It requires that an X windowing system be running to allow the program to operate. None of the servers specified in AR System Administrator are currently accessible. 2002 2003 You cannot connect to the X server. Ensure that ARHOME is correctly set and that you can read and write to the config file. Start a windowing system. Try the operation again after the issues have been resolved. AR System Administrator cannot start without a server to connect to. or are using Windows.Error Messages Guide 1980 2001 A printer error occurred. Cannot read the configuration file. and then restart the aradmin program. Currently. The aradmin program (AR System Administrator) on UNIX is an X program. Failure occurred during a call to initialize AR System client environment. The default page setup is used. there is not a window system running in your environment. If you did not use the -x command line option. Failure while retrieving entries from the server directory file. so printer defaults are being used. 2005 2006 2009 Action Request System Error Messages ! 119 . 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. An associated error message contains details about the failure. In general. You can recover that memory by shutting down unneeded processes. An error occurred while retrieving entries from the server directory file. 2004 You cannot initialize the AR System. Page setup could not be determined. In addition. Cannot allocate memory. The system encountered an error during a call to allocate memory. the AR System directory file is empty or contains references to servers that are not currently accessible. if you used the -x command line option to identify one or more servers. On UNIX. or the permission settings are such that you cannot access it. restarting processes that have been running for a while will help by recovering space those applications may have leaked over time. Correct the problem reported. The UNIX configuration file (config) is missing. remedy.Action Request System 5. You have not saved changes on this screen—they will be lost if you continue. If you proceed. but that field number is within the range of reserved fields (100 to 536870911) in the AR System. The Import operation in AR System Administrator is used for structure definitions only. Ensure that you have specified the correct name for the file you are trying to import. ignore this message and proceed. the system could not find a field with the specified name for the current form. use AR System Import. leave the field ID blank to automatically generate an available ID outside the reserved range. For unlimited capabilities. No structures are in the import file. Your filter definition and all associated actions will be deleted.1 2100 You have specified a field ID within the reserved range. contact your Sales Representative or visit www. When specifying a field reference using the field name. the operation will be terminated.com. If you cancel. You are deleting a filter. Incorrect parameter specification—verify field name spelling. choose an ID outside of the reserved range (greater than or equal to 536870912). and the definition will be retained. the tool did not find any AR System structure definitions in the file. A Delete operation removes the definition. Your form definition and all associated data will be deleted. but be aware that the field may have a special meaning. If the window is closed. the operation will be terminated. 2101 2102 2103 2104 2106 2107 120 "Chapter 2—Action Request System Error Messages . You are now trying to close the window. If you cancel. the workflow associated with the definition (such as filters and active links). Correct the spelling of the field name in the reference. You are deleting a form. This means that there is nothing that can be imported. This server <server_name> is not licensed from Remedy and has limited capabilities. A Delete operation removes the definition and the workflow associated with the definition. Click Cancel to cancel the dismiss action and retain the window and its information. arimport. This error occurs when the server reports an invalid license during login verification. You can create a field in this range. When trying to load this file. If you proceed. and the definition will be retained. If you are creating this field to have the special meaning. If you do not want to create a specific reserved field. all changes since the last Save will be lost. You are attempting to assign an ID number to a form field. You specified a file to be used during an Import operation. the definition will be removed. If you are running AR System Administrator. the definition will be removed. You have made one or more changes on the current window since changes were applied. and ensure that the field exists for the target form. and all the data associated with the definition. If you are trying to import data. If you proceed. the operation will be terminated. and repeat the operation to see if the other errors remain. Correct those errors. Since changes were last applied. The following fields (including data). A Delete operation removes the definition and the workflow associated with the definition. 2112 2114 The following field labels are duplicated in your form. Changes on the following screens will be lost if you continue. A request has been made to close or dismiss the parent window. Your menu definition will be deleted. Because it can be confusing to have fields with duplicate labels. Deleting active links will remove the workflow associated with the active link. If you cancel. A Delete operation removes the definition. and the menu definition will be retained.Error Messages Guide 2109 Your active link definition and all associated actions will be deleted. Click Cancel to stop the Delete operation from being performed. If you proceed. A Delete operation removes the action definition. Additional errors were truncated. You are deleting a filter action. Your filter action will be deleted. Deleting fields will delete the associated data for the fields and requires restructuring the table in the database. you have made one or more changes on a window that is a child of the current window. The language defined in the LANG environment variable is not recognized by AR System. The field labels identified in the message are used for multiple fields on the form. active links (or both). duplicate labels are allowed. The most critical errors are displayed in the current dialog box. all changes since the last Save will be lost. Because fields are uniquely identified by field ID. consider changing one of the labels. and the definition will be retained. the definition will be removed. Click Cancel to cancel the dismiss and retain the current window. Proceed with the Delete operation to continue. The operation encountered a number of errors—too many errors to fit in a single dialog box. 2115 2117 2119 2120 2121 Action Request System Error Messages ! 121 . If you proceed. The fields and the active links affected are listed as part of the message. and their information. You are deleting an active link. If the window is dismissed. the action definition will be removed. You have requested that one or more fields or active links be deleted. and the action definition will be retained. You are deleting a character menu. the operation will be terminated. the definition will be removed. its children. The default language of the server will be used instead. the operation will be terminated. Language defined by LANG environment variable not recognized—using default on server. If you cancel. will be deleted. If you cancel. You are logged in as a subadministrator—access to some structures and functions has been disabled. the operation will be terminated. the action definition will be removed. and the definition will be retained. FTS search capability will be disabled while the operation is in progress. A Delete operation removes the action definition. If you proceed. Your form view will be deleted. You are changing the timing setting for an escalation from calendar to interval and there is a calendar screen open on the system. If you proceed.Action Request System 5. Choose a unique name for the view. If you proceed. The name of an administrator view must be unique for the form. The calendar screen is not appropriate when using an interval time setting. You are deleting an escalation. A Delete operation removes the view definition. Your escalation action will be deleted. If you find that you are not allowed to perform a specific operation. If you cancel. the operation will be terminated. You are deleting an escalation action. the view will be removed. the action definition will be removed. 2123 2124 2126 2127 2128 2129 2130 122 "Chapter 2—Action Request System Error Messages . This prompt enables you to cancel the operation or to specify that the open window be closed. Your form view name is not unique. Users using this view will be reset to the default view the next time they connect to the system. the definition will be removed. A subadministrator does not have access to all of the functions on the tool. If you cancel. perform reindex operations during off hours whenever possible. and the view will be retained. You selected the full text search (FTS) reindex operation. A Delete operation removes the action definition. it is probably because you do not have sufficient permissions. the operation will be terminated. You can log in as an administrator to get full access.1 2122 Your active link action will be deleted. Your escalation definition and all associated actions will be deleted. You are deleting an administrator view of a form. Another view exists with the same name. and the action definition will be retained. If you cancel. Because this operation can take a long time and performance of the system may suffer. You are deleting an active link action. If you proceed. the operation will be terminated. The full text search (FTS) reindex operation can take a long time. A Delete operation removes the definition and the workflow associated with it. and the action definition will be retained. You are logging in to the system as a user who is a subadministrator. If you cancel. You currently have an escalation time specified. A Delete operation removes the mapping definition. You have activated the full text search (FTS) subsystem of AR System. if you are deleting a field. 2132 2133 2134 2135 2136 2137 2138 Action Request System Error Messages ! 123 . If you proceed. In addition. The user attempting to obtain access does not meet these criteria. 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). Deleting the form may affect the functionality of DSO. the user must be assigned a fixed write license. A request has just been made to close or dismiss the window. a new form that contains all the distributed fields will be created. Click Cancel to cancel the dismiss and to retain the window and its information. When the system is restarted. the field you are deleting is one of the fields that make the current form a DSO form. A Delete operation will remove them from the set of operations to be performed. The selected distributed mapping will be deleted. The selected pending mappings will be deleted. You have made one or more changes on the current window since changes have been applied. these items will be retained. Changes on the mapping fields screen will be lost if you continue. If you cancel. the definition will be removed. The data types of a pair of values in a qualification line are not compatible.Error Messages Guide 2131 Incompatible data types in qualification line. Full text search (FTS) index operations will be started. In the qualification line. When you restart the system. the operation will be terminated. all changes since the last Save will be lost. Or. If you cancel. the server automatically recreates the form. If the window is dismissed. and the definition will be retained. You must be a member of the Administrator or Subadministrator group with a fixed license to use this tool. You are attempting to delete a Distributed Server Option (DSO) form or field—do you want to continue? The form you are trying to delete is one of the special DSO forms. Deleting this field will make this form unavailable as a DSO form. You are deleting a distributed mapping. The distributed operation that was initiated against these items will be removed. Items that are pending indexing will begin indexing immediately. You have selected one or more pending mapping definitions to be deleted. All operations that require updating the FTS index will be queued and performed when the system is activated again. You are deactivating the full text search (FTS) subsystem of AR System. Full text search (FTS) index operations will be shut down. ensure that operations are performed only between items with compatible types. and the packing list will be retained. and so on. the application will be removed. you will only delete the AR System web service object and not any underlying XML schemas or WSDL handler URLs. If you continue. if you proceed. The authoring environment will check to ensure that this situation is brought to the attention of the user if it exists.Action Request System 5. Are you sure you want to continue? The form you are trying to delete is a base form for one or more join forms. System does not ensure consistency if global elements/complex types in use are changed. Proceed at your own risk. But because a packing list is really only a container of AR System objects. You are deleting an application. your changes will be saved automatically. You are deleting a web services object. You are deleting a packing list. Your packing list will be deleted. that are contained in the packing list. and the application will be retained.1 2139 Changes in current view will be saved if you continue. This warning is returned when you add a Form (Between open and close services) to an existing web view and try to save it. the operation will be terminated. the guide will be removed. Continue only if you want all dependent forms to be deleted. Open and close services are the start and end of a form respectively. If you proceed. You have applied changes to a form that contains one or more fields with blank labels. Please choose 'embedded' option if you are not sure. Deleting this form will cause forms that depend on it to be deleted. Because join forms are dependent on this form. Your guide will be deleted. the operation will be terminated. the operation will be terminated. 2140 2141 2142 2143 2144 2145 2146 2148 124 "Chapter 2—Action Request System Error Messages . You are deleting a guide. This view contains one or more intersecting FORM declarations. Any FORM tags inserted by the user must not overlap on the open and close service tags. You are trying to change views without having saved your changes to the current view. Other forms depend on the current form. This is a limitation of the authoring environment that does not allow nested or intersecting FORM declarations. all such forms will be deleted if you delete the base form. If you proceed. and the web service will be retained. The system does not guarantee any consistency. If you cancel. Your application will be deleted. If you cancel. the operation will be terminated. If you cancel. If you cancel. and the guide will be retained. If you proceed. 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. Your web service will be deleted. The following field names or IDs have blank labels in your form. workflow. deleting the packing list does not delete any underlying forms. The system encountered an error during a call to allocate memory. The type specified for the field is not recognized.Error Messages Guide 2149 'Public' access is not specified. More than one Sync Search Database command cannot be issued from the same instance of AR System Administrator. AR System Administrator failed to import the required forms while setting up the Search database. In general. you attempted to put check boxes on a field other than a selection field. You can recover that memory by shutting down unneeded processes. Only integer can use numeric text type. You cannot allocate memory. If the error persists. and try the Set Up Search Database command again. Verify the server status. Could not load the definition file from the resource. This form cannot be saved. The definition file of the search database in AR System Administrator did not load. 2200 2202 2203 Only selection type can use check box. Please select a unique name for this field before saving the form. and save the form again. While defining properties for a field. because two or more fields have the same database name. Only fields with the data type Integer may be of numeric text type. Additionally. call Remedy Customer Support Services. this error occurs when there are too many processes running or when some processes have grown to occupy more. This error can occur if a server exits unexpectedly or fails to import because of some other server-related cause. You cannot issue a Sync Search Databases command for the same (or different) servers at the same time from the same instance of AR System Administrator. All other changes are not saved. of the available memory on your client machine. Ensure that each field has a unique database name. Field <field_name> has a duplicate name. Unrecognized field type. Close and reopen AR System Administrator before you try the operation again. or all. 2205 2206 2207 2208 2209 Action Request System Error Messages ! 125 . you attempted to assign the field type Numeric Text to a field other than an integer field. Open another session of AR System Administrator to perform these operations simultaneously. Incompatible data types in qualification line. Only fields with the data type selection can use check boxes. 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. This will force users to login before accessing wsdl. While defining properties for a field. Update the definition of the field to indicate a valid display type for the field. Set Up Search Database command failed during Import. restart processes that have been running for a while to help recover space those applications may have leaked over time. An associated message contains more details. An associated error message contains more details. The range for the X coordinate is 0 to 1500. Button field is missing an active link assignment. An associated error message contains additional information about the failure. The range for the Y coordinate is 0 to 3000. Select an item. An error occurred while attempting to open a file. Specify the name of a user so you can log in. Review the associated error message for details. The file specified to receive the exported definitions cannot be opened by the tool. The system could not connect to the servers. Resolve the error. and click Delete. Change the coordinate to a valid range. An error occurred while attempting to open your configuration file. therefore. Correct the error. An associated message contains details about the error. Enter a form name. all buttons in a form must have an assigned active link. To delete a field or active link. Cannot query servers. 2219 2220 2228 2231 2232 2234 2236 2241 2243 2269 126 "Chapter 2—Action Request System Error Messages . A problem was encountered while trying to build the GUI structure to represent a field on a screen. X or Y (or both) coordinates are out of range. In the pre-3. This compatibility error occurs when you use a 3. you cannot select the Delete operation. and click Save. The X or Y coordinates you specified for the layout of a form field are not in the valid range. Specify the name of a form so you can complete the specifications for the window. To perform an import or export operation. You cannot open the specified file.1 2214 You cannot open the export file. Enter a name.0 (or later) UNIX Administrator Tool or AR System Administrator to connect to a pre-3.0 server. This error can be the result of an access problem or of a nonexistent directory. A selection is required. select the item.Action Request System 5. and repeat the operation. Enter a user name. and try the operation again. You cannot open configuration file. Try the operation again when the error has been corrected. Form definition problem: invalid field specification. An error occurred while trying to retrieve the list of forms available to the new user.0 AR System. select one or more items to be imported or exported. No field or active link is currently selected on the window. and click Save. Missing closing quotation mark on a character string or name. Save all work on the current window. and click Save. You have not specified a form for the structure you are creating. If a quotation mark is contained within a string. the message number is outside of the allowed range. If you receive this message. You must select at least one operation. The error message should no longer be displayed when you reopen the character menu definition. You must specify the form to which the structure is attached. Exit the tool and start the tool again. Enter a label. Correct the message number. save all work on the current window. An associated message contains information about the position within the line where the unexpected character was encountered. No data entered at previous menu level. You must select a form. Enter a name. Enter a filter name. The message number is invalid. When parsing a line. You must enter a label before selecting Insert or Modify. for the filter you are creating. You have not specified an operation for the filter or escalation to execute. and reselect the desired operation. Select an operation and click Save. You have not entered a name. Unexpected character found. When creating a message type action. The error message should be dismissed when you reopen the character menu definition. You must specify one or more operations. Review the string for the missing quotation mark. an open quotation mark was encountered.Error Messages Guide 2279 Cannot delete the selected item from the list during a cut operation. you must double the contained quotation mark. User messages have message numbers of 10000 or greater. which is required. When parsing a line. an unexpected character was encountered. 2281 2283 2284 2285 2286 2287 2288 2290 2291 Action Request System Error Messages ! 127 . You must enter a label for a menu item that you are creating prior to selecting Insert or Modify. No data entered at selected menu level. and exit the window. An internal error occurred while attempting to remove an item from an internal list. There is no menu definition at the selected level in the menu. There is no menu definition at the previous level in the menu. but no corresponding closing quotation mark was found. and exit the window. An associated message contains information about the position within the line where the operation was expected.Action Request System 5. a conditional operation was expected but not found. When parsing a line. An associated message contains information about the position within the line where the parenthesis was expected. The format is controlled by the default LANG setting and can be overridden by using the ARDATE environment variable. When parsing a line. When parsing a line. a closing parenthesis was expected. but it could not be translated to a known field for the current form. Format of time value is not recognized. and enter only the appropriate parameters. a value for a selection field that was specified was determined to be not one of the legal values for the field. Review the definition of the function. A closing parenthesis expected at this position. An associated message contains information about the position within the line where the operation was expected. a field or value reference was expected. a relational operation was expected but not found. The format of the specified time value is not recognized. 2293 2294 2295 2296 2297 2298 2299 2300 128 "Chapter 2—Action Request System Error Messages . Value specified for selection not one of defined values for this field. You have entered too many parameters in a set fields assignment. Too many nested levels of parentheses in command. When parsing a line. An associated message contains information about the position within the line where the function of the extra parameters can be found. a reference to a field was encountered. The message contains information about the position within the line where the field reference can be found. the system supports a maximum of 64 levels of nested parentheses. A relational operation expected at this position. When parsing a line. When parsing a line. The function definition contains more parameters than are allowed. Unknown field reference found.1 2292 A conditional operation expected at this position. When parsing a line. An associated message contains information about the position within the line where the field or value was expected. Ensure 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 string being parsed has more than 64 levels of nested parentheses. A field or value expected at this position. An associated message contains information about the position within the line where the selection value can be found. A filter can contain a maximum of 25 actions. and try the operation again. You have created the maximum number of active link actions allowed. create a new active link with the same conditions. so the new actions run after the existing actions. save all work on the current window. 2304 2305 2306 2308 2309 2310 2311 2312 2313 Action Request System Error Messages ! 129 . The field is not fully defined until it contains one or more values. Error encountered writing to file. Specify both a directory and file name. An internal error occurred while removing an item from the menu. Ensure that you have specified the required information in the fields you are assigning. and click Save. You have not specified a name for the active link you are creating. Character menu Delete operation failed. on a Set Fields window. You have created the maximum number of filter actions allowed. An associated error message contains the details about why the write operation failed. You have not specified a form for the active link you are creating. The file name specified is longer than the maximum file name supported by the system (up to 255 characters). Selection fields require one or more values.Error Messages Guide 2301 Specify a directory and file name. and click Save. You must specify the form to which the active link is attached. specify one or more fields to receive a value. and exit the window. and add actions in the new filter. create a new filter with the same conditions. You must specify a directory and file name to open a file. Enter an active link name. select Dismiss to skip this action. For example. An error occurred while trying to write to a file. Please enter data. Enter a name. Correct the problem. Specify an execution order that is greater than the current active link. Resulting file name is longer than maximum allowed. To perform additional actions. A name is required. You are already at the maximum number of actions allowed. You are already at the maximum number of actions allowed. and add actions in the new active link. You must select a form. An active link can contain a maximum of 25 actions. Specify an execution order that is greater than the current filter so the new actions run after the existing actions. There is no data entered on the current screen. A selection field requires that one or more values be specified. If you receive this message. To perform additional actions. If you do not want to specify data. The error should be gone when you reopen the character menu definition. and click Save.1 2314 Select a field for your Execute On condition. Enter the value again in one of these formats. This is required when you execute on Return or on Menu Choice. 2315 2317 2319 2320 2321 2322 2323 2324 2325 130 "Chapter 2—Action Request System Error Messages . 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). Fields in this range are reserved for the core fields that are created and managed automatically by the system. For compatibility.Action Request System 5. Unrecognized arithmetic operation. While parsing a qualification line. Select an execution condition. Select an execution condition for your active link. a name was encountered that is not a recognized group name. or group list longer than maximum allowed. and click Save. an error occurred. You must specify one or more occasions for active link execution. This message contains information about the position of the error in the line. and continue with the operation. and click Save. you can use those field IDs for fields with compatible definitions. The internal field length may not be less than zero. While parsing an assignment line. The value entered where a real value is expected is not in legal format for a real value. Unrecognized group in group list. Integer and real fields can contain only digits (except for real values in legal scientific notation). Real values can include a single decimal point or can be in scientific notation. An integer or real field contains a nondigit character. Select a field to attach to. The length specified by a character field must be greater than or equal to zero. an error occurred. You have entered a nondigit character for a numeric field. While parsing the contents of a Group List or Assignee Group field. This message contains information about the position of the error in the line. or the total length of the field exceeds 255 bytes. Field IDs below 100 are reserved for core fields. Assignment line error at position <location>. You have not specified when to execute the active link. Correct the problem. The arithmetic operation specified is not legal in the current context. Qualification line error at position <location>. The execution condition requires that a field be selected to attach the operation of the active link to. You cannot create a new field with an ID less than 100. You have entered an improperly formatted value for a real field. Change the ID to be unique. An error occurred while formatting your diary text. The system default connects to the first server listed in your configuration file. There are no macros available to the administrator for creating a macro-type action for an active link. If you are using AR System Administrator. escalation. 2328 2329 2331 2332 2334 2335 2336 2337 2338 Action Request System Error Messages ! 131 . Use the ARPATH environment variable to point to alternate locations for macro definitions. you can leave the field ID blank for the new field. You cannot change the type of an existing action. You can change other aspects of the definition. You must specify at least one If action. You do not have a known server specified in your configuration file—the tool will default to the first server specified in your directory file. Total width of your fields exceeds the maximum. You cannot change type of an existing action. You have not specified a form for the filter you are creating. One or more of the names specified in the Get list or Index list is not a valid field name for the current form. Your configuration file has registered that you were last connected to a server to which you no longer have contact. or active link. There are no If actions defined. The ID for every field must be unique. to be within the maximum width of 128 bytes. The total width of all the fields specified for Get List fields is greater than the maximum of 128. There are no administrator macros defined. You must delete the existing action and create a new one. No If actions have been defined for the filter. but the change history is not available. If you are using AR System Administrator. Review the definition stored in the database. Create at least one If action. An error occurred while trying to format the change history information for the structure.Error Messages Guide 2326 You have specified a field ID already in use. You must select a form. One of the field names is invalid. You have specified an ID that is in use by another field. you can leave the field blank. Review the width specified for each field and the width of the separators and adjust. Verify the spelling of the names to ensure that you have specified legal fields. The field ID is illegal. as needed. You must specify the form to which the filter is attached. Change the value to be in the legal range. Ensure that the macro you want to run is defined. The ID specified for the field is outside the legal range of field IDs. and a legal ID will be created automatically. and a legal ID will be created automatically. You can run the macros one after another within the same macro. Create the custom mapping again. If a macro nests to include other macros.1 2339 Delete operation failed. A value with an incompatible data type that cannot be converted has been assigned to a field. You have specified two or more values that are the same. Too many levels in nested macro. The macro you are using has more than 15 levels of nested macros. or there is a problem within the database with the storage of definitions. unrecognized. 2340 2341 2342 2343 2345 2348 2349 2350 2351 132 "Chapter 2—Action Request System Error Messages . The values specified for a selection type field must be unique. The macro specified is not in the correct format and is. you have assigned the mapping a name that is already used by another mapping. The system cannot tell the difference between the two values if they are the same. Invalid mapping definition—respecify your custom mapping. Duplicate mapping name—rename your distributed mapping. Enter a value that is within the legal range for a 4-byte integer. An error occurred while performing a Delete operation. You must specify a value with a compatible (or at least convertible) data type. An associated message contains more information. Review the documentation for the expected format for the DDE line. and rename the mapping. Return to the Modify Distributed Mapping window. Invalid macro definition file format. therefore. Field data type and assignment data type are not compatible. The format of this definition has been manually changed. You cannot expand menu <menu_name> for field <field_name>. The tool could not decode the mapping definition for the custom mapping. You must specify a valid macro definition. Selection values must be unique. An associated message contains additional information. You have entered a value in your integer field that is outside of the legal range for integers. The format of the DDE assignment line that is used within a Set Fields operation is not valid. While creating a distributed mapping. and correct the line. Mappings must have unique names. An error occurred while attempting to retrieve and build the indicated menu for the specified field. The value for an integer field is outside the range for a 4-byte integer value. but they cannot be nested more than 15 levels deep. Invalid parameter specification in the DDE assign line.Action Request System 5. the maximum number of nested levels of macros is 15. the message is displayed if you entered 1/1/2075 as a date. An active link already exists in this form with the name: <active_link_name>. You are connected to the system as a subadministrator. the time zone from which all other time zones are adjusted. Enter a value that is within the legal range for an 8-byte real field. <name> is not recognized as a legal component of the date or time format string. To specify a custom mapping or to view a menu of forms. You must be an administrator or be given sufficient access by an administrator to create and modify distributed mappings. 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. If you enter a date outside of the listed range. you will receive this error message. wait until the server is available again. Change the name of the active link so that it is a unique name. <name> is not a recognized <month_or_day>. The value in a real field is outside the range for an 8-byte real value. Specify the assignment of one or more fields. and you do not have access to the Distributed Mapping form to allow definition of Distributed Mappings. For example. GMT here is Greenwich Mean Time. Set operation failed. You have entered a value in a real number field that is outside the valid range for real numbers. The number must be between <number> and <number>. The Set Fields action is not defined to assign values to fields. The names of all active links must be unique. You do not have permission to perform Distributed Server Option (DSO) operations. Get operation failed. You have not entered data for any of your fields—enter data for at least one field before clicking the Save button. An error occurred while the tool was attempting to set a property for a field. Date is out of allowed range of 01/01/1970 to 01/19/2038 (GMT) for Windows Client. <number> is not a valid number for the date <date>. This message is displayed if the format string you specified in the Control Panel is illegal.Error Messages Guide 2352 One of your mapping servers is not available or does not exist. 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 Action Request System Error Messages ! 133 . This is an out-of-range error. Because the server specified as the source or the target of the mapping is not available. An error occurred while the tool was attempting to retrieve a property from a field. This message is displayed if you misspell a month or day name. An active link with the same name already exists. and . 2366 2369 2370 2371 2372 2373 134 "Chapter 2—Action Request System Error Messages .bmp. Try again later. ! For more information about table fields and forms. the column representing the field ID will be removed from the table field. Server <server_name> for table field <table_field_name> is not accessible at this time. If you Save the form. See the Developing AR System Applications: Basic guide for more information about table fields. The qualifier for the table field may be improper. . This error occurs when you try to save an application without providing a name. Table field <table_field_name> has no columns.dib. Form <form_name> on table field <table_field_name> does not exist on server <server_name>. refer to the Developing AR System Applications: Basic guide ! For more information about servers.jpg. This message indicates the table field does not find a field ID referenced by a column in the table field. refer to the following server documentation: ! Configuring AR System ! Optimizing and Troubleshooting AR System ! AR System Database Reference Guide. Add at least one column before you create or modify this table field. The table field tried to connect with the listed server. The listed columns for the <table_field_name> table field do not have corresponding data fields. If you choose to proceed. Enter an application name. See the Developing AR System Applications: Basic guide for more information about table fields. This message indicates that one or more columns in a table field do not match field IDs in the corresponding form. This message occurs when you select an invalid file type for the image you want to associate with an application. Table fields must have at least one column. This error message is returned because the form has been deleted from the server. and AR System Database Reference Guide. See the Developing AR System Applications: Basic guide for more information about table fields. but the server is not running. Optimizing and Troubleshooting AR System. Valid file types include . . you will delete this field. All columns with no matching field IDs will be removed from the table field when the table field is modified.jpeg. refer to the following server documentation: Configuring AR System.Action Request System 5. Enter an application name before you save the application. For more information about servers.1 2365 The table field <table_field_name> definition is corrupt. Unable to save an image for the application. You have encountered an unusual error condition. While trying to log in and connect to the specified servers.ini file. Error getting filter list. The error occurs when AR System Administrator is unable to complete an operation because it failed to obtain an escalation list from the current server. 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.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. 2405 2408 Action Request System Error Messages ! 135 . Reading of user preferences from ar.ini failed.ini file. or if you are not an administrator or subadministrator user for the server. Close the dialog and try the operation again. when the network is too slow (leading to a time-out). While trying to initialize the user preferences. AR System 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. Failed to initialize the system globals. 2380 2381 2382 2383 2401 2403 2404 Unable to connect to any servers. The error occurs when AR System Administrator is unable to complete an operation because it failed to obtain a filter list from the current server. Error getting escalation list. Change the name of the new mapping or delete the existing mapping. AR System Administrator failed to successfully connect to a server. Unknown error code <error_number> encountered. You must supply a non-NULL value for the Database ID. Close the dialog and try the operation again. Close the dialog and try the operation again. This can occur when the server is down. The error occurs when AR System Administrator is unable to complete an operation because it failed to obtain an active links list from the current server. Error getting active links list.Error Messages Guide 2374 Duplicate distributed mapping name. Ensure that the ar. This can be due to an invalid or missing home directory for the selected user name. Unable to initialize user information. This message appears when you try to save a distributed mapping with an existing distributed mapping name.ini file or the specified directory may not exist. The user home directory is missing from the ARuser section in the win. The message with error code <error_number> is missing from the string table. DLL is required. Installing an older AR System client tool (AR System Windows User Tool or AR System Administrator) in the same directory as a newer one may cause this error. Close one or more applications to continue. Failed to create the AR System home directory.DLL version <old_version_number> is an old version. User Name is missing. Specify a value for the field on the form to continue. 2416 2417 2418 2419 2420 2421 2422 2423 2426 Server <server_ name> not found in server list. You selected Execute On: Menu Item/Button in an active link without associating it with a menu item or button on the form.1 2412 Currently running MISCDLL. Ensure that the path is valid and that the disk is not full. and log in again. The selected file is not a valid BMP (bitmap) file. You cannot save a Set Fields action without specifying a value for a field on the form. You cannot access a server that is not specified in the list of servers you are logged in to. You must specify a user name while trying to save user information in the Login Information dialog box. You must specify a home directory while trying to save user information in the Login Information dialog box. AR System Administrator could not allocate memory for its data structure. Reinstall the latest version of the AR System Windows User Tool or AR System Administrator. Failed to load the selected image file. You cannot delete an object that you are currently editing. 136 "Chapter 2—Action Request System Error Messages . filter. Failed to create memory. and try the deletion again. or form that is currently open. At least one field must have a value in a Set Fields action. AR System Administrator failed to create the specified user home directory. escalation. Add the server to your server list in the Login Information dialog box. or it is larger than the supported size of 15 x 16 pixels. Select an appropriate file to continue. You cannot delete an active link. AR System home directory is missing. Close the window in question. Version <current_version_number> of MISCDLL.Action Request System 5. You must specify a menu or button field for active links that execute on a menu or button. but cannot be left blank.2 (or later) to import files larger than 30. In an SQL menu definition. UNIX server. Supply a value index (greater than 0). Button field is missing an active link assignment. Could not remove all the specified pending operations.x Administrator Tool or AR System Administrator into a 2. Specify an SQL command. AR System Administrator may have failed to allocate memory to save the list of forms. This will not be validated in any way. Supply a label index (greater than 0). you must specify the column number of the SQL query result that will be used to create the menu itself. If you have selected more than 300 fields on the screen. you must specify an SQL command.000 bytes using AR System Administrator for Windows. This message occurs when the server has a problem deleting the pending operation after you click Remove in the Pending Distributed Operations dialog. Select fewer fields. UNIX servers prior to version 2. or there may be a network connection problem. Enter an SQL command to continue. but cannot be left blank. In an SQL menu definition. You have selected more fields than will fit in the clipboard. Any number greater than 0 will be accepted. To save an SQL menu definition. Enter an SQL command to continue.0. To save an SQL Set Fields Action. Supply an SQL command. This will not be validated in any way. the specified button field was not associated with an active link. must be upgraded to version 2.2 do not support importing data larger than 30. AR System Administrator failed to read the list of forms on the current server. Select 300 or fewer fields to continue.Error Messages Guide 2427 The following fields do not have valid values set: In an existing Set Fields action. You must assign an active link to the button field (or delete the button) before you can save the form. 2428 2431 2432 2433 2434 2435 2436 2437 2438 Action Request System Error Messages ! 137 . Cannot read forms for server.0. While saving a form using a 3.000 bytes from AR System Administrator for Windows. <server_ name>. This can occur if AR System Administrator cannot allocate enough memory to get the fields’ value or if the fields’ data type is no longer valid. AR System Administrator found some fields whose values are no longer valid. you must specify an SQL command.x server. and try again. you cannot use the Edit → Copy operation. 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. and Closed. Values set to <new_value>. remember that names are case-sensitive. Assigned. You must enter a distributed mapping name. Remove the field from the view to continue. The Value field will be set to the first member of the set of legal states. You must enter an escalation name. you did not specify a name. When creating an escalation. you must enter this information. and server.1 2439 The following field cannot be displayed in this view because it contains invalid properties. you have specified a numeric value that is out of range for that field. Specify a new name for your view. Remove it from this view by using the Fields In View dialog box. When specifying a Distributed Delete DSO Action for a filter. The name you have specified is used by an existing view. Close some applications. If you have selected this option. Another view already exists with that name. form name. you have the option to specify the length of time to retry. one or more of the field mappings is incorrect. you did not specify a name. Enter a distributed mapping name to continue. Unable to display unmapped fields. you have specified a string value for an enumerated field that does not represent a valid state. Get list of fields operation failed. When creating a distributed mapping. You have tried to Show Unmapped Fields in a custom distributed mapping. The floating palette tool bar used to create new fields could not be created because Windows has run out of memory. A value must be entered for the following fields: Request ID. The Value field will not be set. Form. you cannot set Status to Done if the legal states are New. and Server. you must provide a request ID. Insufficient resources to create the palette. When defining a Set Fields action in an Active Link. 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 138 "Chapter 2—Action Request System Error Messages . For example. When defining a Set Fields action in an active link. <value> is not a valid value for field <field_name>. The server may have failed after you logged in to it. Note that <value> is outside the range for field <field_name>. You must specify the hours or minutes (or both) to retry a distributed operation. When defining a distributed mapping on the Options page. The current custom mapping is not valid.Action Request System 5. Your attempt to get a list of fields from a server has failed. The specified field in the current view has missing or invalid display properties and cannot be displayed in the view. or restart your Windows session. Enter an escalation name to continue. 2454 2455 2458 2459 2460 Action Request System Error Messages ! 139 . A maximum of 1985 items can be exported at once. These fields may not contain a combination of single and double quotation marks. so one of these must not exist in the field. the Mapping. the Request ID. This error occurs when the administrator attempts to make any column of the results list wider than 128 characters.Error Messages Guide 2450 The field can contain double quotation marks (“) or single quotation marks (‘). You must have at least one field with a value in a push field action. 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. but it cannot contain both kinds of quotation marks. To avoid this error. AR Runtime will get or set the value of the $fld$ and will treat this field as an OLE pointer variable. because those values are stored already surrounded by either double quotation marks or single quotation marks. This is a special parameter in which you can only add another method which returns this object type. Select a fewer number of items. This error message occurs if you have defined an OLE method that has a parameter of type pointer. and the To Server fields may not contain a combination of double and single quotation marks. This is a special object parameter in which you can only add another method which returns the same object. If the Distributed Delete option button is selected. You attempted to export definitions for more than 1985 items. The parameter can only be filled by nesting another method whose return type is compatible. export fewer than 1985 items at one time. If the Distribute Transfer option button is selected. Specify a value for the field on the form and try again. 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 Form. This error message occurs if you have defined an OLE method that has a parameter of type object (IDispatch). 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. You can also use $fld$ to enter the value for a pointer parameter. 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. The width of a results list field and its separator combined is limited to 128 characters. and try the operation again. This error occurs when you attempt to save a Push Field action without specifying a push field value for a field on the form. 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. Form. and Server fields may not contain a combination of double and single quotation marks. Cannot be inserted by clicking the Add Method button. AR System Administrator will attempt to map it to the OLE methods parameter OLE type. and the containing object of the child method differs from the return type object of the parent method. This error occurs when you place your selection on one of these data structures and attempt an Add Method operation. The Parent return type is not an Object. You get this error message when you try to nest a method that returns a pointer. Please select a method to delete. this error is returned. Please select another one. The constants. if the pointer is incompatible with the parameter pointer type you want to nest. AR System Administrator validates whether the return type is of type object. Cannot add the method. This error occurs when you attempt to add or nest a method. When you provide a value for a parameter. You can call or nest another method out of this return type only if the return type is of type object or object pointer. Type incompatible. and other data structures that are displayed in the type library tree are for display purposes only. Please select a matching function. Please select a method that returns a pointer. the parameter must be of type pointer.1 2461 Please select a matching function. When you nest a method to a parameter. 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.Action Request System 5. This error occurs when you attempt to add or nest a method to a parameter. 2462 2463 2464 2465 2466 2467 2468 2469 2470 140 "Chapter 2—Action Request System Error Messages . Looks like the return type of the method selected and the method to be added are incompatible. AR System Administrator returns this error message explaining that the value cannot be converted to the native OLE parameter type. The Constants and properties are for display only. You cannot add a method here. VARIANT. Please type in a proper value. You cannot call another method on the parent method. enums. Try again. or Compatible. The Parameter or Return value is of wrong type. When you nest a method. the parent method’s return must be one of the following types: IDispatch. and the return value is incompatible with the parameter's native type. This error occurs when you have defined an OLE method that returns a pointer and you try to nest an incompatible return type. If unsuccessful in the conversion. This error occurs when you click Delete Method without first having selected a method. Incompatible objects. The two pointer types do not match. If the parent method’s return type is not one of these types. Labels within guides must be unique. Please enter a non-empty string in label and name fields. a method must be a nested parameter either at the parameter level or at the return level. and locale. Enter a unique name to continue. and you try to add a method by clicking Add Method when the selection is at the return node. Please enter a server name. Select a packing list. A label must be unique and consist of one or more characters. providing a name that has not yet been used in the guide. platform. An error is returned because you attempted to create a view without a label or name. and you selected Enable Workspace. You cannot enter a value in the return value node. To continue. Right-click and select a field. You must specify a name when creating or modifying a packing list. platform. Enter a server name to continue. Enter a packing list name. create this view with a different combination of label. Please give the entry a unique name. Right-click to select a Field. Predefined searches cannot have duplicate names. You cannot have duplicate named predefined searches. The value you entered meet the criteria determined by the administrator. No work space has been selected. you can nest another method. but you did not select a packing list. Rename the label. The administrator defines the number of places to the right of the decimal point (precision) for a given field. 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 Action Request System Error Messages ! 141 . To continue.Error Messages Guide 2471 Can delete only methods at the root level. The administrator may also define the high and low range for values entered into the field. An error is returned because the view you are creating contains the same combination of information as another view. You selected View > By Workspace. You have entered an improperly formatted value for a decimal field. Cannot edit return value. specify a view label and name. To be deleted. This message occurs when the Server Name field in an Open Dialog action is empty. You can't add methods to a return value. and try the operation again. This error message occurs if you have defined an OLE method that has a return value. If the return type is an object. There is already another view with the same label. and locale combination. You do not have the proper permissions to access the file <file_name>. the HTML file generation stopped because the file could not be accessed. The current working directory cannot be removed. There was a hardware error. your drive is corrupted or you are trying to write to a network drive and the network is down. for example. There was an error trying to set the file pointer. the HTML file generation stopped because there are no more directory entries. Bad Path: <path_directory> When deploying an application. There was an attempt to use an invalid file handle. When deploying an application. When deploying an application. When deploying an application. Attempted access to file <file_name> produced a sharing violation.1 2482 An unspecified error occurred. the HTML file generation stopped because the HTML file could not be created. the HTML file generation stopped because 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 error trying to set the file pointer. When deploying an application. When deploying an application. the HTML file generation stopped because the permitted number of open files was exceeded. an unspecified error was returned in generating HTML files that was not covered under errors 2483 to 2495. the HTML file generation stopped because the file is either corrupted or the file is open in a non-shared mode. The file <file_name> could not be located. the HTML file generation stopped because the current working directory cannot be removed. When deploying an application. When deploying an application. The number of directory entries for directory <path_directory> has been exceeded. the HTML file generation stopped because a shared region was locked. When deploying an application. When deploying an application. 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 142 "Chapter 2—Action Request System Error Messages . the HTML file generation stopped because all or part of the path is invalid. There was an attempt to lock a region that was already locked. When deploying an application. The permitted number of open files was exceeded. the HTML file generation stopped because there was a hardware error.Action Request System 5. Error Messages Guide 2494 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. 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. 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. 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. 2495 2501 2502 2503 2504 2505 2506 2507 Action Request System Error Messages ! 143 Action Request System 5.1 2508 The status field must have a default value. If you continue the default value will be changed to the first entry. Do you want to continue? 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. 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, AR System 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. AR System Administrator failed to read a field for the form you selected for an active link or filter. Ensure that AR System Administrator can still connect to the server that the form is on, then try again. 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. 2509 2510 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 144 "Chapter 2—Action Request System Error Messages Error Messages Guide 2523 2524 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. 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). 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. 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. 2525 2526 2527 2528 2531 2532 2533 Action Request System Error Messages ! 145 Action Request System 5.1 2534 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. AR System 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. 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, AR System 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. Active link <active_link_name> is already used by <button_name>. It can not be added to <button_name>. This version of AR System server does not support moving an active link from one button to a different button. To continue, create a new active link. 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. 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. 2535 2536 2537 2538 2539 2540 146 "Chapter 2—Action Request System Error Messages This error occurs when you open a set field active link action. 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 correct this problem. Please remove some forms from the selected form list. To delete Distributed Fields. One or more fields have been deleted from the form that will affect Setfield list. Select none.Error Messages Guide 2541 This form contains a non-standard set of Distributed Fields. When you attempt to delete an OLE method. Distributed Fields will be deleted. and press OK. You can select a maximum of 10 forms through the Selected Form option of the By Form Dialog Box. Please enter a form prefix. Use the Distributed Fields dialog box to recreate a standard set of distributed fields in your form. Distributed Fields will be deleted. you did not enter a prefix before clicking OK. This message indicates that you have selected more than 10 forms. An inconsistent set of distributed fields is present in your form. Select a form. 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. full. 2542 2543 2544 2545 2546 2548 2549 2550 2551 Action Request System Error Messages ! 147 . then click OK. AR System Administrator warns you that all of the subsequent methods (if nesting has been done) 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. Please add at least one form to the selected form list. Distributed fields are system-generated and cannot be mixed-and-matched. or advanced to return to a standard set of fields. basic. A maximum of <number_of_forms> forms can be selected. You have selected the Selected Form option in the By Form dialog box but did not select any forms before clicking OK. Please press the Modify Action button to rectify the problem. and some of the fields that are used in the setfield/value list box have been deleted from the form. select None in the Distributed Fields dialog. Warning: All the subsequent calls will be deleted. When you selected the Form prefix option in the By Form dialog box. Save the filter or escalation only if you are sure of what you are doing. click Modify Action. This message occurs when there is an incorrect data type associated with distributed fields. perhaps because one or more fields was deleted. Selecting this option could cause an infinite loop in the system. The entry mode selection will be set to default. refer to the Developing AR System Applications: Basic guide for available field types. The precision is out of bounds. This warning is noticeable the first time a form is imported and when the form's views are changed. In order to improve this view so that it looks the same on all clients. To continue. The valid range is between 0 and 28. By turning the field back into a “regular” field. The maximum value has a bad value. 2553 2554 2555 2556 2557 2558 2559 2560 2561 148 "Chapter 2—Action Request System Error Messages . Valid range is 0 to 28. No image conversion will take place. You are given the option to reset the value to the previous server you selected. This warning appears when you change a server name for an open dialog active link action. You have entered a value for a Decimal Field in the Attributes page of the Field Properties Dialog Box. A duplicate server was detected in the server list for user <name_of_user>. The maximum is 10.gif). 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. in the list of servers. When viewing a select number of forms in the Server Window. This changes all of the fields' bounding boxes so that they are compatible with 4. You chose an invalid field type to become a global field. You have entered an invalid value for the maximum value in the Field Properties Attributes page for a Decimal Field. Save anyway? If you attempt to change the extension of an image format’s extension (for example. The field type selected is not valid for global fields. you selected more than 10 forms. Warning: Form <name_of_form> not available in server <name_of_server>. You have entered an invalid value for the minimum value in the Field Properties Attributes page for a Decimal Field. trying to save a JPEG file as something.Action Request System 5. select a number less than 10.0 form with a 4.x (and later) version of AR System Administrator. A global field has just been set to a regular field. A maximum of <number> forms can be selected. To continue. this warning appears. for both the short and long names. you now can specify an entry mode. AR System Administrator will upgrade the layout information for this view when you save this form.1 2552 The minimum value has a bad value.x (and later). A workaround would be to create a packing list and use it to view a larger number of forms. Global fields by design have no default values. This message appears when you attempt to import a pre-4. Choose another field ID not from this reserved range. The system encountered an error during a call to allocate memory space when adding indexes. Exporting extension objects in XML is not supported. Unable to realloc memory. You can recover that memory space by shutting down unneeded processes. This warning is returned because you did not define any field mappings for Dialog window type. Selected extension objects will not be exported. These field IDs are reserved for Alert Lists and Result lists. This warning is returned because you cannot export extension objects (non-AR System objects) in XML format. Some fields that are mapped will not be relevant for this form. Choose another field ID not from these reserved numbers. You can recover that memory space by shutting down unneeded processes. Please choose another Field ID for field—<type_of_field>. No field mappings have been defined for Open and Close dialog states. you did not define any field mappings. Unable to malloc memory.Error Messages Guide 2562 Field ID 706 and 1020 are reserved for Alert and Results List respectively. This warning is returned because. 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. No field mappings have been defined. 2563 2564 2565 2566 2567 2706 2707 Action Request System Error Messages ! 149 . Please choose another Field ID for field—<type_of_field>. This range of field IDs is reserved for columns in an Alert List. Restart processes that have been running for a while to recover space those applications may have leaked over time. Restart processes that have been running for a while to recover space those applications may have leaked over time. 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. Field IDs from 711 to 718 are reserved for columns of Alert List. in Search or Submit mode. The system encountered an error during a call to allocate memory space when creating indexes. 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. Please select a menu type. If necessary. Restart processes that have been running for a while to recover space those applications may have leaked over time. Good candidates for indexing include fields that you search on frequently. You may be attempting to index too many fields in your form anyway. If necessary. The system encountered an error during a call to allocate memory space when updating query lists on your form. 2710 2711 2713 2714 2716 2717 2718 150 "Chapter 2—Action Request System Error Messages . You exceeded the number of fields that can be added to a single index. You can recover that memory space by shutting down unneeded processes. for example. You may be attempting to index too many fields in your form anyway. You can recover that memory space by shutting down unneeded processes. You exceeded the number of fields that can be added to a single index. add fields that you search on frequently to your index. You have reached the maximum limit of the fields in an index. removing items from the list. Specify a menu type to continue. Restart processes that have been running for a while to recover space those applications may have leaked over time. you did not enter a menu name. Please supply a menu name. One or more indexes does not have any fields specified. Specify a refresh code to continue. When creating or saving a menu. Enter a menu name to continue. which is 16. Good candidates for indexing include fields that you search on frequently. 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 created index(es) without any fields. you did not specify a menu type. To continue. create multiple indexes for this form.Action Request System 5. 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. Please select a refresh code. Unable to malloc memory. When creating or saving a menu.1 2709 The maximum number of fields that can be specified in one index is <number_of_fields>. which is 16. The system encountered an error during a call to allocate memory space when creating query lists on your form. you did not specify a refresh code. Unable to realloc memory. create multiple indexes for this form. When creating or saving a menu. you did not select a field name. and click Modify Action. When creating a Message active link action. Enter a form name to continue. Please supply a file name. Add menu items to continue. Select a label field to continue. When creating a DDE active link action. the message number is outside of the allowed range. These fields are system-generated and must exist in any regular form. When creating or saving a File menu type. you can hide these fields. Enter a service name. Please supply a value field. Correct the message number. Please supply a form name. you did not select a label field. you did not select a value field. If necessary. you did not enter a file location. you did not enter a server name. When creating or saving a Search menu type. Menu definition is empty. When creating or saving a Character menu type. You cannot delete the following core field(s): When creating or modifying a form. and click Add Action.Error Messages Guide 2719 Please supply a server name. Select a field name. Missing message text. DDE 'Service Name' is missing. Please supply a label field. you did not enter a DDE service name. but you cannot delete them. When creating or saving a File menu type. you did not enter a file name. Must be greater than 9999 and less than 2147483647. When creating a Message active link action. When creating or saving a Search menu type. Please select a file location. Select a value field to continue. you did not enter any message text. 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 Action Request System Error Messages ! 151 . you illegally attempted to delete a core field. Enter a file name to continue. you did not add any menu items. Enter the missing message text. When creating or saving a Search menu type. you did not enter a form name. When creating a Change Field active link action. User messages have message numbers of 10000 or greater. Enter a server name to continue. Missing field name. When creating or saving a Search menu type. Enter a file location to continue. and click Modify Action. and click Add Action. The default value: When creating a decimal field. When creating a decimal field. DDE poke actions must include a DDE item. and click Add Action. you did not enter a DDE topic. Click OK. DDE 'Command' is missing. When creating a DDE active link action. 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 152 "Chapter 2—Action Request System Error Messages . you specified an illegal default value. DDE 'Item' is missing. You cannot open server objects from the Related Workflow tab on the Field Properties window. The named menu is not defined at this time. You will not be able to perform searches for new objects added to your search database. To continue. You now can search for any new objects added to your search database. Synchronization of the Search Database Failed.Action Request System 5. Enter a DDE item. To continue. The minimum value is greater than the maximum value. then open the server object from the Server Window.1 2731 DDE 'Topic' is missing. When creating a DDE active link action. Please open it from the Server Window. DDE 'Path' is missing. Enter a DDE path. and click Add Action. do you wish to continue? When attaching a menu to a character field. Enter a DDE topic. select a menu from the drop-down list of available menus. create a minimum value larger than the maximum value. The Default value is out of range with the minimum and/or maximum value. Try again. you did not enter a DDE path. try performing the synchronization later. Macro name is missing. you specified an illegal range of minimum and maximum values. You successfully updated the search database. create a default value within the minimum and maximum ranges. To continue. you selected an illegal menu. When creating a DDE active link action. and click Add Action. The search database has been synchronized successfully. Specify a run macro command. Enter a DDE command. When creating a Run Macro active link action. and click Add Action. you did not enter a DDE item. Server object <name_of_object> cannot be opened from here. There was a failure in updating the search database. When creating a DDE active link action. To continue. you did not specify a run macro command. you did not enter a DDE command. and click Add Action. you can choose only from the listed views in the drop-down menu. To continue. When creating a real field.remedy. Do you wish to close the field property dialog before correcting the errors? You have specified field property settings that are incorrect. The Default value is out of range with the minimum and/or maximum value. Alert text is missing. you specified an input length outside the legal range of values. and click Add Action. and click Add Action. you specified an illegal default value. and click Add Action. unable to locate your default browser. When creating a Notify filter action. The field length must be between 0 and 4294967295. 2744 2745 2746 2747 2748 2749 2750 2751 Action Request System Error Messages ! 153 . To continue. You attempted changes to a form that were not accepted by AR System server. Feel free to visit our website for the latest information on Remedy products and services at http://www. you specified an illegal default value. you did not enter a user name. you did not enter notify text. The minimum value <minimum_value> and the maximum value <maximum_value>. To continue. Reference Field is missing. When creating an integer field.com. You must install a web browser to access this information. When creating a Notify filter action. When creating a character field. Invalid View Name. The Default value is out of range with the minimum and/or maximum value. User text is missing. your settings will not be saved. create a default value within the minimum and maximum ranges. specify an input length within the legal range. If you close the Field Property dialog box. create a default value within the minimum and maximum ranges. When creating a Notify filter action. When choosing a default form view in the Manage Views dialog box. You must select a defined name. This error message appears when you choose items from Help > Remedy on the Web > Remedy Home Page in AR System Administrator. you did not select the reference field that is required when the notification Mechanism is Cross-Reference.Error Messages Guide 2742 2743 Unable to Save/Update Form. Enter a user name. Sorry. The minimum value <minimum_value> and the maximum value <maximum_value>. Select a reference field. Enter notify text. 1 2753 Unable to log on to any server as administrator or sub-administrator. and click Add Action. After you verify that you have enough memory resources and that the server is running. run the Analyze tool again. The fonts you selected in the Form Fonts tab in the Preferences dialog box were not accepted for some internal reason.Action Request System 5. When creating a Push Fields action. 2754 Please enter Qualification query for this action. The Analyze tool could not find a list of filters on the server. run the Analyze tool again. you did not enter a Push Field If qualification. The Analyze tool could not find a list of forms on the server. Possible problems might be a memory allocation error. Qualification line error at position <number>. Error getting active links list on form <form_name>. for the following reasons: ! ! AR System did not recognize this user name as a valid administrator. run the Analyze tool again. To continue. Enter a qualification. run the Analyze tool again. Possible problems might be a memory allocation error. you did not enter a valid qualification. verify that the server and administrator names are correct. the font you previously selected cannot be understood by AR System for some unknown reason. After you verify that you have enough memory resources and that the server is running. Possible problems might be a memory allocation error. After you verify that you have enough memory resources and that the server is running. The Analyze tool could not find a list of escalations on the server. or AR System server might have stopped running. Error getting filter list. The Analyze tool could not find a list of active links connected to this form on the server. After you verify that you have enough memory resources and that the server is running. Error Getting Font Data. Possible problems might be a memory allocation error. or AR System server might have stopped running. Error getting form list on server <server_name>. You can troubleshoot this problem by verifying that you can select a different font as a preference. There was a failure during log in. If you can. or AR System server might have stopped running. You entered an invalid server name. or AR System server might have stopped running. When creating a Search type menu. Error getting escalation list. Check your qualification. and click Add Action. 2755 2757 2759 2760 2761 2762 154 "Chapter 2—Action Request System Error Messages . you did not specify a set of field/value mappings. verify which form(s) you want to control the active links in your guide. Error: No server has been selected. Form <form_name> not found in list of forms. or select the form that was used for these mappings. You will lose your existing <name_of_guide> assignments by changing the form. To continue. Select a guide to continue. When creating or modifying an Open Window action. Enter or select a different server name to continue. but the action will not function properly. 2766 2768 2770 2771 2772 2773 2776 2777 2778 Action Request System Error Messages ! 155 . Enter or select a different server name to continue. This message contains information about the position of the error in the line. When creating an Open Window action. Active links and filters can be attached to multiple forms. Error: No guide selected for CallGuide action. Create a set of field/value mappings to continue. Do you want to continue? When modifying an active link or filter guide. When creating an Open Window action. To continue. When creating or modifying a Call Guide action. you did not select a guide. you specified a server that the system could not find or resolve. AR System Administrator will let you save the action. Error in export! Export aborted. you did not specify a server. you changed which form controls the active links. Enter or select a server name to continue. Assign line error at position <number>.Error Messages Guide 2765 Server <server_name> not found in list of servers. you did not specify a form. Warning: Some fields that are mapped will not be relevant for this form. Enter or select a form name to continue. Error: No form has been selected. you attempted to enter a set of field/value mappings that are invalid for the form you just selected. 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. This change may create unanticipated results in your guide. When creating or modifying an Open Window action. an error occurred. When creating or modifying an Open Window action. While parsing a qualification line in the Open Window action. When creating an Open Window action. There was an error while attempting to export mail templates. Enter a new set of mappings. you specified a server that the system could not find or resolve. Warning: No field mappings have been defined for Open and Close dialog states. When attempting to save a report of results from the Analyze tool.Action Request System 5. The Analyze tool could not find a list of filters connected to this form on the server. run the Analyze tool again. After you verify that you have enough memory resources and that the server is running. When creating or modifying a Go To Guide Label action. you specified an illegal default value. or AR System server might have stopped running. or AR System server might have stopped running. Enter a guide label to continue. When creating a decimal field. Error getting field list on form <form_name>. run the Analyze tool again. Verify that the guides indeed exist and try repeating the creation of the Call Guide action to continue. The Analyze tool could not find this field connected to this form on the server. Failed to analyze filter <filter_name> in form <form_name>. Error opening file <file_name>. The Default value has a bad value. run the Analyze tool again. Possible problems might be a memory allocation error. Failed to analyze escalation <escalation_name> in form <form_name>. Failed to analyze field <field_name> in form <form_name>. or AR System server might have stopped running. Possible problems might be a memory allocation error. Possible problems might be a memory allocation error. 2781 2782 2783 2784 2785 2786 2787 156 "Chapter 2—Action Request System Error Messages . run the Analyze tool again. or AR System server might have stopped running. Make sure that you are using a . After you verify that you have enough memory resources and that the server is running.1 2779 Error: Addition of guide <guide_name> addition to tree failed. you did not enter a guide label. you were unable to open a new file. The Analyze tool could not find a list of escalations connected to this form on the server. A problem was encountered adding a complete list of guides to the tree. Error: No Active Link specified for guide to go to.txt format for the file and that you have write access to this directory path. Possible problems might be a memory allocation error. create a default value within the minimum and maximum ranges. After you verify that you have enough memory resources and that the server is running. To continue. The Analyze tool could not find a list of fields connected to this form on the server. After you verify that you have enough memory resources and that the server is running. jpeg . the form was still created on AR System server. Dropping connection. The Analyze tool could not find a list of applications on the server. To continue. When you are attempting to create a tab order for shared fields across pages in a page holder. 2789 Errors were found. To continue.dib You can only use the formats listed above.jpg . make sure that the tab order is the same for each view of the form. along with other fields that were modified. This error occurs only with multiple native views of a form in which you are creating the tab order. Verify in AR System Administrator if you can view all forms and all objects. There was an error because the image you attempted to save to a file is not from the following types: ! ! ! ! . After you verify that you have enough memory resources and that the server is running. run the Analyze tool again. There was a failure during login because AR System did not recognize this user name as a valid administrator or subadministrator. Please check the tab order to make sure that all shared fields are in the same order relative to each other. 2791 2793 2794 2795 2796 Action Request System Error Messages ! 157 . and you can only save to a file of the same image type. Possible problems might be a memory allocation error. Some Fields could not be saved in this form.bmp . There was an error when testing the help file or saving it to disk. Error getting application list. Nevertheless. or AR System server might have stopped running. The server failed to save some of the fields you attempted to add to or modify on this form. This problem may be connected to the inability of your underlying RDBMS to create these fields. During the login process. Failed to load <server_object> for form <form_name> from server <server_name>. the server failed to load the different AR System objects connected to this form when you were viewing objects by workspace or by form. Unable to open file. enter a different login name. User <name_of_user> does not have admin or subadmin privileges on server <name_of_server>.Error Messages Guide 2788 Could not detect image type of <type_of_image>. verify that you have the necessary permissions to access the file. then click OK. Verify in AR System Administrator if objects are indeed related. You attempted to perform an operation to an object that has not first been added to the source control system. To enable source control integration with AR System. the view used in the action will be the default administrator view. Please select a Source Control Project. You attempted to import the object definitions from source control but the operation failed. Use a different name. but the call has failed due to instability in the client tool. then click OK. its related items were not loaded. AR System Administrator has issued an API call to refresh the fields on this form. 2805 2807 2808 2809 2810 2811 2812 158 "Chapter 2—Action Request System Error Messages .1 2797 Failed to get related items. You did not select a source control application before you clicked OK in the Source Control tab. Unable to refresh field detail for field <field_name> in form <form_name> on server <server_name>. The View will return to default. Any further operation on this form can cause unpredictable behavior. To handle this problem. You did not select a source control project before you clicked OK in the Source Control tab. whether an active link is connected to a form. Then re-start AR System Administrator and open the form. If this does not work. Export file will not be generated. the Form View you selected could not be found on AR System server. You attempted to create an object that has the same name as an object that already exists in the source control system. for example. When exporting an object. Error: The Active Link <active_link_name> could not find the View <view_name> in Form <form_name>.Action Request System 5. close both the form and the AR System Administrator client. Error getting definition file for object. The export operation will fail. first click the Browse button to select a project and location from the Project Name drop-down list. When creating an Open Window action. Otherwise. you will overwrite the old object with a new one. Object does not exist in Source Control. Please select a Source Control Provider. Open the form in AR System Administrator and choose Form > Select a View to verify that the view you want to use indeed exists. Accordingly. Object already exists in Source Control. first select a provider from the Provider Name drop-down list. and so on. Add the object to the source control project. you may need to reboot your system. To enable source control integration with AR System. First check the object in to source control. You attempted to retrieve user information from source control but the properties could not be displayed in the User Info dialog box. You cannot modify this object. You are in Enforced mode of the Source Control Integration. the user who checked it out first is its owner. you do not have a source control client installed or you have not configured it properly with your AR System Administrator client. (For a detailed discussion on source control issues.Error Messages Guide 2813 Are you sure you want to remove the selected objects from Source Control. In Enforced mode. You have attempted to modify an object that is under source control in Enforced mode on AR System server. Error writing Registry values. However. You cannot modify this object because it does not exist in Source Control. You are in Enforced mode of the Source Control Integration. only one user at a time can check out an object. You cannot modify this object because you did not check it out first. Contact the other user if possible to resolve any administrative issues. In Enforced mode. You then will be allowed to modify objects under source control.) 2814 2815 2816 2817 2818 2819 Action Request System Error Messages ! 159 . You attempted to check out an object that has already been checked out by another user. You are in Enforced mode of the Source Control Integration. You cannot modify this object because it is already checked out to another user. you are not deleting an object from AR System server. refer to the Developing AR System Applications: Advanced guide. you lose the ability to track the history of any changes made to the object. as you will lose history data along with them? When you remove an object from source control. Contact the other user if possible to resolve any administrative issues. then configure it with AR System Administrator in the Source Control tab in the Server Information window. The server is configured for Source Control but you have not integrated it on your client. You are in Enforced mode of the Source Control Integration. If conflicts occur when two users are trying to check out an object at the same time that is in Enforced mode. However. Object is checked out by <user_name>. you attempted to modify an object that does not exist in the source control database. Make sure that you have properly installed the source control client software. Click OK to continue. Contact the other user if possible to resolve any administrative issues. You have attempted to perform a source control action. Be careful not to overwrite some other user’s changes. so modifying an object could overwrite or conflict with someone else’s work. multiple users run the possible risk of accessing the same object at the same time. contact the other user if possible before making any changes to resolve any conflicts. Then you can start using source control integration with the Action Request System server. You are in Advisory mode of the Source Control Integration. You have attempted to perform an operation on an object that is under source control in Advisory mode on AR System server. Modifying an object could overwrite or conflict with someone else’s work because it does not exist in Source Control. In Advisory mode. You have attempted to modify an object that is under source control in Advisory mode on AR System server. Please relogin to this server for the changes made to Source Control Integration to take effect. Modifying an object could overwrite or conflict with someone else’s work because it is already checked out to another user. you did not enter a file name before you clicked OK.1 2820 You are in Advisory mode of the Source Control Integration. Modifying an object could overwrite or conflict with someone else’s work because you did not check it out first. you run the almost certain risk of overwriting another user’s changes or introducing inconsistencies. Otherwise. In Advisory mode. you must once again log in to AR System Administrator. If your development environment absolutely requires Advisory mode. You have attempted to modify an object that is under source control in Advisory mode on AR System server. multiple users run the risk of accessing the same object at the same time.Action Request System 5. Configure your system to have the proper source control integration with AR System. project. Please enter a definition file name. and other configuration settings in the Server Information window. Your Integration is not initialized. 2821 2822 2823 2824 2825 160 "Chapter 2—Action Request System Error Messages . Because AR System integration detects that the object is checked out to another user. Enter a file name to continue. You are in Advisory mode of the Source Control Integration. you run the risk of conflicting with another user’s work. Check out the object before performing any further operations. You are in Advisory mode of the Source Control Integration. After you make any changes in your source control provider. When importing from source control into a file. but your AR System Administrator client is not properly initialized with the source control system. by opening it in the source control client. You attempted to perform a source control operation on a distributed mapping. You attempted to open a source control project but were unable to. by opening it in the source control client. The operation to AR System server was successful but the update to the source control database failed. checking a group name in to source control. checking a mapping in to source control. Import to server anyway? If the object is checked out to another user.Error Messages Guide 2826 Source Control operations can not be performed on Groups. for example. You attempted to perform a source control operation on a group. then try the update operation again to continue. Verify that you have access to the file. This functionality is disallowed with AR System integration. verify that you have access to the project. The object you are importing has been checked out to someone else. for example. that object is skipped and the import process continues. Source Control operations can not be performed on Distributed Mappings. This functionality is disallowed with AR System integration. to continue. To continue. Error getting file from Source Control database. You cannot import this object because it is already checked out to another user. Contact the other user if possible to resolve any administrative issues. There was a failure to retrieve a definition file from source control. 2827 2828 2829 2830 2831 2832 Action Request System Error Messages ! 161 . You attempted to perform an import operation of an object that is currently checked out to another user. You are in Enforced mode of the Source Control Integration. Error updating Source Control database. Verify that the source control database is running. Error opening Source Control project. for example. Import the object to the server later. for example. to continue. checking it in to the source control project) that was not first checked out. You then will be allowed to modify objects under source control.) 2835 2836 162 "Chapter 2—Action Request System Error Messages . an error was encountered in which you cannot modify the selected objects. The server is configured for Source Control but you have not integrated it on your client. Do you wish to continue? During a bulk update to the source control database. (For a detailed discussion on source control issues. refer to the Developing AR System Applications: Advanced guide.cfg/ar.Action Request System 5. To continue. Make sure that you have properly installed the source control client software.) You are in Enforced mode of the Source Control Integration. 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. 2834 Object is not checked out. and try the import operation again. You attempted to manipulate an object (for example. If you are successful. refer to the Developing AR System Applications: Advanced guide. then configure it with AR System Administrator in the Source Control tab in the Server Information window. verify that it is valid. verify that you have access to the objects in the source control database. for example. You cannot modify the selected objects.conf file. You will also see this error message if you import server objects from a .1 2833 Error importing some objects. (For a detailed discussion on source control issues. You then will be allowed to modify objects under source control. log back in to AR System Administrator.def file and a server name alias exists that cannot be resolved in either of the following places: ! Server Name Alias field in the Platform tab in the Server Information window ! Server-Name: in the ar. Check out the object from source control to continue. However. then configure it with AR System Administrator in the Source Control tab in the Server Information window. You have attempted to modify objects that are under source control in Enforced mode on AR System server. Make sure that you have properly installed the source control client software. If you are using a server name alias. you do not have a source control client installed or you have not configured it properly with your AR System Administrator client. During an import operation from source control. by attempting to access them in the source control client. and that both AR System server and the source control database are running. When configuring the number of server threads in the Server Ports and Queue tab in the Server Information dialog box. 2842 The Form name has not changed. and that both AR System server and the source control database are running. 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. Error creating the file. You attempted to refresh the status of an object from the source control database but an invalid status was returned. Min and Max value should be greater than 0. Make sure that the number of Min threads is less than the number of Max threads. Verify that the objects do indeed exist in the source control database. 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. Click Yes to overwrite the existing file with the latest version from source control. The specified file already exists. Also. 2843 2844 2845 2846 Action Request System Error Messages ! 163 . if you are copying the file to a location. Invalid refresh state returned. Ask yourself whether this type of server thread is necessary in your operation. The object will then be added to source control. The specified file does not exist. you attempted to make the number of Min threads exceed the Max number. Do one of the following: ! ! 2840 Make sure that the number of Min and Max threads is greater than zero. To continue. check your permissions. change the name of the form. there was an error in creating the file on AR System server or in the location you specified. You attempted to save a form that is under source code control. When retrieving the latest version of the file from source control.Error Messages Guide 2839 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 set the number of Min and Max threads to zero. You then will be able to manipulate the object as needed. verify that the object does indeed exist in the source control database. Please specify a new name. To continue. you did not specify a target location. you used the name of an object that already exists. To enable source control integration with AR System. 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. first select a provider from the Provider Name drop-down list. Add the required comment. there was a failure to load the server objects that the user is permitted to see. Error: No sample form has been selected. When using the Advanced functionality for an Open Window action. verify that the server is running. Use a different name or rename the original object. You attempted to perform a source control operation on a distributed pool. Deleted objects will not appear even if the database is not synchronized. When searching in the Search Objects window for an object. When creating or modifying an Open Window action. In the Display tab of the Field Properties window. Enter or select a target location to continue. or change the configuration settings. Enter a sample form to continue. Please select a source code control provider.Action Request System 5. Also. This functionality is disallowed with AR System integration. Enter a number equal to or less than 230. no results were returned. for example. Source Control operations cannot be performed on Distributed Pools. Missing target location text. Enter a sample server to continue. Developer comments are required for this operation. When using the Advanced functionality for an Open Window action. verify the user’s access control settings. then click OK. When attempting to create and name a Distributed Pool object. Duplicate distributed pool name. The number of rows exceeded the maximum allowed limit of 230. you did not specify a sample server name. Error: No sample server has been selected. To continue. No matches found in the database for the given query.1 2847 Failed to load <server_objects> from server <name_of_server>. During the login process. you did not specify a sample form name. Objects may have been deleted or the names modified. checking a distributed pool in to source control. You did not select a source control application before you clicked OK in the Source Control tab. 2848 2849 2850 2851 2861 2862 2863 2864 2865 164 "Chapter 2—Action Request System Error Messages . you attempted to set the rows displayed in a form to a number larger than 230. Please enter a comment. com. Create a set of field/value mappings to continue. you cannot create a directory before selecting a support file. by attempting to access them in the source control client. you need to specify a unique alias value. When creating an application object. Directory depth exceeds the maximum allowed limit. contact your Remedy sales representative. When adding localized text in the Alias Value field. for example. For unlimited capabilities.Error Messages Guide 2866 Error: No view has been selected. but the action will not function properly. Cannot delete root element.remedy. When creating or modifying an Open Window action. and try the import operation again. The operation is only partially successful. includes a maximum of three fixed licenses. an authorized reseller. Warning: No field mappings have been defined. there was a failure importing some of the objects. When creating or modifying an Open Window action. verify that you have access to the objects in the source control database.remedy. you cannot add a support file to your application that already exists in the current directory. This version of the Action Request System is ready for use or evaluation without purchasing or activating an authorization key. you cannot delete or change the name of the Resources Directory Structure level under the Support Files tab. you did not specify a set of field/value mappings. When creating an application object. Enter or select a form view to continue. AR System Administrator will let you save the action. Please select an item before creating the directory. If you do not add support files to the new directory. Cannot add file. Some items failed to import. Alias values must be unique. you cannot add more than 255 support files to the current directory. If you are successful. To continue. log back in to AR System Administrator. and is configured for each client to access a maximum of one server. the directory will be removed from the directory structure the next time you open the application object. contact your sales representative or visit www. you did not specify a form view. or visit www. When creating an application object. During an import operation from source control.com. This version of the Action Request System has a maximum limit of 2000 requests per database table. 2867 2868 2871 2872 2873 2874 2877 2878 Action Request System Error Messages ! 165 . When creating an application object. File already exists in the current directory. To obtain a version of AR System without these limitations. x workflow will still function. ask your AR System Administrator for assistance in modifying this packing list. as a workaround.x workflow will still function. Your pre-5. To continue.x workflow will still function. However. AR System was unable to convert the existing macro functionality to its equivalent 5. AR System was unable to convert the existing macro command preferences (found in the Desktop preferences) to its equivalent 5. AR System was unable to convert a keyword used in a macro command to its equivalent 5. When you were saving the application to disk in AR System Administrator. you can manually create a Push Fields action as a substitute for your AR System Windows User Tool macro used in workflow. Error in converting to Open Window action.x workflow action.1 2879 Modifying Packing List may result in loss of data.x workflow will still function. Error in converting modify to Push Fields action. Your pre-5. you can manually create an Open Window action as a substitute for your AR System Windows User Tool macro used in workflow. as a workaround. 2880 2881 2882 2883 2884 2885 166 "Chapter 2—Action Request System Error Messages . as a workaround. Error in converting to Run Process (Preferences) action.x workflow will still function. Your changes to this packing list in your role as a subadministrator may result in loss of data. you can manually create an Run Process action as a substitute for your AR System Windows User Tool macro used in workflow. Your pre-5. Error in converting a macro command. However. AR System was unable to convert the existing macro functionality to its equivalent 5. AR System was unable to convert the existing macro functionality to its equivalent 5. Your pre-5.x Run Process action. Your pre-5.x Open Window action. you can manually create a workflow action as a substitute for your AR System Windows User Tool macro used in workflow. you can manually create a Run Process action as a substitute for your AR System Windows User Tool macro used in workflow. Error in converting to Run Process action. Web view is created but not initialized! Please initialize the web view by opening and saving the web view. However. However. you did not first save the contents of the web view to the server. as a workaround. However. as a workaround.Action Request System 5.x Run Process action.x Push Fields action. Server name should be currently available to process QBE type of queries. Your pre-5. Otherwise. Failed to convert QBE into equivalent qualifier structure. create a new active link that uses the new 5.x workflow actions. If you want to use the 5.x workflow actions. This problem may also affect your pre-5. As a workaround. But as a workaround. Server is referred by a keyword or field ID.x workflow actions.x workflow. please decompose the active link into multiple active links and try again.x workflow functionality. To enable successful conversion. Succeeded.x workflow actions. AR System was unable to convert a macro that contained the $Server$ keyword to an equivalent qualification used by the 5.x workflow functionality.x macro conversion tool. then attempt the macro conversion again. divide the old active link functionality into multiple active links.x workflow will still function. you could create new active links that use the new 5. Your pre-5. The maximum number of new actions that can be created is 25.x workflow functionality. because the qualification used in the macro used a server that could not be found. Could not load the form specified by QBE.x workflow.x workflow functionality. AR System was unable to convert the existing macro functionality to a new set of active link actions.x workflow will still function. Server name should be currently available to process QBE type of queries.x workflow functionality. As a workaround. create a new active link that uses the new 5. New Action cannot be inserted. the active link will not be saved. Form name should be currently available to process QBE type of queries.Error Messages Guide 2886 Number of resultant actions exceeded the maximum. 2887 2888 2889 2890 Could not connect to QBE referred server.x workflow functionality. As a workaround. AR System was successful in converting the existing macro functionality to a new set of active link actions. create a new active link that uses the new 5. But as a workaround. create a new active link that uses the new 5. AR System was unable to convert an existing macro to a new active link action. 2891 2892 Action Request System Error Messages ! 167 . AR System was unable to convert the macro to an equivalent qualification used by the 5. create a new active link that uses the new 5. AR System was unable to convert the macro to an equivalent qualification used by the 5. AR System was unable to convert the macro to an equivalent qualification used by the 5. because the qualification used in the macro used a form that could not found and loaded. This problem may also affect your pre-5. Alias must contain alphanumeric characters only.x workflow functionality. There is already another view with the same alias. These database tables are connected to data sources exposed by an ARDBC plug-in. Use only alphanumeric characters in your alias. Your web alias started with a characters that was not alphanumeric. you did not select a database table name. Conversion Complete. When creating or saving a Data Dictionary menu type. 2895 2896 2897 2898 2899 2901 2902 2903 2904 168 "Chapter 2—Action Request System Error Messages . When creating a View form. select a vendor name. Please enter field type. and locale combination. you did not specify the names of database tables associated with the vendor. create a new active link that uses the new 5. Alias should start with an English alphabet. you attempted to enter a port. You must first specify a server.x workflow action. Only one view per form is allowed this unique set of features. No vendor name specified. This database table provides the external data that will be used in the creation of an AR System form. Please specify a vendor name for this form. platform. In the View Properties window. AR System was unable to convert the macro to an equivalent 5. As a workaround. When creating a Vendor form. Please specify a table name for this form. select a unique table column to be used as the key field. because one of the macro action is not supported. AR System was 100% successful in converting the existing macro functionality into a new set of active link actions. or RPC program number before you entered a server. In the Password Administration tab of the Server Information window. To continue. and locale. Begin your alias with alphanumeric characters only.Action Request System 5. Specify a field type to continue. enter a server name first. Your web alias contained characters that are not alphanumeric. No table name specified. When creating a Vendor or View form. you did not specify a unique table column to be used as the “key field. select and load a table name. password. No key field specified.” This key field will function as the equivalent to the Request ID field in a regular AR System form. To continue. Please specify a key field for this form. platform. To continue. you attempted to create more than one view with the same web alias. To continue. you did not specify a field type under Field Details.1 2894 At least one macro command is not supported. There was a failure to access a file when making a link. enter a web alias. You attempted to perform a save operation on a form without first creating a web alias. to the folder where an external image is stored. The selected <extension>s will be deleted. to where an external image is stored. You may also see this error message when performing a command-line bulk conversion of the form layouts. The file <file_name> does not exist. enter a web alias.jsp file names after deployment.5 or later version to proceed further. Verify that you have access to the file (for example. To continue the save operation. you cannot deploy a form to the web. To continue. You cannot create the following core fields in view or vendor forms.5 (or later). You have attempted an action which requires this component. Form and some web views do not have WebAlias property. in the Explore window) to continue. Some web views do not have WebAlias property. you cannot deploy the form to the web. You are about to delete one or more custom server objects (for example. Verify that you have access to the file (for example. Click Yes to continue the delete operation. Without a web alias for a form’s web view. Directory <directory_name> creation failed. for example. You attempted to create view properties without entering a web alias. enter a web alias. for example. To continue the save operation. you did not select an object type. 2907 2910 2911 2913 2914 2915 2916 2917 Action Request System Error Messages ! 169 . However. There was a failure to create a directory when making a link.Error Messages Guide 2906 Please select object type. When creating or saving a Data Dictionary menu type. you cannot deploy the form to the web. in the Explore window) to continue. You attempted to create a web view without a web alias.jsp file names after deployment. This may result in invalid . Specify an object type to continue. a Flashboards server object). This may result in invalid . Please install Internet Explorer 5. Please specify web alias. the Status History field is the only system-generated core field that is not allowed in the view or vendor forms. Without a web alias for a form’s web view. Without a web alias. 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. The web view of your form cannot be opened because it requires MS Internet Explorer 5. there was an error in saving the active link. Cannot create new objects. repair the macro appropriately. No new objects can be created. install MS Internet Explorer 5.1 2918 Internet Explorer 5. and try the conversion process again. refer to Error 2927 or to the latest AR System release notes. remove the un-supported commands (login-related macro commands) or repair the incorrect syntax in the commands. Error in saving active link. an internal error occurred when transforming a string to its equivalent assignment structure (ARAssignStruct). the AR System administrator configured this server to disable admin operations. The conversion. In the Configuration tab on the Server Information window. there was a failure converting the macro into its equivalent active link functionality. however. remove the un-supported commands (login-related macro commands) or repair the incorrect syntax in the commands. Form must have web alias to generate valid . When using the Macro Conversion utility. To continue. there was an internal schema error converting the macro into its equivalent active link functionality. To continue. The conversion however will attempt to convert the other macros. reset the configuration settings. To continue. Active link could not be converted successfully.jsp file name for its web views. For a workaround. For a workaround. This functionality will not be available until it is installed. When using the Macro Conversion utility.5 (or later). create a web alias. When using the Macro Conversion utility. You do not have access to certain view functionality because MS Internet Explorer 5. will attempt to convert the other macros. To continue.5 (or later) is not installed on your system. You attempted to create a web view of a form without supplying a web alias. and try the conversion process again. refer to Error 2927 or to the latest AR System release notes. for example. for example. When using the Macro Conversion utility. For a workaround. Administrator operations are disabled for this server. install MS Internet Explorer 5. To continue.5 or later cannot be found. 2919 2920 2921 2922 2923 2924 2925 170 "Chapter 2—Action Request System Error Messages .5 (or later) is required for application initialization. Portions of the Admin Tool will not be available until it is installed. You do not have access to important functionality in AR System Administrator because MS Internet Explorer 5. Original Active Link is restored. refer to Error 2927 or to the latest AR System release notes.5 or later cannot be found. To continue. repair the macro appropriately. For a workaround. CCSSchema could not be loaded.5 (or later) on your system. Internet Explorer 5.Action Request System 5. refer to error message 2927 or to the latest AR System release notes. Field specified in assignment structure is missing in the schema. Display fields should not be present in a QBE. When using the Macro Conversion utility. After successful conversion. allowing for the schema and server names to be edited. Error in finding report’s end. Workaround: Verify that the fields are display fields. and are ignored during conversion. In case of failure. 2928 Error in converting AR System Report’s keyword. When using the Macro Conversion utility. ! ! ! Workaround: The schema and server names are not available to queries and can be validated. and should be available to process QBE queries. 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. the admin may refer to $field-id$ by directly editing the Open Window action. original active link will be restored. 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. Refer to the following workaround. An error indicating that the QBE cannot be loaded may be due to the schema not being available. Refer to the following workaround. When editing the Open Window action. An error indicating that the QBE query could not connect to the server. The schema and server names are represented by $field-id$. Verify that the conversion of the query string to a qualifier is correct.Error Messages Guide 2926 Value assigned to field cannot be converted to equivalent AR structure. The server is referred to by a keyword or field ID. 2929 2930 Action Request System Error Messages ! 171 . Error in creating or opening of temporary AR System Report file. For a workaround. The following description lists active links and indicates nature of failure or success under each RunMacro action. These values may be replaced with specific values for conversion. an internal error occurred when converting a value to its equivalent assignment structure (ARAssignStruct). you do not have any associated value in the database. When using the Macro Conversion utility. the administrator must choose the Advanced option. an internal error occurred when converting the AR System report command in the macro. User may refer to FAQ for resolutions and attempt again. an internal error occurred when converting the end of the AR System report in the macro. refer to Error 2927 or to the latest AR System release notes. When using the Macro Conversion utility. an internal error occurred when creating or opening the temporary AR System Report file in the macro. Since your query is on field value in database and display fields. The following are frequently encountered errors when converting macros to active links: ! 2927 An error indicating that the qualifier could not be loaded may indicate that fields referred to are not present. . verify that you have access to the project. The source control project could not be created.1 2931 Field with ID <ID_number> is not present in this form. The server name alias embedded in the object could not be resolved properly. Would you like to delete this field? When deploying an application. You attempted to perform a source control operation on a custom server object (for example. The source control engine failed. 2934 Could not open file: <name_of_file>.. Also. If you are using a server name alias. Source Control operations cannot be performed on Extension Objects. Error from Source Control Provider—Not checked out. This error message is returned by your source control application. Error from Source Control Provider—Unknown project. verify your permissions and that the support file exists and is not corrupted. This error message is returned by your source control application. an error was returned in generating HTML files due to non-existent fields in the web view of the form. verify your permissions. When creating an application object. check out the object. To continue. You cannot modify an object under source control unless you check it out first. Error from Source Control Provider—Could not create project. The project name is a local directory of . start the source control application and verify that the source control project exists on your system. Possible server alias name problem. for example. verify that you can start the source control executable independently of AR System Administrator. To continue.Action Request System 5.def files on your system. To continue. During import operation. you cannot open the support file that you wanted to add to your application. To continue. This error message is returned by your source control application. This corruption may be due to the user hardcoding a new field in the form. Cannot find server <server_name>. 2936 2937 2938 2939 172 "Chapter 2—Action Request System Error Messages . To continue. Error from Source Control Provider—Initialize failed. by opening it in the source control client. a Flashboards server object).. The source control project could not be located. This functionality is disallowed with AR System integration. To continue. the objects could not be imported because: ! ! 2932 2933 The object iteration was not constructed properly. delete the field. This error message is returned by your source control application. Looks like a corrupt field.. verify that it is valid. You failed to check out this file because it is currently checked out to another user. you will also lose history data. This error message is returned by your source control application. To continue. set the source control project in AR System server to Enforced mode. Error from Source Control Provider—File already exists. You cannot add this file to source control because the file already exists. This error message is returned by your source control application. Error from Source Control Provider—Access failure. Error from Source Control Provider—No specified version. add the file to the source control database. delete the file from the source control database first. Error from Source Control Provider—File not controlled. This error message is returned by your source control application. This error message is returned by your source control application. Error from Source Control Provider—File is checked out. examine the version history of AR System objects under source control.Error Messages Guide 2940 Error from Source Control Provider—Already checked out. This error message is returned by your source control application. Error from Source Control Provider—File out exclusive. To prevent this happening in the future. This error message is returned by your source control application. wait until the object is checked in. To continue. You failed to access this file because this operation is not supported by your source control application. To continue. This error message is returned by your source control application. To continue. You attempted to perform a source control operation on a file that is currently locked. You failed to access a file because it is not under source control. You failed to check the object in to source control because of a conflict between you and another user. confirm whether some other user is accessing the file. Error from Source Control Provider—Check in conflict. Contact the other user if possible to resolve any administrative issues. You attempted to perform a source control operation on an object that is currently checked out to another user. To continue. confirm whether some other user is accessing the file. You failed to access a file that is currently in use by another user. 2941 2942 2943 2944 2945 2946 2947 2948 2949 Action Request System Error Messages ! 173 . This error message is returned by your source control application. Remember that when removing the object from the source control database. Error from Source Control Provider—Requested operation not supported. This error message is returned by your source control application. Error from Source Control Provider—File is locked. To continue. You failed to access this file because it contained no specific version history in the source control database. You attempted to perform a source control operation on a file that is exclusively locked by another user. Error from Source Control Provider—Shell Failure. Error from Source Control Provider—Project syntax error. open the project first. To continue. 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 174 "Chapter 2—Action Request System Error Messages .1 2950 Error from Source Control Provider—Non-specific error. The file merge operation failed under source control.Action Request System 5. The file merge operation failed under source control. This error message is returned by your source control application. Error from Source Control Provider—Project already open. Verify that an account has been created for you and that you have permission to access the source control database. You are not a recognized user in the source control database. You failed to access this file because this operation was not performed by your source control application. There was an unspecified project syntax error displayed by the source control application. This error message is returned by your source control application. This error message is returned by your source control application. To continue. You attempted to access a file from a source control project that was not open. Error from Source Control Provider—Requested operation not performed. Error from Source Control Provider—Fix merge. Use your source control application to repair the file merge. This error message is returned by your source control application. This error message is returned by your source control application. Error from Source Control Provider—Invalid user. This error message is returned by your source control application. This error message is returned by your source control application. Error from Source Control Provider—Type not supported. An unspecified error was returned in your source control provider that was not covered under any specific error conditions. 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 Provider—Project not open. verify the correct file path. This error message is returned by your source control application. Error from Source Control Provider—Verify merge. Error from Source Control Provider—Invalid file path. An unspecified shell failure was displayed by the source control application. 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. This error message is returned by your source control application. This file type is not supported under source control. This error message is returned by your source control application. 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. The name will not be modified. Error from Source Control Provider—File does not exist. This error message is returned by your source control application. All operation names must be unique. numbers 1 to 9) for the Currency Codes preferences.Error Messages Guide 2961 Error from Source Control Provider—Not authorized. Rename operation failed on the Source Control Provider. Error from Source Control Provider—Connection failure. or left the currency code field blank. This error message is returned if you modified an operation name but the operation name is not unique. There was a failure to connect to the source control application. Format of date value is not recognized. Incorrect precision. The rename operation failed. You attempted to access a file that does not exist under source control. This error message is returned if you do not select a functional currency list. Please enter a unique name for operation. Incorrect currency code. Duplicate Operation Name. Duplicate Operation Name. This error message is returned when the value of a time stamp has been incorrectly converted for a date type field. Please select at least one Functional Currency. This error message is returned if you accidentally created a duplicate mapping. This error message is returned if you did not define a single digit of numeric precision (for example. This error message is returned by your source control application. Unmap and continue. This error message is returned if you created a duplicate operation name in the Operations List. One or both of the objects have already been mapped. This error message is returned by your source control application. Cannot create or modify a Currency Field without at least one selected Functional Currency. You attempted an operation not authorized by your source control engine. All operation names must be unique. There was an unspecified file syntax error displayed by the source control application. This error message is returned by your source control application. Error from Source Control Provider—File syntax error. Please enter a single digit numeric precision. This error message is returned by your source control application. 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 Action Request System Error Messages ! 175 . This error message is returned because you cannot create a web service that has no operations. in a multi-layered XML schema with a parent-child relationship.Action Request System 5. Delete this operation and try creating a new one. they will be sent in plain-text. Name must contain alpha numeric characters only. This error message is returned if the web services mapping is not unique. This error message is returned because the mapping you created for the web service operation has become corrupt. This mapping object is corrupted. Please delete the current operation and continue. This mapping is not supported. 2974 2975 2976 2977 2978 2979 2984 2985 2986 2987 2988 176 "Chapter 2—Action Request System Error Messages . This error message is returned because. This error message is returned because the web service you are consuming is not secure. Web service cannot be saved without any operations. WebService Handler is using an insecure (http) protocol. Cannot create or modify a data field without specifying a corresponding DB column name.1 2973 Form should be mapped before the fields. Name should start with an english alphabet. 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. Enter at least one operation in the operations list. The XML element selected has maxoccurs greater than 1. This error message is returned if you attempted to map the fields before you have already mapped the form. This error message is returned if your mapping is invalid Objects are not mapped. Please specify a valid DB column name. Mapping cannot be defined. When creating a view form. Objects selected do not have the same map. This error message is returned if the web services name is empty. passwords) will not be properly encrypted. If username and password are mapped. Any critical information (for example. This error message is returned because a field cannot be mapped more than once. This error message is returned if no objects are mapped. data fields must be linked to an underlying database column. This error message is returned if the web services name does not use English alphanumeric characters. This mapping is not supported. When creating or modifying a Flashboard field. negativeInteger. the Name field in the Database tab (in the Field Properties window) cannot be empty.Error Messages Guide 2989 Cannot create or modify a display-only field which has a valid DB column name. nonPositiveInteger. The process was stopped either accidently or intentionally by a user in your environment. Enter a name for the field. AR Datatype . integer. start the server again. then the primary key should be mapped. Distinguishing key(s) is not mapped. This error message is returned if the primary key of the parent form has been mapped. nonNegativeInteger. a display-only field cannot be linked to an underlying database column. AR System Distributed Server Option (DSO) process terminated when a signal was received by the server. Please specify a valid entry mode. Primary key is mapped. If the signal is a number other than 15 or is one you sent directly to the process. At least one choice is not mapped in the mapping object. This error message is returned because you attempted to map data types that are incompatible. Primary key is not 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. The primary key should not be mapped. 2992 2993 2994 2995 2996 2997 2998 2999 3000 Action Request System Error Messages ! 177 . Invalid mapping because of incompatible data types. If field ID is not 1.Character can only be mapped to XML Datatype . If the signal is 15. 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. The number following this error denotes the signal that was received. and continue to work. When creating a view form. The Database Name for a Flashboard field must not be NULL.string. This error message is returned if the distinguishing key in a child form is not mapped. This error message is returned if you did not map any of the choice nodes in a XML schema. Foreign Key(s) is mapped. All the choice nodes have to be mapped for the web service to work properly. Map and continue. or positiveInteger. contact Remedy Customer Support Services for assistance in determining the cause of the problem. The server most likely shut down due to a bug in the system. This error message is returned if any of the immediate children under the choice/all node are mapped to a different form. The server for the DSO process (arservdsd) was terminated by a signal. The request is removed from the pending list. and the operation is not performed. A fatal error occurred within arservdsd and the process has been shut down. This scenario is possible when the Distributed Server Option is started before the AR System Server is ready to accept connections. arservdsd cannot be run unless the system is licensed for it. An associated file system error message contains details about the problem with the file. The AR System Distributed Server Option was previously unable to connect to the AR System Server. If there is a Transfer or Update Status field on the request. Correct the problem indicated by the latter message. The AR System is not licensed for the Distributed Server Option (DSO) process. which is specified in the Modify Distributed Mappings form or overridden in the distributed fields on the actual request. 3003 3004 3005 3100 3101 178 "Chapter 2—Action Request System Error Messages . If repeated connection attempts fail. If the request has a Transfer or Update Status distributed field.390601 at startup.Action Request System 5. The details of the error are contained in an associated error message. A subsequent connection attempt succeeded. AR System Server is now available. A request pending transfer or update has been in the pending state for longer than the Maximum Time to Retry interval.1 3001 AR System Distributed Server Option (DSO) process terminated—fatal error encountered. AR System Server is not currently available -. Details of the fatal error are contained in an associated message. the field is updated to the status Time-out. the field is updated to the status Canceled. AR System DSO process (arservdsd) opens a lock file named ar. A license for the DSO process is required to use the distributed functionality of the system. Contact your distributor for information about obtaining a DSO process license. Error while opening the Distributed Server Option (DSO) process lock file. an associated error message will be output and no further attempts will be made.lck. This file is used to prevent multiple copies of arservdsd from being started. An error occurred while trying to transfer or update a request. 3002 Request pending transfer or update has been pending for longer than the specified retry time-out. Pending distributed operation for this request canceled due to error. and run the server again. 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.will retry connection. delete the lock file to free the lock. No form could be found that contains all the special reserved fields indicating it is a Distributed Mapping form. shut down all unneeded processes. Two forms were found that contain all the reserved distributed mapping fields —delete one form. Additionally. If no arservdsd is running. or change it so that it is not considered a Distributed Mapping form (remove fields in the 200 to 220 range). no action is required. 3103 3106 3107 No Distributed Mapping form could be found on the server. The failure occurred on the server machine in the DSO process. The arservtcd process on the target server may be an older version (2. No Distributed Pending form could be found on the server. The system encountered an error during a call to allocate space. If another DSO process is running. then start arservdsd again. you can restart processes that have been running for a long time to recover space those processes may have leaked while running. To recover the memory. Two forms (identified in the message) have all the fields indicating they are Distributed Mapping forms. No form containing all the special reserved fields indicating it is a Distributed Pending form could be found. and define the appropriate mappings. Load the Distributed Pending form. The server being accessed is not licensed for the Distributed Server Option (DSO) process.Error Messages Guide 3102 Another copy of the Distributed Server Option (DSO) process is already running.0 and earlier) that does not interact with arservdsd. this error occurs when there are too many processes running. Malloc failed on Distributed Server Option (DSO) process. and continue. or when certain processes occupy most or all of the available memory on your server machine. A machine can run only one instance of the DSO process at a time. A Distributed Mapping form is required for the system to support distributed operations. If another DSO process is not running. or the target server is not licensed to use the DSO process. In general. A Distributed Pending form is required for the system to support distributed operations. 3108 3109 Action Request System Error Messages ! 179 . The system cannot work correctly if there are two forms containing mapping information. you have probably encountered a known problem with the NFS lock manager on Sun workstations—the lock manager sometimes keeps a lock running even when the process holding the lock is no longer running. Load the Distributed Mapping form. Delete one of the forms. A pending request with the pending operation tag set to an unrecognized value was encountered. this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server. The From form in the mapping definition is different from the source form in the attempted mapping. The system cannot work correctly if there are two forms containing pending information.Action Request System 5. Typically. If you made no manual requests to the Distributed Pending form and encounter this error. The form defined as the To form does not match the form that is the target of this transfer. this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server. Delete one of the forms or change it so that it is not considered a Distributed Pending form (remove fields in the 250 to 260 range). The system attempted to transfer the specified request. You can only transfer the master instance of a request. Typically. but the Master Flag field on the request is set to No. 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. this error occurs when a mapping specified in a transfer operation on the current server differs from the same mapping on the original server. 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. The server defined as the To server does not match the server that is the target of this transfer. Two forms (identified in the message) have all the fields indicating they are Distributed Pending forms. Only the master copy of a request can be transferred. The server defined as the From server does not match the server that is the source of this transfer. The To form in the mapping definition is different from the target form in the attempted mapping. The To server in the mapping definition is different from the target server in the attempted mapping. Typically.1 3110 Two forms were found that contain all the reserved distributed pending fields encountered—delete one form. contact Remedy Customer Support Services for assistance. The From server in the mapping definition is different from the source server in the attempted mapping. and continue. 3111 3112 3113 3114 3115 3116 180 "Chapter 2—Action Request System Error Messages . The type assigned to a pending request is not recognized. The form defined as the From form does not match the form that is the source of this transfer. thus creating a new request due to ID conflict. the target form does not have a From Request ID field. and an associated message contains more information about the failure. Create New is specified as the action if duplicate Request IDs are encountered during transfer—the target form does not have the required From Request ID field. the distributed command was not performed. you must ensure that there are also values assigned for the From Form and the From Server fields (you can also change these by using ardist).Error Messages Guide 3117 Update was unsuccessful—the From Form field or the From Server field has no value. The distributed operation being attempted expected additional information which is not present. Failed to perform a distributed command. 3118 arserverd received a request to record a distributed command or encountered a situation in which it attempted to automatically record a distributed command. Thus. This error should only occur if you have manually added requests to the Distributed Pending form. the required additional data is missing. A transfer was being attempted with a specific mapping defined in the To Mapping (or From Mapping for an update) field. If you encounter this message. The command being attempted is displayed with this message. Without this data. which is required for this action. pass the request as data only. and a failure occurred during recording. If you made no manual requests to the Distributed Pending form and you encounter this error. If the Master Flag is set to Yes. However. If you used the ardist program to manually change the Master Flag value. You attempted to transfer a request to the target form with ownership transferred to the new request. 3120 3121 Action Request System Error Messages ! 181 . so the transfer or update cannot be performed. contact Remedy Customer Support Services for assistance. The specified mapping is disabled. which is a system form that should not be manipulated manually. If you must retain ownership on the original. the system expects a value in the From Form and the From Server fields. the operation cannot be performed. The Distributed Delete operation requires information about the item being deleted. This information is stored with the pending operation. 3119 A specific mapping was specified on the request—the specified mapping is currently disabled. The From Form and From Server fields contain information about the previous copy of this request (from where the request was transferred). 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. Action Request System 5. Remove or disable the filter attempting the distributed operation. and one of these conditions exists: ! 3123 You did not map the Request ID field of the source form to the Request ID field of the target form. Distributed-Return) during the deletion of a request. It is required that the target form (identified in the error) contain a From Server field if ownership is being transferred. A distributed transfer operation was attempted that included a mapping to another form with a Data + Ownership transfer. It is required that the target form (identified in the error) contain a From Form field if ownership is being transferred. It is required that the source form (identified in the error) contain a Master Flag field if ownership is being transferred. A filter invoked a distributed process (Distributed-Transfer. If a delete operation is in progress. You attempted a distributed transfer operation to another form by using a custom mapping with a transfer mode of Data + Ownership. The source form does not contain a Master Flag field. You must map the Request ID field to the target Request ID field. Distributed-Update.1 3122 A distributed operation cannot be specified while deleting a request—the delete and the distributed operation are both canceled. You attempted a distributed transfer operation using a mapping to another form with transfer mode of Data + Ownership. Transfer with ownership requires that the target form contain a From Server field. Correct the mapping. the error is created—because the request against which the distributed process is run no longer exists. When a distributed process begins. or the From Request ID field must be present on the target form. It is required that the target form (identified in the error) contain a Master Flag field if ownership is being transferred. 3125 3126 3127 182 "Chapter 2—Action Request System Error Messages . and the target form does not contain a From Server field. You attempted a distributed transfer operation using a mapping to another form with a transfer mode of Data + Ownership. and try the transfer again. Transfer with ownership requires that source form contain Master Flag field. You attempted a distributed transfer operation by using a mapping to another form with a transfer mode of Data + Ownership. ! You must map the Request ID field on the source form to one of the above fields on 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. and the target form does not contain a From Form field. or reset the filter so it does not execute on a delete operation. Transfer with ownership requires that the target form contain a From Form field. 3124 Transfer with ownership requires that the target form contain a Master Flag field. the distributed process waits for the operation to be completed. and the target form does not contain a Master Flag field. The server was unable to successfully import the Alert Events form at startup. You included an argument with no specific value on the ardist command line. 3196 3197 Must specify the -s {form} option. The field is a selection field and requires a numeric value. A sockets error occurred while attempting to establish communication with an alert client. See the Action Request System Distributed Server Option Administrator’s Guide for more information about valid command line arguments.Error Messages Guide 3194 Illegal value specified for -m option—legal values are 0 (not master) and 1 (master). as required. You must specify the -s argument to denote the name of the form to be modified. The value specified was either a character or an integer other than 0 or 1. and specify a legal value for this argument. Must specify the -x {server} option. The server will not allow the removal of the Alert Events form or its reserved fields. 3199 Unrecognized command line option. 3300 3301 No Alert Events form could be found on the server. The value specified for the -m argument was not 0 (not master) or 1 (master). The server was unable to locate a form containing the reserved alert events field. Error occurred attempting to communicate with alert client. ardist will not execute with invalid arguments specified. Two forms containing all the reserved alert event fields encountered—delete one to continue. Reissue the command with values assigned to all arguments. Issue the command again. The specified command line argument is not recognized by ardist. You must specify the -x argument to denote the name of the server containing the form to be modified. 3195 Must specify the -e {Request ID} option. All but one form must be removed. 3198 A value is expected for the command line option. Problem encountered during creation of the Alert Events form. 3302 3303 3314 Action Request System Error Messages ! 183 . An associated error message contains details about the failure. The server found more than one form containing the reserved alert events fields. Turn on alert logging to view a trace of the communication activity. Must be AR_NOTIFIER user to perform this operation. You must specify the -e argument to denote the ID of the request (entry) to be modified. A failure occurred while attempting to decode an alert message sent from the server to an alert client. The field value list supplied to the report creation vendor form is missing a required field. Only fields that map to individual fields on the Report form are allowed. The server was unable to successfully import the CleanupAlertEvents escalation at startup. Additional information contains the field number. Unable to get temporary file name for report definition file. 3316 3317 3350 3351 3352 3353 3354 3355 3356 3357 184 "Chapter 2—Action Request System Error Messages . Only fields that map to individual fields on the Report form are allowed. An attempted communication with an alert client did not succeed within the configured time period. Required report field is missing. An associated error message contains details about the failure. Unable to create temporary file for report definition file. Only fields that map to individual fields on the Report form are allowed. Invalid report definition encountered. Inspect the contents of the report definition file for the entry.Action Request System 5. The report plug-in was unable to locate a form containing the reserved Report form fields. The sort list in a list retrieval contains fields that are not part of the report creation vendor form’s list of reserved or core fields. A failure occurred while attempting to get a temporary file name for a report definition. indicating a data transmission error. Illegal field encountered in the field list. Additional information contains the file name. Illegal field encountered in the qualifier. Invalid alert message format. Turn on alert logging to view a trace of the communication activity. an unexpected definition format prevented proper decoding. The qualifier in a list retrieval contains fields that are not part of the report creation vendor form’s list of reserved or core fields. A failure occurred while attempting to create a temporary file for a report definition. Unable to locate Report form. While attempting to transfer data from a formatted report definition to the fields on the report creation vendor form. Failed to load the alert cleanup escalation.1 3315 Timeout occurred attempting to communicate with alert client. Illegal field encountered in the sort list. The field list in a list retrieval contains fields that are not part of the report creation vendor form’s list of reserved or core fields. A value for Distinguished Name is not specified. This error message appears because the field associated with the distinguished name attribute has no value. No errors were encountered during import. Import completed successfully—<number> records imported. This error message appears if the LDAP operation is unsuccessful. Therefore. 3378 3379 4000 Action Request System Error Messages ! 185 . there has to be more fast and list server threads running than there are Report plug-in threads running. The distinguished name must have a value in order to create objects. This error message is returned when the LDAP search URL does not follow the standard format. 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. This error message appears because at least one field on the form must reference the distinguished name attribute. The minimum number of fast and list server threads must be one greater than the maximum number of plug-in threads. Distinguished Name is not configured as a vendor field. A configuration requirement for the Report plug-in has not been met. because proper attribute names are not specified or the operation would violate access privileges enforced by the directory service. An acceptable configuration is as follows: Thread Type Fast List Plugin-ARDBC-Threads Minimum 3 4 2 Maximum 5 6 4 3375 Cannot connect to the directory service. The format is: 3376 ldap[s]://host-name[:port-number]/ 3377 The LDAP operation has failed. In order for the Report plug-in to successfully make requests of the server. The specified LDAP URL is not formatted correctly. This message appears after a successful Import operation. 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. for example.Error Messages Guide 3358 Minimum server thread requirements for Report ARDBC plug-in have not been met. If you continue. Are you sure you want to start importing? System confirms that you really want to begin the Import operation. You have not added or saved your changes to the current mapping. Mapping <mapping_name> not loaded. The current mapping has been changed but not applied. Only one field title exists in the import file. If you continue. This message is logged to the log file when a field is truncated during an Import operation. you will cancel your changes.Action Request System 5. You have not saved your changes to the current mapping. A mapping with the name you have specified already exists. If you choose to overwrite it. The specified mapping is not loaded. 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 186 "Chapter 2—Action Request System Error Messages . System warns you that the specified import file has only one field. you will lose the mappings. Do you want to cancel your changes? System dismisses the Fallback Mappings window before applying the changes. You have not saved nor imported data with the current mappings. Use the Save Mapping menu item or the Import button before exiting the tool to avoid this warning. This is usually caused by an incorrect Import file format or separator string specified on the Open Import File dialog box. This message is logged only to the log file. If you continue. Duplicate mapping name. Click the Modify or Add button to avoid this warning.1 4001 Import of <import_file_name> begun. the earlier mapping will be replaced by the new one. You have tried to exit the tool without saving the modified mappings in the main window. System reports that the Import operation has begun. Record <number>: Field <field_name> truncated to <number> characters. you will overwrite the existing mapping. Earlier messages described why. Are you sure you want to start importing without your changes? You will get this warning if the current mapping has been changed but not applied when the Import button is clicked. Ensure that you specified the correct import file format. Are you sure you want to delete all mappings? System confirms the Delete All button is in both the main and Fallback mapping windows. Click the Modify or the Add button to avoid this warning. You have not added or saved your changes to the current fallback mapping. This message is logged only to the log file. A number has been appended to those titles. your changes will be lost. and restart the import. When duplicate names are found in an . 4020 Action Request System Error Messages ! 187 . Do you want to save your current mappings before closing this window? You have made but not saved changes to the Save Mapping window. There are duplicate field titles in the .arx import data file. do not continue with the import. instead.asc import data file. These fields will be shown by their field IDs in the form fields list.Error Messages Guide 4013 Did not find any matching fields to add as new mappings. Duplicate field titles exist in the . You can continue with the Import operation and no data will be changed.csv or . The name has been changed so that AR System Import can distinguish between the two fields during mapping of data values. save the changes on the fallback mappings window. The Add All button operation did not find any matching form and import fields to add as mappings. To save changes you have made. Those titles have been replaced by their field IDs. 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 you want to copy unprocessed import records to the log file? You have stopped the Import process before the tool has completed operation. Click Cancel to cancel the import. You have not saved your changes to the current fallback mappings. 4014 4015 4016 4017 4018 This file contains duplicate or empty field titles. New Request IDs will be generated for all imported records. both fields will be replaced with their IDs to eliminate confusion about the fields. A number has been appended to the end of the field titles in the import fields list so you can distinguish between them. Duplicate Request ID Handling requires field ID 1 to be mapped. Are you sure you want to start importing without your changes? You are trying to start the Import operation without applying the changes they have made to the fallback mapping window. This file contains duplicate or empty field titles. for example).arx format file. If you continue. Specify whether you want the remaining records to be copied to the log file. Those names have been replaced by their field IDs. This error appears if you do not map the Request ID field (or whatever field has field ID 1) and you then attempt to import data where the IDs of records in the import file need to be known (for updating or replacing. Names are processed from left to right in the file with the field toward the right being modified. 4019 This form contains duplicate or empty field names. click No to cancel closing the window. The form contains duplicate field names. Click OK to create records with new IDs. If you continue. but you specified two mappings to use for the Import operation on the command line. Cannot get children widgets. This error can be caused by not being able to perform Open or Seek operations in the import file. Copying remaining records of <import_file_name> to log file. 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. The record starting at the specified offset cannot be read. Import completed with errors: <number> records were imported. changing. You should never see this message by itself. This error appears when adding. The Import operation has been completed. which you have specified it to be. The specified Import file is not in AR Export format. No saved mappings specified in batch mode. View the log file to see the error messages and records that did not get imported. It occurs when the broadcast message is stopped. Cannot log record starting at <file_offset_of_record>. or removing a mapping request (regular or fallback). <number> records were not imported. or change a request. file: <import_file_name>. remove. Stop broadcast. 4105 4106 4108 4110 4112 4114 4116 4118 4120 188 "Chapter 2—Action Request System Error Messages . You tried to delete a fallback mapping in AR System Import without first selecting one. 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. Two mappings have been specified on the command line. This error message is used in AR System Import for Windows when there is a broadcast of messages within Windows. No mapping selected to delete. It indicates a failure of the mapping or fallback mapping list box to add. Only one mapping is allowed. The tool is running in batch mode. The user terminated the Import operation after it has already started. but you did not specify which mapping to use for import on the command line.1 4102 4104 Invalid AR Export format. User did not want to continue operation. or widget is not a child. Cannot log in to any AR System server. The tool is running in batch mode.Action Request System 5. You have specified a log file name longer than 255 characters. A directory may be specified only if you specify a mapping. The system error is the second part of this message. Log file <file_name> is not a regular text file. Choose another file as the log file. You used the -m flag on the command line. Try reselecting the form and redefining the mappings. You used the -d flag on the command line. or a keyword. 4130 4132 4134 4135 4136 4137 4138 4140 Action Request System Error Messages ! 189 . A log file name is required. 4124 4126 The mapping name is too long. 4128 <field_name> is not a form field. You may not have permission to use the log file. AR System Import cannot initialize the server API and so cannot establish a connection to AR System server. Verify the owner and the permissions for the file. A system error occurred while writing the log file. Cannot get the status of (or open) the log file. You have erased the log file name and clicked Save in the Preferences window. <field_name> is not an import field name. You have specified a log file that is a special file type instead of a normal text file. You have specified a log file name that cannot be opened for read and write. or keyword. but the string enclosed by the dollar signs ($) is not an Import field. The field name specified in the Form Field text control is not a valid field name for the current form. Import log file name is too long. Log file <path_name> is a directory. but did not supply a mapping name following the flag. Cannot initialize the server API. but did not also specify a mapping with the -m flag. You used the variable syntax ($) in the mapping value. ID.Error Messages Guide 4122 The -m option requires a mapping name. You specified a mapping name that is longer than 30 characters. Enter a valid field name. Cannot write to log file. it is possible that the definition of the form was changed by another user. You have specified a directory in the log file text field. an Import field ID. Invalid globals. You may be able to perform the operation by shutting down AR System Import.Action Request System 5. restarting it. Cannot find specified mapping. Cannot read map file for specified mapping. This error occurs if AR System Import is unable to access its mapping or field view. and performing your operation. You may be able to perform the operation by shutting down AR System Import. restarting it. and performing your operation. Cannot open map file for specified mapping. restarting it. Cannot add to mapping list. You may be able to perform the operation by shutting down AR System Import. The mapping file contains invalid syntax. Invalid member data. The import option value is invalid. 4144 4145 4146 4148 4150 4152 4153 4154 4155 4156 4158 190 "Chapter 2—Action Request System Error Messages .1 4142 Cannot build the main import window. The mapping file has a syntax error. This is an internal error. and performing your operation. Correct the syntax as necessary. The file probably has incorrect permissions set. AR System Import could not create the main window. This is an internal error. The operation failed. You may be able to perform the operation by shutting down AR System Import. and the tool could not be started. You may be able to perform the operation by shutting down AR System Import. You may have moved the file or the directory that contained the mapping. restarting it. restarting it. This is an internal error. The mapping file that contains the specified mapping cannot be opened. and performing your operation. and performing your operation. and performing your operation. restarting it. This is an internal error. This is probably caused by a user who edited the mapping file manually. You may be able to perform the operation by shutting down AR System Import. Cannot set mapping list item. Invalid parameters. The mapping file that contains the specified mapping cannot be read. This is an internal error. The system is probably out of memory. restarting it. You may be able to perform the operation by shutting down AR System Import. No tokens exist for a direct mapping. This is an internal error. and performing your operation. This is an internal error. The import file. and performing your operation. This is an internal error. and performing your operation. 4162 4164 4166 4168 4170 4172 4174 4175 4176 4177 4178 4179 Action Request System Error Messages ! 191 . restarting it. Invalid form information UI fields list. Invalid fallback mapping list. The tool could not understand the field titles in the import file. Cannot parse record <number> in import file. restarting it. This is an internal error. restarting it. You may be able to perform the operation by shutting down AR System Import. restarting it. The tool was not able to understand the syntax in the mapping value string. restarting it. Cannot parse import field titles in import file. You specified a nonexistent file as the import file. You may be able to perform the operation by shutting down AR System Import. This is an internal error. The tool could not understand this record in the import file. Cannot get the status of import file. restarting it. This is an internal error. You may be able to perform the operation by shutting down AR System Import. A syntax error exists in the mapping string. You may be able to perform the operation by shutting down AR System Import. or you have removed the file since AR System Import started. This condition could result from low memory. You have specified a directory as the import file. Invalid mapping list. and performing your operation. You may be able to perform the operation by shutting down AR System Import. and performing your operation. This is an internal error. You have specified an import file that is a special file type instead of a normal text file. and performing your operation. The specified import file is not a regular text file. Invalid import fields titles list. This condition could result from low memory. Invalid internal list.Error Messages Guide 4160 Invalid mapping or compound mapping within compound mapping. is no longer accessible. Specified import file does not exist. You may be able to perform the operation by shutting down AR System Import. or the directory it is in. This is an internal error. Rewrite the mapping. and performing your operation. The specified import file is a directory. Cannot open specified import file. A Seek operation cannot be completed in the import file due to a system error. The import file type has not yet been set. and correct the file so that it contains only digits in the FLD-ID line. The specified import file contains a record that is improperly formatted. A field separator string is required. 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 AR System Import. For the ASCII file format. The specified Import field separator string is longer than 30 characters. The Field ID string in the AR Export file does not contain a number.arx ) did not begin with DATA.arx) is not corrupt. The specified import file has no data. Cannot find form field with saved index. but a character that is not a digit was found. The system error appears in the second part of this message. Invalid import file record. The Import file contains only field titles (if that) and no data. 4204 192 "Chapter 2—Action Request System Error Messages . 4200 4202 Import file <file_name> is of an unknown type. You tried to close the Open Import File window without specifying an Import file. The import file is of length zero. Cannot seek in import file. Ensure that the export data file (. This is an internal error. The specified import file cannot be opened due to a system error.1 4180 4182 4184 4186 4188 4190 The specified import file is empty. The import file name is too long. An import file name is required. A data line in an export data file (. The data in the file must be corrected before an import of this line is possible. The Import field separator string is too long.Action Request System 5. Digits are expected in the line after the string FLD-ID. The specified Import file name is longer than 255 characters. The system error is in the second part of this message. a field separator string is required for reading in the field titles. 4192 4194 4196 4198 Record <number>: Unrecognized tag in AR Export file: <file_name>. Error Messages Guide 4206 Record <number>: <value> is not a valid value for field <field_name>. Record <number>: Not enough fields. The record has more fields than the number of field titles. The mapping file could not be created. This error message occurs in the AR System Administrator for Windows when a window broadcasts a message to another window and that window cannot handle the message. expected <number_expected>. This could be caused by an unrecognized selection when mapping to a selection form field. Record <number>: Too many fields. There are currently no mappings defined. <number_not_imported> records were not imported. but there are no mappings files in $ARHOME/arcmds or in any of the directories on the ARPATH environment variable. You chose the Load Mapping menu item. You will never see this message in a dialog box. <number_truncated> records were truncated. Create mapping operation failed. End of <number_of_copied_records> records. Message printed in the log file at the end of all copied records from the Import file. After you choose the Truncate option in the Preferences dialog box and records have been truncated (and some records not imported due to errors). found <number_found>. found <number_found>. Only one -d argument is allowed on the command line. After you choose the Truncate option in the Preferences dialog box and records have been truncated. The error has already been displayed in previous dialog boxes. this message indicates how many records have been truncated and imported. <number_truncated> records were truncated. Import was successful: <number_imported> records imported. 4208 4210 4212 4214 4216 4218 4220 4222 4224 Action Request System Error Messages ! 193 . Two directories to look for saved mappings have been specified on the command line. Import completed with errors: <number_imported> records were imported. or by a character that is not a digit when mapping to a numeric field. The value in the import file is not valid for the form field it has been mapped to. expected <number_expected>. The record has fewer fields than the number of field titles. Broadcast message was not handled. this message indicates how many records have been truncated and not imported. AR Datatype . Invalid mapping because of incompatible data types. This error message is returned because you attempted to map data types that are incompatible.dateTime.string. Invalid mapping because of incompatible data types. or unsigned Long.View or Display can only be mapped to XML Datatype . This message indicates how many records were processed and how many were imported.Date can only be mapped to XML Datatype .decimal. AR Datatype .Action Request System 5. unsigned Short. You can take one of the following actions: ! ! Exit the record to make the field shorter. Verify the file path to ensure that there is enough disk space and that all the directories exist. byte. or unsigned Byte. The default import log file (/tmp/arimport_<user>. 7001 7002 7003 7004 7005 7006 194 "Chapter 2—Action Request System Error Messages .1 4226 Record <number>: a field exceeds the maximum size allowed. You decided to stop the import process before it has been completed.date. AR Datatype .767 bytes (one byte less than 32 kilobytes). AR Datatype . Turn on the truncate character fields’ value option if it is a character field. or gMonth. gMonthDay. unsigned Int. This error message is returned because you attempted to map data types that are incompatible.log on UNIX. This error message is returned because you attempted to map data types that are incompatible. gYearMonth. AR Datatype . Invalid mapping because of incompatible data types.Integer can only be mapped to XML Datatype .int. long. A field of the specified record exceeded 32. This error message is returned because you attempted to map data types that are incompatible. short.log in the ARHOME directory on Windows) cannot be opened.TimeOfDay can only be mapped to XML Datatype . 4499 User stopped import after <number_processed> records were processed.time.Decimal can only be mapped to XML Datatype . 4227 Cannot open the default log file. of which <number_imported> were imported. Invalid mapping because of incompatible data types. Invalid mapping because of incompatible data types. and arimport. gDay. gYear.DateTime can only be mapped to XML Datatype . This error message is returned because you attempted to map data types that are incompatible. AR Datatype . Invalid mapping because of incompatible data types. boolean. This error message is returned because you attempted to map data types that are incompatible. Error Messages Guide 7007 Invalid mapping because of incompatible data types. Failed to resolve existing mappings with the specified schema.string. A few warnings occurred while loading the xml schema.Diary can only be mapped to XML Datatype . 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 generate wsdl from internal mapping. Failed to get top level elements from xml schema. AR Datatype . This error message is returned because you attempted to map data types that are incompatible.Real can only be mapped to XML Datatype . AR Datatype . 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. For example. Invalid mapping because of incompatible data types. This internal error is returned when there are problems while importing the web service from a definition file or while saving the web service.Enum can only be mapped to XML Datatype .string. 7008 7009 7010 7011 7012 7013 7014 7015 7016 Action Request System Error Messages ! 195 . AR Datatype . Invalid mapping because of incompatible data types.Attachment can only be mapped to XML Datatype . This error message is returned because you attempted to map data types that are incompatible. This error message is returned because you attempted to map data types that are incompatible. 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. Invalid mapping because of incompatible data types. This internal error is returned when retrieving the XML data type from the schema.hexBinary or base64Binary.double or float. This error is returned when loading the external XML schema for the input and output mappings of the web services operation. This error is returned when there is a problem with loading the external XML schema. This error message is returned because you attempted to map data types that are incompatible. Specified schema could not be imported. the dependencies of an element in a schema might be missing. Failed to create initial mapping from the specified top level element/type. AR Datatype . Failed to create internal mapping from wsdl. Some of the fields and/or workflow in this form are not supported in this version of the client. A value change is pending on the full text floating license timeout—change will take effect the next time the server is started. 1 .1 7017 Failed to initialize JRE and internal java module.390669. The copy operation failed due to problems with permissions. When connecting the client to AR System server. 196 "Chapter 2—Action Request System Error Messages . This error is returned when the JRE dependencies are missing or corrupt.65535). The number of hours for the Full Text Search Floating License Timeout has been changed in the Timeouts tab of the Server Info window. 390621 390634. then re-started. you set the TCP/IP port to a value outside the legal range.390694). These server configuration settings will not go into effect until the server is stopped. The legal range of values are: ! ! ! ! ! 8029 8031 8032 8033 8034 8201 0 390600 390621 to 390634 390636 to 390669 390680 to 390694 8202 The RPC port specified is not one of the legal values (0. When retrieving a list of field definitions for a form. An admin group list was found in an owned container. Please check the required JRE configuration information in the Configuring the AR System manual. 390600. A warning was returned because an owned container cannot have a list of subadministrator groups. The administrator’s access permissions are determined by the owning object. you set the RPC socket number to a value outside the legal range. The legal range of values are 0 and 1 to 65535. This message occurs when the Any Match for a Push Fields filter action is defined as Error. This list will be disregarded A value change is pending on the floating license timeout—change will take effect the next time the server is started.Action Request System 5. When connecting the client to AR System server. The RPC socket number specified is not one of the legal values (0. 390636 . The number of hours for the Write Floating License Timeout has been changed in the Timeouts tab of the Server Info window. One or more entries match filter conditions—this operation has been defined so that any matches generate an error. 390680 . there was a failure filtering certain field IDs (for example. These server configuration settings will not go into effect until the server is stopped. attachment fields) into the destination structure. then re-started. This error occurs in AR System Administrator when you attempt to set the number of rows for a character field to less than 999. because this version of AR System server is no longer supported. a method ID. Use only these types. The method list required when defining an OLE Automation active link action is empty. Invalid class ID or interface ID. The name of an OLE class ID. The number of rows exceeded the maximum allowed limit of 999. Provide a valid value. Empty automation. The automation structure required when defining an OLE Automation active link action is empty. You must provide at least one method for this structure. This error occurs in the Server Information Dialog. Invalid attachment size. You must specify the appropriate contents for this structure. This error can also be generated when an attachment is erroneously reported with a negative size. Invalid COM value. To continue.Error Messages Guide 8203 The server’s RPC version is not supported. Bad attachment locator type. You must install a source control system and select it in the Provider Name pull-down menu before you click the Browse button. or an interface of an OLE Automation active link action is either empty or exceeding the maximum length allowed (128 characters). The value of an ARCOMValueStruct variable in a method or parameter of an OLE Automation active link action is invalid. 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). Please select a source code control provider. Source Control page. when you click the Browse button and no source control provider is selected in the Provider Name field. There was an error creating an RPC connection. upgrade to a later version of AR System. Empty COM method list. AR System forms cannot store attachments of the size reported. This error is usually caused by an attachment that is too large. by an API program. for example. 8459 8469 8700 8703 8704 8705 8706 8707 Invalid COM name. Correct the name to continue your work. 8708 Action Request System Error Messages ! 197 . The only acceptable attachment locator types are the filename or the buffer. Empty COM parameter list. The value for Application Check Interval is not set properly. Invalid COM method name. Detailed errors follow that explain what part of the method structure is invalid. You must provide at least one method for this structure. Empty COM method. You must specify the appropriate contents for this structure. The method structure required when defining an OLE Automation active link action is empty. Call guide structure empty.Action Request System 5. Detailed error messages explain what part of the structure is invalid. The method structure of the OLE Automation active link action is invalid. Use the Approval Server Admin-Server Settings form to set this to a legal value. Invalid COM parameter.1 8709 Invalid COM method. The parameter list required when defining an OLE Automation active link action is empty. The parameter structure of a method required when defining a method in an OLE Automation active link action is empty. This message occurs when you attempt to create a Call Guide active link action without specifying a Call Guide structure value. 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. The value for the RPC socket is not set properly. Set this to a legal value. Invalid automation string. The parameter structure of a method in this OLE Automation active link action is invalid. The name of a method in an OLE Automation is either empty or exceeds the maximum length allowed (128 characters). You must enter a value to create the Call Guide active link action. You must provide at least one method for this structure. Empty COM parameter. 390680 – 390694). This message occurs when you attempt to create an Open Dialog active link action without specifying an open dialog structure value. 8710 8711 8712 8713 8714 8715 8716 8717 8720 8721 198 "Chapter 2—Action Request System Error Messages . Open dialog structure empty. The value for the Application Check Interval is not within the legal range of 0 to 3600 seconds. You must enter a value to create the Open Dialog active link action. Continuation button title is empty or too long. The tag must be a field or value. If the title is too long. Vendor forms not allowed in join forms. Invalid vendor form definition. Invalid external table name in a vendor field mapping structure. 8723 8724 8725 8727 8728 8729 8730 8731 8732 8733 Action Request System Error Messages ! 199 . Changing the type in the field mapping structure is not allowed. This message occurs when you attempt to create a Go To active link action without specifying a Go To action label. This message occurs when you attempt to create a Call Guide active link action without specifying a Call Guide active link name. shorten the title or lengthen the button. Go To action tag is invalid. The button title cannot be empty or longer than the defined size of the button. that is. you attempted to change a field to a different type. Go To guide label empty.Error Messages Guide 8722 Guide name missing. Bad client type. You must enter a label to create the Go To active link action. Vendor forms may not participate in joins. However. you can modify it without error by setting it to the existing mapping. Unrecognized currency part tag. The field definition for a field on a join form may not be modified once the field has been defined. You attempted to define a disabled or non-existent client type in the client list. You must use a field or value to create the Go To active link action. The value must be a non-negative integer. supply a title. The join form definition includes a vendor form as one of its base forms. 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. The name identified in the vendor form definition is empty. If the title is empty. You must enter a name to create the Call Guide active link action. by setting the client type to a number less than zero. Changing the field mapping is not allowed for join fields. When modifying an existing field in a form. Specify only forms that are not Vendor forms. The name identified in the vendor field definition is empty or exceeds the defined length restriction. This error message is returned if the currency part structure tag contains a value that is not legal. while 1. An error has occurred while loading a plug-in. The specified plug-in does not exist. contains invalid characters. 1. The plug-in will not load. Retrieving attachment data is not supported for this form. 200 "Chapter 2—Action Request System Error Messages . All plug-ins must define the function ARPluginIdentify() and the specified plug-in does not do so. Only numeric characters are valid as decimal data.234 is a valid decimal value. or has been configured to run at a specific port number and has not registered with a portmapper. The decimal data is formatted incorrectly.abc##345 is an invalid decimal value. and may not be a reserved name. This error message is returned if the currency code is not a valid three character string. AR System database connectivity plug-in associated with the form does not support modify operations and a modification was attempted. USD.” The plug-in does not implement ARPluginIdentify(). The plug-in will not load. An arithmetic error was encountered in a decimal calculation. 8735 8736 8750 8751 8752 8754 8755 8756 8758 8759 8760 Cannot establish a network connection to the AR System Plug-In server. Your system is unable to complete the arithmetic operation. For example. AR System database connectivity plug-in associated with the form does not support delete operations and a deletion was attempted. AR System database connectivity plug-in does not support attachments. Plug-in names may not be empty. Delete entry operations are not supported for this form. or is a reserved name. An associated error message contains details of the failure. The plug-in server is either not running. The plug-in service was unable to load the specified plug-in. Set entry operations are not supported for this form. Create entry operations are not supported for this form. The plug-in name is empty. may not contain space characters. AR System server has referenced a plug-in that the plug-in service has not loaded. Invalid decimal value. See your system administrator for assistance.Action Request System 5. AR System database connectivity plug-in associated with the form does not support create operations and a creation was attempted. for example.1 8734 Invalid currency code string length. such as “AREA. Contact your AR System Administrator for assistance. in an incorrect API program. The specified container owner name is incorrect. in an incorrect API program. This error message reports the failure when the set property function of the specified plug-in fails in any way. The specified plug-in failed to initialize properly. This is likely caused by a programming error. Load this parameter with the name of the form you want to reference. in an incorrect API program. The label of the specified reference is empty. and failed to load. 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. A parameter is required. for example. This is likely caused by a programming error. This is likely caused by a programming error. The plug-in server password has been established to restrict access to AR System servers that have been similarly configured. for example. This is likely caused by a programming error. The value of the specified reference is empty. You do not have permission to access this container. In this case. in an incorrect API program. This is likely caused by a programming error. The description of the specified reference is empty. for example. You do not have access to the specified container. Contact your AR System Administrator for assistance. The specified container is missing. The specified container does not exist. The specified plug-in failed to set properties. but the value passed is either NULL or an empty string. for example. The plug-in encountered an error while attempting to initialize. 8762 8763 8800 8801 8802 8803 8804 8805 8806 Action Request System Error Messages ! 201 . Contact your system administrator.Error Messages Guide 8761 An invalid password has been used for access to the plug-in server. for example. the password used by AR System server does not match that of the plug-in service. in an incorrect API program. 8812 8816 8817 8818 8900 8901 8902 8903 202 "Chapter 2—Action Request System Error Messages . in an incorrect API program in which the reference list is invalid. This is likely caused by a programming error. in an incorrect API program. This is likely caused when there is an error in a definition file you are attempting to import. for example. Enter a different name for the container. A dialog has no data to query. No owner name was specified. A dialog has no data to query. for example.Action Request System 5. Sort list ignored for this type of form. This is likely caused by a programming error.1 8809 Illegal container type. No name was specified for the owning object. A dialog has no data to query. in an incorrect API program. This operation cannot be performed on a dialog form. GetListFields ignored for this type of form. This operation cannot be performed on a dialog form. This is likely caused by old server containers. for example. This operation cannot be performed on a dialog form. The container is not supported by the server. A dialog has no data to query. The value of the external reference has an invalid format. Supported container types include: ! ! ! ! ARCON_GUIDE ARCON_FILTER_GUIDE ARCON_APP ARCON_PACK ARCONOWNER_NONE (container is globally owned) ARCONOWNER_SCHEMA Supported container owners are: ! ! 8810 8811 The specified container already exists. Container cannot be owned by this type of object. You attempted to define a container owner object that is not a supported container type. This is likely caused by a programming error. This operation cannot be performed on a dialog form. Sort list not allowed with this type of form. GetListFields not allowed with this type of form. Illegal reference type. This special message for logging appears when the request log type matches the current log. 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. This message occurs when you attempt to delete a field that is referenced in a table field qualification. specify shorter field widths. An attempt was made to create a join form and one of the forms in the join was a dialog form. 8909 8910 8911 8912 The ARGetListEntryWithFields call is not supported by the server. This operation cannot be performed on a dialog form. You cannot delete fields that are referenced in table field qualifications. Ensure the user name and the password exist and are correct. This type of form can only have display-only fields. run arsystem stop. Either the user name or the password is invalid or does not exist on Windows NT Logon Server. This API call is not possible with older servers.Error Messages Guide 8905 8907 8908 Escalations cannot access fields in this type of form. This logging error typically is returned if you have run out of disk space. This error appears when active link workflow attempts to perform an ARGetListEntryWithFields call with a pre-4. free up space in the log directory by deleting old or unwanted files. Error accessing semaphore. Unable to write logging to requested file. If it is. You cannot create joins with dialogs. A dialog has no data to query. or reduce the separators between columns to reduce the total to less than AR_MAX_SDESC_SIZE. This error appears when a server is unable to get or lock a semaphore. To continue. Failure during attempt to update next available VUI ID. The maximum allowed length of AR_MAX_SDESC_SIZE is 128 bytes. Remove the field name from the qualification if you want to delete the field. Remove fields from the list. Windows NT logon fails due to unknown user or invalid password. A dialog has no data to query. 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. Ensure that your machine is configured correctly for shared memory and semaphores. 8913 8914 8915 8918 Action Request System Error Messages ! 203 . Workflow logging active.0 AR System server. This operation cannot be performed on a dialog form. Dialog forms not allowed in join forms. The field is referenced in the qualifier of a table field. and then run arsystem start. Specify this value only. The external authentication server is not responding to calls from the AR System server. Authentication Note: <note> The appended text is a message from the external authentication server. Form name specified multiple times in workflow connection structure form list. it is greater than 255 characters) and therefore the event semaphore could not be opened to enable signals from server. Correct the error. The form was not found in the cache. but no form list was supplied. filter. Contact your AR System Administrator for assistance. This error is returned if the user is modifying the contents of a field but does not have write access. 8921 8922 8923 8924 8925 8926 8927 8930 8931 8932 8933 204 "Chapter 2—Action Request System Error Messages . This error is returned if there is no form list for the workflow connection. This error is returned if an invalid form is found in the form list. This error is returned if two or more forms in a form list have duplicate form names. An associated message indicates why the view was not imported. Unrecognized or misused tag for workflow connection structure. You must specify the form(s) to which the workflow is attached. This error is returned if there is an error in the FTS handle (for example. This error is returned if there are no forms in the form list. You do not have write license. The user has attempted to set the value of the external authentication RPC socket to a different value than 390695.1 8920 Must specify a workflow connection structure to create an active link.Action Request System 5. The workflow must be associated with a single form or a list of forms that currently exists on the server. No views were imported. Cannot connect to the system at this time. The legal value for the RPC socket number for the External Authentication process is 390695. This error is returned when you have not specified the form(s) for the workflow you are creating. The workflow must be associated with a list of forms that currently exist on the server. Workflow connection structure type of form list specified. This error is returned when your attempt to import views into the form failed. and try to import the item again. Error in semaphore name. The authentication service is not responding. or escalation. Authentication Error: <error> The appended text is a message from the external authentication server. This parsing error was encountered while parsing the character data. Compression failed when adding the attachment file to a request during the Perform-Action-Add-Attachment command used in a Run Process filter action. The XML file. The parser encountered an invalid element tag while parsing the XML document. Contact your AR System Administrator for assistance. Valid forms here include only the following: ! ! ! ! 8935 Distributed Mapping Distributed Pending Distributed Pool Application Pending 8936 Compression of file failed. 8937 8938 8939 8940 Error during XML definition parsing. if a user belongs to an excluded group. Error during Xerces-c Initialization. The parser encountered an invalid attribute tag while parsing the XML document. To continue. Client operation was disabled. This error is returned when parsing an XML document. for example. This error is returned because the proxy fork process was unable to write information to its log file. increase the size of the buffer used in the attachment field. The Xerces library globals used in the XML parser failed to initialize. This error is returned because only a valid internal form definition can be upgraded. XML Parsing error. The parser encountered an invalid enumeration value while parsing the XML document. Invalid attribute tag. make sure that the arplugin service and AR System plug-ins are running. Cannot connect to the system at this time. This error also is returned if the size of the input buffer exceeds 57 bytes. To continue. The AR System Plug-In server is not responding. There was an RPC time-out when connecting to the arplugin service. XML Parsing error. Invalid element tag. Invalid enumeration value. and XML object name cannot be parsed. XML Parsing error. XML Parsing error. This error is returned if a client type operation is disabled for the current user. Upgrade of the server internal forms failed.Error Messages Guide 8934 Unable to communicate with arfork daemon. XML string. 8941 8942 8943 8944 Action Request System Error Messages ! 205 . This error is returned because there were duplicate values in a custom style enumerated data type. The process stops and an error message is returned. Duplicate numeric values specified for a custom style enumerated value. The requested dateparts is not supported by this operation. The name of the library is arxmlutil. Please provide a valid license key. verify that the file exists and that you have permissions to access it. Make sure all choices are unique. This error is returned because an EXTERNAL qualification making a reference to itself is an illegal operation.Action Request System 5.1 8945 8946 No such object in the parsed XML stream. While attempting to append the string contents to the end of the file. The Status field cannot be a query style enumerated value. The values must be unique for each choice. Unable to load the arxmlutil library. This error is returned because the server failed to load the AR System XML shared library. The value of the enumerated value style is not a valid value. Either the dateparts value is invalid or this operation does not support the dateparts value. You were unable to create a license because the license key does not match the generated key based on the license information provided. the operation failed because the file could not be opened. An invalid XML document type was specified. 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. This parsing error is returned because no such XML object exists in the object list. This error can only be encountered through an API program. This error message is returned because the requested dateparts is not supported by this operation. EXTERNAL qualification contains a circular reference. This error message is returned because XML import and export is not supported for this object contained in the file. Invalid license key. A failure occurred while trying to open the file. The XML document was unable to be parsed by the server because you specified an invalid XML document type. 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 206 "Chapter 2—Action Request System Error Messages . To continue. 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 is returned because there is an invalid value for an enumerated data type. XML import and export is not supported. The client default is to make encrypted calls to the server. Server information data is in an incorrect format. Year 2002 (there are not 22 months in a year). The key exchange protocol requires shared encryption keys between the client and the server and checks the encryption policy of the server. which would be converted to Month 22. XDR sizeof error during XDR encoding. Error in encryption library. Day 15. 8958 8959 8960 9000 9001 9002 9003 9004 9005 9006 9007 Action Request System Error Messages ! 207 . You see this error message if the specified date string is invalid. The actual key exchange between the client and the server failed due to a serious error by one or both of the RPC calls. When converting a ISO or US date string to Julian calendar format. This error is returned because the RPC call failed and AR System server does not support encryption. The MAC (message authentication code) failed during the decryption routine. Data encryption key exchanged failed. Unrecognized encryption algorithm. when comparing the MAC in the decrypted message against the locally generated MAC.Error Messages Guide 8957 The date format is invalid. This error is returned because an unknown encryption algorithm was used. Server information data is not correctly formatted. This error can occur with commands that take as parameters multiple strings separated by semicolons. Encryption is required on AR System server. You see this error message if XML data type being converted is not supported by the AR System or the XML data type is invalid. Error during symmetric key data decryption. The XML data type is not supported. The date value is invalid. Encryption is disallowed on AR System server. There was a failure in generating the random number used during the encryption routine. For example. you see this error message if the string contains a date value that is not valid. This error is returned because the size of the memory buffer used in XDR (external data representation) is invalid. Public key decryption failed due to no authentication between client and server. This error is returned because AR System server does not disallow encryption. an invalid date format would be 22/15/02. Error during public key data decryption. csv or . The encryption library was not found and cannot be loaded. VUIs for a form must be unique. This error is returned because encryption is turned on but the required encryption shared library DLL could not be found or loaded. stop and start the server. you may need to delete the form and start over. Either install the encryption library or disable client/server encryption. 9052 208 "Chapter 2—Action Request System Error Messages . This error is returned because two or more AR System Message Catalog forms were found on the same server. There must only be one Message Catalog. The label. The encryption license does not match the encryption library. locale. you can have only one Message Catalog form on a server. A field on the Message Catalog form may have been deleted. This error is returned if no encryption licensing is invalid on the AR System server. For localization purposes. The form will be automatically recreated at system startup. Loading of encryption library failed. so that you can reimport it after the form is recreated at system startup.arx. yet no AR System Message Catalog form can be found on the server. . There may be several reasons why you see this error: ! ! ! 9009 9010 9011 9012 9013 9050 The form itself may have been accidentally deleted. This error is returned because encryption is required but the encryption shared library is not loaded. Corrupt data may have been added. 9051 Multiple Message Catalogs exist. This error is returned because the XDR (external data representation) process was unable to present the result pointer into the memory buffer. export any data into an . Client/server encryption is enabled but the encryption library was not found. This error is returned because the Localize Server check box has been selected in the Advanced tab of the Server Information dialog box. and platform properties of this VUI must be unique to the form. Encryption is not licensed on the AR System server. The VUI is not unique for the form. Localization has been turned on but no Message Catalog exists.1 9008 XDR xres error during XDR encoding. This error is returned because the encryption shared library DLL could not be successfully loaded. To continue.xml data file format. make sure the form actually exists.Action Request System 5. To continue. If it does not. and platform. Delete one of the Message Catalog Forms and restart the server. This error is returned if no encryption licensing is present on the AR System server. If for some reason the form itself has become corrupted. create a unique VUI combination of label. In this case. locale. To continue. 9058 9075 Action Request System Error Messages ! 209 . that its contents have not been corrupted. the format of the import file has been corrupted so that it contains no VUI information. To continue. the previously existing default admin view will be used. To get rid of this warning. 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. not even defaults. The field will not be imported. if the server events or server statistics form does not exist. 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 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. This error is returned because no VUI definition from the file was retrieved during the import operation. The server is not localized. 9057 Recursion of localized queries are not allowed. and the import process will continue. The server encountered an error while attempting to create these forms and failed to create them. make sure the Message Catalog Form actually exists. delete the Server Events and Server Statistics forms. This error is returned because a query cannot retrieve more than one localized value of a message at a time. This warning is returned because the default admin view of the form was not found during the import operation. The VUI import file is in an incorrect format.Error Messages Guide 9053 The default VUI specified in the schema import file was not found. No messages were found in the Message Catalog Form. Instead. This error is returned because the timestamp of the localized active link or menu was unable to be updated. these forms will be automatically recreated and the error will go away. the server will create them. The next time you restart the server. This is merely a warning and the server still starts okay. Possible reasons include: ! ! ! 9054 9055 9056 Message Catalog Form was not found on the server. The default VUI was redefined to a pre-existing VUI from the form. On server startup. Update of Localized Active Link or Menu failed. The specified field does not exist in the form. Error encountered during creation of the Server Schema form. and that the Localize Server check box has been selected in the Advanced tab of the Server Information dialog box. For some reason. The Localize Server check box has been cleared in the Advanced tab of the Server Information dialog box. 210 "Chapter 2—Action Request System Error Messages .Action Request System 5. the server will not allow creation of the new form. This error occurs because you cannot run multiple instances of armonitor from the same installation directory. Only one form can contain the Server Events fields. the server was unable to find the Server Events form to record an entry. You attempted to perform an operation (for example. The Server Events form is defined from a unique combination of AR System reserved fields. Error while opening the armonitor lock file. However. To continue. This error is returned during import and export operations. the server was unable to find the Server Statistics form to record an entry. If an attempt is made to create a form that contains these fields while the Server Events form already exists. There was an error returning the fully substituted command from the database. for example. opening a form) to which you have no permissions. the server will not allow creation of the new form. not as the client-side. Error encountered while executing a Web Service. In certain cases. an invalid server-side run process command. If an attempt is made to create a form that contains these fields while the Server Statistics form already exists. This error message is generated by the Web Service plug-in whenever an error occurs during the execution of a Web Service. you can run another instance of armonitor from a different installation directory. While server statistics recording was enabled. While server event recording was enabled. the process will be exported as a client-side process. The command does not occur on the local server.1 9076 Cannot find the Server Events form. (UNIX only) 9102 9130 9150 9200 User has no access permission to <name_of_object>. verify if the SQL command or run process command works from a command line. This error is returned due to a non-local server execution error during the following operations: ! ! 9077 9078 9079 9100 Executing a run process command on the server Retrieving a list of SQL values specified in the SQL command 9101 The command is not a server-side command. Check with your administrator. Only one form can contain the Server Statistic fields. because the direct SQL and run process commands are valid only as a server-side process. Error in parsing the Run Process or Direct SQL command. Cannot find the Server Statistics form. The Server Statistics form is defined from a unique combination of AR System reserved fields. Please reload page to log in again. You attempted to attach an object to an attachment pool in which no fields are left available. 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 Action Request System Error Messages ! 211 . Cannot find an attachment field large enough to hold this attachment. or perhaps you can zip the file to make it smaller. either because the session is invalid. No help available. This is an unexpected error. or perhaps you can zip the file to make it smaller. A failure occurred in retrieving a property from the configuration properties file. because all the available fields are in use. save. A failure occurred while retrieving the list of fields that contain Help text. An associated error message provides details of the failure. has timed-out. Contact your administrator to enlarge the size attachment field so that you can attach it later. Your session is no longer available. You can also try to attach to a different attachment field. The form action request failed. There was an error in one of the form actions. You have to specify a file to upload. Log in again to continue. an invalid qualification statement. You attempted a display. Please select an attachment file first. A failure occurred while trying to retrieve Help text for this form or field. or no session data was retrieved. Contact your administrator to enlarge the size attachment field so that you can attach it later. for example. enter or select a file. Cannot get the fields in the form. Modify. Failed to get config property. or Delete Entry. Submit. You entered a set of incorrect parameters for this operation. or delete operation but did not first select an attachment. There is no field large enough in the attachment pool to contain this particular file.Error Messages Guide 9201 Session is invalid or has timed out. for example. Search. The attachment file size exceeds the maximum size allowed for this attachment field. You attempted to attach a file to an attachment field but did not enter a file name. To complete this process. Illegal request parameter. for example. or ask your AR System administrator to supply more attachment fields to the attachment pool. You attempted to attach a file larger than the maximum size allowed for this attachment field. Remove any un-necessary attachments if you have permissions. There are no available attachment fields. Invalid request parameters. Servlet does not support the doGet() method. contact your AR System Administrator for assistance. because the file path was NULL. even though the system located the file. There was a failure in viewing or saving an attachment file. There was a failure to delete an attachment file because it could not be located on the web server. File not found. either because the file does not actually exists or its value is NULL. There was a problem viewing the file because. This all-purpose error occurs under a multitude of internal system failures. for example. or you did not enter a file path name. 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.Action Request System 5. The operation of saving the attachment file to disk failed. Contact your administrator. Check your permissions. Make sure that the file actually exists.1 9212 Upload file failed. There was a failure in viewing or saving an attachment file because the file could not be found on the web server. Internal error. There is no attachment file to delete. The operation of adding an attachment file failed. it was unable to be sent. including the following: ! 9213 9214 9215 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 Display or save attachment failed. a new window could not be opened to display the file. Problem sending file. 9217 9218 9219 212 "Chapter 2—Action Request System Error Messages . If that does not solve your problem. Make sure that the file actually exists. not POST. This error occurred here because the request parameters for the file were invalid. The file does not exist or is empty. To continue. Cannot convert AR System query into a Crystal query: invalid data type for enum value. rewrite the AR System query into a format more easily understood by the Crystal Report engine. Try to rewrite your AR System query in another way. Make sure that the file actually exists. To continue. 9226 9227 9228 9229 Action Request System Error Messages ! 213 . There was a failure in converting the AR System query into a Crystal Report web query because of unsupported syntax. rewrite the AR System query into a format more easily understood by the Crystal Report engine. A valid AR System query that uses a $NULL$ value must be either in a “‘field’ = $NULL$” or “‘field’ != $NULL$” format. There is no attachment file to save. but the specific reason for the failure is unknown. 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 actually exists. 9221 9222 9223 9224 Crystal Report does not allow ‘}’ in field name. Rename AR System field so that it does not use a close brace. then attempt the conversion again. the attempt to convert it into a Crystal Report web query failed. There was a failure displaying the attachment file in a new window because it could not be located on the web server. Because the AR System query did not use this format. There was a failure in converting the AR System query into a Crystal Report web query. Cannot convert AR System query into a Crystal query: bad enum field type.Error Messages Guide 9220 There is no attachment file to display. The conversion failed because an invalid enum string value appeared in the AR System query. Cannot convert AR System query into a Crystal query: no field name to match with NULL value. Download attachment failed. There was a failure during conversion because the field for which an enum value was provided is not an enum field type. An illegal field name not allowed by Crystal Reports was encountered when converting a AR System query into a Crystal Report web query. Try again or rewrite your AR System query in another way. There was a failure saving the attachment file to the client’s local file system because it could not be located on the web server. To continue. rewrite the AR System query into a format more easily understood by the Crystal Report engine. Remove this character from the fieldname. Unsupported syntax in query conversion. Please see your administrator. Make sure that the file actually exists. Please see your administrator. Please see your administrator. Query conversion failure unknown: <name_of_query>. Re-attach the definition and try again. Cannot display AR System report <name_of_report>. The report consists of a string that cannot be understand by the system. 9238 9240 9241 214 "Chapter 2—Action Request System Error Messages . An invalid operation was specified for a AR System report. Verify that the report actually exists. Cannot decode URL. Invalid AR System report definition. Please try again or see your administrator. The report operation was unable to parse the field IDs and sort order. Re-attach the definition and try again or create a new report. refer to the remainder of the message. The location (URL) of the native report cannot be decoded. The report operation was unable to parse the field attributes in the definition file. Please see your administrator. try creating a different definition file or re-designing your report. Please try again or see your administrator. To continue. The native report operation failed to open the report *. Cannot parse AR System report definition. 9231 9233 9234 9235 9236 9237 Problem in parsing AR System report definition: no 'Report: ' string found. Also check the disk permissions on your configured report directory. The native report output failed because of an invalid report definition. See your administrator. try creating a different definition file or re-designing your report.arr definition file. To continue. or create a new report. Please see your administrator. Report the problem to your administrator. or create a new report. Re-attach the definition and try again. To continue. try creating a different definition file or re-designing your report. Cannot create report directory <name_of_directory>. Check the name of the configured report directory and try again. try creating a different definition file or re-designing your report. Re-attach the definition and try again or create a new report. The native report output failed because the file location was not specified. Bad report operation for AR System reports. See your administrator. To continue. Field has no information in AR System report definition. Please try again or see your administrator. The native report output failed because the report definition specified no fields. Cannot open AR System report file <name_of_file>. The native report failed to appear on your browser for unknown reasons.1 9230 Report filespec location not specified for native reports.Action Request System 5. You might also check your permissions and try again. To continue. To continue. 9243 9244 9245 9246 9247 9248 9249 9250 Action Request System Error Messages ! 215 . No attachment information for report attachment. Ask your administrator to check the report form definition. There was a failure when extracting the report because information about the attachment field could not be retrieved. Please try again or see your administrator. Cannot find report type <type_of_report>. create. To continue. There was a failure when extracting the report due to an invalid data type for the attachment field. an invalid operation was used to post the report. The only valid operations are run. Internal error: Bad data type for query class field. There was a failure extracting the report definition file because no session-specific report directory could be retrieved from the configuration. Cannot find report <name_of_report> of type <type_of_report> for form <name_of_form> on server <name_of_server>. Please try again or 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 engine’s format. There was a failure when extracting the report because the file name of the report could not be retrieved. See your administrator. To continue. No file name for report attachment. check the report and report type forms on the server for valid report names and types. When creating a report in the Open Window action. verify that the query converter class is installed in your CLASSPATH. To continue. To continue. No base directory specified for reporting. See your administrator. or create. fix the action to use a valid operation. use the AR System Configuration Tool to specify a report directory. To continue. See your administrator. edit. There was a failure to load the query converter class when converting the query string from the AR System native format into the report engine’s format. See your administrator. See your administrator. Operation is either run. To continue. Cannot load query converter class <type_of_class>. check that the report’s entry in the report form has a valid attachment. Invalid report operation. There was a failure to retrieve the report type when querying the Report form for the entry that matches the parameters in the request.Error Messages Guide 9242 Bad data type for report attachment field. check the report and report type forms on the server for valid report names and types. Please try again or 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. or edit. See your administrator. check that the report’s entry in the report form has a valid attachment. There were permissions problems in creating a report directory. check the report type form definition.) 9252 9253 9254 9255 9256 9257 9259 Problem opening output stream: <contents_of_string> Please see your administrator. verify that the mid tier has write access to this directory. To continue. 9260 9261 216 "Chapter 2—Action Request System Error Messages . There was a failure locating this object (for example. a schema. See your administrator. verify that the object indeed exists on AR System server.Action Request System 5. Report configuration property <name_of_object> not found. or container) in the server cache. Please see your administrator. See your administrator. To continue. Cannot instantiate query converter class <name_of_class>. An inappropriate command was issued for the report because of an invalid data type. Please see your administrator. check that the query converter class implements the report query converter interface. Status history is displayed for the web in a separate window. There was a failure retrieving the configuration object and the report configuration property for this specific session. No such object(s) in AR System server. There was a failure because the report operation command does not have a command specified for this report type. See your administrator. refer to AR System Java API documentation in HTML format.1 9251 Bad data type for report operation command field. AR System server <name_of_server> does not have form with ID <number_of_ID>. Security violation in creating directory <name_of_directory>: <name_of_directory>. Problem with starting query conversion: <contents_of_string>. 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 engine’s format. verify that the query converter class implements the report query converter interface. To continue. There was a failure creating the XML string containing the Status History field information. Error generating Status History information. (For information on the QualifierInfo class. There was a failure creating the report definition file from the Message Catalog. active link. 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. To continue. Report operation command is empty. To continue. There was an initial failure when converting the original query string into a QualifierInfo structure that the report engine’s format can interpret. See your administrator. enter a value for the required field and re-try the Submit operation. Check your permissions to continue. The Submit operation failed when creating an AR System request. 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. a required field is left blank. Check your permissions to continue. The request was therefore ignored. There was a failure to retrieve the request because that entry ID does not exist in the database. You attempted to access an AR System form that you have no permissions to. In this particular case. User has no access permission to the field <name_of_field>. You attempted to access a field that you have no permissions to. There are many possible causes for a Submit failure. Please select an entry first. The JSP path could not be constructed because some of the following data is missing: ! ! ! ! Form View Application Locale 9269 Unable to perform query because results list field not found. 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. for example. Required parameters include the following: ! ! 9263 9264 9265 9266 9267 Form (or form alias) Server name 9268 Problem opening form in Direct Access. Entry with ID <number_of_ID> does not exist in database. Possible causes for this error include. The Modify operation failed when updating an AR System request. 9270 Action Request System Error Messages ! 217 . Please inform your AR System administrator. a simultaneous modification by another user or a failure in workflow.Error Messages Guide 9262 Submit failed. There was a failure displaying the status history in a new window because no entry was selected. There was a failure in the query because the result list in the form could not be located. There was a failure retrieving the path of the JSP page that represents the form. for example. Modify failed. User has no access permission to the form <name_of_form>. Action Request System 5.1 9271 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. 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 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. 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 AR System 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 AR System Administrator for a different multiple match response in AR System, for example, Set Field to $NULL$. 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. 9272 9273 9275 9276 9277 9278 9279 9280 218 "Chapter 2—Action Request System Error Messages Error Messages Guide 9281 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>. There was a failure during login, because you entered an invalid password. To continue, try re-entering your password. 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$. 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 ensure that it returns at least one matching request. 9282 9283 9289 9291 9292 9293 9294 9295 9296 Action Request System Error Messages ! 219 Action Request System 5.1 9297 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. The original table field/results list query will be used. There was a failure converting the AR System query format into the report engine’s 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: ! 9298 9299 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. ! ! ! 9300 Error occurred when executing process. 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 4.x AR System servers. There was a failure retrieving a user from the pool of available users, because a user pool only works with 4.x (and higher) AR System servers. 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: <name_of_group>: <group_ID>. The qualification failed because it was unsuccessful translating the group names into group IDs. 9301 9303 9304 9305 220 "Chapter 2—Action Request System Error Messages Error Messages Guide 9306 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. 9307 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 code for a currency field. This error message is returned because you did not enter an allowable currency code on a currency field. For example, you entered 1,000 USX, or some other allowable currency code not defined by the 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 name space of the input message is <name_of_namespace>. It must be of the format urn:server: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 correct format you must use is urn:server_name:web_service_name. 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. 9308 9309 9310 9325 9326 9327 9329 9330 Action Request System Error Messages ! 221 Action Request System 5.1 9331 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. 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 mid tier 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). 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. 9332 9334 9335 9336 9337 9338 9339 9701 222 "Chapter 2—Action Request System Error Messages Error Messages Guide 9800 Problem encountered during creation of the Email form. This error message is returned if the Email form does not contain the correct number of required email fields. 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. 9801 Action Request System Error Messages ! 223 Action Request System 5.1 224 "Chapter 2—Action Request System Error Messages message 11 custom error messages 17 G guide. organization of 15 H help documentation 13 D diagnostic messages AR System Error Messages form 13 AR System Message Catalog form 14 error message files 13 message catalogs 11 message reporting 10 messages not in catalog 12 syslog 10 UNIX server errors 10 Windows NT server errors 11 display data types 37 documentation. AR System 18 F forms AR System Error Messages 13 AR System Message Catalog 14 C catalogs.Index A AR System diagnostic messages help 13 message catalogs 11 message reporting 10 UNIX server errors 10 AR System error messages 18 AR System Error Messages form 13 AR System Message Catalog form 14 E error definition 8 error message files 13 error messages. help 13 I internationalizing message catalogs 12 M message catalogs 11 internationalizing 12 message not in catalog 12 message definition 8 messages custom 17 reporting 10 server error reporting on UNIX 10 N note definition 8 Index ! 225 . Action Request System 5.1 O organization of guide 15 R reporting. message 10 S server error reporting UNIX 10 Windows NT 10 server errors AR System 18 UNIX 10 UNIX message catalogs 11 Windows NT 11 syslog 10 T troubleshooting. See diagnostic messages U UNIX error message file 13 message catalogs 11 server error reporting 10 server errors 10 W warning definition 8 Windows NT server error reporting 10 server errors 11 226 " Index .
Copyright © 2024 DOKUMEN.SITE Inc.