How to Troubleshoot Direct Mailer

When a Direct Mailer job completes, Direct Mailer logs an event to the Windows Application event log. This event contains the job number, the start time of the job, the completion time of the job, the total number of recipients in the mailing, and the number of errors that occurred. To view specific error details, see How to View Direct Mailer Job Errors.

Direct Mailer Event Log Codes

To open Event Viewer and locate the application event log message logged by Direct Mailer

1. Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.

2. Commerce Server Core Systems events are labeled as "Commerce Server" in the Source column.

3. Note the Event ID from the Event column.

4. Look up the Event ID in the following table for more information.

Direct Mailer Event Log Codes

Event	Message	Task	Rule
10	Service has been started		Informational
11	Service has been stopped		Informational
12	The job %1 has completed execution. Job Name: %2. Start Time: %3. Finish Time: %4. Recipient Count: %5. Error Count: %6		Informational
13	The job %1 has started execution		Informational
100	Invalid control request		Warning
101	Error opening or appending to the log file: %1 Logging will be disabled at this time.		Warning
102	The job '%1' has been aborted due to a fatal error or because the total errors number for this job exceeded the limit		Warning
103	The job '%1' has been aborted due to system shutdown request	Restart job when system is up.	Warning
104	Attempt to connect to the Direct Mailer Database has failed. Please verify the configuration settings and the database server status	Check the connection string to the database.	Warning
105	The job %1 was aborted because the DirectMailer database has become unavailable. Job Name: %2. Start Time: %3. Finish Time: %4. Recipient Count: %5 of %6. Error Count: %7. The job will continue to show a status of running (3) even once the database is back online. To restart the job, use "dmlrun.exe /run:%1" or stop and restart the direct mailer service.	Check the connection string to the database. Check for network issues.	Warning
106	The job %1 was terminated before running to completion. Job Name: %2. Start Time: %3. Finish Time: %4. Recipient Count: %5 of %6. Error Count: %7.		Warning
107	The job %1 was aborted because there were errors during validating of the job parameters. The error details are below: %2		Warning
200	Cannot start the service: Service Handler is not installed	Install service handler.	Error
201	Cannot initialize the service due to the following error: %1		Error
202	Cannot initialize the service - unknown exception has been raised		Error
203	Cannot access the service configuration information due to the following error: hr=0x%1 %2		Error
204	Cannot access service configuration - unknown exception has been raised		Error
205	Unhandled exception in the module: %1 The module execution terminated		Error
206	The service was initialized but failed to connect to the database. Please fix the problem and restart the service	Please fix the problem and restart the service.	Error
207	CDO Initialization failed: %1	Verify the configuration settings.	Error
208	ADO Initialization failed: %1	Verify the configuration settings.	Error
209	ADO connection to the Direct Mailer database failed: %1. Please verify the configuration settings	Verify the configuration settings.	Error
20A	Failed to execute ADO command due to the following problem: %1. Please verify the configuration settings	Verify the configuration settings.	Error
20B	Invalid configuration parameter(s)		Error
20C	Error while creating or manipulating with a Commerce Server Core Systems core object '%1'. Error code %2.		Error
20D	Error while creating or manipulating with an internal object '%1'. Execution has been terminated.		Error
20E	An Error occurred retrieving global configuration properties for the DirectMailer service. Support Information: Failed step=%1 HRESULT=%2.		Error

Improving Direct Mailer Performance

If Direct Mailer is sending out e-mail slowly, and the e-mail being sent is in MHTML format (implying embedded images/objects), and the body of the e-mail is linked to a URL (rather than a file path), it is possible that the URL is inaccessible or slow to be accessed. Therefore, it may take a long time for Collaboration Data Objects (CDO) to compose the mail message body, causing the Direct Mailer to generate and send the mails at a slow rate. To determine whether this is an issue, try taking the URL links out of the mail body or switch to HTML format (so the mail contains links instead of embedded objects).

Known Issues

This section contains known Direct Mailer issues, including reproduction steps if available, and workarounds/notes.

Problem	Reproduction Steps	Workaround/Notes
No result mail is generated in drop folder if "Message Body Source" is set to an HTTP file.	Open the Marketing Manager. Switch to Campaigns view. Create a direct mail "DM1", set "Message Body Source"="http://csd111/StarterSite/robots.txt". Note:   You can open file "http://csd111/StarterSite/robots.txt" can be opened in Internet Explorer. Test "DM1". Look up result mail in folder "C:\Program Files\Microsoft Commerce Server 2007\DML_drop". Expected Result: Result mail should be generated. Actual Result: No result mail is generated.	Create a Web page that handles the request and embeds the text into the response instead of using a text file.
DirectMailer performance counters don’t use instances, but the site names still appear as instances that you can monitor.		Instances will appear for DirectMailer performance counters corresponding to all Commerce Server Core Systems site names that exist in the deployment; however, the only instance that will be active is the "Anonymous" instance since DirectMailer is a global resource and not associated with any site.

See Also

Other Resources

Direct Mailer Service