I am trying to test out the new SSRS 2016 features, here's what I have so far:
Signed up for an Azure trial
Installed a SQL Server 2016 VM
Created a DB
Configured the reporting services to run classic reports
Downloaded the Mobile Report Publisher
I have been trying stuff out using the predetermined data, however I wanted to pull in some data I'm familiar with. When I try to connect to the server (localhost/reports) I get a Server Error as the 'Server does not support mobile reports'.
Is there something I need to configure to enable this?
Thanks in advance
I think you are connecting to a standard edition of SQL SERVER 2016.
https://www.microsoft.com/en-au/server-cloud/products/sql-server-editions/overview.aspx
Unfortunately Mobile Reports are only supported in Enterprise Edition of SQL Server :(
I took the same install steps as you (robbiecutting). I'm running SS 2016 Developer edition. I found that there was no option for creating Mobile reports in the Report Builder (desktop app), but there is one in the web-based reporting services portal:
Desktop app:
Web portal:
It brings up a nice UI for creating one:
Related
please help me out.
Trying to install feature integration services on VM MS 2019 SQL 2017 web edition server, but it is missing the install files. According to Google SSIS is to be included in web edition licence..
If not, how do I then upgrade my SQL edition..
Best
/Peter
As the above comment mentions, the integration services are not available for the web addition. Currently, there is no way to upgrade to another OS version within GCP. You will have to create a new GCE VM instance and choose the proper OS image to use.
I'm trying to connect SQL Server Report Builder 3.0 to SQL Server 2008 R2. When I click on connect (on builder 3.0) it returns the above connection error. SQL Server Reporting Services on ie is up and running but every time I click on Report Builder button on SQL Server Reporting Services (in internet explorer), it opens up report builder 1.0 instead of 3.0 .
I tried different changes on my link but none worked. There were posts suggesting adding / to the end of my link, it didn't work either.
I use Web Services URL from Report Services Configuration Manager. I tried many online suggestions, uninstalled, and reinstalled Builder 3.0 compatible with SQL Server 2008 R2. None worked so far. I'm using win 8.1 if that matters.
Any help is appreciated!
In a normal local network environment if your SSRS server was called myServer then you would view the reports with
http://myServer/Reports . This is the web portal (called Report Manager in earlier versions I think)
Report Builder needs to connect to the service url with, using our example this would be
http://myServer/Reportserver
If this does not help, then please show the connection you have tried and also show the connection that works that you use to get to the SSRS Home page (where you see your reports listed).
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.
Recently, we have migrated a business application database to Amazon AWS SQL Server RDS. We have loved the flexibility of backup and scaling with the cloudified database, but we have need for writing reports for our gathered analytics data. Our in house data analyst is most comfortable using SQL Reporting Services. Normally, this is installed as a component with the SQL Server install, but we obviously do not have that option on RDS.
My question is, has anyone been able to successfully deploy and use SQL Reporting services with Amazon RDS?
What I have tried:
I attempted to spin up another EC2 instance, install "SQL Server Express with Advanced Services", and point SSRS to RDS, but it said that I had incompatible license types.
I plan on contacting the AWS team directly for this as well, but I thought that I would reach out to SO first to see if anyone has run into this. Thanks.
You might need to use a certain Microsoft-created "Amazon Machine Image", specifically the "SQL Server Optimized" AMI: Microsoft AMIs.
Another option would be to apply SQL Server SSRS containers, hosted on an EC2 VM, connected to RDS. There's a blog on Windocks.com that outlines steps to deliver configured containers for improved scalability (multiple SSRS containers), with simplified management.
I have successfully ran SSRS in Docker containers on Windows ECS/2 VMs for a while and just today came across a fresh out of the oven announcement from Amazon on running SSRS natively on RDS: https://aws.amazon.com/about-aws/whats-new/2020/05/amazon-rds-for-sql-server-now-supports-sql-server-reporting-services/?nc1=h_ls
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