Event ID 3375 - Exchange Journal Archiving task ingesting from journal inbox - 0x8004060C

book

Article ID: 100012271

calendar_today

Updated On:

Description

Error Message

Dtrace Information:
To validate if this is the issue, a Dtrace is needed. Please perform the following steps on the EV server that has generated Event ID 3375 while re-creating the issue.

  • For more information about Enterprise Vault’s Dtrace Utility please see 100038975.
  • Dtrace the process JournalTask for no less than 5 minutes while re-creating the issue.
  • Open the log file created and search for either of the following the strings:


(JournalTask) <12564> EV~W Event ID: 3375 The following envelope message could not be archived as the attached message does not appear valid. |Title: TEST MESSAGE|Mailbox: /O=ROOTEXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=MBX-JOURNAL|No further attempts will be made to archive this message. The message has been moved to the 'Enterprise Vault Journaling Service\Invalid Journal Report' folder. |

(JournalTask) <12564> EV:M {CArchivingAgent::processMessages:#5157} Could not scan [user mailbox] [/O=ROOTEXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=MBX-JOURNAL]. This problem is commonly fixed on the next scan. Cannot list messages: [0x8004060c] [(null)]


Hex code 0x8004060C is a MAPI code that translates to:
MAPI_E_STORE_FULL


Other symptoms:

When reviewing the Dtrace over a long period of time, the same batch of messages may be observed as a result of the next scan of the mailbox. This will continue until 1 or more of the messages in the batch eventually throw the Event ID 3375 and the message(s) get moved to the 'Invalid Journal Report' folder. It may take a long running Dtrace to validate this pattern.
V-437-3375

Cause

The RecoverableItemsQuota on the Exchange Mailbox has been exceeded.

Resolution

From the Exchange Management Shell, run the following query to find the quotas on the affected mailbox:

[PS] C:\Windows\system32>get-mailbox journaling.mailbox | fl name,*quota*

This will return results similar to the following:

Name:                                                Journaling Mailbox
ProhibitSendQuota:                         unlimited
ProhibitSendReceiveQuota:           unlimited
RecoverableItemsQuota:                 30 GB (32,212,254,720 bytes)
RecoverableItemsWarningQuota:  20 GB (21,474,836,480 bytes)
UseDatabaseQuotaDefaults:         True
IssueWarningQuota:                        unlimited
RulesQuota:                                      64 KB (65,536 bytes)
ArchiveQuota:                                   50 GB (53,687,091,200 bytes)
ArchiveWarningQuota:                    45 GB (48,318,382,080 bytes)


If a quota is found on the RecoverableItemsQuota or the RecoverableItemsWarningQuota, the quota should be removed.

  1. Once the quota is removed, the dumpster should be purged as follows:
    • Search-Mailbox -Identity "Journaling Mailbox" -SearchDumpsterOnly -DeleteContent
  2. The following can be used to determine if SingleItemRecovery is enabled on the affected mailbox:
    • get-mailbox journaling.mailbox | fl name, singleitem*
  3. If it is enabled, it should be disabled as follows:
    • Set-Mailbox -Identity journaling.mailbox -SingleItemRecoveryEnabled $False

 

 

Issue/Introduction

Event ID 3375 is preventing the Exchange Journal Archiving task from ingesting messages in the journal inbox. There are no normal indications that processing is occurring when reviewing the J1 and J2 message queues. No items will go to storage. When viewing the Journal Inbox through Outlook, none of the items will go to pending or pending part. However, in the journal inbox, a very small number of items can be observed going into the 'Invalid Journal Report' folder.