Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Oulook connection to DAG Mailbox Servers Public Folder Database disconnects and asks for Password / Restart of RPC Service on Mailbox Server helps

Con risposta Oulook connection to DAG Mailbox Servers Public Folder Database disconnects and asks for Password / Restart of RPC Service on Mailbox Server helps

  • Tuesday, May 22, 2012 10:07 AM
     
     
    Sign In to Vote
    0

    Hello together, 

    we have the following problem: 

    Exchange 2010 DAG with 2 Mailbox Servers in DAG and 2 CHT Servers. On each Mailbox Server is one Public Folder Database.
    All MailboxDatabases have the Same Publicfolder Database to use PFD01.

    The Problem: 
    After some time, Mostly more than one week, Outlook asks for Password on all Users/Workstations. When we check the Outlook Connection Monitor we see that the Public Folder Database connection is "connecting....". 

    So the Problem is server side => we checked the "Microsoft Exchange RPC Client Access" -> it was running. But not working.

    After Restart of this service all connections work again without any Problems. Hopefully for more than the next 4 days... 

    Are there any known bugs or any possibilities to debug this ?

    i'm looking forward to the next patch day mid of june to come to SP2 UR 2 / Acutually we still use SP1 UR5.

    thanks for help. 

    Best 

    Martin


     

All Replies

  • Tuesday, May 22, 2012 10:11 AM
     
     
    Sign In to Vote
    0

    Is it happening to all the version of outlook clients or just 2003?
    I hope Public folder database is mounted.

    Were their any recent changes on the server?

    Gulab Prasad,
    My Blog | Z-Hire Employee Provisioning App

     
  • Tuesday, May 22, 2012 10:13 AM
     
     
    Sign In to Vote
    0

    Public Folder Database is Mounted. All Clients are Outlook 2010.

    there were no reasonable changes i know from... 

     
  • Tuesday, May 22, 2012 10:18 AM
     
     
    Sign In to Vote
    0

    If its Outlook 2010 than it's nothing to do with Public Folder, Public Folder is showing connecting is so other issue.
    Run the Test E Mail Autoconfiguration... on the outlook client and post the result.

    It seems, issue is with autodiscover...

    What happens to OWA?

    Gulab Prasad,
    My Blog | Z-Hire Employee Provisioning App

     
  • Tuesday, May 22, 2012 10:21 AM
     
     
    Sign In to Vote
    0

    Of course Outlook 2010 has something to do with that. 

    Outlook 2010 makes a direct connection with TCPIP / MAPI to the Mailbox Server hosting this Public Folder Database. 

    Autoconfiguration is working fine! no Problems... 

    Besides: Autodiscover/Autoconfiguration is handeled by the CHT Servers. Not from MBX Servers. The Problem is solved after Restart of the RPC Service on the MBX Server... 

    OWA is working... 
    • Edited by -M-T- Tuesday, May 22, 2012 10:24 AM
    •  
     
  • Tuesday, May 22, 2012 10:31 AM
     
     
    Sign In to Vote
    0

    My Friend, I never said it has nothing to do with Outlook 2010.
    I said it's nothing to do with Public Folder Database (Password Issue)

    Now, you said it's working fine after restarting the RPC Client Access Service. Is it still showing Connecting to Public Folders?

    Gulab Prasad,
    My Blog | Z-Hire Employee Provisioning App

     
  • Tuesday, May 22, 2012 10:33 AM
     
     
    Sign In to Vote
    0

    Correct it has to do with the "Microsoft Exchange RPC Client Access-Service" on MBX Server hosting the PDF01 Database. 

    After Restarting the RPC Service Outlook shows the Status "connected" with TCPIP to the Public Folder Database (Server)

     
  • Tuesday, May 22, 2012 10:47 AM
     
     
    Sign In to Vote
    0
    Application lot should get some information.
    I would suggest to bump the diagnostics logging on Public Folder and RPC Client Access Service.

    Gulab Prasad,
    My Blog | Z-Hire Employee Provisioning App

     
  • Tuesday, May 22, 2012 11:22 AM
     
     
    Sign In to Vote
    0

    Thats what i thought. In the Application Log on MBX Server i cant see anythings any problems. 

    Diagnostic logging: 

    Which Attributes whould you activate ?

     
  • Tuesday, May 22, 2012 11:56 AM
     
     
    Sign In to Vote
    0

    Wow - This is the exact issue we are experiencing in our organization. I have been utilising Microsoft Support in a effort to resolve this the last two days, but have found no resolution. We are on SP2 RU1. For no reason the Public Folders disconnect, causing either Outlook 2003/2010 to hang, until the user restarts Outlook, and then they get prompted for a user id and password. The public Folder connects, but goes to our DR replicated site or the 2007 server we will be decommisioning soon. We cant stop the RPC Client Access Service, so to get it working again we have to switchover to DR, restart server, switch back. The worse thing is the change that Microsoft recommended (a change to Folder Hierarchy in adsi edit) is now causing the problem to happen every half hour or so now!

    Will keep an eye on this thread and if we can get it resolved will post details.

     
  • Tuesday, May 22, 2012 12:03 PM
     
     
    Sign In to Vote
    0

    Hi teaseler1, thanks for your reply. Sounds exactly like the same issue we have. 

    i would be delighted if you keep us informed. As soon as i will have the actual service pack my next step would also be opening a Call with Microsoft. 

    Why can you not stop/restart the RPC Service ?

    good luck in your research... 

     
  • Tuesday, May 22, 2012 11:12 PM
     
     
    Sign In to Vote
    0

    Hi -M-T-, the error that I get when attempting to restart the RPC Client Access Service is "The service did not respond to the start or control request in a timely fashion". I only get this error when the Public Folder is in a disconnected state. If the Public Folder is working, then this service will restart without a problem.

     
  • Wednesday, May 23, 2012 9:44 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Does this issue affect all the public folder users?

    Do you have CAS array configured?

    Please try to check RPC Client Access Protocol Logging on the CAS server, which is enabled by default

    The path is "%ExchangeInstallDir%\Logging\RPC Client Access\"

    Exploring Exchange 2010 RPC Client Access service

    http://blogs.technet.com/b/exchange/archive/2010/05/20/3409978.aspx

    Xiu Zhang

    TechNet Community Support

     
  • Thursday, May 24, 2012 1:23 PM
     
     
    Sign In to Vote
    0

    Hi Xiu, 

    yes it affects all users connecting to this public folder database.

    I have CAS Array configured. When i check this logs: for what should i search ?

    Why should i look on the CAS Servers ? The Problem is on the RPC Service on Mailbox Server... 

    Best, Martin

     
  • Friday, May 25, 2012 7:14 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    That is my mistake. It should on Mailbox server role.

    Since we always get connecting for public folder from outlook, I think there should be something wrong with rpc client access, please try to check if we have error or failed from the logging.

    Xiu Zhang

    TechNet Community Support

     
  • Friday, May 25, 2012 5:23 PM
     
      Has Code
    Sign In to Vote
    0

    The only error i can find is:

    OUTLOOK.EXE,14.0.6117.5001,Cached,,,ncacn_ip_tcp,,,-2147024809 (rop::InvalidParam),00:00:00,,RopHandler: IncrementalConfig: [RopExecutionException] Unable to resolve a PropertyTag.. Error code = InvalidParam -> [ResolvePropertyDefinitionException] Can't resolve all property tags to property definitions. Unresolvable property tag = 1744896000.

     
  • Monday, May 28, 2012 5:50 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Please have a look at the article below:

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

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

    Xiu Zhang

    TechNet Community Support

     
  • Tuesday, May 29, 2012 1:33 PM
     
     
    Sign In to Vote
    0

    Hello Xiu,

    this problem should be resolved in SP1 Update Rollup 4 (http://support.microsoft.com/kb/2579150/de) 

    i have update rollup 5 so i think this cannot be our solution. Did you ?

    Best, 

    Martin

     
  • Wednesday, May 30, 2012 3:21 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    I know that the hotfix has been included in rollup4, please try to install hotfix 2535105 seperatlly again.

    Xiu Zhang

    TechNet Community Support

     
  • Tuesday, June 26, 2012 11:53 PM
     
     
    Sign In to Vote
    0

    Hi

    Just getting back to you regarding this. I think we have this resolved now as the problem hasnt come back now for a week since we have made the change.

    We did traces on Outlook, the Network and Exchange performance. When the problem arose the Outlook trace was trying to connect to the correct database, however was getting details "The Server is too Busy"

    Our problem was due to performance on the Exchange server. More specifically due to storage disk performance. When I built our Exchange 2010 environment, we had a external Microsoft Partner advise that we can use cheaper/slower disks. However in our environment this is not the case.

    Check out Disk Read and Write response times, Disk Queue Length and disk active times. Before I moved the databases, these measurements were terrible. I moved the databases to a mix of SAS and ssd drives and theses meaurements are now in a much better state.

    Here is a good article on this for you:

    http://www.techrepublic.com/blog/datacenter/use-resource-monitor-to-monitor-storage-performance/4233

    But I would deffinately check the performance of your servers as this could more than likely be the issue.

    Let me know how you go!

     
  • Wednesday, August 01, 2012 6:41 PM
     
     Answered
    Sign In to Vote
    1

    i opened a microsoft premier support ticket today because in the end i had this issue every hour... 

    after a few hours it was clear that it is a Bug. Microsoft has a KB Article for that:

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

    http://support.microsoft.com/default.aspx?scid=kb;en-US;2535105

    After inserting the Regkey "DisableAvailabilityServiceCalls" on the Mailbox Server hosting the Public Folder Database the Problem is solved!! :)

    Best, 

    Martin

    • Marked As Answer by -M-T- Wednesday, August 01, 2012 6:41 PM
    •