Thank you, My EG version is 8.2 ... View more

UPDATE:  Apologies, I totally missed @jwilson's response that did the same thing as what I tried below.  Thank you for the details.  That worked for me for now.   I may have found a solution, but I'm sure it will return at some point because I'm already starting to see some hanging and occasional crashing when undocking coding tabs. I renamed sas folders with "_old" at the end in the following locations: C:\ProgramData C:\Users\<user>\Appdata\local C:\Users\<user>\Roaming I restarted the remote computer then opened SAS EG to rebuild those folders.  It stopped crashing.  Again, how long it will last given I'm already noticing one-off crashes and freezes.   ... View more

@jwilson  - Can you give some idea of how many datasets it takes before your EG users experience "unacceptable" slowness and how long do these programs run for overall?    I'd suggest that if user jobs take over 30 minutes to run or output hundreds of datasets or are run on a regular basis then you should consider running these as batch jobs which will obviously remove any EG overheads entirely. In my experience, providing power users SAS Management Console so they can easily create and run their own batch jobs is well worth the effort.   Also it might be worth engaging SAS Tech Support to do more analysis on EG performance bottlenecks.   ... View more

Hello @jwilson  Whenever there is an abnormal termination of an EG session the work folder is indeed not deleted. When you are restarting your local machine wit EG open, the OS would send a terminate signal to your application. The EG session is having a forced termination. That is why your session is terminated. Did you check the metadata server / object spawner logs? You are greeted for recovering auto saved session because this is saved locally. You can reproduce abnormal termination by powering off the machine. ... View more

If you are also getting a 403 response from workload orchestrator in the Object Spawner log, I would suggest you look in the Workload Orchestrator log which may have more detail as to why the authentication is failing. Depending on how authentication is configured, workload orchestrator either authenticates against the host or using Kerberos. ... View more

I wonder whether they implemented that strange condition of preventing the reading of the log while it is being written as an artifact of the fact the way your SAS jobs are being run, with all of the logs are being directed to the same place.  Instead of being directed back to the filesystem used by the owner of the program being run, which would presumably already have the proper access roles in place so there is no need worry about the wrong people reading the file while it is being written. ... View more