• This usually affects network paths. Please make sure you use UNC paths rather than drive letters (such as \\Servername\Sharename\Foldername)
  • Test your UNC path in Windows Explorer and let it remember the network credentials (if any).
  • If the scheduler is running as a service, it does not have network access without extra steps. There are two requirements for network access:
  • First, if running as a service, it must be given a log on account. This is done when clicking on the Install… button on the Scheduler tab sheet to install the service. To change the log on account, please uninstall and then re-install the service.
  • Test the account that you assign to the service, by logging in to Windows desktop as a person with the same account. Test that Windows Explorer has access to the volumes that you need. Make sure Windows Explorer remembers the credentials for any network paths.
  • Again, remember that network volumes must be specified using a UNC path such as \\servername\sharename\foldername rather than a mapped drive letter.
  • If this is not sufficient, you can provide a username and password for the network resource in each profile. Use this setting on the Job tab sheet in the profile:
    Network Connections… However, in many cases this is not needed. Rather than specifying the full path for the network connection, you can also try specifying just \\servername.
  • If problems remain, please compare a working and a non-working log file. Take a look at the top, where you can see “Running as” which shows the user account that the jobs run under. They might be different. Log in to the Windows desktop as a person, with the same account that is not working. Test access in Windows Explorer.

  • To change the user account for the service, please stop and uninstall the service and then click “Install” again to specify a different account.

  • For more details, please see Running the scheduler as a service.
Post Category: