While executing a build, eMake was asked to send the contents of the specified file to a cluster agent, but eMake was not able to read the file. The system error detail will provide more information about the specific cause of the failure.
Because eMake is interfacing with an external entity (the filesystem on the computer where eMake was invoked), the cause of the error could be just about anything. The system error detail will provide more information about the specific cause of the failure. However, this error generally means either the filesystem has been modified by a third party while eMake was running, or that there is a defect in CloudBees Build Acceleration.
First verify that no process besides eMake is modifying the files used during the build, which can create the inconsistent state that could provoke this error message. If you are sure that no other process has modified the files while eMake is running, contact CloudBees support for assistance.