Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
Out of the hundreds of SQL server connections that we have created so far one stands out by its weirdness. In Power Query I can enter the server name, and get the list of databases. I select the database and get the list of tables. I select the table content and get - nothing. Nothing but waiting forever.
Now, this does not happen on the Power BI Desktop of the user. It happens on the VM that runs the gateway. Consequently, any refresh attempt on the service also fails because the gateway says "Cannot connect to source undefined".
If the user sets up a gateway on their PC everything works as it should. Gateway on the VM - not working.
Again, this is the only connection out of hundreds that behaves like this. Is it maybe a setting on that particular SQL server that prevents connections from some network locations? But why does it serve up the meta data?
@lbendlin - That's a strange one. It certainly smells suspiciously like some kind of odd network thing going on. Perhaps try to see what Fiddler says?
Fiddler is mostly useless as we need to use our own proxy to do anything in the network. But it looks like the SQL server is woefully unprepared for any serious work - it freezes up when given too many queries at once. Have advised the users to find a better server.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 7 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 10 | |
| 7 | |
| 6 |