Scheduled SQL import over gateway timeout after only 6 minutes?

[Anonymous]

So this is occuring more and more often. I am getting these timeouts against an on prem datawarehouse.

It is scheduled imports over an enterprise gateway.

Its often quite small tables so it should not be because of queries taking too long.

Example below.

Scheduled	16/10/2019, 10:01:23	16/10/2019, 10:07:28	Failed	Before the data import for dim Date tmp finished, its data source timed out. Double-check whether that data source can process import queries, and if it can, try again.

So what is going on here ? 

I would assume there is some kind of problem estabishling a connection? Is there a separate setting for this that I can change, or a setting for "try again"?

There is no limit on the number of concurrent connections to the database.

The database remote query timeout is set to 100000 seconds..

All imports from the datawarehouse are made with the same service account, so can it be some kind of qeue/pooling issue? But then why only wait 6 minutes?

There is a "skip test connection" setting in the gateway datasource settings. Can this help?

[v-lili6-msft]

hi, @Anonymous 

If you could update the gateway to the latest version and try it again.

Regards,

Lin

[Anonymous]

It's the latest version.

Turned on additonal logging and it seems that I have random certificate issues.

Message: A connection was successfully established with the server, but then an error occurred during the login process.
(provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)

[Anonymous]

Can I force the gateway connection string to trust the sql server certificate (TrustServerCertificate=True)?

Or turn off encryption between on prem machines?