I have always set my EG options to open RTF, HTML and PDF file types outside EG. I found that the less EG has to do, the better it runs. ... View more

I don't of any config parameters for session limits, but you could modify the sas.sh script and, like someone said, count the number of current sessions using ps, then only invoke the sas exec command if the limit is under. Either that, or check the LOAD averages, count the number of SASWORK folders, etc. By doing this you can also get the script logic to e-mail an alert to you and/or the SAS developer when this happens. But to my mind, it's not very user friendly. ... View more

This was a concern for us too. We arranged to have a SAS consultant come on site to install and configure SAS V9.2 Base and BI Platform. I believe he even did a practise run at his local SAS HQ before coming onsite. I then sat with the consultant to watch the install process, and all steps were screen-captured into a Word document. This approach is recommended, especially for dealing with the orders, SAS Depot, metadata, deploying any web applications, and testing the install. ... View more

Heh heh. All I'll say is "good luck". What's ESSENTIAL in this exercise is having your absolute best desktop technicians working on the job. Thorough testing of install packages in all situations is a must too (well, duh). ... View more

Yes indeed. Our Websphere start-up can take 10-15 mins...quite short compared to other examples here. But given that 10-15 SAS web applications are being launched in 1 or more containers, you'll find that 3-5 mins for each one will add up significantly. The key thing is to ensure that the scripts to shutdown and start up do so CLEANLY. No left-over processes, no weird errors in the logs, etc. Anything strange needs to be investigated (Google, SAS Notes, SAS track). ... View more

The SAS Deployment Wizard documentation has instructions for creating a silent install. If you can't find the doco, contact Tech Support. You need to launch the Wizard in RECORD mode from the DOS prompt and specify a response file. Then you can run setup.exe with options. This also works with applying a hotfix. The problem we had is that the MS Runtime Components could not always install itself. This crashed the silent install, sometimes causing blue screen of death for the customer. For different Windows O/S you might have to create two response files, one created on each platform. The Wizard should select the correct install files for each O/S, as it would doing it manually. ... View more

What happens when you try to read these files on the operating system, e.g. using shell/command scripts without SAS involved? Also, in your SAS data _null_ step, I'd try reading the files into a dataset without any processing. See how long that takes. ... View more

An update. SAS tech support reproduced the problem and supplied a detailed procedure for changing the timeout parameters and redeploying the web applications. ... View more

Yes we have this problem too in V9.2, BI Platform V4.2, using WebSphere V6.1 (64 bit), TSM3 and TSM2. The timeout occurs 30 mins after login, regardless of activity in the portal. We have a SAS track open, but nothing has worked so far. This is a serious issue, e.g. 3 hour cube training sessions for business staff become rather difficult, and looks bad for the software. I assume IDP is Information Delivery Portal. I have increased the timeout on the portal. No change. Regards Bosch ... View more

Cynthia covered the main points. I'll only add that, traditionally, the /home disk on a UNIX or LINUX server usually has a small amount of space allocated to it. Possibly this area filled up during the PROC PRINT. But a write permission problem seems more likely, since I think you'd still get a partial XLS file if the disk filled up. This behaviour will be O/S platform dependent. ... View more

Our various EG V4.22 problems in Windows XP SP3 seem to stem from installs of Windows that are not consistent. For example, we have more problems installing EG on laptops than desktop machines, for some reason. Older desktop installs caused problems...the fix was to reimage/install Windows (!). I would also contact SAS Tech Support. A key question is: does the problem happen on all installations of EG 4.3 or just yours? With us, the SAS System Requirements Wizard sometimes had problems installing components such as Windows Runtime and/or Microsoft.NET. In some cases there would be a clash during install...this caused Windows to blow up and show the Blue Screen of Death. So my recommendation is to confirm first that EG V4.3 is installed properly. As someone said above, for us uninstalling EG 4.x and removing previous versions and all associated EG folders etc. helped to diagnose the issues. Message was edited by: boschy ... View more

I'll be installing V4.3 in June to see how it runs against our Windows XP SP3 and TSM3 in LINUX dev. ... View more