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.
Related
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
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.
I've downloaded SQL Server 2016 standard edition trial along with SSDT in order to test what one can do with a standard edition in SSIS, SSRS, and SSAS.
I also wanted to know whether standard version's SSISDB logging capabilities differs from the one in Enterprise. For this I wanted to create an SSISDB catalog under Integration Services Catalogs in SSMS.
When I try to do this, however, I get the error saying that
The catalog backup file 'C:\Program Files\Microsoft SQL Server\130\DTS\binn\SSISDBBackup.bak could not be accessed. Make sure the database file exists, and the SQL server service account is able to access it
From googling this issue it appears as this message shows up whenever someone doesn't have SSIS installed, but I have SSIS on the machine, I've even made a small Project and executed it from within SSIS without any issues just to verify.
I have set this up on localhost where I am the admin. Does anyone have any ideas why this won't work?
Regards,
Cenderze
To check if SSIS installed, open Sql Server Configuration Manager, in the SQL Server Services, is something like 'SQL Server Integration Services 13.0' running?
Experienced this error message on MS SQL Server 2017.
Resolved by launching MS SQL Server 2017 install media, added Integration Services feature.
After successful installation, when back into SSMS, right-click on Integration Services Catalog for Create Catalog... option.
You will be asked for an encryption password to create the new SSISDB.
Hope this helps!
I faced with this error when I used lower version of SSMS than SSIS. Check if you use proper version of SQL Management Studio.
You need to go back to the SQL Server installation and check the integration services checkbox.
The issue is because SQL Integration services is not installed properly with the existing SQL Server you are using.
you can check if SQL Integration services are installed or not by,
Opening --> SQL Server Configuration Manager--> SQL Server Services --> Check if "SQL Server Integeration Services is there"
if its there and if you still get the same issue try re-installing.
Else install the SQL Integration services to your existing SQL Server.
The detailed step to installation is given in this link : https://www.mssqltips.com/sqlservertip/6635/install-ssis/
hope this helps !!
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!
I have a SQL box and a web box; the SQL box is close to capacity. I'd like to install reporting services and thought about installing it on a SQL instance i would install on the web box, and only use that instance for reporting services. Is this a good option? What pitfalls will I have if I try to do this?
It's recommended to not mix IIS and SQL on the same box. Because 0f different access patterns and security at least.
The fact your SQL box is close to capacity should set alarm bells ringing and big red flags waving. The Report Server databases are quite small, and I'd lie awake at night if I thought it would overload my your DB server
SO: Should SQL Server be on the same machine as your IIS installation?
If you just install the Reporting Services (SSRS) web piece this should be fine. SSRS comes in 2 sections, the web piece and the database catalog so you could have a web site run on the web server and the catalog database would live on you normal database server. You will need to manually configure SSRS through the SSRS configuration utility and specify the remote server name during the database set up.
The downside of this is that you would be required to purchase an additional SQL license for the web server, since an SSRS installation counts as a SQL instance, but you should be able to use a standard edition license to for both instances.
I didn't find a lot a great resources but the steps would be like this:
--install just SSRS (and Client tools to debug connection issues) on the web server
--run the SSRS configuration tool and configure the app pools, virtual directories
--in the same config tool in the database section just specify the remote SQL server and select "create database" and it will create the database for you and apply the permissions needed to the database instance.
One thing I have found to be kind of quirky about the SQL 2005 SSRS config tool is that you have to "apply" changes when it doesn't seem that intuitive, so beware.
Here's an OK link:
http://www.databasejournal.com/features/mssql/article.php/3573361/SQL-2005-Reporting-Services-Part-1.htm