Microsoft Exchange Troubleshooting Assistant v1.0 now available!

What Jon Avner announced in this blog post is now a reality - today we have released the version 1.0 of Microsoft Exchange Troubleshooting Assistant. You can download it from here:

The download page says:

The Exchange Troubleshooting Assistant programmatically collects configuration data, performance counters and live tracing information from an Exchange server. The tool analyzes each subsystem to determine individual bottlenecks and component failures, then aggregates the information to provide root cause analysis.

Let us know what you think!! Post comments to this blog post or if you need assistance, please go to the newsgroup!

- Nino Bilic

Comments (18)
  1. BD says:

    The link doesn’t work. Has it been released yet.

  2. Exchange says:


    Give it a little if it does not work, sorry about that. I am guessing replication is still taking place. I just tried it and I can access it.

  3. nawaral says:

    this works for exchange 2000 and exchange 2003 ?

  4. Stimpy says:

    I can’t get it to collect ExMon data from the server, although I can run ExMon locally on the server without any problems. What am I missing?

  5. Jon Avner says:

    This will work for both E2K and E2K3, although there might be some tests and features not available for E2K.

  6. jgiambr says:

    Nice tool, very handy….long overdue. Perhaps include a way to run a scan without having to input any symptoms. Sometimes I just want to know that everything is running ok. Sometimes there will be a problem but no one brings it up until it has gone on for a couple of weeks. Good job though!

  7. Jon Avner says:

    It sounds like you’re describing ExBPA, which does do a general scan of your system and looks for any issues and reports everything it finds (mostly config related, but it does other checks as well).  It does over 2500 checks right now, and growing.

    The difference between the tools is that ExBPA is meant to be run regularly to verify system health and ExTRA is meant to be run specifically to deal with a current issue being experienced.  

  8. Jeff25 says:

    Can you explain how this is different from the ExPTA?

  9. Charlie C says:

    Together, this makes-up the Microsoft Exchange Server Analyzer Tools suite.

  10. Charlie C says:

    From what I’ve read, the Troubleshooting Assistant seems to combine the Microsoft Exchange Server Performance Troubleshooting Analyzer Tool and the Microsoft Exchange Server Disaster Recovery Analyzer Tool, which make-up the Microsoft Exchange Server Analyzer Tools suite <;:

    * The Microsoft Exchange Server Best Practices Analyzer Tool scans servers running Exchange Server and identifies items that do not conform to Microsoft best practices.

    * The Microsoft Exchange Server Performance Troubleshooting Analyzer Tool examines the performance of an Exchange Server messaging system, and identifies possible causes of performance problems.

    * The Microsoft Exchange Server Disaster Recovery Analyzer Tool examines an Exchange Server deployment when an Exchange Server database fails to mount, and identifies possible causes of the problem.

  11. Haruya Shida says:

    Actually, Exchange Troubleshooting Assistant (ExTRA) contains the new “Mail Flow Troubleshooter” (we have been calling it ExMFA internally) as well. In short, ExTRA = ExPTA + ExDRA + ExMFA.

    I will blog about the mail flow troubleshooter to describe its functionality in details separately.

  12. tt says:

    Hey guys, please try setting the DPI to 120 and run through the layout in this program.  It’s a mess, with labels covering entry controls.

  13. tt says:

    Just ran the tool and it says that my FCL shows some slow calls to LSASS.  Then there is a link for "Tell me more about this issue and how to resolve it".  Clicking on it takes to me the homepage of the Exchange Server TechCenter.

    In fact, clicking on any "tell me more about how to solve it" links takes me there.  I really was expecting a page with some hints as to how to solve the issues presented.

  14. ninob says:


    Thanks for reporting those two issues, I have sent them to people that can do something about them. :)

  15. Jon Avner says:

    Yes, thanks tt. We will investigate.

  16. Nicole says:

    Regarding the problem gathering exmon data:  Please post your request (and a description of the issue) to the newgroup and I will assist you there.

    Regarding the slow calls to lsass link:  I’ve check the link and it seems to be valid (you should have been directed to  If you are still seeing this problem. please post to our newsgroup for further instructions.



  17. martin says:

    could not see why it could not be made an offence t mas deliver spam or junk mail. I have 2970 unopened in Bulk mail

    attheat the minute and would still get it whate

    ver I did !

  18. Vanman says:

    I am getting this error: "The connection to the Microsoft Exchange Server is unavailable.  Outlook must be online or connected to complete this action".

    When have configured Outlook with my companies Exchange Server, and it prompts me to a sign in page, but I am a loss on why the error says "outlook must be online"?  

    Any ideas?

Comments are closed.

Skip to main content