Solved

FME server: Error submitting a job [only manually started]

  • 6 February 2020
  • 2 replies
  • 15 views

Badge

Hello,

So we upgraded the server to the latest version and now I can't run a workspace.

The error in the localhost.2020-02-06.log file.

06-Feb-2020 11:24:30.318 SEVERE [https-jsse-nio-443-exec-9] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [JobRunnerForm] in context with path [/fmeserver] threw exception
 javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

When we try in FireFox we get "This is an unsafe certificate". Chrome en Edge mark the certificate as safe.

In the catalina.2020-02-06.log:

COM.safe.web.client.SelfSignedTrustManager.checkServerTrusted Server certificate chain received:
Certificate #1:
[
[
  Version: V3
  Subject: CN=internalservername, OU=X, O=Y, L=Z, C=BE
  Signature Algorithm: SHA256withRSA, OID = 1....

  Key:  Sun RSA public key, 2048 bits

We tried every method that we could find:

https://knowledge.safe.com/articles/19708/pkix-path-issues-when-configuring-ssl-for-fme-serv.html

https://knowledge.safe.com/articles/49624/fme-server-and-https-troubleshooting-guide.html

... but nothing works.

It only applies to manually running workspaces, scheduled job work just fine.

Could it be there an "error" in the backupfile that I restore?

 

Sincerely yours,

Jonathan

icon

Best answer by jayqueue 10 February 2020, 09:25

View original

2 replies

Badge

Solved.

There were 2 cacerts

 Directory of C:\Program Files\FMEServer\Server\fme\jre\lib\security

08/12/2019  16:37           101.493 cacerts
 
 Directory of C:\Program Files\FMEServer\Utilities\jre\lib\security

06/02/2020  11:13           104.367 cacerts

I copied cacerts from \Utilities\jre\lib\security\ to \Server\fme\jre\lib\security - restarted - FIXED.

Thanks for the above, saved us hours trying to troubleshoot the same issue which wasn't apparent to begin with.

Reply