ARCHIVED: Interpret error messages from your Google data migration report

This content has been archived, and is no longer maintained by Indiana University. Information here may no longer be accurate, and links may no longer be available or reliable.

Use the information below to interpret migration errors that may have appeared your individual or institutional/group "Google Migration" DryvIQ report.

If you receive an error message not listed here, check to see if the data migrated. If not, you'll need to move it manually. For assistance, contact your IT Pro or your campus Support Center.

Also, be sure to remove data in Google, so that your account remains under quota.

Important:

You’ll need to carefully review your migration reports and manage any failed file migrations. UITS cannot do this work for you, although staff can provide limited guidance in helping you plan for managing your files. For live conversations where you can ask questions, attend a weekly coffee hour at 10am on Wednesdays. You can also contact your local UITS support person.

Error	Severity	Description	Next steps
This file has been identified as malware or spam and cannot be downloaded. [code=cannotDownloadAbusiveFile]	Error	Google Drive flags all `.exe` files and some other file formats as malware without scanning.	If you still need the file, manually copy it to the destination. There is no indication that the file is malware.
The truncated name would result in name conflicts on the storage platform. Duplicate item resolved	Error	A Google file format with the same name exists in the same directory (for example, `test.docx` and `test.gdoc`) so the API cannot create a second copy.	Compare the Google document with its Microsoft counterpart to see if you need to create an additional manual copy.
An access rule for identifier Account[Name here] could not be propagated to the destination platform. Cannot update or delete an inherited permission on a shared drive item. [code=cannotModifyInheritedTeamDrivePermission]	Warning	The person already has inherited permissions on the file/folder, so DryvIQ cannot apply additional permissions to the file or folder. Typically this means the person is already a member of the share and has permissions to any data that has been migrated to that space.	Double-check that the member is part of the share. No action should be necessary.
Response status code does not indicate success: 404 (Not Found).	Failure	During a validation check, the file or folder could not be found at the destination.	Confirm the item does not exist at the destination, and manually move the item if necessary.
An impersonated connection could not be made using the Account [external email address].	Failure	Example: "An impersonated connection could not be made using the Account [dvader@empire.com]." This is an issue with how DryvIQ interprets item ownership. DryvIQ is attempting to migrate a file or folder as another account; since the account is external and not part of IU, DryvIQ cannot impersonate the account.	Manually move the item. Administrators are working with DryvIQ to determine best steps to mitigate this issue for future migrations.
The account 'IU user' is not authorized to perform the requested operation.	Failure	Example: "The account 'jdoe@iu.edu' is not authorized to perform the requested operation." In some cases, the error message may also include the display name of an IU staff member. This is an issue with how DryvIQ interprets item ownership. DryvIQ is attempting to migrate a file or folder as another account, and while it can successfully impersonate the user, the user it's impersonating doesn't have the proper permissions, resulting in a failed item migration.	Manually move the item. Administrators are working with DryvIQ to determine best steps to mitigate this issue for future migrations.
The content rendition could not be retrieved.	Failure	Data did not migrate.	Look into manually copying over the contents.
String or binary data would be truncated. The statement has been terminated.	Warning	This does not appear to be a significant error. May indicate file(s) that haven't migrated successfully.	Check your files with this error in both locations to ensure they have moved, that the file size is the same, and the list of collaborators is consistent. If so, no further action is needed.
The path exceeds the maximum number of 10,000 children.	Failure	The folder contains over 10,000 direct objects and cannot be moved to either destination.	Zip the folder in Google Drive, and then manually move it to your chosen destination.
The item was too large to transfer into the destination storage platform.	Failure	For Microsoft Storage at IU, this means the file was larger than 250 GB and could not be moved.	Move the file to an alternate location, or use a zip program to break it into smaller archives.
Unable to preserve modified-by - security identifier could not be mapped: Account[FirstName LastName] Unable to preserve created-by - security identifier could not be mapped: Account[FirstName LastName]	Info	These objects were created or modified by someone who is either external to IU, or no longer works at IU, and DryvIQ can't set those metadata attributes correctly on the file.	No action needed.
A security identifier could not be mapped: Account[FirstName LastName].	Warning	Sharing permissions could not be mapped to users. Most likely occurs with IU users that no longer exist, or external users that could not be mapped to the destination platform.	If sharing permissions need to be maintained, the owner will have to recreate a sharing link with the details provided.
The provided grant has expired due to it being revoked, a fresh auth token is needed.	Warning	This does not appear to be a significant error. May indicate file(s) that haven't migrated successfully.	Check your files with this error in both locations to ensure that they have moved, that the file size is the same, and that the list of collaborators is consistent. If so, no further action is needed.
The item could not be located within the storage platform.	Warning	This does not appear to be a significant error. May indicate file(s) that haven't migrated successfully.	Check your files with this error in both locations to ensure they have moved, that the file size is the same, and that the list of collaborators is consistent. If so, no further action is needed.
Response status code does not indicate success: 403 (Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.)	Failure	During a validation check, the file or folder could not be found at the destination.	Confirm the item does not exist at the destination, and manually move the item if necessary.
Bad Request [code=failedPrecondition]	Failure	Data did not migrate.	Look into manually copying over the contents.
Source stream timed out on read	Failure	Data did not migrate.	Look into manually copying over the contents.
Service Unavailable	Failure	Data did not migrate.	Look into manually copying over the contents.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)	Failure	Data did not migrate.	Look into manually copying over the contents.