Issue with Domain Services Not Starting After DC2 Delayed Startup, Despite DC1 Being Available

Researcher 6

We have two Domain Controllers (DC1 and DC2). One day, DC2 started 20 minutes late. On that day when client PC's ran services we encountered the following error message:

"The xyz service failed to start due to the following error: The account name is invalid or does not exist, or the password is invalid for the account name specified."

It's important to note that we use Domain Account credentials to run these services on the client PCs. Interestingly, other functions, such as the Task Scheduler, worked perfectly fine, despite using the same account as the xyz service.

We want to know that, when DC1 was avialable why we got error message like domain controller not avialable and also why we could not start any services.

Yanhong Liu 12,505 Reputation points Microsoft Vendor

2024-10-17T05:55:36.2266667+00:00

Hello

If error happen when here only have one DC online, it means that PC can't reach this DC.

you can try to open command as administrator and run below command to check which DC our PC connect with.

nltest /dsgetdc: domainname

If connect with DC2, try to change it to DC1 to see if error will happen again.

nltest /Server:ClientComputerName /SC_reset:Domainname\DomainControllerName

if it has error, then we can find out reason through error massage.
Researcher 6 Reputation points

2024-10-30T12:54:22.5966667+00:00

Hi @Yanhong Liu , Thanks for your response! Just to clarify, we have autologon enabled, which logs in a domain account when the PC starts. The scheduled tasks executed successfully with the same domain account, so it’s puzzling why the services did not run as expected.

Share via

Issue with Domain Services Not Starting After DC2 Delayed Startup, Despite DC1 Being Available

Your answer