Unanswered Public Folders stop working

  • Tuesday, May 15, 2012 8:54 AM
     
     

    Hi, 

    this is a strange issue about Public Folders on a DAG in Exchange 2010.
    Public Folders run on one node of a DAG in Exchange 2010 SP2 RU2, suddenly, access from a client (Outlook) to this Public Folders isn't working anymore.  As a solution my client restarts the Exchange RPC-service.

    However, when we search the Event log, I can't find any error stating the connection is saturated nor broken, nor is there a problem with generating access to Public Folders.

    Somebody has an idea?

All Replies

  • Tuesday, May 15, 2012 5:53 PM
    Moderator
     
     
    HOw much memory in the PF server?
  • Tuesday, May 22, 2012 7:36 AM
    Moderator
     
     

    Hi ,

    Please check the permission of public folder.

    And please also run Exchange BPA tool to check the health of exchange.

    If it has any error, please post here.

    Exchange Public Folder Troubleshooting Resources:

    http://technet.microsoft.com/en-us/library/bb123804(v=exchg.65).aspx

    please also test access public folder via OWA.

    And please check IIS log. Post the error.


    Wendy Liu

    TechNet Community Support


  • Thursday, May 24, 2012 7:42 PM
     
     

    Interesting, we started seeing the exact same problem. Works fine via OWA, but outlook clients that directly connect to the mailbox server start failing - seemingly almost once a day. We restart the RPC service and it works. This started happening right after UR2.

    Running some perfmon following this - http://msexchangeguru.com/2011/02/27/rpc-issues/

    So far I haven't seen enough data from this to indicate a problem like filling RPC threads.

    BPA is clean - what specifically should I be looking for in the IIS logs?

    Memory is great on this server - 64GB.

  • Thursday, May 24, 2012 8:00 PM
    Moderator
     
     

    Interesting, we started seeing the exact same problem. Works fine via OWA, but outlook clients that directly connect to the mailbox server start failing - seemingly almost once a day. We restart the RPC service and it works. This started happening right after UR2.

    Running some perfmon following this - http://msexchangeguru.com/2011/02/27/rpc-issues/

    So far I haven't seen enough data from this to indicate a problem like filling RPC threads.

    BPA is clean - what specifically should I be looking for in the IIS logs?

    Memory is great on this server - 64GB.

    64GB is probably, well, too much unless you are running other apps on the server. Is this a physical box?

  • Thursday, May 24, 2012 10:37 PM
     
     
    Yep, physical...no other apps. And yes, a lot of memory and problem only cropped up after UR2, at least from what we saw.
  • Tuesday, May 29, 2012 11:57 AM
     
     

    This is a virtual server with the PF-database, at the moment 24GB memory, reserved for this machine.

    Still having the problem... .  BPA is also as clean as it can get :-)


  • Thursday, May 31, 2012 9:29 AM
    Moderator
     
     

    Hi,

    I find the KB for Exchange 2010 SP1, and I don’t sure if the SP2 have already be fixed.

    The detail for your reference.

    Outlook client applications cannot connect to public folders after you install Exchange Server 2010 SP1 :

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


    Wendy Liu

    TechNet Community Support

  • Monday, June 04, 2012 7:37 PM
     
     
    Seems like this would be fixed with SP2 or one of the update rollups - any one answer that? The KB does fit the symptoms we have seen.
  • Tuesday, June 05, 2012 2:49 AM
    Moderator
     
     

    Hi ,

    Does only one client can’t access the public folder ?

    What happens on other users ?

    Please “Test E-mail Autoconfiguration” when it can’t access the public folder.

    Check the connection with public folder via “Connection Status” when it can’t get access.

    And check if the Event Viewer in Exchange.


    Wendy Liu

    TechNet Community Support

  • Tuesday, June 05, 2012 3:46 PM
     
     
    No, it is all users when it breaks. And when I check the auto-config you can see the server stops responding. For example, a user that lives on a different mailbox server than the public folders will show a connection for public folders to the server he is on - the re-direct never completes. Basically everything on the public folder server looks fine, but no one can directly connect to it for public folders.