I would suggest enabling workspace server logging as a next step: https://documentation.sas.com/doc/en/bicdc/9.4/bisag/p0atyzdgfzbsjfn1j4bbbt14ic7t.htm Then you can trace the connection using the object spawner log and the workspace server log to see where it is getting hung up at. You want to look at the time stamps. I can see from what you sent that the process is getting created quickly, but we need to know how long it took the client to enter the workspace server session, how long the workspace server took to initialize, and where in the process the hanging is occurring. You can reference my SGF paper to help with tracing the connection and to look at the possible causes: https://www.sas.com/content/dam/SAS/support/en/sas-global-forum-proceedings/2018/2003-2018.pdf ... View more

The error message "The native implementation module for the security package could not be found in the path." is typically related to the configuration of Kerberos delegation.   In the User Managment Console in Active Directory > Delegation Tab, for the SPN entry is the "trust this user for delegation to any service (kerberos only)" check box selected? ... View more

The error you are getting is coming from the postgres database.    Have you tried deleting the compute context using EV yet?  https://go.documentation.sas.com/doc/en/calcdc/3.5/calcontexts/n03002viyaprgmsrvs00000admin.htm    ... View more

There are timeouts that can be set in the SAS 9 environment, like the following:    You can set an inactive client timeout on the logical application servers that will disconnect clients after X amount of time if the connection is sitting idle: Force Servers to Disconnect Idle Clients   There is also a launch timeout that can be set for load balanced application servers to allow X amount of time to wait for the server to startup before failing due to exceeding that wait time.  ... View more

The message you're receiving generally indicates a metadata authorization problem. That is, the user account does not have WriteMetadata to an object. Check first if the identity has WriteMetadata to the SASApp server context, either directly or because of membership in a group.   You might also find the following post in SAS Support Communities useful: https://communities.sas.com/t5/Administration-and-Deployment/Deploy-jobs-in-SAS-MC/td-p/475562 . ... View more

Here are the differences between a standard workspace server, pooled workspace server, and load balanced workspace server:   In the default configuration, SAS presents you with a workspace server that is not pooled (standard workspace server) and a workspace server that is pooled (pooled workspace server).   For the standard, non-pooled workspace server, SAS creates a new server process each time that a client requests a connection. For simple configurations and for sites that do not place heavy loads on a workspace server, a non-pooled server might be adequate. In situations where the demands on the workspace server are greater, you should (depending on which SAS application you are using) consider configuring the workspace server for either pooling (web applications) or load balancing (desktop applications).   In a pooling configuration, a set of server processes are reused to avoid the processing time that is associated with starting a new process for each connection. SAS offers two types of pooling: client-based and server-based. A pooling configuration can also be shared across multiple machines. Pooling is recommended if your server supports SAS Web Report Studio and other web applications. For more information, see Overview of Pooling.   In a load-balancing configuration, your workspace server processes are distributed between multiple machines. Load balancing is recommended if your server supports applications that submit large jobs, such as SAS Data Integration Studio. For more information, see Overview of Load Balancing.   See: https://go.documentation.sas.com/doc/en/bicdc/9.4/biasag/n03001intelplatform00srvradm.htm#n03004intelplatform00srvradm ... View more

Here are some resources that you might find helpful: Virtualization Support Policy: 'SAS Product Support for Application Virtualization (Streaming) Environments' http://support.sas.com/techsup/pcn/virtualization.html   SGF paper on Virtualization using APP-V: Tips and Techniques for Deploying SAS® in an Application Virtualization Environment https://support.sas.com/resources/papers/proceedings13/461-2013.pdf  ... View more

Just to clarify, standard support is scheduled to end for SAS 9.4 & Viya 3.5 and earlier releases in 2025 (after the 5 year grace period that started in 2020). It will then move to limited support until the product is retired. Therefor it will still have support after 2025, but in a limited capacity. https://support.sas.com/en/technical-support/services-policies.html#levels  ... View more

If you logon directly to the computer server and launch SAS Management Console, are you able to successfully validate the SASApp - Logical Workspace Server? If so, then the issue may be that the ports are blocked on the firewall between the client and the server. ... View more

Did you ever run the PROC PERMTEST? If so, check the logs that you enabled. What do you see in the logs? That should help point to where the failure is occurring.  ... View more

If you reproduce the problem then look in your object spawner log, what do you see? Is the connection making it to the object spawner? Is there an error in the log?  ... View more