The fie size exceeds the limit allowed and cannot be saved.

Mar 29, 2014 at 2:07 AM
Edited Mar 29, 2014 at 2:11 AM
First, let me thank you for this awesome program ghostbuster, it is very useful!

I do have a problem. When i clock remove devices i get a message

" unhand;ed exception has occurred in your application. if you click Continue, the application will ignore this error and attempt to continue. if you click quit, the application will close immediately.

the fie size exceeds the limit allowed and cannot be saved".

I get this in the details tab:

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

************** Exception Text **************
System.ComponentModel.Win32Exception: The file size exceeds the limit allowed and cannot be saved
at System.Diagnostics.EventLog.get_OldestEntryNumber()
at System.Diagnostics.EventLog.StartListening(String currentMachineName, String currentLogName)
at System.Diagnostics.EventLog.StartRaisingEvents(String currentMachineName, String currentLogName)
at System.Diagnostics.EventLog.set_EnableRaisingEvents(Boolean value)
at Ghostbuster.Buster.WriteToEventLog(String message, EventLogEntryType elet)
at Ghostbuster.HwEntry.RemoveDevice()
at Ghostbuster.HwEntry.RemoveDevice_IF_Ghosted_AND_Marked()
at Ghostbuster.Mainform.Enumerate(Boolean RemoveGhosts, Boolean HideUnfiltered)
at Ghostbuster.Mainform.RemoveBtn_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.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 **************
Assembly Version:
Win32 Version: 2.0.50727.3623 (GDR.050727-3600)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

Assembly Version:
Win32 Version:

CodeBase: file:///C:/Users/carlosb1/AppData/Local/Apps/2.0/76J1B8QN.NHW/J7J6PC7C.TZD/ghos..tion_2db0c472ee4e4228_0001.0000_762d910d52757127/Ghostbuster.exe

Assembly Version:
Win32 Version: 2.0.50727.3620 (GDR.050727-3600)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/

Assembly Version:
Win32 Version: 3.0.6920.1453 built by: NetFX

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/WindowsBase/

Assembly Version: 1.7.4378.16959
Win32 Version:

CodeBase: file:///C:/Users/carlosb1/AppData/Local/Apps/2.0/76J1B8QN.NHW/J7J6PC7C.TZD/ghos..tion_2db0c472ee4e4228_0001.0000_762d910d52757127/Microsoft.Win32.TaskScheduler.DLL

Assembly Version:
Win32 Version: 2.0.50727.3623 (GDR.050727-3600)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/

Assembly Version:
Win32 Version: 3.5.30729.1 built by: SP

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/

Assembly Version:
Win32 Version:

CodeBase: file:///C:/Users/carlosb1/AppData/Local/Apps/2.0/76J1B8QN.NHW/J7J6PC7C.TZD/ghos..tion_2db0c472ee4e4228_0001.0000_762d910d52757127/IniFile.DLL

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/

Assembly Version:
Win32 Version: 2.0.50727.3074 (QFE.050727-3000)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/

Assembly Version:
Win32 Version:

CodeBase: file:///C:/Users/carlosb1/AppData/Local/Apps/2.0/76J1B8QN.NHW/J7J6PC7C.TZD/ghos..tion_2db0c472ee4e4228_0001.0000_762d910d52757127/WaitCursor.DLL

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/

************** 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 section.
The application must also be compiled with debugging

For example:

< jitDebugging="true" />

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.

so this happens even if i try to remove one device. anyways i click continue it scans but then frezes and does not remove the devices. weird
I have Vista 32 bit, this does not happen in my windows 7 64. Thanks!
Mar 29, 2014 at 6:34 PM

Ghostbuster uses a separate EventLog source. This event log is full and is not cleared or overwritten automatically (that was the default in the old days ;-)

So in the event log viewer search for the Ghostbuster Log and set it to overwrite if needed.

Apr 1, 2014 at 8:17 PM
I checked the event log and it is already overwriting and says number of events 0. Total mystery. I already installed it again and erased old logs and files. If i do press "continue" on the warning message it does the job but only one device at a time hehe :) As long as it works it is ok. If i ever find a solution i will post it . Thanks!