The example paths in OP's code look sanitized to me and I suspect that the real file names are much longer. I have had these kinds of errors occur at $WORK with mapped network drives in the past and the solution I used then was to simply map another drive letter to a subfolder and access the deeply nested directories that way.