06-06-2017 03:28 PM
Thanks. I went to the URL and found the link to download the gateway. The URL was the updated article in Power BI documentation.
I installed and am getting exactly the same error. I'll send logs. The gateway version looks like the same as the version I downloaded and installed yesterday 14.16.6349.1
06-07-2017 09:03 AM
I reverted back to the previous version of the gateway provided by Dimah late yesterday afternoon. I was able to get the SQL data source to take the credentials in Basic mode and all of the reports using that data source successfully refreshed last night.
So, there is definitely a problem with the latest version of the gateway with SQL Server 2008 sources using Basic authentication mode.
Thanks for all the help yesterday and I'm looking forward to the fixed version of the latest gateway.
06-08-2017 12:18 AM
Thanks for sharing your question. But I didn't encounter above issue with the latest on-premises data gateway (personal mode) installed on my local machine, also using basic authentication.
I would suggest you create a support ticket so that you can get more help about how to fix your problem. https://powerbi.microsoft.com/en-us/support/
06-08-2017 08:46 AM
I have been working with on this issue. I am able to connect to other SQL databases with the latest PGW using Windows mode. I think the problem may have something to do with the fact that the SQL db I am connecting to that fails with Basic mode authentication does not support encryption. I get the following message when first connecting to this source using Power BI desktop using Basic authentication.
Speculation on my part, but it's the only thing I can see that might be pertinent to the issue.
06-08-2017 02:26 PM
I found that I always got that when connecting to a SQL Server, it appears to always try and connect securely to SQL Server, and when that fails you get the prompt as shown below.
And in the past that did not cause any issues when doing that either.
06-09-2017 08:55 AM
I have been working with a Microsoft engineer on this problem and the root cause appears to be that the SQL Server database name is somehow being used by the Power BI service as lower case. The database name in our SQL 2008 server is case sensitive and contains upper case letters, so the connection fails when the Power BI service uses lower case with the latest version of the personal gateway. As I noted in previous posts, this problem did not happen with the previous version of the personal gateway or On-prem gateway.
Suggested workarounds from Microsoft are to turn off case sensitivity in our SQL 2008 server, or for me to delete all of my datasets and reupload making sure only the SQL 2008 data sources with correct database names are uploaded. Be assured that the later case will not happen as it would take me weeks to rebuild dashboards and report shares. I have not yet talked to our IT people, but I don't think disabling case sensitivity is a good idea either. Plus, there is no guarantee either of these workarounds will work.
I believe this issues needs to remain an open ticket for Microsoft to fix. It's not reasonable to ask users to change their working datasets just because the personal gateway or On-prem gateway has been changed. The Power BI team has been regularly delivering great features and doing a great job of supporting us users. The responsivness from Microsoft on this issue was excellent and Power BI is one of the best products Microsoft has released in years. Please keep us happy and get this problem fixed ASAP.
I'd be happy to discuss this in person next week at the Data Insights Summit, just let me know.
06-11-2017 08:02 PM
Thanks for sharing your question and the root cause for this problem. According to your response, we know that the SQL Server database name is somehow being used by the Power BI service as lower case with the latest version of the personal gateway, issue occurs when the database name is set to case sensitive. This will be a great notice to other users so that they can take care of this behavior when using the latest gateway. Besides, as you have submitted this issue to Microsoft, our product team will consider fixing it in later release. Appreciate for your patience.