out-lineoutput : Exception of type 'System.OutOfMemoryException' was thrown.


After PAL was run aprox. 40 minutes I got next error:
------------------------------------------- 8< -------------------------------------------<
WARNING: Please post errors or problems with this tool to the PAL web site located at http://www.codeplex.com/PAL with the
following error message and a brief description of what you were trying to do. Thank you.
out-lineoutput : Exception of type 'System.OutOfMemoryException' was thrown.
+ CategoryInfo          : NotSpecified: (:) [out-lineoutput], OutOfMemoryException
+ FullyQualifiedErrorId : System.OutOfMemoryException,Microsoft.PowerShell.Commands.OutLineOutputCommand
------------------------------------------- 8< -------------------------------------------<
Probably because of a lot of previous errors? :
------------------------------------------- 8< -------------------------------------------<
The variable '$SeriesOfCounterValues' cannot be retrieved because it has not been set.
+ CategoryInfo          : InvalidOperation: (SeriesOfCounterValues:Token) [], RuntimeException
+ FullyQualifiedErrorId : VariableIsUndefined
------------------------------------------- 8< -------------------------------------------<
You can find more technical details about my computer (where PAL was run) in attached file (MsInfo32.7z) and input data for PAL in next file (PAL_MS-SQL-Server_2005-2008_00002.7z):

file attachments

Closed Oct 3, 2013 at 6:08 PM by ClintH


ClintH wrote Nov 28, 2012 at 4:35 AM

When working with counter logs with a lot of counters and data, PAL might require a lot of memory to process it. Based on the error, it sounds like you are running the 32-bit version of PAL. 32-bit applications are limited to 2 GB of virtual memory by default and its likely that PAL needs more then 2 GB of memory. The only way to resolve this is to use a smaller log file with less counters in it or use the 64-bit version of PAL on 64-bit Windows or Windows Server. 64-bit applications have 8 TB of virtual address space allowing them to take advantage of more RAM.

kurlati wrote Jan 24, 2013 at 1:33 PM

Is there a way to estimate the amount of RAM needed for a 1GB log file with the System Overview template? Or a way to estimate the amount of RAM by providing the # of counters and time being monitored?

ClintH wrote Jan 24, 2013 at 5:55 PM

I haven't done that kind of monitoring or testing of the tool to know. Please understand that it is just me and I do this work during my free time. The variable that you have to consider is the number of counter instances in the long - not necessarily the size. Also, I remove any unnecessary data from the log as well making a 1 GB log file to only 200 MB in some cases. If you come up with some rough numbers, then that would be helpful. I suggest monitoring the amount of available memory (\Memory\Available MBytes) on the system before and during processing. Available memory is also displayed in Task Manager under the Performance tab.