>>This is true but what I don't get is this runs fine as long as it is not a service. But bombs on a copy file command as a service, even though the account it is using is mine!
>
>Well, I had that situation as well. In my case, the NET command, of whatever the command was, to connect to the other drive was not effective. :) Don't know if this is the case here.

It is definitely a permissions problem. If I run it from the command line the file is copied just fine. But as a service it throws an error.

I guess I don't understand exactly how services work. If I am running this service under my login, should it not have the same permissions as if I were running it from the command line?