SMTP Instance Paused
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2006-05-16
The Microsoft® Exchange Server Analyzer Tool queries the IIS metabase to determine the value of the ServerState property for each instance of a Simple Mail Transfer Protocol (SMTP) Virtual Server.
The ServerState property presents the current state of the server instance. The states, and the corresponding state codes, are as follows: 1 (starting), 2 (started), 3 (stopping), 4 (stopped), 5 (pausing), 6 (paused), or 7 (continuing).
If the Exchange Server Analyzer determines that the value for the ServerState property for a SMTP Virtual Server instance is equal to 6 (paused), the Exchange Server Analyzer displays an error.
SMTP is the native mail protocol for mail submission and mail transport for Exchange Server. This means that clients use SMTP to send messages and Exchange servers use SMTP to deliver messages and message data.
Virtual servers run under a server process that you can start, stop, and pause—much like other server processes. For example, if you are changing the configuration of a virtual server or performing other maintenance tasks, you may have to stop the virtual server, make the changes, and then restart it. When you stop a virtual server, it does not accept connections from users and you cannot use it to deliver or retrieve mail.
An alternative to stopping a virtual server is to pause it. When you pause a virtual server, this prevents new client connections but does not disconnect current connections. When you pause an SMTP virtual server, active clients can continue to submit messages and the virtual server can deliver existing messages that are queued for delivery. However, no new connections are accepted.
For ordinary messaging operations, Exchange Server SMTP virtual server instances should be started.
To resolve this error, follow these steps to start the SMTP virtual server instance.
To start the SMTP virtual server instance
In Exchange System Manager, right-click the virtual server instance that you want to start.
On the Action menu, click Start.
For more information about how to start, stop, or pause SMTP virtual servers, see the following Microsoft Knowledge Base articles:
"XCON: How to Configure a SMTP Virtual Server Part 1" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=266686).
"XCON: How to Configure a SMTP Virtual Server Part 2" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=268163).
"XIMS: How to Flush the SMTP Mail Queue in Exchange 2000 Server" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=251087).
"XGEN: Disabling Protocols in Exchange 2000" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=291330).