Forum Discussion
Advocate IIOn Premise Data Gateway - Can only connect to SQL Server if I open 1433 TCP In
I was able to fix the issue. For anyone else who may get confused if they have a similar setup.
I was connecting to my SQL Server VM by IP Address. When the Enterprise Gateway took over in production, it was decrypting the connection credentials and trying to connect, the connection would fail as it was trying to connect to SQL server via it's own external IP address, which wouldn't work.
If I changed the conn string to (local) or 127.0.0.1 it works straight away. The way I will move forwards is to setup a dns entry like sql1.mydomain.com so that I can develop the reports locally. I will then setup a hosts file entry on the SQL Server VM to point sql1.mydomain.com > 127.0.0.1 so it will work in production too.
Advocate III was able to fix the issue. For anyone else who may get confused if they have a similar setup.
I was connecting to my SQL Server VM by IP Address. When the Enterprise Gateway took over in production, it was decrypting the connection credentials and trying to connect, the connection would fail as it was trying to connect to SQL server via it's own external IP address, which wouldn't work.
If I changed the conn string to (local) or 127.0.0.1 it works straight away. The way I will move forwards is to setup a dns entry like sql1.mydomain.com so that I can develop the reports locally. I will then setup a hosts file entry on the SQL Server VM to point sql1.mydomain.com > 127.0.0.1 so it will work in production too.