On-premises data gateway - Network Request Returned Unexpected Error

I ran the following line in cmd prompt: netsh winhttp show proxy

and got: Direct Access <no proxy server>.

The first time I installed this gateway on the server, I had no issues. The latest version also installs perfectly fine without issue on my company laptop. I didn't have to adjust anything except the services account to an account on the domain. 

I feel like I may be going down the rabbit hole here. Is there something blatantly obvious I'm missing? I've also added just about every microsoft site to the list of trusted sites in internet explorer. 

"rabbit hole" doesn't even begin to describe the gateway setup and maintenance story, especially in an actual enterprise environment (Hard to believe that you are working without proxy, but so be it). 

Anyway, look at the gateway logs  (in appdata under the pbigwservice account) and work on the issues in there one by one.  Try accessing the Azure Service Bus servers via trace route, look at any restrictions on port 443 etc.

Keep posting your error messages. There are many more options for things to go wrong.

I re-installed an April 2020 version. It seems to get my further along. When it asked me to provide my email address to login to the gateway, it accepts it and then prompts me to select my azure ad account. I select it and then normally it would bring me to my company's organizational sign in page but for whatever reason it does not and it errors out. It's almost like it's trying to pop up but it closes out automatically before I can even see it. I thought it was related to internet explorer pop ups but i have pop ups allowed. Here is the error now:

Starting trace on 8/15/2020 8:16:10 PM UTC
Version: 3000.31.3
UserDomainName: 
UserName: 
MachineName: 


EnterpriseGatewayConfigurator.exe Information: 0 : Initialize EnterpriseGatewayMainViewModel
EnterpriseGatewayConfigurator.exe Information: 0 : GetConfiguratorStateAsync
EnterpriseGatewayConfigurator.exe Information: 0 : Value SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client is not defined in registry.
EnterpriseGatewayConfigurator.exe Information: 0 : Value SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client is not defined in registry.
EnterpriseGatewayConfigurator.exe Information: 0 : Found SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client/Enabled data in registry, value: 1.
EnterpriseGatewayConfigurator.exe Information: 0 : Found SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client/DisabledByDefault data in registry, value: 0.
EnterpriseGatewayConfigurator.exe Information: 0 : Value SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client is not defined in registry.
EnterpriseGatewayConfigurator.exe Information: 0 : Value SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client is not defined in registry.
EnterpriseGatewayConfigurator.exe Information: 0 : Value SOFTWARE\Microsoft\.NETFramework\v4.0.30319 is not defined in registry.
EnterpriseGatewayConfigurator.exe Information: 0 : Value SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319 is not defined in registry.
EnterpriseGatewayConfigurator.exe Information: 0 : Configuration client returned null
EnterpriseGatewayConfigurator.exe Information: 0 : Sign In
EnterpriseGatewayConfigurator.exe Warning: 0 : Cannot access default endpoint https://api.powerbi.com and start to use fallback endpoints. Exception: System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 20.42.6.2:443
   at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
   at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.GatewayCommon.ConfiguratorClientExtensions.<DiscoverEmailProperties>d__8.MoveNext()
   --- End of inner exception stack trace ---

Also when I check the gateway logs on my laptop running July 2020, it says TLS 1.2 Client is not defined in the registry. Not sure adding those registry keys to the server were necessary since my laptop doesn't have them and it works great.

A few months ago, I enabled IIS. I wonder if that has anything to do with it...

Another interestig point, when I try navigating to https://api.powerbi.com i get "This page cannot be displayed" but when I try to navigate to the website on my laptop, with the working gateway, I get HTTP403: 
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.

I select it and then normally it would bring me to my company's organizational sign in page but for whatever reason it does not and it errors out. It's almost like it's trying to pop up but it closes out automatically before I can even see it.

That sounds awfully familiar.  in my case some of the trusted root certificates mysteriously went missing from my gateway cluster members. I had to manually re-add the certificates to the trusted root certificate store.

when I try navigating to https://api.powerbi.com i get "This page cannot be displayed"

As I mentioned earlier - this is what you need to work on.  Something on the machine or in your network is preventing the traffic from reaching that site.  Did you disable the Windows Firewall (or poke a hole in it for 443 outbound)?

Yes the firewall is disabled.

Use Fiddler to see where the requests are stuck.  or ask your network friends for help.

A co-worker figured out it was a proxy issue (only took him a few hours). If it wasn't for him, I'd still be working on it......

Network Proxy Settings > Script address

Script address needed to be configured. Why this changed all of a sudden, I have no idea. I'm told it may have been some kind of update recently. I'm just glad it's figured out.