-
Notifications
You must be signed in to change notification settings - Fork 949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1068: Dependency service or group failed to start. #1368
Comments
I've done some tests, and when I install (my own) service via PInvoke it is installed correctly and starts and runs without any problem. I'm also setting the permissions, so the service will work as Network Service. The main difference between my code and the runner code is that I'm installing the service as local account and setting the permissions separately. Here the service is installed using one call:
in my installer I'm doing this as two steps:
Can someone explain to me what is the difference? Why the service can't start when it is set to |
Describe the bug
I've downloaded the latest version of the agent and I wanted to install it as a windows service.
I am able to run the agent as a standalone app without any problems, but It can't start the windows service.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Windows service should start without any problems
Runner Version and Platform
Version of your runner? v2.283.1
OS of the machine running the runner? Windows 10 Pro 21H1 19043.1237 Polish language
What's not working?
Job Log Output
If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.
Runner and Worker's Diagnostic Logs
The service is installed with the default settings.
The logon account is set to:
When I search this account on my PC I have this available:
there is
USŁUGA SIECIOWA
but without theZARZĄDZANIE NT
prefix.The text was updated successfully, but these errors were encountered: