Skip to content

Commit 0115e25

Browse files
Update how-to-troubleshoot-errors-in-asp-net-core-applications.md (#1820)
1 parent bc193e2 commit 0115e25

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

knowledge-base/how-to-troubleshoot-errors-in-asp-net-core-applications.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
2-
title: Troubleshooting Reporting Implementation Into ASP.NET Core Application
2+
title: Troubleshooting Reporting Implementation in ASP.NET Core Application
33
description: "Learn how to troubleshoot errors in ASP.NET Core applications when crashing."
44
type: how-to
55
page_title: How to troubleshoot errors in ASP.NET Core projects
66
slug: how-to-troubleshoot-errors-in-asp-net-core-applications
77
tags: ASP.NET Core, Configuration
8-
ticketid: 1383767
98
res_type: kb
109
---
1110

@@ -34,8 +33,8 @@ If you are experiencing problems while working with Telerik Reporting, the right
3433
## Solution
3534

3635
* Upgrade to the latest version of the product in case the reason for the crash has been fixed.
37-
* Try reproducing the crash on another machine to exclude machine-specific problems, for example, corrupted Telerik Reporting installation.
38-
* 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]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/overview%}) and add the below settings in the `Program.cs` file in the `Main` method:
36+
* Try reproducing the crash on another machine to exclude machine-specific problems, for example, a corrupted Telerik Reporting installation.
37+
* Provide a log file containing detailed information about the error. To create the log file, go to the project that hosts the [Rest Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/overview%}) and add the below settings in the `Program.cs` file in the `Main` method:
3938

4039
````CSharp
4140
public static void Main(string[] args)
@@ -46,7 +45,7 @@ public static void Main(string[] args)
4645

4746
static void EnableTracing()
4847
{
49-
System.Diagnostics.Trace.Listeners.Add(new System.Diagnostics.TextWriterTraceListener(File.CreateText("log.txt")));
48+
System.Diagnostics.Trace.Listeners.Add(new System.Diagnostics.TextWriterTraceListener(File.CreateText("aspnetcoredemo.log")));
5049
System.Diagnostics.Trace.AutoFlush = true;
5150
}
5251
````
@@ -55,4 +54,4 @@ public static void Main(string[] args)
5554
5655
* Another recommended troubleshooting approach is using [Fiddler](https://www.telerik.com/fiddler/fiddler-classic) or another proxy tool to check the requests, responses, and statuses. Please, create a SAZ file (see [Create a Session Archive Zip (SAZ) Traffic archive](https://docs.telerik.com/fiddler/save-and-load-traffic/tasks/createsaz)).
5756
58-
> 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 to reproduce the issue.
57+
> After you generate the log files from the above steps, archive them and attach them to a support ticket. Include the steps that have to be followed to reproduce the issue.

0 commit comments

Comments
 (0)