A "401 - Unauthorized" error occurs in SAS® Marketing Automation 6.7 and SAS® Marketing Optimization 6.7 on Windows


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. 


Resolution

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.

    1. mid-tier servers
    2. compute servers
    3. metadata server

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:

    1. metadata server
    2. compute servers
    3. mid-tier servers

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.


Validation

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."


What to Do When the Issue Still Persists

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:

  1. Open Google Chrome and press Ctrl+Shift+Del to open the deletion menu.
    Delete browsing data window


  2. Click All Time.
  3. Then, click Delete from this device.
  4. In the same window, click Manage other Google data, which displays the following:
    Other Google data window


  5. Click the square box with the arrow to open the Password Manager window. Then, click the right arrow (►) where the sas passwords are stored. Provide your SAS Installer User password:
    Password Manager window

  6.  Delete your SAS passwords.
    Passwords - Password Manager Window

Additional Information

For additional information about the SAS Service start-up order, see the following resources: