My cluster is up and running. But EG/Studio connection fails to start workspace server

LB1961 — Thu, 06 Nov 2025 20:11:29 GMT

== As a junior SAS admin - I only see this ERROR

Line 791: 2025-11-06T14:24:52,663 INFO [00005141] :asasuser - MFA NOT ENABLED (asasuser) T=0.000031

Line 792: 2025-11-06T14:24:52,664 INFO [00005141] :asasuser - New client connection (246) accepted from server port 8592 for user asasuser. Encryption level is Credentials using encryption algorithm AES. Peer IP address and port are [::ffff:10.160.9.127]:57687 for APPNAME=SAS Enterprise Guide.

Line 793: 2025-11-06T14:24:52,796 INFO [00005141] :asasuser - New out call client connection (247) for user sastrust@saspw. Encryption level is Credentials using encryption algorithm AES. Peer IP address and port are [10.226.197.200]:8562.

Line 794: 2025-11-06T14:24:52,808 INFO [00005141] :asasuser - There are no grid option sets defined for SAS application server "SASApp".

Line 795: 2025-11-06T14:24:52,809 INFO [00005141] :asasuser - Client connection 247 for user sastrust@saspw closed.

Line 796: 2025-11-06T14:24:52,933 INFO [00005141] :asasuser - New out call client connection (248) for user sastrust@saspw. Encryption level is Credentials using encryption algorithm AES. Peer IP address and port are [10.226.197.200]:8562.

Line 797: 2025-11-06T14:24:52,974 INFO [00005141] :asasuser - Grid credentials retrieved from authdomain 'DefaultAuth' in metadata.

Line 799: 2025-11-06T14:25:03,040 ERROR [00005141] :asasuser - SSL negotiation could not complete because the socket was closed by the partner.

Line 800: 2025-11-06T14:25:03,041 ERROR [00005141] :asasuser - ERROR: SSL negotiation could not complete because the socket was closed by the partner.

Line 801: 2025-11-06T14:25:03,041 ERROR [00005141] :asasuser - Grid options for this peer were unable to be obtained from the metadata. Therefore this server cannot be launched.

Re: My cluster is up and running. But EG/Studio connection fails to start workspace server

gwootton — Fri, 07 Nov 2025 16:14:06 GMT

Looks like the Object Spawner is successfully connecting to Metadata and then failing to connect to your grid provider (SAS Workload Orchestrator). Because it's an SSL error I would guess this is due to a configuration mismatch between the TLS configuration for SAS Workload Orchestrator (SWO) in SAS Management Console (SMC) and in SAS Workload Orchestrator itself.

This page of the documentation covers the settings in SMC and SWO related to TLS, depending on whether you want this on or off.

Configuring High Availability and TLS with SAS Workload Orchestrator
https://go.documentation.sas.com/doc/en/bicdc/9.4/gridref/n0v45v6q40z5oan11z60rejc4jex.htm

topic Re: My cluster is up and running. But EG/Studio connection fails to start workspace server in Administration and Deployment

My cluster is up and running. But EG/Studio connection fails to start workspace server

Re: My cluster is up and running. But EG/Studio connection fails to start workspace server