+ Start a Discussion
Lisa SeveriettiLisa Severietti 

Invalid User error when connecting to Crystal Reports 2013

I'm using Crystal Reports 2013 and SFDC as my datasource and receive an error message when trying to connect:
Login failed
HY000:INVALID_LOGIN:Invalid username, password, security token; or user locked out. [Databse Vendor Code: 58]

I am connecting to a sanbox, test.salesforce.com, and I have added the IP address of the server where Crystal Reports 2013 is installed to the sandbox trusted sites.  I have tried using just the password and password+token in the login credential and receive the error either way.
I use the same credentials to successfully login to Data Loader.
 
Best Answer chosen by Lisa Severietti
Lisa SeveriettiLisa Severietti
This is what I learned from SAP Support...The Invalid login error I am receiving while trying to connect to a Salesforce datasource in Crystal Reports 2013 is because the 3rd party ODBC driver that SAP has started to use with the 2013 version, only connects to a production org and not a sandbox org.

All Answers

Jagan ReddyJagan Reddy
Hi Lisa,

if you post any screen shots we will try to rectify the issue.

Thanks,
Jagan
jagansfdc@outlook.com
Lisa SeveriettiLisa Severietti
Screen shot of error message User-added image
Lisa SeveriettiLisa Severietti
Screen shot of login credentials
User-added image
Jagan ReddyJagan Reddy
Hi Lisa,

In the place of server you need to give the server name.
you can try like this either Localhost (or) 127.0.0.1 (or) your ip address.
Kindly let me know if u have any issues.

Thanks,
Jagan
jagansfdc@outlook.com
 
Jagan ReddyJagan Reddy
Hey if it is not working,

try like this at server---> https://test.salesforce.com/services/Soap/u/32.0
Lisa SeveriettiLisa Severietti
Hi Jagan,

I tried 
 https://test.salesforce.com/services/Soap/u/32.0
and
the SFDC instance (assuming that is what you meant when you suggested to try Localhost or IP address for the server name) for our sandbox for the server entry in the credentials and still get the same error.
Jagan ReddyJagan Reddy
Hi Lisa,

https://success.salesforce.com/answers?id=90630000000guNOAAY
see this link may be it will help you.
give your current api version at end of url. otherwise reset security token once.

server--
www.salesforce.com/services/Soap/u/32.0  (or) test.salesforce.com/services/Soap/u/32.0


Thanks,
Jagan
jagansfdc@outlook.com
Ramakrishnan AyyanarRamakrishnan Ayyanar
User-added image
Hi Jagan,

I tried to connect my sandbox credentials, i got this error.

i tried urls

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

i need solution.
Jagan ReddyJagan Reddy
Hi bro,

you just reset security token once and try it once will see.
 
Ramakrishnan AyyanarRamakrishnan Ayyanar
Hi Jagan Bro,

Thanks for response.
Your mentioned comments are also tried, but i got same error bro.
Jagan ReddyJagan Reddy
Hmm sorry,

i don't know what's the problem, ask Lisa she may get solution for this one.
Ramakrishnan AyyanarRamakrishnan Ayyanar

Hi Lisa Severietti,

I tried to connect my sandbox credentials, i got this error.


User-added image

i tried urls

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

i need solution
Lisa SeveriettiLisa Severietti
This is what I learned from SAP Support...The Invalid login error I am receiving while trying to connect to a Salesforce datasource in Crystal Reports 2013 is because the 3rd party ODBC driver that SAP has started to use with the 2013 version, only connects to a production org and not a sandbox org.
This was selected as the best answer
Lisa SeveriettiLisa Severietti
SAP said they would open a bug related to this issue.  In the mean time they suggested using a different ODBC driver that would allow me to connect to a SFDC sandbox.  I ended up reverting back to Crystal Reports 2008 (that was an alternative I had available to me).
RobertKafarskiRobertKafarski
Hi, what I have learned a few days ago and what was already mentioned earlier here on this thread, SAP outsourced the salesforce driver beginning with the version 4.1 to a 3rd party and this is when problems started. What I know, there is a patch coming with SP 6 to address this issue but it will be realeased some time in June this year. What I also found is that Crystal Reports 2011 which is version 4.0 runs on the working JAVA based driver and this is what I decided to use in my case as a workaround.