Error messages 501 to 600
The server could not open the form data dictionary file (
Due to a workflow design error or an AR System internal error, the transaction is not committed. To ensure database integrity, the transaction was rolled back.
File is not allowed to be uploaded.
One of the following messages is displayed:
This error occurs when:
Upload is allowed with warning
Appended Message from Custom Plugin
This error occurs when the custom plugin (AV Plugin) finds some issue in the attached file and returns a cleaned file.
An error occurred when the system tried to open a connection to the SQL database. An accompanying error message provides details. The
This error can have several causes, including:
When ARERR 551 occurs, the database error is usually captured in the BMC Remedy AR System SQL log. To help diagnose the cause of this error, generate client-side ARAPILOGGING (when the error is generated from user interaction) and server API and SQL logging to identify the call that failed and the specific database error message.
A SQL database error occurred during an operation against the database. An associated error message contains the full text of the error message from the database. This error could be caused by a direct SQL command in active link or filter workflow. To identify the database error, turn on SQL and Filter logging on the AR System server. The database error will appear in the SQL log. Also turn on client workflow logging as well as ARAPILOGGING. Use the workflow logging to identify the SQL operation that causes the error, and use the database error from the SQL log to work with the database administrator or database vendor to identify and resolve the database problem.
The operation you attempted generates a SQL command that is too large for the database to process.
If the error occurs during execution of workflow, turn on filter logging and active link logging on the AR System server to identify the workflow involved. In the case the resolution is to modify the workflow to reduce the size of the operation.
If the error occurs when saving a form or other workflow object, the reason for the error might be the size of the CREATE VIEW statement generated when the form is saved. You might need to reduce the number of fields on the form. In this case, the CREATE VIEW statement in the BMC Remedy AR System SQL log might be truncated. To troubleshoot the error in this case, engage database administration support to capture the full CREATE VIEW statement in the database logs and to provide information about database limitations.
This is a serious error. The Control record for the data dictionary in the database is missing or contains no records. This error usually indicates a failed installation or a permissions issue. If the error occurred immediately after an installation, the installation might not have been successfully completed. To identify the cause of the problem, use the installer logs. If the table exists and contains a single valid record, work with the database administrator to determine whether the database has a permissions problem.
This is a serious error. One or more enumerated (selection) values are missing from the data dictionary in the database, or are corrupted. This error is most often generated when the AR System server starts up. To troubleshoot this error, gather and provide the following information and to BMC technical support:
This is a serious error. Data expected to be found in the database cannot be found. This error can be caused by data missing in a table associated with a base data table. It can also be caused when the data dictionary definition of a form or other object is corrupt or inconsistent. When the data is managed through BMC Remedy AR System, all appropriate cross-references are maintained. If you manually updated data in the database, you might have broken a required reference. Manual updates at the database level are not supported and can result in errors during AR Server startup or caching of form and object definitions. To troubleshoot this error, gather and provide the following information to Customer Support:
This is a serious error. More data was found in the database than was expected. This error is usually caused by inconsistent definitions in the data dictionary. When the definitions are managed through BMC Remedy AR System, all data is updated appropriately to avoid extra definitions. If you manually updated the data dictionary definitions, you might have added data that conflicts with existing definitions. To troubleshoot this error, gather and provide the following information and to BMC technical support:
This is a serious error. One of the data dictionary entries defining a form or field is missing. To troubleshoot this error, gather and provide the following information and to BMC technical support:
The total length of a character or diary string exceeds the maximum size of a string allowed in the underlying database (500K characters for Oracle). If the field is a character string, edit the data to less than the maximum allowed. If the field is a diary field, you cannot add data to the field for this request. Each database vendor has its own limitations for field sizes. If you have questions, ask your database administrator.
This is a serious error. More than one action for a filter or active link contains the same internal sequencing number. This number allows ordering of the actions in the proper sequence. If you manually changed the database, undo the change you made to restore the database to a consistent state.
Your SQL database engine does not allow qualifications on diary fields or character fields whose maximum length is greater than 4000 bytes for Oracle or 255 bytes for all other databases. You cannot specify a qualification that includes a reference to these types of fields.
The SQL database engine being used stores Help text and change diary information in separate tables from the structure definition. The Help text or change diary entry for a structure is missing. Even when no Help text or change diary exists, a
The SQL database engine being used does not support the modulo operator. You can use the modulo operator in filter, active link, and escalation qualifications, but you cannot use it to search for entries in the database.
The SQL database engine being used does not support field references in a LIKE operation. You cannot specify a search that includes a field on the right side of a LIKE operator.
A SQL command was issued, and values are being retrieved from the database. A request was made for a value from the command. However, the index of the column requested is greater than the number of columns that were requested. If you are using the SQL option of the Set Fields operation, correct the definition of the SQL command used as the qualification to include sufficient columns, or correct the assignment to include one of the returned values. If you are not using the SQL option of the Set Fields operation, this is an internal error.
A deadlock condition was detected in the database. The operation for which this message was received was canceled. Because the deadlock condition should be trapped and the command automatically retried by the server, you should not receive this error message. If you receive this message, continue by reissuing the command. Record the operation you were performing (and the message received), and contact Customer Support.
The system tried to establish a connection with the database and received errors after multiple attempts.
The database was configured not to supply the number of records affected by a SQL statement. Configure the database to supply this information. For example, on Microsoft SQL Server, the
This is an internal AR System server error that happens while creating a new SQL command from another one. If this error occurs, check the SQL and API logs to help debug the issue.
The SQL database is unavailable. The process periodically retries the connection until a connection is obtained or it encounters a fatal error.
This message periodically appears while the system tries to connect to a SQL database that is not responding. It is preceded by message 590. This message is issued as a reminder that the system is not connected, but that it is continuing to retry the connection.
The previously unavailable SQL database is now available, and a connection was established. This message follows either message 590 or 591.
The system failed to retrieve the list of BMC Remedy AR System servers. This list is retrieved only when you specify an update to all servers. If you start the tool from the command line and you use the command-line option