Issues might occur in SAS Marketing Automation for IT administrators. A quick workaround for these issues is to validate your SAS 9.4 environment an ensure that everything works properly, as described in this SAS KB article.
To confirm whether the various SAS servers that you deploy are running properly, complete the following steps. Note that the SAS 9.4 platform must be running properly in order for SAS Marketing Automation to work. If issues occur when validating, you should troubleshoot those issues before using SAS Marketing Automation.
See the following table for summaries of the server validation information. Use the server context name that you entered during the deployment. In the table, the server context name is SASApp.
| Server | Validation Method |
| SAS® Metadata Server | Successfully log on using SAS® Management Console with a SAS Administrator user ID. (For example, sasadm@saspw.) |
| SAS® Content Server |
|
| SAS Pooled Workspace Server |
|
| SAS Workspace Server |
|
| SAS® Stored Process Server |
|
| SAS Object Spawner | If either SAS® Stored Process Server or one of the SAS Workspace Servers validates, then the SAS Object Spawner is running. |
To validate the SAS server tier, complete the following steps:
1. Log on to the machine that hosts on one or more of the SAS Servers.
2. Start SAS Management Console using the command for the appropriate operating system.
Windows: Navigate to Start ►SAS ► SAS Management Console 9.4.
Unix: <SAS-installation-directory>/sasmc
Here is an example: /opt/sas/SASManagementConsole/9.4/sasmc
3. Log on to SAS Metadata Server using valid credentials, such as the SAS Administrator. (For example, sasadm@saspw.)
4. In SAS Management Console, on the Plug-ins tab, expand the Server Manager node.
5. Right-click the SAS Content Server node and select Validate.
SAS Management Console attempts to make a WebDAV connection to the server.
If the connection is successful, the following message is displayed:
Validation Successful!
This message indicates the following:
If the connection is not successful, errors similar to the following are displayed:
SEVERE: Code 502: Service Unavailable
SEVERE: java.net.ConnectException: Connection refused: connect
SEVERE: Code 404:Not found – Path 'http://demo.test.domain:80/SASContentServer/repository/test/' does not exist or user ID 'sasadm@!*(generatepassworddomain)*!' does not have permission to access the path
6. Expand the SAS Application Server node. (The default name is SASApp.)
7. Click the server that you want to validate (such as the SASApp - Logical Pooled Workspace Server, the SASApp - Logical Workspace Server, and/or the SASApp - Logical Stored Process Server).
8. Right-click the server and click Validate. The following message should occur:
Validation Successful!
If problems occur when validating the Server tier, open a SAS Technical Support Case and/or review the associated logs. After opening the SAS Technical Support Case, you can request access to upload the logs via the SASTSDrive.
Your specific log locations are provided in your Instructions.html file. These files are located in the <sasconfig>/Lev1/Documents/Instructions.html or <sasconfig>/Lev1/Documents/Backups folder on each tier (meta, compute, and mid-tier). See Default Locations for Server Logs for additional information.
Note: In a custom installation, you can choose to place all of your server-tier log files in a single directory. If you choose this option, your server-tier log files are written to the path that you specified during installation. (For example, SAS-configuration-directory/Lev1/Logs.)
See the following table for summaries of the server validation information:
| Server | Validation Method |
| SAS Web Server |
Congratulations! You have successfully set up SAS Web Server. |
| SAS Web Administration Console |
|
| SAS Customer Intelligence Studio |
|
To validate the SAS middle-tier, complete the following steps:
1. Log on to the machine hosting one or more SAS servers.
2. Open a web browser. (For example, Google Chrome, Mozilla Firefox, and so on.)
3. Review the Instructions.html file on the Middle-Tier and search for SAS Web Administration console. Then, click the URL.
For example, http://<your mid-tier>:7980/SASAdmin or https://<your mid-tier>:/8343/SASAdmin.
4. Log on using the sasadm@saspw credentials provided during configuration.
5. On the main page, click the Users node.
6. Verify that sasadm is displayed in the System Users section in the right pane.
7. Review the Instructions.html file on the Middle-Tier and search for SAS Web Server Configuration. Click the Server Home Page URL.
For example, http://<your mid-tier>:7980 or https://<your mid-tier>:/8343.
Then, look for the following message: Congratulations! You have successfully set up SAS Web Server.
Note: If problems occur with either the SAS Web Server or the SAS Web Administration Console, open a Tech Support Case and/or review the associated logs. After opening the Tech Support Case, you can request access to upload the logs via the SASTSDrive. Your specific log locations are provided in your Instructions.html file.
Here is an example:
<SASConfig>\Lev1\Web\Logs\SASServer1_1\SASAdmin9.4.log
<SASConfig>Lev1\Web\WebServer\logs
For information about the default middle-tier log locations, see Middle-Tier Logs and Log Locations.