03-15-2016 11:03 PM
Sometimes when I double-click on a SAS program file, I get an automation error and SAS will not start. I have to kill a 'ghost' sas process which is still running in order to start SAS. The ghost process seems to appear after I've used the Help function within SAS. Any suggestions? (I'm running 9.4TS1M3 on Windows 7 x64).
03-16-2016 04:04 AM
Sounds like this could be an issue for SAS Technical Support.
Did you look if such a failed batch run leaves a log file?
03-16-2016 05:41 AM
So it looks as if the typical SAS batch job execution fails. Since you mentioned a "ghost", could it be that the ghost is already running in the background (because you used the help beforehand?) and confuses Windows into trying to use that SAS process instead of starting a new one cleanly?
Forcing Windows to always start a new SAS process in batch mode will probably involve some tinkering with the registry (ugh).
03-16-2016 06:06 AM
On windows double clicking on a .sas file typically opens SAS up in interactive mode. I'm not trying to run batch. I think the puzzle is why if I quit SAS (after using help), a sas process stays running.
03-16-2016 06:12 AM
I think the puzzle is why if I quit SAS (after using help), a sas process stays running.
If that's your problem, this smells like a case for SAS TS. I won't be of much help here, as I run SAS on UNIX(AIX).