Help get this topic noticed by sharing it on Twitter, Facebook, or email.

SF_Replicate jobs suddenly failing with timeouts

We have several sf_replicate jobs which have been running for years to replicate several different salesforce orgs.

Recently these jobs have begun failing with timeout errors and also messages similar to the following:
***********************************************
11:07:18: Failed to read from reply.
Win32Error::
The connection with the server was terminated abnormally

11:07:18: Error: Replication failed.
Source: ForceAmpAPI.SQueryResults4.1
Description: Failed to read from reply.
Win32Error::
The connection with the server was terminated abnormally
**********************************************

I understand this issue is likely not with DBAmp, but was wondering if you could suggest what network/SQL settings we should look at in order to remedy?

Thanks
1 person has
this problem
+1
Reply
  • This error occurs because your firewall / proxy is terminating the connection because of a TCP idle timeout (also call the Dead Connection Timeout). Every firewall / proxy has a configurable value that specifies how many seconds to wait for a response from request inside the firewall. If salesforce takes too long to respond, the timeout kicks in and the firewall kills the connection.

    Reasons why the starts happening:

    1. Your network group lowered the timeout value for your firewall/proxy
    2. Salesforce is taking longer to respond because someone on salesforce altered the security profile of the sf user used by the linked server.
    3. Salesforce is taking longer because there was a dramatic increase in the number of rows in that table.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned