Skip to main content
Question

Reader Cannot Access GDB When Running From .bat In Task Scheduler

  • July 30, 2018
  • 4 replies
  • 25 views

Forum|alt.badge.img

Hello. I'm having trouble running a sample translation with Windows Task Scheduler. Ultimately I will need to run multiple translations on weekends.

I'm using a .BAT file with the following text only:

FME C:\\Users\\ ...[[truncated]]... \\Scaler_Test.fmw

The batch file runs in CMD with the above text only, and the translation is successful.

When running this with Task Scheduler, the translation fails and the log is as follows (portion):

...

2018-07-30 10:10:00| 0.2| 0.1|INFORM|Creating writer for format: NULL (Nothing) 2018-07-30 10:10:00| 0.2| 0.0|INFORM|Trying to find a DYNAMIC plugin for writer named `NULL' 2018-07-30 10:10:00| 0.2| 0.0|INFORM|Loaded module 'NULL' from file 'C:\\Program Files\\FME\\plugins/NULL.dll' 2018-07-30 10:10:00| 0.2| 0.0|INFORM|FME API version of module 'NULL' matches current internal version (3.8 20180209) 2018-07-30 10:10:00| 0.2| 0.0|INFORM|Creating reader for format: 2018-07-30 10:10:00| 0.2| 0.0|INFORM|MULTI_READER(MULTI_READER): Will fail with first member reader failure 2018-07-30 10:10:00| 0.2| 0.0|INFORM|MULTI_READER(MULTI_READER): Adding FILEGDB Reader with keyword FILEGDB_1 2018-07-30 10:10:00| 0.2| 0.0|INFORM|Using Multi Reader with keyword `MULTI_READER' to read multiple datasets 2018-07-30 10:10:00| 0.4| 0.2|INFORM|Creating reader for format: Esri Geodatabase (File Geodb Open API) 2018-07-30 10:10:00| 0.4| 0.0|INFORM|Trying to find a DYNAMIC plugin for reader named `FILEGDB' 2018-07-30 10:10:00| 0.4| 0.0|INFORM|Loaded module 'FILEGDB' from file 'C:\\Program Files\\FME\\plugins/FILEGDB.dll' 2018-07-30 10:10:00| 0.4| 0.0|INFORM|FME API version of module 'FILEGDB' matches current internal version (3.8 20180209) 2018-07-30 10:10:00| 0.4| 0.0|INFORM|FILEGDB reader: Building feature table 2018-07-30 10:10:00| 0.4| 0.0|ERROR |Geodatabase Error (-2147024893): The system cannot find the path specified. 2018-07-30 10:10:00| 0.4| 0.0|ERROR |Could not open File Geodatabase dataset `S:\\ [[filepath redacted]]' for reading

...

I've tried using UNC paths in place of the mapped drive in the Reader, but is breaks the translation completely.

Thanks.

Windows Server 2012 R2

FME Desktop 2018.0 64BIT; Server not installed

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

erik_jan
Contributor
Forum|alt.badge.img+22
  • Contributor
  • 2179 replies
  • July 30, 2018

When running from the task manager, the user is most likely not logged on.

Therefor the user to run the task (system user?) has no privileges on the specified folder and file.


Forum|alt.badge.img
  • Author
  • 20 replies
  • July 30, 2018

When running from the task manager, the user is most likely not logged on.

Therefor the user to run the task (system user?) has no privileges on the specified folder and file.

@erik_jan

 

Do the preferences below compensate for that? If not, what privileges should be changed?

 

 

This user has Administrator access.

 

 

 

 


erik_jan
Contributor
Forum|alt.badge.img+22
  • Contributor
  • 2179 replies
  • July 30, 2018
@erik_jan

 

Do the preferences below compensate for that? If not, what privileges should be changed?

 

 

This user has Administrator access.

 

 

 

 

The log fragment indicates the GDB is read from the S: drive.

 

Is that drive available when no user is logged on, or is that drive created as part of the user logon script (as it usually is)?

 

 


Forum|alt.badge.img
  • Author
  • 20 replies
  • July 30, 2018
The log fragment indicates the GDB is read from the S: drive.

 

Is that drive available when no user is logged on, or is that drive created as part of the user logon script (as it usually is)?

 

 

Not sure. I changed the preference above to "Run only when user is logged on" and received the same result. @erik_jan