I am using Azure Database for MySQL with the following configuration as the data source on a PowerBI report
Firewall Rules: Allow access to Azure services
SSL Settings: Enforce SSL connection is set to disabled
PowerBI Desktop is able to connect to the database.
I then publish the report. Go to app.powerbi.com/home and refresh the dataset.
I get the error Refresh failed due to gateway configuration issues
I do not have any gateways configured given that the database is on Azure
Any tips/guidance would be appreciated.
Some details from the error message and connection to db
Refresh failed due to gateway configuration issues.
This dataset requires a properly configured gateway in order to refresh.
If you're using personal mode, please make sure your gateway is online.
If you're using enterprise mode, please make sure you've added the following data sources in the Gateway Management PortalMySql { server : "XYZ.mysql.database.azure.com" , database : "SOMEDB" }
Please try again later or contact support.
Related
I have a dashboard built with PowerBI Desktop. This dashboard has 3 differents data sources (SQL Server, CSV and API). I have a PRO account.
Everything works fine, but when I want to connect it with my gateway after pubication, it raise me an error for SQL Server connection:
Sorry, it's in french, but it says "Cannot update this datasource credentials. Unknown error"...
What I tried so far:
Fully reconfigure the gateway
Tryed to connect with different credentials
Updated datasources authentification methods (from desktop) and
publish it again
Publish my dashboard on different workspace
Of course, my credentials works fine in my SQL Server
I run out of idea... and I really need to setup this in order to make scheduled refresh.
I have a subsidiary question: there is any good practice about credentials to use right here? It is better to use a service account or personal account for this kind of connection ?
Many thank's for your help.
I am not able to connect to my aws-rds instance from asp.net application
I have been trying to connect my asp.net application with my aws-rds instance i have tried using connection strings setting, its doesn't work, but i am also able to connect to my aws-rds database from sql management studio
i also tried to use migration but when i do update-database from console it create a new database in local db
i have also try to provide all required setting and data and then publish my application with aws toolkit but when opening my site link it gives a error -An error occurred while processing your request.
so any can help me with this issue or provide me the proper steps
Check Inbound and outbound rules for instance.
try to connect it with your instance IP.
refer enter link description here
I try to configure Reporting Server without selecting SSL Certificate for MS SQL Server. Can any body tell me that is that possible to deploy SSRS Report for testing purpose if I dont have SSL Certificate information. Because I am getting below error!
"The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)"
.
Thanks in advance.
You can remove a certificate if one is applied to the service endpoint.
Open Reporing Service Configuration Manager.
under the targeted ssrs instance, navigate to the "Web Sercvices Url".
Make sure the SSL certificate is set to
Save the settings.
Also, make sure the database configured under the "Database" node is accesible from your SSRS instance.
Make sure the database is configured correctly in reporting services configuration manager.
If you updated the service account after the installation you probably want to use SQL Server Configuration Manager to update the account as it also sets the required permissions.
Regarding the SSL - reporting services encrypts the database using this certificate. as long as you are not importing the database or recovering from backup you can use the autogenerated certificate and deploy your projects from SSMS.
I'm trying to figure out which credentials I should be storing to enable use of Reporting Services' Data-Driven Subscriptions. Nothing I type in seems to work. It's all happening on localhost under XP-Pro SP3.
A little background:
I'm able to connect to the localhost server as a Database Engine in SQL Server Management Studio, using either Windows Authentication or the username 'sa' and a given password. However, trying to connect to localhost as a Reporting Services server using those same credentials fails with this error:
Cannot connect to localhost.
Additional information:
Unable to connect to the remote server (Microsoft.SqlServer.Management.UI.RSClient)
No connection could be made because the target machine actively refused it [IP]:80
In Reporting Services Configuration Manager, Windows Service Identity is set up like this:
Service Name: ReportServer
Service Account: LocalSystem
Built-in Account: Local System
Web Service Identity is set up like this:
ASP .NET Service Account: [Machine]\ASPNET
Database Connection:
Server Name: [Machine]
Database Name: ReportServer
Database Version: C.0.8.54
Server Mode: Native
Credentials Type: Service Credentials
The Service Status page is green and running.
The Report Server webpage is available and accessible; I can view and generate reports manually. However, I want to create a Data-Driven Subscription so that I can create multiple reports in one go. This is where I'm running into problems. When I click "Subscriptions", it refuses to let me set one up because
Data-driven subscriptions cannot be created because the credentials used to run the report are not stored, the report is using user-defined parameters values, or if a linked report, the link is no longer valid.
Fair enough, I haven't stored credentials. So I went to the "Properties" section and clicked "Data Sources". By default, the report uses "A shared data source". Switching to "A custom data source" requires me to select credential types. Nothing I enter into this seems to produce a result that will allow me to get past the "Data-driven subscriptions cannot be created..." message and create the subscription.
Anyone know how I can fix this?
That error with subscriptions implies that at least one of the data sources you're using (either for your report or for the subscription data) doesn't have stored credentials.
For example, normally I might be using Windows Integrated Security to connect to a data source, but if I want to store the credentials, I will enter MyDomain\SomeAccount and its Windows password in the box on the Data Source screen, and tick the checkbox to indicate it's Windows security.
If this is done for all the data sources, then you should be able to create a subscription. You don't need to use a custom data source if you're happy to store credentials in the shared data source.
I think you need to store credentials for the data source as well as for the execution account in the SSRS Configuration tool, especially if you're using Local System. Rob is correct about how to set the credentials for the data source, just modify the shared data source directly.
I am trying to run a SQL Server Reporting Services where the data for the report is on a SQL Server database that's on a different server. Integrated Authentication is turned on for both the Report Server and the report. I have confirmed that Kerberos delegation is working fine by using Internet Explorer to run the report from inside the network.
However, when I open the report server through the firewall, I cannot run the report. I get the following error: An error has occurred during report processing. Cannot create a connection to data source 'frattoxppro2'. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Does Kerberos authentication not work outside a firewall?
Kerberos requires a port 88 connection to the KDC, in this case, most likely your DC.
What you probably want to look at is HTTPS + Basic Authentication + Protocol Transition to take the Basic Authentication and translate it into a DC based Kerberos Ticket for delegation and back end authentication.
Protocol Transition with
Constrained Delegation Technical
Supplement
How To: Use Protocol Transition and
Constrained Delegation in
ASP.NET
Not exactly the easiest to set up, but when its working, it works amazingly well.
I'm not really in a position to tell you why kerberos isn't working for you, but did have a alternative suggestion for your configuration. You can use ISA services to expose the reporting server rather than simply poking a hole in your firewall. This is something our company has done successfully - it republishes the reporting services site so the browsers are talking to ISA, not directly to the server. ISA Services is quite happy to pass through your credentials as well.