Error messages 9200 to 9400
You tried to perform an operation (for example, opening a form) to which you have no permissions. Check with your administrator.
Your session is no longer available because either the session is invalid, the session timed-out, or no session data was retrieved. Log in again to continue.
You tried to attach an object to an attachment pool in which no fields are available (all fields might be in use). Remove any unnecessary attachments if you have permissions, or ask your BMC Remedy AR System administrator to add more attachment fields to the attachment pool.
An error occurred in one of the form actions, such as Submit, Search, Modify, or Delete Entry.
You tried a display, save, or delete operation but did not first select an attachment.
A failure occurred while the system tried to retrieve Help text for this form or field. An associated error message provides details.
A failure occurred while retrieving the list of fields that contain Help text.
You entered a set of incorrect parameters for this operation, for example, an invalid qualification statement. This is an unexpected error.
A failure occurred in retrieving a property from the configuration properties file.
No field in the attachment pool is large enough to contain this particular file. Contact your administrator to enlarge the size of the attachment field so that you can attach it later, or try zipping the file to make it smaller.
You tried to attach a file larger than the maximum size allowed for this attachment field. Contact your administrator to enlarge the size of the attachment field so that you can attach it later, or try zipping the file to make it smaller. You can also try to attach to a different attachment field.
You tried to attach a file to an attachment field but did not enter a file name. To complete this process, enter or select a file.
The operation of adding an attachment file failed. Check your permissions. If that does not solve your problem, contact your BMC Remedy AR System administrator.
The attachment file failed to load because the method attribute of the
The operation of saving the attachment file to disk failed either because the file does not exist or because its value is
This all-purpose error occurs during numerous internal system failures, including the following conditions:
An attempt to view or save an attachment file failed, for example, a new window could not be opened to display the file. This error occurred because the request parameters for the file were invalid, because the file path was
An attempt to view or save an attachment file failed because the file could not be found on the web server. Contact your administrator.
An attempt to view the file failed because, although the system found the file, it could not be sent.
An attempt to delete an attachment file failed because it could not be found on the web server. Make sure the file exists.
An attempt to display the attachment file in a new window failed because it could not be found on the web server. Make sure the file exists.
An attempt to save the attachment file to the client's local file system failed because it could not be found on the web server. Make sure the file exists.
An attempt to download the attachment file failed because it could not be found on either the web server or the BMC Remedy AR System server. Make sure the file exists.
The native report output failed because the file location was not specified.
The native report output failed because of an invalid report definition. To continue, try creating a different definition file or redesigning your report.
The native report output failed because the report definition specified no fields. To continue, try creating a different definition file or redesigning your report.
The native report failed to appear on your browser for unknown reasons. To continue, see the remainder of the message.
An invalid operation was specified for a BMC Remedy AR System report. See your administrator.
The native report operation failed to open the report
The report operation could not parse the field attributes in the definition file. To continue, try creating a different definition file or redesigning your report.
The report operation could not parse the field IDs and sort order. The report consists of a string that cannot be understood by the system. To continue, try creating a different definition file or redesigning your report.
The location (URL) of the native report cannot be decoded. Contact your AR System administrator.
Check the name of the configured report directory and try again.
An attempt to extract the report failed because of an invalid data type for the attachment field. Ask your administrator to check the report form definition.
The report was not extracted because information about the attachment field could not be retrieved. To continue, check that the report's entry in the report form has a valid attachment.
The report was not extracted because the file name of the report could not be retrieved. To continue, check that the report's entry in the report form has a valid attachment.
The report definition file was not extracted because no session-specific report directory could be retrieved from the configuration. To continue, use the BMC Remedy Mid Tier Configuration Tool to specify a report directory.
The report was not retrieved when the Report form was queried for the entry that matches the parameters in the request. To continue, check the report and report type forms on the server for valid report names and types.
The report type was not retrieved when the Report form was queried for the entry that matches the parameters in the request. To continue, check the report and report type forms on the server for valid report names and types.
An invalid data type was applied to the query class field when the query string was converted from the BMC Remedy AR System native format into the report engine's format.
The query converter class was not loaded when the query string was converted from the BMC Remedy AR System native format into the report engine's format. To continue, verify that the query converter class is installed in your
During report creation in the Open Window action, an invalid operation was used to post the report. The only valid operations are run, create, or edit. To continue, fix the action to use a valid operation.
An inappropriate command was issued for the report because of an invalid data type. To continue, check the report type form definition.
The report operation command does not have a command specified for this report type.
A failure occurred because the BMC Remedy AR System server failed to retrieve the form with the specified ID needed to create the report.
Permissions problems occurred when a report directory was created. To continue, verify that the mid tier has write access to this directory.
An instance of the query convertor class was not created when the query string was converted from the BMC Remedy AR System native format into the report engine's format. To continue, verify that the query converter class implements the report query converter interface.
An initial failure occurred when the original query string was converted into a
An attempt to create the report definition file from the Message Catalog failed.
This object (for example, a schema, active link, or container) was not in the server cache. To continue, verify that the object exists on BMC Remedy AR System server.
The XML string containing the Status History field information was not created. Status history is displayed for the web in a separate window.
The Submit operation failed while a request was being created. A Submit failure has many possible causes, for example, a required field is blank. (In that case, enter a value for the required field, and retry the Submit operation.)
The Modify operation failed when updating an BMC Remedy AR System request. Possible causes for this error include, for example, a simultaneous modification by another user or a failure in workflow.
You entered an incorrect user name or tried to access an BMC Remedy AR System form that you have no permissions to. Try reentering your user name, or check your permissions to continue.
You tried to access a field that you have no permissions to. Check your permissions to continue.
An attempt to display the status history in a new window failed because no entry was selected. The request was therefore ignored.
Creation of the form view failed because the required parameters contain either no value or a
An attempt to retrieve the path of the JSP™ page that represents the form failed. The JSP path could not be constructed because some of the following data is missing:
The query failed because the results list in the form could not be found. This error message also appears when you are unable to use an Open Window active link action to "drill down" to a record in a table field.
The request retrieval failed because the entry ID does not exist in the database.
An attempt to validate the values for this field so that it can be properly formatted failed.
An attempt to validate the values for this field failed because they are out of the acceptable minimum and maximum range limits defined by the administrator.
An attempt to add the field to the query bar HTML input element failed because it is a display-only field. Only fields holding actual database values, such as an integer field, are included.
An attempt to display the status history failed because it is valid only in modify mode, not for submit or query.
You tried to drill down on a table or to display, by using an Open Window action, a form that does not have a web view defined. This could be a form on a 5.x or later environment in which no web view was defined or a form on a pre-5.x BMC Remedy AR System server. The system cannot open a form that does not have a valid web view on the web. If the server is a 5.x or later server, add a web view for the form, and you can then open it. If the server is pre-5.x, upgrade the server to 5. x or later and then create a web view for the form before you can open it.
A failure occurred because multiple matches were found in the form during a Set Fields or Push Fields action. All workflow processing is stopped. To continue, configure the workflow in BMC Remedy Developer Studio for a different multiple match response in BMC Remedy AR System, for example, Set Field to
A failure occurred because no matches were found in the form during a Set Fields or Push Fields action. All workflow processing is stopped. To continue, configure the workflow in BMC Remedy Developer Studio for a different multiple match response in BMC Remedy AR System, for example, Set Field to
A failure occurred because the name of the server is not in the list of valid mid tier servers. To continue, verify that a valid server exists.
A failure occurred in the process used by the Set Fields action. No results were returned. To continue, verify that the process works independently of the Set Fields action.
An attempt to expand the query string for a dynamic menu, such as a search menu, failed. The server could not parse the query correctly.
An internal system failure occurred during the execution of this active link. This error is not due, however, to a more common multiple match or no match error.
A failure occurred during login because you entered an invalid server name.
The mid tier administrator password you specified is not recognized. To continue, try re-entering your password or contact your BMC Remedy AR System administrator for assistance.
A failure occurred during login because the system does not recognize this user name as a valid administrator. To continue, enter a different login name.
You are running out of available memory because the query returned too many results. To continue, rewrite your query to return fewer requests.
A login failure occurred because you did not enter certain parameters, for example, form name or user name. To continue, enter the missing parameters.
No matches were found for your qualification. However, processing continues to display the zero matches label in the results list header. To continue, refine the qualification to make sure that it returns at least one matching request.
The BMC Remedy AR System query format failed to convert into the report engine's format because the converted query was too complex. The converted query is replaced by the original BMC Remedy AR System query string.
A conflict exists because another user and you are retrieving the same request. To continue, perform one of the following tasks:
The Run Process active link action failed because this Run Process command is not supported. To continue, use a different Run Process command.
The report file cannot be retrieved from the server to the mid tier server.
This generic message indicates an error occurred.
An attempt to retrieve a user from the pool of available users failed because a user pool does not work with this version of BMC Remedy AR System.
An attempt to retrieve the report file failed because the ReportServlet used by the Open Window active link action could not create a temporary directory in which to hold the report or extract the report to the directory.
The qualification failed because the system was unsuccessful in translating the group names into group IDs.
The qualification failed because of an illegal mathematical operation. A
You entered a value for a date/time field that does not fall in the supported range. To continue, enter a date in the range between 1970 to 2037.
Your form is outdated. The form was recently updated in memory. To continue, click the Refresh button on the page.
The status history failed to appear in a new window because the Status History field is missing from the form. The request to display the status history is ignored.
You entered the wrong time format into the Calendar popup window.
You did not enter a valid currency value on a currency field. For example, you entered 1,00 USD.
The specified currency value is a not an allowable currency type. Contact your BMC Remedy AR System administrator.
You did not enter an allowable currency code on a currency field. The mid tier returns the field results based on the last previous valid currency code.
When details about the web service request were extracted from the input document, this error message was returned because the namespace was incorrectly formatted. The location must include the server and the web service parameters.
When a web service request was processed on the mid tier, this error message was returned because no such web service exists on the server.
When a web service request was processed on the mid tier, this error message was returned because no such operation was found in the web service.
The mid tier could not make the necessary API call because an invalid operation type was specified for the web service.
A string value could not be substituted for the XPATH expression because the mid tier server could not find the corresponding mapping node.
The mid tier could not parse the XML date/time string.
The WSDLServlet servlet could not generate the WSDL for a requested web service because the URL was invalid.
A web service was requested, but the mid tier could not locate the web service definition.
Authentication information is not supplied in the web service request, and anonymous user information is not specified in the BMC Remedy Mid Tier Configuration Tool.
In an active link arithmetic operation, the two operands cannot be made to match, or the arithmetic operation is not supported. For example, you tried to add two currency fields that have different currency codes, such as USD and CAD, and no matching functional currencies exist. Or you subtract Decimal1 - Decimal2 = Character. If the target field is a character, only addition is supported (string concatenation).
The AR Server field on the Home Page tab of the BMC Remedy AR System User Preference form and the Server Name field on the Home Page Settings page of the BMC Remedy Mid Tier Configuration Tool are blank. Specify a server in the BMC Remedy Mid Tier Configuration Tool or specify a server for this user in the BMC Remedy AR System User Preference form.
No BMC Remedy AR System servers are configured in the BMC Remedy Mid Tier Configuration Tool. Contact your BMC Remedy AR System administrator.
The Form Name field on the Home Page tab of the BMC Remedy AR System User Preference form and the Default Home Form field on the Configuration tab of the Server Information dialog box are blank. Specify a default home page form in the Server Information dialog box or specify a home page form for this user in the BMC Remedy AR System User Preference form.
Unable to connect to the server that contains the Home Page form. This can occur when the server is down or when the network is too slow (leading to a time-out). Contact your BMC Remedy AR System administrator.
Your user name or password was not accepted by any BMC Remedy AR System server configured in the BMC Remedy Mid Tier Configuration Tool. Contact your BMC Remedy AR System administrator.
An internal error occurred because parameters passed to the back channel were incorrect.
An internal error occurred during a back channel request from the browser to the mid tier server.
The definition of a form that users have loaded was changed in such a way that a table on the form cannot be refreshed.
A user who is logging out tried to make requests to the mid tier. This can occur if a user opened multiple windows and is trying to do something in one window at almost the same time as logging out in another window.
The mid tier could not find a view to display for the specified form. This can occur if a form contains only relative views because relative views are no longer supported by the mid tier.
The form specified in the URL does not exist.
A user tried to load a form on the mid tier in an unsupported locale. The locale is specified either in the languages selection in the browser or in the user preferences. For information about supported locales, see Localizing the mid tier.
A user tried to load a form on the mid tier in an unsupported time zone. The time zone is determined at login time or from the user preferences.
The application specified in the URL does not exist.
The view form servlet requires the server and form parameters to be in the URL (other parameters are optional). If these parameters are missing this error occurs.
The mid tier implementation of global fields limits the amount of data that can be stored in all global fields to about 3.5 KB. To allow more storage, install a supported version of Flash Player.
Log off the existing session and try again. The view form servlet was used with user name and password parameters that differ from the ones used to create the current session.
Aliases are not supported by the BMC Remedy AR System 6.3 and later mid tier so the alias parameters to the view form servlet are no longer supported.
The action failed because the mid tier is unavailable or could not be contacted. This error could also occur if the action was canceled by the user while it was being performed.
Used by the Push Fields action when the administrator configures it to return an error when multiple matches are found. On the If Action page, the If Any Requests Match field has
The modify all action requires that at least one row is selected in the results list. Select one or more entries in the results list and try again.
The Run Process active link action failed because this Run Process command was used incorrectly, such as using a Run Process command that does not return a value in a Set Fields action.
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 Operator types.
An BMC Remedy AR System API function call was used with an invalid data type.
BMC Remedy AR System functions (used in assignments) such as
The guide or the primary form for the guide could not be determined. Dynamic workflow allows an active link guide to be named at run time. If the guide name does not exist on the server, or the guide does not have a primary form, this error is generated.
The guide specified (via dynamic workflow) is invalid. With dynamic workflow you can specify guide names from workflow instead of in BMC Remedy Developer Studio. The definition for the guide specified cannot be found and might be missing from the BMC Remedy AR System server.
The specified menu is invalid. This error occurs if the browser client requests a nonexistent menu. This could be due to an active link change fields action that changed the menu for a character field.
The indicated value was entered as a value for a field with a data type of real. The value is not a legal real value. Change the value to a legal real value, and retry the operation.
The value was entered in a field with a data type of decimal. The value is not a legal decimal value. Change the value to a legal decimal value, and retry the operation.
A numeric field contains a nondigit value. You can specify digits only for integer (numeric) fields. Change the value to a legal integer value, and retry the operation.
The format of a time value is not recognized. You can omit the time portion of a time stamp and include only the date, or you can omit the date and include only the time. The portion omitted defaults to an appropriate value. However, the format of the specified portion of time must match the rules for time stamps. Fix the format of the line, and perform the search again.
BMC Remedy AR System cannot process a time that is out of range. Try again, using a time within the allowed range.
The retrieval included a search that selected more than the maximum number of items allowed by the client or server. The call returned the number of entries specified as the maximum. Narrow your search criteria or change the limit in user preferences. Use the local setting using the BMC Remedy AR System User Preference form and modify the settings for Limit Number of Items Returned. Only an administrator can change the server settings.
Click the icon to the right of the field to select the desired time.
Click the icon to the right of the field to select the desired date.
A user with the supplied login ID cannot be found on any AR System server.
The supplied password is invalid.
An authentication failure occurred, such as supplying the wrong administrator password on the configuration page for the AR System server.
The length of server name or form name passed to the viewformservlet is longer than the allowed length. The maximum server name length is 64 characters and maximum form name length is 254 characters.
The requested plug-in definition does not exist in the Data Visualization Definition form, or the user does not have correct permissions to access that data.
The requested plug-in does not exist in the list of plug-in servers in the BMC Remedy Mid Tier Configuration Tool.
The mid tier should be able to create a directory so that it can download the plug-in information. If it cannot create a directory, this error occurs.
The plug-in JAR file is missing for a given data visualization module in the Data Visualization Module form.
The mid tier cannot download a JAR file for a particular data visualization plug-in in a server.
Flashboards and reports are built on mid-tier local data visualization modules. This error occurs if a request is made for these modules and they are unavailable in the local plug-ins directory.
The available local plug-ins directory should have a
A JAR file is missing in the local plug-ins directory.
The entry class specified for the module does not implement the plug-in interface provided in the
The entry class specified for a module was not implemented.
The plug-in container in the mid tier cannot instantiate the specified entry class for a module.