I'm getting the following HRESULT:0x80020008 (DISP_E_BADVARTYPE) when I try to use CCDSoft V5 (latest version). CCDAP3 boots CCDSoft,finds the camera (ST2000) and turns it on, and about this point the error occurs.

Works fine using MaximDL.

Suggestions (other than use MaxIm)?

James


************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80020008): Bad variable type. (Exception from HRESULT: 0x80020008 (DISP_E_BADVARTYPE))
at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateSet(Object o, Type& objType, String name, Object[] args, String[] paramnames, Boolean OptimisticSet, CallType UseCallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments)
at m.eb()
at m.t6()
at m.fj(Object A_0, EventArgs A_1)
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 **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINNT/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
CCDAutoPilot
Assembly Version: 3.41.7.0
Win32 Version: 3.41.7.0
CodeBase: file:///C:/Program%20Files/CCDWare/CCDAutoPilot3/CCDAutoPilot.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINNT/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.832 (QFE.050727-8300)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINNT/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.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
RestoreState
Assembly Version: 2.0.0.0
Win32 Version: 2.0.0.0
CodeBase: file:///C:/Program%20Files/CCDWare/CCDAutoPilot3/RestoreState.DLL
----------------------------------------
SyD.Shareware.Registration
Assembly Version: 2.3.2007.1
Win32 Version: 2.3.2007.1
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/SyD.Shareware.Registration/2.3.2007.1__4a5d6e6bca524051/SyD.Shareware.Registration.dll
----------------------------------------
OutlookPanes
Assembly Version: 1.0.4.0
Win32 Version: 1.0.4.0
CodeBase: file:///C:/Program%20Files/CCDWare/CCDAutoPilot3/OutlookPanes.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Interop.PinPoint
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/CCDWare/CCDAutoPilot3/Interop.PinPoint.DLL

Hi James,

It is always recommended that you start the underlying programs, in this case connect the camera, before starting CCDAP. See if the error reproduces when the startup proceeds this way. See the CCDAP help system under Troubleshooting and the hint after step 4.

Brand-new user here, setting up CCDAP for the first time. I'm getting this same error. CCDSoft and TheSky are both already started, with server services on both configured for remote program control.

I've checked versions, ensured .NET is installed, gone through the troubleshooting and hints. I've been using CCDSoft successfully for quite some time to control the camera; that works just fine.

Any clues?

This message has been edited. Last edited by: astrotrf,

More information:

Defying the instructions, I did a "connect" in CCDAP3 with TheSky6 and CCDSoft5 not running. It fired both applications up, and then gave the message "no guider present" (my CCD camera - an STL-11K - was not powered on at the time).

I powered the CCD camera on and tried again, with TheSky6 and CCDSoft5 not running. Both fired up again, and CCDSoft5 made a connection to the camera. The instant the connection was established, CCDAP threw the error.

I then shut everything down and fired up TheSky6 and CCDSoft5 first. I then started CCDAP3 and did a "connect". Again, CCDSoft5 connected to the camera, and when the connection succeeded, CCDAP3 threw the error.

As a final attempt, I shut everything down, fired up TheSky6 and CCDSoft5, and connected to the camera. I then started CCDAP3 and did a "connect". After a just-barely-noticeable delay (connecting to TheSky6 first, maybe?), CCDAP3 again got the error.

I'm stuck. If anyone has any idea what else to try, I'd appreciate it.

Thanks.

This message has been edited. Last edited by: astrotrf,

Hi Terry,

I just found out that one of the CCDSoft automation commands is incompatible with .NET running under Windows 2000. This may be the cause of the error you are seeing if you are getting same error as James reported.

Are you using Windows 2000?

> Are you using Windows 2000?

Yup. Do you think you'll be fixing this, or will I need to upgrade to XP?

Thanks.

Hi Terry,

I am not sure. I think the issue is internal to CCDSoft. However, I tried something that may or may not work. Temporarily replace CCDAutoPilot.exe with that in the attachment and see if you can get past the initial error. If so, then the fix concept will work and I will have to apply it throughout the CCDAP source code. If not, then the only alternative is an XP upgrade.

Let me know how you make out.

ccdap3421test5.zip (327 KB, 14 downloads) Win2K possible fix

Hi John, Terry,

I tried using John's temp version, and with STL11K under CCDSoftV5 with latest upgrades, same result.

James

John,

Misfortunately, the fix did not work. What appears to be the same error occurs under exactly the same circumstances.

There are two probably irrelevant differences in behavior, though. Firstly, when allowing CCDAP3 to start TheSky6 and CCDSoft5, when the error window pops up, it now pops up on *top* where it is visible on the screen. Previously, it popped up *underneath* the other application windows and was hidden. Secondly, when allowing CCDAP3 to start the other applications, clicking "Quit" in the error window tears down CCDSoft5 now (but leaves TheSky6 running); the previous behavior was that both applications stayed running.

I dread the idea of upgrading to XP; it's going to mean *weeks* of work. Can I return CCDAP3 for a refund (not saying I will, just that I want to consider the possibility)?

Thanks, James. I was afraid of that. At this point, I have done everything I can do from the CCDAP end. I'll drop a note to the Bisques asking them to make the necessary change but I don't know how long that will take.

Hi John, Terry,

I DO have a recently-acquired copy of XP Pro available, but, like Terry, I really, REALLY, don't want to pursue that course of action.

I'm pretty confident that I can run under MaxIm without the problem, but that will have to be determined later today.

I'll let you know whether or not MaxIm solves this glitch for me.

Best regards,

James

Terry,

I highly recommend *against* allowing CCDAP to launch server applications. From the help system under troubleshooting:

Hint: It is always best to start the lowest level programs first and then load the higher level programs next. For example, assume you are using RoboFocus to control your focuser, FocusMax for focusing and CCDSoft to control your camera. Load and start RoboFocus, confirming it connects to and can control your focuser hardware. Next Load CCDSoft, confirming it connects to your camera. Take a short image to be sure. Next, load FocusMax since it must control both RoboFocus and CCDSoft. Finally, load CCDAutoPilot. If you close any program out of order, then you should close the chain and restart in the appropriate order. If you close CCDSoft, you must therefore close CCDAutoPilot and FocusMax. Then restart CCDSoft, restart FocusMax and restart CCDAutoPilot. Failure to start programs properly or in the proper order may cause subsequent automation failure.

Secondly, when an exception is thrown, as in this case, all bets are off with respect to operational stability.

Rather than installing XP as an upgrade, do yourself a favor and install it fresh. Sure, you will need to reinstall all your applications but you will get better stability in the long run. I have migrated to a Mac platform and am running XP in virtual machines so I've had to do three clean XP installs with the attendant application reinstalls. Be sure you fully update XP before proceeding to application installs. Keep choosing Windows Update until you get no more updates. Then install your applications. It takes around 8 hours if you have all your apps and registration keys handy. Not too bad to move to a more current OS, all things considered.

We can discuss the refund issue when necessary offline.

John,

First, I want to thank you for your very quick response and extraordinary effort in working on this problem.

I know to fire up the applications first, then CCDAP. I only mentioned letting CCDAP start the applications because that procedure is what enabled me to pin down exactly where and when the failure was occurring. I mentioned the behavioral differences just to verify that I was in fact running a different executable than before.

I agree with you completely about installing XP fresh rather than upgrading. In fact, I'm going to move to a new machine so I can keep the W2K machine available for comparison while I switch over.

> It takes around 8 hours if you have all your
> apps and registration keys handy.

That's a *really* big "if". :-) And doesn't take into account the fact that I have to chase down all of the application data and refigure all of the tweaking I've done to them!

I have a nephew who is a real Windows tool and he's dead flat out *enthusiastic* about watching me go through the pain of a switchover to XP, so it looks like that's what I'll be doing.

You're welcome, Terry. Good luck with the upgrade and if you have any problems, get your nephew on the case