Welcome to TechNet Blogs Sign in | Join | Help

Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

This release of ExPTA includes the following:

 

1.    Perfmon data collection:  Collect performance data to log file or analyze previously collected logs.  ExPTA can collect for durations between 5 minutes to 8 hours. Collection works remotely. Data is analyzed in 20 minute time ranges, and results are grouped by the time in which the problem occurred.  You can analyze logs previously collected by ExPTA or via perfmon.  ExPTA will expect that the performance counters listed below are included in any log that is analyzed.

 

2.    Queue thresholds: SMTP Server\Categorizer Queue Length, Epoxy(IMAP)\Queue length, EPOXY(POP3)\Queue length, LDAP times, MSExchangeIS Public\Replication Receive Queue Size, SMTP Server\Remote Queue Length, SMTP Server\Remote Retry Queue Length, SMTP Server\Local Queue Length, Virus scan queue length

 

3.    Network thresholds:  Network Interface\Packet Outbound errors, Network Interface\Output Queue Length, Network Interface\Bytes Total/sec

 

4.    LDAP latency checks:  MSExchangeDSAccess Domain Controllers\LDAP Search Time and MSExchangeDSAccess Domain Controllers\LDAP Read Time thresholds were added to detect problems due to bottlenecks on the AD server.

 

5.    RPC requests: Max RPC requests, average RPC request thresholds are now dependent on the number of users per server

 

6.    Memory changes: Validate that the Database Cache Size Peak < 1.2 GB.  In addition, most of the memory rules have been changed to work off the maximum rather than the average values.

 

7.    Improved reporting: Reporting of results between steps and the summary are now displayed in a consistent fashion, using tabbed pages for the different reports.

 

Pick up the latest version from here.

 

Performance counters analyzed by this version of ExPTA:

 

\Database(Information Store)\Database Cache Size

\Database(Information Store)\Database Page Fault Stalls/sec

\Database(Information Store)\Log Record Stalls/sec

\Database(Information Store)\Log Threads Waiting

\LogicalDisk(*)\Avg. Disk Queue Length

\LogicalDisk(*)\Avg. Disk sec/Read

\LogicalDisk(*)\Avg. Disk sec/Write

\LogicalDisk(*)\Disk Reads/sec

\LogicalDisk(*)\Disk Writes/sec

\Memory()\Available Mbytes

\Memory()\Free System Page Table Entries

\Memory()\Pages/sec

\Memory()\Pool Nonpaged Bytes

\Memory()\Pool Paged Bytes

\MSExchangeIS Mailbox(_Total)\Active Client Logons

\MSExchangeIS Public(_Total)\Active Client Logons

\MSExchangeIS()\Active User Count

\MSExchangeIS()\Exchmem: Number of Additional Heaps

\MSExchangeIS()\Exchmem: Number of heaps with memory errors

\MSExchangeIS()\Exchmem: Number of memory errors

\MSExchangeIS()\RPC Averaged Latency

\MSExchangeIS()\RPC Operations/sec

\MSExchangeIS()\RPC Requests

\MSExchangeIS()\VM Largest Block Size

\MSExchangeIS()\VM Total 16MB Free Blocks

\MSExchangeIS()\VM Total Free Blocks

\MSExchangeIS()\VM Total Large Free Block Bytes

\Paging File(_Total)\% Usage

\Process(*)\% Processor Time

\Process(emsmta)\Private Bytes

\Process(inetinfo)\Private Bytes

\Process(lsass)\Private Bytes

\Process(mad)\Private Bytes

\Process(store)\Private Bytes

\Process(System)\Private Bytes

\Processor(_Total)\% Processor Time

\System()\Context Switches/sec

\System()\Processor Queue Length

\Epoxy(IMAP)\Client Out Queue Length

\Epoxy(IMAP)\Store Out Queue Length

\Epoxy(POP3)\Client Out Queue Length

\Epoxy(POP3)\Store Out Queue Length

\MSExchangeIS Public(_Total)\Replication Receive Queue Size

\SMTP Server(_Total)\Categorizer Queue Length

\SMTP Server(_Total)\Remote Queue Length

\SMTP Server(_Total)\Remote Retry Queue Length

\SMTP Server(_Total)\Local Queue Length

\MSExchangeIS()\Virus Scan Queue Length

\MSExchangeDSAccess Domain Controllers(*)\LDAP Search Time

\MSExchangeDSAccess Domain Controllers(*)\LDAP Read Time

\Network Interface(*)\Output Queue Length

\Network Interface(*)\Current Bandwidth

\Network Interface(*)\Packets Outbound Errors

\Network Interface(*)\Bytes Total/sec

\MSExchangeDSAccess Domain Controllers(*)\LDAP Read calls/Sec

\MSExchangeDSAccess Domain Controllers(*)\LDAP Search calls/Sec

\MSExchangeDSAccess Caches(*)\Cache Hits/Sec

\MSExchangeDSAccess Caches(*)\LDAP Searches/Sec

\MSExchangeIS()\Virus Scan Files Scanned/Sec

\MSExchangeIS()\Virus Scan Files Quarantined/Sec

\MSExchangeIS()\Virus Scan Messages Processed/sec

 

Hope you like it! Let us know if you have feedback on the tool!

 

- Nicole Allen

Published Thursday, April 06, 2006 10:18 AM by Exchange

Comments

Thursday, April 06, 2006 5:23 PM by Martin Pavlis - pavlis.net

# Exchange Server: Performance Troubleshooting Analyzer (ExPTA) v1.1

Friday, April 07, 2006 12:32 PM by subject: exchange

# Weekend reading

&quot;The&quot; weekly list, this time on schedule.

Microsoft Exchange Server Profile Analyzer Web Release 2.5...

# Henrik Walther Blog &raquo; Blog Archive &raquo; Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

Tuesday, April 11, 2006 1:44 PM by Yonkey

# re: Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

I've downloaded it but what i got is 1.0 version. Can you please re-check the download link??
Wednesday, April 12, 2006 1:30 PM by Nicole Allen

# re: Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

Chance are good that either

  a. ExPTA.MSI from v1.0 is stuck in your browser temporary cache.  In this case, if you are using IE, the workaround is to clear the IE cache.  From IE, go to  Tools -> Internet Options -> General -> Delete Files.

   b. You are going through a caching proxy server and it hasn't picked up the file change from microsoft.com.  If this is the problem, you can either wait and try again, or manually change or bypass your proxy server.  
Friday, April 14, 2006 5:06 PM by Yonkey

# re: Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

What would be reason mad.exe eat the CPU to high? possible reason when store.exe consume CPU as well?
Wednesday, April 19, 2006 10:59 AM by Welcome to Flaphead.com @ Home

# Microsoft Exchange Server Performance Troubleshooting Analyzer Tool v1.1

I really, really recommend that you look at this.&amp;nbsp; Like ExBPA it is tool that helps you help yourself.&amp;nbsp;...
Wednesday, April 19, 2006 11:35 AM by Nicole Allen

# re: Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

There are many things that mad.exe does, such as maintanance on the databases, generating the OAB, and tasks for DSProxy, RUS, free busy generation for CDO etc.  Many of the actions done by MAD can also drive up the store.exe CPU.
Thursday, April 20, 2006 3:49 AM by Ed

# re: Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

Hi,

We've been successfully running ExPTA 1.0 and have downloaded ExPTA 1.1.  However, we can't analyse any of the results that are generated.  We see the following 2 errors:

"Failed to retrieve RPC performance counter data from the file <filename>.blg.  An unspecified error occurred while reading the file."
"Error accessing RPC performance counters. String was not recognised as a valid DateTime.."

Any ideas?

Thanks,
Ed.
Wednesday, April 26, 2006 7:20 AM by DaveB

# re: Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

I want to use ExPTA to analyse customer log files off site. The customer has used ExPTA to run an analysis and has sent me the perfmon log files. I'd like to be able to run up ExPTA and select the option to analyse a previous log file. BUT - to get there I have to go through the connectivity test, which fails, 'cos I can't see their server! If I enter one of my servers which I can see, it lets me through but then when I tell it to analyse the log file it says the server names don't match. Is there anyway I can get round this?
Sunday, April 30, 2006 11:44 AM by Is this thing on?

# Lots of Cool Happenings Since January

Well, although I started this blog with the best intentions, I have been very bad at keeping it regular.&amp;nbsp;...
Monday, May 01, 2006 5:33 AM by Garry

# May 2006 - Technical Rollup





Security
&amp;nbsp;





News
&amp;nbsp;
Are Smart Cards the New Way of Life? - Solving the...
Monday, May 01, 2006 5:34 AM by Garry

# May 2006 - Technical Rollup






Security
&amp;nbsp;





News
&amp;nbsp;
Are Smart Cards the New Way of Life? - Solving the...
Monday, May 08, 2006 3:32 PM by Nicole Allen

# re: Exchange Performance Troubleshooting Analyzer (ExPTA) 1.1 has shipped

Responding to DaveB's question above: ExPTA must have network connectivity to the Exchange server and a domain server in order to process the data, as ExPTA gathers other information  from the system (such as the location of data files, and the number of processors) to measure the server health.
-Nicole
New Comments to this post are disabled
 
Page view tracker