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.
Logging more Experience Space events By default, the only things that the Experience Space back-end logs to the Windows Event Viewer are internal errors and business rule validations; it does not log user input exceptions (unlike the Classic user interfaces, which do). If you want, you configure logging so that Experience Space logs user input exceptions as well.
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.
The Content Manager tracing tool Use PowerShell commandlets to start and stop the Content Manager tracing tool, which return detailed information about the activities of (a part of) Content Manager. This tool is relevant both for Content Manager Explorer, as well as additional features you may have installed on top of it.
Debugging Content Manager Debug Content Manager using the Visual Studio Debugger, attaching to the Windows process that is causing you problems.