BookmarkSubscribeRSS Feed
thiennguyen19x5
Fluorite | Level 6

Please help me with error:

Error: The connection could not be established to a SAS Workspace Server named 'Local' running on port on host 'localhost'.

Please verify the following:
- The correct hostname and port number were specified.
- If a firewall is present, it is correctly configured to allow this access.
- An object spawner has been started on the server.
- The SETINIT on the server is not expired.

Please contact your SAS Administrator if the problem persists.

Server response: Server execution failed

12 REPLIES 12
SASKiwi
PROC Star

Are you connecting to SAS on your PC or a remote SAS server? Is this a first time connection or was it working but now it isn't?

thiennguyen19x5
Fluorite | Level 6
On Pc
And It is working until now. I found the error today
SASKiwi
PROC Star

Can you please update the post as answered then. 

 

EDIT: Oops I misread your post. @ChrisHemedinger 's suggestion is the first thing to check.

ChrisHemedinger
Community Manager

If it was working up until just today, check the license -- did it expire? You would have seen warnings before now, but once the expiration hits, no more warnings -- just failure to connect.

SAS For Dummies 3rd Edition! Check out the new edition, covering SAS 9.4, SAS Viya, and all of the modern ways to use SAS!
thiennguyen19x5
Fluorite | Level 6
No, the license is working, not expired
Patrick
Opal | Level 21

@thiennguyen19x5 wrote:
No, the license is working, not expired

How do you know? How have you checked?

SASKiwi
PROC Star

The easiest way to prove if your SAS software is functioning correctly is to start a traditional SAS session from a Windows program shortcut. Try running one of the SAS 9.4 shortcuts:

SASKiwi_0-1715313062152.png

 

KaueMAlmeida
Obsidian | Level 7

I have faced problems like this sometimes. I'll let a hint here.

 

 The correct hostname and port number were specified.

Check if you have access to the server that you are trying to access to. Maybe you have a valid license to access SAS but don't have access to some servers.

thiennguyen19x5
Fluorite | Level 6

Thank you everyone; I just fixed it.

ghartge
Pyrite | Level 9

Great @thiennguyen19x5 !!! But how? Thanks

ghartge
Pyrite | Level 9

Greetings,

I have six projects open that I run each morning using SAS Enterprise Guide 8.3 64 bit. Yesterday I started a new project and received the error message in this thread's original post. Since my other projects were working, and still are, I modified one of my working projects so I could accomplish the work needed.

-Before changing the original working project I saved it.

-I then began the work I was tasked with for the new project using the functioning project and it executed as intended. I completed that work, saved with a new name, and closed the new project.

-I opened the original saved project that I run daily to execute it this morning and it now gives me the error message seen in this thread. The other projects I run daily are still functioning. They were never closed and reopened. They have remained open on my desktop and connected to "Local".

 

It "seems" that as long as I had/have a project that was open before yesterday it will execute, but if I open/start a project and try to execute it I receive the error message. 

 

Any thoughts on this situation? I have not received any expiration notices or emails about that from SAS.

 

Thank you,

 

Gary

ghartge
Pyrite | Level 9
Our issue seems to have been an incorrect expiration date in our update/renewal files. Files resent from SAS solved the issue.

hackathon24-white-horiz.png

The 2025 SAS Hackathon has begun!

It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.

Latest Updates

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
  • 12 replies
  • 4190 views
  • 1 like
  • 6 in conversation