F
Fergie74
Hello;
After a frustrating 48 hours with this issue and the lack of help and
acknowledgement of this issue from MS, I've decided to give this group a shot.
Here's the issue at hand; When a user tries to open, edit or delete a
recurring appointment from Outlook 2003, they get the following error
message(s):
"Can't open this item. The operation failedâ€
Or
“Cannot read one instance of this recurring appointment. Close any open
appointments and try again, or recreate the appointmentâ€
When they try to change the time by dragging the appointment, they get the
following message:
"The item may not have been deleted correctly. If somone sent you the item,
that person's copy of the item may not be updated. The operation failed."
I tried the two suggestions that I found on google; deleting the the
frmcache.dat file (didn't work) and putting the outlook profile into cache
model. Although this method works, its not doable for our environment. So
please don't suggest that.
It looks as though this has been an issue with various versions of outlook;
if memory serves me correct it started with Outlook 98.
This is pretty much affecting the entire user population; we're running
Outlook 2003 with a exchange 2003 enterprise back end.
I need Attainable solutions to this problem. Any help would be beneficial.
After a frustrating 48 hours with this issue and the lack of help and
acknowledgement of this issue from MS, I've decided to give this group a shot.
Here's the issue at hand; When a user tries to open, edit or delete a
recurring appointment from Outlook 2003, they get the following error
message(s):
"Can't open this item. The operation failedâ€
Or
“Cannot read one instance of this recurring appointment. Close any open
appointments and try again, or recreate the appointmentâ€
When they try to change the time by dragging the appointment, they get the
following message:
"The item may not have been deleted correctly. If somone sent you the item,
that person's copy of the item may not be updated. The operation failed."
I tried the two suggestions that I found on google; deleting the the
frmcache.dat file (didn't work) and putting the outlook profile into cache
model. Although this method works, its not doable for our environment. So
please don't suggest that.
It looks as though this has been an issue with various versions of outlook;
if memory serves me correct it started with Outlook 98.
This is pretty much affecting the entire user population; we're running
Outlook 2003 with a exchange 2003 enterprise back end.
I need Attainable solutions to this problem. Any help would be beneficial.