topic Re: Error running a sas 9.3 batch program in SAS Programming

Error running a sas 9.3 batch program

htzcouto — Thu, 09 Nov 2017 12:03:07 GMT

I am trying to run a sas 9.3 batch program and there is the following error

insufficient authorization to access c:\Windows\system32

Thanks for the solution,

Re: Error running a sas 9.3 batch program

Kurt_Bremser — Thu, 09 Nov 2017 12:19:39 GMT

When reporting problems, make it a point to always include the complete log of the failed step(s).

In the case of a failed batch run, make sure that all necessary files (source, log, output) are specified with a full path that you have permission to use.

How are you running your batch program? (cmd window, batch file, powershell, VB script, scheduler)

Re: Error running a sas 9.3 batch program

htzcouto — Thu, 09 Nov 2017 12:26:11 GMT

This is the batch program

"c:\Program Files\SASHome\x86\SASFoundation\9.3\sas.exe" -sysin
"C:\Teste_Batch\prog1.sas"
-PRINT "C:\Teste_Batch\prog1.LST" -LOG "C:\Teste_Batch\prog1.LOG"

This is the message returned:

NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead.
NOTE: All profile changes will be lost at the end of the session.
ERROR: Insufficient authorization to access C:\Windows\system32\prog1.log.

Re: Error running a sas 9.3 batch program

Kurt_Bremser — Thu, 09 Nov 2017 13:57:20 GMT

To quote myself:

"How are you running your batch program? (cmd window, batch file, powershell, VB script, scheduler)"

Re: Error running a sas 9.3 batch program

htzcouto — Thu, 09 Nov 2017 13:59:54 GMT

Windows 7 Professional

Re: Error running a sas 9.3 batch program

htzcouto — Thu, 09 Nov 2017 14:02:33 GMT

Using Windows 7 with Task Scheduler

Re: Error running a sas 9.3 batch program

Kurt_Bremser — Thu, 09 Nov 2017 14:03:00 GMT

I give up.

Re: Error running a sas 9.3 batch program

Quentin — Fri, 02 Feb 2018 15:39:54 GMT

I just hit a similar error. In my case it was because I did not include the -log option, and it looks like when a scheduled task runs as administrator, it writes the log to c:\WINDOWS\system32. I would double check that your -log option is in the command string.