Skip to main content
Solved

Your Job has been submitted does not run


perry
Forum|alt.badge.img+2

Hello,

 

I've updated FME server V2018 to V2019.2.3

Unfortunately nou the scheduling does not run.

There are no scheduled tasks in the que.

If I manually start a job at the server it appears in the que but does not run at all.

Wich services are responsble for the schedular. Do they have to run with SYSTEM?

Or do all the services have to run with SYSTEM?

 

thanks for your reply

 

Best answer by perry

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.

View original
Did this help you find an answer to your question?

4 replies

david_r
Celebrity
  • February 7, 2020

When you did the update, did you follow the manual and also make sure to not keep the old internal FME Server database?


perry
Forum|alt.badge.img+2
  • Author
  • February 7, 2020

yes, we followed the instructions server V2019.


david_r
Celebrity
  • February 7, 2020

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.


perry
Forum|alt.badge.img+2
  • Author
  • Best Answer
  • February 7, 2020

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.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings