topic Salesforce Endpoint Error When Using API Version 42.0 in Talend Studio

Salesforce Endpoint Error When Using API Version 42.0

Anonymous — Sat, 16 Nov 2024 08:21:26 GMT

Hello,

I'm getting an endpoint error when trying to connect to Salesforce using the endpoint (API version 42.0):

https://test.salesforce.com/services/Soap/u/42.0

The error I'm encountering is:

java.lang.RuntimeException: IOException: com.sforce.ws.ConnectionException: unable to find end tag at: START_TAG seen ...</accessibilityMode><chatterExternal>... @1:735
at...

However, the connections works when downgrading the API version to 35.0 as such:

https://www.salesforce.com/services/Soap/u/35.0

What could be causing this?

Below are the connection component's configurations:

I'm using Talend OS for DI v6.4.1

Re: Salesforce Endpoint Error When Using API Version 42.0

TRF — Tue, 24 Apr 2018 09:48:28 GMT

Not sure versions after 39.0 are supported by tSalesforce components.

Re: Salesforce Endpoint Error When Using API Version 42.0

Anonymous — Tue, 24 Apr 2018 09:53:51 GMT

Hello TRF,

Thank you for your reply.

This behaviour is occurring locally, that is on my workstation.

Normally, after a successful build, we deploy this job on a Unix server to be executed automatically. Yesterday, we delivered the job (Production) using the endpoint:

https://login.salesforce.com/services/Soap/u/42.0 and it worked.

So the question remains as to why it isn't working for Sandboxes.

Re: Salesforce Endpoint Error When Using API Version 42.0

TRF — Tue, 24 Apr 2018 09:59:47 GMT

What if you change for 39.0?

Re: Salesforce Endpoint Error When Using API Version 42.0

Anonymous — Tue, 24 Apr 2018 10:13:34 GMT

It works when changing the API version to 39.0 on my workstation. However, we still have a job running on API level 42.0, which is strange.

Re: Salesforce Endpoint Error When Using API Version 42.0

TRF — Tue, 24 Apr 2018 10:30:52 GMT

Once again, not completly sure of this point but I think it may depend of which kind of object you want to work with.

Sorry, no time to explore this subject but it could be the beginning of an explanation (or not...)