The information in this article applies to:
SYMPTOMSWhen making a dynamic link library call to MAPILogon from a 32-bit application directly to MAPI32.DLL, the call will fail from a custom command or a custom message in the Windows NT Mail client. The failure occurs in a MAPI error 2 (MAPI_E_FAILURE) which implies a general failure. CAUSEThis problem occurs when the extension DLL is called while the Mail32 internal lock is on. When the DLL attempts to call out to MAPI, MAPI waits for the internal lock to be released and hangs. STATUSMicrosoft has confirmed this to be a problem in Windows NT version 3.5. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix. Additional query words: prodnt
Keywords : kbusage MailPCMAPI NTInterop kbbug3.50 SMapiCMC |
Last Reviewed: October 12, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |