WLE Crashing on 30-day report creation (on server 2008)

John Isenhart

13 years ago
updated 13 years ago
Fixed

Crashing on Server2008 when attempting Last-30-day report on previous/current month's IIS logs (HTML output). Appcrash error occurs when I manually attempt at about 7% into "Creating Report." I've cleared the cache and run manually to verify behavior. Many of the PNG and GIF files are populated from the HTML output, but at 7% it halts for a while then goes non-responsive.

I have the event log and error window crash data. From crash box detail:
Problem signature:
Problem Event Name: APPCRASH
Application Name: WLExpert.exe
Application Version: 7.1.0.4
Application Timestamp: 4d6cec38
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000096
Exception Offset: 025eea6a
OS Version: 6.1.7600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
...

crash html 2008

Replies 7

Oldest first
Newest first Oldest first

Michael

13 years ago

We have several questions on the problem:

Do you have the "Create HTML reports for additional time ranges" setting enabled in Profile Properties > Time Range?

Does the same error occur if you create a PDF report instead of the HTML one?

How much memory does the program use according to the Task Manager when it crashes?

Reply Link

I'll answer in order asked! :-)
- I DO have the Additional Time Ranges setting enabled currently.
- If I create a PDF report - running it now. It may take some time so I'll post once it completes/errors out.
- The memory seems to peak around a gigabyte just prior to the lockup.

It may be worth noting a couple other things -
- This report WAS working for the last week or so running at a scheduled time overnight (one run per day). This crash just started last night.
- The logfile criteria is set to the current month and then the prior month using the %Date-1m% so we DO have an increasing amount of data per execution as the month progresses.
- Last thing - this is a decent server class box - 8 cores, 16gb RAM SATA RAID-5 storage, so we're not hitting any ceilings hardware-wise.
Thanks
--John--

PDF is crashing as well during the "Creating Report" process. The memory had climbed to 1,094MB of memory utilized at that time.
If this is a simple volume issue, the only work-around I can think of is to use by-day log references, but it would mean that I have to put 30 log references to get the last 30 days using the %Date-xD% method. Can WLE support a log list that long?
-- John --

OK last update - I just attempted to run without the "Create HTML reports for additional time ranges" setting enabled in Profile Properties > Time Range with the same crash.

It seems that the problem appeared because the program needs too much memory to create one of the report tables. In such case the program should show an error message with information which table cannot be generated. However, this functionality was broken in version 7.1 and the program crashed instead of showing the error.

We have fixed the bug and published the fixed version. You can download it from http://www.weblogexpert.com/download.htm (we haven't changed the version number).

Well, the crash still occurs but the crash report did come up this time. It started creating the report, got to around 36% and then the memory usage exploded from ~250 MB up to ~1.1 GB and then crashed.

The report reads as follows:
"Cannot load data from cache file Too much memory is required to load report table "Access Statistics > Paths > Top Paths Through Site"

Not sure how to proceed.
Thanks
John Isenhart

The simplest way to fix the issue is to uncheck the "Top Paths Through Site" table in "Profile Properties > Report > Custom report contents".

However, if you wish to get this table for your log files, it is necessary to determine why the program needs so much memory to create the table.

Probably there is a very large number of different page names and so a very large number of different paths. This issue may occur if you have enabled showing queries in file names and there are a lot of different queries (e.g. because of session ID in queries). If there are some query parameters that don't need to be shown, it is possible to hide them in "Profile Properties > General > Custom analysis settings > Files > Query parameters in file names" - you need to set this option to "Exclude specified" and enter parameters to hide.