I'm trying to develop a custom authentication for Power BI Report Server and followed the following guide:
https://github.com/Microsoft/Reporting-Services/tree/master/CustomSecuritySample
It's OK. I can authenticate my own way, creating a kind of Single Sign On application. Although, I'm getting an error when I try to save a report as a Power BI Report Server on Power BI Desktop. I get Unexpected Error Encountered.
Does anyone know if this is really a problem with my authentication? In other server, same config, without Custom Authentication, everything works fine.
EDIT:
This is the error I get
I did face similar issue, was unable to publish the Power BI reports to report server and was getting same error message "Unexpected Error Encountered"
To resolve this issue you launch your "Report Server Configuration Manager" on server where you have configured Power Bi Report server, and go to tab "Web Portal URL". The url which has been configured; copy it and go to your Power BI Desktop version -> go to File -> SaveAs -> Power Bi Report Server -> Paste the url in New report server address text box which you have copied.
sample url - http://IPaddress/ReportsPower or http://fqdn/ReportsPower
Click on OK button.
It will list you all the reports which are already available or if it fresh report then would show blank and would get Success message.
Please note that I have tried this on Power BI Desktop version - Version: 2.81.5831.1181 64-bit (May 2020)
Add your powerbi credential in credential manager under windows credential with power BI server URL.enter image description here
I think this resolve your problem.
I have resolved this issue with this way.
Thanks
BennyRaja.A
First of all add your server's IP/DomainName only (like 1.1.1.1 or example.com) in Windows credentials manager along with username and password, See the screenshot 1
Secondly click on file=>Save As=> Report Server give full address of report server like http://example.com/reports, See the screenshot 2
Related
We are trying to pull data from Sharepoint site using SSIS ODataSource Connection Manager. But, we are facing issue with the ODataSource which is failing when we are trying to test the connection. It is giving below error message, even though the password we are giving is correct. We are using Microsoft Online Services as Authentication Type.
TITLE: OData Connection Manager Editor
Test connection failed
The sign-in name or password does not match one in the Microsoft
account system.
(Microsoft.SqlServer.IntegrationServices.ODataConnectionManager)
We are using SSDT Version 2017. Here is the screenshot for your reference.
Can you please let us know, what would be the issue and how to fix this.
Thanks in Advance!!
I have Report Builder 3.0 installed on my local PC. I am creating a new report and adding an embedded data source to a SQL Server Analysis Services database.
When I build the connection string of the data source, choosing the server name and the database name, I click 'Test Connection' and receive a message saying "Test connection succeeded". So far, so good.
I close the connection properties with the OK button, and on the Data Source Properties window I click the 'Test Connection' button. This time I get an error saying "The connection either timed out or was lost".
If I ignore the error then I can successfully add a dataset to my report and add data from the dataset in to the report design, but when I try to run the report (on my local PC) I again get an error connecting to the data source.
My best guess is that the connection that succeeded is running under my credentials, whereas the connection that fails is running as some other credential and so needs to use Kerberos delegation to pass my credentials along, but that is only a guess and even if I am correct I am at a loss to understand how to fix the issue - I don't know what other credentials may be being used and I have already set SPN's for the Analysis Services service account.
So it turns out that it was a Kerberos issue as I suspected, and I was also correct that Report Builder was testing the connection using some process running under another authentication context.
It turns out that when setting up Report Builder (and I had forgotten it) that you specify a default SSRS Report Server (see screenshot). It must be that when testing data sources or running reports that it connects to that default Report Server and does the work from there - I was assuming that everything was running locally!
Once I figured that out it was just a case of finding a good guide on how to configure SSRS for Kerberos and everything started working. In my case the only bit that I hadn't already done was to add the <RSWindowsNegotiate/> setting to the AuthenticationTypes in the rsreportserver.config file
I'm trying to connect to a SSRS 2012 Report Manager on a Win Server 2012 server.
I'm getting "The website cannot display the page" error. Can't figure out why.
I've tried the following things:
Browsing either to the computer's name url and either to the computer's network ip address
Changing the service login type.
Running IE as Administrator
I can connect to the Web Service and I can view reports through it.
I'm connecting with a Domain Admin account.
Would appreciate any help. Thank you.
Ok. The answer was indeed detected in the Windows Event Log. Thanks.
Adding the SSRS host as a trusted site in the browser fixed this for me.
I'm working on Java Pos and I'm a newbie. I need (kettle) Pentaho Data Integration in order to integrate the Java POS' database with the database in the ERP. I followed the following manual
"http://www.scribd.com/doc/19583351/Install-Guide-for-Pentaho-Business-Intelligence-BI-Suite-CE"
and I'm stuck at Part 3- Step 1. When I type localhost address in the browser, instead of getting pentaho login page i'm getting a "HTTP Status 404" error.
Do I've to change the tomcat server port or anything else? Please, help me find out the glitch in this program?
Check your server.xml to see what port is listening on. I assume when you started tomcat it started successfully? ( check the log for errors )
Use google.
Finally, if you want to use ETL/Kettle then you need to start off looking at the Spoon tool - this is the UI for building ETL. So look at that first perhaps.
(you dotn even need the BI server if all you're doing is ETL.)
I am having an issue embedding my report into an aspx page.
Here's my setup:
1 Server running SQL Server 2005 and SQL Server 2005 Reporting Services
1 Workstation running XP and VS 2005
The server is not on a domain.
Reporting Services is a default installation.
I have one report called TestMe in a folder called TestReports using a shared datasource.
If I view the report in Report Manager, it renders fine. If I view the report using the http ://myserver/reportserver url it renders fine. If I view the report using the http ://myserver/reportserver?/TestReports/TestMe it renders fine. If I try to view the report using http ://myserver/reportserver/TestReports/TestMe, it just goes to the folder navigation page of the home directory.
My web application is impersonating somebody specific to get around the server not being on a domain. When I call the report from the report viewer using http ://myserver/reportserver as the server and /TestReports/TestMe as the path I get this error:
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.
When I change the server to http ://myserver/reportserver? I get this error when I run the report:
Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.
I have been searching for a while and haven't found anything that fixes my issue. Please let me know if there is more information needed.
Thanks in advance,
Kendra
There are two virtual directories of interest with SSRS.
http://myserver/reportserver is where the web services are.
http://myserver/reports is where the Report Manager interface is.
http ://myserver/reportserver?/TestReports/TestMe works because you're going to the web services and passing in a parameter of the 'address' of the report you want. Notice the ? in there, indicating that the rest is a querystring parameter
http ://myserver/reportserver/TestReports/TestMe is trying to go a subdirectory of the virtual directory, which doesn't really exist.
To get your system working using anonymous access, you'll need to tell IIS to be running your website's application pool as a known user, which has sufficient permission to view the report. You can set this up in Report Manager (http://myserver/reports).
See how you go - good luck.