question

AlessioMorganti-2706 avatar image
0 Votes"
AlessioMorganti-2706 asked AlessioMorganti-2706 answered

Export from Report Viewer don't work: 404 File or directory not found

Good evening, I have a reporting services installation on a backend server and a web application with asp.net technology on the frontend server.
The web application is developed with .net framework 4.7.2 and report viewer is version 15 downloaded from nuget from Visual studio 2019.
The web application with report viewer displays the report well but the export does not work, in any format. The error on the page ".../Reserved.ReportViewerWebControl.axd?ReportSession=l4br..." is "404 - File or directory not found.".
Do you have any idea how to solve the problem?
Thanks in advance

The references are:
https://docs.microsoft.com/en-us/sql/reporting-services/application-integration/reportviewer-controls-support?view=sql-server-ver15
https://docs.microsoft.com/en-us/sql/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-get-started?view=sql-server-ver15

sql-server-reporting-services
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @AlessioMorganti-2706

I tested locally,and it works,I think you can try to open the report on your browser to see if the report can be export well.

0 Votes 0 ·

Hi, in visual studio, in debug mode, everything works correctly but, once the project has been published on the frontend server in production, from the web browser you reach the page that shows the report that is correctly shown. On the other hand, the export doesn't work! Could some component be missing on the server?
Thanks

0 Votes 0 ·
AlessioMorganti-2706 avatar image
0 Votes"
AlessioMorganti-2706 answered

Hi, thanks but in our configuration the reporting services resides on the DB server.
The error in detail was 404.15. We found that the problem was in the length of the get call for exporting the report which was inconsistent with the default settings of the ASP.NET web application. We solved it by making the maximum url length explicit in the web.config.

<system.webServer>
<security>
<requestFiltering>
<requestLimits maxQueryString="3000" maxUrl="1000"/>
</requestFiltering>
</security>
</system.webServer>

Bye

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

IsabellaZhangMSFT-7746 avatar image
0 Votes"
IsabellaZhangMSFT-7746 answered

Hi @AlessioMorganti-2706,

How about put the web application and the SSRS in one server.
I think your issue is about the server schema, and it is out of my rage , you can ask on the relevant forum.

And this is the example of Scale out SSRS deployment to share the same single Report Server Database,you may take a look .
scale-out-ssrs


Best Regards,
Isabella


If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.