Troubleshooting Google Vault Extractor

​​​It is necessary to carefully read through reasons for failure in both the Extractor console and log files.  Most errors are in easy-to-read language, but may be included in long console messages.  Please reference the section below for help diagnosing any errors or messages.  If this page is not addressing your specific issue, please contact BitTitan Support through the MigrationWiz console's Help button.

Note: ​The Google Vault Extractor requires that you have the .NET Framework version 4.6.1 or later installed on the computer on which you install and run the extractor. To determine the .NET Framework version currently installed, follow instructions provided by Microsoft: How to: Determine Which .NET Framework Versions Are Installed
 

Gathering Troubleshooting Information:

  • Deep logging can be found at %userprofile%\appdata\local\bittitan.
    • GoogleVaultExport will contain log output from the console regarding the extraction of data from Google Vault.
    • UploaderWiz will contain log output from the console regarding the upload of Google Vault content from your local machine to Azure.
  • Extra log verbosity is an option by adding the following string to GoogleVaultExport.exe.config inside of the <appSettings> key:
    • <add key="serilog:write-to:RollingFile.restrictedToMinimumLevel" value="Verbose" />
  • Before contacting Support, we recommend that you record a trace of the connection from the time you start Extractor until it stops.

 

Troubleshooting Specific Errors:

  • Message[Quota exceeded for quota metric 'vault.googleapis.com/export_writes' and limit 'ExportWritesPerMinutePerProject' of service 'vault.googleapis.com' for consumer 'project_number:54169706180'.] Location[ - ] Reason[rateLimitExceeded] Domain[global]

To resolve this error, follow the steps in OAuth Set Up.

  • [Error] EX: BitTitan.GoogleVaultExport.Export.GoogleVaultException: Timeout occurred while waiting for new exported Emails for user:
    • These steps are valid for all timeout errors and should be automatically implemented in project that has large export sizes.
    • Google Vault Extractor's timeout settings for gathering new email and waiting for compression can be adjusted with a command line switch.  Remember to implement both switches.
    • -newEmailsTimeout 86400000
    • -compressionTimeout 86400000
  • Error message number: 5535
    • Missing command line switch "-command"
  • Error messsage number: 11140
    • Missing command line switch "inputFile"
    • Represents an issue with the input file
  • Error message number: 6592
    • Missing command line switch "outputFolder"
    • Represents an issue with the output folder
  • BitTitan.GoogleVaultExport.Export.GoogleVaultException: An error occurred when uploading files: The system cannot find the file specified.
    • ​This error can occur when GoogleVaultExtractor cannot find the UploaderWiz executable to run. Ensure that the Google V​ault Exporter and UploaderWiz ​​zip files are unpacked, and store them in the same directory.​
    • Note: Using UploaderWiz requires that .NET Framework version 4.6 or later be installed on the computer on which UploaderWiz runs.​​​
  • Unspecified disconnection and retry failure messages: Due to the method by which Google exports information, disconnection and subsequent retry failures are not uncommon on large exports.
    • Login – regardless of a recent login, please visit the Google Vault page: https://ediscovery.google.com and log out if logged in.  Now log in again and reattempt the export.
  • Messages such as: login failure, unable to login, captcha/challenge page, duplicate input field
    • Login – regardless of a recent login, please visit the Google Vault page: https://ediscovery.google.com and log out if logged in.  Now log in again and reattempt the export.
  • Response status code does not indicate success: (response code listed here)
    • Matters created by Exporter can be identified by the ID string attached to the name of the Matter.
    • This typically represents and unexpected page error.
    • Login – regardless of a recent login, please visit the Google Vault page: https://ediscovery.google.com and log out if logged in.  Now log in again and reattempt the export.
    • Verify Matters – log in to Google Vault and select Matters.  If Exporter was exporting a specific user at the time of the error, remove any Matters created by the Exporter for that specific user and try again.
  • Some messages failed to export correctly.
    • Rerun the export.
  • What if my export fails while in process?

    • Google Vault Exporter is able to resume exporting vault files where it previously stopped.

    • Exports taking longer than 24 hours will be canceled by Google Vault.
    • ​​Note: Do not run more than 30 instances of Google Vault Extractor.  Google Vault can support a maximum of 30 parallel exports.​
  •  

    I've tried everything here and still can't export my Vault.

    • Before contacting Support, run the Extractor on a different or a new machine, and verify the same result.

 

Contacting Support:

If a specific issue isn't listed, or these steps aren't providing a solution, contact BitTitan Support through the MigrationWiz console's Help button.  We want to hear from you! Be sure to include the following information:

  • Basic Exporter log
  • Deep logging
  • Fiddler trace
Was this article helpful?
0 out of 0 found this helpful