FileSystemWatcher invalid directory name

[=?Utf-8?B?c3RhaGxlcnc=?=]

I have written a windows service to watch a folder for newly created
documents. Works fine when watching directories on my local machine, but
always get a "directory invalid" error when I either try to watch a UNC path
or mapped drive.

Any ideas?

Thanks!
Wes

[Samuel R. Neff]

That's funny, I have the opposite problem where I get no error if the
unc path doesn't exist. :-)

Are you sure the user that the windows service is running as has
access to the unc path?

Sam

------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
On Thu, 14 Jun 2007 14:01:01 -0700, stahlerw
<st******@discussions.microsoft.comwrote:

>I have written a windows service to watch a folder for newly created
documents. Works fine when watching directories on my local machine, but
always get a "directory invalid" error when I either try to watch a UNC path
or mapped drive.

Any ideas?

Thanks!
Wes

[=?Utf-8?B?c3RhaGxlcnc=?=]

I am running it on my machine under a domain account that has access.
I have also noticed that I get the error the first time I create a new
document in the directory, subsequent attempts don't trigger or raise an
error.

So just to verify, you have seen it work with UNC path?
"Samuel R. Neff" wrote:

>
That's funny, I have the opposite problem where I get no error if the
unc path doesn't exist. :-)

Are you sure the user that the windows service is running as has
access to the unc path?

Sam

------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
On Thu, 14 Jun 2007 14:01:01 -0700, stahlerw
<st******@discussions.microsoft.comwrote:

I have written a windows service to watch a folder for newly created
documents. Works fine when watching directories on my local machine, but
always get a "directory invalid" error when I either try to watch a UNC path
or mapped drive.

Any ideas?

Thanks!
Wes

[Samuel R. Neff]

Yes, we use FileSystemWatcher in an asp.net app using impersonation.
We impersonate the authorized user when setting up the watcher and
then again when the event is raised ('cause event is raised on a
different thread).

It works fine when the unc is correct and setup. When we install our
app in an environment where the unc share is not setup properly, we
get no error, just no events.

Sam

------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.

On Thu, 14 Jun 2007 19:11:01 -0700, stahlerw
<st******@discussions.microsoft.comwrote:

>I am running it on my machine under a domain account that has access.
I have also noticed that I get the error the first time I create a new
document in the directory, subsequent attempts don't trigger or raise an
error.

So just to verify, you have seen it work with UNC path?

[=?Utf-8?B?c3RhaGxlcnc=?=]

Thanks Sam.
I will investigate the impersonation route.

"Samuel R. Neff" wrote:

>
Yes, we use FileSystemWatcher in an asp.net app using impersonation.
We impersonate the authorized user when setting up the watcher and
then again when the event is raised ('cause event is raised on a
different thread).

It works fine when the unc is correct and setup. When we install our
app in an environment where the unc share is not setup properly, we
get no error, just no events.

Sam

------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.

On Thu, 14 Jun 2007 19:11:01 -0700, stahlerw
<st******@discussions.microsoft.comwrote:

I am running it on my machine under a domain account that has access.
I have also noticed that I get the error the first time I create a new
document in the directory, subsequent attempts don't trigger or raise an
error.

So just to verify, you have seen it work with UNC path?

[Samuel R. Neff]

Worth looking into, but it shouldn't be necessary in your case.

I need it 'cause I'm running in an asp.net app which by default does
not have access to the unc. In your case, the windows service is
already running under an account that has access, so impersonation
shouldn't be necessary.

Sorry I can't help more...

Sam

------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
On Thu, 14 Jun 2007 19:37:00 -0700, stahlerw
<st******@discussions.microsoft.comwrote:

>Thanks Sam.
I will investigate the impersonation route.

"Samuel R. Neff" wrote:

>>
Yes, we use FileSystemWatcher in an asp.net app using impersonation.
We impersonate the authorized user when setting up the watcher and
then again when the event is raised ('cause event is raised on a
different thread).

It works fine when the unc is correct and setup. When we install our
app in an environment where the unc share is not setup properly, we
get no error, just no events.

Sam