Troubleshoot Data Loader issues from the command line

Key Points for Investigating TLS Not Supported Issues

When Salesforce disabled TLS 1.0, Data Loader versions 35 and earlier became unusable. The following steps resolve TLS-related issues when running Data Loader from the command line.

1. Update the Data Loader to the latest version. Data Loader can be downloaded directly from your Salesforce org.
2. Update the Java version on your local machine or server to the most recent version (Java 1.8 or later). Always use the latest version of software.
3. Update the Data Loader JAR file to version 3.0. The JAR file is named dataloader-47.0.0-uber.jar (for Data Loader v38) and should be located in the CLI folders that run the Data Loader jobs.
4. Update the process configuration file on existing batch processes with the correct version reference for the services path. The SOAP endpoint entry in the process-conf.xml file should be updated to reference the correct API version. For example: <entry value="https://test.salesforce.com/services/Soap/u/38.0" key="sfdc.endpoint"> — update the API version number (38.0) to match the version of Data Loader you are using.
5. Check whether TLS 1.0 is disabled in your org. If yes, Data Loader versions 35 and earlier are no longer usable following the disablement of TLS 1.0.