SQL Reporting :: Use The ReportViewer To Display SSRS Reports?
Mar 26, 2010
Starting to look into an web app thet uses the ReportViewer to display SSRS reports. This is for SSRS 2008. What would be the best way to go about the follwoing: The reports are sales reports so only ceratin people will get to see certain reports.
1: If a user opens a report which they can see and that report has a subreport which they can't, will the subreport still be viewable?
2: If the webapp will be used by many different people internally and eventually by outside people, what is the best security startegy to use, just plain ServerReportCredentials passing, or something else?
I have SSRS (discountasp.net) and I currently display reports on my web page using Reportviewer and use .net code to authenticate them (username/password). Recently I have bought VPS (Windows Server 2008 Web Edition + .net 4.0) and would like to use SSRS the same way as above. I have never done this before so need some guidance on that just to ensure the server is still "safe". Below are some questions that I think are related but feel free to add other comments that I didn't think about.
1) Set up new user? What permissions are required? 2) Configure SSRS to for external connections? 3) Firewall?
I am currently working on an applicaiton that will use the ReportViewer to display reports in an aspx form.
I have mostly done RDL files but was considering using RDLC this time. With over a dozen reports I will be using stored procedures or inline queries for the datasource.
The problem I am having is that if I use RDLC, I do not know how I can getting around having to do "IF" checks for assigning the proper datasource to the ReportViewer's LocalReport.DataSource.
With the RDL file I do not have that problem since it uses the Procedure created in the report.
Is there a way to dynamically choose the proper datasource for a class of different methods for different reports or is this simply a limitation in using RDLC over RDLS ?
It seems that the RDL development environment is easier from that standpoint.
I am getting "ASP.NET Session Expired" error when viewing SQL Server 2008 reports using the Microsoft ReportViewer web control. I found this article http://balanagaraj.wordpress.com/2009/09/25/session-has-expired-in-asp-net/ which suggests to use one worker process in IIS application pool, but that may affect performance, is there any other solution for this? I tried setting "AsyncRendering" to false already and that didn't work.
I'm designing some reports to summarize recently compiled research findings. These reports are going to be posted on an ASP.NET page (via the report control) on the web site. I do not want to authenticate users, as the findings are meant to be public and requiring users to register and authenticate would add a barrier and is likely to decrease traffic.I've seen similar posts where reports are meant to be viewed by everyone on an intranet and permissions could be set using a designated workgroup. I need alternative solutions to the problem of making a report viewable by everyone who visits a site. I'm also currently unfamiliar with Kerberos (and I know that will probably pop up as a potential solution), so if there's a convenient way outside of that it would be great.
I am using VWD 2008 with VB.Net code-behind. I have multiple parameterized RDLC reports that use tableadapters in a .xsd dataset that I use a reportviewer to view / export the PDF reports.
Lately, we have noticed that the reportviewer is causing many errors on our webserver and sometimes causing the webserver to crash. It has been recommended to me to move the RDLC reports to SSRS, which we also have up and running on another server.
My question is how do I do this? Do I have to convert them to RDL files? What about the fields on the .aspx pages that supply the parameters? Also, what do I do with the tableadapters?
We want to not use the reportviewer but still have the capability to retrieve the RDLC reports in PDF format.
I have been developing reports using BIDS 2005 and deploying them to a report server on my development machine.
These reports can be called succesfully from both the report manager and my asp.net website.Everything has been working fine.
Some time back some early versions of the reports were deployed to a test server in order that they could be tested away from the development machine. The reports processed successfully.Today I have uploaded a number of completed reports (using Report Manager) to the test server and am getting an error message for each one when I try to run it direct from Report Manager.
The message is: "An error has occurred during report processing Common Language Rutime detected an invalid program"
I've been trying to resolve this for a few hours now and am getting nowhere. Google has thrown up some finds on the error message but these seem to refer to people having issues with the compilation of large methods or forms with a very high number of controls.I can't see this being appropriate because most of the reports are relatively simple and the most complex probably has only 100 different controls.
Due to a recent hard disk failure, my company issued me Windows 7 (in part for certification testing as we begin to roll it out to the general employee base at the end of the year). As a result, I'm using vwd 2010, where I had been using vwd 2005. The existing site used the reportviewer 2005, but I'm finding it difficult to find information about editing those files in vwd 2010. Can anyone point me to the appropriate place or have some insight as to what must happen in order to manage 2005 reportviewer reports in vwd 2010? I have downloaded and installed the reportviewer 2010 add in. The site is using framework 2.0 even though the web servers are using 3.5 (One of the things I need to do is upgrade the site to 3.5, but I have a support issue to work on first.)
We currently have two web servers (Windows Server 2008 Standard, IIS7) setup to host an ASP.Net website and are using the basic features of our hardware firewall to provide network load balancing (NLB) between the two servers. This means we have had to change the ASP.Net session state mode to SQL Server in order to make the data stored in session accessible no matter which server responds to the request. The main issue now is that crystal reports (basic edition packaged with VS2008) do not seem to support serialization which is needed in order to store/transfer the report to session state on SQL Server.
From what I have read so far in order to get crystal reports working in a web farm environment it seems the only option is to upgrade to Crystal Reports Server and load the reports from a third server. Another option may be to use SQL Server Reporting Services (SSRS) as we already have this so no extra cost involved, however I'm not sure if SSRS would resolve the issue with storing reports in session?
I am using one ReportViewer with already established SQL Stored Procedures connected to three report files (*.rdlc). There are three radio buttons which are to be associated with each report that needs to be displayed in the ReportViewer. Here is an example if a radio button is selected:
[Code]....
The ReportViewer works for the first radio button selection but then for the other selection I get the following error:
A data source instance has not been supplied for the data source 'spEx1'
i Have upgraded my Reports from Report server VS 2005 to VS 2008 .
My reports works fine in local, development & test server.
After Ugrading to 2008 it works fine in local server & devlopement serverr.
When i deployed to Test server i am trying to access my reports i am getting below errors,
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DataSource1'. (rsErrorOpeningConnection) For more information about this error navigate to the report server on the local server machine, or enable remote errors ..
i checked the Datasource conncetion properties..its pointing to correct Test database only..
My reports are windows integrated...
Now it works in srs 2005 developement & test server. For same properties it works in dev server, it doesn't works in srs 2008 test server.
Users want to get email PDF report. I am using ASP.net Reportviewer .rdlc file in local mode (I don't have a sql reporting services). My question is how to generate PDF reports programmatically without going to the report web page.
I am trying to build reports using the ReportViewer feature in Visual Studio 2010 Professional and I am encountering the following error when I try to run the aspx page containing the report.Compiler Error Message: CS0102: The type 'SupApps_SecurityDataSet' already contains a definition for '_schemaSerializationMode'The error is stating the issue is on line 27 of the file but I dont see how to view the code on a rdc file in Visual Studio.
I have developed a set of ssrs .rdl reports and am trying to display them from the reportviewer control embeded in my asp web page. The problem is that when I select the print icon on the reportviewer control I am prompted to install ms sql server. What is the best way to print .rdl reports from the web page's embeded reportviewer control to the client's local network printer.
In VS2008 C# web applications when using Microsoft Reportviewer to create an embedded rdlc report you can generate a report on the screen but when you try to send that same report to the printer by clicking the printer icon on the toolbar you get an error stating:
"unable to load client print control"
How do you get the report to print on the printer?
Normally, the intention of my report is when the user selects ReportType as ALL, they should enter in EnterID as ALL But for some reason, when the user selects ReportType as ALL and he enters the EnterID as value 100 or 200 or some number, the report is showing incorrect results. Now, what I want is When the user selects ReportType as 'ALL' and if he enters anynumber other than ALL, I would like to see a pop up message displaying saying 'Please type ALL'.
I am new to this sql reporting service. But anyhow by surfing I am able to bind the report but i was stuck in image display.Anyways, i also managed that. But the real problem is whenever i was keeping a image control in rdlc report i was having session prob. If i remove the image control then as usual report works fine.either for session problem or for image display. I am keeping the image name in database but for binding the rdlc report i am using a store procedure which return the path (static) concating with the image name(kept in database).
I try to use a reportviewer for a localreport. The page ran without error but the ReportViewer didn't display, not even the control itself. To verify I did get the data from the SQL server, I bind the same datatable to a gridview on the same page at the same time. The gridview displays the data without any problem and the reportviewer is just a blank area.
I am very new to the SSRS arena and have not yet developed any reports with this. I'm creating a website which requires reporting...as new reports are developed within SSRS, how do those suddenly appear in the asp.net application for selection by a user? I like to have the ability for an administrator to create new reports and allow the ASP.net application to somehow offer it dynamically as a selection. Keep in mind, some of the reports may require input parameters...those parameters would also need to be displayed from the asp.net application also.
Can this be done dynamically some how or does it require actual coding is needed to the website, every time new reports are introduced in order to display the report along with the parameters needed?
