An issue occurs after you apply SAS® Viya® patch updates in an environment with the SAS® Anti-Money Laundering solution. When you launch SAS® Data and AI Studio (formerly SAS® Studio) and select the SAS AML compute context, the compute session times out and fails to be created with an error code 2049.
In addition, the following error message might be displayed:
The sas-compute pod log also contains a warning message about a sas-deployment-metadata ConfigMap that is not found:
{"level":"warn","version":1,"source":"sas-compute","messageKey":"compute-log-icu.services.launch.kubernetes-process-message.warn.log","messageParameters":{"job_message":"Failed: Error: configmap \"sas-deployment-metadata-8dfbh8d4f8\" not found","serverID":"<ID>"},"properties":{"logger":"service/compute/service/launch","span_id":"<ID>","trace_id":"<ID>","req":"POST /compute/jobs","tenant":"provider","caller":"launch/runner.go:189"},
"timeStamp":"2026-10-08T14:19:05.823940+00:00","message":"The server with the ID \"<ID>\"
returned the following warning from Kubernetes: \"Failed: Error: configmap \"sas-deployment-metadata-8dfbh8d4f8\" not found.\""}
After you apply SAS Viya patch updates, the patches can create a new sas-deployment-metadata ConfigMap. The sas-compute-job-config PodTemplate that is used to create compute sessions is updated with the new configmap. However, the sas-aml-compute-job-config PodTemplate that is copied from the sas-compute-job-config PodTemplate when the SAS Anti-Money Laundering provisioning job's CONFIGURE_AML_COMPUTE_PT task runs does not update and still contains the old copied ConfigMap reference that no longer exists.
Complete either of the following workarounds to circumvent this issue:
Then, try launching a new SAS Data and AI Studio session and select the SAS AML compute context in the new session.
A fix for this issue is planned for a future software release.