EDIT 9/23/2009: We have updated the download link to the Exmon tool which now also works on Exchange 2007 as well as Exchange 2010.
I am pleased to announce that this month's Exchange Web release...
Updated Jul 01, 2019
Version 2.0
Blog Post
Roland and others getting error 183:
Yes, we're aware of this issue. If Exmon crashes (or is killed) while collecting data the trace will continue. However, we do have a limit of 512 MB at which point the tracing will stop. The reason for the 183 error is that Exmon tries to start a new trace (while the old one is still tracing) and it can't because only 1 trace is allowed at a time. Waiting for the file to hit 512MB will fix the problem. Alternatively, you can use the tracelog.exe tool (in the Windows Reskit) to stop the Exmon trace by the following commmand
tracelog -stop 'Exchange Event Trace'. When you run it though, it's important to make sure the Exmon.exe process is not running.
The reason for the crash (that leaves us in this state) isn't known right now, but I have anecdotal evidence that the repro is this:
1. Start Exmon (which starts tracing)
2. Immediately goto File->Save (when there's no data displayed yet in Exmon).
The File->Save is NOT meant to specifiy the location of where the trace files go. Instead it's used to SAVE the contents of the current trace into a CSV format. To change the current tracing directory, you should run exmon from the directory you want to trace into...
For example, if you want to trace to x:blah, then you should do the following:
1. x:
2. cd blah
3. "c:program filesExchange User MonitorExmon.exe".
This will trace the files to the correct location. You could alternatively use the Perfmon collection method or the tracelog.exe method as specified in the help file.
Chris Mitchell
Software Design Engineer
Exchange Performance Engineering Team
This posting is provided "AS IS" with no warranties, and no rights confered.
Yes, we're aware of this issue. If Exmon crashes (or is killed) while collecting data the trace will continue. However, we do have a limit of 512 MB at which point the tracing will stop. The reason for the 183 error is that Exmon tries to start a new trace (while the old one is still tracing) and it can't because only 1 trace is allowed at a time. Waiting for the file to hit 512MB will fix the problem. Alternatively, you can use the tracelog.exe tool (in the Windows Reskit) to stop the Exmon trace by the following commmand
tracelog -stop 'Exchange Event Trace'. When you run it though, it's important to make sure the Exmon.exe process is not running.
The reason for the crash (that leaves us in this state) isn't known right now, but I have anecdotal evidence that the repro is this:
1. Start Exmon (which starts tracing)
2. Immediately goto File->Save (when there's no data displayed yet in Exmon).
The File->Save is NOT meant to specifiy the location of where the trace files go. Instead it's used to SAVE the contents of the current trace into a CSV format. To change the current tracing directory, you should run exmon from the directory you want to trace into...
For example, if you want to trace to x:blah, then you should do the following:
1. x:
2. cd blah
3. "c:program filesExchange User MonitorExmon.exe".
This will trace the files to the correct location. You could alternatively use the Perfmon collection method or the tracelog.exe method as specified in the help file.
Chris Mitchell
Software Design Engineer
Exchange Performance Engineering Team
This posting is provided "AS IS" with no warranties, and no rights confered.