Skip to main content
Question

Running a workspace using a .bat file

  • November 18, 2015
  • 4 replies
  • 60 views

mbaer
Contributor
Forum|alt.badge.img+1
  • Contributor
  • 7 replies
When I schedule a .bat file that runs my FME workspace through windows task scheduler it returns a 0x2 error but when I run the .bat file manually it works fine.
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.

4 replies

mbaer
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • 7 replies
  • November 18, 2015
It is scheduled with admin rights to the machine so it has rights. I am still getting the same message. What should be in the "Start in " parameter be set to pint to? I have not made any changes to the scheduler besides setting times for the triggers and setting up the action.

david_r
Celebrity
  • 8391 replies
  • November 23, 2015
It is scheduled with admin rights to the machine so it has rights. I am still getting the same message. What should be in the "Start in " parameter be set to pint to? I have not made any changes to the scheduler besides setting times for the triggers and setting up the action.

The "Start in" parameter should be set to the FME_HOME directory.

If you still cannot get it to work, consider looking for related error messages in the Windows event logs.


david_r
Celebrity
  • 8391 replies
  • November 23, 2015
It is scheduled with admin rights to the machine so it has rights. I am still getting the same message. What should be in the "Start in " parameter be set to pint to? I have not made any changes to the scheduler besides setting times for the triggers and setting up the action.

I checked the error code, and it points to insufficient rights. Just be aware, that the scheduled events run with restricted privileges by default, even though the user might be local admin. You will have to specifically assign full admin privileges on a per-task basis, see here:

Access denied (0x2) error as an administrator in Windows Task Scheduler


Forum|alt.badge.img
  • 49 replies
  • November 19, 2018

The "Start in" parameter should be set to the FME_HOME directory.

If you still cannot get it to work, consider looking for related error messages in the Windows event logs.

Thanks - yes, I needed to set the FME_HOME directory (same path as FME.exe).