Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="https://stackoverflow.com/questions/3098486/cannot-access-files-on-drive-mapped-network-share-from-a-windows-service">This SO post</a> describes a similar scenario to what you've described. </p> <p>One of the links posted as a response to that question led me to <a href="http://msdn.microsoft.com/en-us/library/ms685143.aspx" rel="nofollow noreferrer">this MSDN article</a> which provides a variety of reasons as to why one might encounter errors when trying to access shared network drives by using a mapped drive letter. </p> <p>Microsoft's suggestion (see below) is to simply use a UNC path.</p> <blockquote> <p>A service (or any process running in a different security context) that must access a remote resource should use the Universal Naming Convention (UNC) name to access the resource.</p> </blockquote> <p>To answer your actual question more specifically, with regards to why it suddenly can't access the network share, I would venture a guess to say that the network share is being disconnected by Windows due to an idle timeout, as discussed in <a href="http://support.microsoft.com/kb/297684" rel="nofollow noreferrer">KB297684</a>. Any attempt to access the disconnected drive will be met with a small wait as the connection to the network share is re-established, which could presumably be what is causing your issue.</p> <p>To test this theory, try writing some data to a file on the network drive at a relatively short interval (every 10 minutes, perhaps?) to try and <em>convince</em> Windows that the drive is still active.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload