Jump to content


Photo

Unhandled Exception in Sequence


  • Please log in to reply
4 replies to this topic

#1 DaveS

DaveS

    Member

  • Members
  • 21 posts

Posted 27 May 2017 - 06:17 PM

I think this has occured after a .net update.
Just trying to open Sequence gets an unhandled exception error from .net framework referring to index out of bounds of the array.
I've updated Sequence to 2.11 and tryed "repairing" the .net framework to no avail.

Anyone else had this? Or any ideas on where to go from here?

#2 DaveS

DaveS

    Member

  • Members
  • 21 posts

Posted 28 May 2017 - 01:48 PM

Well it gets stranger.
I think I've tracked it down to a problem reading the filters from the wheel, possibly in Maxim.
By avoiding this it looks like I can run Sequence as I could before, at least as far as plate solving for PinPoint. Still cannot run an actual sequence.

#3 MikePaling

MikePaling

    Member

  • Members
  • 50 posts
  • LocationUK ... Notts

Posted 30 September 2017 - 11:23 AM

Hi ...

It looks like I am having a very similar problem :-(

When I ask Sequence to read the filters on my Moravian G2-8300 I get a similar error message.

 

At the minute I am unable find a solution.

 

Am I using old Moravian ASCOM drivers for the filter wheel or am I doing something silly???



#4 MikePaling

MikePaling

    Member

  • Members
  • 50 posts
  • LocationUK ... Notts

Posted 30 September 2017 - 12:20 PM

Hi again ...

I have just downloaded the log from my error message ....

I only get this error message when I ask Sequence to access my Moravian CCD. When I ask MaximDL to take test images everything seems to work correctly ... I can pick and choose my different filters and ask it to take different exposures without any obvious problems.

It is only when I start to try to use Sequence that I run into this error message ... and this log is complete mumbo-jumbo to me!!!

Any advice from anybody ????

 

The error log is as follows .....

 

******************************************************************************************

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

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Sequencer.frmSettingsCCD.cmdReadFilters_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.8689 (QFE.050727-8600)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Sequencer
    Assembly Version: 0.2.0.5
    Win32 Version: 0.2.0.5
    CodeBase: file:///C:/Program%20Files%20(x86)/Sequence/Sequencer.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
    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.8690 (QFE.050727-8600)
    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.8681 (QFE.050727-8600)
    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.8670 (QFE.050727-8600)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
Microsoft.VisualBasic.Compatibility
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.8670
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic.Compatibility/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.Compatibility.dll
----------------------------------------
Interop.PinPoint
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Sequence/Interop.PinPoint.DLL
----------------------------------------
Interop.MaxIm
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Sequence/Interop.MaxIm.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8679 (QFE.050727-8600)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.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.

 



#5 MikePaling

MikePaling

    Member

  • Members
  • 50 posts
  • LocationUK ... Notts

Posted 30 September 2017 - 03:32 PM

It looks like I have managed to sort out my "error" problem :-)))

 

At first, after getting some advice from a friend, I deleted the " Endpars.ini " file. Which is found at [ C: > Program Data > ASA > Sequence.]

Apparently this file can get corrupted and is not deleted if Sequence is repaired or a newer version installed.

 

However this did not fully solve the error problem.

 

So I deleted the "Endpars" file again and installed the latest version of Sequence (v0.2.1.1) .... it now everything works in Sequence :-)))))

 

Hopefully plain sailing now ... until I hit the next problem!

Mike






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users