locked
corrupt system folder database in Exchange 2003 RRS feed

  • Question

  • Hello,

    for exchange 2003 in mixed environment (Exchange 2010 implemented, but not active) replication of system folders fails (e.g. Free/busy, offline address book,       
    organizational forms library, etc..)  - we see:

     Type        Warning                                        
     Source      MSExchangeIS Public St                         
     Category    Replication Errors                             
     Event ID    3092                                           
     Description Error 0x8004010f occurred while processing a replication event.                             
                                                                
     Type        Warning                                        
     Source      MSExchangeIS Public St                         
     Category    Replication Errors                             
     Event ID    3085                                           
     Description Error 0x8004010f occurred while generating an  
                 outgoing replication message.                  

      Also event 3092 we see,  

    Run an isinteg against the public folder stores on each         
    of the servers, the only error is the replication test fails                                                                 

    We tested following:

    · New content created in a new public folder will successfully  
    replicate to other Exchange servers.                                    
                                                                            
    · Old content moved into a new public folder will successfully  
    replicate to other Exchange servers.                                    
                                                                            
    So we believe,  owning Folders table in the public      
    folder store has become corrupt.                                       

    What is best way to proceed?

    Because this are system folders, it is impossible to move then to another PF (tree).

    Thanks - Katrin


    Katrin

    Wednesday, August 15, 2012 10:14 AM

Answers

All replies

  • have you seen this article?

    http://support.microsoft.com/kb/822444

    Wednesday, August 15, 2012 11:00 AM
  • Hello Ishmael,

    Thanks for the answer - but I have some additional questions about this article:

    What will this do to users free/busy information that is already published? It will be deleted and they will need to re-publish this information?

    What would be the best way of re-publishing this information?

    thanks - Katrin


    Katrin

    Wednesday, August 15, 2012 12:54 PM
  • hi katrin

    yes, i expect it will be deleted. the normal way around this would be to replicate it to another public folder server, but this might not be the answer you're looking for...

    the good news is that free/busy information is automaticall generated in its entirety every fifteen minutes by outlook, and the folder only contains a month's worth of data, so in a very short space of time the folder will be mostly repopulated without any intervention on your part.

    see here:

    http://technet.microsoft.com/en-us/library/aa996946%28v=exchg.65%29.aspx

    and also here:

    http://www.msexchange.org/tutorials/freebusy-folders-exchange-server-2003-depth.html

    • Proposed as answer by Terence Yu Thursday, August 16, 2012 7:01 AM
    • Marked as answer by Terence Yu Thursday, August 23, 2012 6:39 AM
    Wednesday, August 15, 2012 1:08 PM
  • Hi
       If post ishelpful to you, please mark the post.

    Terence Yu

    TechNet Community Support


    • Edited by Terence Yu Friday, August 17, 2012 5:56 AM
    Friday, August 17, 2012 5:56 AM
  • Hello Ishmael,

    The actions were applied - it made no difference, it was double checked that the instruction was followed correctly.
    The process did not remove any of the old system folders from the Exchange servers.  Replication is still not occurring.

    sorry for delay - Katrin


    Katrin

    Wednesday, September 5, 2012 10:06 AM
  • hmmm. interesting. do you have another public folder server in the same administrative group? if so you could make sure that all your non-system folder data is replicated, and then delete the public folder store on the troublesome server.

    if the store won't delete you *could* remove it using adsiedit, and then follow the article given previously to create the system folders on one of the other replicas in the same admin group.

    Thursday, September 6, 2012 7:51 AM