Issue
Running SevenReports a C++ Run Time error. Happens either in Archive data reports or database reports
yyyy-mm-dd hh:mm:ss
Environment
I/NET Seven version 2.16 to current
Cause
Scope of Data yyyy-mm-dd hh:mm:ss
Resolution
The C++ Runtime error or crash of SevenReports is due to a timeout problem because the archived data is so much information. What you will need to do is a couple of things listed below:
Run the archive file SevenReport or ArchiveSevenReport file with the following steps in mind
1. If using Archived reports, mount the archive file with the desired dates to search
2. when the date range comes up on the screen, offering to search with date, hour, minutes, and seconds yyyy-mm-dd hh:mm:ss limit the time range. The whole key here is to limit the time range. Example of range is below.
Run the archive file SevenReport or ArchiveSevenReport file with the following steps in mind
1. If using Archived reports, mount the archive file with the desired dates to search
2. when the date range comes up on the screen, offering to search with date, hour, minutes, and seconds yyyy-mm-dd hh:mm:ss limit the time range. The whole key here is to limit the time range. Example of range is below.
In other words, search for only 2 minutes on just one day. Do not put in three days, or three hours. Only search within a very limited search window. The crash occurs because there are huge archive or database entries with thousands of transactions that have to be sorted and searched through.
The crash was due to the report program attempting to generate a report with to much data to sort through. Be patient. Even on old computers, with XP, 500MB or RAM, and limited resources, the reports will be produced.
Time and time again, this issue comes across. Using my old computer in the lab, the database from the customer is loaded, the archive files are loaded and still it works every time. The C++ Run Time error appears when expanding the search to more data and crashed the report. But limiting the amount of time to minutes or perhaps one hour, produces a report. (For an example of unusual examples: there have been 2 minutes of time for the search criteria, and 38,000 pages of report produced.)
2010-08-16 09:00:00 until 2010-08-16 09:02:00
One thing you may want to look into at your site if you are experiencing large amounts of data for reports is Scan Interval. Read TCON300 for more info.
Information on Scan Interval and how this information is collected in the database. This is important because the more data you collect, the faster the scan rate interval, the more data will be in the reports.
Input and Output Points Point Database Parameters
The Scan Interval field is used with all point types. Enter a number between 1 and 255. This is the length of time in seconds that elapses between point scans.
If the point is an external input point, the controller scans the point at the interval you specify here, and updates its state/value in RAM memory of the DCU.
If the point is an external output point, or an internal input or output point, the scan interval determines how often a calculated point equation controlling the point (if applicable) is processed.
If the point is an indirect input or output point, the scan interval governs the time it will take to go to the “old data” state.
The default scan interval is 10 seconds for input points and 60 seconds for output points. All points can have their own unique scan intervals. All external discrete input points are scanned for discrete contact changes at 100 millisecond intervals.
Note: Defining an individual scan interval reduces available RAM memory in the DCU by approximately four bytes. You can conserve DCU memory by using the same scan interval for multiple points.
