Outlook 2003 Calendar meeting accepted, but then shows as tentative

[stuart.corrigan]

We have both delegates and users that accept a meeting (on behalf off
or directly), but the next day the meeting shows as 'Tentatively
Accepted'
To fix, we have tried:
Creating complete new Outlook profile, including deleting the Outlook
Regisrty keys.
Run MfcMapi Editor on mailbox to delete PR_FREEBUSY_ENTRYIDS and then
started Outlook with the cleanfree/busy, /cleanreminders, /sniff, /
cleansniff and /resetfoldernames switches.

It looks like a sever issue toi me, but if any one has any ideas, that
would be brilliant!
Cheers, Stuart

 

[TechieBird]

Hi Stuart

If you don't already, try running for a while with the "send meeting
requests and responses only to my delegates, not to me" option checked. Even
if you can't live with this switched on permanently, it will help narrow down
the cause if you run with it for a while and note whether the problem still
occurs.

Also see http://office.microsoft.com/en-gb/help/HA011276781033.aspx and make
sure you and your delegates follow the advice religiously - the vast majority
of strange calendar behaviour I see resolves itself when everyone is using
that as a guide.

 

[Stuart C]

Hi Stuart

If you don't already, try running for a while with the "send meeting
requests and responses only to my delegates, not to me" option checked. Even
if you can't live with this switched on permanently, it will help narrow down
the cause if you run with it for a while and note whether the problem still
occurs.

Also seehttp://office.microsoft.com/en-gb/help/HA011276781033.aspxand make
sure you and your delegates follow the advice religiously - the vast majority
of strange calendar behaviour I see resolves itself when everyone is using
that as a guide.

--
TechieBirdhttp://bwain-dump.blogspot.com






- Show quoted text -

Thanks TechieBird,

All the users I have checked so far have the box "send meeting
requests and responses only to my delegates, not to me" option
checked.

Just for info, our users have BlackBerrys and connect to Exchange via
Outlook SP2.
Cheers, Stuart

 

[TechieBird]

Hmmm... that does rule out most of what I'm thinking of.

It might be worth investigating the 'berry angle though - CDO (which BES
uses to sync with Exchange) is notoriously twitchy. I'm a bit out of date in
that field though -but I expect there's plenty of information around. I just
googled for "blackberry CDO calendar appointment tentative" (without quotes)
and got some promising looking hits...

 

[Stuart C]

Hmmm... that does rule out most of what I'm thinking of.

It might be worth investigating the 'berry angle though - CDO (which BES
uses to sync with Exchange) is notoriously twitchy.  I'm a bit out of date in
that field though -but I expect there's plenty of information around.  Ijust
googled for "blackberry CDO calendar appointment tentative" (without quotes)
and got some promising looking hits...

Hi Techie,

Sorry for delay.
Microsoft are on the case with this, I have sent them a load of ETL
logs.
I let you know once cause is found.
Cheers, Stuart

 

[Stuart C]

Hi Techiebird,

We finally have confirmation that this is by BlackBerry Enterprise
Server:
The issue that you are describing is a result of changes made to the
BlackBerry Enterprise Server (4.0.7 and 4.1.4 MR2), which was done to
accommodate changes made to Cdo.dll by Microsoft. Additional
information about the changes made to Cdo.dll can be found in
Microsoft KB 932511. Research In Motion is tracking the issue that you
are currently experiencing via SDR144817.

Cheers,
Stuart