From: Brian Tillman [MVP-Outlook] on
"MCM" <mcmalburg(a)digitalmetrology.com> wrote in message
news:f33d6cb2-96e3-4400-bb53-a23bbafdb75b(a)c16g2000yqd.googlegroups.com...

> -Active-
> Google Desktop Outlook Toolbar
> Infuzer Outlook Writer
> Microsoft Exchange Unified Messaging
> Microsoft Office ShartPoint Server Colleague Import Add-in
> Microsoft Outlook Mobile Service
> PDFMOutlook
> Sindows Search Email Indexer

Try disabling Google Desktop Outlook Toolbar, Infuzer Outlook Writer,
PDFMOutlook, and Sindows Search Email Indexer and test again. You'll need a
new message, since messages already received won't change. Reenable them one
at a time and retest between each reenablement. That should determine whether
or not one of them is the culprit.
--
Brian Tillman [MVP-Outlook]

From: MCM on
I've disabled all Add-ins (COM and Exchange Client)... my test meeting
request is still messed up.

Could it have something to do with the fact that it originated from a
customer in the UK and I'm in the US? I can see the meeting request
correctly in my web mail interface and on my Blackberry. Outlook 2007
is the only thing that can't seem to decipher it.

Still frustrated.
From: Brian Tillman [MVP-Outlook] on
"MCM" <mcmalburg(a)digitalmetrology.com> wrote in message
news:a6e6024a-7f13-4e0f-b535-4354874db689(a)19g2000yqu.googlegroups.com...

> I've disabled all Add-ins (COM and Exchange Client)... my test meeting
> request is still messed up.
>
> Could it have something to do with the fact that it originated from a
> customer in the UK and I'm in the US? I can see the meeting request
> correctly in my web mail interface and on my Blackberry. Outlook 2007
> is the only thing that can't seem to decipher it.

I doubt the point of origin matters. Something about the message isn't
permitting Outlook to decode the message properly and in the vast majority of
cases, it's am add-in of some kind on the local PC that's wedged between
Outlook and the server causing a disruption or alteration in the data stream.
You've assured me that in your case it is not, so I really can't think of what
else it might be. Perhaps someone else will have an idea. Sorry I couldn't
solve the problem.
--
Brian Tillman [MVP-Outlook]