asked on

Microsoft, Outlook, 2003 Calendar Sync Problems

I am using Outlook 2003 along with Exchange 2003. Outlook seems to have lost ebtries from some days in my calendar. This only seems to be a problem with Outlook istself as wheen viewing the calendar from OWA then all entries are where they should be. I have tried removing the Outlook profile fromt the local PC and re-adding, but stilll same. Your help on this is most appreciated.

Sembee

When you deleted the profile, did you also remove the OST file?
Have you checked there isn't a view that could be hiding the entries you cannot see?

Simon.

m1ndg4m3

ASKER

No i didnt remove the OST file, maybe i should try that. Yes i checked most filters and view settings i could think of, but none seem to relate to the issue.

m1ndg4m3

ASKER

Ok have tried completely deleted the ost files too. No change. I am testing this by looking at a particular date. Now on that date in OWA there is a full day of appointments, but in Outlook nothing. Very strange indeed.

m1ndg4m3

ASKER

I found a similar problem here -

https://www.experts-exchange.com/questions/21755080/Outlook-2003-Calendar-is-missing-meetings-when-in-cached-mode.html

And sure enough when i turn off cache mode, all calendar items appear. I have tried all solutions in the above article but still no solution. Any ideas?

Sembee

OWA and out of cached mode is using a live connection to the database. Cached mode is using an offline copy of the data.
Does the problem follow to another machine?

Simon.

m1ndg4m3

ASKER

Yes this i what i am saying the problem dissapears when using the live connection. I have tried this on another system and no the problem does not follow, so seems to be this particular system that is the problem. But i have deleted the cache a few times now and still the problem. Could it be a posible disk fault i ask myself?

ASKER CERTIFIED SOLUTION

Sembee

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

m1ndg4m3

ASKER

In correction to what was earlier stated, the problem has indeed followed to another machine. Again the only way to correct this is by turning off cache mode. For the moment this is what i have done, to keep the guy working until i find a solution.