We are running a local PowerBI report server. It displays PowerBI reports just fine. I wanted to add a datasource to it so that we can also use it for SSRS reporting. Everytime we attempt to create a datasource, it throws this error:
Microsoft.SqlServer.ReportingServices2010.RSConnection2010+MissingEndpointException: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. --->
The backend SQL database is 2019.
Any ideas?
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).
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).
I am configuring SSRS 2012 on my system. It gives an option to select/create a report server database. If I am selecting "choose an existing report server database" and selecting the database I am using for my application, I get an error "The database you selected is not a report server database...."
Why can't I use my existing database for reporting service? What are the correct steps to configure SSRS and using my existing database for creating reports?
The database SSRS is asking for is not the database where you have data for reports, but the database where SSRS configuration and temporary datas stays.
These are the default ones:
If you do not have those 2 databases, let the setup create them for you.
You will create Data Sources to your database when you will create your first report.
You can't pick your own database for a report server database, the database it is referring to is the one for the reportserver application itself.
So you need to first create a report server database and link your report server to that, then the report server application will work, then inside this application you create a data source which points to your database with your data you want to report on, you can then start writing your reports.
Have a look here for more detailed steps:
Install Reporting Services Native Mode Report Server (SSRS)
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.
Details are as follows:
Environment:
SSRS 2008 Server, SQL Server 2008 for database, Report Developed in SQL Server Business Intelligence Devlopment Studio - Reporting Project
Error Messages:
"An error occurred during client rendering."
"An error has occurred during report processing."
"Query execution failed for dataset 'DataSource1'."
"For more information about this error navigate to the report server on the local server machine, or enable remote errors "
I have done that (navigation & all that) and the result was that a parameter of a scalar variable needs to be declared. The funny thing is that those variables are properly declared in the datasource and in the report sources everywhere. Also this report/datasource worked no problem on SSRS 2005. In the Development Environment the report runs perfectly. On the server the report only fails when executing and after the parameters have been accepted. We use no stored procedures.
Any help / ideas will be greatly appreciated.
Thanks in advance.
I experienced problems in SSRS 2005 where deploying changes to a report didn't properly update changes to parameters, in particular newly added parameters. The fix was to delete the existing report using Report Manager and then upload the modified version.
Hope this helps,
Bill
When you run in the Dev environment, you're using your windows credentials. Do you also use your windows credentials when you run through SSRS? or are you using different credentials?