BookmarkSubscribeRSS Feed
Madhan_cog1
Quartz | Level 8

Hi Team,

 

We have SAS 9.4 M7 Grid Deployed on a Linux 

New user is unable to connect to Workspace Server through SAS Enterprise Guide.

 


[Error] Failed to start the server.
[Error] The launch of the server process failed with an unknown status code.
[Error] The launch of server SASApp - Workspace Server for user failed.

 

Kindly help me to resolve the issue.

 

The issue is only with new user.

 

Thanks,

Madhan M

7 REPLIES 7
anuraagjv
SAS Employee

Check SAS Object Spawner log. The default locations for SAS server logs can be found here: http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#p1ausbmrrybuynn1xnxb...

 

Have the user in question run the following test from the SAS Enterprise Guide machine and send in the results.

WORKSPACE SERVER TEST:

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

- Select 'Start > Programs > SAS > Utilities > Integration Technologies Configuration'

- Test SAS Servers > Next

- Enter a SAS server definition manually > Next

- SAS Workspace Server > Select 'IOM BRIDGE' connection

- Enter the Fully qualified Server Name - Port (the default port # is 8591)

- User's ID and PW

- Test Connection

Madhan_cog1
Quartz | Level 8

Hi,

 

Thanks for the response.

 

I dont find anything wrong in Object Spawner Log

 

2022-08-09T11:45:27,810 INFO [00157511] :svc_rpa_rnd_agent - New client connection (192) accepted from server port 8591 for user svc_rpa_rnd_agent. Encryption level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are [::ffff:10.18.168.88]:23847 for APPNAME=SAS Enterprise Guide.
2022-08-09T11:45:27,854 INFO [00157511] :svc_rpa_rnd_agent - New out call client connection (193) for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.24.16.70]:8561.
2022-08-09T11:45:27,865 INFO [00000010] :sastest - Client connection 193 for user sastrust@saspw closed.
2022-08-09T11:45:27,907 INFO [00157511] :svc_rpa_rnd_agent - New out call client connection (194) for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.24.16.70]:8561.
2022-08-09T11:45:27,958 INFO [00000010] :sastest - Client connection 194 for user sastrust@saspw closed.
2022-08-09T11:45:33,323 INFO [00157511] :sastest - Client connection 192 for user svc_rpa_rnd_agent closed.
2022-08-09T12:01:55,282 INFO [00157649] :svc_rpa_rnd_agent - New client connection (195) accepted from server port 8591 for user svc_rpa_rnd_agent. Encryption level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are [::ffff:10.18.168.88]:23919 for APPNAME=SAS Enterprise Guide.
2022-08-09T12:01:55,332 INFO [00157649] :svc_rpa_rnd_agent - New out call client connection (196) for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.24.16.70]:8561.
2022-08-09T12:01:55,344 INFO [00000010] :sastest - Client connection 196 for user sastrust@saspw closed.
2022-08-09T12:01:55,381 INFO [00157649] :svc_rpa_rnd_agent - New out call client connection (197) for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.24.16.70]:8561.
2022-08-09T12:01:55,438 INFO [00000010] :sastest - Client connection 197 for user sastrust@saspw closed.
2022-08-09T12:02:00,809 INFO [00157649] :sastest - Client connection 195 for user svc_rpa_rnd_agent closed.
2022-08-09T12:02:05,973 INFO [00157695] :svc_rpa_rnd_agent - New client connection (198) accepted from server port 8591 for user svc_rpa_rnd_agent. Encryption level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are [::ffff:10.18.168.88]:23839 for APPNAME=SAS Enterprise Guide.
2022-08-09T12:02:06,015 INFO [00157695] :svc_rpa_rnd_agent - New out call client connection (199) for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.24.16.70]:8561.
2022-08-09T12:02:06,029 INFO [00000010] :sastest - Client connection 199 for user sastrust@saspw closed.
2022-08-09T12:02:06,068 INFO [00157695] :svc_rpa_rnd_agent - New out call client connection (200) for user sastrust@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [10.24.16.70]:8561.
2022-08-09T12:02:06,119 INFO [00000010] :sastest - Client connection 200 for user sastrust@saspw closed.
2022-08-09T12:02:11,450 INFO [00157695] :sastest - Client connection 198 for user svc_rpa_rnd_agent closed.
[sastest@J2IADSASCTL01 AuditLogs]$

 

The user svc_rpa_rnd_agent  is able to connect to metadata but unable to connect to Workspace server.

 

As per you link below.

 

http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#p1ausbmrrybuynn1xnxb...

 

I see page not found.

 

Madhan_cog1_0-1660061188964.png

 

 

Kindly see if you can assist.

 

Thanks,

Madhan M

 

gwootton
SAS Super FREQ
I see you are in the "AuditLogs" path. Are you looking at the Object Spawner log there or in <SASConfig>/Levn/ObjectSpawner/Logs? You should look at the logs in the default Logs directory for WARN and ERROR messages. If you do not have a Logs directory in the Object Spawner directory it may be in <SASConfig>/Levn/Logs.
--
Greg Wootton | Principal Systems Technical Support Engineer
Madhan_cog1
Quartz | Level 8

Hi ,

 

Yes i verified the logs there as well.

 

2022-08-09T12:01:45,402 INFO [00497154] :svc_rpa_rnd_agent - Grid credentials retrieved from authdomain 'DefaultAuth' in metadata.
2022-08-09T12:01:45,403 INFO [00000010] :sastest - Client connection 41354 for user sastrust@saspw closed.
2022-08-09T12:01:45,661 INFO [00497154] :svc_rpa_rnd_agent - Created grid job 1129 using credentials svc_rpa_rnd_agent (child id 34).
2022-08-09T12:01:50,708 ERROR [00497196] :sastest - PROVIDER(SAS): The job failed. Exit code=255.
2022-08-09T12:01:50,728 ERROR [00496803] :sastest - The launch of the server (SASApp - Workspace Server) process failed with an unknown status code (255).
2022-08-09T12:01:50,728 INFO [00496803] :sastest - Grid job 1129 owned by user svc_rpa_rnd_agent (child id 34) has ended.
2022-08-09T12:01:50,728 ERROR [00497154] :svc_rpa_rnd_agent - The launch of server SASApp - Workspace Server for user failed.
2022-08-09T12:01:50,728 INFO [00497154] :sastest - Client connection 41353 for user svc_rpa_rnd_agent closed.

 

Thanks,

Madhan M

 

 

 

 

 

 

 

 

 

anuraagjv
SAS Employee

When we see the error " failed with an unknown status code (255)", usually the failure is due to file permission errors.  If logging for the WorkspaceServer sessions has been enabled, this is a common source of failure if the user(s) are not able to create the logs due to permissions on the directory holding the logs.

 

Other sources would be incorrect permissions to create the WORK library, or, especially in the case of new users, their Unix $HOME directories do not have the correct permissions.

 

One last cause would be that the permissions on the directories in the <SASConfig> path have been set so that the user is not able to access and execute the WorkspaceServer.sh script.

 

One way you could try to figure this out, would be to enable more logging, or you can navigate to your Workspace Server directory (sas/config/Lev1/SASApp/WorkspaceServer) and run ./WorkspaceServer.sh -nodms with the failing userid.

Madhan_cog1
Quartz | Level 8

Hi ,

 

I Executed the ./workspaceserver.sh with failed user login and below is the output.

 

 


NOTE: SAS initialization used:
real time 0.07 seconds
cpu time 0.07 seconds

Group not defined locally. Using GID for restricted options.
NOTE: Libref SASDATA successfully assigned from logical server.
NOTE: Libref STPSAMP successfully assigned from logical server.
ERROR: Libref DAP_DM1 failed to assign from logical server.
ERROR: User does not have appropriate authorization level for library DAP_DM1.
ERROR: Libref OPC14597 failed to assign from logical server.
ERROR: User does not have appropriate authorization level for library
OPC14597.
NOTE: Libref ACM successfully assigned from logical server.
NOTE: Libref ARTIFACT successfully assigned from logical server.
NOTE: Libref EVDM successfully assigned from logical server.
NOTE: Libref KITS successfully assigned from logical server.

NOTE: AUTOEXEC processing beginning; file is
/opt/sas/gridconf/Lev1/SASApp/WorkspaceServer/autoexec.sas.

NOTE: There were 3 observations read from the data set SASHELP.VOPTION.
WHERE optname in ('DMR', 'LOG', 'OBJECTSERVER');
NOTE: DATA statement used (Total process time):
real time 0.01 seconds
cpu time 0.02 seconds

NOTE: DATA statement used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds

NOTE: PROCEDURE| _DISARM| REGISTER| _DISARM|
2022-08-09T15:38:06,628-04:00| _DISARM| WorkspaceServer| _DISARM| SAS|
_DISARM| | _DISARM| | _DISARM| | _DISARM| | _DISARM| | _DISARM| |
_DISARM| | _DISARM| | _DISARM| | _DISARM| | _DISARM| | _DISARM| |
_DISARM| | _ENDDISARM

NOTE: AUTOEXEC processing completed.

 

Thanks,

Madhan M

gwootton
SAS Super FREQ
Did you run it as user svc_rpa_rnd_agent on the host where grid job 1129 was executed?

This message seems to indicate the user is a member of an undefined group (maybe sssd is pulling user information from an external source, but not groups).

"Group not defined locally. Using GID for restricted options."

Do functional users get that message?
--
Greg Wootton | Principal Systems Technical Support Engineer

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 7 replies
  • 1443 views
  • 4 likes
  • 3 in conversation