I just googled the 1067 error, and it seems to indicate that the service in question (SAS in your case) exited with an exit code <> 0.
My next tries would be
- write a simple .bat that echoes some text into c:\test.txt
- try to run that as a service
- if that works, add the SAS command line in the batch file, capture the exit code immediately after, and echo that to C:\test.txt
- see which exit code came from SAS.
I have to say, though, that I am always astonished by how complicated such simple tasks are in Windows. By $DEITY, am I glad my SAS server runs on UNIX!
... View more