G
Guest
This is not the same error most people get when sharing a calendar. This has
me stumped.
I have an Exchange 2000 Server with Outlook 2003 clients. I've updated all
Outlook 2003 clients to the latest updates and Exchange has the latest
service pack and updates.
When clients change the day view on a PUBLIC CALENDAR to 31 days and scroll
to the next month, they get the error "Could not read the calendar. You don't
have appropriate permission to perform this operation." Once you click Ok, it
allows you to view the data normally.
What's really strange is a user WITH APPROPRIATE PERMISSIONS can add an
entry, then once they switch over to do something in a local folder and
switch back to the public calendar, the entry they've made earlier
disappears. Some others in the office are able to see these entries and some
aren't. I've tried renaming the folder, I've tried exporting the data out
(which is substantial at this point) and putting it into a new public
calendar, none of which has solved the problem.
We need a solution to this problem. Has anyone else experienced this?
me stumped.
I have an Exchange 2000 Server with Outlook 2003 clients. I've updated all
Outlook 2003 clients to the latest updates and Exchange has the latest
service pack and updates.
When clients change the day view on a PUBLIC CALENDAR to 31 days and scroll
to the next month, they get the error "Could not read the calendar. You don't
have appropriate permission to perform this operation." Once you click Ok, it
allows you to view the data normally.
What's really strange is a user WITH APPROPRIATE PERMISSIONS can add an
entry, then once they switch over to do something in a local folder and
switch back to the public calendar, the entry they've made earlier
disappears. Some others in the office are able to see these entries and some
aren't. I've tried renaming the folder, I've tried exporting the data out
(which is substantial at this point) and putting it into a new public
calendar, none of which has solved the problem.
We need a solution to this problem. Has anyone else experienced this?