Is there a way to export logs, posted by Alex Kühnel on Mon Oct 3 10:02:36 2016 
|
hello
Is there a way to export logs from elog (for example after I have selected a filter) to txt or csv...
I found the "Download" attribute but this works for only one elog entry...
regards |
Re: Is there a way to export logs, posted by Alex Kühnel on Mon Oct 3 10:18:19 2016
|
shame on me, there is a way!
I can search with find and then export as csv file
/alex
| Alex Kühnel wrote: |
|
hello
Is there a way to export logs from elog (for example after I have selected a filter) to txt or csv...
I found the "Download" attribute but this works for only one elog entry...
regards
|
|
Datetime format with elog client, posted by Alan Grant on Wed Oct 26 16:39:38 2016
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.
|
|
Re: Datetime format with elog client, posted by Alan Grant on Wed Oct 26 21:41:42 2016
|
UPDATE:
As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.
I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.
| Alan Grant wrote: |
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.
|
|
|
Re: Datetime format with elog client, posted by David Pilgram on Wed Oct 26 22:15:46 2016
|
Hi Alan,
I have no idea if this helps but the Date and Time formats in the config file internally interconnect, as I discovered in trying to define them separately. Define one, and the other is defined.
I only mention this as I spent some hours trying to sort out the issue, only to learn it was a "feature" that Stefan didn't want to correct as it may affect too many others. I can understand that, and made a different solution to what I wanted to do.
| Alan Grant wrote: |
|
UPDATE:
As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.
I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.
| Alan Grant wrote: |
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.
|
|
|
|
Re: Datetime format with elog client, posted by Alan Grant on Thu Oct 27 04:16:10 2016
|
I really appreciate your reply David.
There's only one Datetime defined field that I'm working with so I'm not sure what you mean, if you don't mind elaborating? It sounds interesting.
The only thing I gather right now from what you're saying is that there's essentially two locations where a field can be defined - in the Config file, or via the format of the data itself in the client command - but I could be wrong.
| David Pilgram wrote: |
|
Hi Alan,
I have no idea if this helps but the Date and Time formats in the config file internally interconnect, as I discovered in trying to define them separately. Define one, and the other is defined.
I only mention this as I spent some hours trying to sort out the issue, only to learn it was a "feature" that Stefan didn't want to correct as it may affect too many others. I can understand that, and made a different solution to what I wanted to do.
| Alan Grant wrote: |
|
UPDATE:
As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.
I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.
| Alan Grant wrote: |
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.
|
|
|
|
|
Re: Datetime format with elog client, posted by Andreas Luedeke on Thu Oct 27 11:18:17 2016
|
Yes, this is a known bug of ELOG, see elog:68404
| Alan Grant wrote: |
|
UPDATE:
As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.
I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.
| Alan Grant wrote: |
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.
|
|
|
|
Error starting elog 3.1.2 on Windows server, posted by Peter K on Mon Oct 31 09:51:02 2016
|
Hi,
I'm trying to upgrade ELOG 2.9.2, which I have been used many years, to the new version (3.1.2).
I can't run the new version even from the command line:
c:\Program Files (x86)\ELOG1>"c:\Program Files (x86)\ELOG1\elogd" -c "c:\Program Files (x86)\ELOG1\elogd.cfg"
Access is denied.
Message box appears with message:
c:\Program Files (x86)\ELOG1\elogd.exe is not a valid Win32 application.
What do I do wrong ?
I'm trying to use my old config file. New default config gave the same result :-( |