# Weekly SF\_ReplicateAll failing

**URL:** <https://community.cdata.com/t/weekly-sf-replicateall-failing/211>\
**Category:** CData DBAmp\
**Tags:** sql, question\
**Created:** [June 12, 2023, 7:54pm UTC](https://community.cdata.com/t/weekly-sf-replicateall-failing/211 "2023-06-12T19:54:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndreQ](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@AndreQ](https://community.cdata.com/u/AndreQ)\
**Post date:** [June 12, 2023, 7:54pm UTC](https://community.cdata.com/t/weekly-sf-replicateall-failing/211/1 "2023-06-12T19:54:14Z")

</div>

There are a host of errors, mostly “Error occurred creating primary key for table.” in tables&nbsp;AppDefinition,&nbsp;AuraDefinitionBundleInfo,&nbsp;AuraDefinitionInfo,&nbsp;FormulaFunction,&nbsp;FormulaFunctionAllowedType,&nbsp;FormulaFunctionAllowedType and other.

but also “Using FullCopy because the FieldChangeSnapshot table does not exist.”

threw a SOAP error:&nbsp;Error System.Web.Services.Protocols.SoapException: EXTERNAL\_OBJECT\_UNSUPPORTED\_EXCEPTION: Enter a valid ParentID.&nbsp;&nbsp; &nbsp;at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)&nbsp;at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)&nbsp;&nbsp; at DBAmpAZ.sforce.SforceService.query(String queryString)&nbsp;&nbsp; &nbsp;at afo220l.Uh.w()

Should I wipe out all the tables and start again? Please advise.

Regards

Andre

---

<div class="post-metadata">

**Author:** ![Ankit\_Singh](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/ankit_singh/32/1614_2.png) [@Ankit\_Singh](https://community.cdata.com/u/Ankit_Singh)\
**Post date:** [June 13, 2023, 6:41am UTC](https://community.cdata.com/t/weekly-sf-replicateall-failing/211/2 "2023-06-13T06:41:16Z")

</div>

Hey @AndreQ

Thanks for reaching out to CData Community. This looks like a technical issue that requires a bit of investigation. The best resolution here would be to reach out to CData Support but submitting a form:&nbsp;[https://www.cdata.com/support/submit.aspx](https://www.cdata.com/support/submit.aspx)

Any other details that you can add like when did this start failing, any configuration changes, or just the logs of the failure might help the Tech support team investigate the issue and get you a resolution.