Share via

Why does SSRS Report Viewer control render error on some machines?

Jerry VanDreumel 0 Reputation points
2024-03-06T17:15:57.81+00:00

Using ReportViewerControl 150.1449.0 to render SSRS (rdl files) in a Delphi application

Click the report from the Delphi application and it opens the parameter box. Enter in parameters and it renders results on working machine.

Click the report from the Delphi application and it immediately generates the error.

Works on some machines but not others.

On the ones it does not work on the message received is "The following error occurred while attempting to load the report. Please try again or contact xxxx if this problem persists. An error occurred during local report processing."

Checked Event Viewer at time of occurrence and nothing renders there.

Was hoping application logs might render something but nothing there either.

Server 2022 using SQL 2019

Workstations Windows 11 and Windows 10 both using latest builds available. Some Windows 10 machines work and some Windows 11 machines work. Others get message provided earlier.

Microsoft Process Monitor used as well but not results.

SQL Server Reporting Services
SQL Server Reporting Services

A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.

Windows for business | Windows Server | User experience | Other
Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. Michael Taylor 61,221 Reputation points
    2024-03-06T20:06:07.99+00:00

    This is a general error meaning it couldn't load the report. There are any # of reasons why this could happen. Please post the relevant code that is failing. Specifically we're interested in what type of report you're using (server or local), how it is being loaded and how you're connecting data to it.

    Capture the callstack at the point of failure. This will help narrow down if it is a problem finding a server-side report, report in a local path, issue getting data or rendering. Wrap the call in an exception handler and look at the exception details and any inner exceptions. The inner exceptions, if available, tend to provide the details of what the actual error is.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.