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.
Procedure
- On the Content Manager server, go to the config\ subfolder of
%TRIDION_HOME%.
- Open the Content Manager configuration file, Tridion.ContentManager.config, for editing.
- To additionally log Experience Space user input exceptions, find the
allEvents section and configure the log level to include informational messages by setting the switchValue attribute to All.
- Because this change greatly increases the amount of information being logged to the Windows Event Viewer, you may want to configure logging to log to a file instead. To do so, within the
allEvents section, remove the line <add name="Tridion Event Log" /> in the listeners subsection, and replace it with the following line:
Events are now no longer logged to the Windows Event Viewer, but instead to the file specified as the log file; by default, the log file is the file Tridion.ContentManager.log in the log\ subfolder of %TRIDION_HOME%.
- Save and close Tridion.ContentManager.config.