How to troubleshoot system-level issues that affect the Direct Marketing Agent


System-level changes—such as Operating System (OS) patching, service restarts, or configuration updates—can prevent the Direct Marketing Agent from starting or functioning correctly. These issues often manifest as connection failures, bean creation errors, or middle-tier dependency failures.

Common errors and warnings include the following:

These messages typically occur in the onprem_direct.log.

System issues often arise from the following:

Recommended Troubleshooting Steps

Verify that SAS Services Stopped Properly Before Patching

If patching occurred while SAS services were running, dependencies might be in an inconsistent state. Review logs for connection failures.   

Restart All SAS Services

Note: Ensure that no SAS processes are still running before restarting all SAS services.

ps -ef | grep "sas"
ps -ef | grep "sassrv"


On Windows, use the Task Manager to locate the processes.

Restart SASServer1 After Making Metadata Changes

If users, application objects, or metadata items were modified, restart SASServer1 and any dependent servers.

Restart the Direct Marketing Agent

Once SAS services are stable, restart the agent. See SAS KB0040788 for more details about validating the SAS® 9.4 environment.

Summary

System-level issues typically stem from patching, service restarts, or metadata changes. To resolve most failures, ensure proper shutdown, restart sequencing, and middle-tier stabilization.

References