Article ID: 329375 - View products that this article applies to.
This article was previously published under Q329375
BUG #: 362441 (SHILOH_BUGS)
Concurrent SQL Mail activity can result in exception access violations.
The following stack traces may appear in the SQL Server error log:
* Short Stack Dump * 77F821E1 Module(ntdll+000021E1) (NtSetInformationThread+00000005) * 77E11CCA Module(USER32+00001CCA) (UserRegisterWowHandlers+00000220) * 77E183F1 Module(USER32+000083F1) (CharPrevA+00000010) * 7E816608 Module(UNKNOWN+00000000) * 36353038 Module(UNKNOWN+00000000) * 34393430 Module(UNKNOWN+00000000)
* Short Stack Dump * 05A962B8 Module(MSMAPI32+000262B8) (MAPIOpenFormMgr+00000ED6) * 05C32658 Module(UNKNOWN+00000000)
* Short Stack Dump * 05A7FF71 Module(MSMAPI32+0002FF71) (FBadEntryList+000000B3) * 15FF0824 Module(UNKNOWN+00000000) * 3053414C Module(UNKNOWN+00000000) * 0014BD26 Module(UNKNOWN+00000000) * 35393730 Module(UNKNOWN+00000000)
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How To Obtain the Latest SQL Server 2000 Service Pack
The English version of this fix has 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.
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
Date Time Version Size File name -------------------------------------------------------------------- 09/07/2002 17:47:02 2000.80.687.0 172,600 bytes Sqlmap70.dll
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986This fix works with a registry entry, MAPI_NO_MAIL_flag. If you turn on MAPI_NO_MAIL_flag, you might avoid the access violations. To add and to turn on the MAPI_NO_MAIL_flag registry entry, use Regedt32.exe and locate this registry key:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
For a computer with an instance of SQL Server:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServerFor a computer with a default instance:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServerUnder the MSSQLServer key, add a DWORD value, and then name it MAPI_NO_MAIL_flag. Set its value data to 1.
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 SQL Server 2000 Service Pack 3.