Consideration
FME Flow may fail to load completely in the web browser when using AnyDesk Virtual Machine after installation or a restart. Symptoms include seeing only the "Backup and Restore" page, or the following browser errors:
"Error communicating with FME Flow host."
"FME Flow could not connect to FME Core."
The following errors may also appear in fmeserver.log or fmeconfiguration.log:
An error occurred while running the post-install scripts: The post-install scripts were unable to create the necessary connections to FME Flow.Unable to connect to process during startup. Failed to connect to host localhost on port 707-org.postgresql.util.PSQLException: Connection to localhost:7082 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Why This Happens
FME Flow requires exclusive use of several ports to operate correctly. AnyDesk uses port 7070 by default, which conflicts with one of FME Flow's required ports. Conflicts may also occur on ports 7500 or 7076, or others, depending on the services running on the machine.
How to Resolve It
1. Reconfigure AnyDesk
In AnyDesk, navigate to Settings > Connection > General and change the listening port to one not used by FME Flow. Restart the machine to apply the change.
If you are using a port pool for Distributed Engines, ensure the updated AnyDesk port is not included in the pool defined in fmeServerConfig.txt under FME_SERVER_PORT_POOL.
2. Identify and Free Conflicting Ports
If reconfiguring AnyDesk doesn't resolve the issue, identify which services are using FME Flow's required ports and free them. Please follow the steps for your operating system, then continue to step 3.
Windows:
Open Command Prompt as Administrator and run:
netstat -ano
To identify the service associated with a PID in the output, run:
tasklist /fi "pid eq <PID>"
This information is also available in Windows Task Manager under the Details tab. If a required FME Flow port is occupied, end the conflicting process via Task Manager (End Task) or reconfigure FME Flow to use a different port.
Linux:
Open a console as the root user and run:
netstat -apn
If a required FME Flow port is occupied, end the conflicting process:
kill <PID>
Or reconfigure FME Flow to use a different port.
3. Restart FME Flow Services
After freeing the ports, restart FME Flow Services and rerun the netstat command to confirm FME Flow now occupies the required ports.
4. Run the Post-Configuration Scripts
With all required ports available, manually run the post-configuration scripts to ensure all components are correctly installed. Run the scripts in <FMEServer Install Directory>/clients/utilities as an administrator (.bat files on Windows, .sh files on Linux):
- AddCleanUpTasks
- AddPublishers
- AddQueueNode (2018 only)
- AddServices
- AddSubscribers
- configureDemoWorkspaces
Restart FME Flow Services, then log into your FME Flow web application.
Additional Resources
If you are still experiencing issues, consult the Web Interface troubleshooting guide or contact Safe Software Support.