tbaehnck Posted February 28, 2019 Report Share Posted February 28, 2019 Hi all, I've a problem since a few weeks with sequence. I thought after I switch to another autoslew-version but not sure about it. I have AS 5.2.4.7 and Sequence 0.2.1.1 and also try 0.2.1.3 with the same error. If I start a sequence I get this error message: Informationen über das Aufrufen von JIT-Debuggen anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung. ************** Ausnahmetext ************** System.NullReferenceException: Die Objektvariable oder die With-Blockvariable wurde nicht festgelegt. bei Microsoft.VisualBasic.CompilerServices.Symbols.Container..ctor(Object Instance) bei Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack) bei Sequencer.RunSequence.RefocusFilter(Int16 NewFilterNr) bei Sequencer.RunSequence.ChangeToFilterAndRefocus(Int16 Filter) bei Sequencer.RunSequence.StartSequence() bei Sequencer.frmSequenceRun.cmdRun_Click(Object sender, EventArgs e) bei System.Windows.Forms.Control.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnClick(EventArgs e) bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ButtonBase.WndProc(Message& m) bei System.Windows.Forms.Button.WndProc(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Geladene Assemblys ************** mscorlib Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8793 (QFE.050727-8700). CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll. ---------------------------------------- Sequencer Assembly-Version: 0.2.1.3. Win32-Version: 0.2.1.3. CodeBase: file:///C:/Program%20Files/Sequence/Sequencer.exe. ---------------------------------------- System.Windows.Forms Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.5491 (Win7SP1GDR.050727-5400). 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.8791 (QFE.050727-8700). 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.5495 (Win7SP1GDR.050727-5400). 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.5483 (Win7SP1GDR.050727-5400). 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.5483. 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/Sequence/Interop.PinPoint.DLL. ---------------------------------------- mscorlib.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8793 (QFE.050727-8700). CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll. ---------------------------------------- Interop.MaxIm Assembly-Version: 1.0.0.0. Win32-Version: 1.0.0.0. CodeBase: file:///C:/Program%20Files/Sequence/Interop.MaxIm.DLL. ---------------------------------------- System.Xml Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.8773 (QFE.050727-8700). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll. ---------------------------------------- System.Configuration Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll. ---------------------------------------- 63tk0aa1 Assembly-Version: 0.2.1.3. Win32-Version: 2.0.50727.8791 (QFE.050727-8700). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll. ---------------------------------------- Microsoft.VisualBasic.resources Assembly-Version: 8.0.0.0. Win32-Version: 8.0.50727.5420 (Win7SP1.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/8.0.0.0_de_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll. ---------------------------------------- System.Windows.Forms.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.5420 (Win7SP1.050727-5400). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll. ---------------------------------------- ************** JIT-Debuggen ************** Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der Konfigurationsdatei der Anwendung oder des Computers (machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden. Die Anwendung muss mit aktiviertem Debuggen kompiliert werden. Zum Beispiel: Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten Ausnahmen an den JIT-Debugger gesendet, der auf dem Computer registriert ist, und nicht in diesem Dialogfeld behandelt. The the sequence log file: 00:49:54.619: ************************************************************************ 00:49:54.622: Starting Sequence on Target C:\ProgramData\ASA\Sequence\Target Files\NGC 4216.trg with Exposure settings C:\ProgramData\ASA\Sequence\ExposureSettings\L_180s_mlpt.exp 00:49:54.626: Running now Nr. 1 of this Sequence 00:49:54.748: Starting Sequence C:\ProgramData\ASA\Sequence\Target Files\NGC 4216.trg 00:49:54.749: Target RA: 12h16m52,7s DE: +13d02m34s 00:49:54.750: Focus RA: DE: 00:49:54.754: Focus star was not defined and focus is disabled but I need a place to synch, so autoselected with RA = 12h16m52,7sDE= +14d21m12s 00:49:54.755: Checking now for Pier side for object 00:49:54.766: Cannot finish complete Object on Eastside 00:49:54.774: Have to start on East side because cannot be started on West side 00:49:54.775: Not same Target, check if we have to Autofocus or Synch 00:49:55.626: No Autofocus, because NeverDuringSequence is selected 00:49:55.626: Moving Scope to Autofocus Positon 00:49:55.682: Slewing to 12h16m52,7 +14°21m12 Pierside East Any Idea whats going wrong and what to do? Thanks and best regards Thomas Link to comment Share on other sites More sharing options...
MarkS Posted February 28, 2019 Report Share Posted February 28, 2019 Thomas, I had a similar problem last December, which was still there after I had completely removed Sequence and its Program Data files, and built a new Data file from scratch.... Desperate, I had a look at the Windows permissions (Windows7) and found that somehow they were not set as they should have been. I still cannot explain how that happened, but I reset them in both Autoslew and Sequence Program Files AND Program Data files - and Presto!!!!! system all worked again! So this may not be your problem, but to check with Windows 7 go to the Program Files>Autoslew>(Right Click)>Properties>Security. Check that all permissions are allowed for Administrators, SYSTEM, and Users. Do the same for Sequence and for both Program Data files. I don't know about Windows10, but this may give you a lead.... Someone more knowledgeable than I may have some better ideas - anyway let us know what you find. And good luck! Mark Link to comment Share on other sites More sharing options...
tbaehnck Posted April 17, 2019 Author Report Share Posted April 17, 2019 (edited) Hi Mark, First thank you for your answer and sorry for doing it so late. I tried it but it doesn't help. Then I have done a full new installation of Windows, autopsies, sequence etc. And I get the same error. Any ideas, anybody? Thank you and best regards Edited April 17, 2019 by tbaehnck Link to comment Share on other sites More sharing options...
nakbrooks Posted April 17, 2019 Report Share Posted April 17, 2019 Did you install any other software (not ASA) around the time that Sequence stopped working? In particular any Microsoft .NET software? Was there a Windows 10 update about that time? Personally I use my observatory PC only for astronomy and I disable Windows updates on it. Link to comment Share on other sites More sharing options...
tbaehnck Posted April 19, 2019 Author Report Share Posted April 19, 2019 Hi Nigel, In between I made a new clean installation of Windows 7 with all updates before I install autoslew and sequence. But the same error has come up again. After a phone call with Asa yesterday, I deleted the system.ini of sequence and made all settings again, but this doesn't work neither. Autoslew and sequence are the the latest stable ones, no betas. Other software on the astronomy PC is focusmax, maximdl 5, pinpoint, and ccdinspector. Thats all. Link to comment Share on other sites More sharing options...
tbaehnck Posted April 22, 2019 Author Report Share Posted April 22, 2019 (edited) Hi all, I can report, that the problem is solved . i install the the ascom driver of the atik 460 new, install sequence again and what I think the most important I didn't check the "don't use readout mode" option in the ccd settings. My camera doesn't have different readout modes, but if I didn't check the option and click "read from ccd" the readout mode change to "standard". And now all work fine. I still have errors in the sequence log (error setting readoutmode to 0) but no crash of the programm and I will be able to use sequence for more than pointingfiles again. . Thanks for helping and clear skies Thomas Edited April 22, 2019 by tbaehnck Link to comment Share on other sites More sharing options...
nakbrooks Posted April 22, 2019 Report Share Posted April 22, 2019 Sounds the same issue as this one last year. http://forum.astrosysteme.com/index.php?/topic/1045-strange-new-problem-with-sequence/?fromsearch=1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now