I am facing issues while connecting Reporting Services using Report Builder desktop application from client.
My Environment:
SQL Server Reporting Services 2016
Report builder Latest based on clickonce from client machines
SQL Server Analysis Services Tabular Mode 2016 -
Both my SSRS and Analysis services cube are on same Windows server 2012
Authentication type : CUSTOM
Scenario:
I have enabled Custom Authentication on Reporting Services using CustomAuthentication code. Custom Authentication works fine to connect Report Server. I have role based security setup in Analysis Services 2016 and for custom Authentication Row Level Security is working fine based on CUSTOMDATA parameter.
Now I require Report builder to connect my Reporting Services to do report authoring. In this scenario Report builder successfully does custom authentication and connects to report server but during Data Source connection It again tries to connect SSAS cube from client and it fails. I followed steps in configuring Report Builder access as here: https://learn.microsoft.com/en-us/sql/reporting-services/report-server/configure-report-builder-access
Any help in this regard will be great.
Report authoring with ReportBuilder requires a direct connection from the ReportBuilder client to the data source. See eg
https://blogs.msdn.microsoft.com/psssql/2009/12/03/report-builder-and-firewalls/
Related
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).
We have installed SQL Server 2014 on a web server. And we have connected to the SSRS Reporting Services, but we don't see any options (like import report) to upload into the reporting services.
Can anyone plase guide on this one how to get/upload report the reporting services?
You need to go to the Report Manager portal (e.g. http://yourserver/Reports)
and once you're there and you have the appropriate permissions, there will be an Upload File button.
You should see something like this:
You can also deploy a reports project to the server rather than uploading each one, directly from SQL Server Data Tools
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:
I have an SSRS report that connects to an cube using a shared SSAS data source with integrated security. In visual studio the report works fine and connects successfully. Once I deploy it to the report server (sharepoint 2013 integrated/sql 2012) then it won't work and gives an access denied error.
My user is an admin on the SSAS instance so security is not the issue. Can connect fine with ssrs in visual studio, excel, ssms. Only once the report is deployed and run in sharepoint it doesn't work. Similar error if I go to the data source in sharepoint and try to test the connection.
I believe the problem was that even though my user had permissions. Using integrated security causes a double hop problem (computer ->report server -> db server) in order to authenticate. By using stored credentials on the report server is solves the double hop problem (report server -> db server).
In one of the ASP .Net site we are currently working we have a bulk load of SSRS reports. We have forms authentication for the site and reports have already been created and deployed in the report server. We are having so many problems with authentication when we set the report viewer control to access the server report.
I just want to know what are the advantages or disadvantages of using Local report vs Server Report
Thanks,
Raja
1- client report don't need to report server for rendering. (advantage)
2- you must make a server report by creating a report server project in BIDS but client reports must create in VS.
3- server reports use stored procedure or text script as data provider but client reports use dataset or xml datasource for this.
4- server reports use report server for rendering of the report but for client reports this work done at report viewer control.
5- client reports don't need SSRS installation but server reports need that.
6- for working with server reports you must deploy reports but in client reports you don't need this work.
7- for enterprise projects, it is better that you use server report but in other projects client reports are better.