Unable to display folder

[Guest]

I have a user that is getting the subject error message when trying to view
his Calendar and his Personal Folders. We are using Exchange 2003 - NOT in
cached exchange mode. The issue didn't arise until after he came back from a
trip. On this trip, he accessed his e-mail via Outlook Web Access. The web
address showing for his Calendar is "outlook:xxxxxxx" - which is a long
string of letters and numbers. If I change it to "outlook:calendar", he is
fine. I have tried selecting "Restore Defaults" in Outlook Today -> Home
Page, but that does not resolve the issue.

 

[Guest]

Can you please explain what the user is clicking when they get the error
message? If they select the Calendar from the folder view does it work OK?
Does the Calendar folder have the correct name (i.e. Calendar) from the
folger view?

Thanks

 

[Guest]

The user clicks on his Calendar, and it says that it's unable to display the
folder. The path on the web toolbar shows "outlook:xxxxxxx" (x's = long
string of letters and numbers) instead of "outlook:Calendar". I logged in as
myself on his machine, and the same thing happened with setting up my
account. My E-mail Administrator informed me that an update was pushed out
to his machine while he was gone, so I'm going to try removing that update to
see if that was the cause of the problem.

 

[Guest]

Sounds like a good move. If you need to post back, please include your
Outlook version.

 

[Guest]

It still isn't working. I also tried reinstalling Outlook. We are using
Office 2003 with Exchange Server 2003.

 

[Guest]

The fact it happens logged in as you on the same machine suggests it isn't
anything in the user's profile. All the possible fixes I can think of are
profile-specific so, frankly, I'm stumped.

Perhaps someone else has some ideas that could help...

 

[Guest]

I tried reimaging the user's machine, but the issue was still there. I got
so frustrated that I logged onto my own machine as him, and his mailbox was
fine. So, then, after I logged back onto his newly-reimaged machine, it was
fine. So, I'm really stumped as to why this all happened.