Issue in FileWatcher via UNC

Question

0.00/5 (No votes)

See more:

Am trying to watch a UNC Path file via FileWatcher in Windows service .Service works for local path not for UNC path. I get the below mentioned exception

Service cannot be started. System.ArgumentException: The directory name \\ServerName\Folder1\Target Folder is invalid.

This was the information i got in event viewer i have hosted the service as Network service . I can able to read the above mentioned path in FileWatcher via Console Application not via Windows Service.

Posted 19-Nov-15 21:41pm

Member 11773469

Updated 19-Nov-15 23:47pm

Tomas Takac

v2

Add a Solution

Comments

Tomas Takac 20-Nov-15 5:51am

Are you running it under the same user account?

Dave Kreskowiak 20-Nov-15 12:47pm

What account is your service running under? By default, it's LocalSystem which doesn't have any permissions to any network resources at all.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

ZurdoDev · Answer 1 · 2015-11-20T05:07:00

Solution 1

It is likely a permission issue. Make sure the identity that is running the service has the proper permissions.

Posted 20-Nov-15 5:07am

ZurdoDev