Event Log

About the Event Log

The Event Log lists the key events in running your system:  starting and completing jobs, upgrading POPs, and system errors.   You can apply a search filter, such as the name of a specific job, in the Search Log field, and you can export the Event Log to a CSV file by selecting the Export button.  An event log is also available for each job by going to the reporting section for that job:  Analysis, Simulation, or History (the last of these is for transfer runs).

Event Log Messages Guide

1: Many of the events in the event log relate to normal actions the execute during your job. Some of these are:

A: Job validating and startup:
Obtaining file lists from the target…
Obtaining file lists from the source…
Source file list obtained for directory ‘/DIR_NAME’; 14301 files; 4917 directories

B: Job Processing:
Scanning completed in 221.171 seconds
Diffing completed in 221.871 seconds

C: Job Completion:
Extraction is complete. 17808 files have been delivered to loader.
17808 files transferred, 2187 already in sync, 5 skipped files due to newer target

Event Log Errors

1: In the course of transferring thousands of files over long distances, errors will sometimes occur during your job. They fall into several categories:

  • Read / transmit errors: the file may have a permissions issue, it may be open, or the file may be copy protected. Read errors typically require user intervention – such as 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, CFP 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.

2: The table below describes some of the errors you may see in the CFP Event Log:

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 Millenium 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 Tervela 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 Tervela 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 Tervela 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 re-runs. If they persist, contact Tervela 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 to access the owner of the file/folder due to permissions. This is a message that Windows returns to CFP 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 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 Tervela 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: ### – OneDrive and Sharepoint migrations CFP 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 CFP if the file transfer has completed successfully. If the file transfer fails, Microsoft sends the messages at left back to CFP, and CFP will retry the file. This message is benign except that the Microsoft failures can slow down the job. These are Microsoft errors and not CFP errors.
Unable to get owner information for ‘/path/file.ext’: failed to get security descriptor: EPERM – Access is denied. 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 CFP does not have owner information for that file.
It’s possible that the user the Winapp is running as can read the file contents but not the security-related metadata (owner, ACLs, etc.) It may be due to a file that is unreadable. In any event, it is indicative of insufficient permissions.
Updated on November 1, 2021

Related Articles