FMEServerJobSubmitter unable to connect to FME Server

Hi @stephaneo​ ,

If you go to FME Options > Web Connections and try to authenticate your FME Server connection from there does it work?

After the upgrade did you reconfigure for HTTPS, change your password, or anything else that could mean the saved connection details are no longer correct?

Hi @stephaneo​ ,

Thanks for checking. Just to confirm does this error only happen when you publish and run the workspace containing the FMEServerJobSubmitter to your FME Server? If you try and run the workspace from FME Desktop do you get the same error or does it work?

Hi @stephaneo​ ,

I also wanted to check if your FME Server is set up to use a proxy (https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/Using_FME_Server_with_Proxy_Server.htm)?

Hi stephaneo and all,

we have the same problem after upgrading from 2020 to 2021. In FME Desktop everything is fine but after running of FMEServerJobSubmitter on FMEServer the job fails.

Is this a bug or what about backward compatibility? We can not immediately install FME Desktop 2020 but I suppose that it's necessary to Upgrade the FMEServerJobSubmitter?

Do you have a solution to solve the problem?

Best regards,

Matthias

Hi,

Edit all your workspace and use "embed connection parameters"

@safe: Yes, we use a proxy, what is the difference between web connection 2020 and 2021? Also with FME Desktop 2021 and FME Server 2021 it's not working, only by using embedded connection.

Hi @florenz​ ​,

cc @stephaneo​ , @mattenp​ 

Thank you for tagging me - I’m sorry I missed the latest chatter on this thread. I have spoken with a colleague and he made me aware of an issue that I think is likely the cause of the problem you are all encountering.

A new parameter ‘Verify SSL Certificates’ was introduced for the FME Server Web Connection configuration in FME Desktop 2021. Unfortunately, this parameter isn’t currently exposed in the FME Server Web UI (the internal reference tracking this is FMESERVER-16742) and in FME Server, the value set for this parameter is being saved in the Web Service definition rather than the individual connection. It appears that for any web connections that were restored from an older version of FME this parameter is being set to ‘Yes’ by default. Since it’s set in the web service definition, any new FME Server connections published in 2021 after a restore will also try to verify SSL certificates even if this is explicitly set to no in the connection details because it is using the Web Service that was defined by the restore from 2020 or older. Embedding the connection details resolves the problem because you are no longer using the web service definition to submit the authorization request. 

There are a couple of ways you can workaround this problem: 

Option 1: Import your SSL Certificate via Internet Options. First, export your certificate as Base 64 encoded following the first four steps on this article. Then, from the machine FME Server is installed on search for Internet Options > Content > Certificates > Import and run through this wizard, selecting the .cer file you just downloaded as the one to import. You should restart your browser and then try running your job again. The FMEServerJobSubmitter should now work. 

Option 2: Delete the Web Service Definition from FME Server through Web Connections > Manage Services > Remove (Note this will also remove any existing Web Connections) and then republish a connection from FME Server 2021 or newer. This will reload the Web Service so that the Verify SSL parameter is correctly set to ‘No’ in the definition. You can then re-perform your restore to import any other FME Server connections that may have been removed (make sure overwrite is not checked, so the web service definition isn’t reverted back). 

Please let me know if you have any further problems after working through either of these options.

Hi jpvo,

yes it's a known issue, but there is a workaround. https://community.safe.com/s/article/FMEJobSubmitter-unable-to-connect-to-FME-Server-after-upgrading-to-2021-x Option 2 was the best for us.

Best regards,

Matthias