Forum Discussion

PowerBI_GovUser's avatar
PowerBI_GovUser
New Member
5 years ago

Onprem data gateway error while signing in

Have a Windows 2012 Standard R2 and IIS shows upto 4.5 ( in features / roles ).

I installed 4.8 runtime and developer ( both do not work ) and give me this error whenever i try to start the "onprem" gateway.

The server was also restarted. 

 

Network request returned unexpected error.

Authentication failed because the remote party has closed the transport stream.

   at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)

   at System.Net.PooledStream.EndWrite(IAsyncResult asyncResult)

   at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)

 

 

Need Help

4 Replies

  • GilbertQ's avatar
    GilbertQ
    Icon for Super User rankSuper User
    5 years ago

    Hi PowerBI_GovUser 

     

    That error appears to be because the server cannot connect to the Power BI Service. Have you tried to connect via the HTTPS mode?

     

     

  • PowerBI_GovUser's avatar
    PowerBI_GovUser
    New Member
    5 years ago

    Thanks for the reply. The onprem data gateway software does not load for me to change to https. As soon as i enter my login for power b.i as the "Sign in", i get the error. 

  • PowerBI_GovUser's avatar
    PowerBI_GovUser
    New Member
    5 years ago

    Don't know if this helps but the personal mode of data gateway runs fine from my laptop with my "sign in". So i know that it works with my account from my local laptop to the service. Its just that there is some issue with connecting from the server with standard software. ( My next step would be to try the personal gateway on the server and check the error ? )

  • v-xiaotang's avatar
    v-xiaotang
    Icon for Community Support rankCommunity Support
    5 years ago

    Hi PowerBI_GovUser 

    Have you solved this problem?

    -

    It is most likely caused by your application's default security protocol type being set too low.

    A lot of external APIs now expect requests using TLS 1.2 or above.

    You can easily set the SecurityProtocol in your application by adding this line:

    ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls;

    This can be added just before you call the api, or it can even be added in the application start method. 

    If you don't have all of these options available to you, maybe you are running a .NET 4.0 application, you can also set it like this:

    ServicePointManager.SecurityProtocol = (SecurityProtocolType)48 | (SecurityProtocolType)192 |
(SecurityProtocolType)768 | (SecurityProtocolType)3072;

    You also don't have to include them all, you can take out the ones you don't need.

    FYI:

    https://blogs.perficient.com/2016/04/28/tls-1-2-and-net-support/

     

    Best Regards,

    Community Support Team _Tang

    If this post helps, please consider Accept it as the solution to help the other members find it more quickly.