logins are disabled, IRIS dont startup

Question

Question

Edrian Golob · Mar 10

Hello guys, Can someone help me?

I have the error below when starting my IRIS instance.

--------------------------------------------

irisstart.exe error: pid = 2936
(112)
The service for the IRIS instance did not start.

Consult the Windows NT Application Event Log for details
using the Event Viewer application accessible from the
Administrative Tools menu.

You may find additional information in IRIS console log
(messages.log) in the manager directory.

Instance name = OTHER-INTEGRATIONS

------------------------

I even tried in emergency mode, and changing SystemStart to false in the .cpf.

When consulting the WIndows Event Log, this is what appears:

(283) Startup incomplete, logins are disabled.

Do you know what it could be? It started to occur after a reboot of the Operating System.

The Computer Name remains the same, as well as IP's and Ports, it was just a reboot on the Server.

Product version: IRIS 2021.2

Discussion (7)3

Log in or sign up to continue

score 0 · Answer 1 · 2024-03-10T19:39:51-04:00

I would check that your iris.key file exists and has not expired.

Not sure where messages.log is on Windows but I would look at that over a Windows log.

score 0 · Answer 2 · 2024-03-10T19:47:33-04:00

Edrian Golob · Mar 10

Yes, the file exists, and it has an expiration date of 04/30/2024

0 0

score 0 · Answer 3 · 2024-03-10T19:55:13-04:00

Robert Cemper · Mar 10

messages.log is in %instslldir%\mgr\ as ususal

0 0

score 0 · Answer 4 · 2024-03-10T19:58:45-04:00

This is what the messages.log shows.

*** Recovery started at Sun Mar 10 19:29:16 2024
Current default directory: e:\intersystems\iris\mgr
Log file directory: .\
WIJ file spec: e:\intersystems\iris\mgr\IRIS.WIJ
Recovering local (e:\intersystems\iris\mgr\IRIS.WIJ) image journal file...
Starting WIJ recovery for 'e:\intersystems\iris\mgr\IRIS.WIJ'.
WIJ file not found.
Exiting with status 3 (Success)
03/10/24-19:29:16:564 (5648) 0 Automatically configuring buffers
03/10/24-19:29:16:579 (5648) 0 Allocated 1224MB shared memory: 1024MB global buffers, 35MB routine buffers
03/10/24-19:29:16:579 (5648) 0 Intel Sandy Bridge AES-NI instructions detected.
03/10/24-19:29:16:657 (5648) 0 Creating a new WIJ file
03/10/24-19:29:16:772 (5648) 0 New WIJ file created
03/10/24-19:29:16:830 (5648) 0
Startup of InterSystems IRIS [IRIS for Windows (x86-64) 2018.1.2 (Build 609U) Thu Aug 23 2018 10:30:25 EDT]
   in e:\intersystems\iris\bin\
   with mgr: e:\intersystems\iris\mgr
   with wij: e:\intersystems\iris\mgr\IRIS.WIJ
   from: e:\intersystems\iris\mgr\
OS=[NT], version=[6.2.9200], 2 processors.
Processor type=[8664], level=[6], revision=[20225], active processor mask=[3].
System Initialized.
03/10/24-19:29:16:908 (6032) 0 Write daemon started.

Any idea?

score 0 · Answer 5 · 2024-03-11T07:58:21-04:00

Strange. Maybe a permissions issue?

What user starts the IRIS service? The default Local system?
You can check that in Windows Services, look for "InterSystems IRIS Controller for IRIS".

If so, does the SYSTEM account have access to e:\intersystems\iris ?

I'm just guessing.

score 0 · Answer 6 · 2024-03-12T10:03:15-04:00

Ludwig Rask · Mar 12

Have you tried running ^STURECOV in %SYS? Might be a problem running the startup routine.

0 0

score 0 · Answer 7 · 2024-03-13T09:38:17-04:00

It's unusual that IRIS created a new WIJ file. I would not expect that if the previous shutdown was clean. You would be well-served to contact the WRC for help with recovery.