Outlook Hangs when clicking Calendar button on a meeting invite

We have a Small Business Server 2008 with both Outlook 2003 (SP3) and Outlook 2007 (SP2) clients.  If a client is running Outlook in cached mode and they click the calendar button in a meeting invite, the calendar opens up and then Outlook hangs and requires an End Task.

Here are some of the troubleshooting steps I've tried, in no particular order...

1.  Delete the OST file and allow a new one to be created
2.  Connected to the Exchange server using RPC over HTTP from a remote computer that doesn't experience the issue when connected to a different Exchange server - problem exists on that profile too
3.  Run SCANOST - it reports "The message with the subject 'Hidden Message' exists in your mailbox on the Microsoft Exchange Server but not in your offline folder file."  Researching this error didn't lead anywhere
4.  Changed Calendar view to "Active Appointments", "Events" and "By Category".  This fixed it, but unfortunately nobody wants to use the "Active Appointments" view (the problem exists with the "Day/Week/Month" and "Day/Week/Month" views)
5.  Started Outlook with the /Safe, /rpcdiag, /noextensions switches without luck
6.  Disabled all addins
7.  Moved all calendar and task items to different folders
8.  Disabled the Windows Firewall on the server (there is no client based firewall on the testing machine)
9.  Create a brand new user account on the server and invite them to a meeting, then log that new user on, open the meeting invite and click the calendar button - problem exists
10.  Turn off cached mode.  This rectifies the problem, but it comes back when cache mode re-enabled (even if creating a new OST file)

It seems to be server specific.  As I pointed out, I have a computer that connects to Exchange Server A in cached mode without any problem, but when it connects to Exchange Server B, the issue exists.  All the client machines tested so far that connect to Exchange Server exhibit the same behaviour.

I've spent about 6-7 hours hours on this so far, so any assistance you can provide would be greatly appreciated.

Thanks
closehauledAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

puppydogbuddyCommented:

It is hard to be sure, but I think your issue is one of the known issues discussed on this web site:

            http://www.slipstick.com/outlook/ol2007/known_issues.htm 

when the web site comes up, scroll down about 6 pages until you come to the topic area Calendar Issues.

Hope this helps.
closehauledAuthor Commented:
No, none of those issues describe the hang that we are experiencing.
puppydogbuddyCommented:
<<<<It seems to be server specific.  As I pointed out, I have a computer that connects to Exchange Server A in cached mode without any problem, but when it connects to Exchange Server B, the issue exists.  All the client machines tested so far that connect to Exchange Server exhibit the same behaviour.>>>>

Are you aware that even if the fixes included MS Outlook SP2 fixed the cause of the problem,  MS Outlook would still hang until you deleted/fixed the records that bad/incomplete data on the system at the time you applied SP2.  This is re-enforced by fact that the problem seems to temporarily disappear when you turn cache mode off. So I would look for bad/incomplete records on Server B, and delete or fix them...then see if that solves the problem.

puppydogbuddyCommented:
You might want to try this Exchange Mail Flow Troubleshooter that I just became aware of :
                   http://msexchangeteam.com/archive/2006/08/07/428616.aspx
closehauledAuthor Commented:
Ok, now I feel like a fool.  I'm continually telling my less experienced staff that "if you are having odd issues, the first thing to check is DNS".  It turns out there were some stale DNS records on the server that were pointing to the old server's IP address and a temporary IP address that was assigned when we first installed a 2nd NIC for the virtual server.  For an unknown reason, those records have been ingnored for the last 9 months, but started being used recently.  

The solution was to delete the stale records in the DNS server, restart the DNS services on the server and then restart the DNS client service on all computers.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.