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
VipsVips 

Exception while login

I am new to sforce (just a day old) and it seems quite a strange problem but when an object of SforceService gives a  call to login(username, pwd) method, the following message is displayed in the console:

The request failed with the error message:
--
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>301 Moved Permanently</TITLE>
</HEAD><BODY>
<H1>Moved Permanently</H1>
The document has moved <A HREF="http://www.salesforce.com/us/products/customer-service-support.jsp">here</A>.<P>
</BODY></HTML>

--.

Now this was working fine till yesterday and logged the user successfully.The soap:address location in the WSDL file is still the same https://www.salesforce.com/services/Soap/c/2.5

Can anybody throw some light why it is happening today?

Thanks

Vineet GogiaVineet Gogia

Hi ,

I am facing the same problem. I Tried our developers logins as well as clients real login, but the results was same.

The request failed with the error message:
--
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>301 Moved Permanently</TITLE>
</HEAD><BODY>
<H1>Moved Permanently</H1>
The document has moved <A HREF="http://www.salesforce.com/us/products/customer-service-support.jsp">here</A>.<P>
</BODY></HTML>

--.

I also want to know is it worthy enough to build an application using version 2.5 as it is still evolving  .
Please also tell me the url of the API  to add web refrence to my application.

Thanx
DotNetDevil

VipsVips

At last found the solution...for some reason the

<soap:address location="https://www.salesforce.com/services/soap/c/2.5" />

node in the wsdl file needs to be changed to

<soap:address location="https://www.sforce.com/services/soap/c/2.5" />

Cheers

DevAngelDevAngel

The url in the wsdl is the url to use for login, ALWAYS.  Do not use www.sforce.com.  There was a problem with the login at www.salesforce.com this morning that has been resolved.  PLEASE, don't use hacks as they will likely come around and bite you later on.  If you decide to go against the tide by not following the quidelines given in the documentation and technotes, we cannot support your efforts.