I've considered rewriting in Python but i'm not sure that will be the fix. The dll referenced in the error does exist, and does not throw an error when run from command prompt. Only in a batch situation does this error occur. What would make the batch Python any different?
Running a program in the context of a service is not, in general, the same as running it from the command line.
One key difference is that services are often run using the System account. That account is special in that it is very powerful on the local machine but it has no network rights, e.g. you cannot access a UNC share.
We are having the same problem, but with a windows-service. It runs fine from command-prompt with an exe. But as soon as we put it back in the service we get THE EXACT same message as you.
Did you solve it? (Pleeease say you did...) 🙂
Yes I did, after determining the problem was permissions on the service account (as related in the other post). But another issue I ran into was our security team - service accounts aren't allowed the necessary privileges here, and I am required to use a security account for scheduled jobs. So I re-wrote my app to use locator and map services instead of accessing the database directly. It might be a smidge slower but speed really isn't an issue in our use.
Glad you got it fixed,