locked
Outlook anywhere\ RPC over HTTP hangs.....Only in if the client is outlook 2010 RRS feed

  • Question

  • Dear All,

    We are running Exchange SP3 Update rollup 4

    We have enabled our users to use Outlook Anywhere\ RPC over HTTP from outside\home

    But most of the users compain saying when doing send\recieve, opening a new mail message etc......the outlook Hangs.......Only outlook 2010 clients!!!


    There is no reason which causes this but simply hangs... (Note: In the VPN it works fine as in side the network)

    Then need to kill the outlook processs....then it will come up... but it happens regularly.....

    I observed and followed this suggestion and noticed the following http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/62dc55c9-72f1-4a6d-9e47-128410b4d9e1

     

    But now the I face the issue only in outlook 2010 on both XP and Windows 7

     

    Please suggest!!!

    Manju

     

    Monday, August 22, 2011 11:16 AM

All replies

  • Hi
       1. Please update your outlook 2010 to last version.
       2. Add cas server ip to local desktop hosts file.
       3.
    Verify that authentication programs such as “veriface” is not enabled
       4. Enable transport log of outlook 2010. Maybe it can offer clue.
    For Microsoft Outlook 2010:

    On the File tab, click Options.

    In the Outlook Options dialog box, click Advanced.

    In the Other section, select the Enable troubleshooting logging (requires restarting Outlook) check box, and then click OK.

    Exit and restart Outlook.

    Note When you enable logging, the following registry data is configured by Outlook.

    Key: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Options\MailDWORD: EnableLogging
    Values: 1 = logging enabled, 0 = logging disabled
    You can read this Kb http://support.microsoft.com/kb/300479
    Tuesday, August 23, 2011 2:41 AM
  • Hi,

    I have enabled logging as suggested.

     

    Next i will try to map the CAS server in host file.

    I have NLB of CAS with 2 servers so do I need to Map to NLB IP address or individual CAS Server Name.

     

    Also how to configure outlook after the host mapping.

     

    Manju


    Tuesday, August 23, 2011 8:32 AM
  •    Adding NLB IP address to host file.
       Then you can try to reproduce the error and analyze the log.
    Tuesday, August 23, 2011 8:41 AM
  • This is without modifying the host file

     

    I have got the Logs After enabling the "Enable Logging in outlook 2010 client

    There are 2 logs files which made interest here

    OPMLog:

     

     

    2011.08.23 14:18:27 <<<< Logging Started (level is LTF_TRACE) >>>>

    2011.08.23 14:18:27 HELPER::Initialize called

    2011.08.23 14:18:27 Initializing: Finding a Transport

    2011.08.23 14:18:27 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000

    2011.08.23 14:18:28 MAPI Status: (-- -- ---/--- -- ---)

    2011.08.23 14:18:28 MAPI XP Call: TransportLogon, hr = 0x00000000

    2011.08.23 14:18:28 Initializing: Found a transport, Error code = 0x00000000

    2011.08.23 14:18:28 MAPI XP Call: AddressTypes, hr = 0x00000000, cAddrs = 3, cUids = 1

    2011.08.23 14:18:28 MAPI Status: (IN -- ---/OUT -- ---)

    2011.08.23 14:18:28 MAPI XP Call: TransportNotify(BEGIN_IN|BEGIN_OUT), hr = 0x00000000

    2011.08.23 14:18:28 HELPER::Initialize done, Error code = 0x00000000

    2011.08.23 14:18:28 HELPER::GetCapabilities called, Error code = 0x00000000

    2011.08.23 14:28:24 MAPI Status: (-- -- ---/--- -- ---)

    2011.08.23 14:29:49 MAPI Status: (IN -- ---/OUT -- ---)

     

     

    20110823-152032484-oof:

     

    2011/08/23 15:20:32.484: Request to URL: https://owa.rh-bridge.com/EWS/Exchange.asmx


    2011/08/23 15:20:32.484: Request action: http://schemas.microsoft.com/exchange/services/2006/messages/GetUserOofSettings


    2011/08/23 15:20:32.484: Request XML: <?xml version="1.0"?>


    <q:Envelope xmlns:q="http://schemas.xmlsoap.org/soap/envelope/"><q:Body><ex12m:GetUserOofSettingsRequest xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages"><ex12t:Mailbox xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types"><ex12t:Address>m.gowda@royalhaskoning.com</ex12t:Address><ex12t:RoutingType>SMTP</ex12t:RoutingType></ex12t:Mailbox></ex12m:GetUserOofSettingsRequest></q:Body></q:Envelope>


    2011/08/23 15:20:32.484: Sending request


    2011/08/23 15:20:34.234: Request sent


    2011/08/23 15:20:34.234: Response error code: 80004005


    2011/08/23 15:20:34.234: HTTP status code: 403


    2011/08/23 15:20:34.234: -------------------------------


    2011/08/23 15:20:34.234: There is an error in request/response.


    2011/08/23 15:20:34.234: XML response:


    2011/08/23 15:20:34.234: -------------------------------

     

    I suppose this secong log file is related to OOF but there is error even

     

    Manju



    Tuesday, August 23, 2011 10:01 AM
  • Hi,

    Also when the outlook 2010 client on XP OS connected over the "Outlook Anywhere" the Req\Fail count is 3004\50 

    If this is the case can we suspect the Network?

     

    Again if the 2003 client is on "outlook Anywhere" there is no issue at all.

    It something weird

    Manju

    Tuesday, August 23, 2011 1:23 PM
  • Hi
       1. According to your OPMLog, outlook works well No error. OOF log error won’t cause outlook down.
       2.If it is convenient, You can try to  install outlook 2010 on OS :Win 7.  I find similar case about client OS and network.
      

    Wednesday, August 24, 2011 1:45 AM
  • In windows 7 also i face the same issue with outlook 2010 and even outlook 2007

    It is interesting

    Wednesday, August 24, 2011 5:00 AM
  • Hi Manju,
    You don´t seem to have Autodiscover configured correctly and that will cause Availability (free/busy), OOF and OAB download not to work and could cause Outlook 2007/2010 to hang.

    Since you only have a single name in your certificate, create an SRV-record in the external DNS.

    Outlook and SRV-Records
    http://support.microsoft.com/kb/940881


    Martina Miskovic
    Wednesday, August 24, 2011 7:12 AM
  • Dear All,

    The https://www.testexchangeconnectivity.com/ Auto discover Service test returned following results

    Please let me know which is the best method to resolve this.

     

     

    ExRCA is attempting to test Autodiscover for m.gowda@externaldomainname.com.
    Testing Autodiscover failed.
    Test Steps
    Attempting each method of contacting the Autodiscover service.
    The Autodiscover service couldn't be contacted successfully by any method.
    Test Steps
    Attempting to test potential Autodiscover URL https://externaldomainname.com/AutoDiscover/AutoDiscover.xml
    Testing of this potential Autodiscover URL failed.
    Test Steps

    Attempting to resolve the host name externaldomainname.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 75.101.166.3
    Testing TCP port 443 on host externaldomainname.com to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    Tell me more about this issue and how to resolve it
    Additional Details
    A network error occurred while communicating with the remote host.
    Attempting to test potential Autodiscover URL https://autodiscover.externaldomainname.com/AutoDiscover/AutoDiscover.xml
    Testing of this potential Autodiscover URL failed.
    Test Steps
    Attempting to resolve the host name autodiscover.externaldomainname.com in DNS.
    The host name couldn't be resolved.
     Tell me more about this issue and how to resolve it
    Additional Details
    Host autodiscover.externaldomainname.com couldn't be resolved in DNS InfoDomainNonexistent.
    Attempting to contact the Autodiscover service using the HTTP redirect method.
    The attempt to contact Autodiscover using the HTTP Redirect method failed.
    Test Steps
    Attempting to resolve the host name autodiscover.externaldomainname.com in DNS.
    The host name couldn't be resolved.
     Tell me more about this issue and how to resolve it
    Additional Details
    Host autodiscover.externaldomainname.com couldn't be resolved in DNS InfoDomainNonexistent.
    Attempting to contact the Autodiscover service using the DNS SRV redirect method.

    ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method.
    Test Steps
    Attempting to locate SRV record _autodiscover._tcp.externaldomainname.com in DNS.
    The Autodiscover SRV record wasn't found in DNS.
    Tell me more about this issue and how to resolve it

     

    Manju

    Sunday, August 28, 2011 1:48 PM
  • Hi Manju,
    You need to create a SRV-record in the DNS as I wrote in my previous post.
    Martina Miskovic
    Sunday, August 28, 2011 2:04 PM
  • Dear All,

    The https://www.testexchangeconnectivity.com/ RPC over HTTP Service test returned following results

    What is the missing thing in this???

    Testing RPC/HTTP connectivity.

    The RPC/HTTP test failed.

    Test Steps

    Attempting to resolve the host name webmail.internaldoaminurl.net in DNS.

    The host name resolved successfully.

    Additional Details

    IP addresses returned: 87.213.36.87

    Testing TCP port 443 on host webmail.internaldoaminurl.net to ensure it's listening and open.

    The port was opened successfully.

    Testing the SSL certificate to make sure it's valid.

    The SSL certificate failed one or more certificate validation checks.

    Test Steps

    ExRCA is attempting to obtain the SSL certificate from remote server webmail.internaldoaminurl.net on port 443.

    ExRCA successfully obtained the remote SSL certificate.

    Additional Details

    Remote Certificate Subject: CN=webmail.internaldoaminurl.net, OU=KIM, O=Haskoning Nederland B.V., L=Nijmegen, S=Gelderland, C=NL, Issuer: CN=External URL Subordinate CA 1, DC=internaldoaminurl, DC=net.

    Validating the certificate name.

    The certificate name was validated successfully.

    Additional Details

    Host name webmail.internaldoaminurl.net was found in the Certificate Subject Common name.

    Certificate trust is being validated.

    Certificate trust validation failed.

    Test Steps

    ExRCA is attempting to build certificate chains for certificate CN=webmail.internaldoaminurl.net, OU=KIM, L=Nijmegen, S=Gelderland, C=NL.

    A certificate chain couldn't be constructed for the certificate.

    Additional Details

    The certificate chain couldn't be built. You may be missing required intermediate certificates.

    Sunday, August 28, 2011 2:14 PM
  • Dear All,

    Dear All,

    The https://www.testexchangeconnectivity.com/ OOF reply test over HTTP Service test returned following results.

    What is this error caused by.........???

    Exchange Web Services synchronization, notification, availability, and Automatic Replies (OOF).

    Not all of the tests of Exchange Web Services tasks completed.


    Test Steps 


    Ensuring that the test mailbox folder is empty and accessible. 

    ExRCA couldn't confirm that the folder is accessible and empty. 


    Additional Details 

    Exception details:
    Message: The request failed. The remote server returned an error: (405) Method Not Allowed.
    Type: Microsoft.Exchange.WebServices.Data.ServiceRequestException
    Stack trace:
     at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
     at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
     at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
     at Microsoft.Exchange.Tools.ExRca.Tests.EnsureEmptyFolderTest.PerformTestReally()
    Exception details:
    Message: The remote server returned an error: (405) Method Not Allowed.
    Type: System.Net.WebException
    Stack trace:
     at System.Net.HttpWebRequest.GetResponse()
     at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
     at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)


    Sunday, August 28, 2011 2:16 PM
  • ping -a 87.213.36.87
    Pinging unlabelled-87-36-213-87.versatel.net [87.213.36.87] with 32 bytes of data:

    ping webmail.royalhaskoning.com
    Pinging gateway.royalhaskoning.com [87.213.36.89] with 32 bytes of data:

    You might need to check the DNS-Settings and the configuration in your firewall as well as creating a SRV-Record

    One other option if of course to buy UCC/SAN Certificate with the following names in it:
    webmail.externaldomain.com
    autodiscover.externaldomain.com
    server.internaldomain.local


    Martina Miskovic
    Sunday, August 28, 2011 2:27 PM
  • Hi Martina,

    I dont have webmail.royalhaskoning.com configured for our "outlook anywhere"

    The URL for Outlook anywhere is webmail.internaldoaminurl.net

    Again the OWA url is owa.some-bridge.com

    Ex: The external domain name is (It is not the Exchange OWA adress) example.com

    Internal doamain name is example2.net

    The Outlook anywhere URL is webmail.example2.net

    The  OWA URL is owa.some-bridge.com

     

     

    1.So is the existing URls are correct (differet for OA and OWA)?

    2.What is the recommended method of using the outlook anywhere URL(exchange 2007 SP3)

     

    Manju

     


    Sunday, August 28, 2011 3:46 PM