...
Error | Additional Error Message | Troubleshooting Steps | Product | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
202 Error | Accepted | Adding the iManage External system and validating the URL causes a 202 Accepted error. This occurs when a cloud iManage system URL is incorrectly entered.
| Applies to:
| ||||||||||||||||||
400 Error | Unsupported Grant Type | The unsupported_grant_type error would imply the response we are getting from the API isn’t what is being expected. For this to suddenly happen would imply a configuration change of some sort or possibly a change in the API on iManage’s side.
| Applies to:
| ||||||||||||||||||
Unable to unmarshall error response | When creating a bulk job, with many thousands of records, this may display.
| Applies to:
| |||||||||||||||||||
Max Field Size Exceeded | This is due to the field being too large for the number of characters allowed.
| Applies to:
| |||||||||||||||||||
Error in processing subjobs |
| Applies to:
| |||||||||||||||||||
Creating/Editing/Removing Users/Groups/Dynamic Groups |
| Applies to:
| |||||||||||||||||||
One or more Profile Metadata is missing in the DMS |
| Applies to:
| |||||||||||||||||||
Illegal argument exception: Field name is null or empty |
| Applies to:
| |||||||||||||||||||
User email is required |
| Applies to:
| |||||||||||||||||||
Invalid Parameter for request |
| Applies to:
| |||||||||||||||||||
401 / Unauthorized Error | - |
If a more detailed message appears when moving a document, workspace, or folder: | Applies to:
| ||||||||||||||||||
The “System” server could not process the request. "Token has expired or is invalid” | then follow:
| Applies to:
| |||||||||||||||||||
If Task Scheduler fails for DU |
| Applies to:
| |||||||||||||||||||
If a DistributedCOM error appears | This is a Microsoft issue, please check Microsoft support. The service account may not be granted the rights to run services. | Applies to:
| |||||||||||||||||||
Cannot read folder_template_details | Applying a template has a case sensitivity for the template name. Try ensuring the case of the name entered matches the name in Template Editor. This error might appear when using a template on Manage Team, or other dialogs or jobs. | Applies to:
| |||||||||||||||||||
User is disabled | May accompany a 401 Unauthorized error. Causes for this was found that the service account did not have a last name setup for the account which is required. | Applies to:
| |||||||||||||||||||
403 Error | Error when using Try Again | This can be due to the templated structure inside CAM for the item doesn’t exist. Check the structure of the template. | Applies to:
| ||||||||||||||||||
S3 Access Denied | If a 403 access denied error happens on the S3 bucket after hitting Run Now on a job:
| Applies to:
| |||||||||||||||||||
Forbidden | If this error appears in Data Uploader or Content Mover, try:
| Applies to:
| |||||||||||||||||||
NRTSession Login/ NRC_ACCESS_DENIED | A 403 may not be displayed if the source system is iManage. Steps to resolve:
In the case of Milan, the NRTADMIN password set in Milan is different than what is set in iManage. | Applies to:
| |||||||||||||||||||
404 Error | NRC_NoRecord | This is due to the user to which the matter was being added, never having logged into iManage. Make sure the user has logged in at least once. For example this may show when adding to My Matters. | Applies to:
| ||||||||||||||||||
Document Search fails to load for a group | You can remove the Cam Users group from the layout since the group has no permissions on the attached role. Steps:
| Applies to:
| |||||||||||||||||||
429 Error | Exceeded Allowance Limit your RestAPI Calls | On your external system (iManage, ND, O365…), you may get this after creating bulk jobs.
| Applies to:
| ||||||||||||||||||
500 Error | Unexpected Error when moving Workspaces | This could be a timeout. This can be a:
Fix the problematic area, and retry the job. | Applies to:
| ||||||||||||||||||
"Object reference not set to an instance of an object" | If the server returns a 500 response with that, follow: If this request includes a skip token and has a top value that is a multiple of 50, follow:
| Applies to:
| |||||||||||||||||||
502 Error | Internal Server Error | This could be because of many different reasons:
| Applies to:
| ||||||||||||||||||
Attribute doesn’t apply |
| Applies to:
| Bad Gateway | ||||||||||||||||||
If Data Uploader reports this with Bad Gatewayconnect ETIMEDOUT |
| Applies to:
| |||||||||||||||||||
Bad Gateway |
1- The system is healthy in iManage or ND. If it is unhealthy, this can cause an error. 2- Are the IP’s whitelisted appropriately? Whitelist the URL’s as given: https://pdocs.atlassian.net/wiki/spaces/CCAM/pages/29491219/iManage#Whitelist-URLs | Applies to:
| |||||||||||||||||||
504 Error | Endpoint Request timed out/ Gateway timed out | 504 means a Gateway or Endpoint timeout. Running developer tools or the Log in the Admin panel will show the following:
| Applies to:
| ||||||||||||||||||
520 Error | Event-based scheduling | May appear when creating a sync to a source system. Rerunning the job errors with the same message.
| Applies to:
| ||||||||||||||||||
User Creation in AD Sync- Error creating user process trace |
| Applies to:
| |||||||||||||||||||
User does not exist in External System |
| Applies to:
| |||||||||||||||||||
No Such Key |
| Applies to:
| |||||||||||||||||||
Trim is not a function at save |
| Applies to:
| |||||||||||||||||||
Number of Policies not Updated/ Error Create/Update Policy Job |
| Applies to:
| |||||||||||||||||||
Number of Columns doesn’t match header at Parser.Error |
| Applies to:
| |||||||||||||||||||
Error uploading WS template TypeError: Cannot read property hasOwnProperty of undefined |
| Applies to:
| |||||||||||||||||||
Error uploading WS template Unique Identifiers are missing |
| Applies to:
| |||||||||||||||||||
Error creating user process trace |
| Applies to:
| |||||||||||||||||||
You don't have permissions to perform this operation. Permissions : View-Move-Workspaces |
| Applies to:
| |||||||||||||||||||
Event based job is not supported for this source entity. |
| Applies to:
| |||||||||||||||||||
Error on persisting matter security detailsCannot read property tostring of undefined |
| Applies to:
|
Token was inactive/ The refresh token expired due to inactivity/ Invalid Grant
...
ER_CON_COUNT_ERROR Too many connections |
| Applies to:
|
The token was issued on 2022-07-27T18:53:18.7646555Z and was inactive for 90.00:00:00
Click the Get Token button, to log in to the Office 365 URL specified above. On successful login, the token is displayed here.
Note: The default validity of the refresh token is 90 days which means the customer has 90 days until they need to generate a new token. An organization can extend the refresh token validity using the PowerShell scripts. For more details on configuring refresh token, refer to the following links:
...
...
Error occured while creating user with {"code":"customer.pod.unexpected.error","code_message":"Duplicate"} | This error generally occurs when the user already exists in iManage Prod Environment and the user is being created in the iManage Dev Environment with the same email address. This is a limitation in the iManage cloud environment. One workaround is to create an email address with a dev.domain for testing purposes. Â Note: This cannot be done automatically with the Data Uploader AD Sync unless you have users setup with these email addresses and would require manual intervention. | Applies to:
|
Token was inactive/ The refresh token expired due to inactivity/ Invalid Grant
Applies to:
Status | ||||
---|---|---|---|---|
|
The token was issued on 2022-07-27T18:53:18.7646555Z and was inactive for 90.00:00:00
Click the Get Token button, to log in to the Office 365 URL specified above. On successful login, the token is displayed here.
Note: The default validity of the refresh token is 90 days which means the customer has 90 days until they need to generate a new token. An organization can extend the refresh token validity using the PowerShell scripts. For more details on configuring refresh token, refer to the following links:
Visit Step 5 from https://pdocs.atlassian.net/wiki/spaces/CCAM/pages/30244896/M365+with+CAM+configuration#Connecting-M365-with-CAM-Platform for more information.
...
...
Data Uploader fails with There is an error in XML document
This is due to an XML error in one of DU’s configuration files. Check:
SourceFiles.config
AppSettings.config
ADMapping.config
...
CAM Commands error with HTTP server IP address could not be found
Confirm there is no extra backslash / in the Redirect URL in IMCC
Confirm there is no extra backslash in the External System Configuration RedirectURL
...
Data Uploader fails with UniqueIdentifier is empty
This error message is displayed if Unique Metadata is not assigned to the workspace. To resolve this, update the metadata in the external system configuration to contain the unique metadata (typically clientid, matterid).
...
Office365 API has failed due to token expiration
Refresh the token in the External System Configuration panel, ensure it has a green checkbox.
Renew the client secret in Microsoft by one of the following ways:
Create a new client app and register it to get the clientid and secret as you did in setup. Change the config to that one instead of the old one.
Use the Microsoft guide here to refresh it via powershell: https://www.sharepointdiary.com/2020/12/how-to-renew-a-client-secret-in-sharepoint-online-using-powershell.html
Error {} in applying a security group to a workspace
Confirm group name is not too long
If feeding the id instead of the name, ensure one or the other is present. If both are, it will check both.
Was the iManage or external system group name manually edited but not the CAM name?
The user/group drop-down appears based on the flag set on the layout or system set on templates.
Coinciding Errors Matter system details not found and options.uri is a required argument
These errors display when adding a new folder with the manage folder option.
The issue is because its a non-linked workspace, and there is a limit of 5 folders max that can be added to non-linked workspaces for that command. If you need more than 5, link the workspace.
NRC_FS_NOT_AVAILABLE
Applies to:
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
The file server (iManage) is unavailable to be accessed.
Check with iManage on the reason why it is inaccessible.
...
NRC_EMAIL_IN_USE
Applies to:
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
...
This error occurs when the logged-in user doesn’t have permission to search or update. Please check the user’s permission on a given object (read-only) or check the user’s role permissions in iManage e.g. the permission can’t update or create public documents/folders.
...
Azure Proxy errors
NoneType object has no attribute get
Mismatching redirect URL
If the following error appears: NoneType object has no attribute get, or error- Mismatching redirect URL use the following to troubleshoot.
Confirm there is no extra backslash at the end of the redirect URL. In both Azure proxy, in the CAM external system setup, and check IMCC as well.
Confirm the token setup is on the CAM application and setup successfully.
Try with passthrough authentication.
...
Azure Stack Errors
Applies to:
Status | ||||
---|---|---|---|---|
|
...