If you have SAS Enterprise Guide and SAS for Windows installed on a machine together, they should Just Work. There is no special setup required. But...what if they don't? This article will help you to determine the cause and then (most importantly) correct it.
Many SAS Enterprise Guide users connect to a managed SAS environment with a SAS Metadata server and remote SAS Workspace server. In order to find that SAS environment, you need to have a metadata profile that tells SAS Enterprise Guide where the SAS Metadata server is. When connected, you'll see an indication in the lower-right corner of the SAS Enterprise Guide status bar:
If you hover your cursor over the magic blue text, you can see the details of the connection:
If you have a local SAS installation, you can use SAS from SAS Enterprise Guide without requiring a SAS Metadata server. This is called "No profile" mode. To select No profile mode, click the blue text in the status bar. The Connections window appears, as shown below. (You can also reach this window by selecting Tools->Connections from the main menu.)
Select "<do not use a profile>", then click Set Active (or simply double-click that top item to set it to active).
Important: make sure that this selection is active -- with the blue connection icon -- before you Close the window; otherwise the selection won't take effect.
In "No profile" mode, you have access to your local SAS server, which is named "Local" in the Server List. All file system references and libraries are defined in terms of your local PC.
Any SAS Enterprise Guide features that rely on SAS metadata will be disabled. These include stored processes, metadata-based libraries, integration with SAS Visual Analytics, and more.
Note: working in "No profile" mode does not mean that you are limited to your local PC for data access and SAS processing. You can still define and access SAS libraries that connect to remote databases (as long as you have the proper SAS/ACCESS products and configuration). You can also submit programs to a remote SAS environment via traditional SAS/CONNECT methods, by submitting SIGNON and RSUBMIT statements. In this scenario, SAS Enterprise Guide is working with your local SAS, which in turn is connecting to a remote SAS session that is running SAS/CONNECT.
If you have access to a remote SAS environment and a local SAS installation, you can use them together in SAS Enterprise Guide. To add your local SAS server into the mix, select the Servers tab from the Connections window:
Check the box for "Automatically add local SAS server (if installed) to server list". When you close the Connections window, the Servers List will be updated to reflect all of your SAS servers, whether Local or defined in SAS metadata:
When you have multiple SAS servers in the mix, you do have to be careful when initiating certain activities. For example, when you create a new SAS program, take a moment to make sure that it's set to run on the server that you intend.
Also, when using the File->Import Data task (or any task that doesn't begin with selecting a SAS-server-based data set), be sure that the target SAS server (where you store the resulting data set) is the location that you intend.
In some cases, you might have a local SAS installation but SAS Enterprise Guide can't detect it. You might see a message such as:
No SAS servers available
A local SAS server was not found and no metadata profile is being used. Without a SAS server you cannot open data or run SAS programs.
Do you want to create or modify your profile information?
SAS Enterprise Guide uses the Windows registry to "discover" where SAS is installed. These registry keys are established when SAS is installed, but sometimes "stuff happens" and the key values go missing.
You can verify what SAS Enterprise Guide detects for your local SAS installation. To check this, select Help->About SAS Enterprise Guide. In the "About" window, click Configuration Details. You'll see this window:
The SAS System version and SAS System Command fields will reflect what SAS Enterprise Guide detects. If the values show as "none", then SAS is either not installed or not registered properly.
If SAS is indeed installed, it's an easy problem to fix, though it's a bit of a technical step. To re-register your local SAS:
You might require elevated privileges on your Windows PC to make this change, since it has the effect of modifying the local machine registry. If your organization limits your local admin privileges, you might need to ask your IT support staff to run this command for you.
Make sure to restart SAS Enterprise Guide in order to pick up the change.