Recurring Appointments through Outlook 2003

[Guest]

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.

 

[Ben M. Schorr - MVP]

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.

Out of curiousity -- why can't you use cache mode in your environment? It's
generally preferable -- faster, less network traffic, enables junk
filtering...


--
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
Roland Schorr & Tower
http://www.rolandschorr.com
Microsoft OneNote FAQ: http://www.factplace.com/onenotefaq.htm

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

 

[Guest]

Because we're running a ts environment, and don't want to waste un-necessary
space on the file server.

Like I said, cache mode is not an option for this issue.

 

[Guest]

BTW - I figured out a solution for this; unfortuntely it wasn't a outlook
problem but rather our Exchange 2003 server that was hiccuping.

I find it rather discouraging that the online support for MS products is
crap, and the so-called "experts" or MVPs have no idea about the product they
speacialize in.

Don't get me started with the product support people that MS employs; the
exchange specialist that I had to deal with had no idea what I was talking
about.

Whatever, just gives me another excuse not to go with this turbanware.

 

[Milly Staples [MVP - Outlook]]

Excuse me? Did you not say it was an Exchange problem? When did you query
the Exchange MVPs? And why should the Outlook MVPs know anything at all
about Exchange, since it is an entirely separate product? Did you use
Exchange 2003 as your basis for a query of the Microsoft Knowledge Base
Library?

As for your final comment, perhaps Microsoft is better off not having a
person of your prejudice using its products. Gives the company a bad name.


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Fergie74 asked:

| BTW - I figured out a solution for this; unfortuntely it wasn't a
| outlook problem but rather our Exchange 2003 server that was
| hiccuping.
|
| I find it rather discouraging that the online support for MS products
| is crap, and the so-called "experts" or MVPs have no idea about the
| product they speacialize in.
|
| Don't get me started with the product support people that MS employs;
| the exchange specialist that I had to deal with had no idea what I
| was talking about.
|
| Whatever, just gives me another excuse not to go with this turbanware.
|
| "Fergie74" wrote:
|
|| 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.

 

[Guest]

what did you do onExchange to fix it?? I get the same error.

thx