Search results

Thanks. But I think you mis-spelt "database" . . . :rolleyes:

All the other scheduled tasks run on this server have no issues, it's only this progress one which is problematic. Hence why I think it's Progress related. Frustrating as hell - how hard should it be to extract some lousy data from a database using a scheduled task...

There's no UNC paths involved, I've moved it all to local drives (thought that might be an issue too, but I can rule that out). I've got the output of the environmental variables that exist when running as a scheduled task when not logged on. There were a handful of differences, but none that...

The service account has output rights, so that's not causing the problem. If I try to run the script with my credentials it works, but only if I'm logged into the server: running it as a scheduled task gives me output only if I'm logged into the server on which the task is set. If I'm not logged...

OK, a bit more detail: The batch script is running _progres.exe, and passing it the path to the pf file for the DB, and the path to the .p script to be run. That make it any easier for anyone to help?

Hi I'm not sure if this is a Progress problem, or a Windows problem, but I'll try and see what I get anyway. I've got a batch file which is running a progress script, and dumping out a text file, and it works fine. I'm running this on a Windows 2003 server, and I've got a service account for...