Error messages 9200 to 9400
Number | Description |
---|---|
9200 Error |
You tried to perform an operation (for example, opening a form) to which you have no permissions. Check with your administrator. |
9201 Error |
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. |
9202 Error |
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. |
9203 Error |
An error occurred in one of the form actions, such as Submit, Search, Modify, or Delete Entry. |
9204 Error |
You tried a display, save, or delete operation but did not first select an attachment. |
9205 Error |
A failure occurred while the system tried to retrieve Help text for this form or field. An associated error message provides details. |
9206 Error |
A failure occurred while retrieving the list of fields that contain Help text. |
9207 Error |
You entered a set of incorrect parameters for this operation, for example, an invalid qualification statement. This is an unexpected error. |
9208 Error |
A failure occurred in retrieving a property from the configuration properties file. |
9209 Error |
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. |
9210 Error |
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. |
9211 Error |
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. |
9212 Error |
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. |
9213 Error |
The attachment file failed to load because the method attribute of the |
9214 Error |
The operation of saving the attachment file to disk failed either because the file does not exist or because its value is |
9215 Error |
This all-purpose error occurs during numerous internal system failures, including the following conditions:
|
9216 Error |
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 |
9217 Error |
An attempt to view or save an attachment file failed because the file could not be found on the web server. Contact your administrator. |
9218 Error |
An attempt to view the file failed because, although the system found the file, it could not be sent. |
9219 Error |
An attempt to delete an attachment file failed because it could not be found on the web server. Make sure the file exists. |
9220 Error |
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. |
9221 Error |
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. |
9222 Error |
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. |
9230 Error |
The native report output failed because the file location was not specified. |
9231 Error |
The native report output failed because of an invalid report definition. To continue, try creating a different definition file or redesigning your report. |
9233 Error |
The native report output failed because the report definition specified no fields. To continue, try creating a different definition file or redesigning your report. |
9234 Error |
The native report failed to appear on your browser for unknown reasons. To continue, see the remainder of the message. |
9235 Error |
An invalid operation was specified for a BMC Remedy AR System report. See your administrator. |
9236 Error |
The native report operation failed to open the report |
9237 Error |
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. |
9238 Error |
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. |
9240 Error |
The location (URL) of the native report cannot be decoded. Contact your AR System administrator. |
9241 Error |
Check the name of the configured report directory and try again. |
9242 Error |
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. |
9243 Error |
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. |
9244 Error |
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. |
9245 Error |
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. |
9246 Error |
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. |
9247 Error |
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. |
9248 Error |
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. |
9249 Error |
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 |
9250 Error |
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. |
9251 Error |
An inappropriate command was issued for the report because of an invalid data type. To continue, check the report type form definition. |
9252 Error |
The report operation command does not have a command specified for this report type. |
9253 Error |
A failure occurred because the BMC Remedy AR System server failed to retrieve the form with the specified ID needed to create the report. |
9254 Error |
Permissions problems occurred when a report directory was created. To continue, verify that the mid tier has write access to this directory. |
9255 Error |
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. |
9256 Error |
An initial failure occurred when the original query string was converted into a |
9257 Error |
An attempt to create the report definition file from the Message Catalog failed. |
9259 Error |
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. |
9261 Error |
The XML string containing the Status History field information was not created. Status history is displayed for the web in a separate window. |
9262 Error |
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.) |
9263 Error |
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. |
9264 Error |
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. |
9265 Error |
You tried to access a field that you have no permissions to. Check your permissions to continue. |
9266 Error |
An attempt to display the status history in a new window failed because no entry was selected. The request was therefore ignored. |
9267 Error |
Creation of the form view failed because the required parameters contain either no value or a
|
9268 Error |
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:
|
9269 Error |
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. |
9270 Error |
The request retrieval failed because the entry ID does not exist in the database. |
9271 Error |
An attempt to validate the values for this field so that it can be properly formatted failed. |
9272 Error |
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. |
9273 Error |
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. |
9275 Error |
An attempt to display the status history failed because it is valid only in modify mode, not for submit or query. |
9276 Error |
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. |
9277 Error |
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 |
9278 Error |
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 |
9280 Error |
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. |
9281 Error |
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. |
9282 Error |
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. |
9283 Error |
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. |
9289 Error |
A failure occurred during login because you entered an invalid server name. |
9290 Error | A failure occurred because the remote server <remoteServer> is not reachable. |
9291 Error |
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. |
9292 Error |
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. |
9294 Error |
You are running out of available memory because the query returned too many results. To continue, rewrite your query to return fewer requests. |
9295 Error |
A login failure occurred because you did not enter certain parameters, for example, form name or user name. To continue, enter the missing parameters. |
9296 Error |
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. |
9298 Error |
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. |
9299 Warning |
A conflict exists because another user and you are retrieving the same request. To continue, perform one of the following tasks:
|
9300 Error |
The Run Process active link action failed because this Run Process command is not supported. To continue, use a different Run Process command. |
9301 Error |
The report file cannot be retrieved from the server to the mid tier server. |
9302 Error |
This generic message indicates an error occurred. |
9303 Error |
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. |
9304 Error |
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. |
9305 Warning |
The qualification failed because the system was unsuccessful in translating the group names into group IDs. |
9306 Error |
The qualification failed because of an illegal mathematical operation. A |
9307 Error |
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. |
9308 Error |
Your form is outdated. The form was recently updated in memory. To continue, click the Refresh button on the page. |
9309 Error |
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. |
9310 Error |
You entered the wrong time format into the Calendar popup window. |
9325 Error |
You did not enter a valid currency value on a currency field. For example, you entered 1,00 USD. |
9326 Error |
The specified currency value is a not an allowable currency type. Contact your BMC Remedy AR System administrator. |
9327 Error |
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. |
9329 Error |
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. |
9330 Error |
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. |
9331 Error |
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. |
9332 Error |
The mid tier could not make the necessary API call because an invalid operation type was specified for the web service. |
9334 Error |
A string value could not be substituted for the XPATH expression because the mid tier server could not find the corresponding mapping node. |
9335 Error |
The mid tier could not parse the XML date/time string. |
9336 Error |
The WSDLServlet servlet could not generate the WSDL for a requested web service because the URL was invalid. |
9337 Error |
A web service was requested, but the mid tier could not locate the web service definition. |
9338 Error |
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. |
9339 Error |
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). |
9341 Error |
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. |
9342 Error |
No BMC Remedy AR System servers are configured in the BMC Remedy Mid Tier Configuration Tool. Contact your BMC Remedy AR System administrator. |
9343 Error |
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. |
9344 Error |
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. |
9345 Error |
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. |
9350 Error |
An internal error occurred because parameters passed to the back channel were incorrect. |
9351 Error |
An internal error occurred during a back channel request from the browser to the mid tier server. |
9352 Error |
The definition of a form that users have loaded was changed in such a way that a table on the form cannot be refreshed. |
9353 Error |
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. |
9354 Error |
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. |
9355 Error |
The form specified in the URL does not exist. |
9356 Error |
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. |
9357 Error |
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. |
9358 Error |
The application specified in the URL does not exist. |
9359 Error |
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. |
9360 Error |
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. |
9361 Error |
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. |
9362 Error |
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. |
9363 Error |
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. |
9364 Error |
Used by the Push Fields action when the administrator configures it to return an error when multiple matches are found. On the If Action page, the If Any Requests Match field has |
9365 Error |
The modify all action requires that at least one row is selected in the results list. Select one or more entries in the results list and try again. |
9366 Error |
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. |
9367 Error |
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. |
9368 Error |
An BMC Remedy AR System API function call was used with an invalid data type. |
9369 Error |
BMC Remedy AR System functions (used in assignments) such as |
9370 Error |
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. |
9371 Error |
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. |
9372 Error |
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. |
9373 Error |
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. |
9374 Error |
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. |
9375 Error |
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. |
9376 Error |
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. |
9377 Error |
BMC Remedy AR System cannot process a time that is out of range. Try again, using a time within the allowed range. |
9378 Warning |
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. |
9379 Warning |
Click the icon to the right of the field to select the desired time. |
9380 Warning |
Click the icon to the right of the field to select the desired date. |
9381 Error |
A user with the supplied login ID cannot be found on any AR System server. |
9382 Error |
The supplied password is invalid. |
9383 Error | No forms found containing field ID: <IDNumber>. |
9384 Error | Multiple forms contain field ID: IDNumber. |
9385 Error | Unable to contact the web server to the complete action. |
9388 Error |
An authentication failure occurred, such as supplying the wrong administrator password on the configuration page for the AR System server. |
9389 Error |
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. |
9390 Error |
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. |
9391 Error |
The requested plug-in does not exist in the list of plug-in servers in the BMC Remedy Mid Tier Configuration Tool. |
9392 Error |
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. |
9393 Error |
The plug-in JAR file is missing for a given data visualization module in the Data Visualization Module form. |
9394 Error |
The mid tier cannot download a JAR file for a particular data visualization plug-in in a server. |
9395 Error |
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. |
9396 Error |
The available local plug-ins directory should have a |
9397 Error |
A JAR file is missing in the local plug-ins directory. |
9398 Error |
The entry class specified for the module does not implement the plug-in interface provided in the |
9399 Error |
The entry class specified for a module was not implemented. |
9400 Error |
The plug-in container in the mid tier cannot instantiate the specified entry class for a module. |
Comments