Chapter 5: Managing Exchange Servers

Chapter 5 - Managing Exchange Servers
Monitoring and Managing Microsoft Exchange 2000 Server
by Mike Daugherty
Digital Press 2001

5.2 Managing Exchange services

Exchange 2000 is not a single, monolithic executable image running on your server. Instead, Exchange is a collection of cooperating services. Table 5.1 lists these Exchange 2000 services and the other prerequisite services that must also be running.

Table 5.1: Exchange Services

Service	Function	Service Name /Executable	Requires these Services
Microsoft Exchange Chat	Provides IRC-based chat collaboration.	MSExchangeChat chatsrv.exe
Microsoft Exchange Conferencing	Maintains online conference schedules and controls associated technology providers.	MSExchangeCONF xconfmgr.exe
Microsoft Exchange Connectivity Controller	Provides support services for Microsoft Exchange connectors.	MSExchangeCoCo Iscntrl.exe	Event Log Microsoft Exchange System Attendant
Microsoft Exchange Connector for Lotus cc:Mail	Allows sharing of mail traffic with Lotus cc:Mail systems.	MSExchangeCCMC ccmc.exe	Event Log Microsoft Exchange Information Store
Microsoft Exchange Connector for Lotus Notes	Allows sharing of mail traffic with Lotus Notes systems.	LME-NOTES dispatch.exe	Event Log Microsoft Exchange Connectivity Controller Microsoft Exchange Information Store
Microsoft Exchange Connector for Novell GroupWise	Allows sharing of mail traffic with Novell GroupWise systems.	LME-GWISE dispatch.exe	Event Log Microsoft Exchange Connectivity Controller Microsoft Exchange Information Store Microsoft Exchange Router for Novell GroupWise
Microsoft Exchange Directory Synchronization	Synchronizes MS Mail directory with Active Directory.	MSExchangeDX dxa.exe	Microsoft Exchange MTA Stacks
Microsoft Exchange Event	Monitors folders and fires events, for Exchange 5.5- compatible server applications.	MSExchangeES events.exe	Microsoft Exchange Information Store
Microsoft Exchange IMAP4	Provides IMAP4 services.	IMAP4Svc inetinfo.exe	IIS Admin Service Microsoft Exchange Information Store
Microsoft Exchange Information Store	Manages Information Storage.	MSExchangeIS store.exe	IIS Admin Service Microsoft Exchange System Attendant
Microsoft Exchange MTA Stacks	Provides X.400 services.	MSExchangeMTA emsmta.exe	IIS Admin Service Microsoft Exchange System Attendant
Microsoft Exchange POP3	Provides POP3 services.	POP3Svc inetinfo.exe	IIS Admin Service Microsoft Exchange Information Store
Microsoft Exchange Router for Novell GroupWise	Provides support for scheduling collaboration with Novell GroupWise systems.	MSExchangeGWRtr gwrouter.exe	Event Log
Microsoft Exchange Routing Engine	Processes routing information.	RESvc inetinfo.exe	IIS Admin Service
Microsoft Exchange Site Replication Service	Emulates Exchange 5.5 directory service.	MSExchangeSRS srsmain.exe
Microsoft Exchange System Attendant	Provides system related services for Microsoft Exchange.	MSExchangeSA mad.exe	Event Log NT LM Security Support Provider Remote Procedure Call (RPC) Remote Procedure Call (RPC) Locator Server Workstation
Microsoft Exchange T.120 MCU Conferencing	Multipoint Control Unit for T.120 data conferencing clients .	MSExchangeT120 xt120mcu.exe
MS Mail Connector Interchange	Allows sharing of mail traffic with MS Mail systems.	MSExchangeMSMI mt.exe	Event Log Microsoft Exchange MTA Stacks
MS Schedule Plus Free-Busy Connector	Allows sharing of Schedule+ Free/Busy information.	MSExchangeFB msfbconn.exe	Event Log Microsoft Exchange Information Store

In addition to the Exchange services, several non-Exchange services are important for Exchange 2000. Some of these are listed in Table 5.2.

Table 5.2: Associated Services

Service	Function	Service Name/Executable	Requires these Services
IIS Admin Service	Allows administration of Web and FTP services through the Internet Information Services snap-in.	IISADMIN inetinfo.exe	Protected Storage Remote Procedure Call (RPC)
Microsoft Active Directory Connector	Replicates objects from the Exchange 5.5 directory into the Windows 2000 Active Directory for use by Exchange 2000.	MSADC adc.exe	Event Log NT LM Security Support Provider Remote Procedure Call (RPC) Remote Procedure Call (RPC) Locator Server Workstation
Network News Transport Protocol (NNTP)	Transports network news across the network.	NntpSvc inetinfo.exe	IIS Admin Service
Simple Mail Transport Protocol (SMTP)	Transports electronic mail across the network.	SMTPSVC inetinfo.exe	IIS Admin Service

5.2.1 Starting Exchange services

Certain Exchange services depend on other Exchange services. If these services are started out of order, the needed services will automatically be started. For example, if an attempt is made to start the Information Store before the System Attendant, the Windows 2000 service manager will automatically start the System Attendant. These prerequisite services are shown in Figure 5.4.

Figure 5.4: Exchange service dependencies

Figure 5.5: The Services dialog box

By default, most Exchange services are configured to automatically start when the server is rebooted. However, there may be times when the services will need to be started manually. You can use the following procedure to start the Exchange services.

1. From the Windows 2000 Start menu by selecting Programs   Administrative Tools   Services (Figure 5.5).

2. Right-click on the service you want to start, and select Start to start the service.

3. Right-click on any other services you want to start, and select Start to start the service.

4. Use the Windows 2000 Event Viewer to ensure that the services all started. You can start the Event Viewer by selecting Programs   Administrative Tools   Event Viewer from the Windows 2000 Start menu. Exchange 2000 events are listed in the Application Log. Table 5.3 contains a list of the event IDs that correspond to successful service startups .

Table 5.3: Service Start Event Numbers

Service	Event Source	Event ID
Microsoft Exchange Chat	MSExchangeChat	8194
Microsoft Exchange Conferencing	MSExchangeCONF	8194
Microsoft Exchange Connectivity Controller	MSExchangeCoCo	8229
Microsoft Exchange Connector for Lotus cc:Mail	MSExchangeCCMC	3
Microsoft Exchange Connector for Lotus Notes	MSExchangeNOTES	8229
Microsoft Exchange Connector for Novell GroupWise	MSExchangeGWISE	8229
Microsoft Exchange Event	MSExchangeES
Microsoft Exchange IMAP4	IMAP4Svc	1033
Microsoft Exchange Information Store	MSExchangeIS Mailbox	9523
	MSExchangeIS Public	9523
	MSExchangeIS	1001
Microsoft Exchange MTA Stacks	MSExchangeMTA	9298
Microsoft Exchange POP3	POP3Svc	1003
Microsoft Exchange Router for Novell GroupWise	MSExchangeGWRtr	6015
Microsoft Exchange Routing Engine	MSExchangeTransport	1005
Microsoft Exchange System Attendant	MSExchangeSA	9014
Microsoft Exchange T.120 MCU Conferencing	MSExchangeT120	8194
MS Mail Connector Interchange	MSExchangeMSMI	2318
MS Schedule Plus Free-Busy Connector	MSExchangeFB	1000

If a service fails to start, wait a few minutes and try again. A common cause of failures is that the service is dependant upon another service that has not finished starting. Waiting a few minutes allows these services to finish. Check to ensure that all the necessary services have been started. Try to start the service several times before assuming failure.

Sometimes the Exchange server is simply in a state where a reboot is required, so reboot, and try again before assuming the service has failed. If all attempts to start the service fail, it may still be possible to run the service as an application. Running the service as an application also usually has the advantage of producing more detailed error reporting. This is an acceptable short- term solution while continuing to investigate the problem. The event log will record at least one event for any service start failures. The event will provide a starting point for troubleshooting.

A common cause for many service start failures is that the Exchange service account permissions cannot be validated . If the Microsoft Exchange Information Store service will not start, it may be in a state of recovery. A normal recovery takes from 5 to 50 minutes, depending on the number of log files. Check the event viewer to verify that recovery is taking place.

If the Microsoft Exchange System Attendant will not start, check the event viewer to make sure that the network and related services are working properly. The network services must be running before the System Attendant will start.

5.2.2 Stopping Exchange services

The Exchange services should be stopped cleanly if an Exchange server needs to be restarted. This will ensure that the Exchange databases are stopped properly and that the databases are left in a consistent state.

Because most Exchange services are dependant upon the Microsoft Exchange System Attendant, it is possible to quickly stop most Exchange services simply by stopping the System Attendant. However, if you are having system problems, stopping the services one at a time may help identify the source of the problem and may improve the possibility that the server will restart successfully.

Patience is important. The Information Store service must commit all outstanding transactions to the database. If a service such as the Information Store takes an unusually long time to stop, it is often difficult to tell if there is a problem or if the service simply needs more time to complete. You can use the Windows 2000 Performance Monitor to determine if the service is still attempting to stop or if it has encountered an unexpected error. If the process time for the service is non-zero , it is possible that the service is still attempting to stop and more patience is required. It is not uncommon for this to take as long as 30 minutes. If you prematurely abort a service stop or if the service hangs , the service will be left in an unknown state.

You can use the following procedure to stop Exchange services.

1. From the Windows 2000 Start menu by selecting Programs   Administrative Tools   Services.

2. Right-click on the service you want to stop, and select Stop to stop the service.

3. Right-click on any other services you want to stop, and select Stop to stop the service.

4. Use the Windows 2000 Event Viewer to ensure that the services all stopped. You can start the Event Viewer by selecting Programs   Administrative Tools   Event Viewer from the Windows 2000 Start menu. Exchange 2000 events are listed in the Application Log. Table 5.4 contains a list of the event IDs that correspond to successful service stop events.

Table 5.4: Service Stop Event Numbers

Service	Event Source	Event ID
Microsoft Exchange Chat	MSExchangeChat	8196
Microsoft Exchange Conferencing	MSExchangeCONF	8195
Microsoft Exchange Connectivity Controller	MSExchangeCoCo	8230
Microsoft Exchange Connector for Lotus cc:Mail	MSExchangeCCMC	4
Microsoft Exchange Connector for Lotus Notes	MSExchangeNOTES	8230
Microsoft Exchange Directory Synchronization.	MSExchangeDX	126
Microsoft Exchange Event	MSExchangeES	1
Microsoft Exchange IMAP4	IMAP4Svc	1035
Microsoft Exchange Information Store	MSExchangeIS Mailbox	9539
	MSExchangeIS Public	9539
Microsoft Exchange MTA Stacks	MSExchangeMTA	9299
Microsoft Exchange POP3	POP3Svc	1035
Microsoft Exchange Router for Novell GroupWise	MSExchangeGWRtr	6016
Microsoft Exchange Routing Engine	MSExchangeTransport	1004
Microsoft Exchange System Attendant	MSExchangeSA	9072
Microsoft Exchange T.120 MCU Conferencing	MSExchangeT120	8197
MS Mail Connector Interchange	MSExchangeMSMI	2319
MS Schedule Plus Free-Busy Connector	MSExchangeFB	1001