function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
cl2014cl2014 

partner.wsdl-Failed to parse detail: START_TAG seen ...</sf:exceptionMessage><sf:upgradeURL>... @1:752 due to

I was able to do API calls with partner.wsdl.  However, i am no longer able to do so and get the following error message:

com.sforce.ws.ConnectionException: Failed to parse detail:  START_TAG seen ...</sf:exceptionMessage><sf:upgradeURL>... @1:752 due to: com.sforce.ws.ConnectionException: unable to find end tag at:  START_TAG seen ...</sf:exceptionMessage><sf:upgradeURL>... @1:752
    at com.sforce.ws.transport.SoapConnection.parseDetail(SoapConnection.java:238)
    at com.sforce.ws.transport.SoapConnection.createException(SoapConnection.java:204)
    at com.sforce.ws.transport.SoapConnection.receive(SoapConnection.java:150)
    at com.sforce.ws.transport.SoapConnection.send(SoapConnection.java:99)
    at com.sforce.soap.partner.PartnerConnection.login(PartnerConnection.java:790)
    at com.sforce.soap.partner.PartnerConnection.<init>(PartnerConnection.java:406)
    at com.sforce.soap.partner.Connector.newConnection(Connector.java:27)

According to the login history, each call was actually log in successfully.  Any suggestion to resolve the issue?  Thanks!
Best Answer chosen by cl2014
karthikeyan perumalkarthikeyan perumal
Hello, 

This kind of Exception found when The Login Credentials are invalid.
Either the Connection URL / Username / Password -- Anyone of this might wrong.
Please check the below link which have discussion on same type of issue:

https://developer.salesforce.com/forums/?id=906F0000000AXj1IAG

I have two suggestions. Firstly, see if anything useful has been written to your trace file "traceLogs.txt" as this should contain the full response. Secondly, be aware that Java 7 and lower does not use TLS1.1 or higher by default, so if you're not using Java 8, you'll need to add a JVM parameter of -Dhttps.protocols=TLSv1.1,TLSv1.2
Without the JVM parameters, I got exactly the same symptoms

Hope this will help you.. 

Thanks
karthik
 

All Answers

karthikeyan perumalkarthikeyan perumal
Hello, 

This kind of Exception found when The Login Credentials are invalid.
Either the Connection URL / Username / Password -- Anyone of this might wrong.
Please check the below link which have discussion on same type of issue:

https://developer.salesforce.com/forums/?id=906F0000000AXj1IAG

I have two suggestions. Firstly, see if anything useful has been written to your trace file "traceLogs.txt" as this should contain the full response. Secondly, be aware that Java 7 and lower does not use TLS1.1 or higher by default, so if you're not using Java 8, you'll need to add a JVM parameter of -Dhttps.protocols=TLSv1.1,TLSv1.2
Without the JVM parameters, I got exactly the same symptoms

Hope this will help you.. 

Thanks
karthik
 
This was selected as the best answer
cl2014cl2014
Hi Karthik,

After I added the JVM option, the issue was resolved.  Thanks a lot for your help!

BR,
Claire
Prasad Pulivarthi 5Prasad Pulivarthi 5
Hi Karthik,

I am Prasad, We have the same issue at the moment. I am an Oracle Apps Developer.  There is an Intergration that exists between Oracle and Salesforce through some Java Package calling the API to download XML response which is hosted on a Tomcat Application Server.

Tomcat is hosted on a Windows Server.

When we activate the TLS 1.1 on Salesforce which is originally due on 03/04/2017, the integration fails with below error. We had to deactivate the TLS to make things work.

LPX-00225: end-element tag "sf:exceptionMessage" does not match start-element tag "RESPMSG" Error at line 3 <?xml version="1.0" encoding="UTF-8"?> <RESPONSE><RESPCODE>E</RESPCODE> <RESPMSG>Failed to parse detail: START_TAG seen ...</sf:exceptionMessage><sf:upgradeURL>... @1:755 due to: com.sforce.ws.ConnectionException: unable to find end tag at: START_TAG seen ...</sf:exceptionMessage><sf:upgradeURL>... @1:755</RESPMSG></RESPONSE> API Error: API call returns null API error

I don't think there is an issue with Username/pwd/token because, this error occurs only when TLS 1.1 is activated on SalesForce.

Could you please suggest which direction i should move to debug.

Thanks,
Prasad


 
Clark HruskaClark Hruska

Hello Karthik,

Thanks for this response. I am trying to implement you reccommendation but am still getting the same issue. I have verified that my username and password are correct with the correct security token.

My question is, where will I be adding the parameter to enable TSL 1.2? I have added it to the process.bat file in the data loader folder. Here is the line I updated:

..\Java\bin\java.exe -Dhttps.protocols=TLSv1.2 -cp ..\dataloader-35.0.0-uber.jar -Dsalesforce.config.dir=%1 com.salesforce.dataloader.process.ProcessRunner %PROCESS_OPTION%

Is this correct or am I barking up the wrong tree?

Thanks!
karthikeyan perumalkarthikeyan perumal
Hello, 

if you want enable TSL 1.1 or higher version without having any Issue. 

KInldy follow the process  no need to  modify process.bat file with extra lines. 


Solutions From Salesfroce: 

Reference From this artical.

https://help.salesforce.com/articleView?id=000221207&type=1


Data Loader
To ensure no disruption to the use of Data Loader, customers need to download the newest version of data loader (https://releasenotes.docs.salesforce.com/en-us/spring16/release-notes/rn_forcecom_data_data_loader.htm), released with Spring '16, which is the only version that supports TLS 1.1 and higher. 

User-added image


Newest version of dataloader.

https://releasenotes.docs.salesforce.com/en-us/spring16/release-notes/rn_forcecom_data_data_loader.htm

Hope this will resolve your issue. 

Thanks
karthik