How can I capture the event log?

Please unzip GridJunctionLog.zip and copy the GridJunctionLog.exe file to your Windows Home Server desktop! Do not run from a UNC/network share location that would result in permission error.

Use Ctrl+A and Ctrl+C to copy and paste the log content.

Good Luck and keep us posted.

Thanks for the quick response.  It looks great but it would be more useful to me as a CSV file ("yyyy/mm/dd"," hh:mm","event description").  I had to do a lot of editing to get it into a form that Excel liked.

Is there a limit to how many events are saved or a time limit as to how long they are kept?  If not, can one purge outdated entries?  I have 712 entries since 12/31/08!  I wouldn't want to fill up my registry with these.

As far as a pattern of my particular events, they almost entirely appear clustered around 2AM, 6AM, 2PM, and 10PM every single day.  I'm sure they are not generated by anything I have control over (programmable thermostat, scheduled computer tasks, my lifestyle, etc.).  As I said, my power company reads the meter remotely over the power line itself (i.e. not through a phone connection) so I thought that may be the key.  The make usage figures available to me on their web site and I can display usage by the hour but I guess that doesn't mean they take a reading each hour - They could be interpolating from 4 readings per day at the times I see.

Don

712 entries in say 46 days - interesting that is no joke!

Please do not install the new 1.3.7 version: that would clear your current event history.

No, currently there is no time limit as how long these events are saved but one can easily clear these via the "clear all" button. 

Let me know if you need me to change the GridJunctionLog.exe to display it say using a tab delimited format like:

"yyyy/mm/dd"," hh:mm"               event title              event description

That explains why my data started on 12/31 instead of when I first installed GJ (Nov ?) - I installed GJ 1.3 on that date.  I missed the Clear All button.

I would like the GridJunctionLog.exe to create a comma separated file if it wouldn't be too much trouble: "yyyy/mm/dd"," hh:mm","event title","event description" would be perfect.

Thanks for being so responsive,
Don

Running the new version yielded the following error:

2009/02/15 01:57,Power Restored,CRUSTY restored normal power operations.
2009/02/15 01:57,Power Alert,CRUSTY using battery power.
2009/02/15 01:53,Brownout Event,CRUSTY detected a short term power abnormality.
2009/02/15 05:58,Power Restored,CRUSTY restored normal power operations.
2009/02/15 05:58,Power Alert,CRUSTY using battery power.
2009/02/15 05:54,Power Restored,CRUSTY restored normal power operations.
2009/02/15 05:54,Power Alert,CRUSTY using battery power.
2009/02/15 02:04,Power Restored,CRUSTY restored normal power operations.
2009/02/15 02:04,Power Alert,CRUSTY using battery power.
2009/02/15 02:01,Power Restored,CRUSTY restored normal power operations.
2009/02/15 02:01,Power Alert,CRUSTY using battery power.
The string was not recognized as a valid DateTime. There is a unknown word starting at index 0.
   at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
   at System.DateTime.Parse(String s, IFormatProvider provider)
   at System.Convert.ToDateTime(String value)
   at GridJunctionLog.MainForm.MainForm_Load(Object sender, EventArgs e)

I had already deleted the old version so I can't include the events in the previous format.

Don

whoops looks like it could not convert a datetime - what time zone local are you in?

Meanwhile I changed the exe to skip any dates/entries it cannot parse and it should append those to the end of the log.
 
GridJunctionLog.zip

Please keep me posted.

I am in US EST zone.

Here's the last lines of the program output.  After stripping off starting at the separator line of ====, there were 613 lines left vice 714 events listed on the GJ page. There were about 15 entries on January 3, none of which showed up in the listing.  And the GJ page listing that corresponded to the entry at 2:06:34 looked perfectly normal with Saturday spelled correctly.

2008/12/30 09:58,Power Restored,CRUSTY restored normal power operations.
2008/12/30 09:58,Power Alert,CRUSTY using battery power.
2008/12/30 09:54,Power Restored,CRUSTY restored normal power operations.
2008/12/30 09:54,Power Alert,CRUSTY using battery power.
======================================================================
OK we had to skip 99 entries because we could not convert these to the correct datetimeThese are the ones we had to skip:
Surday, January 03, 2009  2:06:34 AM

Don

Apologies I was not in a position to test the last two builds; just knocking out some code per your feedback - the latest is attached. Please  do post some of the 99 entries which should now be appended at the end.
Thanks

All entries from Saturdays were skipped and they were all listed as "Surday....  The below are just the first few.

======================================================================
OK we had to skip 99 entries because we could not convert these to the correct datetime!
These are the ones we had to skip:
Surday, February 14, 2009  9:57:00 PM
Surday, February 14, 2009  9:56:59 PM
Surday, February 14, 2009  9:53:39 PM
Surday, February 14, 2009  1:57:28 PM
Surday, February 14, 2009  1:57:27 PM
Surday, February 14, 2009  1:53:52 PM
Surday, February 14, 2009  1:53:51 PM
Surday, February 14, 2009  5:58:00 AM
Surday, February 14, 2009  5:57:59 AM
Surday, February 14, 2009  5:54:39 AM
Surday, February 14, 2009  2:07:52 AM
Surday, February 14, 2009  2:07:51 AM
Surday, February 14, 2009  2:03:40 AM
Surday, February 14, 2009  2:03:35 AM
Surday, February 07, 2009  9:57:03 PM
Surday, February 07, 2009  9:57:02 PM
Surday, February 07, 2009  9:53:39 PM
...

perfect! thank you- this is my fault but I now know what needs to be fixed.

Standby

Once more attached but this one should be better now =)

*EDIT* removed old attachment

This version listed all of the events but the AM/PM flag didn't make it.  Perhaps it could be in 24 hour format?