In SAS Enterprise Guide 8.6, disconnecting a SAS Viya compute context can unexpectedly impact other active compute contexts that are connected to the same SAS Viya URL.
When multiple compute contexts are configured (each as a separate connection in SAS Enterprise Guide but pointing to the same SAS Viya environment), disconnecting one context might disrupt other active contexts within the same user session.
This issue affects the following environments:
- SAS Enterprise Guide 8.6
- SAS Viya on Kubernetes with multiple compute contexts that use the same URL
Specifically, the following versions are affected:
- SAS Enterprise Guide 8.6 - 32-bit and 64-bit
- SAS Enterprise Guide 8.6 (SAS Viya only) - 32-bit and 64-bit
Symptoms
- After disconnecting one compute context, the following occurs:
- Other active contexts might become unusable.
- Submitting code might fail or produce no execution.
- The following error can be displayed: The log of the submitted job could not be retrieved.
- Programs running in another context might continue to execute on the server, but the following occurs:
- The log is no longer visible in SAS Enterprise Guide.
- The SAS Enterprise Guide SAS Viya connection appears disrupted.
Cause
This issue occurs due to a defect in SAS Enterprise Guide 8.6 where multiple compute contexts that share the same SAS Viya URL rely on a common client session configuration and connection handling behavior.
Disconnecting one context can inadvertently disrupt the connection state that other contexts use within the same user session.
Resolution
Apply SAS Enterprise Guide 8.6 Hot Fix 3 (HF3)
- Build Version: 8.6 Update 3 (8.6.3.47) (32-bit/64-bit, SAS Viya only)
Installing this hot fix resolves the issue and restores expected behavior. Disconnecting one context no longer impacts other active contexts.
Be sure to validate workflows that involve multiple compute contexts after applying the hot fix
Additional Information
Known Issue
When using multiple compute contexts connected to the same SAS Viya environment, one context might enter a loading state after you start another context. If the second context subsequently disconnects while the first context loads, both contexts might be disconnected instead of only the selected one. This behavior is intermittent and does not occur consistently. The expected behavior is that disconnecting one compute context should not impact other active contexts.
This is a known issue in SAS Enterprise Guide 8.6 Hot Fix 3 that SAS is currently investigating.