Clicking Apply button to run a report with many input controls fails to run on server using IIS as a reverse proxy

Issue:

A report failed to run on TIBCO JasperReports® Server that has IIS installed and used as a reverse proxy server.

The report contains many input controls and after clicking on the Apply button, it appears to do nothing and no report is displayed on the right pane.

After enabling DEBUG for certain loggers in the Log Settings page:

- SQL query executer

- Input control value queries

the jasperserver.log only logs the input control queries and its parameter values but there was no indication that it has ran the actual report.

This exact same report worked fine when it was tested on a different server running the exact same TIBCO JasperReports® Server version and build. 

Solution:

After enabling the browser's dev console (F12), the http request that was recorded when the Apply button is clicked returns a "400 - Bad Request" error:

POST Request URL: https://<server>/jasperserver-pro/rest_v2/reports/organizations/organization_1/OTE_Reports_Test/Booked_Amortization_Report_Levelwise/inputControls/LevelNameBAR;
Amort_From_Month;Amort_To_Month;Exe_From_Month;Exe_To_Month;Deal;DealFlag;DealType;AssetFlag;Touchpoint;ContractStatus;ContractCurrency/values

The  response captured from the downloaded HAR file reveals that the server is running "server Microsoft-IIS/10.0" and the "Response Content" tab displays the following error:

"The length of the URL for this request exceeds the configured maxUrlLength value."

The error indicates that a limitation has been reached on the IIS preventing the http request to succeed. The solution is to increase the default value for the maxUrlLength on the IIS server.

An example article on how to do that is provided in the "Related Articles" section below.

Related Articles:

https://jaredmeredith.com/2017/03/12/solved-the-length-of-the-url-for-this-request-exceeds-the-configured-maxurllength-value/