Troubleshooting reporting implementation into ASP.NET Core application
|Progress® Telerik® Reporting
|.NET Core 2.1+
If you are experiencing problems while working with Telerik Reporting, the right way to determine what have caused them 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 error. To create the log file, go to the project that hosts the Rest Service and add the below settings in the
Program.csfile in the
public static void Main(string args)
static void EnableTracing()
System.Diagnostics.Trace.AutoFlush = true;
Upon running the project and reproducing the error, it will be generated an aspnetcoredemo.log file at the root of the application.
- Other recommended troubleshooting approach is to use Fiddler Jam or other proxy tool to check the requests, their responses and statuses. Please, create Fiddler trace (see How to Record a Log with the Fiddler Jam Extension).
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.