Outlook 2007 error The connection to Micrsoft Exchange is unavailable but Exchange is on line.
We are on Windows 7, and on new systems, Outlook 2007 doesn't connect to Exchange to resolve the user. I found this FixIt that seems to be the only thing that works http://support.microsoft.com/?kbid=319206 . I think the error message is "The connection to Micrsoft Exchange is unavailable. Outlook must be connected or on line to complete this action." We are on Exchange 2007 SP3 and DC is 2008 Standard x64. Also, on our domain, if you close outlook and open it, it asks for credentials. I'd like to get rid of this but nothing seems to work.
July 28th, 2011 11:25pm

Ok, this article fixed it for me. Not sure which server it was pointing to before but try this if you have similar problems. http://forums.msexchange.org/m_1800463281/mpage_1/key_/tm.htm#1800463281 This fixed the Outlook name resolution issue, not the pop up after Outlook connects though... Also, if you need this hard coded say for imaging purposes, this was the only way I was able to permanently fix this issue for my network. To force Outlook to use a pre-defined global catalog server, use the following steps to set the following special registry parameter to point to the Fully Qualified Domain Name (FQDN). Doing this over-rides any setting in the MAPI profile. Click Start, and then click Run. In the Open box, type regedit.exe, and then clickOK. Locate and then click the following key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider Note You may have to create the registry path. On the Edit menu, click Add Value, and then add the following registry value: Value name: DS Server Data type: REG_SZ (string) Value data: FQDN of the global catalog server This allowed me to roll out a bunch of laptops and not have to worry about running the Fix It for each user.
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2011 9:39pm

Just when I thought I had this issue licked, I run sysprep and it seems to have removed the fix and even the registry entry because I'm still getting the same error...
September 8th, 2011 3:05am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics