Windows 10 Pro
Version 1709 OS
Build 16299.666
I have a service which would like to access network drive U:/public/blah.txt
. Running it as a normal user with the command prompt works, running it as a service does not.
If go to services.msc -> servicename -> properties -> Log On -> This account
and use MYDOMAIN/MYUSER
and the correct password and restart, it still does not work, and produces the same error message. This is the account which can successfully run the program from the command prompt.
It's a golang executable running inside a nssm service and the actual error message is Error opening file U:\public\blah.txt: The system cannot find the path specified
.
This program used to work as a service on a different computer, it's even accessing the same drive. the only difference I can see is that the account I'm using now is a domain account, whereas before it was a local user.
Why isn't my service seeing the drive mappings, if it is successfully logged in as the user who has them?