SharpCap Forums

I am experiencing an issue where SharpCap Pro fails to connect to my iOptron CEM60 mount, despite the following:
• iOptron Commander 5750 is functioning correctly.
• ASCOM Platform 7 is up to date.
• All other accessories are properly recognized and connected without any issues.
Has anyone encountered this issue before? Any advice on how to resolve it would be greatly appreciated.
Thank you!
[img]

Hi,

that particular error is often associated with registry entries left behind by the uninstall of the ASCOM driver for the device. In particular, if you have installed a newer version of the ASCOM driver, then gone back to the older version, the uninstall of the newer version may have left behind registry entries that cause the problem you are seeing.

You have a couple of possibilities to fix this...

1) Update the ASCOM driver (probably part of iOptron commander) to the latest version

2) Fully uninstall and reinstall the ASCOM driver - this may or may not fix the problem

3) Manually clean out the conflicting registry entries.

If you want to try the manual clean out then the steps are

* Note down the long string of letters/numbers in the error message - the one starting '{E2AF3DA2...'
* Uninstall the iOptron commander application
* Run registry editor (regedit.exe)
* First try to locate the node HKEY_CLASSES_ROOT\CLSID\{E2AF3DA2-.....
* Inside that node you will find one called 'InprocServer32'
* Inside 'InprocServer32' there will be one or more nodes named with version numbers - ie '9.1.1.0'
* Click on each of the numbered nodes in turn and choose 'Edit' then 'Delete' (or just press the Delete key on the keyboard). Confirm the deletion of each of those numbered nodes
* Now try to locate the node HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{E2AF3DA2...
* Repeat the procedure of deleting the version numbered nodes inside the 'InprocServer32' node in that second place (if you only find one of the two places, don't worry, that should be fine)
* When you have done this in registry editor, reinstall iOptron commander and try again

As with any registry editing, take great care and only delete the numbered subnodes inside the correct 'InprocServer32' nodes - deleting the wrong bits can damage the system to the point that it won't boot any more.

Hope this helps,

Robin