Hi Finn,

I've just tested the same archive on new laptop with Windows 11. 
I unzip it and double-click elogd.exe file, bypass defender warning and the server is running.
To test, i open localhost:8080 on web client and it displays the demo logbook.

Btw i didn't test it as a service. What are the 2 libs you said it misses ?

.
Laurent

> 
> Hi Laurent
> 
> I've found the attached zip files in post 69491. The one containing the ELOG probgram libary won't run on my test laptop - the service wont start
> There is in the same thread a post from Just Keijser containing only the executables, and it won't start either. Starting the elog.exe though gives me that the exe is missing 2 dll files which can be downloaded seperately.
> It is not easy cause there are several versions of the 2 dll files and only one working, but now my elog reports version ELOG V3.1.4-1ebfd06c
> 
> But this cant be the solution - if so the windows version is put to the grave
> 
> Kind Regards Finn

> Hi Finn,
> 
> I've just tested the same archive on new laptop with Windows 11. 
> I unzip it and double-click elogd.exe file, bypass defender warning and the server is running.
> To test, i open localhost:8080 on web client and it displays the demo logbook.
> 
> Btw i didn't test it as a service. What are the 2 libs you said it misses ?
> 
> .
> Laurent
> 
> > 
> > Hi Laurent
> > 
> > I've found the attached zip files in post 69491. The one containing the ELOG probgram libary won't run on my test laptop - the service wont start
> > There is in the same thread a post from Just Keijser containing only the executables, and it won't start either. Starting the elog.exe though gives me that the exe is missing 2 dll files which can be downloaded seperately.
> > It is not easy cause there are several versions of the 2 dll files and only one working, but now my elog reports version ELOG V3.1.4-1ebfd06c
> > 
> > But this cant be the solution - if so the windows version is put to the grave
> > 
> > Kind Regards Finn

Hi Laurent

OK, i can recreate the unzip to folder and run elogd.exe and it works :-). If i unzip to the folder of the version installed (with the windows installer) where it runs elogd.exe as a service, the service won't start.

The problem with the dll files only applies to the post from Just Keijser containing only the executables (3 files) and these executables repport missing: libcrypto-1_1-x64.dll and libssl-1_1-x64.dll

These versions are a black box for me, are the important?

The unzip version (your version) reports: ELOG V3.1.4-395e101 (I think this is the same number as for the 2018 installed version)
The version with the 3 exe files (my version) from Just Keijser reports: ELOG V3.1.4-1ebfd06c
This site reports: ELOG V3.1.4-bcd7b50

Kind Regards Finn

I too have this as an occasional issue, although in my case due to a dodgy pointer.  I too manually delete the entries.

Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.

I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...". So double submits should not be possible any more.

I'm also happy to see this change implemented as we've had to deal with the same issue at times as well. Will this change be incorporated into the latest version (314-2, aka elog-latest.exe), or will there be a new version release (that is not in Changelog yet)? If so, can you give any ETA on this new code availability?

Also I noticed that the Elog Home page still says "Current version is: 3.1.2". I assume that only means it hasn't been updated, not that it means it's the current STABLE version and subsequent releases are beta -- please correct me if I'm wrong. I just want to make sure I understand how the versions and releases work.

Endless thanks for this product and all your work Stefan.

"I committed" means that the change is sent to the GIT repository. People who compile from the source code can pull and compile immediately. Windows users have to wait until I do the next release. I'm developing on a Mac and have to boot a special (old) Windows machine to compile the .exe which each time takes me about one hour including documenation updates, changelog updates, upload of zip files etc. Since my main job is heading a research group, I only can devote this hour once in a while, depending on my work load. Sometime even the weekends are too short.

Thank your very much for your work on this - as i mentioned this is a minor issue.

Kind Regards Finn

 I have a possible explanation for this problem, but it is just guess work. If I'm right, then just download the latest ELOG version and it will work properly again.

• You've downloaded an elog version from git, which still contained the line 12 in elogd.c: char svn_revision[] = "$Id$";
• Since you did checkout from git, the $Id$ was not substituted.  
• ELOG trys to extract the version by this:      rsprintf
            ("<center><a class=\"bottomlink\" title=\"%s\" href=\"https://midas.psi.ch/elog/\">ELOG V%s-%d</a></center>",
             loc("Goto ELOG home page"), VERSION, atoi(svn_revision + 13));
• svn_revision + 13 is pointing into the void. Still I would have expected that you get a number as a result.

My advice: download again and retry.