Program locks up everynight at midnight

I have been running the new compiler versions for a while.
Since starting WD locks up between 12 midnight to 12:05AM every night.
I can get it to skip a night of locking up if I stop the program and restart after about 6PM.
Then it will not lock up 6 hours later (midnight) but will do so at midnight the next night.
Presently running WeatherDisplay37P-86 but just downloaded WeatherDisplay37P-87 and will install now.

Not running anything extra on this Windows 7 system and see no other indication of problems except with WD.
Would appreciate any help.
Thanks

I am having the exact same problem. Will happen ever 48 hours. I even updated to the latest download 88. I will have to reinstall a older non complier version which perfectly. It is a shame because I like all the new features that have been added.

Please help.

Check the usual stuff.

Ensure the virus scanner is excluding the WD directory.
Disable the fancy account stuff for Windows7 like account control (or what ever it is called).

It might be that it wants to do multiple things at those times and locks some files etc.
Not sure really but check the usual suspects first I guess.

H

try build 96
I have changed how the averages/extremes is used (its now left in memory, which will speed things up etc)

I had the lockup the last two nights at 12:10 AM - build 95. The reports thst normaly run just after midnight like precipitation detail and daily almanac did not run so I have missed these for 2 days now

Frank

The update did the trick here. Thanks.
Lockups have stopped with WDisplay.

But, now wdwebcamcapture is locking up every night. Will not run 24 hours. Stops at random times. Mostly between 8:30PM and 10:00PM. I have to stop it with Taskmgr.
I can reboot the computer, or
stop and restart WDisplay, or
use taskmgr to stop then restart wdwebcamcapture with the same results.
Again, Wdisplay and all other support programs (WUrapidfire, Weatherbug, etc) are running, only wdwebcamcapture stops.
May have been occurring prior but with WDisplay locking could not tell.

Currently running v10.37P build 89 but downloading v10.37P build 97 now.

Do you have the “Keep Live” box ticked?
I had the same problem and found that ticking this box stopped the lockups.
Maybe also do a full new install of the latest drivers for the webcam, just to be on the safe side. :wink:

Build 97 fixed the midnight lockup for me. Thanks Brian

Frank

My lockups started when I updated to 95 the other day from a pre-new-compiler version. They happen at 9:10 when the system is trying to upload the daily averages/extremes. I updated to 97 tonight and then investigated why WD was locking at that time.

If I do a manual ‘Upload all now’ and quickly get the FTP upload to display by double-clicking it I see the usual handshake etc. and files being uploaded, it appears to upload the files OK, and then continually says, ‘there are 1 more things to do’ which scolls so fast that by the time I kill it with Task Manager there is no hope of figuring anthing else out.

I was hopeful that 97 would fix this after Frank said it did for him. Perhaps because he is doing a midnight reset and I’m doing a 09:00 one?

EDit to add: My online Daily Weather Report has not updated since I went to 95, which was about 48 hours ago and the FTP process never ends, it just locks WD out of updating - only a reboot fixes it when I get home from work - Kev

no lock up here and all av/ext and noaa reports are up to date , latest version, 9am reset

I tried renaming ftpupd.exe and did a reinstall to ensure it was using the latest ftpupd.exe which I noted had changed recently.

I have downloaded the setup exe again and run it.

The main display reports 97, ftpupd reports 9.12 After uploading webcamimage.jpg, the ftp program continually reports there are 1 more things to do, as previously stated.

I’m stumped. Perhaps reverting to build 44 would be best?

I managed to duplicate the problem, using an affected users settings
the problem only occured if set to create a custom logfile, in the setup, logfile set

can came about because of a change in the sequence of events in the code, and ended up that the month data file was loaded before the current data was saved

I have fixed this now, in build 99

sorry about that to all have been affected

so, use build 99
then go action, convert logfile to data files, to update your month data file

then it should auto update after that

(this affected the averages/extremes and nooa reports not being up to date anymore)

What CPU type/speed, memory, and OS do you have?

That certainly fixed it for me - thanks once again Brian.

WDwebcamcapture program locked up again (as everyday).
Tried to close WeatherD with File/Save-Exit as I normally do. But got the following application error window…
(Exception Access violation of module WeatherD.exe at 013D1022, Access violation at address 0177D1022 in module “WeatherD.exe”, read of address 00000290.)
Had to close (End Process) WeatherD and WDwebcamcapture with taskmgr.
Running Version 10.37Q Build 00 downloaded 16th Oct.

(For information: using WDwebcamcapture with IPcamera and have it set to Restart Daily and Restart Regularly.)

Did file conversion per above and will try again.

Thanks

Updated on Sunday to 37Q Build01 3rd Nov from 37p B 99

WD has locked up both mornings since at 09:08.

Reverting to 37p99 to see if that fixes problem.

The webcam program stopped locking up for me after installing version 10.37Q-01
Thank you.

I get periodic lock-ups at 00:09 which I assume is due to lots of tasks to do relating to the previous day.
It is only once or twice a month.

Solved it with a workaround of sorts by installing Clickoff

This will close the WD dialogue box and the program restarts on it’s own.
There are other ways to do it but this has done the trick several times now for me.
The only ‘problem’ is that you may not be aware it has been stalling.

edit: will try latest WD version as it sounds like the problem is fixed.

Hi all,

I am getting the same lockup problem. I haven’t tested the latest release (Version on 23 November 2010 - 19:51:29), but all the new compiler versions freeze. I will see how it goes tonight.

Regards.

–Santi–

not along of information to go on…
what speed PC?
how much memory?

I have discovered that the last 31 days data graph (monthtodategraph.gif) takes a long time to process, due to all the data being loaded
and that is a bottle neck with the daily averages/extremes updates
I will see If I can stream line that graph update more