A Google Search turned up different possible reasons for that. Let's walk them one-by-one:
This post on our sister site gives the most likely reason in your case, being a problem with the certificate:
I solved this with using a different signing certificate. The Android docs suggest a life of 10,000 days, but that now creates expiry dates after the end of time in *nix timestamps, which is some time in 2038. I generated a new cert that expires in 2037 and resubmitted the apk and it now installs ok. Unfortunately I had to change the identifier of the app and copy all the descriptions/graphics to the "new" app because play won't let you change the cert on an existing app.
As you cannot fix this yourself, it would mean contacting the dev to check and fix.
Unlikely to match your case, as ES File Explorer is a free app requiring no payment. But for others coming here because of the "error 102" in the title, let me quote from that post on our sister site as well:
Error Code 102 refers to connection refused.
Error 102 (net::ERR_CONNECTION_REFUSED): Unknown error
Please go through the following link I hope it may help. Link gives the description of network errors but related to Chrome. As your error is a standard error and might not because of your code but due to some configuration settings.