Skip to main content
  1. CloudM
  2. Migrate 4
  3. Errors & Troubleshooting
  4. Errors

Error: "Unable to get file ACLs as the owner cannot use the drive API" in Google Drive Migrations

Updated

This article explains how to resolve an error that occurs during a Google Drive migration when CloudM Migrate cannot access a user's files.

1. Symptom

During the migration of a user's Google Drive data, the process fails, and the following error message appears in the migration logs:

ERROR: Unable to get file ACLs as the owner cannot use the drive API

This indicates that the migration tool is being blocked from accessing the file permissions (Access Control Lists - ACLs) for one or more files owned by the source user.

2. Cause

This error occurs for one of two primary reasons related to the source user's Google Workspace account:

  • The user account is suspended: Suspended users are immediately blocked from accessing their Google Workspace account and all associated services, including the Google Drive API.

  • The Google Drive service is disabled for the user: The user's account may be active, but if the Google Drive and Docs service has been turned off for their specific Organizational Unit (OU) or for their individual account in the Google Admin console, the API will be inaccessible.

3. Resolution

To resolve this issue, you must ensure the source user account is active and that the Google Drive service is enabled for them.

Step 1: Check the User's Account Status

  1. Sign in to your Google Admin console.

  2. Navigate to Directory > Users.

  3. Search for the user account that is failing to migrate.

  4. Check the user's status. If the account is suspended, the status will be clearly marked in red.

  5. If suspended, select the user and click Reactivate to restore their account to an active state.

Step 2: Verify the Google Drive Service is Enabled

  1. In the Google Admin console, navigate to Apps > Google Workspace.

  2. Click on Drive and Docs.

  3. Select Service status.

  4. Ensure that the service is set to ON for everyone or is specifically enabled for the Organizational Unit (OU) that the user belongs to.

  5. If the service is off for the user's OU, you will need to either:

    • Turn the service ON for that OU.

    • Move the user to an OU where the service is enabled.

Once you have confirmed the user is active and the Drive service is enabled, you can re-run the migration for the affected user in CloudM Migrate.

Was this article helpful?
0 out of 0 found this helpful