I attempted to install the newest version of elog on our site elog server from an old old version.  Around 2008 I believe.  I then received an application failed to initialize properly 0xc0150002 after installing the newest version.  I then tried installing the Feb 2013 version and received the same message.  Panicked, I rolled back our server to its state yesterday.  I would like to update our elog software, anyone know why I am receiving this error??

 Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed:

• Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475).
• Copy your logbook data to a different PC, maybe your office PC.
• Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using)
• If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Good luck!

Andreas Luedeke wrote:

Norm wrote: I attempted to install the newest version of elog on our site elog server from an old old version.  Around 2008 I believe.  I then received an application failed to initialize properly 0xc0150002 after installing the newest version.  I then tried installing the Feb 2013 version and received the same message.  Panicked, I rolled back our server to its state yesterday.  I would like to update our elog software, anyone know why I am receiving this error??  Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed: Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475). Copy your logbook data to a different PC, maybe your office PC. Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using) If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   Good luck!

 Thanks for the reply.  I just got back from a business trip and I will try this ASAP.  Thanks and I will be posting the error message.

Andreas Luedeke wrote:

Norm wrote: I attempted to install the newest version of elog on our site elog server from an old old version.  Around 2008 I believe.  I then received an application failed to initialize properly 0xc0150002 after installing the newest version.  I then tried installing the Feb 2013 version and received the same message.  Panicked, I rolled back our server to its state yesterday.  I would like to update our elog software, anyone know why I am receiving this error??  Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed: Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475). Copy your logbook data to a different PC, maybe your office PC. Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using) If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   Good luck!

 Andreas,

We do not have the current revision at the bottom of any of the pages.  Is there another way I can find out the current revision I'm using?

Thanks!

Norm wrote:

Andreas Luedeke wrote: Norm wrote: I attempted to install the newest version of elog on our site elog server from an old old version.  Around 2008 I believe.  I then received an application failed to initialize properly 0xc0150002 after installing the newest version.  I then tried installing the Feb 2013 version and received the same message.  Panicked, I rolled back our server to its state yesterday.  I would like to update our elog software, anyone know why I am receiving this error??  Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed: Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475). Copy your logbook data to a different PC, maybe your office PC. Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using) If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   Good luck! Andreas, We do not have the current revision at the bottom of any of the pages.  Is there another way I can find out the current revision I'm using? Thanks!

Try:

/usr/local/sbin/elogd -h

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

This is the path for Linux, it is likely different on Windows. But you could just run "elogd -h" in the directory where you compile elogd.

It should print out the version in the first line.

I am on an experiment that used ELOG for all documentation and meeting notes. In our meeting notes we link to elog posts that had been discussed during the meeting. We had done this by hyperlinking the URL to the entry. Recently we had to move our logbook to another machine and so none of our hyperlinks work since the URLs have changed. I noticed that when one creates a new entry in the subject they can reference another post. Is there a way to link another elog in the body of the elog by using its logbook name and id number without having to use a URL?

Thanks in advance

This is one of the rare cases where it helps to read the manual: https://midas.psi.ch/elog/userguide.html#add (You may need to upgrade to elog 2.9)

If you want to replace the old URLs with the new ones, you can edit the logbook files with the entries. The attached script allows you to do so easily. But be careful, try it on a copy of your data first.

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

I'm trying to use the command line to post automatically entries from a web based calendar. I run elogd behind SSL with user/pass configuration. I created an account for the calendar and used the following command line.

[gornea@lheppc63 ~]
$ elog -v -s -a Subject=Test -a Type=Notice -a Category=Planning -h svn.lhep.unibe.ch -p 443 -l "LHEP EXO General" -u calendar ******** "SORRY for SPAMMING! Testing automated posts from command line"

It seems like all parameters are OK but for some reason the connection gets closed. Anybody has an idea why? The SSL certificate is not valid and on the web page users have first to accept it. Can this explain the problem? Is there a flag for elog command line to instruct it to ignore SSL warnings? Thanks a lot!

Command line output:

Successfully connected to host svn.lhep.unibe.ch, port 443
Request sent to host:
POST /LHEP+EXO+General/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------16B1637A4CDBB4E6448003F4
Host: lheppc63.lhep.unibe.ch
User-Agent: ELOG
Content-Length: 1105


Content sent to host:
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="cmd"

Submit
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="unm"

calendar
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="upwd"

Z28yQjUyIQ==
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="exp"

LHEP EXO General
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="encoding"

ELCode
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Subject"

Test
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Type"

Notice
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Category"

Planning
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Text"

SORRY for SPAMMING! Testing automated posts from command line
---------------------------16B1637A4CDBB4E6448003F4

Response received:
HTTP/1.1 302 Found
Server: ELOG HTTP 2.9.2-2455
Location: https://svn.lhep.unibe.ch/LHEP+EXO+General/
Connection: Close

<html>redir</html>

Message successfully transmitted, ID=
[gornea@lheppc63 ~]
$
 

How can I show the Delete option for Admins? 

So I have a logbook with the following config:

[Elog]

Admin User = me, otherguy

Deny Change Config File = otherguy

Restrict edit = 1

Restrict edit time = 4

Menu commands = List, New, Edit, Reply,Last Day, Find, Config, Help

On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080 
But nothing will respond without the logbook name after the port number.  This also seems to be happening to the
"back" submit button.  I can't seem to figure out how to address it.  Suggestions?

> On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
> link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080 
> But nothing will respond without the logbook name after the port number.  This also seems to be happening to the
> "back" submit button.  I can't seem to figure out how to address it.  Suggestions?

Can you show us your config? I had this issue when i was initially trying to integrate elog with apache.

Here's the global section and the logbook section for one of the logbooks affected.  Of note, the 'demo' logbook works
fine and does not have this issue.

[global]
port = 8080
SMTP host = localhost
Welcome title = Welcome
Top group 2012 =  2011, 2010, 2009, 2008, 2007, WINTER

[WINTER]

;*****Look and Feel*****
Page title = Winter Weather
List page title =  Winter Weather
Edit page title = Winter Weather
Theme = default
CSS = default.css
Comment = Winter Weather
Title image =

;*****Email*****
Use Email From = me@me.com
Suppress Email to users = 1
Display Email recipients = 0
Email Encoding = 4
Suppress Email on edit = 1

;*****Settings*****
Entries per page = 30
;Reverse sort = 1
Expand default = 2
Display mode = SUMMARY
Mode command = 0
Time format = %d%B%Y-%H:%M
Summary lines = 15
Show top groups = 0
Message height = 8
Message width = 38
Default encoding = 1
Mode commands = 0
Suppress default = 2
Resubmit default = 2
Back to main = 1
RSS Title = $entry time - $Event

;*****MENU*****
List Menu commands = New, Find
Menu commands = List, New, Edit, Find, Reply, Delete

> Top group 2012 =  2011, 2010, 2009, 2008, 2007, WINTER

Your usage of "Top group" is strange. Top groups should only be used for independent groups of logbooks, more like you were running one dedicated sever fore 
a group of logbooks. Further, you defined logbooks (2008, 2009, ...) which do not exist in your config. Why don't you just remove the "Top group" line from your 
config? If you want to group different logbooks, just use the "group" command as written in the docs.

/Stefan

 Does anyone have a success story with kerberos on windows?

 Anyone?  Bueller?

Can ELog support different languages based on the logged on user?