Comments on: Office 2007 Service Pack 2: The Gift That Keeps Giving!

By: Mick

Mick — Wed, 27 May 2009 23:34:15 +0000

Tried above hot fix on Vista + Outlook 207. but still failed to connect.

Did anyone else found fix for it? This issue happened just after I installed SP2 for Outlook 2007.

By: Edmund

Edmund — Sun, 10 May 2009 10:23:43 +0000

Thanks for digging out the hotfix – Microsoft are literally incredible sometimes.

By: Dan

Dan — Sat, 09 May 2009 17:20:19 +0000

Good find Tom! I’m getting ready to leave for vacation, but as soon as I get back I’ll have to give it a run in the dev environment and see what I can come up with as far as implementation tips for large / disperse deployments. Sounds like that’s going to get it though. Thanks for the update.

Other’s who are having issues with the steps outlined above, or would like to manage this at the client level instead of the server level; check out the link mentioned by Tom above. http://support.microsoft.com/kb/968858

By: Tom

Tom — Fri, 08 May 2009 18:47:55 +0000

So I went digging again for answers from Microsoft and turned up this: http://support.microsoft.com/kb/968858 . It’s a post SP2 hotfix that addresses the problem and it seems to work. I tested a fresh XP SP3 / Office 2007 SP2 laptop this morning before the hotfix and it failed to configure a profile over OA. After this patch I was able to configure Outlook with only the SSL (Outlook Anywhere) connection. Huzzah!

By: Tom

Tom — Fri, 08 May 2009 18:11:04 +0000

We have this issue as well. Making the method #2 changes had no effect and off-LAN clients still can’t create profiles at all. Method #4 also doesn’t work but it gets me a little further along. Running ‘netstat -a’ while Outlook tries to connect shows the computer attempting to make a connection to port 135 (“epmap”) on the mailbox backend server. Of course that will never work because we’re not stupid enough to open port 135 on our mailbox server to the world. You’d think they would test the effects of a Service Pack before vomiting it onto the public. Guess not.

By: MarkH

MarkH — Thu, 07 May 2009 17:04:41 +0000

We have the same issue, upgraded last night to Service Pack 2, then problems appeared with access to one of our Exchange 2003 servers across VPN.

Tried modifying the hosts file but the problem still remains, we get the same error.

We can ping the server by name and by IP address and it replies, and we can even go into the share for the server.

I am stuck!

By: Outlook 2007 SP2 cannot open address list on Exchange Server - Office Update Service

Thu, 07 May 2009 16:21:40 +0000

[...] with some more info yet I can’t find the post for some reason. The below links should help you. http://techblogogy.net/index.php/200…-keeps-giving/ [...]

By: Allen

Allen — Wed, 06 May 2009 02:45:19 +0000

I have the same issue. But I cannot fix it followed your steps.

By: Outlook 2007 SP2 cannot open address list on Exchange Server - Office Update Service

Tue, 05 May 2009 16:02:41 +0000

[...] Outlook 2007 SP2 cannot open address list on Exchange Server Possible Solutions http://techblogogy.net/index.php/200…-keeps-giving/ http://support.microsoft.com/default…b;en-us;969519 I’ve tried method 4 but haven’t had any [...]

By: sarepweb@ucdavis

sarepweb@ucdavis — Tue, 05 May 2009 01:49:20 +0000

I can’t print from Outlook 2007 SP2 clients using Outlook Anywhere. I get this error message: “The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action”

I was able to work-around the initial connection problem by creating the Outlook profile while connected to the Exchange server’s local network. (Outlook Anywhere appears to work fine once the profile has been created). I forwarded your article to my Exchange administrator, but I don’t expect to hear from him for at least a day or two.