none
Address Book: The connection to the Microsoft Exchange Server is unavailable.

    Question

  • Hi,

    I am having a strange problem on the address book between Outlook 2007 and Microsoft Exchange Server 2007.
    I can open address book and download the offline address book with no problem. The problem is when I left the outlook 2007 idle for a few minutes, then I click on Address Book, then it will pop up the error message "The connection to Microsoft Exchange server is unavailable. Outlook must be online or connected to complete this action." But after I close the message box, the connection to the server resume and I can open the address book with no problem. I do know that this isn't a big issue, but this is really annoying. 
    I have tested setup outlook on a few pc, all the pc also facing the same problem except the Exchange Server itself will not have this issue.
    I have tried to google for solution, but couldn't find any solution for it yet. Is there any expert that could enlighten me on solving this problem? 

    Thanks in advance.





    Sunday, November 29, 2009 7:14 PM

All replies

  • Well, I have never heard of that, but what Windows version are the clients running? Any client-based firewalls enabled? Server firewall enabled? Or a firewall in between the server and clients?

    Sunday, November 29, 2009 8:26 PM
  • Cached mode or online mode clients?
    Active Directory, 4th Edition - www.briandesmond.com/ad4/
    Monday, November 30, 2009 4:07 AM
  • Are you running the Exchange server in a cluster or is it standalone. can you access the address book share via a unc path which should be something like:

    \\exchangeServerName\ExchangeOAB 

    Thanks

    Robin
    Monday, November 30, 2009 9:46 AM
  • Hi,

    I have seen this error when exchange BOX have resource issue. Please check health of exchange server randomely.

    But stil i not looking much from sevrer side issue but i will recommend you to enable diagnostic loggoing to generate more event and see.


    Anil
    Monday, November 30, 2009 4:32 PM
  • you could also try switching on extra logging in outlook 2007 follow this article to find out how to do it:

    http://office.microsoft.com/en-us/outlook/HA012304211033.aspx

    Robin
    Monday, November 30, 2009 4:52 PM
  • there is no issue in your client system or in exchange server..
    It is network isuue.Check the response from the server by ping command.
    Tuesday, December 01, 2009 12:06 AM
  • Hi all,

    Sorry for the late reply.

    Andy_D:
    "Well, I have never heard of that, but what Windows version are the clients running? Any client-based firewalls enabled? Server firewall enabled? Or a firewall in between the server and clients?"

    Hi Andy, thanks for the post. The clients are running on Windows XP with SP2 and some are on SP3.  As for the firewall, i had already disable all the firewall, the connection between the server and clients are fully enabled.

    Brian Desmond
    "Cached mode or online mode clients?"

    I had tried both, both had the same issue.


    Robin Ferris
    Are you running the Exchange server in a cluster or is it standalone. can you access the address book share via a unc path which should be something like:
    \\exchangeServerName\ExchangeOAB 

    Hi Robin, I had tried your suggestion, it is able to open the UNC path. The server is setup standalone (Hub Transport, Mailbox, Client Access, Unified Messaging) together with the active directory, and subscribed to another server with the edge transport roles.


    Anil K Singh

    Hi,

    I have seen this error when exchange BOX have resource issue. Please check health of exchange server randomely.

    But stil i not looking much from sevrer side issue but i will recommend you to enable diagnostic loggoing to generate more event and see.



    Robin Ferris
    you could also try switching on extra logging in outlook 2007 follow this article to find out how to do it:
    http://office.microsoft.com/en-us/outlook/HA012304211033.aspx

    Hi Anil and Robin,

    Let me try this suggestion and will get back to you as soon as possible. Thanks for the help.

    m_pradeep
    there is no issue in your client system or in exchange server..
    It is network isuue.Check the response from the server by ping command.

    Hi pradeep, I had tried the ping to the server. It results only 4ms without packet lost for long time. And I have others computer that ping over internet for about 300ms without any packet lost too. Both side of the PC also having this problem if the Outlook 2007 keep idle for about 5 minutes.

    Thanks for your help. Hoping for more suggestion to solve this problem.


    • Edited by bustedapp Tuesday, December 01, 2009 1:48 PM
    Tuesday, December 01, 2009 1:15 PM
  • Hi Robin and Anil,

    Here is the outlook 2007 logging data from a client pc with Windows XP Professional with SP2. And the pc is joined to the same domain as the Exchange Server domain.


    OPMLog:
    2009.12.01 13:22:11 <<<< Logging Started (level is LTF_TRACE) >>>>
    2009.12.01 13:22:11 HELPER::Initialize called
    2009.12.01 13:22:11 Initializing: Finding a Transport
    2009.12.01 13:22:11 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000
    2009.12.01 13:22:11 MAPI XP Call: TransportLogon, hr = 0x8004011d
    2009.12.01 13:22:11 MAPI XP Call: Shutdown, hr = 0x00000000
    2009.12.01 13:22:11 MAPI XP Call: XPProviderInit in EMSMDB.DLL, hr = 0x00000000
    2009.12.01 13:22:11 MAPI Status: (-- -- ---/--- -- ---)
    2009.12.01 13:22:11 MAPI XP Call: TransportLogon, hr = 0x00000000
    2009.12.01 13:22:11 Initializing: Found a transport, Error code = 0x00000000
    2009.12.01 13:22:11 MAPI XP Call: AddressTypes, hr = 0x00000000, cAddrs = 3, cUids = 1
    2009.12.01 13:22:11 MAPI XP Call: RegisterOptions, hr = 0x00000000, cOptions = 2
    2009.12.01 13:22:11 MAPI Status: (IN -- ---/OUT -- ---)
    2009.12.01 13:22:11 MAPI XP Call: TransportNotify(BEGIN_IN|BEGIN_OUT), hr = 0x00000000
    2009.12.01 13:22:11 HELPER::Initialize done, Error code = 0x00000000
    2009.12.01 13:22:11 HELPER::GetCapabilities called, Error code = 0x00000000
    2009.12.01 13:27:03 HELPER::Uninitialize called
    2009.12.01 13:27:03 MAPI Status: (-- -- ---/--- -- ---)
    2009.12.01 13:27:03 MAPI XP Call: TransportNotify(END_IN|END_OUT), hr = 0x00000000
    2009.12.01 13:27:03 MAPI XP Call: TransportLogoff in EMSMDB.DLL, hr = 0x00000000
    2009.12.01 13:27:03 MAPI XP Call: Shutdown, hr = 0x00000000
    2009.12.01 13:27:03 Resource manager terminated



    First run log:
    *** Starting First Run (11-29-2009 19:28:08) ***
    ...HrPreSplashFirstRun called.
    ...HrPreLogFirstRun called.
    ...updating profiles for MAPI.
    ...HrPostLogFirstRun called.
    ...registering forms.
    ...forcing FirstRun Balloon to On.
    ...starting SRS import.
      No SRSImport key.
      SRS import result: 00000001
    ...deleting WAB4/UseOutlook because we're using MAPI.
    ...writing UUID to HKCU.
    ...setting Primary Client to Outlook.
    *** Ending First Run (11-29-2009 19:29:25) ***


    The log above have happen once the message box with the error message. "The connection to Exchange Server is unvailable. Outlook must be online or connected to complete this action."

    Hope this could give you some clue on the problems.

    Thank you very much.

    Tuesday, December 01, 2009 1:35 PM
  • that doesn't immedicately give me an answer, so will have to look a little more into that log.

    have you tried doing a packet capture using network monitor blog here http://blogs.technet.com/netmon/ and capturing from just before the error until just after. the smaller the better.

    you should be able to see the request going out for the address book in the capture and see where it's going etc

    Robin
    Tuesday, December 01, 2009 4:01 PM
  • ow another thing I forgot was to say to use the outlook connection status checker and also autoconfiguration tester, you can get to these by right mouse clicking on the outlook icon in your task tray and holding ctrl at the same time.

    Then choose whic one to run, the status checker would show you how many requests/failures you are getting and the autoconfig would see if everythign is pointing to the riught place as well.

    Robin
    Tuesday, December 01, 2009 4:07 PM
  • Hi,
    I'm Bustedapp


    here is log from the netmon:

    2133 13.468750 OUTLOOK.EXE {MSRPC:22, TCP:21, IPv4:20} 10.10.10.155 10.40.0.80 MSRPC MSRPC:c/o Request: unknown   Call=0x4  Opnum=0x3  Context=0x0  Hint=0x94 

    2144 13.765625 OUTLOOK.EXE {TCP:21, IPv4:20} 10.40.0.80 10.10.10.155 TCP TCP:Flags=.....R.., SrcPort=1026, DstPort=4359, PayloadLen=0, Seq=3805734063, Ack=1853777462, Win=0

    2145 13.765625 OUTLOOK.EXE {TCP:23, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:Flags=...A.R.., SrcPort=4358, DstPort=1026, PayloadLen=0, Seq=2348425327, Ack=2726184865, Win=0

    2146 13.765625 OUTLOOK.EXE {TCP:24, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:Flags=...A.R.., SrcPort=4360, DstPort=1026, PayloadLen=0, Seq=1193436320, Ack=1230969671, Win=0

    2147 13.765625 OUTLOOK.EXE {TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:Flags=......S., SrcPort=4373, DstPort=1026, PayloadLen=0, Seq=3063296659, Ack=0, Win=65535 (  ) = 65535

    2246 14.091797 OUTLOOK.EXE {TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 TCP TCP:Flags=...A..S., SrcPort=1026, DstPort=4373, PayloadLen=0, Seq=1353502743, Ack=3063296660, Win=16384 ( Scale factor not supported ) = 16384

    2247 14.091797 OUTLOOK.EXE {TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:Flags=...A...., SrcPort=4373, DstPort=1026, PayloadLen=0, Seq=3063296660, Ack=1353502744, Win=65535 (scale factor 0x0) = 65535

    2248 14.091797 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 MSRPC MSRPC:c/o Bind:  UUID{F5CC5A18-4264-101A-8C59-08002B2F8426} MS NT Directory NSP(NSPI)  Call=0x1  Assoc Grp=0x0  Xmit=0x16D0  Recv=0x16D0 

    2254 14.384766 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 MSRPC MSRPC:c/o Bind Ack:  Call=0x1  Assoc Grp=0x11C54  Xmit=0x16D0  Recv=0x16D0 

    2255 14.386719 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 MSRPC MSRPC:c/o Alter Cont:  UUID{F5CC5A18-4264-101A-8C59-08002B2F8426} MS NT Directory NSP(NSPI)  Call=0x1 

    2296 14.673828 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 MSRPC MSRPC:c/o Alter Cont Resp:  Call=0x1  Assoc Grp=0x11C54  Xmit=0x16D0  Recv=0x16D0 

    2297 14.675781 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2305 14.962891 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 MSRPC MSRPC:c/o Fault:  Call=0x1  Context=0x0  Status=0x1C00001A  Cancels=0x0 

    2306 14.978516 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2329 15.259766 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2345 15.478516 OUTLOOK.EXE {TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:Flags=...A...., SrcPort=4373, DstPort=1026, PayloadLen=0, Seq=3063298657, Ack=1353503187, Win=65092 (scale factor 0x0) = 65092

    2606 17.134766 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2622 17.447266 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2623 17.447266 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2625 17.744141 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2651 17.884766 OUTLOOK.EXE {TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:Flags=...A...., SrcPort=4373, DstPort=1026, PayloadLen=0, Seq=3063299051, Ack=1353504189, Win=64090 (scale factor 0x0) = 64090

    2777 19.150391 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2791 19.462891 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2792 19.462891 OUTLOOK.EXE {TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 TCP TCP:[Continuation to #2791]Flags=...AP..., SrcPort=1026, DstPort=4373, PayloadLen=121, Seq=1353505649 - 1353505770, Ack=3063299288, Win=64542 (scale factor 0x0) = 64542

    2793 19.462891 OUTLOOK.EXE {TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:Flags=...A...., SrcPort=4373, DstPort=1026, PayloadLen=0, Seq=3063299288, Ack=1353505770, Win=65535 (scale factor 0x0) = 65535

    2794 19.462891 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2829 19.744141 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 NSPI NSPI:Windows stub parser: Requires full Common parsers. See the "How Do I Change Parser Set Options" help topic for tips on loading these parser sets.

    2887 19.962891 OUTLOOK.EXE {TCP:25, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:Flags=...A...., SrcPort=4373, DstPort=1026, PayloadLen=0, Seq=3063299445, Ack=1353505895, Win=65410 (scale factor 0x0) = 65410
    6027 37.681641 OUTLOOK.EXE {TCP:72, IPv4:20} 10.10.10.155 10.40.0.80 TCP TCP:[Keep alive]Flags=...A...., SrcPort=4293, DstPort=1162, PayloadLen=1, Seq=3363826392 - 3363826393, Ack=3069109954, Win=64622
    6083 37.962891 OUTLOOK.EXE {TCP:72, IPv4:20} 10.40.0.80 10.10.10.155 TCP TCP:[Keep alive ack]Flags=...A...., SrcPort=1162, DstPort=4293, PayloadLen=0, Seq=3069109954, Ack=3363826393, Win=65535

    Tuesday, December 01, 2009 4:48 PM
  • Hi,

     

    From your Network package, I notice following error is received:

     

    2305 14.962891 OUTLOOK.EXE {MSRPC:33, TCP:25, IPv4:20} 10.40.0.80 10.10.10.155 MSRPC MSRPC:c/o Fault:  Call=0x1  Context=0x0  Status=0x1C00001A  Cancels=0x0

     

    I would like to explain that the error code 0x1C00001A means NCA_STATUS_CONTEXT_MISMATCH. Following article described more detailed information regarding the error:

     

    http://blogs.msdn.com/roopeshpattan/archive/2009/06/17/rpc-cancel-request-dialogue-box-due-to-session-timeout-triggered-by-the-network-devices.aspx

     

    Would you please also let me know whether the 10.40.0.80 is GC server with Exchange Server installed and the 10.10.10.155 is the Outlook Client?

    Thanks,

    Mike

    Wednesday, December 02, 2009 7:15 AM
  • Hi Mike,


    Yes, 10.40.0.80 is Gc server with exchange server and 10.10.10.155 is the outlook client

    I will check first the error code 0x1C00001A problem and see the detailed information about that. 
    Wednesday, December 02, 2009 12:57 PM
  • Hi Mike,

    i already do the way as u recommend to me , but the outlook problem still appears .

    Is is till have other ways to solve my problem.

    Thanks for help me everyone.
    Friday, December 04, 2009 8:43 PM
  • Hi,

    Did anyone ever solved this issue?  I got the same error with Outlook 2007 client on Exchange 2010 SP2 server...

    gr.

    WOCOM

    Monday, February 13, 2012 2:47 PM