My installation fails, now what? (part 2)
As i said yesterday, I would post a follow up with information about tracing. Today i will show you how it's possible to enable Serverside tracing. Excessive tracing may cause performance degradation and if tracing is set to verbose, large files will be generated.
- Tracing is configured via a common Microsoft CRM registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM
- Different keys for server and clients
- Names of all registry values start with “Trace”
- New settings can be loaded dynamically
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft nor I cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
These keys will help enable server tracing:
| TraceCallStack | DWORD | 1 – Enabled, 0 – Disabled |
| TraceCategories | String | List of trace categories and corresponding levels 1. Off (No Trace - Default) 2. Error (Only error conditions are logged) 3. Warning (Errors and warnings both are logged) 4. Info (Errors, Warnings and Informational messages all are logged) 5. Verbose (Errors, Warnings, Informational and Verbose (step-by-step) messages all are logged) |
| TraceDirectory | String | Local folder where trace files will be created, for example: *:Verbose;SchedulingEngine:Warning |
| TraceEnabled | DWORD | 1 – Enabled, 0 – Disabled |
| TraceRefresh | DWORD | Setting to a different value causes trace to reload new settings |
| TraceSchedule | String | Hourly / Daily / Weekly / Monthly |
Please note that tracing will impact performance and should be turned off when not needed. To turn tracing off Set the TraceEnabled key to 0.
Tommorow I will post the settings on how to enable clientside tracing.