The information in the article applies to all versions of Prism Deploy.
Common Reasons for Error 1600 “Task file not found”
§ The location of the Package is invalid on the target system. Are you using a mapped drive (E:\Packages\package.pwc) or are you using a UNC path (\\server\share\package.pwc)? You can use a drive mapping, but you must make sure that the target systems have that exact drive mapping.
§ The Task has been assigned to run unattended as the current user. In this case, the Task will run as the local system account. Because the local system account doesn't have rights to network shares (unless you've configured NullSessionShares), the Task will fail with error 1600. If you configure a Task to run unattended and you specify a user account for the Task, make sure the user account you've specified has rights to the network location of the Task.
§ Are you using a workstation OS rather than a server OS? Workstations are subject to a 10-concurrent connection limit. If more than 10 clients are trying to access the share at the same time, connections will be denied, resulting in error 1600.