If you use a date format other than US (mm/dd/yyyy), the message tracking cmdlet (Get-MessageTrackingLog) in Exchange 2010 fails.
Let’s walk through an example to prove this with Exchange 2010 SP2 UR3 at the backend. I have sent an email to my wife today (14th Oct) at 20:41.
A simple Get-MessageTrackingLog command with the sender and recipients parameter brings the desired output.
When the cmdlet is extended by specifying a time frame (dd/mm/yyyy), it returns the following error message.
Cannot process argument transformation on parameter ‘Start’. Cannot convert value "14/10/2012 20:38" to type "System.DateTime". Error: "String was not recognized as a valid DateTime."
If I run the same command with 14th Oct in US format (10/14/2012), Exchange displays the message trace.
In short, unless you use the mm/dd/yyyy format for date with the Get-MessageTracingLog cmdlet, you are not going much further with the trace
Is this a bug? Has anyone come across this before? Any workarounds?