crash when I run a task

cryptonym

New Member
Since 6.07 was so problematic for me, never finishing, leaving random huge files, etc, I tried 6.1.

version 6.1.0.2243
hard crash of app, kills gui and taskbar icon

Steps to create:
create new task, named fubar
manual run
unused disk space of C:
erase cluster tips
save & run
nearly instant death.

From the windows event log:

.Net Runtime 2.0 Error report

EventType clr20r3, P1 eraser.exe, P2 6.1.0.2112, P3 4c5ee1f6, P4 system.management, P5 2.0.0.0, P6 4889dedd, P7 e0, P8 3f, P9 system.management.management, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This has been happening on all revs of 6.1 I've tried.

Erase trash works. Rightclick on a file works. Unused space blows up with or without the clear tips.
 

DavidHB

Active Member
Assuming that the Eraser UI crashes when you try to run a free space erase, there do seem to be issues with your .NET installation; I note that the error message appears to relate to .NET 2.0, while Eraser needs .NET 3.5. Try downloading and separately installing .NET 3.5 from the Micrososft page.

It might also be worth checking whether there is an Eraser Task log entry for the failed task. But your symptoms are rather unusual and suggest an installation issue.

David
 

cryptonym

New Member
DavidHB said:
Assuming that the Eraser UI crashes when you try to run a free space erase, there do seem to be issues with your .NET installation; I note that the error message appears to relate to .NET 2.0, while Eraser needs .NET 3.5...
Windows shows the following are installed:
Microsoft .Net Framework 2.0 Service Pack 2
Microsoft .Net Framework 3.0 Service Pack 3
Microsoft .Net Framework 3.5 SP1
Microsoft .Net Framework 4 Client Profile
Microsoft .Net Framework 4.0 Extended

I'll see if it will allow me to reinstall 3.5 over the existing and post the results.

Where would one look for the log file? Also, after the crash the job disappears from the Schedule as though it never existed.

Lastly, 6.0.6 did not crash the UI, but never would finish the cleaning.
 

cryptonym

New Member
I downloaded .Net3.5SP1 again and ran a repair. Rebooted. Ran same test. Same failure.
 

DavidHB

Active Member
The FAQ (link below) have a topic for new users of Eraser 6; that tells you how to find the log. But if the task is not in the Schedule, the log entries will also have been deleted.

If .NET is not the issue (given what you say, this seems likely), the Eraser installation may be the issue. A single failed installation can, in some circumstances, prevent subsequent correct installation. To remove Eraser completely, uninstall, and follow the guidance in this thread, which deals with a different problem, though the suggested solution is the same. I also suggest that, if you can, you run a Registry cleaner. Then reinstall build 2243, and see if that works. You may well need to run Eraser as administrator (details in the FAQ) to erase free space, but the system should not crash. If that doesn't work, I shall need to defer to Joel, as to what you should try next.

David
 

Joel

Active Member
I've seen this in very rare cases where the WMI interface is not accessible to the user. Please check if you are able to access that (through MMC) as that's how Eraser determines that you've got shadow copies (aka system restore points). The crash is really just at the check for shadow copies -- so maybe you can have a look and see if you have something weird about the configuration your computer has.
 

DavidHB

Active Member
Joel

Please could you be a bit more explicit about what needs to be done? All the links I have found so far, including those at Microsoft seem to me to be way outside most users' comfort zone.

David
 

Joel

Active Member
Perhaps one straightforward way (which I just thought of) would be to run perfmon, which AFAIK uses WMI to access the system counters. I may be wrong, but I believe there was a System Restore/VSS counter there.
 

cryptonym

New Member
Joel said:
Perhaps one straightforward way (which I just thought of) would be to run perfmon, which AFAIK uses WMI to access the system counters. I may be wrong, but I believe there was a System Restore/VSS counter there.
I only had 2 items listed in WMI section in perfmon. Maybe under some other specific tag?

I uninstalled, deleted the task file and ran ccleaner. Reinstalled.

All work being done while logged in as administrator, including running of Eraser.

What I did now was run mmc, and add in the WMI plugin. And set it to verbose logging under the properties. I then ran eraser. Here are the wmi log contents from the runs.
Framework.log:
DLL Logged out of framework: CimWin32 08/30/2010 10:02:54.551 thread:2188 [d:\nt\admin\wmi\wbem\sdk\framedyn\wbemglue.cpp.4079]
CimWin32 -> Dll can NOT Unload 08/30/2010 10:02:54.551 thread:2188 [d:\nt\admin\wmi\wbem\providers\win32provider\common\dllcommon.cpp.93]

wbemcore.log:
(Mon Aug 30 10:00:24 2010.1479109) : GetUserDefaultLCID failed, restorting to system verion(Mon Aug 30 10:01:15 2010.1529906) : GetUserDefaultLCID failed, restorting to system verion(Mon Aug 30 10:02:53 2010.1628281) : CALL ConnectionLogin::NTLMLogin
wszNetworkResource = \\.\root\default
pPreferredLocale =
lFlags = 0x0
(Mon Aug 30 10:02:53 2010.1628281) : DCOM connection from X\Administrator at authentiction level Privacy, AuthnSvc = 10, AuthzSvc = 0, Capabilities = 0
(Mon Aug 30 10:02:53 2010.1628281) : GetUserDefaultLCID failed, restorting to system verion(Mon Aug 30 10:02:53 2010.1628281) : CALL CWbemNamespace::ExecQuery
BSTR QueryFormat = WQL
BSTR Query = select * from SystemRestore
IEnumWbemClassObject **pEnum = 0x41EFDA8
(Mon Aug 30 10:02:53 2010.1628281) : CALL CWbemNamespace::ExecQueryAsync
BSTR QueryFormat = WQL
BSTR Query = select * from SystemRestore
IWbemObjectSink* pHandler = 0x0
(Mon Aug 30 10:02:53 2010.1628281) : STARTING a main queue thread 564 for a total of 1
(Mon Aug 30 10:03:05 2010.1640296) : STOPPING a main queue thread 564 for a total of 0


wbemprox.log:
(Mon Aug 30 10:01:15 2010.1529906) : Using the principal -RPCSS/x-
(Mon Aug 30 10:01:15 2010.1529906) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x0
(Mon Aug 30 10:02:53 2010.1628265) : Using the principal -RPCSS/x-
(Mon Aug 30 10:02:53 2010.1628265) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x0

winmgmt.log:
(Mon Aug 30 10:02:53 2010.1628265) : CForwardFactory::CreateInstance
 

DavidHB

Active Member
cryptonym said:
Any other ideas?
Sorry, no. I was waiting for Joel to respond, as he set you down that track.

David
 

Joel

Active Member
Nope, I'm stumped too. I can just add an exception handler to silence the error, but the root of the problem isn't solved... should I?
 
Top