暂时无法在支持网站上提交享有定期维护的产品表单。 如果您需要我们立即提供帮助，请与技术支持部门联系。 对于由此给您带来的不便，我们深表歉意。
获得即时帮助
完成注册
登录
请求定价
联系销售人员
您已选择一个产品捆绑包。 您能否选择单个产品以便我们更好地满足您的请求。 *
技术支持工程师目前正忙，无法回应您的消息。 如果需要即时服务，请通过我们的服务请求表提交请求。
以下文章可根据您的描述解决您的问题。
MessageStats creates log entries during several processes. You can use the Task Logging page to set up logging at the task level.
Use the Task Logging page to configure the following:
Enable logging for the given Task Processor
Select this option to enable logging for this gathering task and you can identify the detail level of the task logs.
Log detail level
Set the level of detail that should be included in the log files. For information about the different levels of details, see About Logging Levels .
Record errors in the Windows Application Event Log
Select this option to also record errors in Windows Application Event logs.
You can define the logging level for your task logs. The following log levels are available, from the most detailed to the least detailed:
Trace
Trace level logging is extremely detailed logging that includes errors, warnings, and status messages, and also low-level event details.Trace logging is only used with custom components provided by Quest development for diagnostic purposes. This level of logging can generate large log file and can affect system performance.
Debug
Debug level logging includes errors, warnings, and status messages, and also low-level event details. Quest Support might ask you to set logging to the debug level to identify and resolve an issue. Use debug-level logging only at the request of Quest Support, since the log files can grow rapidly and can affect system performance. These logs contain very detailed entries.
Status
Status level logging includes warnings and errors, as well as the regular flow of major events. Use the Status level for a new installation to include more detailed logs.
Warning
Warning level logging includes errors that appear at the Errors level. The Warning level also includes errors that occurred but from which the task recovered and continued gathering. Use this level for established and stable implementations.
Errors
Errors level logging includes errors that caused a gathering task to terminate.
It is recommended that you periodically remove obsolete logs.
The Task Retry property page lets you specify the number of times you want to try to connect to a server to run a task. It also lets you specify the number of minutes between each connection attempt.
If MessageStats cannot access a server to perform a task, it will continue to attempt to run the task based on the retry parameters you specified
Number of time to retry connection
Default value is three times.
Number of minutes between retry attempts
Default value is one minutes.
The following sections explain how to create gathering tasks using the Create Task Wizard and explains how the Default Gathering for Lotus and IBM Notes task is used.
A task is a collection of gathering activities. When you create a task, it is listed in the Tasks node of the navigation tree. When you click the Tasks node, the task appears in the Tasks Summary View.
The Tasks Summary View shows all the tasks created for the MessageStats Scheduler Server. The Tasks Summary view displays the properties of a task, including the task name, credentials, schedule, next occurrence, description, and progress.
Tasks are scheduled to run an occurrence of that task. Each occurrence has a start date and time. Each occurrence lists the activities and associated properties in the Task Activity view.
The Task Activity view displays detailed properties of the activities that comprise an individual task. These properties include activity descriptions, source, status, progress, runtime gathering dependencies, start and finish time, activity duration, and execution server.
您可以在附属支持站点上查找适用于戴尔*产品*的在线支持帮助。单击“继续”，转至适用于*产品*的正确支持内容和帮助。
The document was helpful.
选择评级
I easily found the information I needed.
Quest Software门户不再支持IE 8、9和10，建议将您的浏览器升级到最新版本的Internet Explorer或Chrome。
要升级到IE 11，请单击此处
要升级到Chrome，请单击此处
如果继续使用IE 8、9和10，您将无法充分利用我们所有出色的自助服务功能。
