Progress® Telerik® Reporting R3 2017

Standalone Report Designer Problems

Standalone Report Designer Crashes

When the Standalone Report Designer crashes while working with Telerik Reporting, the way to determine what has caused the problem is described in the following steps:

  • Upgrade to the latest version of the product in case the reason for the crash has been fixed.

  • Try the reproduce the crash on another machine to exclude machine specific problems e.g., corrupted Telerik Reporting installation.

  • Provide us with a log file containing detailed information about the Standalone Report Designer crash. To create the log file, turn on tracing for the Standalone Report Designer and perform the actions which caused the crash. Below is the XML you need to add to the Telerik.ReportDesigner(.x86).exe.config file to enable tracing:

    <?xml version="1.0"?>
    <configuration>
        ...
        <system.diagnostics>
            <trace autoflush="true" indentsize="4">
              <listeners>
                <add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\temp\StandaloneDesigner.LOG" />              
                <remove name="Default" />
              </listeners>
            </trace>
        </system.diagnostics>
    </configuration>
    More details about the Standalone Report Designer's configuration file are available in the Configuration article."

    Telerik.ReportDesigner(.x86).exe.config resides in the [InstallDir]/Report Designer directory by default (it is recommended to create a backup copy before modifying it).

  • Check the event viewer logs for any log entries related to the problem.

  • Use Visual Studio Debugger to attach to the Telerik.ReportDesigner(.x86).exe running process before it crashes, in order to pinpoint where the error occurs.

After you generate the log files from the above steps, archive them and attach them to a support ticket. Include the steps which have to be followed in order to reproduce the issue.