After you apply hot fixes to SAS Marketing Automation 6.7 and/or SAS Marketing Optimization 6.7 on a Windows deployment, the following error might occur immediately after you enter valid credentials on the SAS logon page:
401 - Unauthorized
Restarting the affected SAS Web Application services might not resolve this issue.
This issue occurs because cached mid-tier files, ActiveMQ data, or Geode cache files can become stale or inconsistent during the hot fix installation. As a result, the SAS Web Application environment might be unable to successfully authenticate.
To resolve this issue, perform a full mid-tier cleanup and restart of the SAS environment.
1. Stop SAS Servers.
Stop the SAS servers in the following order.
Note: For multi-tier SAS environments, follow the SAS-recommended server shutdown sequence to ensure that all dependent services are stopped cleanly.
2. Clean up the mid-tier temporary files and logs.
Delete, move, or archive the contents of the following directories.
Important: Delete only the contents of the specified directories unless otherwise noted.
<SAS-configuration-directory>\Lev1\Web\WebAppServer\SASServerX_Y\temp\*
These temporary files do not need to be backed up.
<SAS-configuration-directory>\Lev1\Web\WebServer\logs\*
<SAS-configuration-directory>\Lev1\Web\activemq\data\*
Note: Delete only the contents of the data directory. Do not delete the data folder itself. The folder is required for service start-up, and its contents will be recreated automatically during start-up.
<SAS-configuration-directory>\Lev1\Web\geode\instances\ins_41415\*.log
<SAS-configuration-directory>\Lev1\Web\geode\instances\ins_41415\*.dat
<SAS-configuration-directory>\Lev1\Web\geode\instances\ins_41415\ConfigDiskDir_<hostname>
-41415\*.*
Here is an example:
D:\opt\sasinside\Config\Lev1\Web\geode\instances\ins_41415\ConfigDiskDir_test.demo.
sas.com-41415
Note: Delete only the contents of the ConfigDiskDir_<hostname>-41415 directory. Do not delete the directory itself, as it is required for service start-up.
<SAS-configuration-directory>\Lev1\Web\Logs\SASServerX_Y\*
where X and Y represent web application server instances such as the following:
3. Restart the SAS servers.
Start the SAS servers in the following order:
After all servers start successfully, start any remaining SAS services and validate normal application functionality.
Note: Start services in dependency order to ensure that all required back-end services are available before the web applications initialize.
After start-up is complete, do as follows:
For additional validation procedures, see SAS KB0046086, "How to validate the SAS® 9.4 platform when issues occur in SAS® Marketing Automation."
If the problem still persists, make sure that you clear the browser cache, including passwords.
For example, complete the following steps to clear the cache in Google Chrome:
For additional information about the SAS Service start-up order, see the following resources: