crminthefield: PFE CRM Trace Log File Reader

[Blog bot]

Источник: http://blogs.msdn.com/b/crminthefiel...le-reader.aspx
==============

There are going to be times that an issue with a Microsoft Dynamics CRM server will arise and the application log will not provide enough information to help resolve the issue. Or you might be asked by the Microsoft CRM support team for a trace log of the server to help troubleshoot an issue. Depending on the level of tracing, the CRM Tracing can provide very detailed information on what CRM is doing. If you’re interested in enabling tracing, read the article written by a teammate discussing how to enable the CRM Platform Tracing with the Registry or Windows PowerShell, http://blogs.msdn.com/b/crminthefiel...owershell.aspx.

Dynamics CRM Tracing produces a text log file that can contain information of the operation that the Microsoft CRM server performed. The trace file is difficult to read because there might be log entries between steps of the operation that you are interested in. The PFE CRM Trace Log File Reader Tool is supposed to help with reading the log file so you can get an insight on what the CRM server is doing.

You can download the log reader at https://pfecrmtracetool.codeplex.com/.

Open the trace log file from the file menu, once the tool opens the log you will see the individual log entries in a grid. If there are errors, the row will be marked with red. Warnings will have their rows marked with yellow.



Right clicking on a cell is a quick way to search the rest of the log files loaded, for the content in the in the cell. Here I am searching on the ReqID across the log.



The search yields 5 records that are a part of the 13cbc1d9-2e16-4d16-8302-c6b2c8ee64d9 request. In the search area, a count of the number of records that are in the grid and the amount of time those 5 steps took.

You can also search on individual columns. It is best to use contains when searching the Call Stack and Message columns.



The search yields 5 records that are a part of the 13cbc1d9-2e16-4d16-8302-c6b2c8ee64d9 request. In the search area, a count of the number of records that are in the grid and the amount of time those 5 steps took.

You can also search on individual columns. It is best to use contains when searching the Call Stack and Message columns.



In the details area, there are tabs that display the Message and Call stack information. Sometimes there will be message that contains escaped URL’s making them difficult to read, in this case you can check the “Remove HTTP Code” checkbox and it will remove HTTP codes with the corresponding symbols.





Please let me know if there are features that would help in reading CRM trace files.

Thanks,
Walter







Источник: http://blogs.msdn.com/b/crminthefiel...le-reader.aspx