Cumulus Support

My computer restarts every morning at 3:00. I use Startwatch to start VVP and Cumulus. This has been working well for several months. The last three mornings Cumulus has failed to start and produces a bug report which is attached, along with the diags folder. I upgraded from build 980 to build 982 yesterday, but same problem this morning. It could possibly be related to a Windows 7 service pack update a few days ago?

Thanks.

This is the same problem, but appearing in a slightly different place, as was reported by someone else very recently. When Cumulus asks for the logger data since the last time it was running, Virtual VP (in this case) is returning a large number of entries, even though it was only a few minutes ago that Cumulus was closed:

27/02/2011 03:09:37.756 : VP2: Downloading history from 27/02/2011 3:05:00 AM
27/02/2011 03:09:37.756 : y=2011 m=2 d=27 h=3 m=5
27/02/2011 03:09:44.214 : VP2: DownloadData_V = 2554
27/02/2011 03:09:44.214 : VP2: GetNumberOfArchiveRecords_V = 2554
27/02/2011 03:09:44.214 : VP2: Number of history records = 2554

Furthermore, the timestamp in the first entry is invalid in some way, which is causing Cumulus to crash when it tries to process it. I'll put the same check in for this case, as a work around for Virtual VP misbehaving.

Okay, thanks Steve.

Steve, the range check error hasn't happened since updating to build 983 several days ago. I assume that's one of the bugs fixed in that build. Thank you.