A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
Hi @Mary Her ,
There's no Microsoft-side outage tied to this. That message (Sys.WebForms.PageRequestManagerServerErrorException, status 500) comes from SQL Server Reporting Services itself it's a generic wrapper, and the real cause is only visible in the report server logs.
Since SMILNet is an internal report portal, your IT/SSRS admin team will need to check:
- Report server logs: <drive>\Program Files\Microsoft SQL Server\MSRS<version>.<instance>\Reporting Services\LogFiles Look for ERROR entries at the time it failed.
- ExecutionLog3 view in the ReportServer database if the status shows rsProcessingAborted, the report is timing out. Common fixes on the report server side: - Increase executionTimeout in web.config - Add aspnet:MaxHttpCollectionKeys if the report passes many parameters - Check RSTempFiles folder permissions for the service account - Recycle the SSRS app pool If you can get those log lines from your SSRS admin, we can narrow it down further.