After installing SQL Server 2019 & SSRS 2019 developer editions, I am not able to use the object explorer in SSMS to connect to SSRS. (I am also unable to use a web address to open SSRS currently due to my security software.) I think the reason I can't use SSMS is due to one or more of the following:
an error in installation
problems with older version files still left on the computer
an error in using the report server configuration manager
the rsreportserver.config file not getting properly updated.
Before installing 2019 developer editions, I have installed and tried to uninstall most versions since 2012, including 2019 express & evaluation. When I tried to install 2019 evaluation software, I created a new db engine (MSSQLSERVER02) while installing SQL Server. After I installed SSRS, I used the report server configuration manager to use this new engine as the database). This tested correctly. I opened up SSMS & connected to this db engine. When I tried to go to SSRS, the only option was a previous db engine (MSSQLSERVER01). Though I put the new name in the config mgr, there still existed an rsreportserver.config file which had the old db engine (MSSQLSERVER01) and a coded database name.
When I uninstalled the eval ed., then installed the dev versions, I still had the same problem with the old db engine (MSSQLSERVER01) name appearing. When I chose the older db option, I get a lengthy error:
Cannot connect to LAPTOP-999999\MSSQLSERVER01. Unable to connect to the server at LAPTOP-999999\MSSQLSERVER01. The specified URL might not be valid or there might be a problem with the report server version or configuration. Specify a different URL, or contact your server administrator to verify that the report server runs SQL Server 2008 or later. (Microsoft.SqlServer.Management.UI.RSClient)
When I type the the new db engine (MSSQLSERVER03) over the old, I get an error: "TITLE: LAPTOP-999999\MSSQLSERVER03 cannot be found.The Reporting Services instance could not be found. (Microsoft.SqlServer.Management.UI.RSClient)
I also tried putting in the web address into the server name (suggested by DeanOC in a similar question).
Any direction on what to do next would be greatly appreciated!
thanks,
Ginger Burton
c
Related
I have downloaded, installed, & tried to configure evaluation copies of 2019 SQL Server & 2017 SSRS.
When I used Report Server Configuration Manager, I put my new instance of the SQL database engine (MSSQLSERVER05) into the database name.
This connected properly.
Through multiple tries, I have created multiple report servers & temp report servers.
However, when I try to access SSRS from the Object Explorer of SSMS 18.5, 2 old DB names & "SSRS" are the only instances I see.
I have tried using SSRS, but the error says the reporting service instance cannot be found.
If I type in the name of the new database engine (MSSQLSERVER05), I get the same error.
I have had earlier trials of SQL, but tried to uninstall all of them.
I notice that the file rsreportserver.config has "SSRS" in it as well as a coded database name.
This likely needs to change somehow. I would appreciate any help!
Thanks!
Ginger
First, use Developer Edition instead of Evaluation Edition for non-production scenarios, as it's not timebombed.
when I try to access SSRS from the Object Explorer of SSMS 18.5,
There's not really much use in using SSMS to connect to the Report Server. Just open the Report Manager Portal in your browser.
old DB names & "SSRS" are the only instances I see
Not sure, but SSRS 2017 is not installed as part of a SQL Server instance, and you can't have multiple instances installed on a computer. This change was part of the transition of SSRS be a scaled-down edition of Power BI Report Server.
We recently updated our production SQL Server 2016 Enterprise instance from SP1 to SP2. We are currently on version 13.0.5026. Prior to the upgrade, a user with connect rights to SSISDB and proper rights on the Integration Services Catalog folder could deploy an ISPAC file successfully.
After the upgrade, the same users can still deploy to the SSISDB, but when you execute the .DTSX, the script task inside fails validation. If I deploy the exact same ISPAC as a sysadmin, there's no issue. The usual solution I've seen is to confirm that SSDT Configuration Properties are set to SQL Server 2016. We have verified this is set correctly prior to building the ISPAC.
I saw a similar issue when migrating from SQL Server 2014 to 2016 a couple years back, but the solution at that time was to give the Proxy account that runs the package modify rights to the C:\Windows\Temp folder so it can generate temp files. This new issue is hard to pin down, and I don't want to give out sysadmin just so others can do the simple deployment steps.
Any thoughts or suggestions are appreciated.
*******Update/edit************:
The server has a SQL Server 2016 deployment tool located under SQL Server/130/DTS/Binn - ISDeploymentWizard.exe. This deployment tool works. There is another identical wizard under the 140/DTS/Binn location, same name but 1 KB larger (assuming this is because SSMS is a separate install now, and I installed latest and greatest on server). This one fails deployment. I'm banging my head against the wall as to why one works but the other doesn't. Locally we all use SSMS 2017, and with that we get the 140/DTS/Binn ISDeployment file, not the 130 (since that's SQL Server 2016 and we're using SSMS 2017, which I thought was backwards compatible). Either way, this problem just started occurring and we've been on the same version of SSMS for a few months.
Image of the Execution information report from SSMS
Had resolved a similar issue with C# scripts recently. In short: don't use 140 version of ISDeploymentWizard.exe with MS SQL 2016. It apparently mangles something in C# code, or components' properties, and 2016 runtime stops recognising them.
In my case, a package with C# script source has started to throw the following error during the validation phase:
Error: Microsoft.SqlServer.Dts.Pipeline.ComponentVersionMismatchException:
The version of C# source component name is not compatible with this
version of the DataFlow. [[The version or pipeline version or both for
the specified component is higher than the current version. This
package was probably created on a new version of DTS or the component
than is installed on the current PC.]]
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostCheckAndPerformUpgrade(IDTSManagedComponentWrapper100
wrapper, Int32 lPipelineVersion)
The first comment here has helped me to ultimately identify the cause.
I had an SQL Server 2012 database instance installed on server A.
I then installed SSRS 2016 only (not the the complete SQL Server 2016) on server B but pointed the SSRS instance to host its ReportServer database on the SQL Server 2012 instance installed on server A.
At this point all worked well.
I then had a requirement to upgrade SSRS 2016 to SSRS 2017.
I used the Microsoft SQL Server 2017 Reporting Services stand alone installer from https://www.microsoft.com/en-us/download/details.aspx?id=55252
In SSRS 2017 configuration manager, i selected to use an existing database and pointed to ReportServer database i have in the SQL Server 2012 instance i have on Server A.
In SSRS 2017 configuration manager, i have deleted all encrypted data.
I can browse to the reports web portal url, see data sources and the deployed test report files but when i try to open a report, i get the error blow.
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '2017'. The expected version is '173'. (rsInvalidReportServerDatabase)
i have tried to run delete from ReportServer.dbo.ServerUpgradeHistory where ServerVersion = 173 but i still get the same error.
Looks like the old version value is still being stored somehwere in a config file.
Where else should i look, what else should i try?
I resolved the issue by
1- Taking backup of ReportServer databases, then deleting them
2- stopping all report services' windows services. Made them Manual startup.
3- Opened the Reporting Services Configuration form Start Menu > SQL Server {Version}
4- Starting the service from the Configuration application
5- Recreating database from Database tab
Solution is to upgrade SQL Server 2016 to Service Pack 2: SQLServer2016SP2-KB4052908-x64-ENU
https://www.microsoft.com/en-us/download/details.aspx?id=56836
The least intrusive solution I found was this:
USE [ReportServer]
DELETE FROM ServerUpgradeHistory WHERE ServerVersion > 173
Thanks to #Henrik H in the following post:
https://serverfault.com/a/893739
I am trying to make a local development environment SSRS server (just on my local machine).
I have installed SQL Server 2016 Express with the "Database Engine" and "Reporting Services - Native" modules.
When I go to "Reporting Services Configuration Manager", I get this initial screen:
And then when I hit find (w/ just MY-PC-NAME {Obviously, with my real PC name), I get:
And when I add the full SQL Server 2016 Express Reporting Services server instance name (i.e. MY-PC-NAME\SQLEXPRESS), I get:
I have googled these errors / messages to death and it seems that all of the advice / solutions are for older versions of SQL Server (i.e. 2005 and 2008). I have not really found any information on the WMI Provider (other than: https://technet.microsoft.com/en-us/library/dd353297(v=sql.90).aspx ... of which I tried for v9, v110, and v140) all without success).
I cannot access the report server in any way (from IE or IE as
Admin).
I have checked and have the SQL Server Reporting Services service
running.
I have installed SSRS when installing SQL Server 2016 Express and
have tried both "Install Only" and "Install & Configure"
installs...with the same results.
I have also enabled IIS & Associated Windows Features with no luck
either.
I have double checked the Windows Firewall exceptions/rules for SSRS
and those are correct too.
Has anyone else encountered these errors and fixed them and has a Step-by-step guide to fix these errors / get a local Report Server setup for development purposes?
OR
Perhaps I am going about this process all wrong to get a local Report Server setup for development purposes?
Any advice or insight on this would be immensely appreciated.
I had the EXACT same problem. Here's the fix:
1) Go back to the SQL Server download page and re-download the installer for SQL Express.
2) Select the first option to add new features to your installation
3) On the second step of the wizard choose to "add features to your existing instance"
4) When you get to the screen asking which features, choose reporting services
5) Complete the remaining steps of the install wizard
6) When you run the reporting services config tool do not put "\SQLExpress" at the end of the service name. When you hit find, "SQLEXPRESS" Will appear below.
I'm trying to move my databases to a newer Azure subscription. I used to simply click "Deploy to Azure" on a local database from SSMS and have it deployed to a specified Azure server. Importing/Exporting a BACPAC file also works. However, I can't seem to do any of this on the new server. I keep getting the error:
"The service objective 'Web' specified is invalid."
Googling around, I found this thread explaining the need to update the CREATE DATABASE template to accommodate Azure Databases (Azure upgrade, I'm guessing). However, the hotfix provided is specifically for SQL Server 2014 and I'm using SQL Server 2012. I checked other cumulative updates for 2012 here but found no fix for the issue.
Is there any other way I can fix this without having to upgrade to 2014?
Just to summarize my software versions:
SQL Server 2012
SQL Management Studio 11.0.2100.60
Local database: SQL Server 10.50.16000
Old Azure server: SQL Server 11.0.9230
New Azure server: SQL Server 13.0.15
You are getting this error because the latest V12 servers are not supporting the Web and Business Editions anymore. If you don't want to upgrade to SSMS 2014, you can create a V11 server and import your DB on this server. However this is only a temporary solution as Web and Business edition databases will be retired in September. At this point you will have to work with the latest tools to avoid this problem.
There is a Hotfix for it you can download and install on your machine. Please navigate to:
https://support.microsoft.com/en-gb/kb/2936603
You need to enter your email then download link will be sent to your email address. Then install it on your machine and you can see the following options:
Install the database as a Data Project into Visual Studio,
Set the target framework in the properties window to SQL Azure,
Build the project and resolve any unsupported issues.
Publish to your azure site.
I have tried the above and did not work for me - this solution worked!