Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > The Windows Schedule Tasks reports "Network path was not found" error

The Windows Schedule Tasks reports "Network path was not found" error

Overview

The Windows Schedule Tasks reports a Network path was not found error on a node running Windows Server 2003.

Environment

All SAM versions

Cause

The target node is down during the polling of tasks.

The specified credentials do not have permission to access the task files location (By default this path is set to: C:\Windows\Tasks.)

Resolution

Make sure that the target node is not down before polling.

Make sure that the specified credentials have permission to access the task files location.

 

Last modified

Tags

Classifications

Public