OL2000: Outlook Can Generate an Access Violation When a Meeting Request Is Processed in the Inbox

View products that this article applies to.

This article was previously published under Q320511

Expand all | Collapse all

SYMPTOMS

Outlook 2000 may generate an access violation when a meeting request is processed in your Inbox.

Back to the top

When you copy a meeting appointment to your Calendar and then forward that meeting from your Calendar to another user, a property is deleted from the meeting request that is received by the other user. Outlook 2000 cannot always handle the situation of the missing property correctly. If the meeting attendee has a delegate, Outlook 2000 may not handle this situation correctly and you receive an access violation.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

276367 (http://support.microsoft.com/kb/276367/EN-US/ ) OFF2000: How to Obtain the Latest Office 2000 Service Pack

The English-language version of this fix should have the following file attributes or later:

   Date        Time    Size      File name     
   -----------------------------------------
   01-Jul-2002 11:05  2,676,224  Outlook.msp

After the fix is installed, the English version of this fix will have the file attributes (or later) 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 tool in Control Panel.

   Date        Time   Version      Size      File name     
   -------------------------------------------------------
   14-Jun-2000 13:11  1.0.3.27       41,472  Bjablr32.dll
   14-Jun-2000 13:12  3.2.0.27       61,952  Bjlog32.dll
   08-Jan-2001 17:37  1.0.3.28       98,304  Bjsrch32.dll
   17-Sep-2001 14:39  5.5.2655.46   709,904  Cdo.dll
   17-Sep-2001 14:55  5.5.2655.46   812,304  Cdo.dll_0004
   01-Dec-2001 22:00  9.0.0.5930    127,027  Contab32.dll_0002
   14-Jun-2000 13:14  1.0.3.27      183,808  Emablt32.dll
   31-Aug-2000 15:43  5.5.3142.0    154,112  Emsabp32.dll_0005
   05-Oct-2001 06:33  5.5.3165.0    594,192  Emsmdb32.dll_0005
   01-Jun-2001 21:15  5.5.3159.0    131,344  Emsui32.dll_0005
   02-Jun-2000 06:45  9.0.0.4201     86,067  Envelope.dll
   18-Dec-2001 19:19  5.5.3167.0    540,944  Exsec32.dll_0005
   05-Apr-2000 15:02  9.0.0.4005    192,561  Mimedir.dll
   02-Apr-2002 20:04  5.5.3169.0    792,576  Msmapi32.dll_0001
   02-Apr-2002 20:01  5.5.3169.0    623,104  Msmapi32.dll_0002
   07-Jun-2002 16:47  5.5.3171.0    602,384  Mspst32.dll_0004
   07-Jun-2002 16:44  5.5.3171.0    528,656  Mspst32.dll_0005
   31-Jan-2000 21:26  9.0.0.3731    196,661  Oladd.fae
   23-May-2000 11:20                150,690  Olexchng.aw
   30-May-2000 14:53                 26,643  Olsec9.chm
   22-May-2000 19:35                170,617  Olxchng9.chm
   08-Feb-2001 13:17  5.5.3153.0    454,144  Omi9.dll_0001
   08-Feb-2001 13:21  5.5.3153.0    548,352  Omint.dll_0001
   06-Jun-2001 13:05                129,024  Out2ksec.mst
   15-Jun-2002 01:19  8.30.3172.0   782,608  Outex.dll
   23-May-2000 19:19                554,068  Outlhlp.aw_0001
   28-Jun-2002 22:25  9.0.0.6627  5,337,138  Outllib.dll
   31-Aug-2001 20:02  9.0.0.5630  1,675,315  Outllibr.dll
   29-Apr-2002 22:52  9.0.6425.0    368,691  Pstprx32.dll_0002
   21-Jun-2001 18:01  9.0.0.5421     73,772  Rm.dll
   02-Jun-2000 07:30  9.0.0.4201     65,586  Sendto9.dll

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft Office 2000 Service Pack 3 (SP-3).

Back to the top