Duplicate attendee names appear when invitation and response was n

[Jeff]

After inviting multiple attendees to a meeting. Users respond a single time,
but show up in the attendee list multiple times. The names show up multible
times in the invitation list and in the accepted list. Invitees were not on
the invitation list multiple times when the invitation went out. This users
account was tried on several machines with the same issue. The problem seems
to be with one users email.

 

[Jeff Huston]

Do you have Blackberry devices in use at your organization? We have a
similar problem and we're only seeing it on users with blackberrys.

 

[Jeff]

Yes, we do have some blackberry's, but none of the attendee's that are having
the problem have these devices.

 

[Jeff Huston]

We have seen this happen especially when the person who has a blackberry also
has a delegate and that delegate is usually the one who notices the problem
with a meeting request on the blackberry user's calendar.

 

[Jeff]

Is there a fix for this?

We have seen this happen especially when the person who has a blackberry also
has a delegate and that delegate is usually the one who notices the problem
with a meeting request on the blackberry user's calendar.

 

[Jeff Huston]

That's exactly what I'm trying to find out.

Is there a fix for this?

 

[Jen Hays via OfficeKB.com]

did you ever find out a solution this problem. We are seeing the same thing here.

 

[Gaz]

We are having the same problem too. So far. it has only been reproduced with
users who also have a Blackberry account. With Exchange only users, I
couldn't reproduce the problem.

I'm poking around Blackberry's support site at the moment and will post
again if a resolution is found.

 

[rmurray Murray via OfficeKB.com]

Same issue at my work, Blackberry users and Exchange 5.5 and Outlook 2002. Just started last week. I have looked all over the web and have found very little. Please post when or if you have something.

Thank you.
rmurray

 

[Milly Staples [MVP - Outlook]]

I have seen a lot of problems with Blackberries - it is probably something
on their end. I would look into their Knowledge Base articles to see if
they have identified the culprit.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After furious head scratching, rmurray Murray via OfficeKB.com asked:

| Same issue at my work, Blackberry users and Exchange 5.5 and Outlook
| 2002. Just started last week. I have looked all over the web and
| have found very little. Please post when or if you have something.
|
| Thank you.
| rmurray

 

[rmurray Murray via OfficeKB.com]

Thank you i will. If I find anything i will let you know.

Thanks

 

[cdunn]

We've been having the same issue at our company. Does anybody know if it is
a result of the organizer of the meeting having a blackberry or the invitees
accepting the meeting request from their blackberry? I think its an issue
with the organizer having a blackberry but I wasn't sure what everybody else
thought.

 

[rmurray Murray via OfficeKB.com]

Our issue is comming from an admin for a manager. The manager has a Blackberry. Thanks.

 

[cdunn]

I talked to blackberry about this issue and they say it is a known issue with
the Blackbery Enterprise verion 3.6.3.17. They say that it would be fixed if
we upgraded our Blackberry Enterprise software to sp4. We haven't tested
this yet but I wanted to post this before I forgot.

 

[ed_bak]

You need to apply BES Server 3.6 SP4 and a Post SP4 hotfix which fixes
this problem. (Existing calendar items will need to be manually fixed
as the hotfix only prevents the problem from occuring).

Also, if running Exchange 2000 you should apply Post SP3 rollup fixup
-> http://support.microsoft.com/kb/870540 and
http://support.microsoft.com/default.aspx?scid=kb;en-us;886688

Ensure that the CDO.DLL version is the same version on the BES and
Exchange servers (including any OWA servers).

This solved this issue for us.