The Microsoft Dynamics CRM 4.0 Client Diagnostics feature is new for the MSCRM 4.0 Outlook Client only. MSCRM Client Diagnostics is intended to aid in diagnosing common issues with Deployment, UI, Synchronization and Offline features. MSCRM Client Diagnostics provides two different modes of operation, End User Mode and Support Mode. The intent of this blog is to introduce the user, at a high level, to the diagnostics features.
The MSCRM Client Diagnostics feature can be executed from the ‘Start’ menu, under ‘Microsoft Dynamics CRM 4.0’, by clicking ‘Diagnostics. This will display the following dialog:
End User Mode is accessible by all CRM Outlook Client Personas. When you first start the MSCRM Client Diagnostics, you are in End User Mode, where you can either run diagnostics or enter the Support Mode. Diagnostics from the following categories are run while in the End User Mode:
When diagnostics have completed, the user has the option to save the results to an XML file by clicking the ‘Save’ button.
Support Mode may require Administrator privileges on the Client Computer to access files and registry settings. Support Mode is more about troubleshooting problems as directed by support.
The ‘Synchronization Troubleshooting’ tab contains MSCRM Outlook Client Synchronization feature enabled status. Common Synchronization issues can be negated from the problem by turning off the feature (check or uncheck the box and click the Save button) and testing the results. Feature toggles included :
See the ‘Synchronization Troubleshooting’ tab below:
The ‘Advanced Troubleshooting’ tab contains the toggle for ‘Tracing’ and functions to ‘Delete Temporary MSCRM Client Files’ and create a ‘Troubleshooting File for Support’.
See the Advanced Troubleshooting tab below:
An unfortunate feature cut due to security reasons, was the ability for partners to add their own tests to MSCRM Client Diagnostics. Based on User and Support feedback we may revisit this feature in future updates.
There are many dependencies that the MSCRM Outlook Client requires for MSCRM to operate and diagnostics of the basic requirements should be very helpful, even to the end user. Look for future blogs on this subject.
PingBack from http://msdnrss.thecoderblogs.com/2008/01/22/introducing-mscrm-client-diagnostics/
Did you see the post at blogs.msdn.com
In the previous blog, Introducing MSCRM Client Diagnostics, http://blogs.msdn.com/crm/archive/2008/01/22/introducing-mscrm-client-diagnostics.aspx
Diagnostic tool for MS Dynamics CRM 4.0
You can diagnoze server side with this tool now:
Throughout my career at Inetium, I have had a love/hate relationship with the Microsoft Dynamics CRM
Microsoft Dynamics CRM 4.0 diagnostisering
Can you tell me where the Trace file is kept. I see no indication as to its location.
Why is is so difficult to find the trace files once created? Why isn't there a nice button that opens the location or maybe a prompt for me to save them somewhere?
Anyone find the trace location or if you can do this manually through the registry (e.g. so you can do it as a client push)? I found this, but it seems to be only for the server - support.microsoft.com/.../907490. Thanks
Diagnostic is helpful tool
the trace file can be found at <CurrentUser>\Local Settings\Application Data\Microsoft\MSCRM\Traces
Having run this tool it identifies that the Network & Connectivity is poor, yet the network is new, running at 1GB, with GB Cisco switches, teamed NIC on the server etc. Basically there are no reported network issues and a simple PING produces a <1ms response to the CRM web server. Is there any further info as to how this tool derives its network performance calculations? As they don't make sense presently.