Asked by:
windows service startup fails when domain controller is not reachable

General discussion
-
I have a windows service which runs under a domain user account (service account) on a windows 10 20H2 (Build 19042.1165) machine.
This account is added to the group policy "Logon as a service".
If the domain controller is reachable (network cable plugged in) and I start the windows service it successfully starts up and is running.
If the network cable is unplugged (domain controller not reachable) and I start the windows service then it fails with the error message:
The service"xxxx"on"LocalComputer"could not be started.
Error1057:The account name is not allowed or does not exist, or the password is invalid for the specified account name.
How I can achieve that the service starts up successfully?
All replies
-
I would like to provide you the best article from Microsoft support. Check out this article I hope this may resolve your Windows service startup fails error.
https://docs.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/service-startup-permissions
-
-
-
My tip:
You can run the service using a built-in account, like NT AUTHORITY\NETWORK SERVICE ou NT AUTHORITY\NT SERVICE. They are local accounts. Network Service has network access (his permissions are that given to computer object in Active Directory), while NT SERVICE don't.
You can also use LOCAL SYSTEM (or SYSTEM), however, this account has full computer access - please review security implications.
How to change: Go to Service, open the Service properties, and on "Log On" tab, select "This Account". Then write or browse for account name.
Hope this help. Let us know if it works.
Good luck!
Marcelo
Marcelo Lucas Guimarães
MCP, MCTS, MCDBA, MCITP
Twitter: @mlucasg7
Blog: http://mlucasg.wordpress.com- Edited by MarceloLGuimaraes Wednesday, November 10, 2021 11:05 AM Extend explanation
-
My tip:
You can run the service using a built-in account, like NT AUTHORITY\NETWORK SERVICE ou NT AUTHORITY\NT SERVICE. They are local accounts. Network Service has network access (his permissions are that given to computer object in Active Directory), while NT SERVICE don't.
You can also use LOCAL SYSTEM (or SYSTEM), however, this account has full computer access - please review security implications.
How to change: Go to Service, open the Service properties, and on "Log On" tab, select "This Account". Then write or browse for account name.
Hope this help. Let us know if it works.
Good luck!
Marcelo
Marcelo Lucas Guimarães
MCP, MCTS, MCDBA, MCITP
Lucky to read this article, this is amazing, thanks for sharing! you try!
https://coloring-pages.io/
- Edited by colorman4 Tuesday, November 16, 2021 9:05 AM
-
Yes, you are right but but this is very difficult and as a developer I can not do this work. I was view website about writing service and the developer did this work on that site very nicely. You can also visit this site and take help to complete your translation work.
-
Yes, you are right but but this is very difficult and as a developer I can not do this work. I was view website about writing service and the developer did this work on that site very nicely. You can also visit this site and take help to complete your translation work.
-
-
I suggest you the best article from Microsoft Community support. Check out this article This may surely resolve your Windows service startup fails error.
https://docs.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/service-startup-permissions
-
-
-
-
Remember that when you change permissions at service level your are changing the security and IAM access to these services. It has some implications in your environment. So, if the service has dependencies from AD and you change the permissions locally... You are making changes in the security of the resources that are running under that service. It could be a risk.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-