1

Closed

Exception calling "SaveImage" with "2" arguments. Value was either too large or too small for a decimal

description

I received this error when trying to process a SQL Server 2005 machine performance file.
This was with PAL v2.0.7 (I got the error also with v2.0.6)
I previously used Pal v1.35 for this machine without any problems.
 
Full error:
 
Exception calling "SaveImage" with "2" argument(s): "Value was either too large
or too small for a Decimal."
At C:\Program Files\PAL\PAL v2.0.7\PAL.ps1:1308 char:29
  • [Void] $oPALChart.SaveImage <<<< ($sSaveFilePath, $oPALChartImageFormat)
     
    • CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordE
      xception
    • FullyQualifiedErrorId : DotNetMethodException

file attachments

Closed May 30, 2012 at 5:15 AM by ClintH
No response from the user in 30 or more days.

comments

ClintH wrote Mar 16, 2011 at 5:26 AM

I don't know what could cause this. Can you provide more information? Can you post the %temp%\PAL.log file?

BillInEdmonton wrote Apr 13, 2011 at 5:17 PM

Sorry for being slow to get back. It is only occurring when I run it on Windows 7 64-bit (it seems to work when I use Windows Vista 32).

I don't appear to have a pal.log file created. Can this be configured somehow? I am using PAL from the command line.

Kid_Ego wrote Mar 23, 2012 at 1:27 PM

Exact same issue here. I recently updated to 2.2.1, had no problem with the other 3 server logs I parsed. Then this error twice on the same capture file. I checked and I have no pal.log file either. Could it be somewhere else besides just %temp%?

Kid_Ego wrote Mar 23, 2012 at 1:54 PM

Rolled back to 2.1, received the same error. Located the pal.log file (attached).

Kid_Ego wrote Mar 23, 2012 at 2:50 PM

FYI: On a hunch, I told PAL that the server had 8 processors insterad of teh actual 16 and the parsing worked.

Kid_Ego wrote Mar 30, 2012 at 3:49 PM

Just happened again.
Windows Server 2003 Enterprise x64 Edition.
5.2.3790 SP2 Build 3790
16 Procesors
8GB of RAM.

Testing the same theory and lieing to PAL by telling it there are only 8 Processors...

ClintH wrote Apr 10, 2012 at 3:04 AM

Have you tried running the analysis at an output location that has a smaller path? I can get this error when I use an output path that is very long. This seems to be a problem with the file system. Please let me know if this workaround works, so I'll know if I need to research a different problem.

So.... I forgot to enable the PAL.log writing functionality before releasing v2.2.1. Sorry. I plan on releasing v2.3 soon with multi-threading support, so I'll make sure to re-enable the logging.

Kid_Ego wrote Apr 11, 2012 at 5:24 PM

I just re-tested putting the capture file in a folder right off the root of C:.
Unfortunately I received the same error. When I lied to PAL and claimed 8 processors instead of the actual 16, it worked.

ClintH wrote Apr 12, 2012 at 6:25 AM

Can you send me the counter log through this web site or at my email address? clinth@microsoft.com. I'll debug it from there. Thank you.