Forum Discussion
Certifiticate problem w enterprise gateway import mode, when direct mode works ok
I found the link within the refresh history on the gateway to be helpful. https://msdn.microsoft.com/en-us/library/ex6y04yf%28V=VS.110%29.aspx?f=255&MSPPError=-2147217396
In short, I was using the server shortname but the cert had the FQDN. So i used the FQDN in the connection so that the connection string matches the cert. Was a very simple fix.
I found the link within the refresh history on the gateway to be helpful. https://msdn.microsoft.com/en-us/library/ex6y04yf%28V=VS.110%29.aspx?f=255&MSPPError=-2147217396
In short, I was using the server shortname but the cert had the FQDN. So i used the FQDN in the connection so that the connection string matches the cert. Was a very simple fix.
That was it and as said, very simple fix.
For some reason the unmatching connection string was working ok in the direct query, but that does not matter.
I'm having the same issue, exept I am using the FQDN in the connection string. But I still get the same error message. No reply from PowerBI support yet despite rasing a ticket.
The above link does not give me information on how to determine the FDQN, or at least I am missing or not able to understand how to get it. Is there somewhere on the SQL server that can identify this?
You can obtain your FQDN by typing the following into PowerShell:
[System.Net.Dns]::GetHostByName(($env:computerName))
If you run that from the SQL server host, it will give the FQDN.
Thank you. I was able to find the FQDN (assuming it is the HostName) - I have entered this as my server but I am now getting an error that it is unable to connect "cannot connect to the server". Again it works fine when using direct query, just not on import. looks like you were having the same issue, did you find resolution?
