Shuttle allows you to choose from the following report types to verify the job results:
Statistics
The Statistics report displays the job details:
- How many files transferred, with how many errors (if any)
- File metrics, such as the distribution of file sizes
The Job Performance Estimates section in simulation jobs provides a rough job duration estimate and the bottleneck for data migration.
Report
The Report type lists paths to the analyzed files and folders. The Details panel for each entry allows you to verify information such as Source Account, Target Account, Status and more. You can also see who collaborated on a particular file or folder. To do so, click Collaborators.
File System
Displays the details on how your data is structured by showing how many total files and bytes are in each of the root folders. Drilling down into the folders allows you to determine where the biggest clusters of data are.
Use Filters and Source/Target switcher to view specific data sets.
Exports List
Lists the exported reports. You can go through them and download the ones you need.
Users
Lists the owners of files and folders subject to migration. Use Source/Target switcher to view the list of users as they exist on the source (Source tab), or as they will exist on Box (Target tab).
Collaborators
Lists the collaborators (users or groups) on files and folders subject to migration. Use Source/Target switcher to view the list of collaborators as they exist on the source (Source tab), or as they will exist on Box (Target tab).
Job Log
Provides comprehensive information on all files that failed to transfer in your job.
Job Log errors
Sometimes errors can occur during the transfer. Such errors fall into several categories:
- Read / transmit errors: the file may have a permissions issue, it may be left opened, or the file may be copy protected. Read errors typically require user intervention, for example closing files or fixing permissions so a file can be accessed and transferred.
- Transmission errors: the file may not transfer completely, or there may be a discrepancy between how the file is read on the source and target. If the file does not transfer completely, Shuttle will reject it and re-try the transfer.
- Write errors: an example of a write error is that some cloud providers place a limit on the number of bytes in a single file or in the total bytes in the account. If you try to transfer a file to that cloud provider that is too big, you will generate a write error.
The table below describes some of the errors you may see in the Job Log:
| Error | Description |
EBUSY, Process cannot access the file because it is being used
by another process. |
File is open or in use by an application. Close the file or application to clear the error. This error can also occur if the file was open during a system event such as a computer crash or power outage, and the file did not have time to close gracefully. |
EPERM, Access Denied, Digital Millennium Copyright Act
|
These are all different permissions errors. The user must resolve the permissions issue on the source to transfer the file. |
ENOENT, ENOTFOUND, Not found, Unable to verify that the selected
item <path> exists on job source
|
This error means the file was not found, and can occur if the file was deleted from the source while the migration is in progress. If you did not delete the file, contact Shuttle Support. |
ENOSPC |
When this error is for a Windows source or target, the disk drive on which your Windows app is installed is full. You will need to move some of the data off your Windows drive to continue the job. |
Size-exceeded |
Some cloud providers place limits on the max size of any single file that can be uploaded, or the max data that the account can hold. If you exceed these limits, you will get an error in the Event Log. Sometimes you can resolve these errors by upgrading your cloud provider account; consult them for details. Your other alternative is to split the file up into smaller components. |
Flow stalled, transfer stalled |
This error results when there is a delay in the flow of data between source and target for any number of reasons: disruption in communication, a server event, or edge cases related to variations in file size. Contact Shuttle Support for resolution. |
Peer Connection Lost, Failed to register DirectPath Peer |
This indicates a loss of connectivity between the source and target POPs on your job. If you are using the Windows app in your job, the Windows app’s connection to the Internet may be an issue. Consult Shuttle Support for further information. |
Process terminated abnormally with code 40010004 |
Computer on which the Windows app is installed was forcefully shut down. |
Size mismatch |
This sometimes results when a file is opened and saved while the migration is in progress. In this case, the error message will state byte sizes greater than 0 for the expected and written file sizes. Close the file and run the job again to transfer the file. |
SOCKET, AUTH, ECONNRESET, ECONNREFUSED, Service Not Available, Unrecognized Upload ID
|
These are transient communications errors between the source and target and typically resolve when the job reruns. If they persist, contact Shuttle Support. |
The specified network name is no longer available, Windows cannot
find the network path |
Most common root cause for these errors is inability to access the owner of the file/folder due to permissions. This is a message that Windows returns to Shuttle when that happens. ‘Specified network name…’ is returned for folders, while ‘Windows cannot find…’ is returned for files. These errors may be returned due to other causes, but the most common issue is permissions. |
Unauthorized – User needs to complete email confirmation |
This error appears when a target user on an account mapping run has not responded to their email from the cloud provider to join the corporate account. Ask the user to confirm their account and contact Shuttle support for details on how to clear the error. |
User [username] (email) does not have a provisioned OneDrive |
The user may have a OneDrive account, but they don’t have personal space to write data to. Accounts can be bulk provisioned with scripts; contact Microsoft for details. |
JobImportant: ID: ### and JobRestart: ID: ### in OneDrive and Sharepoint migrations |
Shuttle moves data to the Azure layer of your Microsoft account, but Microsoft must move the file to your OneDrive or Sharepoint account. Microsoft then sends a response to Shuttle if the file transfer has completed successfully. If the file transfer fails, Microsoft sends the messages at left back to Shuttle, and Shuttle will retry the file. This message is benign except that the Microsoft failures can slow down the job. These are Microsoft errors and not Shuttle errors. |
Unable to get owner information for |
Most of the files affected by this error are hidden or system files that will be filtered out from transfer in the job. Note that this is not necessarily a file that fails to transfer, particularly in a non account mapping job – but Shuttle does not have owner information for that file. |
Additional settings
Filters
Specific report types, such as File System and Report, use the Filters button to activate a side panel you can use to narrow down the results.
Source / Target switcher
Collaborators and Users reports allow you to switch between the source and target files, showing the information as it is on the source or as it will be on the target. These are often similar but not exactly the same. A few examples of how these two options differ:
- Two source users are being merged and their information ends up in one Box account. In this case, the source view would show both users and their counts separately. The target view would show one user and the combined total file size, file, and folder counts.
- Some content is skipped and will not be transferred to Box. In this case, the source view would show more files and folders than the target view.
- One or more collaborators are skipped. In this case, the source view would show both collaborators, and the target view would not show any skipped collaborators.