FME Flow Could Not Connect to FME Core

Symptom

After logging in to the Web User Interface, the following message is displayed:

Could not connect to FME Core.
Please ensure that it is running.

Cause

This issue generally appears when the FME Core and Database services are unavailable or cannot be started. As well, this can occur in a system designed for Core Failover. If the location of the services is not be visible to the FME Flow (formerly Server) Application service or the services have not been configured correctly, the Web Application server would not be able to connect to the core.
 

Resolution

The following is a set of solutions that may correct the issue. Please run through each solution and after making any changes, check the Web User interface to see if the error message has been removed.

Services

Using this guide, test that the services are running correctly.

Permissions

Ensure that the user running the FME Services has permissions to read/write to the installation directory and see if the problem is resolved after making changes. To change the user running the service, see this guide.

Ports

On a distributed setup, you need to allow connections on the FME Flow Core Service machine (usually port 7071). For a detailed look at the FME Flow's required ports see here.

• For Windows, take a look at Windows Firewall. Try turning it off briefly to test if this is the cause of the issue.
• For Linux, take a look at iptables.

Active Directory

If you have configured Active Directory integration (especially if you are currently attempting to configure it and start receiving this error message), please take a look at the Active Directory Troubleshooting section of the FME Flow documentation. Issues connecting to Active Directory could completely prevent the FME Flow core from starting up.

DNS

Try connecting to FME Flow from the machine where it is installed using http://localhost/fmeserver. If that returns an error saying the webpage is not available, there could be a problem with the DNS configuration on the machine. To confirm this, check the entries in the hosts file for the machine:

• Locate the following directory: C:\Windows\System32\drivers\etc
• Open the hosts file with a text editor
• Add a mapping for localhost by including the following line in the file: 127.0.0.1 localhost
• Save your change and restart FME Flow

Post Installation Failover Configuration

On an installation designed for core failover, make sure that you have configured all additional installation steps. See documentation here.
 

Additional Support

If the solution is still not resolved, check the following sources for error messages:

• FME Flow logs.
• Window Event Viewer. Look for errors relating to FME or PostgreSQL.
• PostgreSQL database logs. Note: Error reporting must be configured, see PostgreSQL error reporting and logging setup .

If an error message is found, search back in the FME Community for a solution or contact Technical Support for further assistance.