Unable to Transfer Files because of Access Violation Error - Search Again

SUMMARY

When I transfer files using standard drag and drop, Clone Folder or an Xchange Agent, I receive an Access Violation error and the transfer stops. What is this error and how can I get my files transferred?

SOLUTION

This message can happen for a variety of reasons. An Access Violation can occur during a transfer if:

• The file you are trying to copy or synchronize is on a mapped drive and you do not have the appropriate network permissions.

Talk to your System or Network Administrator to receive the necessary network access permissions. We recommend that you have read, write and delete permissions. This will allow LapLink to use all of its file transfer features.


• The file you are trying to copy or synchronize may be protected or is unshared.


If you are using Windows NT or Windows 2000, you may have changed the file properties to protect or encrypt the file. Change the file properties to unprotect or share the file.


• The file you are trying to copy or synchronize is open or in use by another user.



• The file will need to be closed. For example, if you are trying to copy an Excel spreadsheet, the spreadsheet can't be open in Excel.



• The file you are trying to copy or synchronize is in use by Windows, a program or a system service.


Sometimes a program, such as Excel, keeps a temporary copy of the file open that causes this error. Close the program and try the transfer again.
If the file is a Windows file or is used by a Windows service and cannot be closed, LapLink will not be able to transfer the file.

Related Articles

ACT! Database Synchronizing Using LapLink    Daylight Savings Time Changes Causes Conflicts in Xchange Agents and File Transfers    Error Message: Access Denied when using an Xchange Agent    Error Message: Computer Errors to a Blue Screen when Transferring via the Serial Network Cable    How do I Copy Hidden Files? What are Protected Files?    How to Copy AutoCad Files using LapLink

Last updated: Thursday, August 30, 2001

Article #70

Legacy Article #2052