Question

FME Server Could Not Connect to Core

  • 16 August 2017
  • 9 replies
  • 15 views
deanhowell
Badge +9

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.

9 replies

redgeographics
Rank
Userlevel 4
Badge +25

Did you try the FME Server Troubleshooting guide?

deanhowell
Badge +9

Did you try the FME Server Troubleshooting guide?

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
Rank
Userlevel 1
Badge +18

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
Badge +9

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
Rank
Userlevel 1
Badge +18
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
Badge +9

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

caicedop

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
Badge

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

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.

Reply


Community Stats

28,631
Posts
109,159
Replies
36,510
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.