When discussing details about an issue, a common area of interest is the “point of failure”. This is the exact point in time that the issue occurs, where it occurs, and under what conditions. The idea of determining the point of failure is to ultimately find a means by which to reproduce the issue being observed. Once any issue can be reproduced on demand, it is infinitely easier to work towards a solution. For troubleshooting, the identification of a point of failure means that we are able to reproduce the issue, collect applicable logs, sample items, and make assessments on if the issue is environmental or not. In most instances, we can collect samples that are provided to our Support team for analysis. This frequently expedites the troubleshooting of an issue and results in a drastically shortened time to resolution.
Migration Manager for PSTs has very robust logging features that enable administrators to effectively troubleshoot problems. There are two categories of logs - agent logs and server logs. Agent logs are generated by the Migration Agent and are stored on a user's computer. Agent logging is enabled by default. Server logs are generated by the various Migration Manager for PSTs modules and the Core. Server logging is disabled by default. To learn how to enable logging in Migration Manager for PSTs please visit use this on the topic.
The Windows Migration Agent has two components, the discovery agent and the migration agent, and both components generate logs. The logs are stored in %temp%\Quest\. Both logs can be retrieved from a workstation using the Request Client Logs feature in the Admin Console. If enabled, a user can elect to send logs to the server using the Send Log feature of the Migration Agent.
The Discovery Agent log is written to a file named FileScanner_hostname.log. The log will not be created if there are no warning levels. There is rarely a need to change the logging level, but you may be directed by Quest Support to change it for troubleshooting.
The migration log is updated every time the agent polls or every ten minutes when the agent checks for configuration changes and its name is MigrationAgent.log The Migration Agent log records items such as routine polling results, user enablement status, error conditions, work items to be processed, etc.
Server logs are used to log all routine work and errors conditions. They are extremely important for troubleshooting problems that occur with modules, consoles, the portal, and all client/server interactions. There is a log for every running Migration Manager for PSTs service, the Admin console on the core server, and the web interface. Each log has a maximum size of 100MB, at which point the new log is created and the original one renamed to include “archive” and a number in its name. These logs are stored in c:\program files (x86)\Quest\logs\. The various server log descriptions are in the following table. The directory where logs are stored can be changed during installation.