When the IIS Log File Gatherer task is run from a second Task Exection Server it fails with the following error:
"The following error occurred during the processing of a given gathering: The device is not ready"
The local IIS Log file cache that is used to store the IIS Logs that are copied to the MessageStats server while they are processed is a global setting that applies to all Task Execution Servers. The location for this cache is the same as the Tracking Log Cache which is set in the MessageStats console under the Properties of the Tasks node.
If the path to the Tracking Log Cache that is configured in the MessageStats console does not exist on the second Task Execution, the device is not ready error is logged as the IIS Log File Gatherer task is trying to copy the IIS Log files to a location on the second Task Execution server that does not exist.
Example 1: The path for the Tracking Log Cache is configured to be the following in the MessageStats console:
D:\Program Files (x86)\Quest Software\MessageStats\Tracking Logs
However, the second Task Execution server does not have a D: drive. Because the Tracking Log Cache path configured in MessageStats does not exist on the second Task Execution server the task fails.
Example 2: The path for the Tracking Log Cache is configured to be the following in the MessageStats console:
D:\Program Files (x86)\Quest Software\MessageStats\Tracking Logs
The second Task Execution server does have a D: drive but the path: Program Files (x86)\Quest Software\MessageStats\Tracking Logs does not exist under the D: drive on the second Task Execution server
WORKAROUND:
The path to the Tracking Log Cache configured in the MessageStats console has to exist on all Task Execution Servers where the IIS Log Gatherer task is run. It is not possible to configure the path to the Tracking Log Cache on each Task Execution Server.
To configure the path for the Tracking Log Cache:
If the path configured in the MessageStats console for the Tracking Log Cache cannot be created on each Task Execution server where the IIS Log Gatherer task is run, then the task will need to be run from the server where the Quest MessageStats Scheduler Service is installed
STATUS:
Enhancement request TF00186642 has been submitted to Development for consideration in a future release of MessageStats
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center