proxy gatewey

[merini]

Hello,

I install power bi and it works well, against the installation of the gatewey to update the data since ODBC does not work, I could not locate the probelemme? knowing that I work in a company and they use proxy !

I tried your problem solving methods related to the proxy and it still does not work! what do you suggest to me to configure the gateway?

,

Best Regards,

[MaximeLejeune]

Hello, my gateway does not work anymore when it worked very well, here are my error messages

1st message :

Failed to update gateway details. You may have to change the account under which the gateway runs.
Error updating gateway configuration.

2nd message :

Network connectivity is limited.

Check that network access is working properly. You may need to change the firewall and proxy configurations.

3rd message :

Network access to Azure Service Bus is limited.

Check that network access is working properly. You may need to change the firewall and proxy configurations.

4th message :

Failed to verify gateway connectivity. Common issues are described in https://go.microsoft.com/fwlink/?linkid=838272.
 
Here is the tree of procedure calls:
System.Net.Sockets.SocketException (0x80004005): The requested name is valid, but no data of the required type was found
    at System.Net.Dns.GetAddrInfo (String name)
    at System.Net.Dns.InternalGetHostByName (String hostName, Boolean includeIPv6)
    at System.Net.Dns.GetHostEntry (String hostNameOrAddress)
    at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.CheckDNSQuery ()
    at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck. <> c. <Run> b__5_0 ()
    at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.HealthCheckAction.Run (Func`1 checkMethod)

Afficher plus

Afficher moins

Suggérer une modification

Partager la traduction

Best regards

Envoyer

Annuler

Votre contribution sera utilisée pour améliorer la qualité de la traduction et pourra être suggérée aux utilisateurs (sans vous identifier)

Réessayer

Merci de votre contribution

Votre contribution profite à des millions d'utilisateurs de Traduction

EN SAVOIR PLUS

Échec de la vérification de la connectivité de la passerelle. Les problèmes courants sont décrits dans la page https://go.microsoft.com/fwlink/?linkid=838272. Voici l'arborescence des appels de procédure : System.Net.Sockets.SocketException (0x80004005): Le nom demandé est valide, mais aucune donnée du type requise n’a été trouvée at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.CheckDNSQuery() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.<>c.<Run>b__5_0() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.HealthCheckAction.Run(Func`1 checkMethod)

Traductions de Échec de la vérification de la connectivité de la passerelle. Les problèmes courants sont décrits dans la page https://go.microsoft.com/fwlink/?linkid=838272. Voici l'arborescence des appels de procédure : System.Net.Sockets.SocketException (0x80004005): Le nom demandé est valide, mais aucune donnée du type requise n’a été trouvée at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.CheckDNSQuery() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.<>c.<Run>b__5_0() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.HealthCheckAction.Run(Func`1 checkMethod)

Définitions de Échec de la vérification de la connectivité de la passerelle. Les problèmes courants sont décrits dans la page https://go.microsoft.com/fwlink/?linkid=838272. Voici l'arborescence des appels de procédure : System.Net.Sockets.SocketException (0x80004005): Le nom demandé est valide, mais aucune donnée du type requise n’a été trouvée at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.CheckDNSQuery() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.<>c.<Run>b__5_0() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.HealthCheckAction.Run(Func`1 checkMethod)

Exemples de Échec de la vérification de la connectivité de la passerelle. Les problèmes courants sont décrits dans la page https://go.microsoft.com/fwlink/?linkid=838272. Voici l'arborescence des appels de procédure : System.Net.Sockets.SocketException (0x80004005): Le nom demandé est valide, mais aucune donnée du type requise n’a été trouvée at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.CheckDNSQuery() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.<>c.<Run>b__5_0() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.HealthCheckAction.Run(Func`1 checkMethod)

Synonymes de Échec de la vérification de la connectivité de la passerelle. Les problèmes courants sont décrits dans la page https://go.microsoft.com/fwlink/?linkid=838272. Voici l'arborescence des appels de procédure : System.Net.Sockets.SocketException (0x80004005): Le nom demandé est valide, mais aucune donnée du type requise n’a été trouvée at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostEntry(String hostNameOrAddress) at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.CheckDNSQuery() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.<>c.<Run>b__5_0() at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.HealthCheckAction.Run(Func`1 checkMethod)

Voir aussi

[Anonymous]

@merini,

Could you please translate the above error message in English or share us installer log which is located at %localappdata%\Temp\On-premises_data_gateway_*.log.

Additionally, you can follow the guide in the article below to configure proxy settings for on-premises gateway.
https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-proxy/

Regards,
Lydia

[merini]

Hi,

You will find attached errors translated into English and the error report generate.

Regards,

Merini

First Message:

Check that network access is working properly. You may need to change the firewall and proxy configurations.

Seconde message:

Verify that "On-premises data gateway service" is running in the Services control panel

Third message :

Failed to verify gateway connectivity. Common issues are described in https://go.microsoft.com/fwlink/?linkid=838272.
 
Here is the tree of procedure calls:
System.Net.Sockets.SocketException (0x80004005): The requested name is valid, but no data of the required type was found
    at System.Net.Dns.GetAddrInfo (String name)
    at System.Net.Dns.InternalGetHostByName (String hostName, Boolean includeIPv6)
    at System.Net.Dns.GetHostEntry (String hostNameOrAddress)
    to Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck.CheckDNSQuery ()
    to Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.NetworkCheck. <> c. <Run> b__5_0 ()
    to Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.HealthCheck.HealthCheckAction.Run (Func`1 checkMethod)

[Anonymous]

@merini,

1. Configure Proxy following the guide in this article.
2. Add relevant ports in your firewall.
3. Right-click the setup.exe and choose "Run as administrator" to start it.

If you still fail to install gateway, please share us installer log. You can upload the log to OneDrive and post shared link of the log file.

Regards,
Lydia