function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
laurentblaurentb 

API v2.5 login problem

Hello

I can't login anymore on both my dev account and the account of our company

I'm targeting https://www.salesforce.com/services/Soap/u/2.5 with urn:partner.soap.sforce.com' as namespace


 

DevAngelDevAngel

Hi laurentb,

Ok, are there any messages returned in the form of faults or exceptions?  Are you - using java or .net or something else?  I'd be glad to help, but I'll need a little more detail.

Erik ForsbergErik Forsberg

I have the same problem. In my case, this is what I get back.

I am sending the POST to http://salesforce.com/services/Soap/u/2.5

which the partner wsdl file seems to say.

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
  <soapenv:Fault>
   <faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:Server.NoService</faultcode>
   <faultstring>The AXIS engine could not find a target service to invoke!  targetService is u/2.5</faultstring>
   <detail/>
  </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>

DevAngelDevAngel

HI Erik,

Can you try www.salesforce.com?

Erik ForsbergErik Forsberg

Sorry, my typo.

I was indeed POSTing to http://www.salesforce.com/services/Soap/u/2.5

That generated the previous fault.

 

DevAngelDevAngel

Ok, no problem.  In the first post you posted the response xml, can you do the same for the request?  This is generally the kind of message that indicates a namespace problem.

 

 

Erik ForsbergErik Forsberg

OK, here is the request (password is changed to protect the individual) (ignore the formatting as the UI edit control doesnt allow me to enter it exactly, the real XML doesn have any CRLF in it)

<?xml version="1.0" encoding="UTF-8"><SOAP_ENV:Envelope xmlns:SOAP_ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><ns:login xmlns:ns="urn:soap.sforce.com"><ns:username>brad.gillham@sendia.com</ns:username><ns:password>xxxxxx</ns:password></ns:login></SOAP-ENV:Body></SOAP-ENV:Envelope>

DevAngelDevAngel

Hi Erik,

If you are using the partner wsdl the red below should be partner.soap.sforce.com, enterprise wsdl should be enterprise.soap.sforce.com.

Most proxy generators handle this for you.  What language and technologies are you using?

<?xml version="1.0" encoding="UTF-8"><SOAP_ENV:Envelope xmlns:SOAP_ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><ns:login xmlns:ns="urn:soap.sforce.com"><ns:username>brad.gillham@sendia.com</ns:username><ns:password>xxxxxx</ns:password></ns:login></SOAP-ENV:Body></SOAP-ENV:Envelope>

Erik ForsbergErik Forsberg

I'm modifying our own XML-RPC stuff into SOAP. I will try this right now.

Thanks

 

Erik ForsbergErik Forsberg

Thanks, that was the problem. Can login now.