Microsoft.ReportingService.Interface not found even with Reporting Server installed - reporting-services

I have been trying to compile an old project for my company, which uses Microsoft SQL Server 2005 as the database. Within the project, one part is to reference Microsoft.ReportingService.Interface. However, upon compilation, the compiler said it cannot be found.
My machine (a virtual one, anyway) is a Windows Server 2008 R2 (64-bit) Standard version, with Microsoft SQL Server 2005 (64-bit) installed (along with 64-bit SQL 2008 and 2008 R2). All 3 SQL Server versions got everything installed (SQL Server, SSRS, SSAS, SSIS, and all misc stuff). However, when I look at the GAC, only the one with SQL 2008 was there (version 10), and the one for SQL 2005 is not there. Order of installation is SQL 2005, 2008 and 2008 R2.
Does anyone know whether I will have to reinstall SQL 2005, or if there is any other way to make it work?
Thanks in advance!

I have figured this out by myself... by searching the installation folder, the DLL is in there, but it was not registered to the GAC. Simply installing the DLL to the GAC directly solves the problem.

Related

SQL Server version mismatch

I'm trying to attach a SQL Server .mdf to my Management Studio 2014, but I get the error:
Attach database failed for Server '...\SQLINSTANCE'. (Microsoft.SqlServer.Smo)
Additional information:
An exception occured while executing a Transact-SQL statement or batch.
(Microfost.SqlServer.ConnectionInfo)
The database 'DatabaseName' cannot be opened because it is version 706. This server supports version 663 or earlier. A downgrade path is not supported.
Could not open new database 'DatabaseName'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
The .mdf was created on SQL Server 2012 (which presumably is represented as 'version 706' in the error message).
OK, so I need to upgrade my DB engine to 2012 on my home PC. That means installing 2012 Express from https://www.microsoft.com/en-gb/download/details.aspx?id=29062
A couple of questions though before I do that. By installing 2012, would it be added to Management Studio 2014 automatically? Would I then have both 2008 & 2012 as options for new databases I might want to create, or would 2012 simply replace 2008?
On the download page, it says the supported OSs are "Windows 7, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2". But I'm using Windows 10. Is this just a case of MS not updating the page or does 2012 really have a problem with Windows 10?
EDIT: It's true that this question is similar to ones previously asked on SO (such as The database cannot be opened because it is version 706), but here I'm not contemplating rolling back the 2012 version of the DB to 2008, but issues pertaining to installing 2012 on my home PC.
So, your SQL Server version is 2008 - you have 2014 management studio and you need to use a database from a server version 2012.
If that is the case; then I hope some of the following will help:
Windows 10 can run SQL Server 2012 fine.
The documentation might just not be updated, but I've not personally seen any issues on multiple instances.
Management Studio 2014 can connect to SQL Server version 2012 as well. You don't need to install it again.
Unless you wish to remove SQL Server 2008, you'll need to install 2012 as a new instance, so you basically have two SQL Servers running. This however, will have affect on how you connect to the databases.
Check out, for example: https://msdn.microsoft.com/en-us/library/ms143531.aspx for more information
So instead of having multiple instances, consider whether you'll still need 2008, so it might be removed if you don't need it at all.
Also - consider whether it might be worth it to upgrade your local instance to newer version - 2014 for example. However this of course might give you the same problem in reverse in the future, if you ever need to make a database on 2014 instance and move it to a 2012 instance.
It all depends on the actual requirements, set-up and development models. Basically because you say it's your home computer, I'd think the newest version might just be the best approach, as you're less likely to use that version as a "creator" rather than a development version.

Upgrade RDLC from 2008 to 2010 (2005 report to 2008 report) Error

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.

Installing SQL Server Reporting Service (SSRS) 2005 on machine having 2008 version already, possible/how?

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.

Install SQL Server 2008 R2 & .Net 3.5 during setup

I need to create a setup package that will not install SQL Server 2008 R2, a sample database, data and .Net 3.5 SP1 along with a setup installation.
I am using Visual Studio 2008. How do i do this?
Is it possible to install the full version, not express from setup package?
You can add other installers to setup packages; however it isn't normally customary to include one for SQL Server for the following reasons:
1, What if they have a different version installed (i.e. you are installing SQL Standard and they already have SQL Enterprise available)?
2, What if they have a SQL server installed on another server that they wish to use?
3, In a couple of years time Microsoft release the next version of SQL server and your software is still installing SQL Server 2008?
For the sample database and data just add the SQL in as a resource and get the app to run the script on first execution.

SQL Server 2008 Installation Incomplete

This question may look stupid and dumb but I needed to ask this. I installed SQL server 2008 but what I have finally installed is this (see the images).
Is SQL Server 2008 is installed? If not how can I install it?
Start Menu
Control Panel (Add/Remove)
SQL Server 2008 is installed but you might have to install Client tools for Sql Server 2008 to access the installed instance..