locked
Exchange 2007 hangs on Outlook Client "retrieve" RRS feed

  • Question

  • SBS2008 Std

    Exchange 2007 SP1

    Forefront for Exchange

    Symptom: I applied SBS2208 server updates (including net 4 framework) and have lost remote access to smartphone. LAN outlook clients (2003, 2007,2010) all show very elongated "retrieving" from server (excess of 60 minutes). I ran testexchange connectivity.com and it failed autodiscover.

     

    What can I do to get exchange working again?


    John Lenz
    Wednesday, April 20, 2011 3:23 PM

Answers

  • Funny thing is that I only use the wizards to configure. Something went wrong with "Fix" but I am back up and operating. I'll try later to use "Fix".

    John


    John Lenz
    • Marked as answer by JohnLenz Monday, May 9, 2011 1:12 PM
    Wednesday, April 27, 2011 7:48 PM

All replies

  • I would start by applying Exchange 2007 SP3 to begin with. That will reset a lot of things.
    Once you have done that, if it continues to fail to work, then you can try running the fix my network wizard in SBS.

    You don't need .net framework 4 to be installed, unless you have an application that requires it.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    Wednesday, April 20, 2011 9:25 PM
  • Simon,

    Success. The last time I tried to install SP3, Forefront for Exchange complicated the install which resulted in a corrupted AD. I had to wipe the C drive and rebuild. This time I took the 4 hours to uninstall Forefront for Exchange before going to SP3. What was interesting was as soon as forefront was uninstalled, the "hang" went away and the push to the Android smartphone started working again.

    I successfully move to SP3 and re-installed forefront for exchange. I will watch to see if the "hang" comes back


    John Lenz
    Thursday, April 21, 2011 11:58 PM
  •  

    Hi,

     

    How is thing going on after reinstalling Forefront? If the system still hangs up, you may create a new thread in Forefront forum. Meanwhile, I would like to confirm whether Autodiscover can work fine now. Do you get any error message when testing Autodiscover on Exchange Remote Connection Analyzer website?

     

    Please navigate to http://www.testexchangeconnectivity.com and select “Outlook AutoDiscover” to analyze the problem. If there is any error message, please post it here for research.

     

    Thanks.

    Novak Wu

     

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, April 25, 2011 7:28 AM
  • Both SP3 and Forefornt are installed and both internal and push email is working. I ran the test and it failed. What does this mean? Here is the diagnostic:

    Attempting the Autodiscover and Exchange ActiveSync test (if requested).
    Testing of Autodiscover for Exchange ActiveSync 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://longsoho.com/AutoDiscover/AutoDiscover.xml
    Testing of this potential Autodiscover URL failed.
    Test Steps
    Attempting to resolve the host name longsoho.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 67.173.82.253
    Testing TCP port 443 on host longsoho.com to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl01_tmmArrow">Tell me more about this issue and how to resolve it</label>
    Additional Details
    A network error occurred while communicating with the remote host.
    Exception details:
    Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 67.173.82.253:443
    Type: System.Net.Sockets.SocketException
    Stack trace:
    at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
    at Microsoft.Exchange.Tools.ExRca.Tests.TcpPortTest.PerformTestReally()
    Attempting to test potential Autodiscover URL https://autodiscover.longsoho.com/AutoDiscover/AutoDiscover.xml
    Testing of this potential Autodiscover URL failed.
    Test Steps
    Attempting to resolve the host name autodiscover.longsoho.com in DNS.
    The host name couldn't be resolved.
    <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl01_ctl00_tmmArrow">Tell me more about this issue and how to resolve it</label>
    Additional Details
    Host autodiscover.longsoho.com couldn't be resolved in DNS Exception details:
    Message: The requested name is valid, but no data of the requested type was found
    Type: System.Net.Sockets.SocketException
    Stack trace:
    at System.Net.Dns.GetAddrInfo(String name)
    at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
    at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
    at Microsoft.Exchange.Tools.ExRca.Tests.ResolveHostTest.PerformTestReally()
    .
    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.longsoho.com in DNS.
    The host name couldn't be resolved.
    <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl02_ctl00_tmmArrow">Tell me more about this issue and how to resolve it</label>
    Additional Details
    Host autodiscover.longsoho.com couldn't be resolved in DNS Exception details:
    Message: The requested name is valid, but no data of the requested type was found
    Type: System.Net.Sockets.SocketException
    Stack trace:
    at System.Net.Dns.GetAddrInfo(String name)
    at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
    at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
    at Microsoft.Exchange.Tools.ExRca.Tests.ResolveHostTest.PerformTestReally()
    .
    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.longsoho.com in DNS.
    The Autodiscover SRV record was successfully retrieved from DNS.
    Additional Details
    The Service Location (SRV) record lookup returned host remote.longsoho.com.
    Attempting to test potential Autodiscover URL https://remote.longsoho.com/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.
    Test Steps
    Attempting to resolve the host name remote.longsoho.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 71.194.120.240
    Testing TCP port 443 on host remote.longsoho.com to ensure it's listening and open.
    The port was opened successfully.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
    Test Steps
    Validating the certificate name.
    The certificate name was validated successfully.
    Additional Details
    Host name remote.longsoho.com was found in the Certificate Subject Common name.
    Testing the certificate date to confirm the certificate is valid.
    Date validation passed. The certificate hasn't expired.
    Additional Details
    The certificate is valid. NotBefore = 12/24/2010 6:27:27 PM, NotAfter = 9/22/2011 3:43:11 AM
    Checking the IIS configuration for client certificate authentication.
    Client certificate authentication was detected.
    Additional Details
    Accept/Require client certificates were found. Set the IIS configuration to Ignore Client Certificates if you aren't using this type of authentication.

    John Lenz
    Monday, April 25, 2011 12:57 PM
  • This will cause an issue:

    "Accept/Require client certificates were found".

    I would suggest that you start by running the Fix My Network wizard from the SBS management console.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    Monday, April 25, 2011 10:53 PM
  • Hi,

     

    Do you encounter any problem when configuring new Outlook profile automatically via Autodiscover?

     

    Based on the result in Exchange RCA website, the Autodiscover can be detected in SRV record. To verify whether Autodiscover can work fine or not, I suggest you perform the following steps.

     

    1. While Outlook is running, hold down the CTRL key, right-click the Outlook icon in the notification area, and then select Test E-mail AutoConfiguration.

    2. Verify that the correct e-mail address is in the box next to E-mail Address.

    3. Clear the check boxes next to Use Guessmart and Secure Guessmart Authentication.

    4. On the Test E-mail AutoConfiguration page, verify that the check box next to Use AutoDiscover is selected, and then click the Test button.

    5. Then, please check whether there is any error code and post it here for research.

     

    Thanks.

    Novak Wu

     

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, April 26, 2011 6:33 AM
  • I ran autodiscover test with no reported errors. Where is IIS do I fix accept/require client certificates?
    John Lenz
    Tuesday, April 26, 2011 8:01 PM
  • As I have written three times now - run the Fix My Network wizard. That will correct many of the issues with the SBS configuration.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    Tuesday, April 26, 2011 10:11 PM
  •  

    Sembee,

     

     Thanks For your assistance.

    I did run the "fix my network" wizard. It failed on Internet ports and DNS naming. Then I lost all connectivity to the Internet. After 3 hours I was finally able to re-run Connect to Internet, setup Internet address and add trusted certificate. I did lose my VPN but after a re-boot I re-ran VPN connector and it took.

     

    I will monitor system for next few days and re[port back. I am a bit wary of running "fix my network" again.

    John


    John Lenz
    Tuesday, April 26, 2011 11:37 PM
  • That usually happens when the server is not configured with the wizards, but is configured manually. The fix my network wizard configures everything as SBS wants it to be configured, which is the best way. While you can configure everything manually that will mean a lot of the SBS functionality will not work.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    Wednesday, April 27, 2011 1:22 AM
  • Funny thing is that I only use the wizards to configure. Something went wrong with "Fix" but I am back up and operating. I'll try later to use "Fix".

    John


    John Lenz
    • Marked as answer by JohnLenz Monday, May 9, 2011 1:12 PM
    Wednesday, April 27, 2011 7:48 PM