Error on auto-opening ASCOM GS Sky Telescope

A place to report problems and bugs in SharpCap
Forum rules
‍

If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs

Please also read about Troubleshooting USB Issues before posting.

*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***

Please include the following details in any bug report:

* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
Post Reply
astrocalina
Posts: 37
Joined: Thu Jul 18, 2024 8:17 am

Error on auto-opening ASCOM GS Sky Telescope

#1

Post by astrocalina »

Hello,
when I connect my camera with the autoconnection the mount it doesn't connect, the log is the following (of course che mount is connected and powered on):
Error 20:33:32.942754 #13 Creating telescope mount ASCOM GS Sky Telescope : Exception of type 'NotRegisteredException' : Failed to create ASCOM Mount driver object for ASCOM.GS.Sky.Telescope (ASCOM GS Sky Telescope)
Stack Trace: at new SharpCap.MountProxy.ASCOM.MountWrapper(string deviceName, string progId, IUIDisableSource disableSource) in C:/Documents/Source Code/SharpCap/src/SharpCap.MountProxy.ASCOM/MountWrapper.cs:line 70
at IMountProxy SharpCap.MountProxy.ASCOM.MountFactory.OpenDevice(string deviceName, IUIDisableSource disableSource) in C:/Documents/Source Code/SharpCap/src/SharpCap.MountProxy.ASCOM/MountFactory.cs:line 54
at T SharpCap.ProxyFinder<T>.OpenDevice(string deviceName, IUIDisableSource disableSource) in C:/Documents/Source Code/SharpCap/src/SharpCap/Utils/ProxyFinder.cs:line 149
at IMountProxy SharpCap.Models.Mount.CreateProxy() in C:/Documents/Source Code/SharpCap/src/SharpCap/Models/Mount.cs:line 395 in IMountProxy SharpCap.Models.Mount.CreateProxy()
Error 20:33:32.944605 #13 Inner Exception : System.Runtime.InteropServices.COMException (0x80080005): Retrieving the COM class factory for component with CLSID {DFAC33EA-34DB-460D-810F-5EBFA40FB478} failed due to the following error: 80080005 Esecuzione del server non riuscito. (0x80080005 (CO_E_SERVER_EXEC_FAILURE)).
at object RuntimeTypeHandle.AllocateComObject(Void* pClassFactory)
at object RuntimeType.CreateInstanceDefaultCtor(bool publicOnly, bool wrapExceptions)
at new ASCOM.Com.DriverAccess.DynamicAccess(string ProgID) in J:/ASCOMLibrary/ASCOM.Com/ASCOM.Com.DriverAccess/BaseClass/DynamicAccess.cs:line 39
at new ASCOM.Com.DriverAccess.ASCOMDevice(string progid) in J:/ASCOMLibrary/ASCOM.Com/ASCOM.Com.DriverAccess/BaseClass/ASCOMDevice.cs:line 41
at new ASCOM.Com.DriverAccess.Telescope(string ProgID) in J:/ASCOMLibrary/ASCOM.Com/ASCOM.Com.DriverAccess/Telescope.cs:line 49
at ITelescopeV3 SharpCap.MountProxy.ASCOM.MountWrapper.CreateTelescope(string progId) in C:/Documents/Source Code/SharpCap/src/SharpCap.MountProxy.ASCOM/MountWrapper.cs:line 81
at new SharpCap.MountProxy.ASCOM.MountWrapper(string deviceName, string progId, IUIDisableSource disableSource) in C:/Documents/Source Code/SharpCap/src/SharpCap.MountProxy.ASCOM/MountWrapper.cs:line 62 in IMountProxy SharpCap.Models.Mount.CreateProxy()
Error 20:33:32.953600 #13 Async Connect to ASCOM GS Sky Telescope failed : Exception of type 'NotRegisteredException' : Failed to create ASCOM Mount driver object for ASCOM.GS.Sky.Telescope (ASCOM GS Sky Telescope) () in async Task SharpCap.Base.Interfaces.FakeAsyncConnectable<T>.DoInTask(Action a, CancellationToken cancellationToken, string action)+(?) => { }
Error 20:33:32.954700 #13 Inner Exception : System.Runtime.InteropServices.COMException (0x80080005): Retrieving the COM class factory for component with CLSID {DFAC33EA-34DB-460D-810F-5EBFA40FB478} failed due to the following error: 80080005 Esecuzione del server non riuscito. (0x80080005 (CO_E_SERVER_EXEC_FAILURE)).
at object RuntimeTypeHandle.AllocateComObject(Void* pClassFactory)
at object RuntimeType.CreateInstanceDefaultCtor(bool publicOnly, bool wrapExceptions)
at new ASCOM.Com.DriverAccess.DynamicAccess(string ProgID) in J:/ASCOMLibrary/ASCOM.Com/ASCOM.Com.DriverAccess/BaseClass/DynamicAccess.cs:line 39
at new ASCOM.Com.DriverAccess.ASCOMDevice(string progid) in J:/ASCOMLibrary/ASCOM.Com/ASCOM.Com.DriverAccess/BaseClass/ASCOMDevice.cs:line 41
at new ASCOM.Com.DriverAccess.Telescope(string ProgID) in J:/ASCOMLibrary/ASCOM.Com/ASCOM.Com.DriverAccess/Telescope.cs:line 49
at ITelescopeV3 SharpCap.MountProxy.ASCOM.MountWrapper.CreateTelescope(string progId) in C:/Documents/Source Code/SharpCap/src/SharpCap.MountProxy.ASCOM/MountWrapper.cs:line 81
at new SharpCap.MountProxy.ASCOM.MountWrapper(string deviceName, string progId, IUIDisableSource disableSource) in C:/Documents/Source Code/SharpCap/src/SharpCap.MountProxy.ASCOM/MountWrapper.cs:line 62 in async Task SharpCap.Base.Interfaces.FakeAsyncConnectable<T>.DoInTask(Action a, CancellationToken cancellationToken, string action)+(?) => { }
I don't have any J disk on my pc...
How could I solve my issue?
Thank you
Attachments
Log_2025-02-03T20_29_00-6456.log
(81.07 KiB) Downloaded 29 times
User avatar
admin
Site Admin
Posts: 17526
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Error on auto-opening ASCOM GS Sky Telescope

#2

Post by admin »

Hi,

no need to worry about the J drive showing in the log - that's actually recording the location of the code used to build some of the ASCOM libraries that go into SharpCap.

From the original error message and the 'NotRegisteredException', the most likely thing to cure the issue will be to uninstall the GreenSwampServer and then install it again. A 'repair' of the installation may also work. Something seems to have gone amiss with the GSS installation that is stopping SharpCap from connecting to the driver and a reinstall/repair should help.

I would also suggest making sure that all your software is up-to-date - SharpCap, GreenSwampServer and the ASCOM platform.

cheers,

Robin
astrocalina
Posts: 37
Joined: Thu Jul 18, 2024 8:17 am

Re: Error on auto-opening ASCOM GS Sky Telescope

#3

Post by astrocalina »

Hi,
thank you for your answer:
I've just upgraded everything and now I will try to reinstall GSS.
I will be back to you to give you a feedback.

Bye
astrocalina
Posts: 37
Joined: Thu Jul 18, 2024 8:17 am

Re: Error on auto-opening ASCOM GS Sky Telescope

#4

Post by astrocalina »

Hi,
it works thank you.
Now, maybe, I will try to schedule something to uninstall and install GSS automatically :)

Bye
User avatar
admin
Site Admin
Posts: 17526
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Error on auto-opening ASCOM GS Sky Telescope

#5

Post by admin »

Hi,

the loss of registration isn't something that should really happen - it tends to mean that the registry keys associated with the code needed to access the ASCOM driver have been removed or changed. Things like registry cleanup programs, installing or uninstalling the GSS software (or other software if the other installer is badly written) or rolling back windows to an earlier state could cause this, but general use should not.

cheers,

Robin
astrocalina
Posts: 37
Joined: Thu Jul 18, 2024 8:17 am

Re: Error on auto-opening ASCOM GS Sky Telescope

#6

Post by astrocalina »

Hi,
I have an other issue with GS Server 1.0.8.6 and the last SharpCap:
when I connect SharpCap GS Server I see "Connected Application: 1" but the mount doesn't connect automatically.
Last week (my last test) it was connecting automatically.

I don't know where is the issue.
Thank you
Attachments
screen01.jpg
screen01.jpg (25.96 KiB) Viewed 926 times
User avatar
admin
Site Admin
Posts: 17526
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Error on auto-opening ASCOM GS Sky Telescope

#7

Post by admin »

Hi,

assuming that you haven't got anything else set up to talk to the GS Server, then the 1 connected application will be SharpCap, which indicates that everything is working as it should for communication between SharpCap and GS Server.

If that is the case then I think you need to look for the cause of failure to auto connect to the hardware somewhere within GS Server - check settings or options, or possibly go back to an older version of GS Server if you have upgraded recently. I must admit that I haven't seen any problems like this, but I am still on version 1.0.6.5

thanks,

Robin
Post Reply