On 12/05/2020 15:15, Adam Retter wrote: > Thanks for your response Mark, further comments inline below - > >> It shouldn't. >> >> Maybe a permissions problem? Although running as LocalService is should >> be fine. > > So I am using the `--ServiceUser=LocalSystem` flag - to run under the > LocalSystem account. (i.e. NOT `NT Authority\Local Service`).
Sorry. I knew that and still typed it wrong. LocalSystem is a member of the local administrators group so it should be able to read the file. Maybe try running the service as the same user as the one you use when running from the command line. That should help narrow down what is going on. >> I guess check the obvious. Does the dll exist where the app is looking? > > It does exist yes. I have a working theory in fact that it loads the > DLL, but it is the dependencies of that DLL (which will be various > Windows system DLL's) that it can't load. Is there a tool (ProcessMonitor?) that you can use to monitor attempts to load DLLs? >> Can LocalSystem read that file etc. > > Do you know - Is there someway that I can directly execute code under > "LocalSystem" to see if I can reproduce the problem outside of > Procrun? I'd go the other way and run procrun under the user you know works on the command line. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
