K
Katy M via OfficeKB.com
Hi,
We have 5 users affected by the following problem: They receive a meeting
request from an external source (i.e. for 8pm on August 9th 2005), but as
soon as the open the meeting request, the time and date change to approx
30mins in the future. e.g if the users opens the request at 12:20pm on
August 8th 2005, the meeting time & date change to 12:30pm on August 8th 2005.
Both the sender and recipient are in the same time zone and country and the
appointment still shows correctly for the sender and any other recipient
apart from these 5 users. The problem is machine specific as I can log on as
the user on another machine and the time/date shows up correctly. They are
running Windows XP SP2, with Office 2003 SP1.
I have discovered that the problem only occurs as long as Cached Mode is
enabled on their computer - as soon as Cached Mode is disabled, the problem
disappears. Has anyone else experienced this problem, or can anyone give me
an explanation as to why the problem is happening? It seems strange that
only 5 out of approx 150 users are affected. Any assistance would be greatly
appreciated.
Thanks,
Katy.
We have 5 users affected by the following problem: They receive a meeting
request from an external source (i.e. for 8pm on August 9th 2005), but as
soon as the open the meeting request, the time and date change to approx
30mins in the future. e.g if the users opens the request at 12:20pm on
August 8th 2005, the meeting time & date change to 12:30pm on August 8th 2005.
Both the sender and recipient are in the same time zone and country and the
appointment still shows correctly for the sender and any other recipient
apart from these 5 users. The problem is machine specific as I can log on as
the user on another machine and the time/date shows up correctly. They are
running Windows XP SP2, with Office 2003 SP1.
I have discovered that the problem only occurs as long as Cached Mode is
enabled on their computer - as soon as Cached Mode is disabled, the problem
disappears. Has anyone else experienced this problem, or can anyone give me
an explanation as to why the problem is happening? It seems strange that
only 5 out of approx 150 users are affected. Any assistance would be greatly
appreciated.
Thanks,
Katy.