Skip to content

Commit 2633e79

Browse files
authored
Update troubleshoot-report-server-net.md (#202)
1 parent e1e2544 commit 2633e79

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

knowledge-base/troubleshoot-report-server-net.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,6 @@ By enabling logging, the internal exceptions that are not shown on the browser p
5050
5151
5252
1. Use the [Event Viewer](https://learn.microsoft.com/en-us/shows/inside/event-viewer) to inspect `Application Event Logs` of the Telerik Report Server for .NET application - [Application Event Log (IIS)](https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-8.0#application-event-log-iis). The events can be saved into `evtx` files by right-clicking on the events in the Event Viewer -> `Save Selected Events...`.
53-
1 [Run the app at a command prompt](https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-8.0#run-the-app-at-a-command-prompt) to catch start-up errors that may not be part of the Application Event log by executing `dotnet Telerik.ReportServer.Web.Core.dll` in the root directory of the Telerik Report Server for .NET - `C:\Program Files (x86)\Progress\Telerik Report Server\Telerik.ReportServer.Web.NET`.
53+
1. [Run the app at a command prompt](https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-8.0#run-the-app-at-a-command-prompt) to catch start-up errors that may not be part of the Application Event log by executing `dotnet Telerik.ReportServer.Web.Core.dll` in the root directory of the Telerik Report Server for .NET - `C:\Program Files (x86)\Progress\Telerik Report Server\Telerik.ReportServer.Web.NET`.
5454
5555
>note If the problem persists, you may open a support ticket and send us in an archive (ZIP/RAR file) the [SAZ file](https://docs.telerik.com/fiddler/Save-And-Load-Traffic/Tasks/CreateSAZ) recorded by `Fiddler`, as well as the `.log` and `.evtx` files. Including the steps which have to be followed in order to reproduce the issue may speed up the diagnostic process.

0 commit comments

Comments
 (0)