Consideration
After logging in to the Web User Interface, users may see the following message:
Could not connect to FME Core.
Please ensure that it is running.
This happens in FME Flow when the Web Application Server cannot reach the FME Core service.
Why This Happens
This message generally appears when:
- The FME Core and FME Flow Database services are unavailable or cannot start.
- The system uses a Core Failover configuration, and the Web Application Server cannot locate the active FME Core.
- The FME Flow Application Server cannot see the service location, or the service is not configured correctly. In these cases, the Web Application Server cannot connect to FME Core.
How to Resolve It
Work through each option below. After making a change, check the Web User Interface to see if the message is resolved.
Option 1: Check the FME Flow System Services
Use this guide to test that the FME Flow system services are running correctly: About the FME Flow System Services
Option 2: Check Permissions
Confirm that the account running the FME Flow system services has read/write permissions to the FME Flow installation directory. To change the account that runs the service, see: Running the FME Flow System Services Under Different Accounts (Windows)
Option 3: Check Ports
On a distributed installation, allow connections on the machine running the FME Flow Core service (usually port 7071). For a full list of required ports, see: FME Flow Ports
- On Windows, check Windows Firewall settings. Temporarily disable the firewall to test whether it is blocking the connection.
- On Linux, check the iptables configuration.
Option 4: Check Active Directory Configuration
If Active Directory integration is configured, or is currently being set up, see: FME Flow Troubleshooting: Windows Active Directory. Problems connecting to Active Directory can prevent FME Core from starting.
Option 5: Check DNS Configuration
From the machine where FME Flow is installed, try connecting to FME Flow using http://localhost/fmeserver. If the page is not available, the machine may have a DNS configuration issue. To confirm this, check the entries in the hosts file:
- Open the following directory:
C:\Windows\System32\drivers\etc - Open the hosts file with a text editor.
- Add a mapping for localhost by adding this line:
127.0.0.1 localhost - Save the change and restart FME Flow.
Option 6: Check the Failover Configuration
On an installation designed for Core Failover, confirm that you completed all additional installation steps. See: Install the FME Flow Core and FME Engines
If the message persists, check the following sources for error messages:
- FME Flow logs.
- Windows Event Viewer. Look for errors relating to FME or PostgreSQL.
- PostgreSQL database logs. Error reporting must be configured; see PostgreSQL error reporting and logging setup.
If an error message is found, search the FME Community for a solution, or contact Support for further assistance.