Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi,
I created a report using a SQL Server data source with a SQL Statement (just a normal SQL query on one table, set in the advaced settings under 'SQL Statement') in Power BI Desktop. To connect to the server from Power BI Desktop I used the following server format: SERVER: PORT .
I tried to set up a Scheduled Refresh for the dataset. However, it states my gateway is 'Not configured correctly'. It does show the SQL server connection I'm using, but it's not able to connect. If I manually add the same SQL Server as a data source with the format: SERVER,PORT (note the comma, instead of the colon) it does connect to the SQL server.
I've tried to change the format to SERVER,PORT in my Power BI Desktop so it matches the format that is required by the gateway, but it doesn't connect. It shows me the error "The name provided is not a properly formed account name".
How is this possible? And can someone please provide me with a solution? Does it have something to do with the use of a SQL Statement?
Cheers,
Solved! Go to Solution.
@eppe2000,
We should use servername,port as server in Power BI Desktop to connect to SQL database, I can successfully connect to SQL using this format with SQL statement.
How about you open a new PBIX file, delete the existing SQL permissions and reconnect to SQL Server ?
Regards,
Lydia
@eppe2000,
We should use servername,port as server in Power BI Desktop to connect to SQL database, I can successfully connect to SQL using this format with SQL statement.
How about you open a new PBIX file, delete the existing SQL permissions and reconnect to SQL Server ?
Regards,
Lydia
Hello,
I have the exact same issue but the solution you provided does not work for me. I simply can not use the format "servername,port" to connect to an SQL Server Database in Power BI Desktop. And I can not use semicolon while creating the gateway, so I can not use the gateway to refresh the dataset of my report. Does your solution not work in new Power BI versions?
I was able to resolve the issue by assigning an alias to my "server,port" in SQL Server Management Studio on the same machine where I designed the report and created the gateway. This allowed me to use the alias as the server name in both Power BI Desktop and when creating the gateway connection, thus ensuring consistency and avoiding the previous issues with differing formats.
Deleting the existing permissions and reconnect to the SQL Server using a comma worked. Thanks!
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.