Hi Till,

just add a line to "<FMEServerHome>\Server\processMonitorConfigEngines.txt":

NODE_OVERWRITE=true

on your engine only host machine. This will allow to config the desired number of engines by the START_ENGINE_* lines.

This is also in the documentation, but perhaps not where expected:

http://docs.safe.com/fme/html/FME_Server_Documentation/Default.htm#AdminGuide/Install_32_and_64_Bit_Engines_On_Same_Machine.htm?Highlight=NODE_OVERWRITE

It's possible that the engine machine has not been given access to the database on the core machine. Take a look at the following article: https://knowledge.safe.com/articles/20008/unable-t...

Hm, just saw this. I did find an error in the file mentioned and restarted both the core and the engine. It still does not work.

NODE_OVERWRITE=true

Just wondering if this is still the recommended way to do this in FME2019 also? Ie edit the processmonitorconfigengines.txt? It seems that the new web GUI lets you input these parameters directly in the webgui, but it seems not to always "obey" this number in an environment with many engines. Also when restarting the core or engine it sometimes "picks up" the number from the processmonitorconfigengines and not the "database/webgui" ? 

Hi @sigtill, No, this wouldn't be the recommended way to manage the number of engines to start in 2019. If you're seeing the number of engines as set in the web interface being 'forgotten' when restarting the core or engine services, that sounds like a problem that we'd want to investigate and resolve. Are you seeing that kind of behaviour very frequently? Would you mind reporting that to use through: https://www.safe.com/support/report-a-problem/ ?

Yes, I`ll try to debug with the client a bit more and then report an issue to figure out if it is a browser issue, load balancer issue, network issue etc. I will file a support-case when I have enough info, thanks @lauraatsafe