Automation Fails with “The Network Path Was Not Found” When Exporting Files in Toad (4313434)

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Automation Fails with “The Network Path Was Not Found” When Exporting Files in Toad
Description
An automation task runs successfully when executed manually but fails when scheduled. The failure occurs during the export phase of a Select to File activity.

Observed behavior:
- Automation starts and connects to the database successfully
- Execution script begins normally
- Export process fails with error:
  “File_1 - The network path was not found.”
- The issue occurs intermittently but typically on the first activity
Example log: 4/27/2015 10:25:50 AM: Begin execution script activities
4/27/2015 10:25:50 AM: Begin Export of File_1
4/27/2015 10:25:50 AM: Connection established
4/27/2015 10:26:30 AM: File_1 - The network path was not found
4/27/2015 10:26:30 AM: Failed
Cause

The issue is caused by network access and mapping limitations during scheduled execution. When the automation runs in the background (such as via Task Scheduler or Toad automation scheduler), the process may not have access to the network location, even when a UNC path is used.

Although the UNC path is specified and the user has access, the system context running the automation may not properly resolve or maintain access to the network share.
Resolution
Ensure the network location is properly mapped and accessible before running the automation.

Workaround: Map the Network Drive
1. Map the network folder as a drive on the local machine.
2. Ensure the mapping is available to the user or system account running the automation.
3. Update the automation:
  - Either continue using the UNC path
  - Or use the mapped drive path
4. Rerun the scheduled automation and verify the export completes successfully.
  
  Once the network drive is mapped, the issue typically does not occur.
Additional Information

Scheduled automations often run under a different user context or session than interactive executions, which can impact access to network resources. Even when UNC paths are used for portability, some environments require explicit network drive mapping to ensure stable access during unattended execution. This behavior may also apply to other activities such as file copy operations, including those involving SharePoint or remote file systems.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Automation Fails with “The Network Path Was Not Found” When Exporting Files in Toad (4313434)

Title

Description

Cause

Resolution

Workaround: Map the Network Drive

Additional Information

Leave a Comment