I have created a report using SSRS when the report is publish to the SSAS server (Different than DB Server), and I am trying to access the report I got strange error.
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DD_BE'. (rsErrorOpeningConnection)
Login failed for user 'NT AUTHORITY\ANONYMOUS
then i go back to check the data source connection.
i set the credential is to use windows authentication (integrated).
here the connection in Data tool is fine
every thing seems fine here then I go to check SSRS Manager to check Data Source.
And I changed the credential and I got different error.
Check the option Use as Windows credentials when connecting to the data source.
Related
We are trying to implement RLS on SSRS reports so that the user viewing the reports gets to see only records he is permitted to.
For this purpose we are required to use the following settings while connecting to the data source (that is an SQL-server DB), with impersonation enabled:
When the checkbox is unchecked, the database connects normally and all reports utilizing the source are working normally.
However, when we try to enable impersonation and try to connect, it hits with the following error:
You can try the following settings. If you want to use user credentials to connect the data Source.
In Other ways you can change the "Type of credentials to SQL Server if you want to Users to use SQL Server Authentication.
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
I am trying to create an Android Mobile app via the Azure app service and while doing so, I am trying to create a database, but I am getting the error 'there was an error while creating data connection 'SQL data connection'. Deployment to resource group failed'. Please help as soon as possible.
$
This error is due to server limit exceeding the quote associated with your account. Under all resources, check if there's a new SQL server created with a random name- you will need to delete that. Attempt to create again.
(just done- it worked!)
I've faced the exact issue.
First time it failed giving the error - Data Connection Creation Error..!
When Configuring for the first time it didn't work for me.
i.e.,
Creating a Database
Creating a New Server
Entering Server Admin Login
Entering Server Admin Password
I've noted down all the above information.
Tried Second time setting up the Connection String with the above details IT WORKED.
Hope this information helps.
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
why this error comes?
I am using windows authentication. But i am getting error
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
can any one help me in this how to solve this problem?
Most likely it means you're trying to connect from an impersonated context and you did not set up constrained delegation. See Manage Kerberos Authentication Issues in a Reporting Services Environment for details and troubleshooting.
First of all, I always prefer to use the 'impersonation' settings in the ISS configuration that do not set the user/password in the web.config. Everything was fine in the QA environment, but then I passed to the production environment and some options of the web site in production started to show the 'Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON' error.
The issue was that I copied the web-site configuration from the QA server, using the 'Save configuration to a file' option in IIS6 while creating a brand new Application Pool in the production server.
After several hours trying to solve this error, I just deleted the Application Pool, and used the 'Save configuration to a file' option to copy the Application Pool configuration and then restored it to the new server.
If you copy the web-site configuration, also copy the Application Pool configuration. That solved my problem, without changing anything about the authentication method, the database or the web-site itself.
Reporting Setup:
I had a report accessing datasource A, with a subreport which accessed datasource B.
The report connections were set to use Integrated Security.
From my development machine:
The "main" report would run perfectly fine from my development environment (as it was running everything as me.)
From the server:
I was able to execute the subreport directly, with no problem.
The main report would run, with the text "Error: Subreport could not be shown."
Actual Problem:
The subreport was executing under the NTAUTH\ANON user, because it was the Reporting Services code which was calling the sub-report. This error was in the SSRS Logs:
System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Solution:
Set up the sub-report data connection to execute using a SQL User login.
Only grant that user execute on the particular procedure you're calling for the report.
This allowed me to get the report working without involving other departments that controlled the application servers (modifying web.configs or IIS configurations)