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

SF_Replicate fails on namespace__[Ee][Aa-Zz]__c

--- Starting SF_Replicate for pse__Expense__History V3.6.8
10:03:58: Parameters: glob pse__Expense__History Version: V3.6.8
10:03:58: Drop pse__Expense__History_Previous20181105T100358027 if it exists.
10:03:58: Create pse__Expense__History_Previous20181105T100358027 with new structure.
10:03:58: DBAmpNet2 3.6.8.0 (c) Copyright 2015-2017 forceAmp.com LLC
10:03:58: Parameters: replicate pse__Expense__History_Previous20181105T100358027 SN Glob glob
10:03:59: System.Web.Services.Protocols.SoapException: INVALID_TYPE: sObject type 'pse__e' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call f
or the appropriate names.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at DBAmpNet2.sforce.SforceService.describeSObject(String sObjectType)
at DBAmpNet2.SFDataLayer3.GetSchema(String objName)
10:03:59: DBAmpNet2 Operation FAILED.
10:04:00: Error: Replicate program was unsuccessful.
10:04:00: Error: Command string is C:\"Program Files"\DBAmp\DBAmpNet2.exe Exportsoap "Replicate" "pse__Expense__History_Previous20181105T100358027" "SN" "Glob" "glob"
--- Ending SF_Replicate. Operation FAILED.
Msg 50000, Level 16, State 1, Procedure SF_Replicate, Line 383
--- Ending SF_Replicate. Operation FAILED.
1 person has
this problem
+1
Reply
  • Ben, for some reason your forum entries are being marked as spam by the forum software. That causes a delay in response.

    Is there anything about your email address that may contribute to this classification ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • With regard to your issue:

    It is a bug and it will be fixed in the next version of DBAmp. But, in the meantime if you want to have a quick fix, do the following:

    Modify the SF_Replicate stored procedure

    Find the following line:
    set @prev_table = @table_name + '_Previous' + CONVERT(nvarchar(30), GETDATE(), 126)

    Change the line above to:
    set @prev_table = @table_name + '_Previous'

    Click execute to make the changes

    Then, retry the SF_Replicate. The only tables that will still cause issues are __mdt tables, that will also be fixed in the next version of DBAmp.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I'm not sure what's wrong with the account that's related to my work email, but I can use my personal getsatisfaction account instead if the other is causing problems.

    I wanted to edit my post because I made a typo. It's the __history tables, not the __c tables that are failing.

    Also, I found that the objects like namespace__[Cc][Aa-Zz]__history have the same problem as namespace__[Ee][Aa-Zz]__history, hopefully you already realized that I made a typo and found the other edge case on your own.

    The workaround you suggested did fix the replication.

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

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