0 Kudos

Frequent SChannel Errors on server hosting Enterprise Gateway

Status: Delivered
by AnniePower Frequent Visitor on ‎04-20-2017 08:26 AM

We are noticing frequent SChannel Errors in the Event log on the machine that is running the enterprise gateway. The file in PBI will refresh anyways.  I'm guessing there is something else that the gateway requires, that isn't on the list of required items for the gateway.  This behavior was seen in our original testing environment, our new production environment, as well as the environment of another company I work with that is also using Power BI.  Someone suggested adding a cert.  We added a self-signed cert, and rebooted the machine for fun, no change.  Is it safe to ignore these errors?

 

36882: The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate.

 

36888: A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 48. The Windows SChannel error state is 552.

Status: Delivered
Comments
by v-haibl-msft Super Contributor
on ‎04-21-2017 12:47 AM

@AnniePower

 

I can repro the same issue as you. I’ve reported it internally to Power BI Team: CRI 36096485
I’ll post here once I get any update about it.

 

Best Regards,
Herbert

by Moderator Vicky_Song
on ‎04-21-2017 12:49 AM
Status changed to: Accepted
 
by v-haibl-msft Super Contributor
on ‎05-02-2017 07:02 PM

@AnniePower

 

I've got response from the Product Team. If the refresh is successful, it is safe to ignore these errors.

 

Best Regards,
Herbert

by Moderator Vicky_Song
on ‎05-02-2017 07:05 PM
Status changed to: Delivered
 
by AnniePower Frequent Visitor
on ‎05-03-2017 04:38 AM

Thank you @v-haibl-msft !

by jchughes New Member
on ‎09-21-2017 02:54 AM

I have the same issue but the refresh is not successful.  Any advice welcome.

by Splint New Member
on ‎10-05-2017 11:50 PM

For some reason my gateway started to use a self signed certificate from a seperate SQL server (one of my data sources). Not sure what caused this but I expect it to be some setting on the SQL server that changed.

Fix for now: I Found the self signed certificate on the SQL server, exported the certificate, and imported it on the gateway server (trusted root certficate store). Refresh was now successful. 

 

Make sure your datasource name exactly matches the certificate subject.