Written by

Internal Applications Developer at InterSystems
Question Hannah Sullivan · Sep 14, 2023

Fixing IRIS "service did not start due to a logon failure" Error

When I attempt to start my local IRIS instance (named LATEST) I am getting the below error

"(111) Error starting service: LATEST
Reason: (1069) The service did not start due to a logon failure."

Does anyone have experience with this or know how to resolve the logon credentials associated  with this start? 

Product version: IRIS 2021.1
$ZV: IRIS for Windows (x86-64) 2022.1.2 (Build 574U)

Comments

Evan Gabhart · Sep 14, 2023

If this was tied to your Windows password and you recently changed it then you may need to change the credentials for the service.
Try searching for "Services" in the windows search box and open the app. Then find the service associated with this instance (I think it would be InterSystems IRIS Controller for LATEST) and open properties and go to log on tab. Change the credentials here to match your OS credentials and then try starting your instance. Hope that helps!

0
Hannah Sullivan  Sep 14, 2023 to Evan Gabhart

Thank you for the assistance Evan - this solved my problem. 

0
Mark Boulton  Sep 15, 2023 to Evan Gabhart

I had the same problem and this solved it as well. Thank you.

0
Evgeny Shvarov · Sep 15, 2023

And if you use Docker for your dev environment you will never face such a problem.

0
Ben Spead  Sep 15, 2023 to Evgeny Shvarov

I thought that Windows containers still have issues?  Or is Windows on Docker at full parity now with Linux on Docker?

0
Evgeny Shvarov  Sep 17, 2023 to Ben Spead

I'm not the one who can answer as I'm on Mac, but I hope there are developers on Windows who are happy with Docker and can share their experience

0