Getting error messages once an hour

Ask a Question
,
1

Hi Brian,

Build 35 was going great guns till this morning (Sunday) then it started throwing errors at 1 minute past the top of the hour every hour through the day.


ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 7:01:26 AM 03/13/11
Above error or program log occured at :7:01:26 AM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 8:01:08 AM 03/13/11
Above error or program log occured at :8:01:08 AM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 9:01:10 AM 03/13/11
Above error or program log occured at :9:01:10 AM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 10:01:12 AM 03/13/11
Above error or program log occured at :10:01:12 AM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 11:01:19 AM 03/13/11
Above error or program log occured at :11:01:19 AM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 12:01:20 PM 03/13/11
Above error or program log occured at :12:01:20 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 1:01:22 PM 03/13/11
Above error or program log occured at :1:01:22 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 2:01:22 PM 03/13/11
Above error or program log occured at :2:01:22 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 3:01:24 PM 03/13/11
Above error or program log occured at :3:01:24 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 4:01:24 PM 03/13/11
Above error or program log occured at :4:01:24 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 5:01:25 PM 03/13/11
Above error or program log occured at :5:01:25 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 6:01:20 PM 03/13/11
Above error or program log occured at :6:01:20 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 6:26:54 PM 03/13/11
Above error or program log occured at :6:26:54 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 7:01:20 PM 03/13/11
Above error or program log occured at :7:01:20 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 8:01:17 PM 03/13/11
Above error or program log occured at :8:01:17 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 9:01:17 PM 03/13/11
Above error or program log occured at :9:01:17 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 10:01:19 PM 03/13/11
Above error or program log occured at :10:01:19 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 11:01:18 PM 03/13/11
Above error or program log occured at :11:01:18 PM 03/13/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 12:01:20 AM 03/14/11
Above error or program log occured at :12:01:20 AM 03/14/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 1:01:19 AM 03/14/11
Above error or program log occured at :1:01:19 AM 03/14/11
ERROR: Access violation at address 0067E5C6 in module 'WeatherD.exe'. Read of address 00000028 at time/date 2:01:19 AM 03/14/11
Above error or program log occured at :2:01:19 AM 03/14/11

I had checked the system after the Daylight Saving Time changed and found that I hadn’t applied the time zone fixes to the copy of Windows 2000 on the weather system! #-o I applied the fix at ~4:30 am and everything was chugging along again with the new time. Then this stuff happened! :? The restart happened that I have set for 3:42 am on Sunday and Wednesday, so it was a new instance of WD running.

Any idea where to look for what might be causing this?

George

2

try running the debug version to see if that creates an error report , if and when the error occurs again
(I presume it will be with a internet file update)

3

Well running the beta debug seems to have scared the error away! 8O :lol: Nothing in the programerrorlog.txt, but did have the error in the attached pic twice during the day. Also videolastday.flv was only 3 hours long, 7:30 - 10:30 am, but videolastday.mp4 and videolastday.wmv ran from 7:30 am to 7:54 pm just over 12 hours. 8O :? #-o

I’m gonna try the full install of build 35 again and see if the error creeps back again or not, but the flash video not going past 3 hours duration is weird considering the Windows media video is created off the same mp4 file as the flv is and it went the full day. :wink: #-o

George

moviemkrerr.JPG
moviemkrerr.JPG573×264 13.1 KB

4

Well the error messages I was having went away on both the debug and full version build 35, but now the moviemaker is throwing up errors, yesterday 3 times, today once. I have attached the popup and event viewer pics from the latest error. The moviemaker doesn’t seem to want to make flv videos longer than 3 hours on my system. 8O :? #-o Again today I have an flv video that runs from sunrise till 10:30 am, but the mp4 and wmv videos both run the full day. I have attached a snap of my settings for the moviemaker if that’ll help.

George

moviemkrerr1.JPG
moviemkrerr1.JPG573×264 13.1 KB

moviemkrerr2.JPG
moviemkrerr2.JPG402×445 26 KB

settings.JPG
settings.JPG878×672 46.4 KB

5

not sure why you are getting that error
its some memory error

try this update
http://www.weather-display.com/downloadfiles/moviemaker.zip
which has error debug added to it
see if shows an error report

6

Okay Brian,

Sent off in 2 emails 2 separate EurekaLog files from the system when it was doing the last hour video and the allday video.

George

7

its an error with the actual component used
try deleting the time stamped web cam image files
as there might be a corrupted one

8

Hi Brian,

Okay, I added a few more lines to my backup/maintenance script that runs nightly to kill off the timestamped images. I’ll let it run for a day and see if any errors show, if something shows I’ll fire off a copy of the EurekaLog to you to look over.

George

9

Hi Brian,

Made no difference killing off the time stamped webcam images, everything was running good from sunrise till the 11:13 allday video generation, then every time since at 12:13, 13:13… etc. Seems to die when trying to create the allday flv file, the mp4 and wmv are both okay and full length, the flv ends around 10:40 am according to the playback and won’t have anymore video added for the rest of the day, but the mp4 and wmv run from sunrise to sunset. :? I know that the base video is the mp4 and the flv and wmv are created from that file, so why the flv bombs but not the wmv has got me stumped. :roll: :? #-o

Sitting with fingers crossed,

George

10

I think I have fixed the problem
use this new update
http://www.weather-display.com/downloadfiles/moviemaker.zip
vers 3.8

11

Hi Brian,

You nailed it this time!!! =D> =D> The 6 pm run had no “BONKK!!” accompaniment this time and a full day till 6:11pm flv video was produced. :smiley: :wink:

Hope this means this error has had its day and has now left the building! :lol: :wink:

I’ll keep my ears open for any error sounds, and check the system at least once a day to see everything is running okay. :wink:

Great work! =D> :thumbright:

George

12

yes, looks like I have fixed it
which is good news

problem was, the FTP upload was started before the file had been finished creating (early in the day with less data it would not happen)