# Troubleshooting

This section shows a couple of techniques for fixing problems related to report generation.

## ReportWatcher service not running <a href="#reportwatcher-service-not-running" id="reportwatcher-service-not-running"></a>

A modernized application require a ReportWatcher service running to render reports. See the [previous section](http://product-docs.azurewebsites.net/PBNet/articles/reports/reportServiceConfiguration.html) on configuring this service.

If a modernized application is running **without** an active ReportWatcher service, the control that should display a report will look like the following image:

In the browser developer tools a failed request should be displayed related to this problem:

## Error during report rendering <a href="#error-during-report-rendering" id="error-during-report-rendering"></a>

The console of the ReportWatcher service displays errors that may occur during report rendering.

*TODO EXPAND THIS SECTION*

## Inspecting generated RDL <a href="#inspecting-generated-rdl" id="inspecting-generated-rdl"></a>

If there is something that is not being rendered as expected it may be useful to inspect the generated RDL document . To do this a setting can be enabled in the `Web.config` of the `ReportWatcher` service to dump report definitions to a directory:

```
    
        
    
```

This directory is going to have files with the RDL that will be used to render the report:

This report definitions could be inspected using a text editor or the [ReportBuilder tool](https://www.microsoft.com/en-us/download/details.aspx?id=53613).

## Tracking exceptions inside ReportViewerControl <a href="#tracking-exceptions-inside-reportviewercontrol" id="tracking-exceptions-inside-reportviewercontrol"></a>

It may be useful to get a hint on an internal error that occurred inside ReportViewer. To get inspect exceptions being raised while the report is being rendered, attach a debugger to the ReportWatcher service and disable the "Enable Just My Code" Visual Studio setting:


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gapvelocity.ai/webmap/powerbuilder-to-.net/reports/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.