Troubleshooting Content Manager
To troubleshoot your custom code interacting with the Content Manager server, troubleshoot TOM.NET (only for templating or event handling code) or the Core Service.
- Debugging Content Manager
Debug Content Manager using the Visual Studio Debugger, attaching to the Windows process that is causing you problems. - The Content Manager tracing tool
The Content Manager tracing tool returns detailed information about the activities of (a part of) Content Manager. - Content Manager profiler
The Content Manager profiler tool provides the ability to generate aggregated profiling reports for Content Manager with Powershell cmdlets. - Custom code deactivation
When troubleshooting a Content Manager issue, first deactivate your own code or third-party code to rule out any issue that may be caused by it. - Troubleshooting browser-based user interfaces
If the Content Manager's browser-based user interfaces do not behave as you would expect, this section can help you zoom in on the source of the problem. The problem may be on the client side in Javascript, or it may be in the user interface back-end running on the server.
Related concepts