Sometimes when using SAS EG 7.13 I try to run a program and the task status panel shows "Status: Connecting to server". I'm using a local server, connecting to data sets on a network drive. It gets stuck at this point and will not continue. I have tried restarting the PC but this does not help. I have tried multiple programs in different projects and none of them run. If I run the program from another PC it works fine.
What causes this problem and how can I fix it? Thanks in advance.
Ah, that gives us another line to pursue.
Since the SAS instance is on your local machine, when you try to stop a query and it doesn't stop it means that very likely the local SAS instance is still chugging away, which may be consuming TONS of your machines resources.
The next time this happens, try opening Task Manager, and look for the "SAS 9.4 for Windows" (or something similar) background task.End that task, which will kill whatever SAS was doing. When you start up EG the next time, it will start a new SAS task.
Tom
If its working fine on another computer then there must be something different about the setup of your computer that is causing the problem. How do you link to the the network drives where your data is stored? Do you map drive letters or to you point to the drive using a file share like \\MyFileServer\MyFolder?
Fortunately/unfortunately I've returned to work the following day and it's all working now. However, this is a reoccurring problem so I'm still interested in what problem-solving techniques I should be using next time.
To answer your question, although the drives are mapped to a letter, the libname is defined using what you've described as a file share (the path starts with \\). Is one of these ways better than another?
Since EG is just running SAS on your local computer, try bringing up SAS standalone, and see if the log gives you any indications.
Tom
Yes, that's exactly correct. It's just something to rule out.
For example, it used to be the case that if your SAS license had expired, you'd get no information to that effect by starting up EG, but starting up SAS would display a clear message.
Intermittent problems are a royal pain! How often is it happening?
Tom
Ah, that gives us another line to pursue.
Since the SAS instance is on your local machine, when you try to stop a query and it doesn't stop it means that very likely the local SAS instance is still chugging away, which may be consuming TONS of your machines resources.
The next time this happens, try opening Task Manager, and look for the "SAS 9.4 for Windows" (or something similar) background task.End that task, which will kill whatever SAS was doing. When you start up EG the next time, it will start a new SAS task.
Tom
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.