• Andrew Srb
  • NEWBIE
  • 0 Points
  • Member since 2017

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
    Questions
  • 1
    Replies
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