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

A DBAmp Refresh Job error has occured

This morning we came in to many email alerts in regards to the subject above (A DBAmp Refresh Job error has occured). After much digging, we found the source of the issue was in the SF_Replicate, FeedComment:

--- Starting SF_Replicate for FeedComment
11:39:38: Drop FeedComment_Previous if it exists.
11:39:38: Create FeedComment_Previous with new structure.
11:39:38: Run the DBAmp.exe program.
11:39:38: DBAmp Bulk Operations. V2.12.18 (c) Copyright 2006-2010 forceAmp.com LLC
11:39:38: Replicating into FeedComment_Previous , CHRYGIGO / Salesforce Backups .
11:39:38: Opening SQL Server rowset
11:39:39: Error: RunQuery failed with com_error.
11:39:39: MALFORMED_QUERY: Implementation restriction: directly querying FeedComment is only supported for admin users in version 23.0 and higher.
11:39:39: Error: DBAmp.exe was unsuccessful.
11:39:39: Error: Command string is C:\"Program Files"\DBAmp\DBAmp.exe Export FeedComment_Previous "CHRYGIGO" "Salesforce Backups" "SALESFORCE"
--- Ending SF_Replicate. Operation FAILED.
Error: SF_Replicate failed for table FeedComment
Error 50000, Severity 16, State 1, Line 191
--- Ending SF_Replicate. Operation FAILED.

We are currently running the DBAmp Version 2.12.18, and was curious if you had any ideas on what the problem may be. Haven't had any issues with this before, it is a recent development. Please advise on how we can fix this issue, thanks!! You can post on this, or email me directly at cclifford@chrysalisventures.com.
1 person has
this problem
+1
Reply
  • The issue has occurred because salesforce.com changed the requirements for a query on the FeedComment table.

    There are many routes to fix this:

    1. Upgrade DBAmp using http://www.forceamp.com/upgrade.htm You are running a version of DBAmp that is 2 years old and there have been significant fixes since then.

    OR

    2. If the FeedComment table is not needed by your integration, you can modify the sf_replicateall and sf_refreshall stored procs to skip it. This could be a temporary work around until you are able to upgrade. There are comments in the stored procedures that indicate how to skip tables; let me know if you need more detailed information.
  • (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

  • I’m thankful
    Thank you Bill for your quick response. Shortly after I posted that issue, I found another post in relation to my issue, so I apologize for making you do redundant work. I have conversed with my partner here, and we are going to do the upgrade, but I did want to express gratitude for you fast response and support. We are very pleased with your service and support!! Will update more if needed, and thanks again!!
  • (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