none
Windows XP clients cannot connect to public folders after installing CU7 RRS feed

  • Question

  • Hello!

    Yesterday I installed CU7 on our Exch2013 servers. We have 3 CAS and 7 Mailbox servers. One of Mailbox servers used for PublicFolders databases and mailboxes. All is fine except Windows XP clients. They're cannot connect to public folders. When users try to expand PF three they're receiving an error "Cannot expand folder. Configuration not set". Office 2007 and 2010. On Win7 and 8.1 all is OK (office 2007, 2010 and 2013).

    Friday, December 12, 2014 10:03 AM

Answers

  • Hi woo1fer,

    I checked in our database and didn't find any clue that it's a known issue in Exchange 2013 Cu7, so we are not sure whether a fix will be released. And as XP have exceeded the support life cycle, we strongly recommend to upgrade the client to supported version. Thanks for your understanding.

    Regards,

    Eric Zou

    Wednesday, December 24, 2014 10:49 AM
    Moderator

All replies

  • Hi W001fer, 

    Thanks for the question.

    The issue you encountered is: XP Clients cannot connect to the public folder database after applying the last RU7. The impacts are:

    1. All the internal and external XP clients.

    2. All the Outlook versions.

    If there are any misunderstanding, please let me know.

    Based on my experience, I have seen a lot of Outlook Anywhere issues on Windows XP machines due to authentication issues. In order to narrow down this cause, would you please do me a favor to have a test on one of your XP machine and change authentication type to Basic. Can you access the public folder successfully?

    In order to do more research on this case, could you please send the following log files to ibsexc@microsoft.com

    1. Get-OutlookAnywhere |FL
    2. Get-ExchangeCertificate |FL
    3. APP log if any contains the related error event ID about this issue.

    Thanks,

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Simon Wu
    TechNet Community Support

    Monday, December 15, 2014 8:37 AM
    Moderator
  • Hello, Simon!

    Thank you for reply! Changing authentication type didn't make any effect. There aren't any errors about this issue in App or System log on all of my servers. On which server should I execute Get-ExchangeCertificate?

    Monday, December 15, 2014 11:29 AM
  • Hi,

    On the CAS server that your Outlook Anywhere proxy server name refers to. One more helpful thing is to collect the RPCTrace log on a problematic XP client.

    1) You need to get the RPCTrace tool from Microsoft Support. It’s generally a Zip file contain 4 files: emsmdb32.dll, olmapi32.dll,disabletrace.reg,trancetofile.reg. Or you can send an email to ibsexc@microsoft.com with the thread url. I will try to send the file to you.

    When you get the tool, locate C:\Program Files\Microsoft Office\Office12, please rename the 2 dll files “emsmdb32.dll, olmapi32.dll” to .bak file. Then copy trace-enabled version of these 2 files (in the Zip file you download) to this folder.

     

    2) Run the registry file attached “Tracetofile.reg”, then click “OK”.

    3) Then start Outlook, type the Logon credentials. Choose the problematic user’s Outlook profile which could steadily reproduce this problem.

    4) Reproduce this problem. Let me know the exact time.

    5) Collect RPC trace log in C:\tmp\rpctrace.log.

    6) Restore the 2 Outlook dll files that we changed in step 1). And run disabletrace.reg to disable the trace.

    Thanks,

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Simon Wu
    TechNet Community Support

    Tuesday, December 16, 2014 2:50 AM
    Moderator
  • Hello, Simon!

    I couldn't send an email to this email address.

    Delivery has failed to these recipients or groups:

    ibstfex@microsoft.com
    Your message can't be delivered because delivery to this address is restricted to authenticated Sender.

    Diagnostic information for administrators:

    Generating server: DM2PR0301MB1215.namprd03.prod.outlook.com

    ibstfex@microsoft.com
    Remote Server returned '550 5.7.12 RESOLVER.RST.SenderAuthenticated; Delivery restriction check failed as sender not authenticated'

    Original message headers:

    Received: from BN3PR0301CA0060.namprd03.prod.outlook.com (25.160.152.156) by
     DM2PR0301MB1215.namprd03.prod.outlook.com (25.160.219.16) with Microsoft SMTP
     Server (TLS) id 15.1.31.17; Tue, 16 Dec 2014 08:11:25 +0000
    Received: from BY2FFO11FD039.protection.gbl (2a01:111:f400:7c0c::163) by
     BN3PR0301CA0060.outlook.office365.com (2a01:111:e400:401e::28) with Microsoft
     SMTP Server (TLS) id 15.1.36.22 via Frontend Transport; Tue, 16 Dec 2014
     08:11:24 +0000
    Received: from DUB004-OMC3S31.hotmail.com (157.55.2.40) by
     BY2FFO11FD039.mail.protection.outlook.com (10.1.14.224) with Microsoft SMTP
     Server (TLS) id 15.1.26.17 via Frontend Transport; Tue, 16 Dec 2014 08:11:24
     +0000
    Received: from DUB121-W25 ([157.55.2.9]) by DUB004-OMC3S31.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);
    	 Tue, 16 Dec 2014 00:11:22 -0800
    X-TMN: [5aTfT+RHpHoe1idyLIy0g0xclDul1vu4]
    X-Originating-Email: [dfedorenkov@hotmail.com]
    Message-ID: <DUB121-W253DFEFF4B783524F59286A86C0@phx.gbl>
    Return-Path: dfedorenkov@hotmail.com
    Content-Type: multipart/alternative;
    	boundary="_776aa1af-f841-4ec7-b88e-5ca0f636d127_"
    From: Denis Fedorenkov <dfedorenkov@hotmail.com>
    To: "ibsexc@microsoft.com" <ibsexc@microsoft.com>
    Subject: RPCTrace tool request
    Date: Tue, 16 Dec 2014 11:11:22 +0300
    Importance: Normal
    MIME-Version: 1.0
    X-OriginalArrivalTime: 16 Dec 2014 08:11:22.0635 (UTC) FILETIME=[E12295B0:01D01907]
    X-EOPAttributedMessage: 0
    Received-SPF: Pass (protection.outlook.com: domain of hotmail.com designates
     157.55.2.40 as permitted sender) receiver=protection.outlook.com;
     client-ip=157.55.2.40; helo=DUB004-OMC3S31.hotmail.com;
    Authentication-Results: spf=pass (sender IP is 157.55.2.40)
     smtp.mailfrom=dfedorenkov@hotmail.com; 
    X-Forefront-Antispam-Report: CIP:157.55.2.40;CTRY:US;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(438002)(189002)(3905003)(199003)(51694002)(110136001)(229853001)(512934002)(450100001)(15975445007)(77156002)(120916001)(107886001)(46102003)(62966003)(2351001)(107046002)(2501002)(104016003)(71186001)(92566001)(106466001)(2421001)(2561002)(86362001)(84326002)(73972006)(102066001)(77806003)(21056001)(19617315012)(33656002)(19625215002)(4396001)(64706001)(20776003)(46316001)(99396003)(83332001)(50986999)(19580395003)(87572001)(6806004)(87836001)(54356999)(1511001)(31966008)(82202001)(36756003)(15714825004)(15852004);DIR:INB;SFP:;SCL:1;SRVR:DM2PR0301MB1215;H:DUB004-OMC3S31.hotmail.com;FPR:;SPF:Pass;MLV:ovrnspm;PTR:dub004-omc3s31.hotmail.com;MX:1;A:1;LANG:en;
    X-Microsoft-Antispam: UriScan:;
    X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB1215;
    X-Exchange-Antispam-Report-Test: UriScan:;
    X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004);SRVR:DM2PR0301MB1215;
    X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB1215;
    X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply


    Tuesday, December 16, 2014 8:19 AM
  • Did you ever find a work-around for this?  I'm in the exact same situation;  just updated to CU7 yesterday and today XP clients running Outlook 2010 cannot access Public Folders.
    Monday, December 22, 2014 5:13 PM
  • Hi W001fer,

    I found there is some change about Public Folder in Exchange 2013 CU7, although ours is modern Public Folder, i would share this team blog with you:

    On-Premises Legacy Public Folder Coexistence for Exchange 2013 Cumulative Update 7 and Beyond

    I did research about this issue with no luck. Since the issue just happens on Windows XP machines, and Windows XP has end its life cycle. It is recommended to upgrade the clients. Otherwise, as a temporarily workaround, you may suggest the users access Public Folder via OWA.

    I will keep researching this issue, will post it here if any update.

    Thanks,

    Jessie

    Tuesday, December 23, 2014 3:45 AM
    Moderator
  • Hi Jessie!

    In another thread I've found temporary solution - installing another mailbox server with CU6 and migrating all PF mailboxes there. Our clients with XP now working normally. Still waiting for some information or fix from MS.

    Tuesday, December 23, 2014 12:00 PM
  • Hi woo1fer,

    I checked in our database and didn't find any clue that it's a known issue in Exchange 2013 Cu7, so we are not sure whether a fix will be released. And as XP have exceeded the support life cycle, we strongly recommend to upgrade the client to supported version. Thanks for your understanding.

    Regards,

    Eric Zou

    Wednesday, December 24, 2014 10:49 AM
    Moderator
  • Exact same problem here.  >_<...

    Alex Hung

    Thursday, December 25, 2014 11:43 AM
  • The client is Outlook 2010, not Windows XP.

    Exchange Server Supportability Matrix states that Outlook 2010 is supported with Exchange Server 2013 SP1 and later (regardless of the client operating system).

    https://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx


    MCTS


    Thursday, January 22, 2015 6:22 AM