G
Guest
I'm attempting to use the FileSystemWatcher class to monitor a folder on a
remote server. My app is running as a Windows service, currently on an XP
machine, but it will be on Server 2003 in production. Everything works fine
when I set the Path to a local drive (i.e. "C:\Test"). However, when I
attempt to set the Path to a UNC path to my remote folder (i.e.
"\\servername\share" with an actual server and share name of course), I
receive an error stating that "The directory name \\servername\share is
invalid."
I have read many posts and articles by others with this same issue. The
common response is that they don't have the proper security settings for the
service. I had checked and triple checked that for my service, however, and
my service is running with a domain account that has Full-Control access to
the directory in question. Does anyone have any other ideas about what might
be causing this problem? Any advice would be appreciated...
Thanks,
Greg
remote server. My app is running as a Windows service, currently on an XP
machine, but it will be on Server 2003 in production. Everything works fine
when I set the Path to a local drive (i.e. "C:\Test"). However, when I
attempt to set the Path to a UNC path to my remote folder (i.e.
"\\servername\share" with an actual server and share name of course), I
receive an error stating that "The directory name \\servername\share is
invalid."
I have read many posts and articles by others with this same issue. The
common response is that they don't have the proper security settings for the
service. I had checked and triple checked that for my service, however, and
my service is running with a domain account that has Full-Control access to
the directory in question. Does anyone have any other ideas about what might
be causing this problem? Any advice would be appreciated...
Thanks,
Greg