Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   XML import Error, posted by Donald on Thu Feb 27 15:15:55 2014 new__2.xml
    icon2.gif   Re: XML import Error, posted by Andreas Luedeke on Mon Mar 3 15:42:29 2014 
       icon2.gif   Re: XML import Error, posted by Donald on Tue Mar 4 19:48:02 2014 new__2.xml
          icon2.gif   Re: XML import Error, posted by Donald on Tue Mar 11 15:17:36 2014 
Message ID: 67669     Entry time: Thu Feb 27 15:15:55 2014     Reply to this: 67670
Icon: Question  Author: Donald  Author Email: don.drummel@gmail.com 
Category: Question  OS: Windows  ELOG Version: 2.9.2-2475 
Subject: 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  656 Bytes  | Hide | Hide all
<?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>
ELOG V3.1.5-fe60aaf