Startup error message after normal shutdown

[Paul Rubin]

Hi Quang, if you log off of Windows or reboot, upon logging back in to Windows, when you launch DocFetcher, it complains that DocFetcher is already running, even though it is not. I believe the problem is that when Windows shuts down, it exits DocFetcher, but DocFetcher does not recognise this as a 'normal' exit. Can this be fixed?

[Nam-Quang Tran]

I think this normally happens when you hide DocFetcher in the System Tray and then shut down Windows without exiting DocFetcher. Technically, this means you didn't close DocFetcher cleanly, so the next time you start the program, it thinks the previous instance either crashed or is still running.

Can this be fixed?

In principle, yes, but it requires more work than I can afford at the moment.

[Lidit]

I also get the same issue when I automatically close docfetcher using a cmd scrpit that close it (and countless other apps) to free the CPU during the night:

taskkill /f /im DocFetcher.exe
taskkill /f /im docfetcher-daemon-windows.exe
taskkill /f /im javaw.exe

When I reopen it (it start by default after rebooting), I get this error:

It seems an instance of DocFetcher was not terminated cleanly or is still running. Do you want to launch another instance?

[Nam-Quang Tran]

@ Lidit

Well, "It seems an instance of DocFetcher was not terminated cleanly" is what happens if you kill DocFetcher via taskkill. Not really that surprising... DocFetcher currently does not support script-based shutdown.

[Paul]

Please somebody create script shutdown? Is it hard to do, I have no idea about this ?

Every day our file server reboots, but when it tries to start DocFetcher the next day as a start up program (upon auto log on), it hangs on the message window, never to restart again day after day :( : (

At the moment I schedule a DocFetcher.bat --update-indexes every two hours, which takes some CPU/SSD resources.

Otherwise it would have been a perfect real-time indexer using the tiny resource daemon.

[Nam-Quang Tran]

@ Paul:

here's a modified version of portable DocFetcher that might do the trick:

http://docfetcher.sourceforge.net/docfetcher-1.1.22-portable.zip

It has an option "CheckSingleInstance" in the advanced settings file. If you set the option to false, DocFetcher will no longer warn if it was killed the last time it was run.

The new option will be included in the next official release if there are no problems with it.

[Paul]

Hi Nam-Quang,

It seems to be working ok.

The DocFetcher GUI appears as normal the next morning after an auto user log in and after a windows shutdown the night before. No more error message.

Thanks !

[Lidit]

Thanks for your work Nam-Quang!

Solved : I installed the 1.1.22 portable version you are talking about, and set "CheckSingleInstance" to false and it works

(It's not a problem, but it migh help some user that it did not work on the non-portable DocFetcher 1.1.22. It's confusing, especially because it's not mentioned that it's not portable)
In this version there is no "CheckSingleInstance" but "AllowOnlyOneInstance".
● When "AllowOnlyOneInstance = false" I get the anoying ok-cancel popup at startup.
● When it's set to true, it doesn't launch (I see in task manager it launch the docfetcher process, then javaw as a child, but then javaw is killed and this also kill docfetcher).

[Nam-Quang Tran]

@ Lidit: The AllowOnlyOneInstance setting is in the settings-conf.txt file, which is DocFetcher's "internal" settings file that you normally shouldn't be touching.

The above download link is indeed the portable version. There's no non-portable version with the new CheckSingleInstance setting yet.