サインイン
 
ホームライブラリサポート情報ダウンロードラーニングセミナーフォーラムサイトマップ
マイクロソフトの技術情報ポータル >
> 
> 
Exchange 2010 Event 8010 Defer message

回答の候補 Exchange 2010 Event 8010 Defer message

  • 2012年5月8日 1:50
     
     
    サインインして投票
    0

    Dear

    Recently, I got Event 8010 from Exchange 2010. I found the Journaling mailbox keep deferring the message with following error description:-

    400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; Failed to process message due to a permanent exception with message Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by a retry response because the message was marked for retry if rejected. [Stage: CreateMessage],400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; Failed to process message due to a permanent exception with message Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by a retry response because the message was marked for retry if rejected. [Stage: CreateMessage]

    How Should I stop the Exchange defer this message and either to stop generate this event log?

     

すべての返信

  • 2012年5月9日 9:21
    モデレータ
     
     
    サインインして投票
    0

    Hello,

    This is a known issue, and will be fixed in a futrue update.

    Thanks,

    Evan

    Evan Liu

    TechNet Community Support

     
  • 2012年5月11日 14:50
     
     
    サインインして投票
    0

    Hi Evan,

    Can you explain a bit more please?
    We also have this problem since a month.
    Is this due to an update? If so, which one?

    From where do you have this information?

    Is there a technical document or an explanation which I can send to our customer about this?

    Kind Regards,
    Andy

     
  • 2012年5月14日 1:59
    モデレータ
     
     
    サインインして投票
    0

    Sorry, based on our policy, I cannot post the detail information on the forum.

    Thanks for understanding.

    Evan

    Evan Liu

    TechNet Community Support

     
  • 2012年5月29日 16:00
     
     
    サインインして投票
    0

    Evan,

    Have you heard anything about this bug?  We are having this issue with journaling and the same 8010 error message as the first post.  It seems like this is the most up-to-date answer I could find so I was just curious if there was any more available info.

    Thanks,

    Rob

     
  • 2012年5月31日 7:52
     
     
    サインインして投票
    0

    Same problem here...  It does not happen to all the emails only some handful will be stuck in the queue trying to be delivered to Journal mailbox.  Below is the exact error message:

    LastError: 400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; F
                        ailed to process message due to a permanent exception with message Property: [0x67480014] FID, Prop
                        ertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480
                        014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by
                         a retry response because the message was marked for retry if rejected.

     
  • 2012年6月12日 20:55
     
     回答の候補
    サインインして投票
    0
    It's definitely a bug, confirmed by Microsoft. Supposed to be fixed in SP2 RU4 but there's no ETA for that at this time
    • 回答の候補に設定 waddyjohn 2012年6月12日 20:59
    •  
     
  • 2012年7月5日 20:32
     
     
    サインインして投票
    0

    Yet another bug? That prevents Journaling from working properly? And no explanation, lest of all a solution. Just 'you got it, you eat it'. As a matter of official policy. 

    Nice. 

     
  • 2012年8月13日 14:17
     
     
    サインインして投票
    0
    Any updates on this yet from anyone ? We are having the same issue intermittently and it has brought down Exchange twice in 2 months.