Could not find part of the path

Question

Ok, before I say anything else, let me note that I know this has been asked multiple times on SO. However, I have scoured the internet and haven't been able to find a solution for my particular case.

I'm trying to take an XmlDocument object and save it to a network drive. It works perfectly when I try to save it to my local C drive, but when I try to save to a network drive, either testing locally or from an IIS7 web server, I get the error "Cannot find part of the path V:\Test\DocName.xml". Here is the code I am using to try and accomplish this:

using (var stream = new FileStream(Path.Combine(@"V:\Test", doc.DocumentElement.Name + ".xml"), FileMode.Create, FileAccess.Write))
    doc.Save(stream);

doc is, of course, an XmlDocument. I have double and triple checked that I have rights to the directory, and I know for a fact that it exists and is not hidden or anything. Any ideas?

And V is a mapped network drive on the server? And directory Test exists? — Ryan Wilson, May 31 '18 at 17:52
I'd remote into your web server and make sure that it has the V drive mapped correctly. — Ryan Wilson, May 31 '18 at 17:54
What happens if you open Windows Explorer, click the address line, and paste: `V:\Test\\`? Does it open that directory? — ispiro, May 31 '18 at 17:55
It navigates to the directory -- yes, it opens that directory — John Paul Smithdeal, May 31 '18 at 17:55
Also, even if I take out Test and try to save to the root of V:\, the same thing happens — John Paul Smithdeal, May 31 '18 at 17:57
Yep, it's correct...even the error message says it correctly: V:\Test\DocName.xml — John Paul Smithdeal, May 31 '18 at 18:02
Another idea for a test (if you don't want these long shots tell me, I'll go away :) try a simple `File.WriteAllText(...)` to see if that does work. And perhaps also a different file name, in case the current one got locked by your previous tries somehow. — ispiro, May 31 '18 at 18:02
It's a different file name every time, I'm just using that on here as a placeholder. I'll try the WriteAllText thing though — John Paul Smithdeal, May 31 '18 at 18:03
Have you tried the UNC path `\\server\share\path-to\filename.xml`. Drive mappings are per user. Does your app pool user have drive mapped? — MisterSmith, May 31 '18 at 18:14
Yes. Don't forget though, this continues to happen even after I deploy to IIS web server... — John Paul Smithdeal, May 31 '18 at 18:14
I have tried the UNC path, but not the app pool user mapping...how would I do that? It's running under ApplicationPoolIdentity right now and I have impersonation turned on on my site. — John Paul Smithdeal, May 31 '18 at 18:16
https://support.microsoft.com/en-ca/help/257174/using-mapped-drives-with-iis Mapped drives are never supported by IIS. You have to use UNC paths, even if that requires you to learn how to configure access permissions, which would be a different question. — Lex Li, May 31 '18 at 23:11

ispiro · Answer 1 · 2018-05-31T18:28:53.007

0

AFAIK Drive mappings are per user. See more in this answer.

This means that if Visual Studio is not running under the same account as your mappings, it won't find it.

Also IIS is presumably running under a different "user". So same there.

edited May 31 '18 at 18:28

answered May 31 '18 at 18:16

ispiro

26,556
38
136
291

score 0 · Answer 2 · answered Jun 01 '18 at 07:13

From Using Mapped Drives with IIS

Drive mappings are an extension to the net use command and are created on a per-user basis. That is, the entries for drive mappings exist under the Hkey_Current_User registry key for the user who maps to the network drive. Also, drive mappings are created with the credentials of the user who is currently logged on.

As .NET websites run in an AppPool and this is associated with an account, usually a service account, it will not recognise any drive mappings.

It is recommended in .NET applications to use UNC paths instead of drive mappings.

Could not find part of the path

2 Answers2