AnonymousI have this same problem sometimes as well. I have scripts scheduled to run daily on an XP machine. Originally the schedule pointed to a mapped drive. I switched it to the UNC path thinking that the mapped drive was going offline until the first script tried to access it. This seemed to have improved the problem but it still happens randomly. I can go a week without seeing it happening and then the next week it could happen once or a few times. Since the PC is, for whatever reason, unable to see the script the initial time, adding additional error handling into it will not help. Running the scripts locally would most likely resolve the problem, but I would prefer to have them on our shared drive. I have one script that I first launch a batch file to pull the most up to date copy of the script from the shared drive and then run it locally. Since I have Windows XP on this machine, I’ve wondered if upgrading to a newer OS could resolve this but I have not gone this route yet.
Since the problem is so sporadic, trying it on another PC a few times will most likely not return the error.