Microsoft KB Archive/257217

= Simple Mail Transfer Protocol Service Stops Unexpectedly or Does Not Relay Correctly =

Article ID: 257217

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q257217





SYMPTOMS
You may experience one or more of the following symptoms:   The Simple Mail Transfer Protocol (SMTP) service may stop unexpectedly with a call stack similar to one of the following:      SMTPSVC!?UnMarkHandledRcpts@SMTP_CONNOUT@@QAEHXZ+0x4c SMTPSVC!?ConnectToNextIpAddress@SMTP_CONNOUT@@QAEHXZ+0x1ba SMTPSVC!?ProcessClient@SMTP_CONNOUT@@UAEHKKPAU_OVERLAPPED@@@Z+0x1ee      ChildEBP RetAddr 0483fcbc 77e84bab ntdll!ZwDelayExecution+0xb 0483fcdc 77e84b7f KERNEL32!SleepEx+0x32 0483fce8 6e5a50af KERNEL32!Sleep+0xb 0483fd28 6e5a5161 IisRTL!CReaderWriterLock3___LockSpin+0x87 0483fd48 6e5a3ad4 IisRTL!CReaderWriterLock3___WriteLockSpin+0x40 0483fd50 6e5a3fec IisRTL!CLKRLinearHashTable__WriteLock+0x1b 0483fd5c 6e5a23c6 IisRTL!CLKRHashTable__WriteLock+0x16 0483fd68 6ba096a7 IisRTL!CLKRHashTable__Clear+0x9 0483fd6c 6ba096b4 mailmsg!CRecipientsHash__ReleaseDomainList+0xc 0483fd7c 6ba0966b mailmsg!CRecipientsHash__Release+0xa 0483fd88 6ba08c95 mailmsg!CRecipientsHash__~CRecipientsHash+0x9 0483fd90 6ba08d44 mailmsg!CMailMsgRecipientsAdd__~CMailMsgRecipientsAdd+0x23 0483fd9c 030e4ea0 mailmsg!CMailMsgRecipientsAdd__Release+0x21 0483fdac 030e0bde phatq!CICategorizerMailMsgsIMP__FinalRelease+0x40 0483fdb8 030e57dd phatq!CICategorizerListResolveIMP__Release+0x1e 0483fdc0 030e4d8c phatq!CICategorizerMailMsgsIMP__Release+0xd 0483fdd0 030e4598 phatq!CICategorizerPropertiesIMP__UnSetPropId+0x3c 0483fde4 030e95c1 phatq!CICategorizerPropertiesIMP__~CICategorizerPropertiesIMP+0x28 0483fdfc 030e756f phatq!CCatAddr__~CCatAddr+0x51 0483fe1c 030e74a8 phatq!CCatRecip__~CCatRecip+0x9f      ChildEBP RetAddr  Args to Child 3356f2b4 673918e4 f106b014 3356f300 00000000 KERNEL32!InterlockedCompareExchange+0xc 3356f2d4 67391338 02d30650 3356f308 6c9538fc STAXMEM!MpHeapFree+0x44 3356f2e0 6c9538fc 3356f308 6c95a753 3356f308 STAXMEM!ExchMHeapFree+0x16 3356f2e8 6c95a753 3356f308 6c958e35 3356f308 mailmsg!operator delete+0x12 3356f2f0 6c958e35 3356f308 00000000 23aac070 mailmsg!CMemoryAccess__FreeBlock+0x9 3356fb60 6c958ef5 00000001 3356fb30 3356fb08 mailmsg!CMailMsgRecipientsAdd__AddPrimaryOrSecondary+0x1e2 3356fb84 030e2ab8 7daedc60 00000000 00000000 mailmsg!CMailMsgRecipientsAdd__AddPrimary+0x1f 3356fbbc 030f4033 00000066 3356fbdc 23aac070 phatq!CICategorizerPropertiesIMP__PutStringA+0x88 3356fbfc 030f3f25 00000066 013f8edc 23aac064 phatq!CDefaultDSNSink__`vector deleting destructor'+0x23 3356fc18 030f0da5 23aac070 030b3530 23aac064 phatq!fIsMailMsgDSN+0x75 3356fc3c 030e1dfa 7d0fb424 7d0fb460 7daedc60 phatq!CICategorizerItemAttributesIMP__QueryInterface+0x55 3356fc80 030de66e 00000000 013fbc68 23aeeff0 phatq!CICategorizerDLListResolveIMP__AllocICategorizerItem+0x6a 3356fcbc 030c82a1 013f7ca0 7d0fb424 030c8e80 phatq!CCategorizer__AsyncResolveIMsg+0x31e 3356fce8 030c3e2e 7d0fb424 030d3a7b 7d0fb424 phatq!CAQSvrInst__fPreCatQueueCompletion+0x81 3356fcf0 030d3a7b 7d0fb424 03180050 5fd713b0 phatq!fPreCatQueueCompletionWrapper+0xe 3356fd20 030c80d7 7d0fb424 00000000 00000000 phatq!CAsyncMailMsgQueue__HrQueueRequest+0x21b 3356fd90 030cb842 7d0fb424 00000001 3452d948 phatq!CAQSvrInst__SubmitMessageToCategorizer+0x2b7 3356fda8 030cb8b2 00000001 3452d97c 67857bab phatq!CAQSvrInst__PreCatEventCompletion+0x92 3356fdc4 678578c5 00000001 00000000 34584818 phatq!CAQSvrInst__SetCallbackTime+0x12 00000001 0000012b 0000009c 678578c5 00000000 SMTPSVC!CStoreDispatcher__Dispatcher+0x19e   When you attempt to send an SMTP message, the message remains in the Outbox and is never sent. In addition, you are unable to receive SMTP messages that are sent to you. On the Exchange 2000 Server computer that you are connected to, the Inetinfo service may stop unexpectedly with a call stack similar to the following:      ChildEBP RetAddr 0452e120 6739190c ntdll!RtlFreeHeap+0x1bf 0452e140 67391338 STAXMEM!MpHeapFree+0x6c 0452e14c 6c9538fc STAXMEM!ExchMHeapFree+0x16 0452e154 6c958a5c mailmsg!operator delete+0x12 0452f228 6c958e7a mailmsg!CMailMsgRecipients__CopyTo+0x354 0452faac 6c958ef5 mailmsg!CMailMsgRecipientsAdd__AddPrimaryOrSecondary+0x227 0452fad0 02cd4248 mailmsg!CMailMsgRecipientsAdd__AddPrimary+0x1f 0452fb08 02ce5823 phatq!CTopLevelInsertionRequest__HrInsertSearches+0x168

0452fb48 02ce5715 phatq!CBatchLdapConnection__DecrementPendingSearches+0x103 0452fb5c 02ce5c6d phatq!CBatchLdapConnection__HrInsertInsertionRequest+0x65 0452fb64 02ce2595 phatq!CStoreListResolveContext__HrInsertInsertionRequest+0xd 0452fb74 02cd44ef phatq!CEmailIDLdapStore__InsertInsertionRequest+0x15 0452fb88 02cd358a phatq!CTopLevelInsertionRequest__BeginItemResolves+0x4f 0452fb98 02cd34f1 phatq!CICategorizerListResolveIMP__BeginItemResolves+0x1a 0452fbcc 02ccfdce phatq!CICategorizerListResolveIMP__StartMessageCategorization+0x1b1 0452fbe4 02cce658 phatq!CCategorizer__AsyncResolveIMsg+0x22e 0452fc08 02cb8da2 phatq!CatMsg+0x158 0452fc3c 02cb47ff phatq!CAQSvrInst__fPreCatQueueCompletion+0x92 0452fc48 02cc4c32 phatq!fPreCatQueueCompletionWrapper+0xf 0452fc78 02cb8ba7 phatq!CAsyncMailMsgQueue__HrQueueRequest+0x132  If you select the Allow all computers which successfully authenticate to relay, regardless of the list above check box in the properties of the SMTP virtual server, click the Access tab, and then click Relay, some computers with valid authentication credentials may not be allowed to relay messages through the virtual server.

<div class="resolution_section">

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

260910 How to Obtain the Latest Windows 2000 Service Pack

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in Microsoft Windows 2000.

This problem was first corrected in Windows 2000 Service Pack 1.

<div class="moreinformation_section">

MORE INFORMATION
To allow any computer with valid authentication credentials to relay messages through an SMTP virtual server:
 * 1) Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
 * 2) If the Administrative Groups branch exists in the left pane, expand it, expand the appropriate administrative group's branch, expand the Servers branch, expand the appropriate server's branch, and then expand the Protocols branch. To expand a branch, double-click the branch or click the plus sign (+) to the left of the branch.

If the Administrative Groups branch does not exist, expand the Servers branch in the left pane, expand the appropriate server's branch, and then expand the Protocols branch.
 * 1) In the left pane, click the SMTP container, in the right pane, right-click the appropriate SMTP virtual server, and then click Properties.
 * 2) Click the Access tab, and then under Relay restrictions, click Relay.
 * 3) Click to select the Allow all computers which successfully authenticate to relay, regardless of the list above check box, click OK, and then click OK again.

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Keywords: kbhotfixserver kbqfe kbbug kbfix kbgraphxlinkcritical kbwin2000sp1fix KB257217

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.