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

I'm get the following error for the past 4 days that has broken the replication process.

I'm get the following error for the past 4 days that has broken the replication process.

--- Starting SF_Replicate for FeedComment
09:25:30: Drop FeedComment_Previous if it exists.
09:25:30: Create FeedComment_Previous with new structure.
09:25:31: Run the DBAmp.exe program.
09:25:31: DBAmp Bulk Operations. V2.13.11 (c) Copyright 2006-2011 forceAmp.com LLC
09:25:31: Replicating into FeedComment_Previous , EGRET / Salesforce_Local .
09:25:31: DBAmp is using the SQL Native Client.
09:25:31: Opening SQL Server rowset
09:25:32: Error: RunQuery failed with com_error.
09:25:32: Implementation restriction: directly querying FeedComment is only supported for admin users in version 23.0 and higher.
09:25:32: Error: DBAmp.exe was unsuccessful.
09:25:32: Error: Command string is C:\"Program Files"\DBAmp\DBAmp.exe Export "FeedComment_Previous" "EGRET" "Salesforce_Local" "SALESFORCE"
--- Ending SF_Replicate. Operation FAILED.
Error: SF_Replicate failed for table FeedComment
Error 50000, Severity 16, State 1, Line 198
--- Ending SF_Replicate. Operation FAILED.
1 person has
this problem
+1
Reply
  • The issue is that with the Winter 12 release salesforce decided that the FeedComment table could only be accessed if you were an admin AND you were using the Winter 12 api (23.0). The version of DBAmp you have installed is running the 22.0 api.

    1. Is your org now on WInter '12 ? Login to salesforce.com and look up in the left hand corner.

    2. Are you doing an sf_replicateall ? If so, how is your replication process 'broken' ? Normally, if a table fails, sf_replicateall just continues to the next table.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Bill,
    Yes you are correct. It does appear to move on to the next table, however the error is still trapped by the job. The server reports that the job failed because the error condition bubbles up.

    If the table can't be replicated, can I avoid any attempt to copy / replicate the FeedComment table? Otherwise I won't know the difference b/w an acceptable error and a critical error.

    As for the version of Salesforce, I had several people check (per your instructions) and no one found the version information. It does have a box to preview Winter12, so I will assume we are on a lesser version.

    Hope this helps. Let me know if there is a proc change I can make to avoid attempting to replicate "FeedComment" for version less than Winter12.

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

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

  • In the sf_replicateall proc you'll a line that looks like this:

    if @tn = 'Vote' CONTINUE

    Add the following line at the same spot

    if @tn='FeedComment' CONTINUE

    Be sure to make the same modification to the sf_refreshall proc as well.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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