Just doing a basic XXCopy backup copying all of Drive C to a Shared Drive "R/S/T/U/V" across the network. Each day the destination drive changes, using hard drives vs. tapes for Mon-Fri backups. The problem is not limited to any of the destination drives. All the destination drives are on the same server box. But this seems to be a Run Program> issue, not XXCOPY. If I copy/paste from the Macro Scheduler log into the Command window, the command runs with no problem.
Example of line that does not run:
Code: Select all
Run Program>command.com /c xxcopy C:\*.* T:\Holter /EXC:\Data\Backups\Xxcopy\ExcludeList.txt /backup /CK0 /FF /PB >> C:\Data\Backups\Logs\20050413.log
Scheduled to run at night unattended. They trigger OK, but intermittently come back with an error message box that says "Had trouble running ".... the full string shows up here....."
I have been able to eliminate the error by removing the output that is redirected to the text file. If I drop >>....... I don't get the error. Is there some length limitation for Run Program that I don't know about? Could it be the result of a circular problem because trying to do a backup that includes the destination location in the redirected report?
Some days the scripts run OK, sometimes they come up with the error message. Cannot predict when they will run. I guess I could break up the command line into a couple of variables and send them instead.
Another option is probably to use UNC vs. Mapped Drive Letters.
But I want to understand the problem befote I implement a solution. What is wrong?