Do you know if an update to the emailer transformer can cause a bug in FME Server?

Hi @julianshom​ ,

What version of the Emailer do you have? In FME Workbench, are you able to upgrade the package before publishing it to FME Flow (Server)? Is the Emailer running successfully in FME Workbench and only failing in FME Flow (Server)?

Workspaces that fail on FME Flow (Server) are resubmitted 3 times before failing. Is this what you're experiencing with the looping? You can change the number of retries if needed. See Job Recovery documentation for more detail.

Thanks,

Kezia

Yes if a workspace is crashing on FME Flow it will be resubmitted 3 times. You might be able to get some more Information about the details of the crash in the fmeprocessmonitorengine.log file 

Resources>Logs>engine>current>fmeprocessmonitorengine.log

Best thing would probably be to update the email transformers/packages and republish the workspaces. 

One thing you can try and test is to just copy one of those old email transformers into a new simple workspace and just test like that.  

Hi @keziaatsafe​ and @virtualcitymatt​ thank you for the answer.

So my problem has two decorrelated elements. I was able to set up my FME Servers to avoid restarting processing in case of a failure.

The version of the emailer I am currently using is version 3.3.3.

I tested with FME Desktop (as @virtualcitymatt​ proposed with a creator and emailer) and it works on my machine but on some of my colleagues' machines the workflow does not work with this error message

There is a known Windows bug that may cause instability when using Python in the current locale. Please update to Windows 10 version 2004 and greater, or to Windows Server 2022. See http://fme.ly/nw5 for more details.

Do you think that a different python setting can change the behaviour of the emailer?

Thank you in advance and have a nice day,

For your information we have managed to get the emailer working with FME Desktop by changing the region of the windows server and the machines from France to English (Canada).

We therefore believe that an encoding problem in the localization of the plugin may be the source of our problem.

We are still working on getting it to work with FME Server.

Do you think that a reinstallation of FME Server in English would make the emailer work?

Hi @julianshom​ ,

What build of FME Server 2022 are you using? There was a known issue with FME Server 2022.0 on Windows Server in French System Locale, where the FME Server services cannot be started. This article has more detail and a workaround for the services... However, this is the first time I'm hearing that French locale is affecting the Emailer transformer. What are the errors you're seeing in the job log with the Emailer?

Thanks,

Kezia

Hi @keziaatsafe​ ,

The build that we use is FME Server 2022.1.3, 22630.

Yes, we had already seen the problems with the French localisation, but that seemed to be due more to a poor handling of the installation files in French.

My problem is that I don't have a very precise log message. It's as if the treatment stops in the middle of the process.

Thanks for the answer,

Julian.

Check out the fmeprocessmonitorengine.log > you can often find stuff which isn't in the logfile in there.

Logs>engine>current>fmeprocessmonitorengine.log

Hi @virtualcitymatt​ ,

My engine>current>fmeprocessmonitorengine.log give me that (cf image attached) when I test the emailer (creator + emailer).

In our installation it is a specific user that starts the FME Server services, so we are in the process of modifying the localization for this user to see if the emailer works once the setting is changed to English (Canada), as it does with our local use and FME Desktop.

Julian.

Ahh yeah, that's just a crash - my guess is that what you are attempting will fix the issue

Indeed by changing the localization for the user launching the FME Server service my workflows with emailer are working correctly.