Dataloader 63.0.0. Issues

[jmvang89]

Reaching out for some help on on an issue we are having with the latest version of Dataloader. We currently have Amazon Corretto 17 version 17.0.13.11.1 and Dataloader version 63.0.0. Following the installation and launching Dataloader, we are getting an error stating along the lines or unable to check for the latest available data loader version: PKIX path building failed.... any help to point into the right direction would be greatly appreciate it.

Thank you,

[ashitsalesforce]

It is likely to do with your sfdc.endpoint configuration value in config.properties file. Here is a discussion of a similar issue. Can you share your config.properties file after removing sensitive information?

[jmvang89]

Hello ashitsalesforce,

So I'm looking at the file and there are nothing in there except 2 lines: #Salesfice Data Loader Config and #(timestamp) PST 2019. I should also add for context, we've extracted and installed DataLoader v63 in the extracted folder of v63 etc. We have not tried installing on top of the existing v62 however v62's config.properties files does contain the information in the linked articles/forum post.

Thanks,

[ashitsalesforce]

That means your 63.0.0 config.properties is using default settings. A few follow-on questions:

• Do you see a similar error message on the console when using v62 with the same JDK?
• Does v63.0.0 show up and are you able to login and perform the operations?
• The issue is likely because the cert presented by the service at "https://developer.salesforce.com/tools/data-loader" is not acceptable on the client side. Wondering if your org has a proxy for outbound traffic. If so, you will need to configure it through the UI or through config.properties file. If not, we need more details for further troubleshooting, for which set rootLogger.level=DEBUG
  in configs/log4j2.properties file.

[jmvang89]

Well we were able to figure out the issue. It turns out that recently we had migrated to Hyperforce customer and an update on Salesforce's domains and IPs on our firewall did the trick.https://help.salesforce.com/s/articleView?id=000384438&type=1

I appreciate all the help and promptness on lending a hand!
Regards
John

[ashitsalesforce]

Good to hear that your issue is resolved and thanks for giving an update with the root-cause of the issue. Makes sense that a migration will need either whitelisting new domains/IPs or upload new certs or both.