Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m frustrated

Refresh Task Table failing

I am trying to refresh the TASK table and am getting an error that the query runs too long. Salesforce has bumped out timeout to 10 minutes, but am still getting the error. In the DBAmp documentation, I see a proc called SF_ReplicateLarge defined which sounds like what I need. I do not see the stored proc in my SQL server or in the installation folders.

Any help would be appreciated.
1 person has
this problem
+1
Reply
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • This is from the SQL Agent job. When I run the refresh in a stand alone query the message is "Query running too long". I've also attached the code used at the bottom of this message.

    Message
    Executed as user: SalesForceUser01. --- Starting SF_Refresh for Task [SQLSTATE 01000] (Message 0) Cannot execute the query "SELECT "Tbl1005"."AccountId" "Col1009","Tbl1005"."Action__c" "Col1010","Tbl1005"."Activity_Created_Date__c" "Col1011","Tbl1005"."Activity_Manager__c" "Col1012","Tbl1005"."Activity_Team__c" "Col1013","Tbl1005"."ActivityDate" "Col1014","Tbl1005"."Advertiser_at_Time_of_Activity__c" "Col1015","Tbl1005"."Big_Deal_Prospect__c" "Col1016","Tbl1005"."Business_Days__c" "Col1017","Tbl1005"."Cadence_Current_State__c" "Col1018","Tbl1005"."Cadence_Input_Transition_Date__c" "Col1019","Tbl1005"."Cadence_Next_Contact_Date__c" "Col1020","Tbl1005"."Cadence_Next_State__c" "Col1021","Tbl1005"."Cadence_Transition__c" "Col1022","Tbl1005"."CadenceID__c" "Col1023","Tbl1005"."Call_Direction__c" "Col1024","Tbl1005"."Call_Duration_Hrs__c" "Col1025","Tbl1005"."Call_Duration_in_Min__c" "Col1026","Tbl1005"."Call_Info__c" "Col1027","Tbl1005"."Call_Made__c" "Col1028","Tbl1005"."Call_Reason__c" "Col1029","Tbl1005"."Call_Result__c" "Col1030","Tbl1005"."CallDisposition" "Col1031","Tbl1005"."CallDurationInSeconds" "Col1032","Tbl1005"."CallObject" "Col1033","Tbl1005"."CallType" "Col1034","Tbl1005"."Completed_Date__c" "Col1035","Tbl1005"."Completed_Date_Day__c" "Col1036","Tbl1005"."CreatedById" "Col1037","Tbl1005"."CreatedDate" "Col1038","Tbl1005"."Day_of_Week__c" "Col1039","Tbl1005"."Days_Since_Last_Activity__c" "Col1040","Tbl1005"."DaysSinceLastAMVerbal__c" "Col1041","Tbl1005"."Description" "Col1042","Tbl1005"."Dialed_Number__c" "Col1043","Tbl1005"."First_of_Month__c" "Col1044","Tbl1005"."Id" "Col1045","Tbl1005"."IsArchived" "Col1046","Tbl1005"."IsBigDealRep__c" "Col1047","Tbl1005"."isCallActivity__c" "Col1048","Tbl1005"."IsClosed" "Col1049","Tbl1005"."IsDeleted" "Col1050","Tbl1005"."isEmail__c" "Col1051","Tbl1005"."IsRecurrence" "Col1052","Tbl1005"."IsReminderSet" "Col1053","Tbl1005"."IsVisibleInSelfService" "Col1054","Tbl1005"."Last_of_Month__c" "Col1055","Tbl1005"."LastModifiedById" "Col1056","Tbl1005"."LastModifiedDate" "Col1057","Tbl1005"."Lead_Source__c" "Col1058","Tbl1005"."Main_Note_ID__c" "Col1059","Tbl1005"."M... 09:00:02: Using Schema Error Action of yes [SQLSTATE 01000] (Error 0) 09:00:03: Using last run time of 2014-04-01 17:14:00 [SQLSTATE 01000] (Error 0) OLE DB provider "DBAmp.DBAmp" for linked server "SALESFORCE" returned message "FAHttp::Send::WinHttpReceiveResponse Win32Error:: The operation timed out ". [SQLSTATE 01000] (Error 7412). The step failed.

    ************************* Code from Job

    DECLARE @SalesForceInstance VARCHAR(100) = 'SALESFORCE'

    EXECUTE [dbo].[SF_Refresh]
    @table_server = @SalesForceInstance, -- sysname
    @table_name = 'Task' , -- sysname
    @schema_error_action = 'Yes'

    GO
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I would first run the DBAmp Configuration Program, menu choice Registry Settings and set the Network Receive Timeout to 2400.

    Then retry the operation.

    The sf_replicateLarge stored proc is available in the latest version of DBAmp. You can upgrade following the instructions at http://www.forceamp.com/upgrade.htm

    Please let me know if this does not resolve the issue.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I will give that a try. I have one SQL Server upgraded to the new version (2.17.7), but have yet to do our production version. I still don't see the SF_ReplicateLarge proc on the 2.17.7 version. Is there a newer version?

    Thanks!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I upgraded to version 2.18.3 and updated the registry setting to 2400 as suggested. I tried an SF_ReplicateLarge. It ran for 2 1/2 hours and then failed. The output is below although I cut out several iterations of the same series of messages.

    Any other suggestions?

    --- Starting SF_ReplicateLarge for TASK
    10:25:18: Drop TASK_Previous if it exists.
    10:25:20: Create TASK_Previous with new structure.
    10:25:23: Run the DBAmp.exe program for "where Id>'000000000000000' and Id'00T3000001cZwiYEAS' and Id'00Ta000002VwL36EAF' and Id'00Ta000002XShHGEA1' and Id
    --- Ending SF_ReplicateLarge. Operation FAILED.
    Msg 50000, Level 16, State 1, Procedure SF_ReplicateLarge, Line 359
    --- Ending SF_ReplicateLarge. Operation FAILED.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Can you send the unedited output to me at support at forceamp.com ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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