Skip to content

Latest commit

 

History

History
60 lines (47 loc) · 3.88 KB

troubleshoot-report-server-net.md

File metadata and controls

60 lines (47 loc) · 3.88 KB
title description type page_title slug res_type
Troubleshooting Report Server for .NET
Learn how to diagnose problems with the Telerik Report Server for .NET web application using logging.
troubleshooting
Debugging Report Server Manager
troubleshoot-report-server-net
kb

Environment

Product Progress® Telerik® Report Server for .NET

Description

The Report Server for .NET application can stop working for a variety of reasons such as installation failures, user permissions, IIS bindings, corrupted storage, etc.

By enabling logging, the internal exceptions that are not shown on the browser page can be seen and used to resolve the issue.

Solution

  1. Ensure that the ASP.NET Core Module (ANCM) is installed on the machine with the Telerik Report Server for .NET - Install ASP.NET Core Module (ANCM).

  2. Check for errors in the Browser Console or failing requests in the Network tab.

  3. Use Fiddler to see the exact requests from the Report Viewer of the Report Server Manager to the Report Server REST Service, and the corresponding responses - they may indicate what has failed.

  4. Enable Serilog logging - [Enabling logging in the Report Server for .NET]({%slug logging-rs-net%}), and inspect the logs.

  5. Enable ASP.NET Core Module logging in the Report Server for .NET application by editing the web.config file in the root directory of the application, e.g. C:\Program Files (x86)\Progress\Telerik Report Server\Telerik.ReportServer.Web.NET.

    

    6. 




<configuration>
<location path="." inheritInChildApplications="false">
	<system.webServer>
	<handlers>
		<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
	</handlers>
	<aspNetCore processPath="dotnet" arguments=".\Telerik.ReportServer.Web.Core.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" >
			<handlerSettings>
			<handlerSetting name="debugFile" value=".\logs\aspnetcore-debug.log" />
			<handlerSetting name="debugLevel" value="FILE,TRACE" />
			</handlerSettings>
	</aspNetCore>
	</system.webServer>
</location>
</configuration>





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...`.
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`. 

>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 that have to be followed in order to reproduce the issue may speed up the diagnostic process.

## See Also

* [Enabling logging in the Report Server for .NET]({%slug logging-rs-net%})