The last couple times that I had an error like this, they was because of a few things:
- The fileserver was leveraging an NFS mount point which was down
- The agent ACL's had gotten "messed up" and files were getting messed up causing permission errors during copy
- The umask setting on our servers had been adjusted due to "server hardening", so files were written correctly as root, but the bladmin ID had no rights to read them.
These may have nothing to do with your situation, or we may get lucky. When you find out what it is, please let us know and I know that I'll add it to my bag of tricks.
is the bldeploy.xml in the location noted on dc1blstore ? are there any error messages in the rscd log on the file server (dc1blstore) when it happens ?