Outlook Calendar Problem

Hi,

I run a network that uses Exchange for e-mail. I have a user in one of our branch offices that is having some strange problems with his calendar. He uses Outlook 2002.

His calendar opens fine but when he goes to add a new appointment, the time always defaults to the next 30 minute increment from the current time. So here's a little run-down of what happens.

He opens Outlook.
He clicks Calendar.
He picks a date. For this example lets say it's April 10th.
He picks a time. Lets say 1 pm.
He double clicks the block for 1 pm.
A new appointment opens up. The starting time defaults to March 20th at 10:30 am instead of April 10th at 1 pm.

I've tried running a repair and completely reinstalling Office on his machine. The really strange thing is that this problem follows his exchange account. I've added his username as a profile on my local machine and it happens for him here as well. When I log in with my username however, I don't have the problem.

Anybody else ever run into this problem?

 

The first week of the year is January 1st. And his system clock is ok. It always creates the new appointment at the next 30 minute interval regardless of where he tries to create it. Trying to open an appointment for June 3rd at 11 am and then creating one for April 10th at 4 pm will create 2 appoints for today at 5 pm (it's 4:58 as of this writing.)

 

I poked around a little bit more today. The problem with his Outlook calendar follows around his exchange account. I've opened his profile on my laptop with Outlook 2003 and that profile still has the same timing issues.

 

Unfortunately all of his calendar options were the exact same as mine and my calendar works just fine. The tool didn't come up with anything either. I'm guessing my only course of action now is to remake his exchange account which I'm not terribly excited about doing.

Thanks for the help though.

 

I found the problem. In his calendar views, his start and end fields were changed to Recurrence Range Start and Recurrence Range End. After changing them back to the default Start/End, it took care of the problem.