Anasayfa » Forum

MSExchangeTransport...
 
Bildirimler

MSExchangeTransport Event id 9213  

  RSS
mrtsimsek
(@mrtsimsek)
Üye

Merhabalar,

 

Her yarım saate bir Exchange Server 2010 SP1 Rollup2 üzerinde aşağıdaki hatayı alıyorum. Queue da Submission altında 2 adet mail duruyor. Yardımlarınızı rica ediyorum.

 

Log Name:      Application

Source:        MSExchangeTransport

Date:          18.02.2011 14:06:30

Event ID:      9213

Task Category: Categorizer

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      xxx.local

Description:

A non-expirable message with the Internal Message ID 14297 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.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchangeTransport" />

    <EventID Qualifiers="49156">9213</EventID>

    <Level>2</Level>

    <Task>9</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2011-02-18T12:06:30.000000000Z" />

    <EventRecordID>119745</EventRecordID>

    <Channel>Application</Channel>

    <Computer>xxx.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data>14297</Data>

  </EventData>

</Event> 

 

Selamlar,

Murat 

Alıntı
Gönderildi : 18/02/2011 16:36
Hakan Uzuner
(@hakanuzuner)
Kıdemli Üye Yönetici

Merhaba

User Action Kısmına bakın

Details
Product: Exchange
Event ID: 9213
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: RetryCategorizationIfFailed
Message: A
non-expirable message with the internal message ID %1 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 Mail Flow Troubleshooter.
   
Explanation

This Warning event indicates that a
journal report that was sent to a journaling mailbox has been rejected.
The journal report has been resubmitted to the Submission queue for
categorization. This Warning event may be generated when an error is
encountered with the recipient configuration of the journaling mailbox.
After the recipient configuration of the journaling mailbox is
corrected, Microsoft Exchange Server 2007 automatically delivers the
journal reports to the journaling mailbox. The following conditions may
cause the journaling mailbox to become unavailable:

  • The journaling mailbox no longer exists.

  • The Hub Transport server is unable to access the Active Directory directory service.

  • The recipient object of the journaling mailbox in Active Directory is invalid.

  • The primary Simple Mail Transfer Protocol (SMTP) address of the specified recipient is invalid.

  • The SMTP address that is configured on the specified recipient is not unique.

  • Other recipient resolution, routing, or content conversion errors have occurred.

   
User Action

To resolve this warning, do the following:

  • Determine
    why the journaling mailbox is unavailable. You may be able to retrieve
    information about why the journal reports were rejected by running the
    following Exchange Management Shell command on the Hub Transport server
    that attempted delivery of the journal report:

    Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*<journaling mailbox SMTP address>*" } | Format-List

    This
    command retrieves all the messages that are currently waiting to be
    delivered to the journaling mailbox that you specify. For example, if
    the SMTP address of the journaling mailbox is journaling@contoso.com,
    you would use the following command:

    Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*journaling@contoso.com*" } | Format-List

    The LastError property of each message that is returned contains the reason the message was rejected.

  • Use the following corrective actions to resolve the most common issues that cause this warning:

    • Verify
      the recipient configuration information is correct. If the recipient's
      SMTP address was entered incorrectly, correct the SMTP address in the
      journal rule. Then, create a temporary mailbox with the previously
      entered incorrect SMTP address. This mailbox will accept the journal
      reports that are sent to the incorrect SMTP address. You can then
      forward these journal reports to the correct journaling mailbox, and you
      can delete the temporary mailbox.

    • Verify that no duplicate SMTP addresses are configured on recipients in your organization

    • Verify that there are no invalid characters in the SMTP address of the configured recipient.

    • Run the Dcdiag command line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name>
      at a command prompt on the Exchange server. Use the output of Dcdiag to
      discover the root cause of any failures or warnings that it reports.
      For more information, see Dcdiag at the Microsoft Windows Server TechCenter.

You
can also use an alternate journaling mailbox to help manage journal
reports that have been rejected. However, journal reports that have
already failed categorization prior to enabling the alternate journaling
mailbox are not redirected. For more information about how to configure
an alternate journaling mailbox, see How to Configure an Alternate Journaling Mailbox. For more information about journaling, see Overview of Journaling.

 

Danışman - ITSTACK Bilgi Sistemleri
****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen "çözüldü" olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

CevapAlıntı
Gönderildi : 18/02/2011 17:37
mrtsimsek
(@mrtsimsek)
Üye

Merhabalar,

Bu makaleyi forumda yazmadan önce uyguladım ancak herhangi bir değişiklik olmamıştı. hafta sonu sunucuyu restart ettim açıldığında Queue da bekleyen o iki mail ve 9213 event'i ortadan kayboldu. Ayrıca yanıt için teşekkür ederim.

 

Selamlar,
Murat 

CevapAlıntı
Gönderildi : 21/02/2011 20:42
Hakan Uzuner
(@hakanuzuner)
Kıdemli Üye Yönetici

Geçmiş olsun Murat bey, ayrıca geri dönüş için teşekkür ederim.

Danışman - ITSTACK Bilgi Sistemleri
****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen "çözüldü" olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

CevapAlıntı
Gönderildi : 21/02/2011 23:47
Paylaş: