Eraser Crash on "Add Data" (Incorrect function)

Status
Not open for further replies.
P

Petersgc

New Member
When trying to create a new Task and clicking on the button "Add Data" the program crashes with the following error:

EreaserError.png


Detailed Error Message:
Code: 
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80070001): Incorrect function. (Exception from HRESULT: 0x80070001)
   at Eraser.Util.VolumeInfo..ctor(String volumeId)
   at Eraser.Util.VolumeInfo.get_Volumes()
   at Eraser.TaskDataSelectionForm..ctor()
   at Eraser.TaskPropertiesForm.dataAdd_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Eraser
    Assembly Version: 6.0.6.1376
    Win32 Version: 6.0.6.1376
    CodeBase: file:///C:/Program%20Files/Eraser/Eraser.exe
----------------------------------------
Eraser.Manager
    Assembly Version: 6.0.6.1376
    Win32 Version: 6.0.6.1376
    CodeBase: file:///C:/Program%20Files/Eraser/Eraser.Manager.DLL
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
Eraser.Util
    Assembly Version: 6.0.6.1376
    Win32 Version: 6.0.6.1376
    CodeBase: file:///C:/Program%20Files/Eraser/Eraser.Util.DLL
----------------------------------------
Eraser.DefaultPlugins
    Assembly Version: 6.0.6.1376
    Win32 Version: 6.0.6.1376
    CodeBase: file:///C:/Program%20Files/Eraser/Plugins/Eraser.DefaultPlugins.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.1 built by: SP
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Eraser.resources
    Assembly Version: 6.0.6.1376
    Win32 Version: 6.0.6.1376
    CodeBase: file:///C:/Program%20Files/Eraser/en/Eraser.resources.DLL
----------------------------------------
BevelLine
    Assembly Version: 1.0.3589.29437
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Eraser/BevelLine.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Eraser.Manager.resources
    Assembly Version: 6.0.6.1376
    Win32 Version: 6.0.6.1376
    CodeBase: file:///C:/Program%20Files/Eraser/en/Eraser.Manager.resources.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Eraser Ver: 6.06.1376
OS: Windows XP SP2
Running the latest .Dotnet checked with Windows-update

Any Help would be greatly appreciated as the program is unusable.
 
I'll need the configuration of all your drives and partitions on your computer as well as where they are mounted. It's a bug, but I lack information to solve it...
 
HDD Configuration

Disk0 - Basic 74.52GB - NTFS - (ST3802110A) (IDE) (C:\)
Disk1 - Dynamic 279.46GB - NTFS - (ST330083) (SATA) (G:\)
Disk2 - Basic 465.76GB - NTFS - (ST350064 1AS) (SATA) (E:\)
Disk3 - Basic 698.64GB - NTFS - (ST375064 0ns) (SATA) (S:\)

Disk4 - RAID5 1397.27 GB - NTFS - (3x ST375064 0ns) (SATA) (R:\)

*Raid Controller onboard Nvidia nForce

If there was an issue somewhere my guessing would be its something to do with the raid ;)
 
How about the mount points? Could I have them too? Are any of the disks partitioned (including EFI ones)

I'm actually suspecting the Dynamic disk; the RAID should appear to the system (and hence to Eraser) as a single normal drive.
 
Useing the MountVol Program I am given this information. Is this what you require?

\\?\Volume{a4dab9de-992d-11db-b93c-806d6172696f}\
C:\

\\?\Volume{f1d53f52-95d8-11dc-8980-001a92b8a94f}\
S:\

\\?\Volume{ad1aad40-95b8-11dc-a8b0-806d6172696f}\
E:\

\\?\Volume{41e7fa4e-95d8-11dc-897f-001a92b8a94f}\
R:\

\\?\Volume{d6f84468-eb1d-432c-a314-547da339bcd3}\
G:\


No disks are partitioned and the dynamic disk shows up as a normal hard disk volume.


**Edit i have updated my Previous post to included the drive letters as I believe that is what you mean by "Mount Points"
 
I'll need a stack trace -- could you PM me an email address (citing this topic) so I can send a debug build down your way? I need a memory dump to be able to see where the crash is (and so I can fully make sense of your problem here)

And you're right, dynamic disks seem to be fine (I've only tested on a Basic disk though, I'll try a Striped, Spanned and RAID-5 disk in a moment)
 
Striped (RAID-0), Mirrored (RAID-1), RAID-5, Spanned (JBOD) and Basic volumes all work fine, it's definitely the RAID setup; please drop me a PM and I'll send a debug build your way.
 
Sorry, I'm going to lock this topic, could you please go to Trac instead -- a bug is already reported there and I don't want to shuttle back and forth. See http://eraser.heidi.ie/trac/ticket/289.
 
Status
Not open for further replies.
Back
Top