B
BakerTaylor
I recently converted to Windows 10. I had a number of jobs in Task Scheduler that ran successfully on Windows 7. The jobs call a SAS command, execute a job from that application, and write a log. They do not run in Windows 10 via the task scheduler, though all run successfully from the command prompt. I found that converting all of the jobs to batch files helped - but I still cannot run any job that exists, reads from, or writes to a network drive.
I receive the error: 2020-01-29T08:33:58,266 INFO JobMon: PROC | 0 | 2020-01-29 08:33:58,252 | 2020-01-29 08:33:58,267 | ERROR | DATAFLOW_2 | 10
ata Job 3 | Failed to launch child 'C:\Program Files\SASHome\DataFluxDataManagementStudio\2.5\bin\..\bin\dfwfproc.exe' (CreateProcess failed with error 5 (Access is denied. )).
This is for a job that exists on a shared network drive. However, if I move the job to my C drive and change everything within the job to read and write on C, the job runs. This is not a SAS issue as I have verified with their tech support.
As I said, these all ran successfully on Windows 7. What changed to cause them to all fail on Windows 10. I already tested ending the Runtime Broker as suggested by your support chat and it did nothing.
Continue reading...
I receive the error: 2020-01-29T08:33:58,266 INFO JobMon: PROC | 0 | 2020-01-29 08:33:58,252 | 2020-01-29 08:33:58,267 | ERROR | DATAFLOW_2 | 10
ata Job 3 | Failed to launch child 'C:\Program Files\SASHome\DataFluxDataManagementStudio\2.5\bin\..\bin\dfwfproc.exe' (CreateProcess failed with error 5 (Access is denied. )).This is for a job that exists on a shared network drive. However, if I move the job to my C drive and change everything within the job to read and write on C, the job runs. This is not a SAS issue as I have verified with their tech support.
As I said, these all ran successfully on Windows 7. What changed to cause them to all fail on Windows 10. I already tested ending the Runtime Broker as suggested by your support chat and it did nothing.
Continue reading...