If you have a different machine that has Management Studio installed, use that! If that works, then we may want to do the test specifically from the gateway machine. To start, it doesn’t necessarily have to be the same machine as the gateway. Because it is SQL Server, I’d really like to try Management Studio. How do we do that? You can use the same test that you used locally! Use something like a UDL file or another tool to see if it can connect. This helps to exclude a lot of potential complexity. Or, if you had a custom application, let’s remove that from the picture. This is why I like to remove the gateway from the picture. Maybe you start to think something on the Power BI side is broken, or maybe we can’t talk to the Azure Service Bus. You may know that locally works and remote does and start looking at why the gateway specifically isn’t working. I want to simplify this and get the gateway out of the picture.Ī lot of times we can become fixated on the app we are looking at and ignore other possibilities. We know that the problem is remote applications being unable to connect to SQL Server. I can’t list all of the possible problems here, just know that there are usually more than one reason that something could be not working. Meaning that SQL Server isn’t listening on that network. Maybe the machine is multi-homed (multiple NICs) and the remote machine is on a network that isn’t bound to the SQL Server. This would only allow local connectivity. It could be other issues as well, such as TCP and Named Pipes being disabled for the SQL Server and only allowing Shared Memory. That comes from 10+ years of experience troubleshooting connectivity problems. My gut is telling me that this is a Windows firewall issue. This means that had we installed the gateway locally there probably wouldn’t be any issue and it would just work. In our example, we are going to say that local connectivity is successful. This also means there is something stopping remote connections. If the connection works, then we know the data source, SQL Server in our example, is online and can accept at least local connections. Just make sure you do it on the actual machine the data source resides on. You can create a DSN and test the connection as part of that DSN. You could also use the ODBC manager if you have an ODBC Driver installed on the machine. For SQL Server, that would be Management Studio. You can also use the tools that ship with the data source. You could use a Universal Data Link (UDL) file. There are different ways that you can test local connectivity. In our example, the gateway is on a different machine from the SQL Server, so it is remote. If you have something that is remote to the data source, you are going to want to try it locally first.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |