Source: NCP Engine
Explanation: The NCP engine could not find the file because the client requested file directory does not exist, or the logged-in user does not have sufficient privileges to rename or move the file.
Action: If you know the file exists, check the path and file name, ensure that the user is a trustee for the path with at least the Read right and File Scan right, and ensure the user has an authenticated connection to the server. For a clustered volume, ensure that you specify the virtual server for the cluster resource instead of the physical server in the share path.