Mez Mez - 4 months ago 49
C# Question

Report viewer does not load, showing blank space - running local RDLC files

I got a problem with reporting services, running local rdlc files on the 2005 version.

I have in the HTML a report viewer set to run locally as follows :

<rsweb:ReportViewer ID="ReportingServicesReportViewer" runat="server" Height="100%"
ProcessingMode="Local" ShowParameterPrompts="False" Width="100%">

In the code

// create SqlConnection
SqlConnection myConnection = new SqlConnection(ConnectionString);
myCommand.Connection = myConnection;
SqlDataAdapter da = new SqlDataAdapter(myCommand);

//get the data
DataSet data = new DataSet();

if (data != null && data.Tables.Count > 0 && data.Tables[0].Rows.Count > 0)
ReportingServicesReportViewer.Visible = true;
ltrStatus.Text = string.Empty;

//provide local report information to viewer
ReportingServicesReportViewer.LocalReport.ReportPath = Server.MapPath(Report.RDLCPath);

//bind the report attributes and data to the reportviewer
ReportDataSource rds = new ReportDataSource("DataSet1", data.Tables[0]);
ReportingServicesReportViewer.Visible = false;
ltrStatus.Text = "No data to display.";

When the method to populate the report viewer with the results of the report is executed, nothing comes up as if the report viewer is not even there.

What I did to trouble shoot till now:

  • Checked the event viewer for errors and this is the only thing related
    which I get, [Domain]\sp_dbadmin Reason:
    Failed to open the explicitly specified database. . However,
    my user which I am connecting is a sysadmin. I have checked that and
    am sure because I checked the sys.server_role_members

  • I tried impersonating the logged in user, to no avail

  • I created a specific user with sysadmin rights, and gave all access rights both from IIS and also on the sql server 2008.

Has anyone encountered a problem similar to this, any ideas?


Try using a simple report , sometimes reportviewer throws exception caused by invalid RDLC and shows an empty report.

Try also to debug the project and look at the output window in Visual Studio: you will see the warning raised bu the RDL engine, it could be useful to investigate the reason of the error.