System.ArgumentOfOfRange exception in Eraser 6.0.7.1893

markx

New Member
Hi,
I do not know if this is a known problem.
Eraser 6.0.7.1893 crashes immediately upon launch on Windows 7, 64-bit.
This is from the Windows crash report:

<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7600 </Build>
<Product>(0x3): Windows 7 Home Premium</Product>
<Edition>HomePremium</Edition>
<BuildString>7600.16539.amd64fre.win7_gdr.100226-1909</BuildString>
<Revision>1</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
<ParentProcessInformation>
<ParentProcessId>3424</ParentProcessId>
<ParentProcessPath>C:\Windows\SysWOW64\cmd.exe</ParentProcessPath>
<ParentProcessCmdLine>&quot;C:\Windows\SysWOW64\cmd.exe&quot; </ParentProcessCmdLine>
</ParentProcessInformation>
<ProblemSignatures>
<EventType>CLR20r3</EventType>
<Parameter0>eraser.exe</Parameter0>
<Parameter1>6.0.7.1893</Parameter1>
<Parameter2>4bbfca0e</Parameter2>
<Parameter3>mscorlib</Parameter3>
<Parameter4>2.0.0.0</Parameter4>
<Parameter5>4a27471d</Parameter5>
<Parameter6>15d</Parameter6>
<Parameter7>24</Parameter7>
<Parameter8>System.ArgumentOutOfRange</Parameter8>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>6.1.7600.2.0.0.768.3</Parameter1>
<Parameter2>1033</Parameter2>
</DynamicSignatures>
<snipped system information />
</WERReportMetadata>

Thanks,
Mark
 
Just to get the context clear, you installed Eraser, and as soon as you tried to launch the program, you had this error. Is that correct?

If so, go to the 8th to 10th posts in this thread, and use the instructions there to check whether the folder 'Eraser 6' and the file Task List.ersx exist. If they do, delete the file and try to start Eraser. If they don't, come back and we'll go from there.

Incidentally, although I'm running a development build at the moment, I ran build 6.0.7.1893 on precisely the same OS as you for several months without problems. This difficult bit is to track down the effects of variations between individual systems ...

David
 
Deleting the .ersx file immediately fixed the crash-on-startup error.
Thank you!

I suggest making the fix instructions sticky in the forums
so that one searching can quickly find them.


Thanks!
Mark
 
markx said:
Deleting the .ersx file immediately fixed the crash-on-startup error ... I suggest making the fix instructions sticky in the forums
so that one searching can quickly find them.
I'm glad its fixed. Actually, there is already a sticky on fixing common problems in the FAQ sub-forum to this one, where (I'd guess) you'd expect and want it to be. For my reply to you, I linked to a thread where the instructions are specific to Windows 7, as you'd said that that was your OS.

David
 
Back
Top