Sign Up ›

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Emily Josie YoungEmily Josie Young 

Jitterbit to Salesforce Failure

Jitterbit is throwing this error message, and I was wondering if anyone had any insight as to what Salesforce doesn't like about the operation?

Fatal Error:
Transformation failed.

Error:
Call to webservice at https://na25.salesforce.com/services/Soap/u/33.0/00Di0000000HoUP failed. Reported error: The webservice call failed. Failed to check for a SoapFault in the response: D:/Temp/jitterbit/OpId_551186_b683752b-91c9-4c26-b945-54faedbc4f5b/_t636876_target_res.xml Failed to check for Soap Fault in the response: Fatal SAX error: Invalid document structure XML file: D:/Temp/jitterbit/OpId_551186_b683752b-91c9-4c26-b945-54faedbc4f5b/_t636876_target_res.xml The response was: [{"channel":"/meta/subscribe","clientId":"i21moplv8c3qqiiu7gbzivbr0eg","error":"400::Cannot send messages with different client ids in the same request","successful":false}] <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="urn:partner.soap.sforce.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Header><LimitInfoHeader><limitInfo><current>54795</current><limit>3710000</limit><type>API REQUESTS</type></limitInfo></LimitInfoHeader></soapenv:Header><soapenv:Body><queryResponse><result xsi:type="QueryResult"><done>true</done><queryLocator xsi:nil="true"/><size>0</size></result></queryResponse></soapenv:Body></soapenv:Envelope> (The posted soap envelope was: 'D:/Temp/jitterbit/OpId_551186_b683752b-91c9-4c26-b945-54faedbc4f5b/_t636876_target_req.xml'.) [CODE:10721] file: WebServiceHandler.cpp, line 857 [CODE:10104] file: TreeMapperWebService.cpp, line 141
forceAMPforceAMP
We are having the same issue with DBAmp with 5 different customers.

It appears that the salesforce server is genreating an improper repsonse to the SOAP api request.  Similiar to the user above, what we are seeing is the following text at the beginning of the response:

[{"channel":"/meta/subscribe","clientId":"i21moplv8c3qqiiu7gbzivbr0eg","error":"400::Cannot send messages with different client ids in the same request","successful":false}]

It appears that a Streaming api response is being erroreously prefixed to the SOAP XML response.

The issue is intermittent and is occuring across several API endpoints.  In addition, the content header of the response indicates that the response is gzipped but the prefix above is not compressed in the actual message.

Please contact me if further details are needed.
 
bhargav swargambhargav swargam
Hi forceAMP,

Could you let me know how can we handle this case ?

Thanks,
Bhargav
forceAMPforceAMP
Are you having this same issue ?  What integration tool are you using ?
forceAMPforceAMP
Emily,  

Can you contact me at support@forceamp.com about this issue ?  I want to coordinate are cases at salesforce support to try to get escalation.

Thanks,  Bill 
bhargav swargambhargav swargam
Host: readyat.my.salesforce.com
GET /services/async/31.00/job/ 75031000006RaprAAC/batch 
 
Usually , all the calls are fine, but intermittently we get following response, which is causing issue. 

[{"channel":"/meta/subscribe","clientId":"1lceemip5qe2kq91l0n4v7s3o71i","error":"400::Cannot send messages with different client ids in the same request","successful":false}]
<?xml version="1.0" encoding="UTF-8"?><batchInfoList
   xmlns="http://www.force.com/2009/06/asyncapi/dataload">
<batchInfo>
  <id>75131000007i02rAAA</id>
  <jobId>75031000006RaprAAC</jobId>
  <state>Completed</state>
  <createdDate>2015-08-13T19:53:26.000Z</createdDate>
  <systemModstamp>2015-08-13T19:54:07.000Z</systemModstamp>
  <numberRecordsProcessed>10000</numberRecordsProcessed>
  <numberRecordsFailed>0</numberRecordsFailed>
  <totalProcessingTime>40198</totalProcessingTime>
  <apiActiveProcessingTime>32483</apiActiveProcessingTime>
  <apexProcessingTime>0</apexProcessingTime>
</batchInfo>
<batchInfo>
  <id>75131000007i03GAAQ</id>
  <jobId>75031000006RaprAAC</jobId>
  <state>Completed</state>
  <createdDate>2015-08-13T19:57:17.000Z</createdDate>
  <systemModstamp>2015-08-13T19:58:10.000Z</systemModstamp>
  <numberRecordsProcessed>10000</numberRecordsProcessed>
  <numberRecordsFailed>0</numberRecordsFailed>
  <totalProcessingTime>51920</totalProcessingTime>
  <apiActiveProcessingTime>33672</apiActiveProcessingTime>
  <apexProcessingTime>853</apexProcessingTime>
</batchInfo>
<batchInfo>
  <id>75131000007i03uAAA</id>
  <jobId>75031000006RaprAAC</jobId>
  <state>InProgress</state>
  <createdDate>2015-08-13T19:59:33.000Z</createdDate>
  <systemModstamp>2015-08-13T19:59:56.000Z</systemModstamp>
  <numberRecordsProcessed>4800</numberRecordsProcessed>
  <numberRecordsFailed>0</numberRecordsFailed>
  <totalProcessingTime>23847</totalProcessingTime>
  <apiActiveProcessingTime>10836</apiActiveProcessingTime>
  <apexProcessingTime>1480</apexProcessingTime>
</batchInfo>
</batchInfoList>
 
jhurstjhurst
We are looking into what is happening here.  If you can log a support case with any information you have around time the error happens, specific calls (if any patterns emerge on what calls the issue happens on), and any other details you can think of.

Thanks
Jay
bhargav swargambhargav swargam
i have mailed @ support@forceamp.com ,with the info i have. 
Use case here is , we are using serial mode for bulk writing and checking the job status at an interval of 10seconds. we are facing this issue
intermittently.
jhurstjhurst
Hello,

I wanted to give an update on this issue from the Salesforce side.

We have identified the bug on our end as a buffer issue inside of our web server.  The error could happen if client applications begin to flood the application server with a very large number of API errors.  On top of that, there is a timing component such that a successful call had to be made at the exact time in order to trigger the issue.

We have a fix identified, and will be rolling it out to the Winter '15 and SUmmer '15 instances over the next couple of weeks.  If you have any questions, please feel free to let me know.

Thanks again to Bill over at ForceAmp for helping us identify and troubleshoot the issue.

Jay Hurst 
Andrew SrbAndrew Srb
I'm having this issue as well. Not sure if anyone figured out how to solve this. Was working fine for a while after installing and then it started to get hung up:

The operation "Upsert PatientDiag" failed.
Fatal Error
Transformation failed.
Error(s) while processing C:\Users\Andrew Srb\Desktop\extracts\FULL\FULL\PtDiag.csv
Call to webservice at https://afcompanies.my.salesforce.com/services/Soap/u/37.0/00D37000000Hhf1 failed. Reported error:
The webservice call failed. The web service returned a SOAP Fault:
Code: sf:INVALID_SOAP_HEADER
Message: INVALID_SOAP_HEADER: You can't use TransferOpenActivities to change a PatientDiag__c's owner.

Detail: <sf:UnexpectedErrorFault xmlns:sf="urn:fault.partner.soap.sforce.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sf:UnexpectedErrorFault"><sf:exceptionCode>INVALID_SOAP_HEADER</sf:exceptionCode><sf:exceptionMessage>You can't use TransferOpenActivities to change a PatientDiag__c's owner.</sf:exceptionMessage></sf:UnexpectedErrorFault>

Additional details:
Failed to call the web service at "https://afcompanies.my.salesforce.com/services/Soap/u/37.0/00D37000000Hhf1".
Reason: The last (and probably most relevant) error was:
The server returned HTTP Status Code : 500 Server Error

Error is: The server encountered an unexpected condition that prevented it from fulfilling the request.
Headers sent by the server:
HTTP/1.1 500 Server Error
Date: Tue, 17 Jan 2017 17:13:00 GMT
Strict-Transport-Security: max-age=31536000; includeSubDomains
Set-Cookie: BrowserId=sDTX2NHYSr-tRLvbLCT9Mg;Path=/;Domain=.salesforce.com;Expires=Sat, 18-Mar-2017 17:13:00 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked


(The posted soap envelope was: 'C:/Windows/Temp/jitterbit_dl6/OpId_798856_e83574ed-e0fd-4807-82b3-8982302793f2/1_PtDiag_t895461_target.csv_req.xml'.) [CODE:10721] file: WebServiceHandler.cpp, line 1027 [CODE:10104] file: TreeMapperWebService.cpp, line 142
Failed to perform transformation using local source file:
C:/Windows/Temp/jitterbit_dl6/OpId_798856_e83574ed-e0fd-4807-82b3-8982302793f2/1_PtDiag.csv
jhurstjhurst
Andrew,

This is not the same issue.  Salesforce is returning you  hat looks to be acvalid error here:

<sf:exceptionMessage>You can't use TransferOpenActivities to change a PatientDiag__c's owner.</sf:exceptionMessage>

This is saying that you cannot use the TransferOpenActivities OwnerChangeOption header with yout custom object - https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_header_ownerchangeoptions.htm

Hope this helps.
Jay
Emily Josie YoungEmily Josie Young
DO we know what project this is on? Josie Young
Interlinx AssociatesInterlinx Associates
I am getting a similar error saying "You can't use TransferOpenActivities to change a User's owner."  I am importing users into a sandbox with Jitterbit.  I used this exact same data and mapping at the beginning of Feb into a different sandbox.  The only difference is this is Spring '17.  It worked in a Winter '17 sandbox.  Any ideas?

Below is the full error from Jitterbit.
_____________________________________________________________________________________________________
The operation "01 Upsert Inactive Users" failed.
Fatal Error
Transformation failed.
Error
Call to webservice at https://cs71.salesforce.com/services/Soap/u/37.0/00D4D0000008gt8 failed. Reported error: The webservice call failed. The web service returned a SOAP Fault: Code: sf:INVALID_SOAP_HEADER Message: INVALID_SOAP_HEADER: You can't use TransferOpenActivities to change a User's owner.  Detail: <sf:UnexpectedErrorFault xmlns:sf="urn:fault.partner.soap.sforce.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sf:UnexpectedErrorFault"><sf:exceptionCode>INVALID_SOAP_HEADER</sf:exceptionCode><sf:exceptionMessage>You can't use TransferOpenActivities to change a User's owner.</sf:exceptionMessage></sf:UnexpectedErrorFault>  Additional details: Failed to call the web service at "https://cs71.salesforce.com/services/Soap/u/37.0/00D4D0000008gt8". Reason: The last (and probably most relevant) error was: The server returned HTTP Status Code : 500 Server Error  Error is: The server encountered an unexpected condition that prevented it from fulfilling the request. Headers sent by the server: HTTP/1.1 500 Server Error Date: Sun, 12 Mar 2017 21:33:13 GMT Set-Cookie: BrowserId=HH6XYY4TRXG9EgH3vv_Nsg;Path=/;Domain=.salesforce.com;Expires=Thu, 11-May-2017 21:33:13 GMT Expires: Thu, 01 Jan 1970 00:00:00 GMT Content-Type: text/xml; charset=utf-8 Transfer-Encoding: chunked   (The posted soap envelope was: 'C:/Windows/Temp/jitterbit_dl6/OpId_2579191_5434aa1a-8411-4700-b678-60b5daa927f6/_t2553756_target_req.xml'.) [CODE:10721] file: WebServiceHandler.cpp, line 857 [CODE:10104] file: TreeMapperWebService.cpp, line 141
happyreadinghappyreading
I got this error recently too. The solution is to goto Jitterbit project, in Advanced Option of the Upsert, click Edit next to Ownership Options and tick N/A next to Transfer Open Activities. Save and deploy. Run the operation again, no error.