Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 628 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 627, 628, 629 ... 806, 807, 808   Next  
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  67669   Thu Feb 27 15:15:55 2014 Question Donalddon.drummel@gmail.comQuestionWindows2.9.2-2475XML 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>
  67671   Tue Mar 4 19:48:02 2014 Reply Donalddon.drummel@gmail.comQuestionWindows2.9.2-2475Re: 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 Reply Donalddon.drummel@gmail.comQuestionWindows2.9.2-2475Re: 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?

  65835   Thu Apr 17 19:56:41 2008 Smile Don Perreadperrea@uwo.caQuestionWindows2.7.3Custom Links in each column, in the display list?

Using the "Link Display  =" I can turn of the link to each individual entry, however, I would like to have a custom link in one of my columns. Is this possible?

 

Thanks for this wonderful tool.

 

Don

  65924   Mon Jul 14 16:23:26 2008 Warning Don Perreadperrea@uwo.caQuestionWindows2.7.4TCK-##### stopped Working
  65925   Mon Jul 14 16:25:21 2008 Warning Don Perreadperrea@uwo.caQuestionWindows2.7.4TCK-##### stopped Working

We have been successfully using the TCK-##### for several months and suddenly today it has stopped incrementing. We were at ticket # 40 and this morning any new tickets come up as 12 and never increment? We have tried restarting the elog service. Any suggestions would be appreciated.

 

Thank You

 

Don

  65926   Mon Jul 14 17:19:13 2008 Reply Don Perreadperrea@uwo.caQuestionWindows2.7.4Re: TCK-##### stopped Working

Don Perrea wrote:

We have been successfully using the TCK-##### for several months and suddenly today it has stopped incrementing. We were at ticket # 40 and this morning any new tickets come up as 12 and never increment? We have tried restarting the elog service. Any suggestions would be appreciated.

 

Thank You

 

Don

My apologies for posting this question. I have found the solution.

We had two log books each with the same variable called "Ticket" but different values. When an entry from one was Moved to the other the counter was confused. I had to manually change the value of "Ticket" to match the convention of the log book that the entry was now in.

 

Thanks

 

 

  68359   Fri Jul 15 19:46:26 2016 Entry Donjang.dongwook@gmail.comBug reportAllELOG V3.1.0-241Escape character [ or ] doesn't work within [url]

Here is the problem:

[url=http://example.com?arrays[]=v1&arrays[]=v2]click here[/url]

How can I escape [] inside url tag?

\[\] seems not working.

Goto page Previous  1, 2, 3 ... 627, 628, 629 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6