This article was previously published under Q178393
This article has been archived. It is offered "as is" and will no longer be updated.
On a computer running Windows NT Server 4.0 with Service Pack 3 (SP3) andMicrosoft SQL Server 6.5 installed, when you send a message usingxp_sendmail, SQLMail and the SQL Server service may stop responding (hang).You cannot stop the SQL Server service using SQL Enterprise Manager, SQLService Manager, or the NET STOP MSSQLSERVER command.
This problem, originating in the Windows NT SP3 build of Mapi32.dll, isknown to occur when your Windows Messaging mail profile is configured toconnect to the Internet (for example, a POP3 mail server) and the SQLServer "priority boost" configuration parameter is set to 1. This may notoccur with the first message sent, but may occur on subsequent attempts tosend a message.
To workaround this problem, set the SQL Server "priority boost"configuration parameter to 0.
If, for other reasons, you require this configuration parameter to be setto 1, obtain the latest service pack for Windows NT version 4.0.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
NOTE: Returning to the previous build of Mapi32.dll (which is the basebuild of this file, installed with Windows NT 4.0) is not recommended,because fixes were made to this file for Windows NT SP3 to correct otherSQLMail problems. Please see the following Microsoft Knowledge Base articlefor more information:
159425 PRB: Messages Blocked with SQLMail and Exchange Client
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.