Chat now with support
Chat with Support

NOTICE! We are upgrading our support telephone services, implementing Genesys, starting the week of May 19, 2025

MessageStats 7.8.1 - Reports User Guide

Upgrading MessageStats Overview Typical MessageStats Upgrade Scenarios Moving the MessageStats Database Moving and Upgrading MessageStats Moving Custom Reports and Report Subscriptions Viewing, Creating, and Editing MessageStats Reports My Reports and Corporate Reports Exchange Executive Summaries Reports Exchange Organizations Reports Exchange Server Reports Exchange Content Analysis Reports Exchange Mailboxes Reports Exchange Mail Contacts Reports Exchange Distribution Groups Reports Exchange Public Folders Reports Exchange Storage Reports Exchange Internet Reports Exchange Inventory Reports Migration Reports MessageStats Gathering Reports Appendix A: How to Read the Reports Report Filter Definitions

About task migration

When upgrading MessageStats, you are prompted to initiate task migration.

Depending on how your MessageStats Scheduler Service is configured and on the number of existing tasks that you have to migrate, task migration can take several hours. If you choose to cancel task migration during the installation process, you can run it separately at a later time.

You cannot use the upgraded MessageStats release until the existing tasks have been migrated.

When you run the MigrateTasks.exe tool, it performs the following tasks:

The following error conditions might be reported during task migration:

Error Message

What It Means

Problem migrating task

Problem migrating task instance

Problem updating occurrence status of task instance

These errors can appear if you deleted any task files in the MessageStats tasks folder. The task migration continues but the status of occurrences related to the missing task documents will be inaccurate.

Problem migrating property X of task

Problem migrating property x of task instance

Problem updating status of task instance

Problem updating progress of task instance

These errors can appear if there are errors in the task documents, or if there were errors during database installation. Task migration is not performed for the problematic information, but will otherwise continue.

If task migration is stopped unexpectedly, the Quest MessageStats Scheduler Service might be left in a disabled state. In this situation, you must enable the scheduler service before you can restart task migration.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating