Explanation: The AR System user configured in the Remedy Adapter connection does not exist on the AR System Server. However, the logon succeeded and the connection was enabled with a guest user on the AR System. Note that this happens only when the AR System is configured to allow guest users logon.

Action: Check the user account you have defined in the adapter connection. If you do not want to allow guest user logon, configure the AR System to deny logon to guest users.

Explanation: When creating an adapter service, Designer displays appropriate adapter service settings in the Flow Service Editor. Designer accesses logic in Remedy Adapter to obtain the appropriate settings for the adapter service. Remedy Adapter was unable to obtain all the form names from the AR System. As a result, the Form Name field in the adapter settings will not list all available forms.

Reason: Remedy Adapter is unable to obtain all form names might be that the user does not have the privilege to access one or forms, or there might be a problem with one or more forms.

Action: If the Form Name field contains the form you want to use, proceed. Otherwise, use have an AR System administrator check the form and its accessibility, and make corrections as necessary.

Explanation: Remedy Adapter is retrieving a value from an AR System field. However, the data type of the AR System field is not supported by Remedy Adapter. Remedy Adapter will use the data type java.lang.Object for the field. For more information about data type mappings, see AR System Data Type to Adapter Data Type Mapping.

Action: To avoid the error, you can update the Input Fields tab of the adapter service to unselect the Use Field check box.