0
You can fix this with one of several solutions
Have your Sys Admin set up a service user and have them ONLY grant access to the two paths so domain\ServiceUser has access to \\Server1\share and \\Server2\share then run the service as that user
Second you can run the service as Local System Account and grant the machine access to both paths
Third Have the Service run on Server1 and use a filesystemwatcher to activate the service and then you ONLY have to grant access to server 2
FileSystemWatcher MUST run on the server it is monitoring to run successfully and reliabley
These are just a couple of the ways to Fix this
0
It might not be the party-line way to go but I found the easiest way to handle this particular issue is to set up a virtual directory pointing to the location you want the service to access, and then setting up the permissions to give the windows service account credentials read and/or write access to that virtual directory.