Skip to main content

This article covers setting up FME Form & Flow Emailer transformers, but doesn't cover the System Email setup in FME Flow.


https://support.safe.com/hc/en-us/articles/25407404506253-How-to-Connect-to-Microsoft-Exchange-Online-using-OAuth-2-0-Microsoft-Modern-Authentication

That page has much fewer settings available than the transformers:



The docs don’t mention how to use Client ID (UI notes this as Microsoft OAuth only)
https://docs.safe.com/fme/html/FME-Flow/WebUI/System-Email.htm
 

What are the steps needed to set up System Email with Microsoft OAuth?
Do we need to register an SMTP Account & Password rather than use Client ID / Client Secret?

Can you hit Test and see what error message you get back

https://support.safe.com/hc/en-us/articles/25407557880205-FME-Flow-Troubleshooting-Email

Often the ports are not opened if you didn’t install Flow with the Service Account that might run flow services. You may need to check with IT network admin that the following ports 25 and 587 are open on the hosting machine:

https://docs.safe.com/fme/html/FME-Flow/ReferenceManual/FME-Flow-Ports.htm

 


Hi,

Here’s the error:

Failed to start following subscriber process: Error communicating with FME Flow host localhost. Contact your FME Flow administrator who can investigate the log files for further details. Also see: http://fme.ly/e100007#error-communicating-with-fme-server-hostConnection refused: connect

 


lots of potential causes you need to one by one check over:

1. The FME Flow installation was initially completed using the express option, and FME Engines were later added to a separate machine. However, the necessary database update step was missed, resulting in the Engine host being unable to locate the System Database.

2. The hostname reported by the FME Engine machine is not resolvable by the FME Flow Core.

3. The FME Engine is unable to establish a connection with the System Database.

4. There is a time zone mismatch between the Core and Engine hosts.

5. Essential network ports are blocked or closed.

6. The Engines are failing to connect to the Job Queue