Summary

This article describes how to produce detailed debug logging to help with troubleshooting Report Commander issues.

More Information

Debug-level logging provides additional details when Report Commander processes a report. This information can be used to troubleshoot problems or unexpected behavior.

See article K00000452 for general information about configuring logging for Report Commander.

Debug logging from within the Command Line Builder or Project Editor

When you execute a report or project from within the Command Line Builder or the Project Editor, Report Commander shows the Run Project window. Within this window, click the Debug button to show additional details from the report execution.

The Copy to Clipboard button in the upper-right corner of the window can be used to copy all messages to the clipboard in text format, to be pasted in an e-mail message or support request. This button always copies the debug-level output, even if that level is not displayed.

Executing a report using the Command Runner (adcrutil)

When you execute a report using the Command Runnder (adcrutil), you can create debug logging by adding the "-debug" option to your Report Commander command line. The output will be written to the console and to the log file if you have specified one using the -logfile option. See article K00000452 for information on configuring a log file.

Note: when adding the "-debug" option to the command line, be sure it appears before the "-parameters" or "-namedparameters" option.

Executing a report using the Project Runner (adrcexec)

When you execute a report using the Project Runner (adrcexec), you can create debug logging by adding the "-debug" option to your Report Commander command line. The output will be written to the console and to the log file if you have specified one using the -logfile option or the Logging settings for the project.