Error messages 8900 to 9100

The GetListFields operation cannot be performed on a dialog form.

This operation cannot be performed on a dialog form. A dialog has no data to query.

The GetListFields operation cannot be performed on a dialog form.

This operation cannot be performed on a dialog form. A dialog has no data to query.

The Sort List operation cannot be performed on a dialog form.

This operation cannot be performed on a dialog form. A dialog has no data to query.

The Sort List operation cannot be performed on a dialog form.

This operation cannot be performed on a dialog form. A dialog has no data to query.

Escalations are not allowed on a dialog form.

This operation cannot be performed on a dialog form. A dialog has no data to query.

Dialog form can only have display-only fields.

This operation cannot be performed on a dialog form. A dialog has no data to query.

Windows Logon fails.

Either the user name or the password is invalid or does not exist on Windows Logon Server. Make sure that the user name and the password exist and are correct.

Dialog forms are not allowed in join forms.

An attempt was made to create a join form and one of the forms in the join was a dialog form. You cannot create joins with dialogs.

Field referenced in the qualifier of a table field cannot be deleted.

You tried to delete a field referenced in a table field qualification. You cannot delete fields referenced in table field qualifications. To delete the field, remove the field name from the qualification.

Some of the fields have been truncated from the results list because the total length of the fields and separators is greater than the maximum allowed.

The maximum allowed length of AR_MAX_SDESC_SIZE is 128 bytes. Remove fields from the list, specify shorter field widths, or reduce the separators between columns to reduce the total to less than AR_MAX_SDESC_SIZE.

The ARGetListEntryWithFields call is not supported by the pre-4.0 AR System server.

Active link workflow tried to perform an ARGetListEntryWithFields call with a pre-4.0 BMC Remedy AR System server. This API call is not possible with older servers.

A server could not get or lock a semaphore. Make sure that your computer is correctly configured for shared memory and semaphores. If it is, run arsystem stop, and then run arsystem start.

A server could not get or lock a semaphore. Make sure that your computer is correctly configured for shared memory and semaphores. If it is, run arsystem stop, and then run arsystem start.

Workflow logging activated.

The request log type matches the current log.

Insufficient disk space for logging to requested file. Free up disk space before continue.

This logging error typically is returned when you run out of disk space. To continue, free up space in the log directory by deleting old or unwanted files.

Unable to update next available VUI ID.

You were unable to update the next field ID column in the database for a new VUI in a form.

Must specify a form for the workflow to create an active link, filter, or escalation.

You did not specify the forms for the workflow you are creating. Specify the forms to which the workflow is attached.

The form list for the workflow contains no forms.

The form list contains no forms. The workflow must be associated with a single form or a list of forms that exist on the server.

The authentication service is not responding. Cannot connect to the system at this time. Contact your BMC Remedy AR System Administrator for assistance.

The external authentication server is not responding to calls from the BMC Remedy AR System server.

Unrecognized or misused tag for workflow connection structure.

No form list exists for the workflow connection. The workflow must be associated with a list of forms that exist on the server.

The legal value for the RPC socket number for the External Authentication process is 390695.

The user tried to set the value of the external authentication RPC socket to a value other than 390695. Specify 390695 only.

The appended text is a message from the external authentication server:note.

The appended text is a message from the external authentication server.

The appended text is a message from the external authentication server: error.

The appended text is a message from the external authentication server.

The form was not found in the cache.

An invalid form was found in the form list.

Error in semaphore name.

An error exists in the FTS handle (for example, it is greater than 255 characters), and therefore the event semaphore could not be opened to enable signals from server.

You do not have write license.

A user is modifying the contents of a field but does not have write access.

No views were imported.

Your attempt to import views into the form failed. An associated message indicates why the view was not imported. Fix the problem, and reimport the item.

The proxy fork process could not write information to its log file.

The proxy fork process could not write information to its log file.

Upgrade of the server internal forms failed. Only a valid internal form definition can be upgraded.

Only a valid internal form definition can be upgraded. Only the following forms are valid here:

• Distributed Mapping
• Distributed Pending
• Distributed Pool
• Application Pending

Compression of file failed.

Compression failed when adding the attachment file. To continue, verify that enough memory is available for the client program, which could be either the Mid Tier, or a plug-in server, or a custom Java program by using AR API. Check if the file exists in the given path and has appropriate permissions. If the issue is still not resolved, see the appended message provided in the error and fix the root cause. 

You do not have permission to the client operation: operationName.

A client-type operation was disabled for the current user, for example, if a user belongs to an excluded group.

Error during Xerces-c Initialization.

The Xerces library globals used in the XML parser failed to initialize.

The AR System Plug-In server is not responding. Cannot connect to the system at this time. Contact your BMC Remedy AR System Administrator for assistance.

An RPC time-out occurred when connecting to the plug-in server. Make sure that the plug-in server and BMC Remedy AR System plug-ins are running. For more information about troubleshooting plug-in server connectivity, see the entry for error 8760.

Error during XML definition parsing.

An error occurred when an XML document was parsed. The XML file, XML string, and XML object name cannot be parsed.

XML Parsing error. Invalid element tag.

The parser found an invalid element tag while parsing the XML document.

XML Parsing error. Invalid attribute tag.

The parser found an invalid attribute tag while parsing the XML document.

XML Parsing error. Invalid enumeration value.

The parser found an invalid enumeration value while parsing the XML document.

XML Parsing error. Invalid character data.

This parsing error occurred while the character data was parsed.

No such object in the parsed XML object list.

This parsing error is returned because no such XML object exists in the object list.

EXTERNAL qualification contains a circular reference.

An EXTERNAL qualification making a reference to itself is an illegal operation. The process stops and an error message is returned.

Invalid license key. Please provide a valid license key.

You were unable to create a license because the license key does not match the generated key based on the license information provided.

Invalid session configuration option.

You were unable to set a valid public API session variable. This error can be encountered only through an API program.

Invalid enumerated value style.

An enumerated data type has an invalid value.

Custom style enumerated value must be unique for each choice. The specified value is a duplicate.

Duplicate values exist in a custom style enumerated data type. Make sure all choices are unique.

The Status field cannot be a query style enumerated value.

The Status History field of a Data Dictionary style character menu cannot be expanded as a query style enumerated value.

An invalid XML document type was specified.

The server could not parse the XML document because you specified an invalid XML document type.

Unable to load the arxmlutil library.

The server failed to load the BMC Remedy AR System XML shared library. The name of the library is arxmlutil.

A failure occurred while trying to open the file.

While trying to append the string contents to the end of the file, the operation failed because the file could not be opened. To continue, verify that the file exists and that you have permissions to access it.

XML import and export is not supported.

XML import and export is not supported for this object in the file.

This operation does not support the specified date part.

The requested date parts are not supported by this operation. Either the date parts value is invalid, or this operation does not support the date parts value.

The date format is invalid.

The specified date string is invalid. For example, an invalid date format would be 22/15/02, which would be converted to Month 22, Day 15, Year 2002 (a year has only 12 months).

The date value is invalid.

When converting an ISO or US date string to Julian calendar format, you see this error message if the string contains an invalid date value.

The XML data type being converted is not supported by AR System.

The XML data type being converted is not supported by BMC Remedy AR System or the XML data type is invalid.

Server information data is in an incorrect format.

Server information data is not correctly formatted. This error can occur with commands that take as parameters multiple strings separated by semicolons.

A required element is missing from the XML input document.

Verify that the XML input document is correct for the XML mapping document. A required element is missing from the XML input document.

Unexpected element encountered in the input XML document.

Verify that the XML input document is correct for the XML mapping document. An unexpected element is in the input document.

The number of entries exceeds the XML element's maxOccurs value.

The number of entries in the list must be equal to or less than the maxOccurs value.

The number of entries is less than XML element's minOccurs value.

The number of entries in the list must be equal to or greater than the minOccurs value.

The default notification mailbox is not specified.

No default mailbox was configured so no default mailbox is available for the email notification.

Required XML element is missing from the XML mapping.

The format of the XML mapping document is incorrect and must be corrected.

Required XML attribute is missing from the XML mapping.

The format of the XML mapping document is incorrect and must be corrected.

A required attribute is missing from the XML input document.

Verify that the XML input document is correct for the XML mapping document. A required attribute is missing from the XML input document.

The key for this entry must be unique in the XML input document.

The key for this entry must be unique in the XML input document.

The reserved centralized user preference field can only exist on one form-- delete the duplicate.

The system found two forms containing the reserved centralized user preference field. Delete one of the forms.

The reserved centralized administrator preference field can only exist on one form -- delete the duplicate.

The system found two forms containing the reserved centralized administrator preference field. Delete one of the forms.

The reserved centralized file preference field can only exist on one form-- delete the duplicate.

The system found two forms containing the reserved centralized file preference field. Delete one of the forms.

The "from information" of the email notification message cannot exceed 255 bytes.

Enter "from information" of 255 bytes or less for the email notification message.

The "reply to" information of the email notification message cannot exceed 255 bytes.

Enter "reply to" information of 255 bytes or less for the email notification message.

The CC list of the email notification message cannot exceed 255 bytes.

Enter CC information of 255 bytes or less for the email notification message.

The BCC list of the email notification message cannot exceed 255 bytes.

Enter BCC information of 255 bytes or less for the email notification message.

The organization list of the email notification message cannot exceed 255 bytes.

Enter organization information of 255 bytes or less for the email notification message.

The mailbox name information of the email notification message cannot exceed 255 bytes.

Enter mailbox name information of 255 bytes or less for the email notification message.

Failed to open a system form definition file:fileName.

The server failed to open a system form definition file that should be in a standard location. The server needs to add the system form by importing the definition from the file. Make sure the file specified in the error message is present and accessible.

Setting application owner is disallowed.

The application owner object property cannot be set.

Object is already owned by another application.

This object has an application owner and cannot be added to this application. To add the object to this application, first remove it from the application that owns it.

Changing the data type of the field is not allowed.

You cannot perform an import in place operation if the data type of a source field is different from the data type of a destination field with the same field ID.

Group permissions have been removed from the object because the object is in a deployable application.

A deployable application cannot have group permissions.

Roles permissions have been removed from the object because the object is not in a deployable application.

An object not in a deployable application cannot have role permissions.

The alias for this object is not unique. It will be set to empty string.

The web alias names for applications, forms, and views must be unique. The web alias names for views must be unique in all views for the form.

Change field action can only be: 1 to indicate a field or 0 to indicate a value.

The option value that was specified is invalid. It must be specified as 1 to indicate a field or to 0 to indicate a value. Contact your BMC Remedy AR System administrator.

Archive or Audit information could not be set for this form.

This message is accompanied by more specific messages. Examine the associated messages to diagnose the problem.

Cannot delete data fields from Archive or Audit form.

An attempt was made to delete data fields (field types 1 to 14 and 35 to 37) from an archive or audit form. To delete a field, clear the Enable option in the source form to disable archiving or auditing for the form first.

Cannot modify Limit Info or Permission for a data field in an Archive or Audit form.

These values will be made NULL before setting. This warning is returned when the LimitInfo or Permission property for a field that takes data (field types 1 to 14 and 35 to 37) in an archive or audit form is modified. The system sets these properties to NULL before setting them. Set these values to NULL to avoid seeing the warning message.

Cannot create this field in Archive or Audit Form. If this is a main form, then a field with that ID exists in the Archive/Audit form and archive or audit will be disabled. If this is an Archive/Audit form then fields of this type cannot be created.

When a field is created in the source form, BMC Remedy AR System tries to create the same field in the corresponding archive or audit form. This error is returned if another field with the same field ID but a different data type exists in the archive or form. Either create the field with the same ID and data type in the source form, or clear the Enable option for archive or audit on the source form. Data fields, such as fields with data types 1 to 14 and 35 to 37, cannot be created in an archive or audit form.

An archive or audit form cannot be created for a source form because of a lack of memory or a database error. Archive/Audit for this form has been disabled.

An archive or audit form cannot be created for a source form because of a lack of memory or a database error. The create or set operation on the source form completes, but archive/audit is disabled.

If any of the Copy options are chosen, form name must be present.

The Archive Type selected is Copy To Archive And Delete From Source or Delete From Source, but the archive form name was not specified. Enter a form name in the Archive To Form field.

Both the Source form and the Archive or Audit form must belong to the same Application.

You cannot add or remove only the source form or only the associated archive/audit form from an application. The source form and a corresponding archive/audit form must be removed from an application together, or added to an application together.

Archive Type does not match the remaining archive information passed in.

If archiveType is not one of the valid archive types or archiveType is AR_ARCHIVE_NONE, all other fields, including form name, time, enable, and query, should also be empty. Specify the correct archive type with the right parameters in the API call.

Archive not possible on Dialog or Archive forms. For Vendor forms, only 'Copy to Archive' option is available.

Forms with a Dialog or Archive form type cannot be archived. Only the Copy to Archive archive type is available for Vendor type forms.

Turn off the archive or audit to this form in order to delete this form.

If an archive or audit form is being deleted and its source form has archive or audit enabled, either disable archive or audit on the source form, or if you use the ARDeleteSchema API call, use the AR_SCHEMA_SHADOW_DELETE option.

Cannot modify or create entries in an Archive or Audit form.

You cannot create or modify existing entries in an archive or audit form. If you are using the MergeEntry API call, entries can be added to the form, but existing entries cannot be overwritten or modified. Also, filters (Push field or Set field) cannot modify or create entries in an archive or audit form.

The Archive or Audit form is invalid. Archive or Audit form should be of proper type, proper permissions as the source form. Please check the manual for requirements for a valid Archive or Audit form.

An existing form that is not a valid archive/audit form is specified as an archive/audit form. Fix the archive/audit form, or specify the name of an existing form, and BMC Remedy AR System automatically creates a valid archive/audit form. For more information about archive and audit forms, see Configuring data archiving for a form and Auditing changes to data.

Encryption is disallowed by the BMC Remedy AR System server.

The RPC call failed, and BMC Remedy AR System server does not support encryption.

Encryption is required by the BMC Remedy AR System server.

The BMC Remedy AR System server does not disallow encryption. The key exchange protocol requires shared encryption keys between the client and the server and checks the encryption policy of the server. The client default is to make encrypted calls to the server.

Data encryption key exchange failed.

The actual key exchange between the client and the server failed due to a serious error by one or both of the RPC calls.

Error during public key data decryption.

Public key decryption failed due to no authentication between client and server.

Error during symmetric key data decryption.

The MAC (message authentication code) failed during the decryption routine, when comparing the MAC in the decrypted message against the locally generated MAC.

An error occurred in the encryption library.

An attempt to generate the random number used during the encryption routine failed.

The specified public key encryption algorithm is not supported by the encryption library.

An unknown encryption algorithm was used.

The size of the memory buffer used in XDR (external data representation) is invalid.

The size of the memory buffer used in XDR (external data representation) is invalid.

XDR xres error during XDR encoding.

The XDR (external data representation) process could not present the result pointer into the memory buffer.

The encryption library was not found and cannot be loaded.

Encryption is turned on, but the required encryption shared library DLL could not be found or loaded.

Loading of encryption library failed.

The encryption shared library DLL could not be successfully loaded.

Encryption is not licensed on the BMC Remedy AR System server.

No encryption licensing is on the BMC Remedy AR System server.

The encryption license does not match the encryption library.

No encryption licensing is invalid on the BMC Remedy AR System server.

The encrypted string is greater than the maximum length allowed.

The actual size of the string exceeds the size limit specified for the string. This error can occur when the string becomes corrupted.

To encrypt/decrypt a null string is not allowed.

An internal error occurred because the string has a NULL value.

An error occurred with the decryption because the CRC is invalid.

The encrypted string could not be decrypted because the cyclic redundancy check (CRC) failed. An invalid CRC indicates that the encrypted string is corrupted.

FIPS encryption failed.

To comply with FIPS 140-2 standards, the encryption library must enter FIPS mode. This error indicates the encryption library failed to enter FIPS mode.

Client cannot connect to this FIPS-compliant server because the client is connected to a server that does not enforce FIPS.

Servers that enforce FIPS compliance have one of these encryption configurations:

• Encrypt-Data-Encryption-Algorithm set to 8 (Performance Security) and Encrypt-Security-Policy set to 1
• Encrypt-Data-Encryption-Algorithm set to 9 (Premium Security) and Encrypt-Security-Policy set to 1

Servers that do not enforce FIPS compliance include the following:

• Servers on which Encrypt-Data-Encryption-Algorithm is set to 6 or 7
• Servers using AR System 7.1 encryption modes
• Servers using no encryption
• Servers whose encryption is disabled
• Servers on which encryption is allowed (Encrypt-Security-Policy set to 0) but not required (Encrypt-Security-Policy set to 1)

Client cannot connect to this FIPS-noncompliant server because the client is connected to a server that enforces FIPS.

Servers that enforce FIPS compliance have one of these encryption configurations:

• Encrypt-Data-Encryption-Algorithm set to 8 (Performance Security) and Encrypt-Security-Policy set to 1
• Encrypt-Data-Encryption-Algorithm set to 9 (Premium Security) and Encrypt-Security-Policy set to 1

Servers that do not enforce FIPS compliance include the following:

• Servers on which Encrypt-Data-Encryption-Algorithm is set to 6 or 7
• Servers using AR System 7.1 encryption modes
• Servers using no encryption
• Servers whose encryption is disabled
• Servers on which encryption is allowed (Encrypt-Security-Policy set to 0) but not required (Encrypt-Security-Policy set to 1)

FIPS mode requires the security policy to be "encryption required".

The AR System server Encrypt-Data-Encryption-Algorithm option is set to 8 (FIPS-compliant performance security) or 9 (FIPS-compliant premium security) but the Encrypt-Security-Policy option is set to 0 (encryption allowed but not required). Therefore, the AR System server or the Java plug-in server did not start. For more information, see the AR System server arerror.log file or the Java plug-in server arplugin.log file. To fix this error, set Encrypt-Security-Policy to 1 (encryption required).

Localization has been turned on but no Message Catalog exists.

The Localize Server check box is selected on the Advanced tab of the Server Information dialog box, but an BMC Remedy AR System Message Catalog form cannot be found on the server. This error can occur for several reasons:

• The form might have been deleted.
• A field on the Message Catalog form might have been deleted.
• Corrupt data might have been added.

To continue, make sure the form exists. If it does not exist, stop and start the server. The form is automatically re-created at system startup. If the form itself is corrupted, you might need to delete the form and start over. In this case, export any data into an .arx, . csv or .xml data file format so that you can reimport it after the form is re-created at system startup.

Multiple Message Catalogs exist. There must only be one Message Catalog.

Two or more BMC Remedy AR System Message Catalog forms were found on the same server. To continue, you can have only one Message Catalog form on a server. Delete one of the Message Catalog Forms and restart the server.

The VUI is not unique for the form. The label, locale, and platform properties of this VUI must be unique to the form.

For localization purposes, VUIs for a form must be unique. To continue, create a unique VUI combination of label, locale, and platform.

The default VUI specified in the schema import file was not found. The default VUI was redefined to a pre-existing VUI from the form.

The default admin view of the form was not found during the import operation. Instead, the previously existing default admin view is used.

The specified field does not exist in the form.

The display instance of a field in the VUI did not correspond to the display instance of the field in the cache during the import operation. The field is not imported, and the import process continues.

The VUI import file is in an incorrect format.

No VUI definition from the file was retrieved during the import operation. The format of the import file was corrupted so that it contains no VUI information.

The server is not localized.

This error is returned when a request is made to return multiple localized texts from the Message Catalog Form but the server is not actually localized. Possible reasons include:

• Message Catalog Form was not found on the server.
• No messages were found in the Message Catalog Form, not even defaults.
• The Localize Server check box was cleared in the Advanced tab of the Server Information dialog box.

To continue, make sure the Message Catalog Form exists, that its contents is not corrupted, and that the Localize Server check box is selected in the Advanced tab of the Server Information dialog box.

Recursion of localized queries are not allowed.

A query cannot retrieve more than one localized value of a message at a time.

Update of Localized Active Link or Menu failed.

The timestamp of the localized active link or menu could not be updated.

The join form contains a circular reference.

Fix the join form definition.

A system error prevented the Unicode converter from being opened.

A system error prevented the Unicode converter from being opened.

Failed to convert the Character data to Unicode format.

Character data could not be converted to Unicode format.

Failed to convert from Unicode format to character data.

Character data could not be converted from Unicode format.

Server allows only Unicode clients (except Administrator).

BMC Remedy AR System server does not support non-Unicode clients such as BMC Remedy Data Import (GUI Version), the runmacro program, and version 6.3 of the Mid Tier. The server provides limited Unicode support for BMC Remedy Administrator. To contact this server, use a browser. Use BMC Remedy Developer Studio instead of BMC Remedy Administrator.

Problem encountered during creation of one of the server system forms.

On AR System server startup, if one of the AR System server's system forms does not exist, BMC Remedy AR System creates it. This message indicates that AR System failed to create the missing forms, however, AR System still starts. You might also see this message when starting the AR System server if you replace the AR System executable or do not overwrite the database when installing AR System. To eliminate the message, delete the Server Events and Server Statistics forms. The next time you restart AR System, these forms are automatically re-created, and the message no longer appears.

Cannot find the Server Events form.

While server event recording was enabled, the server could not find the Server Events form to record an entry.

Server Events fields can only exist on one form. Delete the duplicate.

The Server Events form is defined from a unique combination of BMC Remedy AR System reserved fields. If an attempt is made to create a form that contains these fields while the Server Events form exists, the server prevents creation of the new form.

Cannot find the Server Statistics form.

While server statistics recording was enabled, the BMC Remedy AR System server could not find the Server Statistics form to record an entry. The form might have been deleted or a system failure might have occurred. To automatically re-created the form, restart the BMC Remedy AR System server.

Server Statistics fields can only exist on one form. Delete the duplicate.

The Server Statistics form is defined from a unique combination of BMC Remedy AR System reserved fields. If an attempt is made to create a form that contains these fields while the Server Statistics form exists, BMC Remedy AR System prevents creation of the new form.

Application Statistics fields can only exist on one form. Delete the duplicate.

The Application Statistics form is defined from a unique combination of BMC Remedy AR System reserved fields. If an attempt is made to create a form that contains these fields while the Application Statistics form exists, BMC Remedy AR System prevents creation of the new form.

Cannot find the Application Statistics form.

While application statistics recording was enabled, the BMC Remedy AR System server could not find the Application Statistics form to record an entry. The form might have been deleted or a system failure might have occurred. To automatically re-create the form, restart the BMC Remedy AR System server.

Application Statistics fields can only exist on one form. Delete the duplicate.

The Application Statistics Configuration form is defined from a unique combination of BMC Remedy AR System reserved fields. If an attempt is made to create a form that contains these fields while the Application Statistics Configuration form exists, BMC Remedy AR System prevents creation of the new form.

Cannot find the Application Statistics Configuration form.

The BMC Remedy AR System server could not find the Application Statistics Configuration form. The form might have been deleted, or a system failure might have occurred. To automatically re-create the form, restart the BMC Remedy AR System server.

User is currently connected from another machine.

A user cannot log in to BMC Remedy AR System from two computers at the same time.

If a user holding the license, has logged on to the client for more than 15 minutes, ARERR 9093 is displayed after the initial ARERR 9084. ARERR 9093 is not displayed if the log on time interval is less than 15 minutes.

Host IP address not found.

The BMC Remedy AR System server did not find the client IP address in the API call. Contact Customer Support.

The import file does not hold an application definition.

The import file does not hold an application definition.

User data is corrupted.

User information in an internal database table is damaged or corrupted. Contact Customer Support.

Cannot change license type of a user to Fixed more than 3 times in 1 week.

An attempt was made to change the license type of a user to fixed more than three times within one week. Obtain additional fixed licenses if necessary.

User data is corrupted. License deleted.

User information is being updated and information for the user is damaged or corrupted. The user license was deleted by the system. Contact Customer Support.

User is currently connected from another machine.

ARERR 9093 can be found in the arapi log file.

A user cannot log in to BMC Remedy AR System from two computers at the same time. You can terminate the connection to AR System from the other computer.

If a user holding the license, has logged on to the client for more than 15 minutes, ARERR 9093 is displayed after the initial ARERR 9084. ARERR 9093 is not displayed if the log on time interval is less than 15 minutes. You now get a dialog with a Yes and No option to override your other connection.

Subadministrator group permissions have been removed from the object because the object is in a deployable application.

A deployable application cannot have subadministrator group permissions.

Subadministrator roles permissions have been removed from the object because the object is not in a deployable application.

An object not in a deployable application cannot have subadministrator role permissions.

Value specified for the Authentication Chaining Mode is outside the valid range of 0 - 4.

This error occurs when the authentication chaining mode parameter is set outside the valid range in the BMC Remedy AR System configuration file. For more information, see Specifying authentication chaining mode.

Cannot find the Server License form.

The AR System server is unable to locate a form containing the server licenses, which might have been accidentally removed. The Server License form is automatically created when AR System is started, so try restarting the server. If the problem still occurs, contact Customer Support. If restarting fixes the problem, you might need to re-enter the server licenses. If the problem is not fixed, AR System runs in evaluation mode.

Server License fields can only exist on one form. Delete the duplicate form formName.

The AR System server can contain only one form containing the license fields. Note that the license form field IDs are in the restricted range. This error can be caused by creating a copy of the license form.

The command does not occur on the local server.

A remote server execution error occurred during the following operations:

• Executing a run process command on the server
• Retrieving a list of SQL values specified in the SQL command