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

Unable to Base64Decode for column Body

15:12:08: DBAmp Bulk Operations. V2.12.18 (c) Copyright 2006-2010 forceAmp.com LLC
15:12:08: Replicating into Document_Previous , NWT-VM-DB01 / Salesforce_Sandbox_backup .
15:12:08: Opening SQL Server rowset
15:12:49: Error: Unable to Base64Decode for column Body.
15:12:49: Error: Failed to Insert Row into SQL Server table. Id 01540000000RUocAAG
Source: Microsoft OLE DB Provider for SQL Server
Description: Unspecified error
15:12:49: Error: Replication failed.
15:12:50: Error: DBAmp.exe was unsuccessful.
15:12:50: Error: Command string is C:\"Program Files"\DBAmp\DBAmp.exe Export Document_Previous "NWT-VM-DB01" "Salesforce_Sandbox_backup" "SALESFORCE_SANDBOX_FULL"
--- Ending SF_Replicate. Operation FAILED.
Error: SF_Replicate failed for table Document
Error 50000, Severity 16, State 1, Line 191
1 person has
this problem
+1
Reply
  • Does anyone have a problem with the documents table in SF?
    Sorry I didn't realize I was posting a stack trace when I created this issue. I thought I was searching.
  • (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

  • Hi Paul,

    Can you take a look at that document and see how big it is:

    Select BodyLength from SALESFORCE_SANDBOX_FULL...Document where Id='01540000000RUocAAG'

    Thanks.
  • (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

  • 16643022

    Also I get this failure:
    --- Starting SF_Replicate for ContactShare
    11:54:13: Drop ContactShare_Previous if it exists.
    11:54:13: Create ContactShare_Previous with new structure.
    11:54:15: Run the DBAmp.exe program.
    11:54:15: DBAmp Bulk Operations. V2.12.18 (c) Copyright 2006-2010 forceAmp.com LLC
    11:54:15: Replicating into ContactShare_Previous , NWT-VM-DB01 / Salesforce_Sandbox_backup .
    11:54:15: Opening SQL Server rowset
    12:15:52: 2313532 rows copied.
    12:15:52: Drop ContactShare if it exists.
    12:15:52: Rename previous table from ContactShare_Previous to ContactShare
    Error: SF_Replicate failed for table ContactShare
    Error 15225, Severity 11, State 1, Line 338
    No item by the name of 'ContactShare_Previous' could be found in the current database 'Salesforce_Sandbox_backup', given that @itemtype was input as '(null)'.
  • (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

  • So for the first problem, that document has exceeded the dbamp max of 12Meg per document. Later versions of DBAmp have a way of handling this (either by not copying down the body of the document or by increasing the max).

    You can upgrade to the latest version of DBAmp using the instructions at www.forceamp.com/upgrade.htm

    The other thing you might want to consider is whether you really need the document table locally. You can modify the sf_replciateall and sf_refreshall procs to skip the document table. Let me know if you need details.

    Problem 2: More than likely you ran the sf_replicate command using a user that does create dbo schema tables. Look in the database and see if there are tables that have another schema besides dbo. DBAmp is written with the assumption that only dbo schema will be used.
  • (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