Skip to main content
Question

FME Server Could Not Connect to Core

  • August 16, 2017
  • 9 replies
  • 161 views

deanhowell
Influencer
Forum|alt.badge.img+24

Our installation of FME Server has just stopped working.

All services are running but I have noticed in the Engine Logs that it is struggling to register engine.

2017-08-16 14:46:58| 0.3| 0.3|INFORM|FME(R) 2017.0.1.1 (20170512 - Build 17291 - WIN64)

 

2017-08-16 14:46:58| 0.3| 0.0|INFORM|FME_INSTANCE_NAME FMEQAS901_Engine1

 

2017-08-16 14:46:58| 0.3| 0.0|INFORM|Registering with FME Server on host 'localhost'...

 

2017-08-16 14:46:58| 0.3| 0.0|ERROR |FME Engine failed to register with FME Server 'localhost' on port 7070: Could not establish connection to host

Any advice would be welcomed.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

9 replies

redgeographics
Celebrity
Forum|alt.badge.img+59
  • Celebrity
  • 3700 replies
  • August 16, 2017

deanhowell
Influencer
Forum|alt.badge.img+24
  • Author
  • Influencer
  • 315 replies
  • August 16, 2017
Yes tried the troubleshooting guide but still nothing. I added local host entry, changed directly permissions, started the services (many times), tried accessing it from remote machine and much more :)

 

 


stalknecht
Contributor
Forum|alt.badge.img+21
  • Contributor
  • 305 replies
  • August 16, 2017

Can you check if the port is not blocked by a firewall.

In case the engine is on the same machine

open a cmd-prompt  on the server and type:

netstat -na | find "7070"

it should return:

  TCP    0.0.0.0:7070           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:7070         127.0.0.1:61320        TIME_WAIT

deanhowell
Influencer
Forum|alt.badge.img+24
  • Author
  • Influencer
  • 315 replies
  • August 16, 2017

Can you check if the port is not blocked by a firewall.

In case the engine is on the same machine

open a cmd-prompt  on the server and type:

netstat -na | find "7070"

it should return:

  TCP    0.0.0.0:7070           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:7070         127.0.0.1:61320        TIME_WAIT
I get no result when running the netstat command. Does that mean I need to add something to our firewall settings?

 

 


stalknecht
Contributor
Forum|alt.badge.img+21
  • Contributor
  • 305 replies
  • August 17, 2017
I get no result when running the netstat command. Does that mean I need to add something to our firewall settings?

 

 

Try turning it of to confirm it works without and immediately switch it on and add an exclusion to the firewall.

 

 


deanhowell
Influencer
Forum|alt.badge.img+24
  • Author
  • Influencer
  • 315 replies
  • August 17, 2017

It turned out to be a database issue, where our Oracle database was locked.


caicedop
  • 2 replies
  • June 29, 2020

Can you check if the port is not blocked by a firewall.

In case the engine is on the same machine

open a cmd-prompt  on the server and type:

netstat -na | find "7070"

it should return:

  TCP    0.0.0.0:7070           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:7070         127.0.0.1:61320        TIME_WAIT

Hi, when you say "on the server", do you refer to the web server where tomcat is running or Core/Engine server? Thanks.


daraghatsafe
Forum|alt.badge.img
  • 135 replies
  • July 2, 2020

Hi, when you say "on the server", do you refer to the web server where tomcat is running or Core/Engine server? Thanks.

Hi @caicedop, I believe in this case they are referring to a Core/Engine.


caicedop
  • 2 replies
  • July 3, 2020

Hi @caicedop, I believe in this case they are referring to a Core/Engine.

In that case, the port 7070 is open and server is listening on that port. According to the logs the engine registers with no issue, but still getting "There was a problem communicating with the REST API" error.