https://communities.sas.com/t5/SAS-Enterprise-Guide/Kill-sas-exe-created-by-Enterprise-Guide-on-the-server/m-p/2367#M788 Hi,<BR /> <BR /> I have written a sas-program which will run at the start of our nightly batch-process and kills all de sas.exe instances on the server and deletes the corresponding work and util folders.<BR /> <BR /> Is this what you want ??<BR /> <BR /> Regards,<BR /> Henk Fri, 23 Mar 2007 10:32:45 GMT deleted_user 2007-03-23T10:32:45Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Kill-sas-exe-created-by-Enterprise-Guide-on-the-server/m-p/2366#M787 We are using EGuide 4.1 in a Windows Client Server environment (XP - 2003). When EGuide connects with the server a sas.exe is started. When EGuide is stopped, this sas.exe does NOT stop... These sas.exe's take memory and sometimes also cause dead locks on tables. We are 'treating' the problem by killing all sas.exe with a Prc2 directory in there work environment... This is not 'nice'.<BR /> Now, my question: does anybody know of another way of treating this annoying problem? Fri, 23 Feb 2007 12:05:14 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Kill-sas-exe-created-by-Enterprise-Guide-on-the-server/m-p/2366#M787 deleted_user 2007-02-23T12:05:14Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Kill-sas-exe-created-by-Enterprise-Guide-on-the-server/m-p/2367#M788 Hi,<BR /> <BR /> I have written a sas-program which will run at the start of our nightly batch-process and kills all de sas.exe instances on the server and deletes the corresponding work and util folders.<BR /> <BR /> Is this what you want ??<BR /> <BR /> Regards,<BR /> Henk Fri, 23 Mar 2007 10:32:45 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Kill-sas-exe-created-by-Enterprise-Guide-on-the-server/m-p/2367#M788 deleted_user 2007-03-23T10:32:45Z