Exchange 2010 Journaling: Stuck messages in Submission queue

Update: This appears to be a documented bug in  KB2681250
However, the KB notes that it should be patched as of SP2 RU3 and it still appears to be an issue in SP3.  Opening support case now.

Further update: Looks like this is a distinct bug from the reported on in the above KB.  Scheduled to be patched in SP3 RU3.  Specifically, my issue seems to deal mostly with meeting invite replies (Accepted/Declined, etc.)

There’s an issue that appears to pop up periodically with Exchange Journaling which annecdotally, is due to having a BES server attached to your Exchange environment or  if a user has a broken signature in the Outlook client.  It appears some or all of these messages are Calendaring responses with a subject like “Accepted: Meeting Name” or “Declined: Meeting Name”

Messages get stuck in “Retry” in the Submission queue, which shows as an Event 9213 in the Application log:

Log Name: Application
Source: MSExchangeTransport
Date: <date>
Event ID: 9213
Task Category: Categorizer
Level: Error
Keywords: Classic
User: N/A
Computer: <servername>
Description:
A non-expirable message with the Internal Message ID 12345678 could not be categorized. This message may be a journal report or other system message. The message will remain in the queue until administrative action is taken to resolve the error. Other messages may also have encountered this error. To further diagnose the error, use the Queue Viewer or the Exchange Mail Flow Troubleshooter.

Looking at the message info it shows:

Last Error: 400 4.4.7 The server responded with: 550 5.6.0 M2MCVT.StorageError; storage error in content conversion. The failure was replaced by a retry response because the message was marked for retry if rejected.

A note about the line “The server responded with: 550 5.6.0…”  This appears to be the local Exchange server, not the intended destination server.  In context, since the message is in the “Submission” queue and not in one of the destination queues, that makes sense.

Without a way to specifically stop the messages, they can at least be manually removed from the queue using:

Get-Message -Server <servername> -Filter {FromAddress -eq "<>" -and Status -eq 'Retry'} | Remove-Message

Note, the second part of the filter “Status -eq “Retry”.  Normal Journaling messages also fly by with blank from addresses and this avoids removing any of those.

Advertisements

9 responses to “Exchange 2010 Journaling: Stuck messages in Submission queue”

  1. Gerry says :

    Nice one, worked like a charm. Thanks!

  2. gary says :

    thansk

  3. Keerti says :

    How about exchange 2013. I am facing the same issue in our infra

  4. ril3y says :

    The same powershell command to clear the current stuck messages should work in 2013, though I haven’t tried it. I still have the same issue in 2010, and I’m stumped as to the cause. Probably should report it again. If you have the ability, open a support case about it yourself. Extra people reporting the issue can’t hurt.

  5. mike says :

    Just wondering did you ever get a resolution to this? Sure we can remove the messages but we need to journal everything, including meeting requests. I am finding this on our fully patched Exchange 2010 environment where some journaled meeting requests get stuck in the Submission queue with a status of: 400 4.4.7 The server responded with: 550 5.6.0 M2MCVT.StorageError; storage error in content conversion.

    • ril3y says :

      Unfortunately no. I’ve called in about it on two separate occasions and the support person indicated that it was a known issue, scheduled for a fix in the future update. But those updates have passed and the issue remains. We haven’t migrated to 2013 yet, so I don’t have a sense of whether it is fixed there or not. One of these days maybe I’ll try again, but I’m not hopeful of a patch. Apparently 2016 is a year away at this point.

  6. Jackie says :

    I can confirm this is still an issue in our environment, even after updating all Exchange 2010 servers to SP3 RU7.

  7. Marco says :

    It’s even still existing on Exchange 2013 CU6….It’s really annoying

  8. El Krikone says :

    Awesome, worked like a charm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: