As already mentioned, SAS Tech Support is your best option to progress this. ... View more

wow - Great! ... it works!  There is a possibility to change and adapt the shortcut. I hope it'll endure a long time. 🙂 Thenk you! -Martin- ... View more

Thank you, Mark, for your answer.   How " to create the job in EG, and then edit the trigger directly in the Windows Scheduler. When scheduling a job, EG just opens the Windows scheduler. " ?   I would like to schedule the task like in this video :Utilisation des fonctionnalités de planification de SAS Enterprise Guide - SAS Video Portal But I don't have this possibility any more :    Thank you for your help ! ... View more

Same issue here. Do you have a link to the patch? ... View more

Hi Alan, I think I understand and agree with your position, however I am not sure that we are aligned on what the problem actually is. I don't and never expect SAS to miraculously work universally or with bad data or poorly crafted code. What I expect (and perhaps this bears repeating) is that SAS is capable of releasing a PC file after an error is encountered/detected by SAS. That is it. Nothing more. It shouldn't take disconnecting from the SAS server or restarting SAS Studio or EG to free the file up. If you're wondering (and I doubt you are) why I am so hung on his issue, well it's three-fold: 1. I can't prevent the Excel files that I import from always being 100% compatible with the PROC IMPORT WHERE clause. I can certainly try (and will), but there is no guarantee it won't happen. 2. Similar to #1, I can't always ensure that the PROC IMPORT WHERE clause will be aligned the filtered column type. The vast majority of the time, they are (aligned). 3. Most of my EG projects are designed to set up the environment macro variables, libraries, etc. based on a user prompt response and other system variables. Each time an external file is lock and I have to disconnect or restart and when I do I lose all of the environment settings; which takes time to reset and present additional opportunity for entry error. No response is required and I very much appreciate you take time out for your day(s) to help me. At this point, I am not looking for a solution cause it sounds like one isn't available (aside from not getting the SAS error) and we can officially close this track. ... View more

Figures. Interestingly, I had never seen the behavior and then it happened to me one afternoon at the SAS Innovate conference. So, I think all that does suggest something in the environment. (Or the gremlin moved from your box to mine!) As best I could tell, the delays I was seeing were simply delays on each network call to the workspace server from EG. There are many calls as connections are made and as code is submitted. So "small" delays on each one do add up. In my case, I was connected using Wi-Fi via VPN cross-country to our servers. When those types of delays occur, it is exceedingly frustrating, both when using EG and when trying to diagnose the cause. I have collected all the logs I have on this issue and am going to continue to look at it as I'm able. My recommendation is that if the problem doesn't return for you, then great. But if it does return, please open a Tech Support ticket and provide them with an EG log and the corresponding workspace server log for a session where the delays occur. Also tell them I requested you do that and to please get me involved in the ticket. Then we can pick it up with less delay. Regards, Mark ... View more

Hi @kevin_stanford - I understand you are frustrated with the lags you are experiencing with EG 8.  Did you open a tech support track? If you do that, and provide tech support with logs for an EG session that shows the lag, I will be able to analyze the log to see if I can determine the cause of the delays.   It is best if a matching set of an EG log and the corresponding Workspace Server log are included.   After the track is opened, I will take a look at the logs.   Mark Allemang ... View more

I'd also suggest checking the Windows Event Viewer, in case there are other errors happening to trigger the EG problem. ... View more

Yes, the /option command line argument should work the same in EG 8.3 and EG 8.4. ... View more

I would Suggest to go to the windows machine that has the SAS Server EG is sonnecting to, and opern sas session up, then while this SAs wondow is open, open another SAS session and see if the same earning is in the second SAS session log window.   The first coarse of action will be to rename the follwing files by adding a file extension of "002" to the end of the following files.   C:\users\<userid>\Documentation\MY SAS files\9.4\profile.sas7bcat C:\users\<userid>\Documentation\MY SAS files\9.4\profile2.sas7bcat C:\users\<userid>\Documentation\MY SAS files\9.4\profbak.sas7bcat C:\users\<userid>\Documentation\MY SAS files\9.4\p\regstry.sas7bcat   Once you have renamed those files then re-start SAS and see if you the same notes and warnings...   Thank you Manjunath  ... View more