ElmerBeFuddled Posted April 1, 2012 Posted April 1, 2012 (edited) Not sure if this was a net framework error, I assumed it was with PS I'd just opened so shut the error message straight away (Doh!!).Just after the start of my 3rd image pass, I get the warning and when I looked at W7T again I had a big red cross across the bottom progress area. Will say it didn't affect the running of the tool, just didn't know how much longer it would take!At this moment in time the 3rd pass is still running. I'll send the error file when it finishes if I get one. Edited April 1, 2012 by ElmerBeFuddled Quote
Legolash2o Posted April 2, 2012 Posted April 2, 2012 (edited) Any updates on this? Thanks Edited April 2, 2012 by Legolash2o Quote
ElmerBeFuddled Posted April 3, 2012 Author Posted April 3, 2012 (edited) As of yet, no. Even after numerous runs of W7T. If it occurs again and I get an error window, I'll be sure to get a snip before closing. BTW, wasn't asked to send error log for uploading, nor was one generated AFAIK.(Good to get back in here!!! ) Edited April 3, 2012 by ElmerBeFuddled Quote
Legolash2o Posted April 3, 2012 Posted April 3, 2012 Probably a direct .NET Framework error outside W7T then, i've seen another user experience it a while (7-8 months). Quote
Sterlin Posted April 3, 2012 Posted April 3, 2012 I received a runtime error during integration yesterday... the option "continue" allowed Win7 Toolkit to finish, although it had an elongated, red "X" in the lower section of the window. The program completed and produced expected results.The error text follows:See the end of this message for details on invokingjust-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index at System.Collections.ArrayList.get_Item(Int32 index) at System.Windows.Forms.ToolStripItemCollection.get_Item(Int32 index) at System.Windows.Forms.ToolStrip.OnPaint(PaintEventArgs e) at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs) at System.Windows.Forms.Control.WmPaint(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.StatusStrip.WndProc(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.5448 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll----------------------------------------W7T Assembly Version: 1.4.0.11 Win32 Version: 1.4.0.11 CodeBase: file:///C:/Users/Brian/Documents/OSwork/Win%207%20Toolkit/W7T.exe----------------------------------------System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll----------------------------------------System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll----------------------------------------System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll----------------------------------------System.Management Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll----------------------------------------Vista Api Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Brian/Documents/OSwork/Win%207%20Toolkit/Vista%20Api.DLL----------------------------------------SevenZipSharp Assembly Version: 0.64.3890.29348 Win32 Version: 0.64.3890.29348 CodeBase: file:///C:/Users/Brian/Documents/OSwork/Win%207%20Toolkit/SevenZipSharp.DLL----------------------------------------Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll----------------------------------------************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.For example:<configuration> <system.windows.forms jitDebugging="true" /></configuration>When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box. Quote
Sterlin Posted April 3, 2012 Posted April 3, 2012 I had the same issue... just posted in "Runtime error" thread.Sorry for the duplicate post!~S Quote
Legolash2o Posted April 3, 2012 Posted April 3, 2012 No worries, i merged the thread.Unfortunately i had this a while back and could never figure it out as it never happened again I'll try googling for a bit... Quote
ElmerBeFuddled Posted April 5, 2012 Author Posted April 5, 2012 Happened again just. Standard .Net Framework Error. Attached is the .Net log..NetError.txt Quote
Legolash2o Posted April 5, 2012 Posted April 5, 2012 (edited) Unfortunately, those errors did not tell me where the error happened, however i have discovered that code which catches errors did not work for everyone but me, so i've fixed that and from now on it will write errors like that to a text file, which i hope it will tell me where the issue is and it will be in v15. Edited April 5, 2012 by Legolash2o ElmerBeFuddled 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.