Puzzling exception

[bgowland]

Trying to solve a problem in the nDroid service when users have videos/music media on network shares I find I can't enumerate the directories when the path is the root of a mapped network drive.

Using this code where foldername is Z:\

Code:

List<string> folderList = null;
try
{
    folderList = new List<string>(Directory.GetDirectories(folderName, "*.*", SearchOption.TopDirectoryOnly));
}
catch (DirectoryNotFoundException dnfe)
{
    Log.LogException("GetMediaFolderContents() - enumerating folders", dnfe);
    return "";
}

...I catch a DirectoryNotFoundException logged as

Code:

GetMediaFolderContents() - enumerating folders threw exception: Could not find a part of the path 'Z:\'.   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption)
   at System.IO.Directory.GetDirectories(String path, String searchPattern, SearchOption searchOption)

According to the MSDN page for Directory.GetDirectories that exception reason is "The specified path is invalid (for example, it is on an unmapped drive)." but the drive IS mapped and the nDroid service has permission to access it.

The weird thing is what I'd expect to fail is passing the sharename into that function (\\myserver\music\) but that actually DOES work. :confused:

This is only happening for mapped networked drives - D:\ for example (which is local), works fine.

Anybody seen anything like this? Got a cure?

[mvallevand]

Is this related to your other post where I wrote about "Local System" issue http://forums.nextpvr.com/showthread.php...post431289 ? You won't see mapped drive letters either.

Martin

[bgowland]

Is this related to your other post where I wrote about "Local System" issue http://forums.nextpvr.com/showthread.php...post431289 ? You won't see mapped drive letters either.

Yes and no but I think you've just pointed me in the right direction.

No I'm not using LocalSystem to run the service, I'm using my usual account which currently has Z: mapped.

But of course the account details just provide login / user privileges and it doesn't mean it's sharing my current user process so the service process doesn't have a Z: mapped. Doh!

At least that explains it. Thanks.