Error messages 300 to 399
The system encountered an error during a call to allocate space. The failure occurred on the server during processing of a call from the client. In general, this error occurs when too many processes are running or when some processes have grown to occupy most or all available memory on the server. Recover the memory by shutting down unneeded processes or by restarting processes that have been running for a while.
An error occurred while writing to the indicated file. An accompanying message from the operating system provides details. Determine why the write failed, and correct the problem before retrying the command.
No entry exists in the database with the Request ID you specified. The specified Request ID is invalid, or the entry was deleted by another user during the time you were processing it.
This message is returned by web services and API programs. In the same situation, similar messages are returned by web clients (see error message 9296).
The server has no form with the specified name. Either the specified name is incorrect, or the form is on another server.
Some operations in the system are restricted to users with Administrative access. These operations include the ability to restructure the database by adding forms, filters, and active links and the ability to delete existing requests from the database. To perform this operation, log in as a user who has administrative permission to the form you want to update.
BMC Remedy AR System automatically generates IDs for requests in the system. The next available ID will overflow the definition for the Request ID field.
If you specified a length for the Request ID field that is less than the maximum allowed (
As a final option, contact Customer Support to help you reset the next request ID counter. Do not try this task yourself because numerous actions must be performed, in sequence, to make this change successful.
Limits are specified for the indicated field. These limits might be a low and high range limit if the field is an integer or real field, or a maximum length or pattern if the field is a character field. The actual limit and which field the limit is on are displayed with the error message.
Verify the value specified against the limits defined for this field. The value must be changed to be within the limits, or the limits must be redefined to allow the value specified.
During submission of a request, no value was supplied for the required field. The field does not have a default value, so a value must be supplied during the submit operation.
Perform one of these actions:
A field was specified twice in the field or value list. Each field can be assigned only a single value and can be specified only a single time in the field or value list.
Remove the duplicate definition from the list, and reissue the command.
The entry you are trying to modify was modified by another user after the last time you retrieved the definition. The changes made might impact your changes. You can override this error and apply the changes. If you apply the changes (and override the error), all changes you make take precedence over the changes made by the previous user. If you do not apply your changes, the previous user's changes are retained.
The value for a field in the field or value list is incompatible with the data type defined for that field. The value of a field must be the same or compatible data type. Change the value specified to be compatible with the data type of the field to which the value is being assigned.
The field ID references a field that is not defined for the current form.
You attempted an operation against the wrong form or server, or the structure of the form was changed to eliminate the field ID from the form. Change to the correct form or server, or remove the Field Name from the Field Sort Order list to complete the operation.
The data types of the fields used in an arithmetic operation are not consistent with the operations allowed for that operation. For information about the allowed data types of operations, see C data types.
The data types of the fields used in a relational operation are not consistent with the operations allowed for that operation. For information about the allowed data types of operations, see C data types.
The field is not related to the current form.
You attempted an operation against the wrong form or server, or the structure of the form was changed to eliminate the field ID from the form. Change to the correct form or server, or remove the ID from the field list to complete the operation.
You are trying to delete a form or field that contains data. You must explicitly override this error for the operation to succeed. By default, the system deletes structures only when no data is lost.
During processing, an error occurred while the server tried to use a temporary file. An associated error message contains details.
By default, temporary files used by the server are created in the directory
A form with the same name already exists on this server. Form names must be unique. Choose a different name, or rename the existing form.
No group with the indicated ID exists on this server. The group ID specified is incorrect, or the group with this ID was changed or deleted from the system. Determine what groups are available. If the group ID was changed, simply change the ID, and reissue the request. Otherwise, use the ID of another group, or remove the reference to this group and reissue the request.
The operation you are performing requests a length change to one of the core fields. The field you are changing has restrictions on its length. For information about the use and limits of the core fields, see C data types.
The menu is not defined on the current server. You attempted an operation against the wrong server, or no menu is defined by that name. Change to the correct server (if the former), or specify an existing menu (if the latter).
Menus can contain a maximum of 15 levels. You specified a menu that contains more than 15 levels at some point in its hierarchy.
A character menu definition was found in which the definition of menu items and children do not form a consistent tree structure. Some children item definitions have no parent item.
The filter is not defined on the current server. You attempted an operation against the wrong server, or no filter is defined by that name. Change to the correct server (if the former), or specify an existing filter (if the latter).
The name you are specifying for this filter is already in use by a filter on this server. Choose a different name for the filter, or rename the existing filter.
You are trying to set a required field to a
Statistical operations can only be performed on integer and real fields or with arithmetic operations that result in real or integer fields (for example, the difference between two times). The operation you attempted is incompatible with these limitations.
The password you specified for the user name is not recognized. The problem can be with the password or with the authentication string (for NT authentication, the authentication string is the NT domain) or with both. Enter the password defined for this user name to access the system as that user.
You do not have write (change) access to a field that you are trying to change. You must have write access to write to that field.
You do not have write (change) access to a field that you are trying to change on this entry (request). You have write access to this field for requests assigned to you (or to a group you are a member of) or submitted by you, depending on the permission settings. On this entry, you are not serving in the role that allows you change access to the field, so you cannot change the field on this particular entry.
You do not have write access to this field at create time. This indicates that you do not have general write access to the field, and the create mode of the field is protected. You have access to this field on requests assigned to you (or a group you are a member of) or submitted by you, depending on the permission settings. Because this request does not exist yet, you are not serving in any role yet, so you cannot set the field for this instance during a submit operation.
You do not have access (read or write) to the field that you are trying to access. You must have access to a field to read or change its values.
Several reserved field definitions are reserved for BMC Remedy AR System. You specified one of these fields with settings that are incompatible with the limits set on the definition of those fields by BMC Remedy AR System. Review the discussion of the BMC Remedy AR System core and reserved fields in Core fields.
The data contents of a reserved field do not meet the rules for the data in that field. For the discussion of the BMC Remedy AR System core and reserved fields, see Creating and managing fields for details on the allowed data format.
You cannot assign a user to any of these groups using the User form. The Submitter (ID 3), Assignee (ID 4), Assignee Group (ID 7) and Dynamic (IDs 60000 to 60999) groups define per-instance access rights. You become eligible for the extra access permissions allowed to these groups if you are the Submitter or Assignee or are a member of the Assignee Group or Dynamic group for the request being displayed. You are the Submitter if your login name appears in the Submitter field, and you are the Assignee if your login name appears in the Assigned To field. Membership in a computed group is determined by the contents of the Computed Group Definition field on the Group form.
This version of BMC Remedy BMC Remedy AR System has a maximum limit of 2000 requests per database table, includes a maximum of three fixed licenses, and is configured for each client to access a maximum of one server. To obtain a version of BMC Remedy BMC Remedy AR System without these limitations, contact your BMC sales representative, an authorized reseller, or visit http://www.bmc.com.
You are merging requests into a form from another source. You specified a request ID in the merge operation that conflicts with an existing ID in the system. You did not specify to create another ID in case of conflict; therefore, the merge operation failed.
To merge the new request, specify the option to create IDs, or delete the existing request before merging the new one.
You specified a diary field in the merge operation, and the format of the diary data does not match the expected format. A diary field is a formatted character string consisting of a set of user name, time stamp, and character string triplets separated by valid separator characters. Separators are defined in the include file
If you receive this error during an import action, it is probably caused by a corrupt change diary. Try importing without the change diary. You can do this by removing the lines beginning with
You specified the Status History field in the merge operation, and the format of the status history value does not match the format expected. A Status History field is a formatted character string consisting of a set of user name and time stamp pairs organized (in order) by the various states that status can contain and separated by valid separator characters. Separators are defined in the include file
Could not run a process as requested. The process was a filter or escalation Set Fields process action. In either case, the process did not run. An associated error message might contain more details.
Determine why the process did not run, and, if possible, correct the circumstances. Then retry the operation.
The BMC Remedy AR System directory file could not be opened. An associated error message describes why the
An error occurred when loading a filter definition from the database. An internal error occurred, or manual changes were made to the contents of the database.
Two groups were defined with the same group ID but with different access characteristics. All groups are keyed by the group ID. Two or more groups with the same ID are actually a single group definition with two names. If two groups have the same ID, both definitions must specify the same group type and group category.
To correct the problem, change the group ID for the group being added to be unique, or change the type and category of the new or existing group to be of the same type and category.
The name you are specifying for this active link is already in use by an active link defined on this server. Choose a different name for the active link, or rename the existing active link.
The active link is not defined on the current server. You attempted an operation against the wrong server, or no active link is defined by that name. Change to the correct server (if the former), or specify an existing active link (if the latter).
You are not allowed to access the specified active link. Permissions defined for the active link do not allow you to get the definition of or execute the actions for the requested active link. Contact your BMC Remedy AR System administrator if you need access to the active link.
At startup, the group cache for the database contains no group definitions. Without group definitions, only BMC Remedy AR System administrators can access the system. This error usually occurs due to someone deleting data from the database. Re-establish the group structure for successful use of the database.
You specified one of the core fields in a delete operation. Core fields cannot be deleted. If you do not want to use the core field, you can ignore it by defining it as a hidden field. The obsolete core fields (IDs 9, 10, 11, 12, 13, and 14) can be deleted from your form.
During an arithmetic operation, the system detected a divide by 0. Restructure your queries to avoid this illegal operation.
The password field is a write-only field. To maintain security, you cannot specify a qualification on the password field.
During a filter or escalation action, an attempt to notify the submitter or assignee of the request occurred. However, the field holding this information contains a reference to the Submitter or Assignee group. To prevent an infinite loop, the system is canceling the notification.
If you are receiving this error, reconfigure the notification targets in your system to eliminate this condition.
You are not allowed to access the specified form. Form permissions do not allow you to get the definition of the form or of its fields or to access the data it contains. Contact your BMC Remedy AR System administrator if you need access to the form.
Only users with administrator permission can access (for read or change) a filter definition. The current user does not have administrator permission.
The name you are specifying for this character menu is already in use by a character menu defined on this server. Choose a different name for the character menu, or rename the existing character menu.
The character menu definition contains too many items on one level of the menu tree. BMC Remedy AR System allows a maximum of 99 items on any one menu level. You can use multilevel menus to split large menus into multiple smaller and more manageable menus.
An error occurred while the system tried to access a menu definition file on the server. An associated error message contains details. After you fix the problem, the menu is available.
Note: Make sure that the menu definition file (along with all localized versions) is available on the server. Contact your system administrator for more information. See Localizing file menus.
The server is running in a multiple-socket mode, and the socket in use for this client is not the default socket of 390600. All structural changes must be made using the server connected to the default socket. Use routines connected to the default socket, or restart this tool with the RPC socket definition reset to the default value of 390600.
A currency conversion between two different currency types was needed during the execution of workflow, and the conversion ratio does not exist in the BMC Remedy AR System Currency form. Supply conversion ratios in the BMC Remedy AR System Currency form for all possible conversions.
This server is configured not to allow unqualified searches, and you issued an unqualified search. Specify some qualifying criteria in one or more fields to limit the amount of data being returned from the server.
During submission of a new request, a value specifying the keyword
The filter definition contains a Set Fields action where a diary field was assigned a value of
The escalation is not defined on the current server. You attempted an operation against the wrong server, or no escalation is defined by that name. Change to the correct server (if the former), or specify an existing escalation (if the latter).
The name you are specifying for this escalation is already in use by an escalation on this server. Choose a different name for the escalation, or rename the existing escalation.
An error occurred when loading an escalation definition from the database. An internal error occurred, or manual changes were made to the contents of the database.
Only users with administrator permission may access (for read or change) an escalation definition. The current user does not have access to the escalation.
No form ID was found in the file
The system can be configured with a Submitter Mode of Locked or Changeable. You configured the system with a value of Locked. In this mode, the value of the Submitter field cannot be changed after submission (even by the administrator).
The server could not create an alert event request in the database. An associated error message contains details. The following are possible causes:
Only users with administrator privileges can read or change a distributed mapping definition. The current user tried to access a distributed mapping and does not have administrator privileges.
The specified distributed mapping does not exist on the current server. One of these conditions exists:
You cannot assign the same name to more than one distributed mapping. Choose a different name for the mapping, or rename the mapping with which the conflict exists.
In a distributed environment, you can update only one entry (marked as the current master) in a chain. You tried to update a copy other than the master. Perform the update on the current master copy of the entry.
A distributed or application operation activated by a filter action includes one or more arguments with single (') or double quotation marks ("). Somewhere in the command line, a mismatch in the number of quotation marks exists (the number of open and closed single or double quotation marks is not even). The command-line arguments cannot be processed.
The command line in which the mismatch exists is displayed and includes an error message. The distributed or application operation is not performed. Retry the operation, and use the correct command-line syntax.
To run the specified delete operation against the Distributed Pending and Distributed Mapping forms, you must be the Distributed Server user (process). The distributed forms are part of the system structure and must not be deleted or modified. To delete one or both of these forms in BMC Remedy Developer Studio, select the forms for deletion, and ignore the system warning related to the forms.
When a system is licensed for the Distributed Server Option, a pair of forms is automatically created by the server. During the creation of these forms, an error occurred. An associated error message contains details. Fix the problem, and restart the
A filter action was extracting data from another form, or from another table in the database, and found no rows that matched the qualification criteria. The administrator configured the action to return an error if no matches were found.
A filter action tried to extract data from another form, or from another table in the database, and found multiple rows that matched the qualification criteria. The administrator configured the action to return an error if multiple matches were found.
The administrator defined one or more unique indexes on this form. The values on the entry you are submitting or modifying duplicate the field (or fields) defined in the unique index. Review the values for the entry to make sure that values that must be unique are unique.
A maximum size restriction of 1000 menu items is placed on the size of file style menus when accessing the system from a Windows client. Large menus are unwieldy and can hurt performance. If you need a large menu, consider breaking it into smaller pieces and connecting the appropriate menu with the subset you are interested in.
The name contains a control character. Object names can contain only printable characters. Change the name to remove the control characters.
Multiple API calls - those enabling you to perform a set of operations in a single call - do not support specifying the same ID several times in the same call. If you specify two sets of changes or specify to delete the same object several times, confusion about the desired operation can arise.
Reissue the operation without specifying the same ID multiple times.
A "nested filter exception" error is returned because a filter exception condition is already being thrown.
When updating an entry in a join form, an option controls whether a field used in the join qualification can be updated. To maintain data integrity of the record in the join form, this operation is not allowed using the web client. To override this error using the BMC Remedy AR System C API, specify the set option of
The VUI is not related to the specified form. You attempted an operation against the wrong form or server, or the structure of the form was changed to eliminate the VUI ID from the form. Change to the correct form or server or use a VUI ID that is associated with the form to complete the operation.
The VUI is already associated with the form. Both the VUI name and the VUI ID are unique values. One or the other is already in use for this form.
To create a VUI, specify a unique name and ID--or leave the name blank and the ID set to 0 to have the system create a name and ID for you.
Every form must have at least one VUI defined. You are trying to delete the only VUI for the form, and this is not allowed.
A new VUI for the form could not be created. An associated error message contains details.
The system requires that the name for all fields and VUIs on a form be unique. You supplied a name already used by another field or VUI. Change the name of this item, and retry the operation.
Neither the Status History field nor any part of the Status History field can be used in a query style character menu.
BMC Remedy AR System server was temporarily locked for use by users without administrator permissions; for example, because updates are being performed. If you cannot wait to try your operation, consult your BMC Remedy AR System administrator.
An active link specified that a process is to be run on the server to return a value to be assigned to a field. The server timed out waiting for the process to return the requested value. Ask the administrator if the filter process time-out must be raised (up to 20 seconds) or if another change is needed so that the process returns a result in a timely manner.
The support file is not related to the specified object. You attempted an operation against the wrong object or server, or the structure of the form was changed to eliminate the indicated support file ID from the object. Change to the correct object or server or use a support file ID associated with the object to complete the operation.
The Group List field (field 104) is a reserved field with a restriction that the field cannot be more than 4000 characters in length. The definition being saved or imported has an unlimited length. Change the length to be 4000 or fewer characters.
If the server is unable to allocate memory from the shared cache, this message appears, and the server terminates.
The BMC Remedy AR System server detected an active link definition integrity issue. Repair or replace the active link definition.