Sas EG throwing unexpected result occurred

[nagaraj1991]

i am getting below error when i use sas eg .If i click on any library i am getting unexpected result error occured error .Saw many posts in sas community but it didn't help .Support team also uninstalled eg and again installed but still didn't work .Admins also has told access everything are perfect 

[Error] The launch of the server process failed because of an invalid or inaccessible SASUSER library.

-------------------------- Technical Information Follows --------------------------

Exception Details:
----------------------------------------
Exception type: SAS.EG.SDS.SDSException
SAS Message: [Error] The launch of the server process failed because of an invalid or inaccessible SASUSER library.

Raw Message: <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">The launch of the server process failed because of an invalid or inaccessible SASUSER library.</SASMessage></Exception></Exceptions>
Source: SAS.EG.SDS.Model
Target Site: SASWorkspace

Stack Trace:
at SAS.EG.SDS.Model.Server.SASWorkspace(Boolean checkWorkspace)
at SAS.EG.SDS.Views.View.DoPopulate(DisplayOperation& op)

Inner Exception Details:
----------------------------------------
Exception type: SAS.EC.Directory.Model.SDSException
SAS Message: [Error] The launch of the server process failed because of an invalid or inaccessible SASUSER library.

Raw Message: <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">The launch of the server process failed because of an invalid or inaccessible SASUSER library.</SASMessage></Exception></Exceptions>
Source: EC.Directory
Target Site: Connect

Inner Exception Details:
----------------------------------------
Exception type: System.Runtime.InteropServices.COMException
SAS Message: [Error] The launch of the server process failed because of an invalid or inaccessible SASUSER library.

Raw Message: <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">The launch of the server process failed because of an invalid or inaccessible SASUSER library.</SASMessage></Exception></Exceptions>
Source: SASObjectManager
Target Site: CreateObjectByLogicalNameAndLogins

Stack Trace:
at SASObjectManager.ObjectFactoryMulti2Class.CreateObjectByLogicalNameAndLogins(String Name, Boolean synchronous, Object pIOMI, String LogicalName, LoginDef pOMRLoginDef, LoginDef pSASLoginDef, String nameValuePairs)
at SAS.EC.Directory.Model.Server.Connect(ConnectionInfo connInfo)

Could anyone please give the solution 

[Kurt_Bremser]

This is the crucial part:

The launch of the server process failed because of an invalid or inaccessible SASUSER library

Make sure that the user-id used in the session has a home directory on the SAS server. If you are in a LDAP environment, simply logging on to the server via SSH should do the trick.

[nagaraj1991]

No curt ,i checked there is  a home folder .now it is throwing different error .

Could not establish a connection to the server on the requested machine.  Verify that the server has been started and that the host and port of the server match the client's connection information.

-------------------------- Technical Information Follows --------------------------

Exception Details:

----------------------------------------

Exception type:  SAS.EG.SDS.SDSException

Message:         Could not establish a connection to the server on the requested machine.  Verify that the server has been started and that the host and port of the server match the client's connection information.

Source:          SAS.EG.SDS.Model

Target Site:     SASWorkspace

Stack Trace:

   at SAS.EG.SDS.Model.Server.SASWorkspace(Boolean checkWorkspace)

   at SAS.EG.SDS.Views.View.DoPopulate(DisplayOperation& op)

Inner Exception Details:

----------------------------------------

Exception type:  SAS.EC.Directory.Model.SDSException

Message:         Could not establish a connection to the server on the requested machine.  Verify that the server has been started and that the host and port of the server match the client's connection information.

Source:          EC.Directory

Target Site:     Connect

Inner Exception Details:

----------------------------------------

Exception type:  System.Runtime.InteropServices.COMException

Message:         Could not establish a connection to the server on the requested machine.  Verify that the server has been started and that the host and port of the server match the client's connection information.

Source:          SASObjectManager

Target Site:     CreateObjectByLogicalNameAndLogins

[jebjur]

The error message indicates that the client machine can't get through to the workspace server port or it is connecting to the wrong machine. Is this only occurring on one client PC, or multiple machines? I would check to see if there is a firewall between the EG client machine and the SAS server and make sure the workspace server port is open. Sometimes a company firewall will have the workspace server port (8591) blocked for communication.

[nagaraj1991]

only some users are facing the issue .How to check the pot is open or not 

[jebjur]

The error that you're seeing:

Exception type: SAS.EC.Directory.Model.SDSException

Message: Could not establish a connection to the server on the requested machine. Verify that the server has been started and that the host and port of the server match the client's connection information

can be the result of a number of things.

Most commonly,
1.) The profile information in Enterprise Guide is incorrect.
2.) The SAS server is down or the object spawner service is not running on the server
3.)Firewall port 8591 is blocked. To verify, try to telnet the workspace server port from the EG client machine to confirm that the workspace server port is not blocked.

Example:
telnet compute1.sas.com 8591

If you need any further assistance, I suggest you contact SAS Technical Support

[nagaraj1991]

Thanks a lot for your quick reply ..before  today 2 or 3 users were facing the issue .so we refreshed the object spawner from sas management console .That created some orphan process .So that made the issue bigger .Now we are checking to kill the process 

My doubt is when we refresh the object spawner i,t was refreshing for long time so we closed the window .After that the issue became more so when we try to connect to server we were getting error about the port is closed .when we checked the object spawner log we found some orphaned server process is running.So don't know what caused the issue .

So what happens actually when we refresh the object spawner .When we get this kind of issue is this a right way to refresh the object spawner ?

or we need to restart the object spawner.sh  from back end 

Please let me know .

I will post the result about today's issue 

[Kurt_Bremser]

When the object spawner "acts up", it's best to kill it completely and start it anew. Otherwise a dead instance might block the listening port(s).

[nagaraj1991]

thanks  kurt for the reply  .we restarted the object spawner and it solved the issue .But still for some users not able to run programs in eg .PORT 8591 IS REJECTING .What can we do for this one .

ObjectSpawner_2018-06-16_auirsfcdi001_54138.log:2018-06-16T14:57:14,140 WARN [00872706] :acoe_sasprd - New client connection (82791) rejected from server port 8591 for user au\gargap. Peer IP address and port are [::ffff:10.13.130.125]:53266 for APPNAME=SAS Enterprise Guide.
ObjectSpawner_2018-06-16_auirsfcdi001_54138.log:2018-06-16T14:57:29,472 WARN [00872708] :acoe_sasprd - New client connection (83193) rejected from server port 8591 for user au\gargap. Peer IP address and port are [::ffff:10.13.130.125]:53268 for APPNAME=SAS Enterprise Guide.

[jebjur]

For the users who can't submit programs in Enterprise Guide, what version of Eguide are they running (Help- About Enterprise Guide). Do they have the same version as the users who can submit programs successfully? 

[nagaraj1991]

version is 7.1,,for others it is working ...Any idea where the sas eg logs will be there 

[jebjur]

I am looking for a more detailed version number, such as 7.11, 7.12, 7.13, etc. There was an issue with Eguide 7.12 that resulted in the same message you are receiving, it was fixed in Eguide 7.13. 

[nagaraj1991]

It is 7.11

[jebjur]

For the users who can't submit programs from Enterprise Guide, have them test their connection to the SAS workspace server with the IT Configuration wizard. The instructions are attached (ignore the instructions for local server). If they get an error, please send the resulting log along with the entire object spawner log and open a track with Technical Support

[andreas_lds]

All users have the necessary file-system-right to access the config-directory of the instance / level?