Microsoft KB Archive/312013

From BetaArchive Wiki
Knowledge Base


OFFXP: Outlook MAPI Message Store Cannot Handle Free Threaded Access

Article ID: 312013

Article Last Modified on 10/26/2006



APPLIES TO

  • Microsoft Outlook 2002 Standard Edition



This article was previously published under Q312013

SYMPTOMS

When applications such as Microsoft SQL Mail try to use the Outlook Messaging Application Programming Interface (MAPI) message store (Mspst32.dll) to handle free threaded access, the session context is shared between multiple threads; at some point, the following call starts to fail:

pInbox->OpenEntry(...) with hr = 80040107


If Mspst32.dll is not used for access, everything appears to be properly synchronized.

CAUSE

This problem can occur if the OpenEntry call on the folder is not correctly protected by a critical section.

RESOLUTION

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

307841 OFFXP: How to Obtain the Latest Office XP Service Pack


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

   Date          Time    Version     Size        File name     
   ----------------------------------------------------------
   Oct-19-2001   21:42   10.0.3409     133,448   Contab32.dll
   Oct-19-2001   21:42   10.0.3318     108,872   Emablt32.dll
   Oct-19-2001   21:42   10.0.3131     194,888   Emsabp32.dll
   Oct-19-2001   21:42   10.0.3409     538,952   Emsmdb32.dll
   Oct-19-2001   21:42   10.0.3117     125,256   Emsui32.dll
   Oct-19-2001   21:42   10.0.3311     850,248   Msmapi32.dll
   Oct-19-2001   21:42   10.0.3207     526,664   Mspst32.dll
   Oct-19-2001   21:42   10.0.3311     735,560   Outex.dll
   Oct-19-2001   21:42   10.0.2915   1,972,552   Outllibr.dll
                



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 XP Service Pack 1.

Keywords: kbhotfixserver kbqfe kbbug kbfix kbofficexppresp1fix kbofficexpsp1fix KB312013