This is going to be a tough one. Debugging on BCA is not easy.
First thing to try is to runit manually while LOGGED ON to the BCA server. If that doesn’t nelp, you can try adding logging to your macro. Write out to a log file after each step. Put the log file in a location on the BCA server that “survives” after the BCA job is done.
Second, I’ve had difficulties using that CopyAll.Execute method … just too fragile … whether interactive or via BCA. It’s one of the methods I eliminated when developing this whitepaper.
Dwayne Hoffpauir 
(BOB member since 2002-09-19)