none
How to find the folder in FID= RRS feed

  • Question

  • I have been looking at the error:
    As part of updating a message (MID=1-28DFDB7165) in a folder (FID=ad-DE359) many search folder links were also updated.

    I'm not asking about this  error specifically, I'm asking how do I find this folder?  If this information is offered in the log file, isn't there a way to find the folder that the log is referencing?

    Friday, October 14, 2011 7:37 PM

Answers

  • On Fri, 14 Oct 2011 19:37:55 +0000, The_Messenger wrote:
     
    >
    >
    >I have been looking at the error: As part of updating a message (MID=1-28DFDB7165) in a folder (FID=ad-DE359) many search folder links were also updated.
    >
    >I'm not asking about this error specifically, I'm asking how do I find this folder? If this information is offered in the log file, isn't there a way to find the folder that the log is referencing?
     
    Without having to deal with EWS and writing your own code, the easiest
    way is to dismount the database and run:
     
    isinteg -dump [-l logfilename]
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Xiu Zhang Monday, October 17, 2011 5:48 AM
    • Marked as answer by Xiu Zhang Friday, October 21, 2011 9:21 AM
    Friday, October 14, 2011 9:52 PM
  • On Mon, 24 Oct 2011 15:41:28 +0000, The_Messenger wrote:
     
    >given the difficulty of dismounting a db, I was looking for way to do this without a dismount. I think I'm either chasing an EAS connection or possibly someone actually has 127 search folders.
     
    I haven't tried this myself, but:
    http://www.devnewsgroups.net/exchangedev/t53740-decoding-fid-mid-values-event-9555.aspx
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by The_Messenger Friday, December 2, 2011 6:58 PM
    Tuesday, October 25, 2011 2:09 AM
  • Hello!

    I was able to get the mailboxes that were causing these events this way.
    So I did manage to find the mailboxes, but not the exact messages yet..
    So I can confirm the post above from Rich does work to find the value.

    (reference : http://messagingnetwork.blogspot.com/)

    Go to
    PFDAVadmin
    when connect choose "mailboxes"

    Tools
    Options
    Enable logging to file - check box

    Tools
    Export properties
    Unmark all and mark only:
    PR_Display_Name: 0x39000003
    ptagFID: 0x67480014

    Export to the .txt file.
    open .txt file and use Ctrl+F to find folder (use FID number from Error Event ) when you find folder you find user mailbox.

    • Marked as answer by The_Messenger Friday, December 2, 2011 9:07 PM
    Monday, November 28, 2011 2:03 PM

All replies

  • On Fri, 14 Oct 2011 19:37:55 +0000, The_Messenger wrote:
     
    >
    >
    >I have been looking at the error: As part of updating a message (MID=1-28DFDB7165) in a folder (FID=ad-DE359) many search folder links were also updated.
    >
    >I'm not asking about this error specifically, I'm asking how do I find this folder? If this information is offered in the log file, isn't there a way to find the folder that the log is referencing?
     
    Without having to deal with EWS and writing your own code, the easiest
    way is to dismount the database and run:
     
    isinteg -dump [-l logfilename]
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Xiu Zhang Monday, October 17, 2011 5:48 AM
    • Marked as answer by Xiu Zhang Friday, October 21, 2011 9:21 AM
    Friday, October 14, 2011 9:52 PM
  • Rich,

    given the difficulty of dismounting a db, I was looking for way to do this without a dismount.  I think I'm either chasing an EAS connection or possibly someone actually has 127 search folders. 

    Monday, October 24, 2011 3:41 PM
  • On Mon, 24 Oct 2011 15:41:28 +0000, The_Messenger wrote:
     
    >given the difficulty of dismounting a db, I was looking for way to do this without a dismount. I think I'm either chasing an EAS connection or possibly someone actually has 127 search folders.
     
    I haven't tried this myself, but:
    http://www.devnewsgroups.net/exchangedev/t53740-decoding-fid-mid-values-event-9555.aspx
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by The_Messenger Friday, December 2, 2011 6:58 PM
    Tuesday, October 25, 2011 2:09 AM
  • Hello!

    I was able to get the mailboxes that were causing these events this way.
    So I did manage to find the mailboxes, but not the exact messages yet..
    So I can confirm the post above from Rich does work to find the value.

    (reference : http://messagingnetwork.blogspot.com/)

    Go to
    PFDAVadmin
    when connect choose "mailboxes"

    Tools
    Options
    Enable logging to file - check box

    Tools
    Export properties
    Unmark all and mark only:
    PR_Display_Name: 0x39000003
    ptagFID: 0x67480014

    Export to the .txt file.
    open .txt file and use Ctrl+F to find folder (use FID number from Error Event ) when you find folder you find user mailbox.

    • Marked as answer by The_Messenger Friday, December 2, 2011 9:07 PM
    Monday, November 28, 2011 2:03 PM
  • Good ideas from this thread.

    I was able to use pfdavadmin to match the fid with a user mailbox.  I had 6 fid references in my event logs so I moved those 6 to a single database, just in case I had to run isinteg it would only be once.  But after determining which mailboxes had the issue I was able to resolve it by running "outlook /cleanfinders" on each mailbox. 

     

    I misunderstood the error also.  I thought there were mulitple search folders, the error clearly states search folder links.  My issues resulted from users who had a lot, I mean thousands, of unread messages and then they had clicked on the unread email search folder.  So the ultimate resolution for my situation will be for users to not have so much unread e-mail.

    Thanks to all who took part in this, there was good help here.

    Friday, December 2, 2011 6:58 PM