Large Salesforce tables Replication Fails

  • 30Views
  • Last Post 1 weeks ago
0
votes
Steve Tempest posted this 2 weeks ago

My salesforce replication job's are failing to sync for the first time. I've copied details below on the tables affected.

I have a lot of records in the tables and would like to know if I'm doing something wrong as the sync takes days to complete.

Please dont tell me this is a problem with salesforce, I need to know how to make it work. If there are particular columns that I should exclude then let me know which ones.

I've paid for enterprise subscription can you please ensure this request get's prioritised support.

Salesforce table have all columns. First time replication with create table and incremental sync selected. Recurring sync enabled to every hour.

All the data looks like it has copied then it fails.

############ Salesforce Contact table to SQL Server ############

# of records created in destination 4,448,467

# Job ID: 17324544

########## END ##########

############ Salesforce Order table to SQL Server ############

# of records created in destination 9,611,474

# Job ID: 17270889

########## END ##########

############ Salesforce Account table to SQL Server ############

# of records created in destination 4,453,645
# Job ID: 17324496

########## END ##########

############ Salesforce OrderItem table to SQL Server ############

# of records created in destination 10,543,787

# Job ID: 17320226
########## END ##########

############ Salesforce Case table to SQL Server ############
# of records created in destination 7,532,814

# Job ID: 17271321

########## END ##########

Order By: Standard | Newest | Votes
-1
votes
Mariia Zaharova posted this 2 weeks ago

 

> ############ Salesforce Order table to SQL Server ############

At the moment, the following error occurs while running this package: 

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.)

 

> ############ Salesforce Contact table to SQL Server ############

> ############ Salesforce Account table to SQL Server ############

> ############ Salesforce OrderItem table to SQL Server ############

At the moment, the following error occurs while running these packages: 

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"

 

> ############ Salesforce Case table to SQL Server ############

At the moment, this package executes without errors. However, this package was failed with this error several times:

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"

 

All these errors occur at SQL Server side. Such error usually means that the target computer is running, but the service that you're trying to connect to is not available. 

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: https://skyvia.com/resources/docs/index.html?sqlserver_connections.htm

 

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.

 

0
votes
Steve Tempest posted this 2 weeks ago

The error numbers I listed were days before the error you have responded to.  Non of the error numbers I've quoted relate to an SQL error, nor did I mention one in my description.

It feels like you didnt really look at the problem and are in a rush to close the tickets. I have waited for days for you to respond to my support request I'd appreciate it if you could escallate this to a developer or someone who is technical.

Please look at the error numbers that I listed as that is when it first failed.

Your right yesterday the SQL server did restart and was offline for a period of time and the errors you have mentioned are expected due to that happening.

0
votes
Mariia Zaharova posted this 1 weeks ago

Dear Steve! We have contacted you by email, please check it.

Close