Hi @mattw1ilkie​ ,

As a general note, you should never use an FME Desktop version later than your FME Server version. Even though those versions are close there is potential for problems. If you are able would you be able to create a workspace in a version equal or lesser than FME Server and test that. I would also try to confirm that there are no proxy's set up in either environment that might be interfering with the SSL authentication.

Thank you Richard. I've installed the latest FME Server (Jan 12 2021 release) on a different machine and we'll see if that works better. I've had some troubles getting that install working though so won't be able to follow up here until that one is solved (ref).

After working with @richardatsafe​  on the phone we've verified that 2021-01-21 release fixes the ssl error.

It's unlikely the disparity between Desktop and Server caused the error (but nevertheless it's still recommended-to-required to keep their versions synchronized).

Unfortunately this is wrong. The script does work fine on the 2nd fme server instance, running v2020.2.2, that we tested on. However after upgrading the 1st server to v2020.2.2 also the SSL error persists. So there's something about the primary environment that is different and not related to the fme server version.

In some cases when the FME Server Engine account is run under the same account as a FME Workbench on the same machine a custom interpreter set for on FME Desktop can be picked up by the FME Server Engine. This can prevent the reader from finding the correct module. You can confirm nothing is set for the engine account by checking the registry settings: Computer\\HKEY_CURRENT_USER\\Software\\Safe Software Inc.\\Feature Manipulation Engine\\Python

Thank you for remembering to come back and update this thread Richard. Under the press of other duties I had forgotten. (Also your description is much more concise than my personal solution notes!)

SUMMARY

Problem: We get the error "Can't connect to HTTPS URL because the SSL module is not available." when running a workspace on FME Server but the same workspace run from FME Desktop on another machine is okay. The same script published to another FME Server instance is okay. Additionally, sometimes the server run does work. Curiously, after a failed run for a period of time afterward other previously fine scripts will also fail, and then later resume being successful. The same SSL error is reported in all of the failed cases.

• Job# : Result
• 347,348 : "Old faithful" script runs successfully
• 349 : Problem script fails
• 350-352 : "Old faithful" fails
• 353+ : (off screen) Reliable script successful again, all subsequent runs also successful

Cause: The machine has side by side installs of FME Server and Desktop. The Desktop FME is using a custom python environment. For reasons not understood, occasionally FME Server is finding and using the custom environment. (It's not supposed to use custom unless specifically instructed, but something is making that go awry.)

Solution: 

Choose between FME installs and not use the other. For us FME Server wins.

 To disable the FME Desktop custom python environment. Set the Desktop FME python registry key "Use Custom Python 64" to "false" (or rename the keys with path values).

HKEY_CURRENT_USER\\Software\\Safe Software Inc.\\Feature Manipulation Engine\\Python