Exchange Mail Flow Troubleshooter – EXTRA

In this blog we will be learning how to start mail flow troubleshooting in Exchange Server 2010 with the help of EXTRA. It is difficult to understand the cause of the issue. EXTRA will help you diagnose the issue.

Before You Begin

It is mandatory that you should have thorough understanding on ports, smtp, firewall and other components involved in transport.

====================================================

Lets Explore EXTRA

To open EXTRA from an Exchange Server 2010 server go to Start > Run > and type EXTRA

image

Figure 1.1 : EXTRA

image

Figure 1.2 : Welcome to EXTRA

image

Figure 1.3 : Task Selection Screen

image

Figure 1.4 : Symptoms

In figure 1.4 we have basic symptoms to select. Based on our selection the tool will help us to move further. It is always important to understand the symptoms else your troubleshooting might fail.

I have selected the last option for pending submission.

image

Figure 1.5 : Server and User Information

In figure 1.5 it is asking Please provide the name of a computer with the Mailbox server role installed where submitted messages are not being processed.

image

Figure 1.6 : Retrieving Information about Exchange Server

image

Figure 1.7 : Basic Server Information

In figure 1.7 it clearly says that the one or more required services are not started. Now lets move ahead and see what is the service name which is not started.

image

Figure 1.8 : Basic Server Information

Select the error message and you will see detailed description of which service is failed.

image

Figure 1.9 : Mailbox Server role Health Results

image

Figure 1.10 : Hub Transport Server Role Heath Results

Although we came to know which service is causing the issue, however it is a best practices to check the health of Mailbox and Transport server.

image

Figure 1.11 : Results

image

Figure 1.12 : Microsoft Exchange Transport service in stopped state

Go ahead and start the service. This service is dependent on AD Topology service. If you are unable to start the service then you can easily find the cause using Application Event Logs.

====================================================

Happy Learning

Sunder

MSEXCHANGETEAM | Ideas That Click

Tagged , . Bookmark the permalink.

Comments are closed.