In SAS Digital Marketing, the config.xml file might become corrupted. The file might be updated incorrectly with duplicate entries, or it might lose some or all of the entries.

This problem might occur when you apply a SAS Digital Marketing hot fix to your system or at other times.

If duplicate entries of the execution contexts are generated in the config.xml file, SAS Digital Marketing might fail to execute some broadcasts. Calls to multiple, erroneous execution contexts might appear in the sdm_server log file, as shown below:

2014-04-25 11:07:25,495 [DEBUG] m.sas.email.server.DynamicControllerImpl - Available execution contexts : [localhost, localhost].
2014-04-25 11:07:25,495 [DEBUG] m.sas.email.server.DynamicControllerImpl -Acquiring execution context on grid node [localhost].
2014-04-25 11:07:25,495 [DEBUG] m.sas.email.server.DynamicControllerImpl -Acquiring execution context on grid node [localhost].

If the config.xml file loses some or all of its entries, the SAS Digital Marketing server might fail to start.

If you discover erroneous duplicate entries of objects in the config.xml file, stop the SAS Digital Marketing server and remove these entries. Then restart the server.

If the config.xml file loses some or all of its entries, replace the file from a recent backup and restart the SAS Digital Marketing server.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Digital Marketing 6.3 is available at:

A fix for this issue for SAS Digital Marketing 6.1_M1 is available at: