FIX: SQL Mail Operations Are Not Thread Safe When You Use Them in Conjunction with the xp_stopmail Stored Procedure (307932)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions) SP1
This article was previously published under Q307932
BUG #: 355601 (SHILOH_BUGS)
SYMPTOMS
Starting with SQL Server 2000 Service Pack 1 (SP1), issuing a xp_stopmail stored procedure while other SQL Mail activities ( xp_readmail, xp_deletemail, xp_findnextmsg, xp_sendmail) are running may lead to unexpected errors.
The unexpected errors that may occur include:
- Memory leaks.
- Unexpected MAPI error conditions.
- MAPI spooler problems.
- The overall stability of SQL Server can be compromised.
CAUSE
Internal reference count activity of the MAPI profile leads to an incorrect release of the MAPI interfaces during the xp_stopmail operation.
RESOLUTIONTo 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:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
WORKAROUND
To work around this behavior, make sure that no other SQL Mail activities are in progress when xp_stopmail is executed.
STATUSMicrosoft has confirmed that this is a problem in Microsoft SQL Server 2000 SP1.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
| Modification Type: | Major | Last Reviewed: | 7/1/2002 |
|---|
| Keywords: | kbbug KB307932 |
|---|
|