SASApp Server + : When clicked on + in SAS Enterprise Guide - Received an Error

[raj231]

HI, When I click on SASApp+ server in SAS Enterprise Guide I get an error with SDS exception.

I tried to debug by checking the SASApp server permissions and I have the access and the login was successful but the SASApp would not expand in Servers selection.

I tried to check the access for the directory permissions in SAS Configuration and I have the permissions yet it does not expand. 

Please suggest if I'm missing somewhere, thanks

[Kurt_Bremser]

Check the Object Spawner and Workspace Server logs on the server.

SASCONF/Lev1/ObjectSpawner/Logs and SASCONF/SASApp/WorkspaceServer/Logs

[Kurt_Bremser]

Also check for free space in your configuration tree, the WORK location, and your home directory.

[AnandVyas]

If possible, please share the snap of the error message you are getting. It could help us understand the error better and suggest steps to fix the issue.

[raj231]

I have checked but looks like all looks good but still not able to expand SASAPP+

[AnandVyas]

When you aren't able to expand the application server (SASApp) it means that the ID you are using isn't able to spawn a workspace session. Now this could be due to various reasons and is difficult to determine without any error message or snap or log. I would suggest you to check object spawner logs if you have access on whats being logged when you perform this step.

[Kurt_Bremser]

You think that it all looks good, but you should put more eyes to this.

I suggest that you run a tail -f on the Spawner log while you try to start your SASApp, and look at the events added to the log. Stop the tail immediately after your request has failed, and copy/paste what is displayed for further use.

Next, look at the Workspace server logs, and inspect the log from a failed attempt, if such was created at all.

Depending on the criticality of the information contained in the logs, you might consider saving them as .txt files for attaching here, or you open a track with SAS technical support.

[raj231]

Thanks for the details but can you help me as what happens when we try to expand SASApp Server.? The logs look fine with no error in SAS but wanted to know as what does SDS and dosscht and vacrash means?

[Kurt_Bremser]

We need to see the logs, really. Either post them here, or bring them to the attention of SAS TS if you're afraid of making critical information public.

[Sajid01]

Your SAS Administrator should be able to diagnose this.
Quite often users are denied access to connect to servers by making them members of certain groups.

I have the following suggestions. 
1.Please check the metadata server log.
2.Make sure that you are not a member of a group to which access is denied.

[raj231]

Thanks All for your comments. But can you suggest as what happens when SASAPP is expanded. Which security permissions would apply, how does the libraries get assigned? I want to confirm on my understanding. My understandings have been provided in my initial post where all I have checked for access. Any document or explanation would be helpful.

[AnandVyas]

Based on the settings at your site different things could happen when you launch a SAS Session. In a generic way this guide helps to understand SAS Application servers.

https://documentation.sas.com/?docsetId=bisag&docsetTarget=p02g5i3unupca2n164s14wc9obxq.htm&docsetVe...

[Sajid01]

The simplest scenario where this can happen is when a user or group is denied read metadata permissions either specifically or through an ACT.
If you have access to SAS Management Console it's easy to find. Otherwise your SAS Administrator should be able to help.

[jcFranklin]

You asked what happens when SASApp is expanded. When you expand SASApp in Enterprise Guide, you are launching a workspace server session. The only libraries that get assigned at that time, are pre-assigned libraries. They can be pre-assigned in metadata (SAS Management Console) or defined in an autoexec file.