none
A folder is being scoped by a search which no longer exists. This may result in failures or errors when attempting to update the folder contents on exchange 2010 sp1 ru5 RRS feed

  • Question

  • hi

    this morning i started to receive the following error in the application log (exchange 2010 sp 1 ru5)

    Warning EventType=2

    SourceName=MSExchangeIS Mailbox Store

    EventCode=10033

    Message=A folder is being scoped by a search which no longer exists. This may result in failures or errors when attempting to update the folder contents. If this message continues to persist for this mailbox, moving the mailbox to a different database may resolve the issue.

    Database: UK-DB-01
    Folder: [MBX:username][foldername]
    MsgHeader ID: 2a51-238B31
    Folder ID: 1-EB23E
    Search Folder ID: 1-114829

    it seems to repeat itself quite often and lots of different subfolders in the users mailbox are being referenced

    any idea how this can be resolved?

    many thanks

     

    Tuesday, January 17, 2012 1:04 PM

Answers

  • Hi elbutre,

    Per your description, there must be some corrupted hierarchy in the mailbox. And if you move the mailbox  to other database or use new-mailboxrepairrequest, the corrupted mailbox would be repaired.

    Regards!

    Gavin

    TechNet Community Support

    • Marked as answer by Gavin-Zhang Tuesday, February 7, 2012 6:18 AM
    Thursday, February 2, 2012 7:21 AM
  • Hi,

    Did you try to move the mailbox to a different database as the message suggests?

    Leif

    • Marked as answer by Gavin-Zhang Tuesday, February 7, 2012 6:18 AM
    Tuesday, January 17, 2012 2:44 PM
  • Hi elbutre,

    If you want to confirm the the move process, it is better to set the logging level for the mailbox move, and then check it.

    Regards!


    Gavin

    TechNet Community Support

    • Marked as answer by Gavin-Zhang Tuesday, February 7, 2012 6:18 AM
    Friday, February 3, 2012 5:33 AM

All replies

  • Hi,

    Did you try to move the mailbox to a different database as the message suggests?

    Leif

    • Marked as answer by Gavin-Zhang Tuesday, February 7, 2012 6:18 AM
    Tuesday, January 17, 2012 2:44 PM
  • not yet, am going to do that tonight. i was hoping there is another solution. not a big fan of moving mailboxes. our blackberry server does not handle it very well and it is a bit of a hassle but i guess better than having these errors appear every couple of minutes

    i will let you know how it goes

    Wednesday, January 18, 2012 8:50 AM
  • Hello,

    I have been seeing this issue as well on Exchange 2010 SP1 RU6.  Quite some time back I did move the mailbox but it did not stop those warning messaegs.  I was wondering if there is any other way to resolve this issue.

    Event id 10033 gives this information where it clearly gives mailbox and folder name.  But I could not able to find any message with the header ID indicated in the event id message.  I was thinking it might help to resolve this issue.

    Folder: [MBX:Mailbox Name][Folder Name]

    MsgHeader ID: 172b-1CB2E77

    Folder ID: 3-D045DD1

    Search Folder ID: 1-252CBA

    ==============

    Helo elbutre,

    Please let us know if moving mailbox worked for you.

    Thanks,


    Raman
    Thursday, January 19, 2012 9:20 PM
  • Hi Raman,

    I would suggest that you could update exchange to sp2, and then make some tests.

    Regards!

    Gavin

    TechNet Community Support

    Friday, January 20, 2012 6:14 AM
  • Hello Gavin,

    Thanks for your response.  I am seeing this issue even before SP1.  This problem is still there post SP1. 

    I have also started to wonder if this is a false alert.

    Although, I have not started to plan sp2 yet.

    Thanks,

     


    Raman
    Friday, January 20, 2012 8:10 PM
  • hi

    in my case this problem started when i setup a new profile on the users desktop. I also noticed this only seems to happen during office hours because the errors stopped after 9pm and started again at around 6am.

    today i turned off the desktop and this reduced the number of warnings but they have not gone away completely so it is not all related to the users desktop (but turning off the desktop has reduced number of events dramatically)

    the user also has a blackberry and perhaps this device is causing the problem for the remainder of the events?

    i will move the users mailbox to another database on Sunday evening and see if that makes a difference.

    is anyone else seeing these events happening only during particular times of day and for instance not after working hours ?

    maybe it is not a database issue but a client issue and it is just a matter of figuring out which client is causing the problem and fixing that rather than moving mailboxes?

    Wednesday, January 25, 2012 12:54 PM
  • Hi raman03,

    How about to use new-mailboxrepairrequest to repair the mailbox, in my opeinion, there seems some corruption about the mailbox, some information for you:
    http://blogs.technet.com/b/exchange/archive/2010/08/23/3410708.aspx
    Or you could use the MFCMAPI to check the folder according to the folder id "Folder ID: 3-D045DD1", confirm the folder whether exists, you could delete it if the folder is no used.

    Regards!

    Gavin

    TechNet Community Support

    Monday, January 30, 2012 8:33 AM
  • i have just moved the mailbox to another DB and the erros have gone away for now. will check again tomorrow but first signs are good

    the odd thing was that hte mailbox move took nearly 6 hours to complete (2gb in size)

    it took 10 mins to get to 20%m then 2 hours before it started to move from 20% to 95% which took just over an hour

    it was then stuck at 95% for over 2 hours, and then all of a sudden completed (i turned of our CDP backup of the exchange store and all of a sudden the mailbox move completed, could be coincidence)

    no corrupted items were found during the move and no errors came up in the event log

    regards

    Wednesday, February 1, 2012 1:05 PM
  • Hi elbutre,

    Per your description, there must be some corrupted hierarchy in the mailbox. And if you move the mailbox  to other database or use new-mailboxrepairrequest, the corrupted mailbox would be repaired.

    Regards!

    Gavin

    TechNet Community Support

    • Marked as answer by Gavin-Zhang Tuesday, February 7, 2012 6:18 AM
    Thursday, February 2, 2012 7:21 AM
  • since moving the mailbox i have had no more warning event entries in the event log of the mailbox server
    Thursday, February 2, 2012 3:17 PM
  • Hi elbutre,

    If you want to confirm the the move process, it is better to set the logging level for the mailbox move, and then check it.

    Regards!


    Gavin

    TechNet Community Support

    • Marked as answer by Gavin-Zhang Tuesday, February 7, 2012 6:18 AM
    Friday, February 3, 2012 5:33 AM
  • Hi raman03,

    How about to use new-mailboxrepairrequest to repair the mailbox, in my opeinion, there seems some corruption about the mailbox, some information for you:
    http://blogs.technet.com/b/exchange/archive/2010/08/23/3410708.aspx
    Or you could use the MFCMAPI to check the folder according to the folder id "Folder ID: 3-D045DD1", confirm the folder whether exists, you could delete it if the folder is no used.

    Regards!

    Gavin

    TechNet Community Support


    The repair request fixed a couple of these for me, thanks for the info Gavin :)

    Stew

    Wednesday, July 18, 2012 7:04 AM
  • I've got the same errors (3rd round now) on a shared mailbox in 2010 SP3.

    We've moved the mailbox twice, the errors would disappear, but within a couple of weeks it came back again.


    DQ

    Wednesday, May 21, 2014 3:12 PM
  • I had the same error.

    I used

    New-MailboxRepairRequest -Mailbox <Emailaddress> -CorruptionType SearchFolder

    After a few seconds the problem was solved.

    The other options are also usefull.

    Greetings - Leo


    • Edited by Leonid-S Thursday, November 6, 2014 2:21 PM
    • Proposed as answer by Ash.Powell Wednesday, April 22, 2015 1:15 AM
    Thursday, November 6, 2014 2:20 PM