Enviroment: (All Servers)Windows Server 2003 R2 SP2Exchange Server 2003 SP2(All Clients) Windows XP SP2 Outlook 2007 SP2 (12.0.6425.1000) Calendar Updates (but not the inital meeting notice) to external address get stuck in outgoing queue (Backend to Bridgehead). Queue status reads Unable to open the message for delivery. Internalrecipients are uneffected. The messages fail with error 4.4.7. Meeting updates forwarded as email (meeting sent as iCal) succeed. So far only a few clients seem affected. I got these when I turned logging to max. Event Type: Warning Event Source: MSExchangeTransport Event Category: Connection Manager Event ID: 4006 Date: 12/11/2009 Time: 11:33:44 AM User: N/A Description: Message delivery to the host '172.16.2.98' failed while delivering to the remote domain '_d117066673c6dc4e9ae794f77df47630_S' for the following reason: Unable to open the message for delivery. Event Type: Information Event Source: MSExchangeTransport Event Category: Routing Engine/Service Event ID: 977 Date: 12/11/2009 Time: 11:33:44 AM User: N/A Description: Following connector fails to connect to its target bridge head. CN=Internet Connector,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=IO Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=io,DC=local KB938650 (http://support.microsoft.com/kb/938650) is the closest match I could find, but Im hesitant to apply a hotfix that is not specificly for my problem. Any thoughts?

Is this happening for ALL updates? Or just a select few? Personally, I would install that hotfix and follow the instructions in that KB and test.

Is this happening for ALL updates? Or just a select few? Personally, I would install that hotfix and follow the instructions in that KB and test. All meeting updates sentby a few (5 of 95) users.I'm going to have them try sending updates from OWA next to see if its Outlook.

Have you seen this thread, the one who has tried the hotfix?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Have you seen this thread, the one who has tried the hotfix? James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com I have seen it and downloaded the hotfix. However I amnot ready toapply a server side fix for an issue effecting 7% of my clients. I'd rather not risk breaking everyone to fix a few.Additional Info:The exchange server is clustered - I forgot to metionthisif it matters.I can now confirm OWA does not have any issues, even with meetingspreviously affected.

Any update?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

I woulds also make sure you have applied the latest Outlook updates:http://support.microsoft.com/kb/975729

I woulds also make sure you have applied the latest Outlook updates:http://support.microsoft.com/kb/975729 That hotfix is listed for Russian versions of Outlook 2007.All released updates are installed. I'm tring reinstalling Outlook next (hopefuly today).

oops. Sorry. Wrong link.Here is the latest hotfix /rollup package:http://support.microsoft.com/kb/974994/12.0.6425.1000 is not the latest.I would also compare online vs cache mode. If Outlook is in cache mode, close it and delete the .ost to create a new offline cache.

On Tue, 22-Dec-09 17:55:03 GMT, AndyD_ wrote:>oops. Sorry. Wrong link.Here is the latest hotfix /rollup package:http://support.microsoft.com/kb/974994/12.0.6425.1000 is not the latest.I would also compare online vs cache mode. If Outlook is in cache mode, close it and delete the .ost to create a new offline cache. I've always found the MS Office build numbers confusing.Installing that update changes the first build number, not the lastone.E.g. before installing that rollup the 1st build number was0. Now it looks like this: 12.0.6520.5000 SP2 MSO 12.0.6425.01000---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Yea, not to mention there seems to be no consistent public announcement of the latest office hotifxes even though they typically fix a lot of issues.

I'll give that hotfix a try if reinstalling doesn't solve the issue.I'll check if cache mode is on but generaly for our users it isn't.

Reinstalling Outlook on the clients did not fix the issue. Neither did installing the Office Outlook 2007 Hotfix package (KB974994). When I compare the file versions installed by the Exchange Hotfix (KB938650) to our server I find the following: These files are currently newer than the hot fix versions (6.5.7653.5) Cdo.dll - 6.5.7654.12 Cdoex.dll - 6.5.7654.12 Davex.dll - 6.5.7654.12Excdo.dll - 6.5.7654.12Exoledb.dll - 6.5.7654.12Lsmexhc.dll - 6.5.7654.12Madfb.dll - 6.5.7654.12 Two dll's are older and one is not present.Massync.dll - 6.5.7638.1Microsoft.exchange.oma.userinterface.dll - 6.5.7638.1Rtdsmcal.dll - Not Found Since many dll’s would be backdated I’d rather not install the hotfix. Any risk of just adding the FixRecipientTrackStatusTime reg key mentioned in the KB, without installing the hotfix?Anyone know the purpose of Rtdsmcal.dll?

This issue has been going on too long.Can anyone answer these questions?What is the risk of just adding the FixRecipientTrackStatusTime reg key mentioned in the KB, without installing the hotfix?Does anyone know the purpose of Rtdsmcal.dll? is it nessasary? Thanks.

David, Any luck with this? We are having the same issue and installed a patch to get the updates moving through the queue. We found that if OL 2007 users sent an external email, it would go through fine, but when they attempted to update the meeting request, the update would hang in the SMTP queue and NDR later on. We installed patch KB938650 and it solved the issue, but now we are getting duplication on a lot of our meeting updates on internal meetings. Microsoft Support is havin us try a bunch of things to no avail. The RTDSMCAL.dll was missing as well and MSS had us stop the Exch services, register that dll then start the services again. The dll did not register and we still have this issue. They are talking about massive mailbox corruption, which I can't see. Phil