BookmarkSubscribeRSS Feed
al13pn
Calcite | Level 5

After I have updated to the new SAS enterprise guide version, I keep losing the connection to the current session while running some programs after each other and lose all the datasets that are in Work or other libraries.

 

Error: The connection to the server has been lost.

The size of the datasets are small and I don't think the memory is the issue.
Has anyone got this issue?

8 REPLIES 8
ChrisNZ
Tourmaline | Level 20

SAS EG is extremely  sensitive to network disconnections. That's what's happening here.

It's a known weakness that's never been addressed.

You need a strong network link. If you're using wifi, try using a cable.

 

SAS Studio is very robust in this respect. EG uses SAS IOM to communicate, and I always assumed that that IOM was fragile. Does anyone know whether SAS Studio uses IOM?

Kurt_Bremser
Super User
I am pretty sure that IOM is used in the communication between the web application and compute servers. But even if they don‘t share the same physical computer, the connection will be much more stable, as it‘s usually within a data center.
al13pn
Calcite | Level 5

Thank you for your reply. 
Although, I don't think that the problem is with the connection. Since, I have a strong and reliable network and I also tried with LAN cable and the problem remains. Is there any other reason that could cause this issue? 

Tom
Super User Tom
Super User

@al13pn wrote:

Thank you for your reply. 
Although, I don't think that the problem is with the connection. Since, I have a strong and reliable network and I also tried with LAN cable and the problem remains. Is there any other reason that could cause this issue? 


Is it random? Or does the running the same SAS code cause the connection to be lost?

Make sure your code does not do something silly like executing the ENDSAS statement or setting the ERRORABEND option.

al13pn
Calcite | Level 5

Yes it is random! Some times in the 1st code sometimes in the 5th code in the process. 
No there is no  ENDSAS statement or setting the ERRORABEND in the program. 

 

The program was working perfectly with the previous version of SAS.

AlanC
Barite | Level 11

I doubt it is SAS version; that is probably coincidental. Not necessarily, just a guess.

 

To track it down, I would suggest looking at the network and the processes to eliminate your end of the puzzle.

 

Use procmon and filter it down to the EG process. Use one of the network sniffers (I use Fiddler) and see if something is glitching the network. Both tools are free. 

 

A lot of times these things are caused by additional security or other tools deployed onto machines. It could be some of my demons like Ivanti or CrowdStrike or something along those lines.

https://github.com/savian-net
SASKiwi
PROC Star

Talk to your SAS administrator and ask him to check the SAS metadata server logs for any clues regarding the dropped connections. What is your current EG version?  I too doubt it is an EG version issue otherwise it would be widely reported. 

 

Is it specific to certain programs or does it impact all programs?

andreas_lds
Jade | Level 19

Colleague experiencing the same issue after migrating from EG 7.x to 8.3. There was a hotfix for SAS Integration Tools that could address the issue, still not verified by myself.

hackathon24-white-horiz.png

The 2025 SAS Hackathon Kicks Off on June 11!

Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.

YouTube LinkedIn

Creating Custom Steps in SAS Studio

Check out this tutorial series to learn how to build your own steps in SAS Studio.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 8 replies
  • 1808 views
  • 0 likes
  • 7 in conversation