Apex Code Development You need to sign in to do that
Don't have an account?
Jim McCabe salesforce replicate error using DBAmp
Here is the error message that I’m getting
12:25:16: Error: An error has occurred while fetching rows from salesforce.com.
12:25:16: Too many requests waiting for connections
12:25:16: Error: Replication failed.
Source: ForceAmpAPI.SQueryResults4.1
Description: Too many requests waiting for connections
12:26:05: Error: DBAmp.exe was unsuccessful.
12:26:05: Error: Command string is C:\"Program Files"\DBAmp\DBAmp.exe Export "Lead_Previous" "ISQ-UTLSQL-01\U1" "SalesForce_Prod" "SALESFORCE"
--- Ending SF_Replicate. Operation FAILED.
Msg 50000, Level 16, State 1, Procedure SF_Replicate, Line 244
--- Ending SF_Replicate. Operation FAILED.
Does anyone have any suggestions on how to fix?
12:25:16: Error: An error has occurred while fetching rows from salesforce.com.
12:25:16: Too many requests waiting for connections
12:25:16: Error: Replication failed.
Source: ForceAmpAPI.SQueryResults4.1
Description: Too many requests waiting for connections
12:26:05: Error: DBAmp.exe was unsuccessful.
12:26:05: Error: Command string is C:\"Program Files"\DBAmp\DBAmp.exe Export "Lead_Previous" "ISQ-UTLSQL-01\U1" "SalesForce_Prod" "SALESFORCE"
--- Ending SF_Replicate. Operation FAILED.
Msg 50000, Level 16, State 1, Procedure SF_Replicate, Line 244
--- Ending SF_Replicate. Operation FAILED.
Does anyone have any suggestions on how to fix?
2. Run the DBAmp Configuration Program on your current install and choose Configuration/Options. Copy down your current serial numbers.
3. Stop SQL Server.
4. Run the DBAmp installation program. You will need your serial number for installation. Please contact support at forceamp.com if you need help with this value.
5. Restart SQL Server
6. The DBAmp stored procedures change with every release. You must upgrade every SQL database that currently contains DBAmp stored procs with the new versions. Update the DBAmp Stored Procedures by running the Program Files/DBAmp/SQL/Create DBAmp SPROCS.sql file. You must modify all instances of the @ProgDir variable in the script if you installed DBAmp in another directory other than c:\Program\Files\DBAmp . Failure to do this will result in errors.
Because the new version may connect to a newer API endpoint, additional fields and objects may become visible with the upgrade. If you are using sf_refresh for local copies, you must run sf_replicate on that object to pickup these schema changes. Then you can resume your normal sf_refresh schedule.