Skyvia Jobs Failing - Urgent

  • 10Views
  • Last Post 4 weeks ago
0
votes
Sanjul Bhakri posted this 4 weeks ago

Hi Skyvia Jobs are failing and three differenr types of error are:

 

1. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

2. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

3. 

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

 

 

Please help - all connections seem working fine. 

Best, 

Sanjul

0
votes
Mariia Zaharova posted this 4 weeks ago

These issues occur on the SQL Server side and is not related to Skyvia. Such error usually means that the target computer is running, but the service that you're trying to connect to is not available. 

 

1) You may start by taking a look at SQL server Connection in Skyvia. Set 'Command Timeout' to 120 sec. This is the time to wait while trying to execute a command before terminating the attempt and generating an error.

2) Lookup mapping in the package (together with Upsert) causes execution latency. Please select the "Use first match when multiple results" checkbox in the Lookup Options. This may provide a performance gain.

3) The common cause is a connection loss on the network transport level.

Also, firewalls can be set to "forcibly" close a socket if it does not meet the criteria of the firewall rule - usually a time limit.

 

After the changes are applied, please rerun the package. If the package faces the same error increase 'Command Timeout' to 240 sec.

Close