I am dealing with this issue for the past 4 years and it bugs me very much.

1. My company generates msi installers with wix toolset, and they create multiple Windows services. Those services run with an AD service user + password. The services are created with the user and a "password" I enter in the installer UI, but always fail to start. The first service to start is stuck in "starting" status.

Eventually it will lock the service user down, just as if the password was incorrect. I guarantee the password I type in the msi UI is correct.

So, during installation while the first service is starting, I simply open that service and update the password under Log On tab and save, and magically, it starts and all the other services start too. WHY? Why do I have to change the password one one service only to get the others working?

2. The problem is the same if I let the installer create services with LocalSystem, they will start just fine. Then I would update them with the service user and password with sc config, as we all do. They will fail to start, in the same way, all of them. Until I update the password of ONE of them, then they will all start.

What am I doing wrong? What can explain this behavior?

EDIT: the AD service user indeed has login-as-service permissions or the service would never start

I am dealing with this issue for the past 4 years and it bugs me very much.

1. My company generates msi installers with wix toolset, and they create multiple Windows services. Those services run with an AD service user + password. The services are created with the user and a "password" I enter in the installer UI, but always fail to start. The first service to start is stuck in "starting" status.

Eventually it will lock the service user down, just as if the password was incorrect. I guarantee the password I type in the msi UI is correct.

So, during installation while the first service is starting, I simply open that service and update the password under Log On tab and save, and magically, it starts and all the other services start too. WHY? Why do I have to change the password one one service only to get the others working?

2. The problem is the same if I let the installer create services with LocalSystem, they will start just fine. Then I would update them with the service user and password with sc config, as we all do. They will fail to start, in the same way, all of them. Until I update the password of ONE of them, then they will all start.

What am I doing wrong? What can explain this behavior?

EDIT: the AD service user indeed has login-as-service permissions or the service would never start EDIT: The first time it fails to start, event log shows: "The xyz Service service was unable to log on as DOMAIN\username with the currently configured password due to the following error: Logon failure: the user has not been granted the requested logon type at this computer."

subsequent errors are all the same: "The xyz Service service failed to start due to the following error: The service did not start due to a logon failure."

I am dealing with this issue for the past 4 years and it bugs me very much. My company generates msi installers with wix toolset, and they create multiple Windows services. Those services run with an AD service user + password. The services are created with the user and a "password" I enter in the installer UI, but always fail to start. The first service to start is stuck in "starting" status.

Eventually it will lock the service user down, just as if the password was incorrect. I guarantee the password I type in the msi UI is correct.

So, during installation while the first service is starting, I simply open that service and update the password under Log On tab and save, and magically, it starts and all the other services start too. WHY? Why do I have to change the password one one service only to get the others working?

The problem is the same if I let the installer create services with LocalSystem, they will start just fine. Then I would update them with the service user and password with sc config, as we all do. They will fail to start, in the same way, all of them. Until I update the password of ONE of them, then they will all start.

What am I doing wrong? What can explain this behavior?

I am dealing with this issue for the past 4 years and it bugs me very much.

1. My company generates msi installers with wix toolset, and they create multiple Windows services. Those services run with an AD service user + password. The services are created with the user and a "password" I enter in the installer UI, but always fail to start. The first service to start is stuck in "starting" status.

Eventually it will lock the service user down, just as if the password was incorrect. I guarantee the password I type in the msi UI is correct.

So, during installation while the first service is starting, I simply open that service and update the password under Log On tab and save, and magically, it starts and all the other services start too. WHY? Why do I have to change the password one one service only to get the others working?

2. The problem is the same if I let the installer create services with LocalSystem, they will start just fine. Then I would update them with the service user and password with sc config, as we all do. They will fail to start, in the same way, all of them. Until I update the password of ONE of them, then they will all start.

What am I doing wrong? What can explain this behavior?

EDIT: the AD service user indeed has login-as-service permissions or the service would never start