from SAS® 9.2 Intelligence Platform Desktop Application Administration Guide at support.sas.com:
When you create a connection profile, the Connection Profile Wizard provides, by default, a check box named Save user ID and password in this profile. If a user selects this check box, then the user’s ID and password are stored in the user’s connection profile on the local file system. Saving the ID and password in the profile allows users to reconnect in the future without entering these values again.
Follow these steps to remove the Save user ID and password in this profile check box from the Connection Profile Wizard and require the manual entry of credentials:
- On the host of the SAS Metadata Server, open in a text editor the file omaconfig.xml.
- Change the value of the option SASSEC_LOCAL_PW_SAVE from 1 (or Y or T) to 0 (or N or F).
- Save and close the file.
- Restart the SAS Metadata Server as directed in the SAS Intelligence Platform: System Administration Guide.
After you change the setting for this option and restart the metadata server, each client uses the previous setting for its first connection. The client then discovers the revised setting and conforms to that revised setting for subsequent connections.
If you change the setting to disallow saved credentials, and credentials are already present in a user’s connection profile, those credentials must be manually removed.
The original SAS Enterprise Guide 4.1 expiration date is December 1st of this year. SAS Enterprise Guide 4.1 customers who have not applied the SAS Enterprise Guide hot fix 41EG09wn or later will be affected. The workaround is to download and apply the latest hot fix:
SAS Enterprise Guide die dates and extensions are documented in the SAS Note 33359:
SAS released Hot Fix A53007 for Enterprise Guide 4.22 on June 29, 2010. This Hot Fix applies to 32-bit and 64-bit versions of Microsoft Windows. The Hot Fix address two issues, including:
- Issue 38357 – SAS stored process might fail to run when the language is set to Norwegian
- Issue 40130 – Errors might occur running a project after migration in SAS Enterprise Guide
You can obtain more details at the SAS Enterprise Guide 4.22 Hot Fix Downloads page at http://ftp.sas.com/techsup/download/hotfix/HF2/A53.html#A53007.
I had been using SAS Enterprise Guide 4.22 for months without any crashes, but in May I installed the SAS Hot Fix A53005 primarily because it was available. After installation of the Hot Fix, whenever I attempted to run the Create Format task, even in a brand new project, I received the following error:
SAS Enterprise Guide has encountered a problem. We recommend that you save your work and restart SAS Enterprise Guide.
I submitted a ticket to SAS Tech Support, and for SAS, it took a relatively long time to get resolved. Tech Support had to forward the issue on to the Development Team, who determined that the hot fix (and A53003 before it) relied on a patched version of the Microsoft Visual C++ runtime. The patched version of the runtime was used because it fixed a security hole in ATL (Active Template Library).
Tech Support sent me the link for the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update (http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en), and when I applied the update to my system, the Create Format task worked fine.
from Chris Hemendinger, senior software manager in SAS R&D and author of The SAS Dummy
Supported Versions and Combinations:
- You can use EG 4.1 with local SAS 9.2 (no metadata server). Everything local on your Windows machine; it should just work.
- You can have both EG 4.1 and EG 4.2 on your local machine, along with local SAS 9.2, and all should work together.
- You can have SAS 9.1.3 and SAS 9.2 on your local machine, but EG (either version) will use only the version of SAS that is registered for local use, which is usually the version that was installed last. You can run "sas /regserver" to register a particular version of SAS.
- You can have SAS 9.1.3 and SAS 9.2 side-by-side on a server machine with two metadata servers (one 9.1.3 and one 9.2) and object spawner instances, as long as you assign unique ports for the metadata server and workspace servers. So in this way, you could point EG 4.1 at the SAS 9.1.3 instance, and EG 4.2 at the SAS 9.2 instance. This approach might be helpful for transitioning.
Unsupported Versions and Combinations:
- You cannot use EG 4.1 with remote SAS 9.2, nor can you connect to a SAS 9.2 metadata server. The SAS 9.2 metadata server has a different API that EG 4.1 doesn’t speak.
- You cannot use EG 4.2 with SAS 9.1.3 at all: EG 4.2 relies on some new features within SAS 9.2 that aren’t compatible with SAS 9.1.3 (ODS Graphics and some new APIs).
A strong point of SAS Enterprise Guide is that it interacts seamlessly with many data types using the Microsoft Jet Engine (Excel .xls, Access .mdb, dBase .dbf, Lotus.wk?, Paradox .db, and text files .txt .csv etc). To provide even more flexibility, there are also a few different ways in Enterprise Guide to output data to Excel. A user can export their data to Excel, export to Excel as a step in a project, or they can right-click on a data set and select Send To –> Microsoft Excel. The latter is a convenient feature that many users are comfortable with, but in Enterprise Guide 4.1, your results might not be what you expect.
One data set that we were working with included a date variable which was stored as a DATE9. format. A user complained that every time she exported the data it ended up in DATETIME format, and all of the zeroes from the time complicated her project. I tried to replicate her problem many times by exporting the same data set into Excel and I ended up with DATE9. every time. I finally asked her to send screen shots of what she was doing, and noticed what she called “export” was actually using “Send To –> Microsoft Excel”. I explained that to get the results she wanted, she needed to use the “real” export technique. After I solved this problem, I browsed to support.sas.com and sure enough, SAS had already identified this issue in Microsoft Excel might not maintain date formats in SAS Enterprise Guide. Apparently this issue is fixed in Enterprise Guide 4.2 but I have not tested it yet.
I was one of the unfortunate ones who was unable to attend the SAS Global Forum in Seattle last week. Thanks to discussion forums, blogs, and Twitter, I was able to keep up with a lot that was going on. I was particularly interested in some of the new features that will be available in the next version (4.3) of Enterprise Guide, which is scheduled to be available this summer. Below are some of the features that were mentioned:
- context sensitive keyword completion (syntax suggestion)
- relative file addressing
- code reverse engineering (see what old code is doing)
- an autoexec process flow for projects (runs automatically when project is opened)
- code analyzer (reads a program and turns it into a process flow)
I also had the opportunity to preview some of the new features in the upcoming version of Web Report Studio (4.3). SAS is expanding drag and drop capabilities, which makes creation of report even easier. The biggest news though is the ability to use more than one data source in a report section!
SAS recently released Hotfix 41EG14 for Enterprise Guide 4.1. The hotfix resolves issues identified in:
- Problem Note 39149: The SAS Enterprise Guide editor’s width of caret position panel within the status bar does not accommodate for large row and column number schemes
- Problem Note 38003: Unable to edit existing parameter in SAS® Enterprise Guide®
Enterprise Guide 4.1 Hot Fix 41EG14 (406)
The following considerations apply to SAS Enterprise Guide 4.2 customers who have used SAS Enterprise Guide 4.1 or earlier releases.
- Support for SAS Enterprise Guide repositories has been discontinued; all metadata must be stored in a SAS Metadata Repository.
- Servers are no longer administered through SAS Enterprise Guide Explorer, and must now be administered using SAS Management Console. For information about administering servers, see the online Help for SAS Management Console.
- Users and user groups are no longer administered through SAS Enterprise Guide Explorer, and must now be administered using SAS Management Console. For information about administering users, see the online Help for SAS Management Console.
- The project format has changed from earlier releases. To change the format, you must either open each project in SAS Enterprise Guide 4.2 or use the Migration Wizard for SAS Enterprise Guide and the SAS Add-In for Microsoft Office. You must also use the migration wizard to import the metadata changes that occurred during the BI migration from SAS 9.1.3 to SAS 9.2. For more information, see "Using the Migration Wizard" in Administering SAS Enterprise Guide.
- Tasks are no longer enabled or disabled for user groups, so any task assignments for SAS Enterprise Guide users are not maintained. Any restrictions on SAS Enterprise Guide tasks must be made through roles, and administered through SAS Management Console. For information about using roles in SAS Enterprise Guide, see "Administering Role-Based Settings" in Administering SAS Enterprise Guide and the online Help for SAS Management Console.
I’m currently attending Querying and Reporting Using SAS Enterprise Guide training at the SAS office in Austin, TX. I’m a veteran at using Enterprise Guide, but SAS has great training courses and you always pick up a lot of worthwhile information when you are lucky enough to attend. One tidbit that was covered yesterday that I think is worth passing on is how to prevent the procedure title from displaying when you create reports in EG.
To remove THE FREQ PROCEDURE (or any procedure used in your project) title from your report, go to Tools –> Options –> Tasks –> Tasks General and uncheck “Include SAS Procedure Titles in Results”. This is a global setting, so the titles will not appear in any project’s output unless you check the box again.