Closed MarkBaggett closed 6 years ago
Hi Mark, I received the above error when I run the program. Your assigned task was created on Jul 10 was that of this year? The most recent exe is posted from 1 yr ago so I am running the most recent. Is there any workaround or have you been able to solve the issue. Thank you! 19 Oct 17
Hi. I committed a CSV only version of the tool a minute ago. If you wouldn't mind giving that a try and seeing if it resolves your issue I would appreciate it. You lose XLSX and some of the features it offers but hopefully it resolves the CRASH that some users are experiencing with very large Application Event tables. Email my gmail account directly at lo127001 if you wouldn't mind sharing the results and or a copy of the SRUDB.DAT file that is causing the crash.
Thanks, Mark
I've released a new version of SRUM_DUMP that creates CSV files instead of XLSX. This avoids the memory error that some of you have experienced when writing XLSX files to disk. CSV = No EXCEL == no crash.
Note that the current template has some fields that contain XLSX formulas (Total bytes, etc) and formatting. This will not do anything in a CSV file. You will want to open the XLSX_TEMPLATE and remove any calculated fields or delete the columns in the resulting CSV files.
I was given an example of a SRUM.DAT file that I am unable to process. (Thank you Martin WIlling!) While processing the file the tool produces the following output:
The first line "Unable to find table ..." isn't a problem. This is just a warning that indicates that the SRUM file you are analyzing doesn't contain that table. No big deal. The next line "I was unable to write the output file..." is a problem. In this case the error is not caused by permissions or the path as the error message indicates. The problem is that the system is running out of Memory. Unfortunately MemoryErrors can not be always be caught in Python (See docs https://docs.python.org/2/library/exceptions.html#exceptions.MemoryError ) so the error message returned by the program isn't at all helpful. Usually after the word "ERROR:" you would see what the error is. If NOTHING appears after the word "ERROR:" then you are probably having the same issue. When I run this through the debugger I can clearly see that it is a memory error...
There were some recent changes to openpyxl in dealing with memory usage and large spreadsheets. The current release was using openpyxl (2.4.7). This is an open issue that I will have to resolve. I'm working on it now.