Here's how to troubleshoot problems you might encounter when setting up Google Workspace Migrate and running a migration.
Association errors | Tracking a migration | Bridge errors
Troubleshoot association or connection errors
Expand section | Collapse all & go to top
Check the service host logs- To find the logs:
- On a platform installation—Go to C:\Program Files\Google Workspace Migrate\Google Workspace Migrate Platform\AppBridgeServiceHost.log.
- On a node installation—Go to C:\Program Files\Google Workspace Migrate\Google Workspace Migrate Platform Node\AppBridgeServiceHost.log.
If you're running an earlier version of Google Workspace Migrate, you might need to use G Suite in the path instead of Google Workspace.
- Open the log and scroll to the end.
- If there are relevant issues, troubleshoot the issues.
You can safely ignore the "Access denied: Symmetric encryption is required for this service request but not configured" message.
- If you can't fix the issue, go to Contact support for Google Workspace Migrate issues.
- Sign in to the Google Workspace Migrate platform and, in the top-right corner, click Servers.
- Verify your nodes appear in the list.
- Check that the status of the nodes is Ready (green).
If you get an error when trying to associate a node with the Google Workspace Migrate platform, check if the node is running:
- In a browser on the machine that is running the platform, enter the node's IP address and port (for example, http://192.0.2.1:5131).
- If the platform can reach the node and the node service is running, you'll get a "Node is running" message.
- If you receive an error, try the following options:
- If it's a network error, resolve it and try again.
- Restart the node service.
- Reinstall the node application. For details, follow the steps in Install the node servers.
If you get this error:
- Go to the service host log for the node server.
For details, go to Check the service host logs.
- Check for the following error: The provided platform host address https://platformserver:443/Hub was unreachable.
- If you see the error, try the following options:
- Check the network connection to the platform server. If there's a network issue, resolve the issue and restart the node service.
- If the platform is configured with a TLS certificate, in a browser on the computer that is running the platform, enter the platform's IP address and port (for example, https://192.0.2.1:5131). Also, check that the TLS certificate is valid and that it hasn't expired.
If you get an invalid_grant message in the host log, check whether:
- You enabled all API scopes for your target account. For details, go to Use the Google Cloud Console to turn on APIs.
- The service account is authorized for the required scopes in the Google Admin console. Use your OAuth 2.0 client ID for authorization and not your service account's client ID. For details, go to Create the OAuth web client ID.
If your migration is running slowly or not at all, the error might be related to Google Workspace's API quota levels. For details, go to Work with quotas.
Track the health & progress of a migration
Expand section | Collapse all & go to top
Monitor partitionsAs you run a scan or bridge, you can monitor the status of the partitions.
- In the Google Workspace Migrate platform, click Scans or Bridges.
- On the scan or bridge you want to check, click Logs
Partition log.
- Under State, check the status of the partitions:
- Ready—Ready to begin.
- Starting—Preparing to migrate or scan.
- Crawling—Reading data from the source system.
- Processing—Preparing to write data to the target system.
- Committing—Writing data to the target system.
- Cancelled—Failed. Proceed to Troubleshoot canceled partitions.
- Completed—Finished working.
- Skipped (displays when retrying failures)—Skipped because no failures.
If you find a partition with Canceled in the partition log, troubleshoot using these options below.
Option 1: Check error codes
To find the error codes, point to a row in the partition log and click More
Option 2: Check the nodes
Use the partition log to check whether all partitions on a node are canceled. All nodes canceled usually indicates connection issues, for example, the source service is temporarily unavailable. Complete the steps in Error associating a node. Then, retry the scan or run a delta migration.
Option 3: Check the partition execution log
If the issue affects multiple nodes, you can examine the partition execution log. To view the execution log associated with a partition:
- Open the partition log.
- Point to a row in the log and click More
- Click State
- Review the failures to isolate and troubleshoot the cause of the problem.
- Retry the scan or migration.
If there's an increase in similar failures in the migration summary, your migration configuration is probably incorrect.
Check the following configuration items to make sure they're correctly set up:
- Ensure the APIs, particularly the Admin SDK, are correctly enabled in the Google Admin console. For details, go to Use the Google Cloud Console to turn on APIs.
- Make sure the user account exists on the source account and in Google Workspace. Verify the account is not frozen, suspended, or renamed.
- Verify that all users have the necessary Google Workspace services (for example, Gmail or Google Drive) turned on. For details, go to Google Workspace requirements.
If you get this error in the host logs, you might need to allow third-party apps for Drive files.
To fix the issue, follow the steps in Allow third-party apps to work on files stored in Drive.
Fix bridge errors
Expand section | Collapse all & go to top
Run a bridge as a delta migrationYou can often fix many errors by running a delta migration. A delta migration identifies persistent errors and cleans up temporary issues, such as rate limiting and quota levels, networking issues, and 401 errors. You can run a delta migration multiple times to troubleshoot. For details, go to Get ready to go live.
| 60008 error or keyword | Steps to troubleshoot |
|---|---|
| No mapping found. | You might get this error if you're migrating shared drive data from one Google Workspace account to another, and you have manually created the shared drives on the new account. To troubleshoot:
|
| Transaction that the affected item depended on failed. | Look at other failed items in the same bridge and troubleshoot those issues. When you resolve the issues, run a delta bridge. |
|
Parent object failed to migrate. You might also see: The bridge execution was halted or completed prior to dependency of the transaction being completed. |
The parent object of the affected item failed to migrate, or the child object migrated before the parent. To troubleshoot:
|
| Target parent entities removed, renamed, or moved to another location after a migration. When another bridge attempted to migrate the source parent or child entities again, they couldn't be found. |
|
| Source-to-target mapping pair isn't supported. | Review your mappings to make sure that the source and target locations are valid. For details, go to Create & manage a mapping for Exchange, SharePoint, file shares, Box, or Google Workspace. |
| LocationNotFound | A Google Workspace shared drive couldn't migrate to a shared drive on the target account because the target user doesn't have a Google Workspace license that includes shared drives. Check the licenses on your target account and try again. |
| OrphanedContent |
You might also see this error if the owner of the orphaned item isn't specified as a source account in the mapping. Google Workspace Migrate won't migrate the item and shows a 60008 error code. The error is unavoidable in this situation. Note: Orphaned files in a different target location likely stem from a separate issue. The situation can occur, for example, if there is no target folder specified in the mapping for orphaned items, and the items are put in the target user's My Drive root folder. |
- In the Google Workspace Migrate platform, click Scans or Bridges.
- On the scan or bridge that you want to check, click Logs
- Point to the transaction and click More
- Use the table to locate common transaction errors and steps to troubleshoot.
| Error message & code | Steps to troubleshoot |
|---|---|
| Transaction in a Failed state | Locate the transaction and troubleshoot using the information in the transaction details. |
| Error message: The request type does not allow write operations
Error code: 1048640 |
The request handler for the object type is unable to write the object to the target account (for example, the source item doesn’t have an equivalent type in Google Workspace).
Check if your location mapping is set correctly and the mappings are logical. |
| Error message: An internal connector error occurred
Error code: 2097125 |
Check the error messages in the transaction and execution logs. If the error message doesn’t help, check for detail in the platform or node service host logs. |
| The bridge execution was halted or completed prior to dependency of the transaction being completed | The item didn't transfer because it depended on another item being migrated first, but that item didn’t migrate successfully. For example, a file in a folder didn’t migrate because the folder wasn't created in Drive.
In the error, find ABHierarchicalPath.Path and note the associated item. Then, find the item in the transaction logs to understand why it failed to migrate. |
A transaction in your transaction log might be skipped for the following reasons:
- You're running a delta migration, and the object hasn't changed since the previous migration.
- The object was excluded by a filter condition in the settings template.
- You're migrating email content to a group, and a large message attachment is skipped.
- You're using a shared drive settings template but migrating content to My Drive.
Depending on the migration source, other reasons that an item could be skipped are:
- SharePoint—A folder is skipped because it isn't part of a document library.
- Exchange—Draft emails are skipped when they're migrated to Google Groups.
- Box—A file revision is skipped because the revision is empty.
- File shares—An item is skipped because the nodes don't have sufficient permission to access the item.
- Gmail—Chat messages (items under the Chat label) are skipped.
Still need help?
Go to Contact support for Google Workspace Migrate issues.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.