Skip to main content
insightsoftware Docs insightsoftware Docs
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Mapped drives do not work in the Jet Scheduler

Overview

In many instances, using "mapped drives" (where a driver letter such as P:, R:, S:, etc. is assigned to a network location) will not work with scheduled tasks.

For example:

The drive letter "S:" may be mapped to a network location such as "\\server_name\folder_name"

When the scheduled task is run by the Windows Task Scheduler (WTS), the WTS may not know how to map the drive letter to that network location and you see an error similar to "The input path "S:\report_name.xlsx" is not a valid file or directory.

Resolution

In the Jet Scheduler, instead of the driver letter, use the full path name.

So, for the above example:

Instead of this format Use this format
S:\report_name.xlsx \\server_name\folder_name\report_name.xlsx

Published:

Mapped drives do not work in the Jet Scheduler

Overview

In many instances, using "mapped drives" (where a driver letter such as P:, R:, S:, etc. is assigned to a network location) will not work with scheduled tasks.

For example:

The drive letter "S:" may be mapped to a network location such as "\\server_name\folder_name"

When the scheduled task is run by the Windows Task Scheduler (WTS), the WTS may not know how to map the drive letter to that network location and you see an error similar to "The input path "S:\report_name.xlsx" is not a valid file or directory.

Resolution

In the Jet Scheduler, instead of the driver letter, use the full path name.

So, for the above example:

Instead of this format Use this format
S:\report_name.xlsx \\server_name\folder_name\report_name.xlsx

For an optimal Community experience, Please view on Desktop