Error message

Invalid requests[0].deleteDimension: Cannot delete a column that doesn't exist. Tried to delete column index 2 but there are only 2 columns.

What’s happening?

You deleted Column C from the mapping sheet and/or deleted column D from the binding sheet. At the end of the extraction process there's a formatting process which reformats your spreadsheet. It failed because the default number of columns changed.

Solution 

Don't delete any columns in the mapping sheet or the binding sheet.

Error message

500 internal error

What’s happening?

An internal error occurred in Migrate for AODocs or in the source data.

Solution 

Investigate the issue to check whether it comes from your source or from Migrate for AODocs. For example: for Sharepoint migrations, you should have a line in the log displaying something like this: 

[Sharepoint] load url : https://[...]/_api/Web/Lists(guid'abcdefg')/Items

Try to access this URL using your browser. This is often related to internal Sharepoint errors that must be solved.

If the problem is on the AODocs side, contact the AODocs Support team by email at support@aodocs.com or open a ticket.

Error message

More than 50000 characters in a cell

What’s happening?

You’re exporting data "from scratch" using a Google Spreadsheet.

Your export contains a document property with more than 50,000 characters. Google Sheets doesn't support this many characters in a single cell.

Solution 

Run a migration "from scratch" using a CSV file into Google Drive to be able to store these large properties. Your data is exported into the migration folder in your My Drive in a subfolder named with your migration ID.

Note: This is less flexible as you have to edit it using a text editor, but it will help you to find the value that's too large.

Issue

You can't addd a service account as an uploader account on the administration page. 

After entering the service account name, the consent applies to your current migration account instead of a new uploader account.

Learn more: Add uploader accounts.

What’s happening?

You're trying to use a service account that doesn't have access to the Google Drive service, which is mandatory to be defined as uploader account.

Solution 

Use Google Workspace accounts as uploader accounts or activate Workspace services on this service account

Error message

No uploader account available

What’s happening?

You’re trying to migrate documents containing attachments stored in Google Drive. To do this, you need to define at least one uploader account with Google Drive offline access consent (granted via a dialog when you add a new uploader account).

Solution

1. Access the administration page and add an uploader account to your domain.

2. Grant offline consent (if you’re not using the domain-wide Migrate for AODocs - Uploader management application on the Google Workspace Marketplace).

3. Assign the uploader account to your workspace.

Learn more: Create and authorize uploader accounts.

Error message

Key path element name is longer than 1500 bytes

What’s happening?

One of properties in your document class is bound as a Category property, and the value of this property in a document is too long to be stored in an AODocs Category property.

Solution 

In the binding sheet find properties bound as Category and see the "Source name"

In the data sheet find the value in the columns mapped to a category.

There are two options:

• If you don’t want to alter the original data, change the category type containing values that are too long from CATEGORY to TEXT.
• If you want to keep the CATEGORY type, reduce the size of the value of the category in the document (maximum 1000 characters).

Error message

com.google.apphosting.api.DeadlineExceededException

What’s happening?

Your migration contains too much data to be performed in 10 minutes.

This usually means you have many document classes, folders or properties to create.

Solution 

Split your migration in two to be able to perform all checks in 10 minutes.

Error message

Duplicated IDs : [0CCE…..] running a Lotus migration.

What’s happening?

You have a file named 0CCE…...xml which contains the same information as another file. This means you have two files generated for these two XML files. 

Solution 

There are two options:

• In your migration spreadsheet, find the two rows that have the same ID, delete one of them and re-run the validation.
• Search in the export folder for the XML file indicated in the error message. If it is there, delete it then copy the migration and delete the obsolete migration.

Error message

06C003A0C23D934580257EE300380520 | attachment 'file:///E:/AODocs/NotesExporter/802569F40051945D%20-%20Deal%20Archive/files/06C003A0C23D934580257EE300380520-
Incident%20-%20151016-000710%20-%20New%20Business%20Template%20
%20Fixed%20Fee%20Commercial%20contract_php.mht=null' not uploaded 

What’s happening?

A source file wasn't successfully uploaded during the upload stage.

The validation checks that all attachments listed in the data sheet in your migration spreadsheet have valid Google Drive files as destination. If you got this error, a file hasn’t been successfully uploaded.

Solution 

Patch the migration to bring it return it to the upload stage to upload missing attachments (only the missing attachments will be uploaded).

1. Open the API Explorer - Migration patch.

2. Edit the URL as indicated below:

4. Click Authorize and execute.

The gateway resumes the upload stage and then progresses to the validation stage.

Error message

Some versions don't have an ID defined.

What’s happening?

You mistakenly created extra rows in your migration spreadsheet which lack mandatory information such as ID or TITLE. 

This usually happens when you create a CSV file from an Excel file. Migrate for AODocs doesn't remove extra columns as they aren't empty (they contain ",,,,,")

Solution 

Delete the extra rows created by mistake, and continue your migration.

Error message

ApiField(super=ApiDocumentField(fieldId=Rz4KQCp0KrGIdMAONj,  [....]) is not a native field

What’s happening?

There's an issue with a property being created that already exists as a Category in your library but not as a Category in the binding sheet.

Solution 

In the migration spreadsheet, find the property in the binding sheet, and switch it to CATEGORY.

If you can't find the property, use the API Explorer to identify which property it is, using libId and the documentTypeID to retrieve the corresponding name of the property ID.

Error message

Invalid property id: STRING for DocumentClass[...]) 

What’s happening?

There's an issue with a property being migrated that isn’t the correct type: it is either already a Category in AODocs but set as a String in the binding sheet or vice versa.

Solution 

Check the existing categories in the library and make sure that they strictly match the properties noted as CATEGORY in the binding sheet. 

Error message

For input string: "abcd"

What’s happening?

You’re trying to migrate a document with an invalid format into AODocs.

This may mean that you created properties in AODocs before running the migration, but you created one or more duplicate properties, marked as DOUBLE and defined as STRING in the binding sheet. 

Solution 

Check the binding sheet to identify the wrongly defined property.

Error message

Task size too large.

What’s happening?

You’re trying to migrate a document that contains too many items of data to be performed in a row.

This usually occurs when you’re trying to migrate documents:

• from Lotus Notes, with many empty properties
• with lots of versions and lots of properties for each version

Solution 

Open the data sheet and binding sheet in your migration spreadsheet.

You may see many empty properties (in our Lotus Notes migration test, we had 2645 empty properties out of a total of 3000 properties). The binding is used for all documents that are created and uses lots of memory if you defined lots of properties. This means that you don’t have enough space for document data. Delete all the unnecessary empty properties (in the data sheet and the binding sheet) and retry your migration. 

Note: If you're using Google Cloud Storage, you can't edit your migration spreadsheet.

Error message

The file with fileId: [...] has already been added to AODocs

What’s happening?

One of the following is occurring:

• Your document is already created in AODocs.
• You’re trying to migrate a document with a Google Drive attachment which is already attached to an existing AODocs document.

Solution 

1. Find the document corresponding to this file ID using the API Explorer

2. Check the existing AODocs document has the expected properties and versions.

3. Find the corresponding line in the data sheet and delete it.

4. Resume the migration to complete it.

Issue

A PKIX message appears in the Gateway during the extraction of the content after the creation of the Sharepoint migration.

What’s happening?

The connection between Sharepoint and your Virtual Machine (VM), which is included in the browser, must be secure. The JAVA program doesn’t have access to the certificate.

Solution 

Add the certificate manually. You must be administrator of the VM.

1. Stop Gateway.
2. Open the corresponding Sharepoint site in your browser.
3. Click the lock to the left of the URL in Chrome.
4. Click Certificate.
5. Save your certificate in a folder.
6. Go to the security folder in the installed JAVA folder
   (usually: C:/Program Files/Java/jdk11.X/lib/security)
7. Run the command:
   keytool -import -trustcacerts -keystore cacerts  -storepass changeit -noprompt -alias [ALIAS_OF_THE_SITE]  -file [PATH_TO_CERTIFICATE.cer]
8. Restart Gateway.

Issue

You have many HTTP 429 status codes, leading to an error message in the migration card.

What’s happening?

You’re running too many requests on the Sharepoint online tenant.

Sharepoint online is highly restrictive of the number of requests run by a single user.

Solution 

Use different accounts for different migrations (there's a limit per user defined by Microsoft).

Don't run too many migrations on the same site at the same time (there's a limit per site defined by Microsoft).

Don't run too many requests at the same time on the same domain (there's an overall limit per tenant defined by Microsoft).

Run the migration at night as quotas are also consumed by users working on Sharepoint.

Error message

C:\... because you are running on a non-POSIX file system

What’s happening?

This issue usually occurs on Windows FileServers which aren’t POSIX compliant.

Solution 

This is just a warning to inform you that it may lead to encoding issues when listing files. It doesn't block your migration from proceeding.