| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67665
|
Thu Feb 20 17:37:06 2014 |
 | Markus Grosse-Kock | M.Grosse-Kock@reken.de | Question | Windows | 2.9.2-2475 | Re: Adaptation of the language |
| Stefan Ritt wrote: |
|
| Markus Grosse-Kock wrote: |
|
Hello,
I want to change the language to German. But it does not work.
Here my config:
Theme = default
Resource dir = D:\Elog
Language = german
Where is the problem? Or is it not possible to change the language in Windows?
Best regards,
Markus
|
You put the "Language = german" statement into the logbook section, but it has to be placed in the [global] section as written in the documentation. Unfortunately this section of the configuration file cannot be accessed through the web interface, so you have to edit the elogd.cfg file manually, which might require admin rights.
Viele Grüsse nach Reken,
Stefan
|
Danke, hat funktioniert.
Gruß Markus |
|
67669
|
Thu Feb 27 15:15:55 2014 |
 | Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | XML import Error | Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type |
| Attachment 1: new__2.xml
|
<?xml version="1.0" encoding="UTF-8"?>
<ELOG_LIST>
<ENTRY>
<MID>
2
</MID>
<DATE>
2014-02-24 22:28
</DATE>
<OBJECT>
Archived Client:
</OBJECT>
<ACTION>
Archived Client:
Archived Client to Manual_Archive and took a full backup of it
</ACTION>
<TEXT>
ticket: 123456
Decommission of client.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
<ENTRY>
<MID>
3
</MID>
<DATE>
2014-02-20 20:15
</DATE>
<OBJECT>
Added client:
</OBJECT>
<ACTION>
Added client:
Added client to VMware policy
</ACTION>
<TEXT>
Ticket 1919191
New DHCP server needed to be backed up.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
</ELOG_LIST>
|
|
67670
|
Mon Mar 3 15:42:29 2014 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 2.9.2-2475 | Re: XML import Error |
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps. |
|
67671
|
Tue Mar 4 19:48:02 2014 |
| Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | Re: XML import Error |
| Andreas Luedeke wrote: |
|
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps.
|
Hi Andreas
That worked, thank you so much. now I'm on to a new error.
Now every time i try to do the import it crashed the elogd.
OS is windows server 2008 R2. I have the elogd installed as a service.
here is the even log:
Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86
I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?
|
| Attachment 1: new__2.xml
|
<?xml version="1.0" encoding="UTF-8"?>
<ELOG_LIST>
<ENTRY>
<MID>
2
</MID>
<DATE>
2014-02-24 22:28
</DATE>
<OBJECT>
Archived Client:
</OBJECT>
<ACTION>
Archived Client:
Archived Client to Manual_Archive and took a full backup of it
</ACTION>
<ENCODING>plain</ENCODING>
<TEXT>
ticket: 123456
Decommission of client.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
<ENTRY>
<MID>
3
</MID>
<DATE>
2014-02-20 20:15
</DATE>
<OBJECT>
Added client:
</OBJECT>
<ACTION>
Added client:
Added client to VMware policy
</ACTION>
<ENCODING>plain</ENCODING>
<TEXT>
Ticket 1919191
New DHCP server needed to be backed up.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
</ELOG_LIST>
|
|
67677
|
Tue Mar 11 15:17:36 2014 |
| Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | Re: XML import Error |
| Donald wrote: |
|
| Andreas Luedeke wrote: |
|
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps.
|
Hi Andreas
That worked, thank you so much. now I'm on to a new error.
Now every time i try to do the import it crashed the elogd.
OS is windows server 2008 R2. I have the elogd installed as a service.
here is the even log:
Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86
I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?
|
Anyone have any luck reproducing the error? or have suggestions on how to fix it? |
|
68581
|
Thu Mar 16 16:11:02 2017 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.9.2-2475 | Re: Duplicate entries | I've seen exact;y this effect, even though I have branching = 0 in my config file - so ordinarily no chance to have two
replies to an entry. My pointer aka mouse (I'm on Linux) is a bit dodgy, and sometimes disconnects/reconnects, so in effect gives a very fast double click. I've always assumed that was the cause of the problem. The two replies have incremental IDs, and both those IDs are listed in the "Reply to" header section of the entry. I'm not sure how this overcomes the branching = 0 detail, though.
That is what I have assumed, but if others see this on occasion, perhaps it's got a different cause.
| Alan Grant wrote: |
|
Periodically (rarely) on manually adding a record into Elog it generates a duplicate record with its own incremented ID and I don't know why. I just delete the duplicate in the meantime but would like to know if anyone else has seen this and whether their is a answer/fix for it. Thanks.
|
|
|
68706
|
Fri Nov 24 17:29:49 2017 |
| Michael Cianci | mcianci@lhs.org | Question | Windows | 2.9.2-2475 | Windows 10 | Sorry to bother you with such a simple question, but I am not an IT professional. We just received word that our IT department has plans to update our system to Windows 10 in 2018. Was wondering if our current version of ELOG was compatable with Windows 10? Thank You Very Much For Your Help. |
|
69266
|
Wed Dec 2 04:07:57 2020 |
| Harry Martin | harrymartin772@gmail.com | Question | Linux | 2.9.2-2475 | Re: Duplicate entries | I find that I can reply to a message ("original" message, if you will) without doing anything to the reply message (the "copy" of the original message, if you will). If I then submit it, it gets saved as a new message, identical to the one I replied to.
I read through the options at the end of the docs. I did not see anything about a way to suppress identical messages, or a way to force the user to make some kind of change to make the reply different from the original.
| David Pilgram wrote: |
|
I've seen exact;y this effect, even though I have branching = 0 in my config file - so ordinarily no chance to have two
replies to an entry. My pointer aka mouse (I'm on Linux) is a bit dodgy, and sometimes disconnects/reconnects, so in effect gives a very fast double click. I've always assumed that was the cause of the problem. The two replies have incremental IDs, and both those IDs are listed in the "Reply to" header section of the entry. I'm not sure how this overcomes the branching = 0 detail, though.
That is what I have assumed, but if others see this on occasion, perhaps it's got a different cause.
| Alan Grant wrote: |
|
Periodically (rarely) on manually adding a record into Elog it generates a duplicate record with its own incremented ID and I don't know why. I just delete the duplicate in the meantime but would like to know if anyone else has seen this and whether their is a answer/fix for it. Thanks.
|
|
|
|