This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Error messages 501 to 600

Number Description
504 Error

Missing or invalid form definition file.

The server could not open the form data dictionary file (form.ar. This file is in the database directory referenced by the Server-directory setting in the ar.conf file (UNIX) or the ar.cfg file (Windows). Make sure that the directory setting is correct. If it is correct, look in that directory for the definition file. An associated error message explains why the file was not opened. If the file is not present, restore the file from a backup. Verify the permissions on the file to make sure that the user running the arserverd process has read and write access. Update ownership or permissions as needed.

524 Error

This operation encountered an error and the transaction has been rolled back.

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.

525 Error
File is not allowed to be uploaded.

One of the following messages is displayed:

  • Extension ext is not allowed
  • Files without extensions are not allowed
  • Appended Message from Custom Plugin

This error occurs when:

  • A particular file extension is not allowed as an attachment
  • A file is not allowed by the custom plugin since it is a virus-infected file
526 Error
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.

550 Error

Unable to connect to the SQL database. Please ensure the SQL database is running or contact the Database Administrator for help.

An error occurred when the system tried to open a connection to the SQL database. An accompanying error message provides details. The ar.conf file (UNIX) or the ar.cfg file (Windows) file contains definitions for the environment variables to set for each database. The value for Dbhome-directory, applicable only to UNIX, is the directory of the database server or client installation on the UNIX computer where BMC Remedy AR System is installed. The names of other needed settings begin with the name of the database (for example, Sybase-Server-Name or Oracle-SID ). Make sure that these values are correct. If you moved your database or changed these parameters, update the requests in this file and then restart the arserverd process.

551 Error

Unable to connect to the SQL database.

This error can have several causes, including:

  • During server start-up, the database was not accessible. Verify that the database is running and is accessible to the AR System server.
  • During operation, this error can occur if AR System needs to contact an external database that is not accessible, for example, when opening a view of an external table.

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.

552 Error

The SQL database operation failed.

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.

553 Error

Operation requested is too large for a single SQL command.

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.

554 Error

The Control record for the data dictionary in the database is missing.

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.

555 Error

One or more selection values are missing from the data dictionary in the database.

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:

  • The arerror.log file.
  • In release 7.5 and later, if the error occurs during server startup, use the database consistency checker (the -dbcheck server option) and capture the output to a log file. For more information, see Running the database consistency checker.
  • On UNIX, also capture the UNIX console output during startup when the error is generated.
556 Error

Missing data in the SQL database.

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:

  • The arerror.log file.
  • The API and SQL logs, which help identify which forms or tables were involved.
  • (Release 7.5.00 and later) If the error occurs during server startup, use the database consistency checker (-checkdb server option) and capture the output to a log file. See Running the database consistency checker.
  • (UNIX) The UNIX console output during startup when the error is generated.
557 Error

More data was found in the database than was expected.

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:

  • The arerror.log file.
  • The API log and the SQL log. These will help identify which forms or tables were involved.
  • In release 7.5 and later, if the error occurs during server startup, use the database consistency checker and capture the output to a log file. For more information, see Running the database consistency checker.
  • On UNIX, also capture the UNIX console output during startup when the error is generated.
558 Error

Form or field definition is missing.

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 arerror.log file.
  • In release 7.5 and later, if the error occurs during server startup, use the database consistency checker and capture the output to a log file. For more information, see Running the database consistency checker.
  • On UNIX, also capture the UNIX console output during startup when the error is generated.
559 Error

Character string exceeds maximum size allowed.

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.

560 Error

Multiple actions have the same internal index (likely data corruption).

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.

561 Error

The underlying database does not support qualifications on fields with a length over 4000 bytes for Oracle or 255 bytes for all other databases.

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.

562 Error

Help text or change diary definition is missing.

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 NULL entry is in these tables. If you manually changed the database, undo the change you made to restore the database to a consistent state.

563 Error

% cannot be used to search for entries in SQL database.

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.

564 Error

Field references on the right side of the LIKE operation is not supported by SQL 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.

565 Error

The requested value is beyond the number of values returned.

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.

566 Error

Requested record is locked by another user. Please retry.

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.

567 Error

Failed to connect to database after multiple attempts.

The system tried to establish a connection with the database and received errors after multiple attempts.

569 Error

The number of database records affected by a SQL statement was not available from the database.

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 No count connection option cannot be selected.

570 Error

Incorrect format in the SQL command.

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.

590 Note

SQL database is not available — will retry connection.

The SQL database is unavailable. The process periodically retries the connection until a connection is obtained or it encounters a fatal error.

591 Note

SQL database is still not available — continuing to attempt connection.

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.

592 Note

SQL database is now available.

The previously unavailable SQL database is now available, and a connection was established. This message follows either message 590 or 591.

600 Error

Error while opening/reading from BMC Remedy AR System directory file.

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 -s to specify an update to a single server, this error cannot occur because no server list is accessed.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Rafael Espindola

    Reading the description of "556 Error" says:

    • (Release 7.5.00 and later) If the error occurs during server startup, use the database consistency checker (-dbcheck server option) and capture the output to a log file. See Running the database consistency checker.

     

    But checking the referred link it says:

    The database consistency checker uses the -checkdb start up option for arserver.exe (Windows) and arserverd (UNIX).

     

    The right option is the second one. Or am I wrong?

     

    Jun 15, 2016 09:32
    1. Anagha Deshpande

      Hello Rafael,

      I will confirm this with SME and will write back to you.

       

      Regards,

      Anagha 

      Jun 16, 2016 02:30
      1. Anagha Deshpande

        Hello Rafael,

        The database consistency checker uses the -checkdb startup option for arserver.exe (Microsoft Windows) .

        I have corrected the topic.

        Regards,
        Anagha

        Jun 27, 2016 02:19