Skip to main content
Question

Scheduling Job on FME Server 2016

  • February 12, 2016
  • 6 replies
  • 17 views
erik_jan
Contributor
Forum|alt.badge.img+22

I created a workspace and tested it in FME Desktop.

Then published it to FME Server and tested it again.

Created a schedule to run the job this morning (and every day) at 07.00 (it is now 08.10).

Next I edited the workspace, tested and republished it (no changes to parameters).

Checked the schedule and it was still valid and enabled.

But no jobs where executed at the scheduled time (no passes and no failures).

My machine was locked and running (no shutdown).

Any suggestions why my job has not run?

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.

6 replies

stalknecht
Contributor
Forum|alt.badge.img+21
  • stalknechtContributor
  • Contributor
  • 305 replies
  • February 13, 2016

Anything inside the log-files?

fmelizard
Safer
Forum|alt.badge.img+20
  • fmelizardSafer
  • Safer
  • 3719 replies
  • February 15, 2016

Does the job appear as queued or running? Or did never get submitted it all?

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Author
  • Contributor
  • 2179 replies
  • February 15, 2016

The issue was solved after recreating the schedule.

I still don't have a clue why it did not run in the first time.

It did not even start, so no entries in any log files.

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Author
  • Contributor
  • 2179 replies
  • February 15, 2016

Does the job appear as queued or running? Or did never get submitted it all?

@kenbragg The job never got submitted. And I checked the date and time more than once. After recreating the job ran this morning without problems.

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Author
  • Contributor
  • 2179 replies
  • February 16, 2016

But again this morning the schedule was not executed.

I changed it to 10.00 AM yesterday and FME server executed the job (Succeeded.)

I changed it back to 07.00 AM starting on Feb.16 after the 10.00 AM execution expecting the job to run this morning and daily after that.

But no execution or job queuing was performed.

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Author
  • Contributor
  • 2179 replies
  • February 18, 2016

OK, I finally figured it out:

On Windows 10 (and perhaps earlier versions too) a power setting can cause the machine to shutdown instead of hibernating.

And that will cause FME server to shut down too.

This can be solved to switching to the "Maximum performance" power setting, which avoids the shutdown.

Community Stats

32,100
Posts
121,893
Replies
39,744
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.