Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- From: "Bob Milton" <DocBob1945@xxxxxxxxxxxxxxxx>
- Date: Tue, 14 Mar 2006 14:10:29 -0800
A windows service starts before anyone logs on. At that time, there are
no mapped drives. When you log on, you can see w:, but your service has
failed by then.
Services are designed that way on purpose - all the computer has to do
is start up. SQL Server is a great example - you can set it up, put the
computer in a closet, and leave it alone and still use SQL from a client
machine.
Bob
"mhetherington" <mhetherington@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DF1EC0CE-7FCC-49FC-8920-E6FF9A1C9C55@xxxxxxxxxxxxxxxx
Thanks for the reply Bob. However, I have two comments/questions...
1) While running as a Windows Service, I can map a drive and access it
like
a local drive - it's just ProcessStartInfo.WorkingDirectory fails when I
set
it to a mapped drive. So, when you say "there are NO mapped drives" I
would
argue that there are...once you map them. Did I misunderstand your
statement?
2) In my code, ProcessStartInfo.WorkingDirectory doesn't like UNC paths
either. Have you experienced something different?
"Bob Milton" wrote:
When a windows service starts, no one is logged into the computer.
Until
someone logs in, there are NO mapped drives! So, you will have to use UNC
paths (//server/share1/dir1).
Bob
"mhetherington" <mhetherington@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:D1961D07-866B-4753-99E0-01EC564E2D78@xxxxxxxxxxxxxxxx
Just discovered a critical piece of the puzzle...
The Start() method fails, as described below, only when running as a
Windows
Service. When I try the same thing from s straight Console App while
logged
in as the service account user, Start() succeed. However, when running
as
a
Windows Service it doesn't seem I can set WorkingDirectory to any
mapped
drives...even though I have confirmed that the mapped drive does exist
and
is
accessible to the service account.
So, a refinement of my question should read "Has anyone successfully
set
ProcessStartInfo.WorkingDirectory to a mapped network drive while
running
as
a Windows Service?"
"mhetherington" wrote:
Has anyone successfully called the Start() method on a
System.Diagnostics.Process object with the object's
ProcessStartInfo.WorkingDirectory set to a path on a mapped network
drive?
For example, if I have "w:" mapped to "\\serverA\share1" and set
ProcessStartInfo.WorkingDirectory = "w:\dir1", my calls to
Process.Start()
always fail with the error "The directory name is invalid".
Whereas, if I do the same thing with WorkingDirectory = "c:\dir1",
calls
to
Process.Start() always succeed.
Before anyone asks, yes the directory "dir1" does exist on w: and is
readable under the user context calling the Process.Start() method.
If no one has successfully executed Process.Start() with
WorkingDirectory
pointing to a mapped network drive, does anyone have any (MS)
reference
article confirming that this is not possible and perhaps explaining
why?
Thanks in advance.
.
- Follow-Ups:
- Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- From: mhetherington
- Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- References:
- Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- From: Bob Milton
- Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- From: mhetherington
- Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- Prev by Date: Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- Next by Date: Advice on Handling Large File Download via HTTP
- Previous by thread: Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- Next by thread: Re: ProcessStartInfo.WorkingDirectory and Mapped Network Drives
- Index(es):
Relevant Pages
|