When you start too many campaigns at the same time using SAS Marketing Automation Launcher, some campaigns might fail with the following errors in the malauncher log:
Caught exception
ApplicationException
Cause message is getMAUser(123dbd6c-dc7a-41a2-8626-a0b8c7dec6d9) failure
ERROR 2026-03-25 16:28:46,442: EXCEPTION
ERROR com.sas.analytics.crm.ma.launcher.ExecutionFacade:logon()
ERROR getMAUser(543dbd6c-dc7a-41a2-8626-a0b8c7dec6d9) failure
com.sas.analytics.crm.error.client.ApplicationException: getMAUser(123dbd6c-dc7a-41a2-8626-a0b8c7dec6d9) failure
In SASCustIntelCore6.7.log:
ERROR [CIAsyncExec-304] [] [] om.sas.analytics.crm.ma.launcher.log.Log - com.sas.analytics.crm.ma.launcher.ExecutionFacade:logon()
com.sas.analytics.crm.error.client.ApplicationException: getMAUser(123dbd6c-dc7a-41a2-8626-a0b8c7dec6d9) failure
ERROR om.sas.analytics.crm.ma.launcher.log.Log - 24 Unable to acquire security manager
The malauncher log location is defined in the sasmalauncher.ini file.
- Windows: <SASHome>\SASMarketingAutomationLauncher\6.7
- Linux: <SASHome>/SASMarketingAutomationLauncher/6.7
The SASCustIntelCore6.7.log location is on the middle-tier machine.
- Windows: <SAS-configuration-directory>\Lev1\Web\Logs\SASServer6_1\
- Linux: <SAS-configuration-directory>/Lev1/Web/Logs/SASServer6_1/
Note that there is not a set number of current campaigns that can cause the problem. That number is based on various factors for your specific system.
Workaround
Complete either of the following workarounds to circumvent this issue:
- Start fewer campaigns at the same time with SAS Marketing Automation Launcher.
- Use a non-optimized campaign group. When you create the group definition, leave the group definition as non-optimized.