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 1 to 99

Number Description
1 Error

Message not in catalog — message number = <messageNumber>.

Text corresponding to that message number was not found. The BMC Remedy AR System server cannot find the message catalog file, which is arsystem.cat on UNIX and is arcatalog<language>.dll on Windows. The most common cause of this error is that the path to the message catalog file is not correctly defined.
To resolve this problem:

  • For UNIX, see Message catalogs in UNIX and follow the recommended steps to configure the NLSPATH.
  • On Windows, the message catalog .dll file is installed in the same directory as the AR System server. Make sure the <ARSystemInstallDir> is included in the PATH environment variable.

Note

If you get the text for other message numbers but not the one causing this error, then the message catalog is accessible but does not include this error. In this case, check this document for the message number and information. If the message number is not in this document, contact Customer Support, and provide the message number and the circumstances that prompted the message.

20 Note

BMC Remedy AR System server terminated when a signal/exception was received by the server.

The error message includes the signal that was received.
(For UNIX) If the signal is 15, the BMC Remedy AR System process was stopped due to a normal shut down command. This signal indicates that the process terminated from a command to do so. If the signal is not 15, AR System server terminated due to a system error.
If the shutdown signal is anything other than normal shutdown, the AR System server has failed and the incident will generate stack output to the arerror.log file. To help resolve this problem, contact BMC Remedy Support and provide the following information:

  • The arerror.log file that includes the time of the crash.
  • The armonitor.log file that includes the time of the crash. If other AR System processes failed abnormally due to a shutdown of AR System server, or to a server crash, the armonitor.log file will provide information about other processes that failed.

Note

Only those processes that are started with the AR System server by means of an entry in the armonitor.conf file are included in armonitor.log output.

  • Any other AR System logs that cover the time of the crash.
  • The current version and patch level of the AR System server. The first step in troubleshooting a crash of the AR System server is often to upgrade to the latest patch release of a current version.
21 Note

BMC Remedy AR System server terminated — fatal error occurred in ARSERVER.

A fatal error occurred in the arserverd process. Details about the error are in an associated message. This generic message indicates that the error was fatal, and the process is shutting down.

22 Error

Failure during open/write to the filter/escalation log file, logging to the log file is suspended.

A file system error occurred while BMC Remedy AR System was running a filter or escalation that logs information to a file (using the Log to File action). An associated message detailing the reason for the failure appears with this message. Processing continues, but logging to the log file is suspended until the problem is corrected (see error message 23).

23 Note

Open/write to the filter/escalation log file resumed successfully.

A failure was reported on an open or write action to the log file identified by Error 22. Additional actions occurred to access this file, and the file is now accessible and can be written to. Any operations between the message indicating a write failure (Error 22) and this message are not included in the log file.

24 Error

Failure while trying to run the filter/escalation process.

An error occurred while BMC Remedy AR System was executing a filter or escalation that runs a process. An associated message provides details. Verify that the process definition is correct. If necessary, correct the process definition in the filter or escalation.

25 Error

Fields in 'set fields' action do not exist in the target form.

The filter or escalation being executed is trying to set values in fields that do not exist in the target form. Fix the definition. Specify values only for fields that exist in the target form. A common cause for this error is a filter or escalation that tries to assign a value to a field that formerly existed on the form but was deleted after the definition was created.

26 Error

Administrator operations are disabled on this server.

The BMC Remedy AR System server is configured to disallow administrator operations. If the server is part of a group of servers sharing the same database, perform the server operations on the server in the group that allows administrator operations.

27 Note

This COPY of the Action Request System(R) does not have its authorization key set, but is ready for use or evaluation. For unlimited capabilities, contact your sales representative.

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.

28 Error

The demo license for this AR Server has expired. Please contact your distributor for license information.

The demo license for the system on which you are trying to run the BMC Remedy AR System server expired. The system is now running in an unlicensed mode (see error message 27). You must obtain a license to run BMC Remedy AR System server in any mode other than evaluation mode.

29 Note

The AR Server license is a Demo license that expires <expirationDate>.

You are operating with a demo license, which expires on the specified date. Contact your distributor for information about upgrading your license.

31 Note

The new user was issued a fixed license of the following type: <licenseType>.

You created a new user who is assigned a fixed license. A user was successfully created. The message shows the current number of users who have a fixed license and the total number of users allowed. The <licenseType> is replaced by write, full text, or flashboards to indicate the type of fixed license.

32 Note

BMC Remedy AR System server terminated normally.

Server shut down without problems.

33 Error

AR System failed to start a process.

Make sure that your system is not low on resources. BMC Remedy AR System failed to start a process. Make sure that your system has no resource problems that prevent new processes from starting.

34 Error

Error while opening the BMC Remedy AR System server lock file.

BMC Remedy AR System server (arserverd, arservdsd, or arservftd) opens a lock file named ar.lck at start-up, and ar.lck. <rpcNum> (ar.lck.390601 for arservdsd and ar.lck.390602 for arservftd ) for servers on alternate RPC sockets. These files are used to prevent multiple copies of the BMC Remedy AR System processes from being started on a single RPC socket simultaneously. An associated file system error message supplies more details. Fix the problem, and rerun the server.

35 Error

Another copy of the server is already running on the same RPC socket.

Only one instance of BMC Remedy AR System server can be run (on a specific RPC socket) on a computer at a time. If a server is already running in this RPC socket, no action is required. If the server is not running, you probably encountered a known problem with the NFS lock manager on Oracle workstations. At times, the lock manager keeps a lock active even when the process holding the lock is no longer running. If no arserverd process is running, free the lock by deleting the lock file. Start the arserverd process after removing this file.

36 Error

The database is not the expected version (may need to run upgrade program).

BMC Remedy AR System server (arserverd ) expects a different version of the BMC Remedy AR System database from the version being referenced. BMC Remedy AR System server cannot run against an unknown version of BMC Remedy AR System database.

37 Error

Error while accessing one of the debug trace files. Debug tracing to the file is disabled.

The system debugging mode was activated, and the system cannot access one of the debugging trace flags. The associated message provides details. To correct the problem, see the message. The system continues to run, but debug tracing to the file is disabled.

38 Error

Filter/escalation 'set field' process returned an error. The current transaction is rejected. No update to the database occurred.

A filter or escalation was performing a Set Fields action using the option to run a process and return a value, but the process returned an error message. The text of the message returned appears with this error. The error terminates the operation being performed, and the current transaction is rejected. No update to the database occurs.

39 Error

Filter/escalation 'set field' process timed out before completion.

A filter or escalation was performing a Set Fields action using the option to run a process and return a value, but the process was not completed within the time-out interval specified for filter processes. The administrator has control over the timeout setting for the process. It can be configured, in BMC Remedy Developer Studio, to be from one to 20 seconds with a default of five seconds.

41 Warning

Unrecognized command line argument — ignoring command line and continuing.

The command-line argument displayed on the following line is not a legal command-line argument for BMC Remedy AR System server. The command-line argument is ignored and processing continues.

42 Warning

Server not licensed to run with multiple-RPC sockets — ignoring setting and continuing.

The server is configured to run multiple queues, but you do not have a multiple server license. The RPC socket setting is being ignored, and processing continues.

43 Error

Unable to retrieve the menu for character field "field name".

A $MENU$ pattern is specified for a field with a character menu, and the server is encountering an error while building the menu to verify the value against. The error can be due to one of the following reasons:

  • The menu is built from a search against a form on a different server. The server restricts access locally to the same server process for performance and consistency reasons. You cannot use a $MENU$ pattern verification for a remote search.
  • The menu is built from a search against a local form, but the search is encountering an error during retrieval.
  • The menu is built from a file, and the file cannot be found.
  • The menu is built using a direct SQL command against another server. The server restricts access locally to the same server process for performance and consistency reasons. You cannot use a $MENU$ pattern verification for a remote SQL command.
  • The menu is built using direct SQL against a local database, but the command is encountering an error during retrieval.
44 Error

You have exceeded the maximum number of forms allowed under the current server license.

The BMC Remedy AR System server you are running against has a limited license. You are allowed to create only a specified number of forms, and you are at that limit. Remove one or more of the existing forms before you create a form.

46 Error

Message action and Log action in else branch are not supported for escalations.

You created an escalation and specified one or more message type actions or one or more log actions in the else branch. Escalations do not have a message type action and do not support log or set field in the else branch. Change the definition to eliminate the message type actions, and use log actions in the action list only.

47 Warning

Email notification operation timed out before completion.

The system was blocked while trying to send a notification through email. To prevent the arserverd process from hanging while waiting for the mail system, the process waits for 20 seconds. If arserverd receives no response, the process disconnects from the mail system and issues this error.
The mail will probably be delivered when the mail system recovers.

48 Error

Insufficient space for the response to be returned (minimum of 4,096 bytes).

An internal RPC failure occurred. A client is accessing the server and has specified insufficient space for the response to be returned.

49 Error

Internal error: The request ID is invalid.

An internal RPC failure occurred. A client is accessing the server and has specified an invalid identifier for the requested information.

50 Warning

You have no permission to this field.

The field is accessible only to administrators. No permission settings were specified to allow access to other users. This is expected if you are restricting access to the field. However, if you want other users to access and manipulate this field, you must assign permissions to the field.

51 Warning

Field ID specified does not exist in this form.

A retrieval operation was attempted for the field identified by the indicated ID, but the target form has no field with that ID. The data for the correctly identified fields was retrieved.

52 Warning

The field is a core system field and cannot be changed.

You tried to modify the contents of a core system field (Request ID, Create Date, Last Modified By, Last Modified Date, or Status History). These fields are managed by BMC Remedy AR System and cannot be changed.

53 Warning

Administrator access required to get permission information.

You requested permission information about a field. Only a user with administrator access can retrieve permission information. No permission information is returned, but all other requested information is retrieved.

54 Warning

No changes have been specified for the update operation.

You specified a Modify operation to the system, but no modifications were specified. If the command is being executed programmatically and set operations with no changes might be specified, this warning can be trapped and ignored in your program.

55 Warning

The following item was not imported: <item>.

You tried to import one or more items (forms, filters, active links, escalations, or character menus) to the current server. The listed item was not successfully imported. An associated message indicates why the item was not imported. Fix the problem, and try to re-import the item.

56 Warning

Entry does not exist on form.

You tried to retrieve a request that does not exist. If this message is received when retrieving an item that was reported in a preceding retrieval, the item might have been deleted by another user.

57 Warning

One or more fields in the statistic operation had a NULL value. Those values are excluded from the statistics computation.

The requested statistical operation found one or more NULL values in the fields that were being used for the calculation. Because NULL fields contain no meaningful data for the calculation being performed, only those fields that contain non-NULL values are included in the computation.

59 Warning

Your login failed, but connected as a guest user.

You tried to log in with a user name that BMC Remedy AR System did not recognize. BMC Remedy AR System allowed you to log in, but only as a guest user.
If you think the login name exists, verify spelling and capitalization to continue. Enter the login name correctly (including case).
If the login name does not exist, ask the administrator to add the user as a valid login name to the system.

60 Warning

You do not have read access to field.

You tried to access a field to which you do not have read access. If access to this field is required, ask the administrator to extend your permissions to include this field.

61 Warning

You do not have read access to this field on this record.

You tried to access a field to which you do not have read access for the current BMC Remedy AR System request. If access to this field on this request is required, ask the administrator to include read access to this field.

This message is issued (instead of Warning 60) when you may have access to this field on some requests, such as when you are the Submitter or Assignee, or are a member of the Assignee Group of the specific case.

62 Warning

You do not have access to the requested record.

You tried to access a request to which you do not have access. If access to this request is required, ask the administrator to grant access to you.

This error results when you do not have access to the Request ID field (the unique key given to each request in the system).

63 Warning

One or more values in the statistic operation cannot be retrieved due to permission restrictions. Those values are excluded from the statistics computation.

You tried to perform a statistical operation that included values from fields that you are not allowed to access. BMC Remedy AR System completed the statistical operation, but the inaccessible values were not included in the results. If it is necessary that those values be included in the computation, ask the administrator to extend your permissions to include the fields.

64 Warning

The filter/escalation action cannot write to the specified log file — action created but not logged in the log file.

You created a filter or escalation action that logs to a file. The action was created, but the file you specified does not exist and cannot be created. An associated message provides details. The action does not perform an operation until the file system error is corrected. When the log file is created, the action logs transactions.

65 Warning

Multiple form links are not supported in new filter definition syntax. Only the first link is loaded.

The filter definition uses an older syntax in which filters could be linked to multiple forms. The new definition allows only a single form link. The filter is loaded, but only with access to the first form in the list of forms. Ask the administrator to restructure the filter definition to see a single form. If you need filters with the same actions, create multiple filters.

66 Warning

The query matched more than the maximum number of entries specified for retrieval.

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 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.

67 Warning

Not able to open the menu.

The file associated with the menu is not accessible.

68 Warning

RPC environment variable is out of legal range (390600, 390603, 390619 - 390669, 390680 - 390694). NOTE: The value 390603 and the range 390619 - 390669 are specialty servers and may have restricted functionality.

The value of the ARRPC environment variable is not a legal value. To use the default RPC socket, clear this variable. To use the ARRPC environment variable, this value must be 390600 (the admin daemon), 390603 (the escalation daemon), 390619 (the flashboard daemon), 390620 through 390634 (fast daemon), 390635 through 390669 (list daemon), or 390680 through 390694 (private daemon).
The environment variable is being ignored, and processing continues.

69 Warning

Creation of one of the SQL views for the form failed within the SQL database. Form is created successfully, but the SQL view is not in place.

While trying to create the SQL view for this form, the system encountered the associated SQL error. This error prevented the creation of the SQL view. The table definition and the structure needed by BMC Remedy AR System server is complete and in place. Only the SQL view for this form is not in place.

The definition of the form and associated fields are complete and in place. You can access the form and continue with operation of the system. The only missing information is a SQL view for this form, which is needed only if you directly access the SQL database by using the SQL view.

70 Warning

The character menu referenced by one or more fields in this form does not exist.

The character menu referenced by one or more fields in this form does not exist. No character menu exists for the field, even though the system has a menu defined for it.

71 Warning

Only the Administrator has access to this active link.

The active link is accessible only to Administrators. No permission settings were specified to allow access by other users. This is correct if you are restricting access to the active link. However, if you want other users to perform this active link, administrators must assign permissions to the active link.

72 Warning

The query matched more than the maximum number of entries specified by the server.

The retrieval being performed included a search that selected more than the maximum number of items specified by the server. This number is less than the maximum specified by the server for this call. The call returned the number of entries specified as the maximum by the server.

73 Warning

A change to the Submitter mode setting does not take effect until AR System is shut down and restarted. It is a pending change until the next restart.

A change to the Submitter mode setting does not take effect until BMC Remedy AR System is shut down and restarted. It is a pending change until the next restart.

74 Warning

A duplicate index has been specified — duplicate was omitted.

You specified the same index twice for a form. You cannot create duplicate indexes. This message is a warning about the duplicate, but processing was completed with the index created only once. BMC Remedy AR System automatically creates a unique index on the Request ID field. Although this index does not show in the list of indexes, it is on every form. You receive this error if you try to create an index that contains only the Request ID field.

75 Warning

No floating write license tokens are available. Currently accessing the system in read-only mode. License will upgrade when one is available.

You are assigned a floating write license, but no floating write license tokens are available at this time. You are allowed access to the database for read-only use. The system will try to upgrade your license type when a token is available.

76 Note

A write token has become available and has been allocated to you — access has been upgraded to write access.

You previously received Warning 75. A floating write token became available, and it is allocated to you. You now have full read and write access within your permissions.

77 Warning

No free floating full text license tokens are available. Currently accessing the system without full text search capability. License will upgrade when one is available.

You are assigned a floating Full Text Search Option license, but no floating Full Text Search Option tokens are available at this time. You are allowed access to the database but without access to the full text search (FTS) engine. The system will try to upgrade your license type when a token is available. The system uses the default database search capability on all fields, including the fields that are FTS indexed.

78 Note

A full text token has become available and has been allocated to you — access has been upgraded to allow full text searching.

You previously received warning 77 indicating you could not get a Full Text Search Option license token, but you were allowed to access the system by using the default database search strategy. A floating Full Text Search Option license token became available, and it was allocated to you. You now have full text search (FTS) access within your permissions.

79 Warning

Request for unique setting on database index has been ignored for fields of this type.

A unique index was requested for a field type that does not allow unique indexes, such as a currency field. Request a unique index only for field types that allow it.

80 Warning

Delete field failed — field contents set to NULL and field renamed.

You tried to delete a field from a form. The delete operation failed. Details are displayed in an associated message. The system performed the next closest operation by logically deleting the column, renaming it in the database to avoid naming conflicts, and setting all data values to NULL.

81 Warning

The field is a distributed server reserved field that can be updated only by the distributed server process.

Some of the Distributed Server Option (DSO) reserved fields cannot be changed except by arservdsd. An attempt was made to change one of those reserved fields.

82 Warning

A field with a length greater than 255 bytes cannot be in an index. To prevent an error, the field was removed from the index definition.

A change to the limits definition of a field was made. The new limits cause the field length to change from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is used in one or more indexes for the current form. A field with a length greater than 255 bytes cannot be in an index. To prevent an error, the field was removed from the index definition for the form, and the remaining indexes were rebuilt.

83 Warning

A field with a length greater than 255 bytes cannot be in a result list. To prevent an error, the field was removed from the result list.

A change to the limits definition of a field was made. The new limits cause the field length to change from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is in the list of fields to be returned in the results list. A field with a length greater than 255 bytes cannot be in the results list. To prevent an error, the field was removed from the results list definition.

84 Warning

A field with a length greater than 255 bytes cannot be in a sort list. To prevent an error, the field was removed from the sort list.

A change to the limits definition of a field was made. The new limits cause the field length to change from fewer than 256 bytes to 256 bytes or greater (unlimited). This field is in the sort list. A field with a length greater than 255 bytes cannot be in the sort list. To prevent an error, the field was removed from the sort list definition.

85 Warning

You cannot create indexes on a join form. To index a field, define the index on the base form.

You cannot create indexes on a join form. To index a field, define the index on the base form.

90 Error

Cannot establish a network connection to the BMC Remedy AR System server.

The BMC Remedy AR System server is inaccessible from the client computer where the error occurred. To resolve this problem, consider these questions and then follow the appropriate suggestions:

  • Is the ARERR 90 isolated to a single client computer or user? If so:
    • Check the configuration on the client computer.
    • If the configuration is correct, check the network connectivity from the computer where the error is reported.
  • Is the error reported to a group of computers or users or systemwide? If so:
    • Check the network connectivity from a computer where the error is reported.
    • Make sure the AR System server process is running.

Check the client computer's configuration

  • To verify that the server is registered for client access, review the etc/ar file (utilities or other server components) or the Login > Accounts dialog box (Windows clients).
  • If no entry is in the ar file or the server is not marked with a green check mark in the Accounts dialog box, add the entry or (on Windows) select it.
  • Make sure the server name is spelled correctly in the ar file or the Accounts list in the Windows client Login dialog box.
  • If access to the server requires a TCP port (for example, the server is behind a firewall or is not using the portmapper), make sure the correct TCP port is included in the entry.

Check the network connectivity

  • At a command prompt on a computer where the error is reported, issue a ping command to the server. If the ping command does not return a successful reply, a problem exists with the network connection to the BMC Remedy AR System server.

You might need to test the connection to the server using its short name (for example, <serverName>), its fully qualified domain name (<serverName.domainName.com>), and its IP address (for example, <nnn.nnn.nnn.nnn>).

  • If necessary, work with a network administrator to resolve the problem.

Check the server process

  • Use operating system tools to make sure that the server process (arserverd or arserver.exe ) is running. When the AR System server starts up, error 90 can appear while the server is loading information into the cache. In this case, the server process is running. If this occurs:
    • (UNIX) Check the arforkd process. If it is running, the server has finished loading the cache.
    • (Windows) To determine whether the server port is assigned, use NETSTAT -a. The port is set when the cache load is completed.
    • (UNIX and Windows) Review the arerror.log and armonitor.log files. If the server failed during startup, errors reporting that the server terminated are in these logs.
  • If the AR System server is not running, restart it.

Check the UNIX server hosts file

  • If the server is configured to use a portmapper (TCP port = 0), make sure the localhost line in the /etc/hosts file is above the <hostName> line. For example:
    127.0.0.1 localhost100.100.100.100 TestServer
91 Error

RPC call failed.
AR System clients use the RPC layer to connect to the AR System server's TCP port. This error occurs when an RPC call fails. On CreateEntry RPC calls, this error may occur even if the entry is created. Causes of this error include but are not limited to:

  • An invalid RPC packet was detected
  • (UNIX) The BMC Remedy AR System server is low on file descriptors
    On UNIX, the number of file descriptors allocated to the AR System server is determined by an operating system setting in the shell where the server was started. If thread logging is on when the AR System server starts, the number of file descriptors appears in the thread log. For example:
    Limits found: current rlimit=8192 - max rlimit=8192
    BMC recommends a minimum file descriptor setting of 2048 or 2.5 to 4 times the number of concurrent users, whichever is greater. Concurrent users include other server tier components such as Email Engine, DSO, and custom API programs. To ensure that adequate file descriptors are available in recent releases of BMC Remedy AR System, running with file descriptors set to 8192 on UNIX is not uncommon.
    On Windows, the default setting of 10,000 file handles is generally sufficient. To see whether a process is using a large number of handles, check Windows Task Manager. If this is a recurring error and increasing the file descriptors or file handles for the AR System server does not resolve it, turn on ARAPILOGGING for the client that receives the error to isolate the API call that is failing with ARERR 91. For information about C API client-side API logging, see C API Client-side ARAPILOGGING.
    A less common cause of this error is running an API program that is incompatible with the AR System server. In this case, recompiling the API program with the same API version used by the AR System server might resolve the error.
92 Error

Timeout during database update — the operation has been accepted by the server and will usually complete successfully.

A time-out occurred while data or structures in the database were being updated. In most cases, the operation is performed after the time-out. Verify that the updates were made, and retry the operation if necessary. Because this error occurs on update, it can be associated with a filter action. If this error recurs, use ARAPILOGGING and client workflow logging to identify the API call and SQL statements associated with the error. If you contact Customer Support for assistance, provide the filter, API, and SQL logs containing these SQL statements. (For logging information, C API Client-side ARAPILOGGING.)

Ask your database administrator to review the performance of the database. The performance of the AR System server during database updates depends on the performance of the database. BMC recommends that AR System administrators work closely with database administrators to ensure optimum database tuning.

93 Error

Timeout during data retrieval due to busy server — retry the operation.

A time-out occurred during a retrieval operation because the server or database was busy performing other operations. Causes include low system resources, such as CPU time, or server resources, such as thread congestion.

To troubleshoot this error, first determine whether the time-out error is isolated to an operation (for example, saving a form), a user, or a group of users or is reported systemwide. If the error is isolated to an operation, a user, or a group of users, use client-side logging, including ARAPILOGGING, along with server API and SQL logging to capture the API call associated with error 93. The failed API call is marked in the log with a FAIL status. For example, this entry is for an ARGetServerInfo call with a time-out error:

*/+GSI ARGetServerInfo — as user . . .
*/-GSI FAIL — RPC Client has timed out

For more information about logging, see Enabling logs.
When contacting Customer Support for assistance, provide at least the following information:

  • The server API and SQL logs that capture the time when ARERR 93 occurred.
  • If the error is isolated to an operation or user, provide the client workflow logging with API, database, filter, active link, and macro output captured.
  • A copy of the server ar.conf or ar.cfg file.
  • AR System server environment information:
    • The server operating system and version
    • The database type and version
    • The AR System server version and patch level
  • A list of other applications that might share server resources with the AR System server or the database.
94 Error

Timeout during database query — consider using more specific search criteria to narrow the results, and retry the operation.
A time-out occurred while data was being retrieved from the server during an ARGetList call (ARGetListEntry, ARGetListEntryWithFields, and so on). This can be caused by poorly specified search criteria or by the database being too busy to respond within the time-out period.
If the error is reproducible, use client-side ARAPILOGGING to isolate the API call that fails with ARERR 94. Then use the information in the client-side API log to isolate the API and SQL SELECT statement associated with the error in the client workflow log or in the server API and SQL logs. This error is often associated with a query to a form when a large number of records is returned. You can resolve this error by modifying the search to return fewer records. If the error occurs during a workflow search, you might need to modify the workflow actions or adjust the server settings to return fewer records.

Ask your database administrator for help, and review performance of the database. The performance of the AR System server during database updates depends on the performance of the database. BMC recommends that AR System administrators work closely with database support to ensure optimum database tuning.

To check the database response time for the AR System API call that generates this error, run the SELECT statement captured in the SQL log. To do so, log in at the database prompt as the database owner of the AR System server in the environment where the server is running. To more accurately gauge the time, run the statement from the command line, not from a database tool.

95 Error

RPC and sockets initialization failure.

The attempt to initialize the RPC and sockets subsystems failed. Make sure the proper sockets libraries are present.

96 Warning

Capability not supported by this BMC Remedy AR System client.

Some features cannot be fully mapped from earlier versions of BMC Remedy Administrator.

97 Error

You can connect to only one unlicensed server in a session — Connection to the second server is denied.

The system allows you to connect to only one unlicensed server at a time. You can connect to any number of licensed servers. Either you specified multiple unlicensed servers to connect to, or workflow is accessing a second unlicensed server. You must license your servers to connect to them at the same time from a single client tool.

98 Error

The Administrator Commands feature is no longer supported.

The Administrator Command feature was removed from the product. Its functionality is no longer supported. A comparable functionality is available through active links, which enable you to define a running process in which the process runs on the server.

99 Error

The same AR System Server ID is found on two different servers — neither will be accessible until one is shut down and tools restarted.

Two servers in your environment have the same AR System server ID. Both servers are disabled until the license conflict is resolved.

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