Issue launching SAS Studio in Viya: Unable to create compute server session. Failed to launch proces

[NEEA_MIA]

We just ran an upgrade and installed some patches in Viya (3.4) and when it came back online, we couldn't get into SAS Studio, getting the error below. It was working fine before.

If the screenshot isn't easy to read, the text says: "There was an error while starting SAS® Studio. Unable to create compute server session. Failed to launch process. Failed to launch process: host=vSASviya.inhouse.nwalliance.org port=53230 ssl=false Failed to connect to server. A valid authentication credential could not be found."

We are able to access everything else in Viya. When looking in Environment Manager, the launcher-server is running, so it appears that maybe authentification was reset, but can't seem to find how to resolve or where to troubleshoot this.

Thanks,

Aaron James

Northwest Energy Efficiency Alliance

[SASKiwi]

This is going to take some further diagnosing, so you would be best to open a track with Tech Support if you haven't already.

[NEEA_MIA]

Thanks for the response. We have opened a track with Tech Support and are waiting to hear back.

I wasn't sure if someone had any similar experiences and if there were any particular areas we should look at to diagnose. Since everything was working fine before, I suspect that it is likely a configuration that was missed, but not sure what that would be.

[gwootton]

The log for the compute service, launcher service and launcher server might have some more detail on the failure. The error has to do with host authentication. Typically when you log in to Viya you use a user / password to get an authentication token from SAS Logon after it uses the supplied credentials against your LDAP server. When you ask for a compute server, those same credentials are used to try to own a process on the host. This type of failure can occur if those credentials don't work on the host, and the user does not have credentials stored to perform that host level authentication.

[thesasuser]

Hello @NEEA_MIA 
Once you are able to resolve the issue please do share the steps on this post.

[Jacek_Velobank]

Spoiler

Similar problem.

Solution was recreating credentials in Environment Managers and choosing valid groups and valid local username.

Like here, I guess

https://go.documentation.sas.com/doc/en/calcdc/3.5/calcredentials/n1tfaj0ycsd1xsn14hyhso38530t.htm