Topic Last Modified: 2009-03-16
The Microsoft® Exchange Server Analyzer Tool queries the Microsoft Internet Information Server (IIS) metabase to enumerate the list of Simple Mail Transport Protocol (SMTP) transport event sink bindings. The Exchange Server Analyzer tries to locate several standard event bindings, based on the following list that is pre populated in the Exchange Server Analyzer:
- Custom Exchange DSN Sink
- EHLO Inbound Command Handler Sink for XLSA
- EHLO Response Handler Sink for X-LSA
- EOD Inbound Command Handler Sink
- Exchange Categorizer
- Exchange LoadBalancer
- Exchange NTFS Store Driver
- Exchange Router
- Exchange SMTP Protocol Logging Sink
- Exchange SMTP Protocol Security EHLO Sink
- Exchange SMTP Protocol Security EXPS Sink
- Exchange SMTP Protocol Security EXPS-Aux Sink
- Exchange SMTP Protocol Security EXPS-EOD Sink
- Exchange SMTP Protocol Security Mail Sink
- Exchange SMTP Protocol XEXCH50 Before Data Sink
- Exchange SMTP Protocol XEXCH50 EHLO Response Sink
- Exchange SMTP Protocol XEXCH50 EOD Sink
- Exchange SMTP Protocol XEXCH50 Inbound EHLO Sink
- Exchange SMTP Protocol XEXCH50 Inbound MAIL Sink
- Exchange SMTP Protocol XEXCH50 Inbound RCPT Sink
- Exchange SMTP Protocol XEXCH50 Inbound XEXCH50 Sink
- Exchange SMTP Protocol XEXCH50 per recipient event Sink
- Exchange SMTP Protocol XEXCH50 RCPT Response Sink
- Exchange SMTP Protocol XEXCH50 Response Sink
- Exchange Store Driver
- Exchange Transport AntiVirus API
- Exchange Transport XEXCH50 Submission Sink
- MAIL Inbound Command Handler Sink for TURF
- Mobile Categorizer
- MSExchange Content Filter EOD Sink
- MsgTrackLog Sink
- RCPT Inbound Command Handler Sink
- SMTP Eventlog Sink
- UmConvSink
- X-LSA Inbound Command Handler Sink
- X-LSA Response Handler Sink
- X-LSA Sink
If the Exchange Server Analyzer finds that one or more standard event bindings are missing, the Exchange Server Analyzer generates a warning.
An SMTP transport event occurs when message data is transported into or out of the SMTP service. All messages go through events. These include X.400 and RPC incoming or outgoing messages. One common example of an inbound transport event is the arrival of a message to the SMTP service either over the network or in the SMTP pickup directory. When this transport event occurs, a source for this event notifies the transport event sinks, each of which can take some type of action based on the data content of the message. The system performs no other action with the message data after it passes the message data to the sink until the sink completes its action and returns the message. The sink has exclusive control of the message data and state while it performs this action.
Missing transport event sink bindings can cause mail flow problems. If the Exchange Server shows symptoms of mail flow problems such as message queuing, reregister the transport event sinks.
To reregister the transport event sinks-
From the Microsoft Exchange Server, open a Command Prompt window and change to the \Program Files\Exchsrvr\Bin folder.
-
Type the following commands to reregister transport event sinks:
regsvr32 exps.dll
regsvr32 miscat.dll
regsvr32 onsubmit.dll
regsvr32 peexch50.dll
regsvr32 phatcat.dll
regsvr32 protolog.dll
regsvr32 reapi.dll
regsvr32 regsinks.dll
regsvr32 tranmsg.dll
regsvr32 turflist.dll
regsvr32 xlsasink.dll
regsvr32 msgfilter.dll
-
Restart the Simple Mail Transfer Protocol service.
-
Rerun the Exchange Server Analyzer to verify that the warnings are no longer present. If event sink warnings continue to occur and you experience mail flow problems, contact Microsoft Product Support Services (PSS).
For more information about transport event sink bindings see the following Exchange resources:
- Microsoft Knowledge Base article 258224, "XCON: Enumerating the
Registered Transport Event Sinks" (http://go.microsoft.com/fwlink/?linkID=3052&kbid=258224)
- "SMTP Service Design" in the Technical Reference Guide for
Exchange Server 2003 (http://go.microsoft.com/fwlink/?LinkId=58876)