ReportViewer (remote mode) in VS 2008 and ReportingService Server 2008 not possible? - reportviewer

MSDN says about Report Viewer in VS 2008:
"The ReportViewer controls require information that is only exposed through the SQL Server 2005 SOAP execution endpoint."
http://www.gotreportviewer.com/ says about Report Viewer in VS 2008:
"In remote mode the ReportViewer control can only view reports hosted on a SQL Server 2005 Report Server".
Is there really no Update unitl now for using ReportViewer in VS 2008 in remote mode together with Reporting Service Server 2008 ?
I'm getting error message when using it:
"# The version of the report server web service definition (WSDL) is either not valid or unrecognized. The server is not a compatible version.
* System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header 'SOAPAction':
...schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices/LoadReport..."


I don't think that's quite correct (I'm up and running using ReportViewer in VS2008 against a report server under SQL Server 2008).
Here's my interpretation of the 'rules':
1) A ReportViewer in CLIENT processing mode can't display reports created in VS2008 (Business Intelligence Development Studio 2008) because it doesn't have the necessary code to handle new report objects that were introduced since SQL Server 2005.
2) A ReportViewer in REMOTE processing mode can display reports from SQL Server 2008 Reporting Services because the server itself handles the report building. ReportViewer just streams the results back from the report server.
3) The "SQL Server 2005 SOAP execution endpoint" is what you're actually hitting with ReportViewer, I believe (can anyone confirm this?). I just finished wrapping the SOAP API for my web app that handles publishing reports and the WSDL is called ReportingServer2005.asmx (there's also a ReportingService2006.asmx to be used for SharePoint integration) - there's no 2008.
I'm just moving us from SQL Server 2000 to 2008, so all of my reports aren't using any newer features like the tablix. It's certainly possible that ReportViewer can't display a report from 2008 if it uses any new visual components that were introduced in 2008.

Related

#Errors in SSMS built-in reports

From my local computer I am using SQL Server 2016 Management Studio client (SSMS) to connect to a SQL Server installed on a remote computer. I connect using Windows Authentication method.
My SQL Server Management Studio 2016 installed in my local computer shows below versions installed:
Microsoft SQL Server Management Studio 13.0.16100.1
Herramientas cliente de Microsoft Analysis Services 13.0.1700.441
Microsoft Data Access Components (MDAC) 10.0.17763.1
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 9.11.17763.0
Microsoft .NET Framework 4.0.30319.42000
Sistema operativo 6.3.17763
SQL Server version installed on remote computer is as below:
When I build reports I get a lot of "#Error" printed on it. As an example, to build a report about all blocked transactions I go to Server node -> Reports -> Standard Reports -> Activity – All Blocked Transactions. It shows "#Error", see below screenshot (in this screenshot there are no blocking transactions):

It seems it is caused by an out-of-memory exception. Restarting SSMS corrected the problem. After restarting SSMS, built-in reports are correctly generated, no more #Errors are shown.
I found this solution here.

Microsoft SQL Server 2012 Reporting Services

Whether it is possible to adjust mailing which will be automatically formed in Microsoft SQL Server 2012 Reporting Services until it turns out to send the report?

How to Get SQL Server Reporting Services to Install so that it Works

I found this link for SQL Server Reporting Services
SQL Server Reporting Services
In this they said go to SQL Server data tools and when I search I can't find so what I do for that?
And when I try to do that when I go to configuration tools in SQL Server 2008 R2 and click on
Reporting Services configuration manager then it show me error when I connect it show me error
Unable to connect to the Report Server HOME-PC
So here anybody can tell me how do I start using SQL Server Reporting Services?

You did not install SSRS correctly I am guessing as parts are missing. You can install SSRS through the SQL Server insall in a few different versions:
SSRS 2012 where and how to download
The download for Express(the free version) is here:
http://www.microsoft.com/en-us/download/details.aspx?id=29062
Once you get a successful install there is a more SSRS centric tool than the services configuration. It is under All Programs>SQL Server (version)>Configuration Tools>Reporting Services Configuration Manager. You need to ensure that SSRS is fully working before developing for it. I wrote an article on deployment here that covers the bases:
How SSRS deployment works?
Checking that SSRS is actually up and working with correct permissions is half the fun of SSRS! ;)

SQL Server Reporting Service

I'm trying to set up a Report server on my local machine, but I cannot get past the Database Setup step in the Reporting SErvices Configuration Manager.
I have SQL Server 2005 on my machine, which runs XP SP3.
I have reporting services installed, and the service is running, but anytime I try to setup the Reports and ReportServer database, I get the following message:
The feature "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services
Any help would be greatly appreciated.

Can you run the SQL Server Installation Tool.
Under Tools Select Installed SQL Server Features discovery report.
Tell us what this says.

Sql Server Reporting Service without Full SQL Server

I am going to use SSRS to generate report for my website.
Scenario:
I have 2 servers, Application server & Database Server.
I want to have reports(.rdl files) sitting on Application server(IIS) accessing data on SQL server(Database Server)
In order to fulfil these requirement I require to install SQL server 2k5 on my Application server just for having SQL server reporting service. So I am just waisting one of licence of SQL server by installing that on Application server.
Is anyone having any idea how to install only reporting service with SQL server 2k5??

In order to have Reporting Services on your Application server, you would have to use a SQL license. You can install just the Reporting Services section of SQL Server, but it is still technically part of the SQL Server application and requires a license for use on that processor(s).If that is a huge issue, then I would have to recommend keeping the Reporting Services section installed with the rest of the database installation on your Data server.
http://www.microsoft.com/sql/prodinfo/previousversions/rs/howtolicensers.mspx
The server components of SQL Server 2000 Reporting Services include the Report Server and the Report Server Database. The Report Server processes and renders reports, and handles scheduled events and report delivery. The Report Server Database stores report definitions, report metadata, subscription information, and so on. Each Report Server requires either a local or remote connection to a Report Server Database. To use any of these components, each computer on which the Report Server and the Report Server Database are installed must have a valid SQL Server 2000 license.

You could install SQL Server Express on the application server.
It's free, and there's an edition which comes with Reporting Services.
In comparison with the "real" editions, SQL Server Express Edition is limited concerning how much CPU and RAM it can use, but it will probably be fast enough to run your reports.

blatantly incorrect. You do not need a SQL Server license to use SQL Server Reporting Services, you can use SQL Server Express edition. I've use SQL Server Express Edition in addition to linked servers-- to query stuff on -ANY- database server. And it works great.
SSRS is a great platform, I Just hate it when people run around saying that you NEED a license to use it. I'll bet that guy works for Oracle corp!

You do have an alternative. You can embed reports directly into your code projects in .Net. In this case the report runs through the Microsoft.Reporting.WinForms and Microsoft.Reporting.WebForms namespaces, ReportViewer object. Each report will have a ".rdlc" extension instead of ".rdl", though the two files types are actually equivalent. There is an ASP.Net version of the ReportViewer that allows you to integrate these reports into your website. You just need to drag the ReportViewer control from the toolbox into your website to configure it. For more information, see the MSDN overview of ReportViewer Controls.

If you dont want to use a whole license you can always use reportviewer. Just so I dont put too much answer out here, the big site for this is gotreportviewer.com.
The reportviewer control does the work of the reporting services server when it comes to the generation of reports. RDL files are like xml files and dont do much until they are interpreted. If you embed the reportviewer in your application on the web the work will be done on the user side. It is simialar to microsofts xps format, it has to be interpreted.
If you don't want to create an application for your reports the new version of sql2008 with advanced controls allows you to install a free version of reporting services. It doesnt have all of the goodies but it works for simple deployments.