When you did the update, did you follow the manual and also make sure to not keep the old internal FME Server database?
yes, we followed the instructions server V2019.
If the server works with the services running as local system, but not as the dedicated service account, I would assume that the service account doesn't have the necessary rights.
Hi David,
I've found this item:
Confirm the paths to the FME Engines are valid by looking in the process monitor configuration
file here:
FME Server 2015 and newer: \\Server\\ processMonitorConfigEngines.txt
The paths to the FME Engines are visible near the end of the file:
I have replaced this file with out backup file. Now the scheduling is recognized en jobs are in the que and running.
I still do not know why or if this is the solution, but I'm glad the scheduling is working.
I will monitor this the next few days. for now thanks.