Chat now with support
Chat with Support

MessageStats 7.6 - Administrator Guide

What is MessageStats? MessageStats Information Sources Using the Console Interface Creating a Connection to Exchange Creating Gathering Tasks Default Gatherings Extending Gathering Tasks Configuring Audits Setting MessageStats Server Properties Setting Configuration Properties Setting Exchange Organization Properties Setting Exchange Server Properties Setting Task Execution Server Properties Setting Task Default Properties Compressing Tracking Log Files Using the MessageStats Reports Console Database Management Appendix A:Microsoft ASP.NET Configuration Issues Appendix B: Gathering Task Dependencies Appendix C:Troubleshooting Permission Problems

Specifying Paths for Task Log Files

Using the Task Logging Paths tab, you can specify the local location on the task execution server to which the task log files are written. You can also specify a share location for the files so that the files can be viewed from a remote MessageStats console.

Store task logs in

Select the path location on the local task execution server in which the task logs are to be stored.

Task Log Share for Remote Consoles

Specify the share in which log files are stored for remote access. During installation, you are prompted to create a share on the task execution server for application log files. The share is required so that a remote MessageStats console can access the task logs.

Setting Up Archiving for Task Logs

As part of task logging configuration, you have the option of enabling task log archives. You can set the length of time that you want to keep archived log files, and you can schedule a time at which log files are archived.


Use the Task Logging Archive tab to configure the archiving for task logs, if using.

Enable archiving for MessageStats task logging

Select this option to specify the time that you want to retain the task log files, and the method for handling the files once the time limit is reached. The check box is cleared by default.

Number of months to keep

Specify the length of time, in months, that you want to keep the task log files.

Time to execute archiving

Set the time at which you want the archiving process to be run on the task execution server.

Task Logging Management Method

Select one of the following options to handle the task logs once the time limit for keeping them has been reached:

Select Delete Files if you want the archived task log files to be deleted when the number of months you selected to retain the files has expired.
Select Move Files to Backup Location to copy the files to the path location that you specify and delete them from the MessageStats server.
Select Compress Files to Backup Location to compress the files and copy them to the path location that you specify. The compression option uses the PKZIP 2.0 file archive format.

Configuring Task Processors

Using the Task Processors tab, you can define the maximum number of task processors that can be run concurrently by the task execution server at any time.


Select the Task Processor tab.
Click Apply.

Modifying Task Processor DCOM Credentials

Task credentials refer to the account under which the task processors run to gather information from the Exchange servers.

By default, the task credentials set for the Task Execution Server are used by all tasks. However, you can also set separate credentials under which a specific task will run. If the task is using the default credentials for the Task Execution Server, you can correct the credentials using the DCOM Credentials property tab.

If the task uses explicit credentials, you can correct the credential information for the specific task. For information about how to change the credentials for a specific task, see Changing Task Credentials .

If the task credential information for a task is incorrect, when you run the task it will fail continually. This problem is easy to diagnose since the error details are provided in the task log. If you view the log and see the following error text, the credentials for the task are invalid and must be corrected:

Another issue that might occur is that a task never appears to be running. Even if you force the task to run using the Run Now command, the task never appears to start. This issue can also be caused by a DCOM problem.

When you use the DCOM Credentials tab to modify the account, changes are made to the MessageStats Task Processor COM object. These credentials can also be accessed using the DCOM Config section of Windows Component Services and are used to instantiate the COM object.



Displays the existing account set as the MessageStats Task Execution Server account.


Enter the password for the service account.

Confirm Password

Re-enter the password to confirm it.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating