QIE service not starting "Couldn't get lock for C:\ProgramData\QIE\logs\qieLauncher.log"

Question

In the C:\ProgramData\QIE\logs\stderr.log I see this error and cannot get the QIE service to start.

 

2015-01-28 15:45:12 Commons Daemon procrun stderr initialized

Jan 28, 2015 3:45:12 PM com.qvera.launcher.utils.QieLauncher main

SEVERE: Will shut down with failed status due to unexpected exception: java.io.IOException: Couldn't get lock for C:\ProgramData\QIE\logs\qieLauncher.log

java.io.IOException: Couldn't get lock for C:\ProgramData\QIE\logs\qieLauncher.log

at java.util.logging.FileHandler.openFiles(Unknown Source)

at java.util.logging.FileHandler.<init>(Unknown Source)

at com.qvera.launcher.utils.QieLauncher.main(QieLauncher.java:76)

 

Jan 28, 2015 3:45:12 PM com.qvera.launcher.utils.QieLauncher main

INFO: End of the 'main' line.

Jan 28, 2015 3:45:12 PM com.qvera.launcher.utils.QieLauncher main

INFO: Calling exit(99) so the service enters a failed state.

I tried running the service as Local System and as their domain administrator account (I changed this in the windows services mmc)

In the windows event logs I see "The QIEService64 service terminated unexpectedly.  It has done this 6 time(s)."

-Xmx1024m is in the startup tab

Since the C:\ProgramData\QIE\logs\qieLauncher.log file didn't exist I did try creating it manually with no change.

Answer 1

It seems like there are missing permissions in that qieHome folder. You could try to reinstall 'As Admin', or make sure that the network user has access to the qieHome directory.  But it seems like you have checked those same areas.  We can setup a webex to look at it with you.

Answer 2

That error is when there are too many qieLauncher.*.lck files in the qie logs directory.  This can occur if the OS shuts down without allowing QIE to cleanly exit.  If you remove all of the files in the qie/logs directory, you should be able to start up again.

If your OS shuts down on a scheduled basis, I suggest creating another task to shutdown QIE before the OS.

Comments

In one case the network admin had a script that remotely shutdown the server QIE was installed on.  This caused QIE to be terminated abruptly which left the .lck files in place.  The fix is to call a script to stop the QIE service first, giving it time to finish processing the messages it is working on.  Then shutdown the OS after QIE has terminated cleanly.  See this question to script the start and stop of QIE: https://www.qvera.com/kb/index.php/692/how-to-start-and-stop-qie-from-a-script-or-command-prompt?show=693#a693