But in my case, it fixed the issue so if you are running out of options, maybe you can just give it a try ).
I am not saying that this workaround will fix each and every issues linked to an error code 1067… Sometimes, this error will be linked to the fact that the service cannot find the executable for example.
Log out all sessions: stop all services running with this account, all processes (from the task manager, there should be nothing on the “users” tab), aso… Alternatively, you can also disable the services (or manual mode) and then reboot the Windows Server.I am not saying that this workaround will fix each and every issues linked to an error code 1067.
Open a cmd prompt > The current folder should be C:UsersLogin to the Windows Server with another administrator account Start the target Service > It should now be working.Since this is an AD account (that I will call below), it is possible to remove the local profile, it will just be recreated automatically when needed, you just need to remove it properly and for that, there are particular steps: The workaround is simply to delete the local profile… So with all these information, it appeared that the issue was linked to this particular technical user but only locally to this Windows Server… When working with AD accounts, it is always possible to face some issues with local profile VS domain profile (thanks Stéphane Haby for pointing that out to me, I’m not a Windows expert )) so I tried to work on that and after some time, I found a workaround to this issue. It means that the issue is not linked to the technical user globally.Using the technical user to start a service on another Windows Server.The technical user is listed and allowed to start the service so there is no issue there.Checking the ‘Log On As a service’ Local Policies.It means that the issue is somehow linked to this particular technical user.Changing the Log On As user to something else.I performed a lot of tests on this environment to try to narrow down the issue and the following tests in particular were quite relevant: This was the first time I saw this error, ever, so I wanted to know more about it. The error code 1067 means ‘ERROR_PROCESS_ABORTED’. We were using a dedicated technical account (AD account) to do the installation and to run this service. Unfortunately this didn’t go well and the start command wasn’t working at all. Some time ago, we were installing a Migration Center (from fmeAG) on a Windows Server and at the end of the installation, the service named Migration Center Job Server is configured and finally started.