You can create server definitions to SAS® OLAP Servers prior to SAS 9.2 and third-party OLAP servers for use in SAS Enterprise Guide. Private OLAP Server definitions store the connection information required to get to these server types. Once defined, a private OLAP server can cause SAS Enterprise Guide to become unresponsive.

The issue is related to the Data Execution Prevention (DEP) feature in Microsoft Windows Vista and Microsoft Windows 7. DEP limits access by the .NET objects used in the SAS 9.1 and SAS 9.2 OLAP Data Providers. Some third-party OLAP providers also could be affected by this change in the operating system. If you are only accessing SAS 9.2 OLAP cubes, SAS recommends that you connect to the OLAP cube through the OLAP Server option rather than the private OLAP server. For SAS 9.1 users, the workaround is more complex:

1. Delete the private OLAP server definition from File ► Open ► OLAP Cube.
   
2. Close SAS Enterprise Guide.
3. Locate the AppData folder for your environment. See SAS Note 17730 for details on locating the correct folder for your installation.
4. Delete the OpenDlg file from the location in step 3.
5. Open SAS Enterprise Guide.
6. Redefine your private OLAP Server.

This process must be repeated each time the private OLAP server is opened. If possible, SAS recommends using SAS Enterprise Guide 4.1 when connecting to SAS 9.1 OLAP Servers.

Operating System and Release Information

A fix for this issue for SAS Enterprise Guide 4.305 is available at:

A fix for this issue for SAS Add-in for Microsoft Office 4.305 is available at:

A fix for this issue for SAS Enterprise Guide 4.3 is available at: