Error messages and problem solving

A warning or error message might be displayed in the user interface to provide information about the adapter or when an error occurs.

The following table contains warnings or errors that might be displayed on the user interface if the adapter is installed on your workstation.

Table 1. Warnings, error messages, and corrective action
Warning or error message	Corrective action
ERROR (307): Required field (without a default) not specified; 101. ERROR (307): Required field (without a default) not specified; 8.	Specify the following required attributes on the account form: Login Name Full Name
ERROR (382): The values for this entry violate a unique index that is defined for this form.	Provide a unique login name for the Login Name attribute on the account form when you perform a user add operation.
(52) The field is a core system field and cannot be changed.	An attempt was made to modify the contents of one of the following core system fields: Request ID Create Date Last Modified By Last Modified Date Do not modify these fields because the Remedy AR System server sets values for these fields.
ERROR (326): Required field cannot be reset to a NULL value; 2.	An attempt was made to delete the value specified in the Creator field. The Remedy AR Systemserver sets the default for this field; however, if you specify a different value, ensure that you: Do not set the value of the field to NULL. Specify a string value (for example, `Demo`) or an alphanumeric character (for example, `av234`.)
ERROR (417): Cannot translate a group name in either the Group List or Assignee Group field; 104.	This error occurs when an incorrect value is specified for the Group List attribute during the user add operation. Perform the following steps to set the Group List attribute: Ensure that the group exists on the Remedy AR System server by performing a support data reconciliation operation. Select the group from the updated list available for the Group List attribute.
ERROR (30): You are already at the limit of the number of fixed user licenses of the following type; Full Text : (0).	An attempt was made to create a user and assign a fixed license to the user. You reached the limit of the number of fixed user licenses. Add the user with a read, none, or floating license, however, not a fixed license. The License Type attribute is replaced by write, full text, or flashboards to indicate the type of fixed license. If you do not have anymore fixed licenses, ensure that the sample users are deleted. Contact the Remedy AR System server distributor for information about obtaining additional licenses.
ERROR (9860): The application license format is not valid.	This error occurs either when the application license format is not correct or the license information is specified incorrectly. Ensure that the license names end with User Fixed or User Floating and each license for a user is separated by a semicolon (;).
ERROR (8932): You do not have write license.	An attempt was made to add or modify the contents of a field, however, you do not have write access. Ensure that you provide the Resource Administrator name who has read and write permissions on the Remedy AR System server, for example, `Demo` on the adapter service form on IBM® Security Identity Governance and Intelligence.
ERROR (333): You have no access to field; 101.	An attempt was made to add or modify the contents of a field, however, you do not have read or write access. Ensure that you provide the Resource Administrator name who has read and write permissions on the Remedy AR Systemserver, for example, `Demo` on the adapter service form on IBM Security Identity Governance and Intelligence.
ERROR (302): Entry does not exist in database.	An attempt was made to modify a user that does not exist in the Remedy AR System database. Ensure that the user exists in the database by performing a reconciliation operation and then perform the modify operation.
ERROR (90): Message not in catalog; Message number = 90;ONC/RPC program not registered IP Address of Resource.	This error occurs when an attempt to connect to the Remedy AR System server fails. Perform one of the following steps: Check whether you can ping the workstation on which the Remedy AR System server is installed. If you cannot ping the workstation, ensure that the Remedy Action Request System server service is running on the workstation on which the Remedy AR System server is installed. If the service is not running, restart it. Check whether there is successful LAN connection between the Security Directory Integrator and the workstation on which Remedy AR System server is installed.
ERROR (304): Must have Administrative permissions to perform this operation.	An attempt was made to add, modify, or delete a user without the Administrator permissions and Fixed License of the Remedy AR System server. Ensure that you have Administrator permissions and a Fixed License of the Remedy AR System server to perform the operation.
WARNING (77): 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; Hostname of Remedy AR System server	You are assigned a floating, Full Text Search Option license, however, there are no floating, Full Text Search Option tokens available at this time. You can access the database without access to the full text search (FTS) engine. The system tries 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.
ERROR [com.remedy.arsys.api.NativeLibraryLoader] - Could not load native library java.lang.UnsatisfiedLinkError: arjni70 (Not found in java.library.path)	Perform the following steps: Copy the C API files for AIX operating system to the `ITDI_HOME`/jvm/jre/bin/classic directory. See Copying the Remedy AR System library files. Navigate to the `ITDI_HOME`/jvm/jre/bin/classic directory. Run the following commands: `ln -s libicui18nbmc32.0.a libicui18nbmc32.a ln -s libicudatabmc32.0.a libicudatabmc32.a ln -s libicuucbmc32.0.a libicuucbmc32.a` Restart the Dispatcher service.
ERROR [com.remedy.arsys.api.NativeLibraryLoader] - Could not load native library java.lang.UnsatisfiedLinkError: arjni70 (Not found in java.library.path)	Perform the following steps: Copy the C API files for HP-UX operating system to the `ITDI_HOME`/jvm/jre/lib/PA_RISC2.0/server directory. See Remedy AR System. Navigate to the `ITDI_HOME`/jvm/jre/lib/PA_RISC2.0/server directory. Run the following commands: `ln -s libicui18nbmc.sl.32.0 libicui18nbmc.sl.32 ln -s libicudatabmc.sl.32.0 libicudatabmc.sl.32 ln -s libicuucbmc.sl.32.0 libicuucbmc.sl.32` Restart the Dispatcher service.