We're trying to set up an environment to migrate an SSRS 2005 installation to SSRS 2012. The install of SSRS 2012 appeared to go fine. I understand that 2012 (well, 2008 +) does not need IIS anymore, that it uses something called HTTP:sys. Aside from not knowing what HTTP:sys is, I'm fine with it. The new server did not have IIS installed on it when I installed SSRS 2012. It does now but it is shut off. So SSRS 2012 is installed and configured according to the prompts (and a Youtube tutorial and a comparison to how our SSRS 2005 is configured) and it all seems straight forward and should "just work". But when I follow the URL to the Report manager, I'm prompted for network credentials and then get a blank webpage, not the following as expected (except empty of course):
I've run into this one before on an install of SSRS 2008R2.
Open the rsreportserver.config(By default, it can be found from C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer)
Comment out the <RSWindowsNegotiate/> under <AuthenticationTypes> element.
Microsoft Reference
Related
I have an SSRS report project I'm working on in Visual Studio 2015, and I am unable to deploy my reports to the correct target server version.
The reports need to be able to deploy and run on SQL Server 2012, 2014 and 2016. Visual Studio 2015 allows for a Target Server Version option for the project of 2008R2, 2012, or 2014, which is what the target server version of the project is set to. The designer automatically upgraded the source RDL file schema to the 2016 version of the report once you open and do anything within it. I understand this part is by design.
The problem comes when you build the report. The build output files in the \bin\Debug or \bin\Release folders are not targeted to the correct server version. The following tag looks like it updates correctly in the output files:
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
However, the build fails to remove and leaves behind all of the other SSRS 2016 tags within the built RDL files, and as such cannot be deployed to SSRS 2012 or 2014.
I have Visual Studio 2015 v 14.0.25431.01 installed with SQL Server Data Tools v14.0.60812.0 with SQL Server Reporting Services 13.0.1700.68.
Is there something that I'm missing that needs to be done as well besides setting Target Server Version to "2008R2, 2012, or 2014" to get it to build to the correct Target Server Version?
I had this same problem. What I needed to do to resolve this was
Clean the project
Under Project > Properties > General set TargetServerVersion to "SQL Server 2008"
Set TargetServerVersion to "SQL Server 2008 R2, 2012 or 2014"
Rebuild the project
Your project should now deploy to the correct version
I'm new to SSRS.
Recently upgraded my development environment from Visual Studio 2010 to Visual Studio 2015 Enterprise Edition. Currently my reports are made using Crystal Reports. I would like to to use SSRS and I'm trying find out my current environment will allow me to do it.
So now I'm using Visual Studio 2015 and SQL Server 2008 R2.
Can I create SSRS Reports using these two?
If yes, how can I create it?
I know how to create a report and publish it using the Business Intelligence Development Studio in SQL Server 2008 R2. But could not understand how I could use those reports in my WebApplication project in Visual Studio 2015.
Also would like to know - Is it possible to reuse my existing datasets which I'm using in my Crystal Reports?
Should I upgrade my SQL Server version?
Yes, you can create reports for SSRS 2008 R2 with VS 2015. You will need to download, and install, the SQL Server Data Tools (SSDT) at the following link.
https://msdn.microsoft.com/en-us/library/mt204009.aspx
To build reports, create a new project using the Report Server Project template found under Templates/Business Intelligence in the New Project dialog. (After you install SSDT)
This is the replacement for BIDS, so much of what you see should look familiar.
Not sure about the Crystal Reports datasets, but you should be able to reuse any SQL or stored procedures that may be a part of these.
Should you upgrade? At some point, sure, but it isn't required. SQL Server 2016 is about to be here, and you are working with a product that is over 4 years old, and more than likely going to be out of support soon, if it isn’t already.
There is a setting in Visual Studio (See above answers for more details.)
There is a setting in
Project --> Properties --> TargetServerVersion
Note that here, server means database server or db-server, as opposed to web server or report-server.
But note well: For me, it is only the version in the folder:
..Projects\myProject1\myProject1\bin\Debug
that will actually deploy and work.
I've been trying to get a report running through Microsoft ReportViewer in Visual Studio 2012. Here is my situation.
I have a report (.rdl file) that was originally created through Microsoft Reporting Services running on a SQL Server 2008 R2 server.
I originally tried moving it into a VB.NET project running through Visual Studio 2005, but when I converted the .rdl file to .rdlc and tried to bring it into the VS 2005, I could not view the .rdlc file in design time. A while after that, I figured out that this was due to schema compatibility issues because of the fact that the report was created on a SQL Server 2008 server.
So then I tried creating a project through Visual Studio 2012 instead, which we also had in house. This time I was successfull at being able to view the report in design time. However after that, I ran into run time issues because I was using Version 8 of the Microsoft.ReportViewer.Winforms dll. I believe that this was also due to a schema comaptibility issue
So now, I'm trying to move up to using a newer version of the Microsoft.ReportViewer.Winforms dll (Version 11). When I remove the Version 8 and add the version 11 instead in my references, everything appears to be fine at first, no errors present. However, when I try to build my project I get the many compile errors all over the place like the following:
Type 'Microsoft.Reporting.WinForms.ReportViewer' is not defined.
The wierdest part is that if I were to remove and re-add the reference, or check one of the Microsoft.Reporting references in the Imported namespace, all the errors go away. But when I rebuild the project the errors come back, and I'm stuck.
I'm currently running the Microsoft .NET framework 4.5 on my computer, and I'm using Microsoft Visual Studio Professional 2012 as my development platform.
Any help would be appreciated
Thanks,
Doug
This might help: How to edit SSRS 2008R2 Reports in Visual Studio 2012?
I have multiple reports that have been created over the years and anytime a RDLC file is opened in the VS2010, it is asking for an upgrade. I have seen many posts about changing the .config file, but these files are not using config files since they are application based. I have Microsoft.ReportViewer.Winforms, .Common, .ProcessingObjectModel and, .WebForms 9.0 and 8.0 installed on the lab machine.
After upgrading a report and trying to run it on the lab machine ( ms server 2008) I am returned an error of: "The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition' which cannot be upgraded.
Does Report Viewer 2010 Redistributable Package fix this issue? I cannot find a distinct answer. If not, is there another workaround without changing server modes from local to server?
You should really be opening those using the SQL Server Business Intelligence Development Studio (BIDS), which can be found under the Microsoft SQL Server 2008R2 folder on the Programs menu.
I have a computer (windows 7) which already has SSRS 2008 installed. We also need to install SSRS 2005 on it. When I run installer for 2005 I see "reporting service" option greyed out. What could be the reason? How can install ssrs 2005 on this machine?
They can certainly coexist, I have had servers with 3 versions on them whilst migrating reports.
It's possible that you've installed it with the same instance name which would then make reporting services think that it is already installed and not let you. There could also be an issue with IIS ports.
When I've needed to do this I've installed them the other way around (2005 first then 2008 then 2008 R2) which might be an issue as well due to shared components.
Is there a particular reason you would want to use 2005? Any existing reports that you may have that are 2005 should work fine on 2008.
As Davos indicates they will coexist but you would have to uninstall 2008, then install 2005, and then reinstall 2008.