Can't delete empty calendar folders from Exchange server

[Darryl Zurn]

I am using Entourage 2004 11.2.3 with an Exchange server. Perviously I have
used Entourage X and Outlook for my calendars/emails etc.

Now using Entourage 2004, I have several calendars I've made in a futile
effort to get my free/busy information to match the calendar events I have.
Now I have two extra calendar folders ("Calendar1" and "Calendar sm") that
can't be deleted. I tried to right-click to select the "delete calendar"
contextual menu but that one is greyed out.

And Outlook Web Access thinks that "Calendar sm" is my real calendar, and of
course won't delete it .

How can I delete the empty calendars or at least make OWA, Free/Busy, and
Entourage use the SAME calendar for these three things?

Thanks in advance.

Darryl Zurn

 

[Andy Ruff]

Your f/b info is generated by your primary calendar, typically called
"Calendar." The primary calendar is the one displayed in OWA when you press
"Calendar"--in your case, this sounds like "Calendar sm." If Calendar1 is
owned by you and cannot be deleted, I'd first try emptying the cache on your
Exchange account and seeing if this resets your calendar permissions when it
redownloads all the events.

Free/Busy information is actually generated by the Exchange server, not
Entourage. Entourage merely tells the server about an event and it's up to
the server to generate the appropriate free/busy information.

-Andy

 

[tgash70]

Andy,

I am trying to fix this issue as well. Your reply to Darryl explained
what the cause what but not how to actually fix it. Do you know of a
documented procedure to fix this problem?

Thank you
Tom

 

[tgash70]

Andy,

I am trying to fix this issue as well. Your reply to Darryl explained
what the cause what but not how to actually fix it. Do you know of a
documented procedure to fix this problem?

Thank you
Tom

 

[Allen Watson]

Andy,

I am trying to fix this issue as well. Your reply to Darryl explained
what the cause what but not how to actually fix it. Do you know of a
documented procedure to fix this problem?

Andy said: "I'd first try emptying the cache on your
Exchange account"

Locate the Exchange account in the folder list. Right click on it. Select
"Empty cache" from the popup menu.