Sonntag, 23. Oktober 2011 23:30
There is a bug in the Message Tracking Results screen of the Microsoft Exchange Troubleshooting Assistant whereby the any attempt to sort by a column containing numeric values will result in the list being sorted in alphanumeric order rather than numeric. Good examples of this can be shown by attempting to sort by "TotalBytes" or "InternalMessageId" columns.
While it is feasible to export the list to a CSV file and then sort it correctly in Excel, the correct sorting of columns within the Troubleshooting Assistant's "Message Tracking Results" GUI would be much more convenient - especially when security policies prevent the use of desktop applications like Excel on server accounts. With any luck someone from Microsoft will log this bug to be fixed in due course.
In case someone else needs to do this work-around, you can pipe the results of a message search to the export-csv macro within the Microsoft Exchange Shell. For example:
get-messagetrackinglog -Start "09/20/2011 8:30:00 AM" -End "10/20/2011 11:59:00 PM" | export-csv c:\temp\emailtrace.csv
Note however, that there is another bug here. Dates specified in the command string as shown by the GUI Message Tracking tool cannot be used in the Microsoft Exchange Shell without swapping the day and month fields if your locale doesn't use US-style date format. You will also need to add an extra leading space to single digit hour values.
- Bearbeitet ThirdHarmonic Montag, 24. Oktober 2011 00:28 Correction regarding locale date issue
Dienstag, 1. Mai 2012 09:41Thank you for sharing this.
Let me share the same with MS-Exchange Product Team, and let's see what they say.
I will update you once I will hear from them.
Zahir Hussain Shah | MVP - Exchange Server | Senior Infrastructure Consultant - Messaging | My blog: http://zahirshahblog.com ]If my answer fixes your problem, mark them as answer, so it will help others to find a solution]