Error connecting Dataloader to the Sandbox

[ronaldfernandezizertis]

Describe the bug #1020
"I am trying to connect Dataloader in OAuth with my Sandbox credentials, and I am getting a connection failure error. I have entered the Test.salesforce URL and the domain of my organization in the Dataloader settings, but it does not connect. Additionally, when the failure occurs, it tries to connect to login.salesforce, which is for Production, even though I have never configured it that way. I also think the version of Java might be causing the issue, but I'm not sure, I have changed the config file in OAuth to my domain but it still does not connect me and redirects me to login.salesforce instead of my organization, but what I really want is to be able to connect to my Sandbox.Could someone help me with this issue? I would really appreciate it."

Expected behavior
Connect .

Screenshots

Desktop (please complete the following information):

• OS: [e.g. MacOS Big Sur, Windows 11]
• Version [e.g. 56.0.4]

[ashitsalesforce]

Hi @ronaldfernandezizertis ,

Can you try with test.salesforce.com URL for Sandbox? Also, are you able to login to your sandbox instance using the same username? Here is the help page on sandbox login URLs and usernames to use.

[ronaldfernandezizertis]

Thanks for your answer. I have already tried it with test.salesforce.com and it is exactly the same as with my org domain. I honestly don't know what to do.

[ashitsalesforce]

Hi @ronaldfernandezizertis , the error message indicates that data loader is unable to connect to Salesforce login service. Can you check the following?

• If your desktop/laptop is at your work, perhaps it is behind a corporate firewall which stops direct outbound traffic. If so, you will need to specify the web proxy settings after getting them from your browser or by asking your desktop administrator.
• Try login to the production org (https://muface.my.salesforce.com or https://login.salesforce.com) and check if the issue still occurs.
• Try OAuth login . It uses your system's browser for logging in. If the login succeeds but data loader fails to show the list of salesforce objects, provide the error messages shown in the console window.

[ronaldfernandezizertis]

I think it is that it does not detect the JAVA version, I have installed the 17,21 and 22 and I get null.

[ashitsalesforce]

Hi @ronaldfernandezizertis , given that you are seeing Data Loader UI means that the Data Loader launcher script (dataloader.bat) is able to pick up the right Java version.

The error message you are seeing means that Data Loader is unable to reach out to salesforce.com site to check for availability of a new version. This is most likely due to a firewall setup on your desktop that prevents any direct outbound communication. The likely reason to block direct outbound communication in an office desktop is to have all outbound traffic go through a central proxy service. Contact your desktop admin for the proxy service configuration information.

[ronaldfernandezizertis]

Ok, I was afraid that something like that could happen, but in this case I need to indicate specific PROXIS or just tell the system administrator to check the Salesfoce and Dataloader PROXIS?

[ashitsalesforce]

You need to ask your desktop administrator the following information:

• DNS name or IP address of your company's proxy service.
• Port number of your company's proxy service for outbound connections.
• username and password, if any, used by your company's proxy service to allow outbound connections. These are different from your Salesforce username and password.
• NTLM domain, if any, associated with proxy service's username and password.

[ashitsalesforce]

I am attaching an internal version of data loader that tries to detect system proxy settings. If any found, it sets proxy host and port values in Settings dialog if they were not already set.

To try it, install it in a different folder than your current data loader installation, launch it, and view Settings to see if proxy host name and port settings are prefilled.

dataloader_v62.0.1.zip
MD5 (dataloader_v62.0.1.zip) = 6fc07b1942de868dde7b641a7e41cb1b

[ronaldfernandezizertis]

Thank you very much, sorry for not having replied I have opened an internal incident to see if that remote computer I have blocked but I'm still waiting, I tried to download the Dataloader 42.0.0 and I get the same thing: Failed to send request, I'll try with the version you have provided me to see if I can connect, thank you very much for your help !!!!

[50471736]

Ronald, the suspense is killing me. Let us know if the new version helps.

[ronaldfernandezizertis]

Hahahaha, it didn't work, as ashitsalesforce told me, I have to release the PROXYS because something is blocking the communication. My client is the government and surely they have many restrictions. When they give me permissions I will tell you if I have been able to solve it.

[ashitsalesforce]

Hi @ronaldfernandezizertis , if you don't mind trying once again, I am attaching a patch that has the code to discover proxy service host and port if they are set at system level. While this does not guarantee success as the code can't discover proxy username and password as well as NTLM domain if configured, it may help you provide further details to the network admin so that you can get proxy username, password, and NTLM domain if configured in your network.

dataloader_v62.0.1.zip
MD5 (dataloader_v62.0.1.zip) = c81c30c3be91adf605aad9beeb7f09f2