Monitoring journal mailboxes

Article:HOWTO56634  |  Created: 2011-08-01  |  Updated: 2013-07-12  |  Article URL http://www.symantec.com/docs/HOWTO56634
Article Type
How To


Subject


Monitoring journal mailboxes

You can set up Enterprise Vault so that it archives all messages that the Microsoft Exchange Server system sends and receives, provided that the messages are passed to one or more specific Microsoft Exchange journal mailboxes.

The Exchange Journaling task runs continuously, checking for items in journal mailboxes and immediately archiving them. These items are deleted from the mailbox as they are archived and no shortcuts are created.

It is important that you monitor journal mailboxes to make sure that items are archived promptly. It is especially important that you do this if you have suffered some sort of system failure which required a system restart.

If you are running an Exchange Journaling task, messages in the journal mailbox should be archived soon after they arrive in the mailbox.

To check a journal mailbox

  1. Run Microsoft Exchange Client or Microsoft Outlook.

  2. Log on to a profile that has access to the journal mailbox.

  3. Check that there are no messages in the Inbox folder that are older than one day. If there are any messages older than one day, then there is likely to be a problem.

  4. Look in the following folders, which are under the Enterprise Vault Exchange Journaling Task folder:

    Above maximum size

    Contains messages that exceed the maximum size that is set in the Exchange journaling policy.

    Failed Codepage nnn

    To fix the problem, do one of the following:

    • Install the missing codepage.

    • Use the default ANSI codepage (ACP codepage).

    These tasks are described below.

    When you have set up codepages correctly, move the failed messages back to the Journal Inbox so that they are processed again.

    Failed DL Expansion

    Contains the items that cannot be archived because Enterprise Vault is unable to expand their distribution lists.

    Failed External Filter

    Contains the messages that cannot be processed by a custom filter.

    Check the Enterprise Vault Event Log to determine the cause of the problem.

    Also check that the rule set file references the correct XML schema.

    Failed to copy

    Contains the messages that are probably corrupt. Try dragging them to your desktop and then, when they are on the desktop, double-clicking them.

    You may find that the messages are now not corrupt. If you drag them from your Desktop to the Inbox folder, the Exchange Journaling task tries to archive them again. Remember to delete the corrupt versions from the Failed to copy folder.

    Failed to store

    Contains the messages that cannot be archived. They probably failed because of a problem with the Storage service. You can move all these items back to the Inbox folder and the Exchange Journaling task tries again to archive them.

    Invalid Journal Report

    Contains messages whose journal report (P1 envelope message) does not conform to Microsoft's specification.

To add the codepage

  1. Install the required codepage on the Exchange Journaling task computer.

  2. To prevent a similar problem from happening on Exchange Mailbox task computers, install the codepage on each Exchange Mailbox task computer.

  3. If you use a building blocks configuration, repeat the changes on every Enterprise Vault server in your site.

See Use the default ANSI codepage (ACP codepage)

See Monitoring the system status


Legacy ID



v11738451_v41328148


Article URL http://www.symantec.com/docs/HOWTO56634


Terms of use for this information are found in Legal Notices