Is the goal to return an image file to the client, without any HTML?  If so then create a streaming stored process and use this exact code (no STPBEGIN/END) with SAS/GRAPH procedures:   goptions devide=png gsfname=_webout; proc gchart data=sashelp.class; vbar age / discrete; run; quit;   Use this exact code (no STPBEGIN/END) with SG procedures:   ods graphics on / imagefmt=png; filename temp temp; ods _all_ close; ods html file=temp gpath=_webout; proc sgplot data=sashelp.class; hbar age; run; quit; ods html close;   Vince DelGobbo SAS R&D ... View more

Hi Nik, Thanks for the link and the post. Your method gives me some really good options for my reports, and the .js static file suggestion should save a lot of work! Thanks again! Nathan ... View more

Thanks, @SimonDawson (good guess on the customer), but it there a complete, definitive list available? ... View more

Hi @MariaD,   thanks for that.   I was not refering, per-se, to just using too much RAM or CPU, my excuses for my poor explanation. Please let me provide further explanation. SAS Stored Process Server and SAS Pooled Workspace Server do work with pools of connections, right? With a limited size. The pool can handle also more sessions that the size of the queue, because they will be put in the queue. But this queue has limits too.  If the limit is reached, you will basically see that no more sessions of that kind of SAS server can be launched. But it could be also that the Object Spawner cannont launch more sessions of any kind, for that Object Spawner, affecting other SAS server sessions.   And this is what it could happen, as example, if you have long STP or PWKS sessions, you have a pool of, say, 4 or 8 simultaneus SAS jobs. If more jobs are coming in while the running ones have not finish, and you push this queue enough, the spawner will find the trouble.   Also, the ulimits, is worth to check indeed. But since you are telling me only about pooled sessions, I can guess ulimits won't be the only thing to fine tune. But extending the pools sizes/settings.   A final note: if you change the pool settings, you would need to restart the Object Spawners to ensure th new settings from metadata are taken in effect. ... View more

FYI -   We made a good progress on this. However certain services such as the operating systems services, OLAP server, content server etc..are trying to connect through hostname and traffic is only allowed through ELB and NGNIX. If we modify their connection property within the SMC by replacing the hostname with the ELB name then it works but I don't think that is a SAS recommended way of configuring the environment.    Any comments? ... View more

This behaviour is why we initially built the interface in ESM that allows admins to delegate the OS-level session management to power users, while auditing any OS-level intervention. It can often unfreeze the UI while keeping the appserver clean of zombies and old sasworks, especially with less recent versions of EG.   Another feature we put in on a whim, but our EG-heavy clients love is the ability to terminate a disconnected session while keeping its SASWork intact, so that they can copy their old SASWork over to the SASWork for their new session and resume their EG projects from an intermediate task rather than starting again.  ... View more

The CPU cost of the query at the SQL Server side is not included here, only your SAS session. This note indicates that it took 3 mins (elapsed time) for SQL Server to execute the query, and a couple of seconds of CPU time for SAS to write the data back.         ... View more

How long do your services take to execute? Is it anywhere near 5 minutes?   Have you already tried restarting your WebAppServer? ... View more

Thanks everyone. I'll roll out a open source server on the machine for now and lock it down that way.    We're going to have either an Oracle or SQL server with the data and use SAS via ODBC connections to the DB which should give us the row level auditing I need. That's what my IT team is saying at least, that's not my role fortunately 🙂 ... View more

Unfortunately the suggested approach of reinstalling the metadata server SASHOME and copying the configuration directory over to the new machine is not supported.  Replication of SAS environments or parts of SAS environments must conform to the same standards documented in the SAS Disaster Recovery Policy and Update Host Name References documentation.   https://support.sas.com/en/technical-support/services-policies/disaster-recovery-policy.html   http://go.documentation.sas.com/?docsetId=bisag&docsetTarget=n0zdcqxsmd21wtn17vt0w2prek90.htm&docsetVersion=9.4&locale=en   While the plan to reinstall SASHOME is good in that the SAS Deployment Wizard will be run to make sure some of the checks are done it still fails to provide a SAS environment which will not only run but is supportable and maintainable.  Tasks such as applying hotfixes, applying maintenance and being able to migrate the environment often fail in these scenarios and often there is no method to recover from those failures.  Even from the perspective of running, the SAS Backup and Recovery Tool and SAS Environment Manager fail to function in environments repaired using techniques such as this.   Since unfortunately there are no backups of the metadata server the two supported choices here are to perform a complete new deployment using either a SAS Migration Utility package or promotion after the new environment is installed.   Here is what I encourage customer to do before performing updates of their Unix SAS environment.  These suggestions can also be incorporated into your backup and recover plan for your SAS environment.  It is imperative that you have operating system level backups done using a method that preserves the original date/time stamps, ownership and permissions of the files/directories in your SAS environment.  You need a backup of every SASHOME and SAS Configuration directory for every tier of your environment which were taken during the same outage window with all the SAS servers and processes stopped. The backups must be in sync because you will possibly need to restore all the tiers if you have unresolvable problems during your deployment. If you do not have these backups then a reinstall of the environment will likely have to be done.   Thanks, Doug SAS Unix Systems Technical Support ... View more