Outlook 2007 and Exchange Server 2003 - No end dates in OL2007

[Stephen White]

Hi folks - I have tracked down, I believe, the source of my problem with
appointments which appear in OL2003 as viewed through Terminal Server not
showing up when I connect to the exchange server from my desktop using
OL2007. And I do not have an iPhone.

I found that, when viewing my appointments in the "View All" mode in OL2003
via TS, all the appointments have end dates (as they should). When I view
them in OL2007 however, the majority of them do not have an end date and
consequently do not appear, or do not appear properly, in Day/Week/Month
view. However, when double clicked to edit the properties of the
appointment, the end date dialogue box clearly indicates the end date.
Rechoosing the identical end date from the pull down menu results in OL2007
accurately registering it because after clicking Save/Close, that
appointment will then show up in Day/Week/Month mode.

To reiterate, the appointment is being recognized properly in OL2003 run off
of Terminal Server but not when connected in cached mode in OL2007.

I have deleted the OST file but the appointments get recreated in the faulty
manner. I have cleared all offline items in the calendar but same issue. I
have "reset view" in Customize Current View. I have deleted the
frmcache.dat, extend.dat, Views.dat and Outcmd.dat files to have them
recreated but that didn't work either.

Now I have been synchronizing my HTC Touch (WM 6.1) for over a year and the
appointments with no end date where not only created on the Touch so I don't
think it is a WM synch issue. I am running Vista, btw.

Any suggestions?

Thanks!

SW

 

[Thomas Everritt]

We are experiencing the same problem using EX03. All appointments appear on
the Terminal Server with OL03 client and on the T-mobile Dash but some
appointments disappear using both OL03 and OL07 on the local computer. When
you open the all appointments view, the missing appointments have no end
date. The fix is as you describe.

The only common denominator we have found is the mobile synchronization.
Have not seen the problem using BES.