This article provides a structured reference for common errors encountered within the Xakia–iManage integration. Each entry sets out the error as it appears, the likely cause, and the recommended steps to resolve it.
Access is denied
Access is denied
Cause | Resolution |
The service principal used to connect to iManage does not have the required permissions, or the application is setup with “Allow Token Refresh” enabled. | Go to Xakia Admin > Integrations and identify the service principal user used to authenticate to iManage.
Ensure that this user exists in iManage and is a member of the NRTADMIN group.
Ensure that the user is a member of the iManage library that the client is trying to link to (using the example screenshot on the left, the library its trying to access is "ACTIVE".
Check the "Allow Refresh Token" setting in iManage Control Center. "Allow Refresh Token" should be set to No. "Access Token Expiry" should be set to 30 minutes.
If a customer needs to make this refresh token change in iManage, the Integration Host needs to be deployed to remove the cached iManage access tokens. |
Error Code 401: Unauthorized
Error Code 401: Unauthorized
Cause | Resolution |
The service principal used to connect to iManage does not exist, is disabled, or the password is incorrect. | Go to Xakia Admin > Integrations and identify the service principal user used to authenticate to iManage.
Ensure that this user exists in iManage and is enabled. Consider resetting the password for this account in iManage - and update the settings on the Xakia side with the new password. |
NRC_NO_PRIVILEGE
NRC_NO_PRIVILEGE
Cause | Resolution |
Service Principal User does used to connect to imanage does not have the required permissions – Xakia recommends NRTADMN access | Go to Xakia Admin > Integrations and identify the service principal user used to authenticate to iManage. Ensure that this user exists in iManage and is a member of the NRTADMIN group. |





