Error Code List

This list of error codes includes locations that are reserved for error codes that do not currently exist.

0. AM_SUCCESS

The operation completed successfully.

1. AM_FAILURE

The operation did not complete successfully. Please refer to the log file for more details.

2. AM_INIT_FAILURE

The C SDK initialization routine did not complete successfully. All the other APIs may be used only if the initialization went through successfully.

3. AM_AUTH_FAILURE

The authentication did not go through successfully. This error is returned either by the Authentication API or the Policy Initialization API, which tries to authenticate itself as a client to Access Manager.

4. AM_NAMING_FAILURE

The naming query failed. Please look at the log file for further information.

5. AM_SESSION_FAILURE

The session operation did not succeed. The operation may be any of the operations provided by the session API.

6. AM_POLICY_FAILURE

The policy operation failed. Details of policy failure may be found in the log file.

7. This is a reserved error code.

Currently, no error code exists at this location.

8. AM_INVALID_ARGUMENT

The API was invoked with one or more invalid parameters. Check the input provided to the function.

9. This is a reserved error code.

Currently, no error code exists at this location.

10. This is a reserved error code.

Currently, no error code exists at this location.

11. AM_NO_MEMORY

The operation failed because of a memory allocation problem.

12. AM_NSPR_ERROR

The underlying NSPR layer failed. Please check log for further details.

13. This is a reserved error code.

Currently, no error code exists at this location.

14. AM_BUFFER_TOO_SMALL

The web agent does not have memory allocated to receive data from Access Manager.

15. AM_NO_SUCH_SERVICE_TYPE

The service type input by the user does not exist. This is a more specific version of AM_INVALID_ARGUMENT error code. The error can occur in any of the API that take am_policy_t as a parameter.

16. AM_SERVICE_NOT_AVAILABLE

Currently, no error code exists at this location.

17. AM_ERROR_PARSING_XML

During communication with Access Manager, there was an error while parsing the incoming XML data.

18. AM_INVALID_SESSION

The session token provided to the API was invalid. The session may have timed out or the token is corrupted.

19. AM_INVALID_ACTION_TYPE

This exception occurs during policy evaluation, if such an action type does not exist for a given policy decision appropriately found for the resource.

20. AM_ACCESS_DENIED

The user is denied access to the resource for the kind of action requested.

21. AM_HTTP_ERROR

There was an HTTP protocol error while contacting Access Manager.

22. AM_INVALID_FQDN_ACCESS

The resource provided by the user is not a fully qualified domain name. This is a web container specific error and may be returned by the am_web_is_access_allowed function only.

23. AM_FEATURE_UNSUPPORTED

The feature being invoked is not implemented as of now. Only the interfaces have been defined.

24. AM_AUTH_CTX_INIT_FAILURE

The Auth context creation failed. This error is thrown by am_auth_create_auth_context.

25. AM_SERVICE_NOT_INITIALIZED

The service is not initialized. This error is thrown by am_policy functions if the provided service was not initialized previously using am_policy_service_init.

26. AM_INVALID_RESOURCE_FORMAT

This is a plug-in interface error. Implementors of the new resource format may throw this error if the input string does not meet their specified format. This error is thrown by the am_web layer, if the resource passed as parameter does not follow the standard URL format.

27. AM_NOTIF_NOT_ENABLED

This error is thrown if the notification registration API is invoked when the notification feature is disabled in the configuration file.

28. AM_ERROR_DISPATCH_LISTENER

Error during notification registration.

29. AM_REMOTE_LOG_FAILURE

This error code indicates that the service that logs messages to Access Manager has failed. The details of this error can be found in the web agent’s log file.