When Microsoft Exchange Server 2003 users who have
ActiveSync enabled access their mailboxes through a Microsoft Office Outlook client, they receive "overdue" reminders
for recurring appointments even
though they have already dismissed these reminders.
Notes- Users receive these "overdue" reminders for recurring
meetings that are
scheduled for the day that the reminders are received.
These reminders indicate "x days overdue" or
"xx hours overdue."
- The user receives an "overdue" reminder for the latest
occurrence of
the recurring meeting.
- If you dismissed the latest occurrence
of the recurring meeting,
this does not affect the problem.
This issue occurs because the information about the next
scheduled delivery of a reminder for a recurring meeting may be lost during
calendar synchronization between a Windows Mobile device and Exchange Server
2003.
Hotfix information
A
supported hotfix is available from Microsoft. However, this hotfix is intended
to correct only the problem that is described in this article. Apply this
hotfix only to systems that are experiencing the problem described in this
article. This hotfix might receive additional testing. Therefore, if you are
not severely affected by this problem, we recommend that you wait for the next
software update that contains this hotfix.
If the hotfix is available
for download, there is a "Hotfix download available" section at the top of this
Knowledge Base article. If this section does not appear, contact Microsoft
Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. For a complete list of Microsoft Customer Service and
Support telephone numbers or to create a separate service request, visit the
following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have Exchange Server 2003 Service
Pack 2 installed on the server.
For more information, click the following article number to view
the article in the Microsoft Knowledge Base:
836993 Â
(http://kbalertz.com/Feedback.aspx?kbNumber=836993/
)
How to obtain the latest service packs for Exchange Server 2003
Restart requirement
You do not have to restart the computer after you apply this
hotfix. However, the following services are restarted automatically when you
apply this hotfix:
- The Microsoft Exchange System Attendant service
- The Microsoft Search service
- The Internet Information Services (IIS) Admin Service and
all dependent services
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file
attributes (or later file attributes) that are listed in the following table.
The dates and times for these files are listed in Coordinated Universal Time
(UTC). When you view the file information, it is converted to local time. To
find the difference between UTC and local time, use the
Time
Zone tab in the
Date and Time item in Control
Panel.
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time |
|---|
| Cdo.dll | 6.5.7655.3 | 724,992 | 04-Apr-2009 | 01:43 |
| Cdoex.dll | 6.5.7655.3 | 3,971,584 | 04-Apr-2009 | 07:16 |
| Davex.dll | 6.5.7655.3 | 1,135,616 | 04-Apr-2009 | 07:12 |
| Excdo.dll | 6.5.7655.3 | 3,657,216 | 04-Apr-2009 | 07:16 |
| Exoledb.dll | 6.5.7655.3 | 2,621,440 | 03-Apr-2009 | 16:12 |
| Exosal.dll | 6.5.7655.3 | 70,144 | 04-Apr-2009 | 06:58 |
| Lsmexhc.dll | 6.5.7655.3 | 143,872 | 04-Apr-2009 | 01:46 |
| Madfb.dll | 6.5.7655.3 | 526,336 | 04-Apr-2009 | 07:16 |
| Mdbmsg.dll | 6.5.7655.3 | 3,384,832 | 04-Apr-2009 | 02:19 |
| Rtdsmcal.dll | 6.5.7655.3 | 40,960 | 04-Apr-2009 | 02:08 |
| Store.exe | 6.5.7655.3 | 5,267,968 | 04-Apr-2009 | 07:00 |
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.