Error 0x80131040 and iOptron CEM26

[AngusMcDuff]

There is a similar 2023 posting involving this error and the ZWO EAF. Periodically, I have had problems with port conflicts when using this mount and an Optec focus motor. I have resolved them by changing the startup order and/or cycling the power on/of. Nothing has worked lately. I have installed all the latest drivers. I can connect directly to Ioptron Commander and the mount is recognized and works properly. If I then try to connect from SharpCap Pro, I get error message 0x80131040. If I restart everyting and try to connect to the mount from SharpCap, i still get the error message and the mount will not power up and connect.

I read that this issue could be with .NET Core versions and settings but that is beyond my paygrade.

Has anyone resolved this issue?

Thanks
Rich

[AngusMcDuff]

Using a suggestion in an old post, I was able to connect to the mount using the ASCOM Device Hub Telescope. It's a little clunky but seems to be working. There is clearly something wrong with a driver or software but if this works, I'll be happy enough.

[admin]

Hi,

good to hear that you managed to get things working using the Device Hub.

The error code typically means that there is some information in the registry about the ASCOM driver that doesn't match the information on disk. Sometimes an uninstall and reinstall of the affected ASCOM driver may help fix the problem, but not always. It's also worth making sure that you have the latest version of the affected ASCOM driver (the error can occur if the registry lists a newer version than the version that's actually on disk).

cheers,

Robin

[AngusMcDuff]

Hello Robin

I'm still having problems. I have updated all the device drivers. I also updated the mount firmware. I tried different cameras. Nothing helps. I have attached a SharpCap log. It seems that SC found the device (mount) at 06:58:39.392217 and completed some actions but then the problem starts. Would you interpret this and offer some suggestions? I also sent an email to iOptron. Thanks

Rich

[admin]

Hi Rich,

OK, so it definitely looks like there might be something up with the way that information is stored about that ASCOM driver in the registry.

If you are comfortable using the 'regedit' tool, open it up and navigate to the registry key

Code: Select all

HKEY_CLASSES_ROOT\CLSID\{C13F2FED-7D46-479C-ADB1-A199E40F787C}\InprocServer32

You should see some other sub-keys inside that key - I only have one which is called '9.1.1.0' as shown below.

Screenshot 2024-12-11 121954.png (11.42 KiB) Viewed 892 times

these sub keys represent different versions of the ASCOM driver, and it sounds possible that you might have more than one there, and maybe the highest version is a higher version than the actual version of the ASCOM driver on disk. At least, that's a common cause of the error you are getting.

If you do have multiple versions there, or a higher version than the version of iOptron commander you have installed, the fix should be as follows...

* Uninstall iOptron commander
* Press F5 in registry editor to refresh the view of the registry and see what has been left behind after the uninstall in that part of the registry
* Delete the InprocServer32 key (which will also zap any remaining subkeys with rogue version numbers)
* reinstall iOptron commander

Always be careful when using regedit - deleting the wrong things can trash your system!

I also noticed in your log that you have a couple of odd errors with SharpCap being unable to load the code needed to talk to two brands of camera (SVBony and Imaging Source/Celestron). It would be very helpful if you could check the C:\Windows\System32 folder on your machine and see if the following DLL files are present in that folder or not:

* MSCVP140.DLL
* ucrtbase.dll
* mscoree.dll
* VCOMP140.DLL
* Setupapi.dll

You may have some but not all of those files - I have so far assumed that all of them are *always* present on Windows installs, but maybe I am wrong and need to install some of them with SharpCap.

thanks,

Robin

[AngusMcDuff]

Robin

Thank you very much for solving my problem. There were actually three versions in the registry. I have attached a screen print. There is now only 9.1.4.0 and my equipments is operating perfectly.

My System32 directory contains none of the files you listed. I am using
Windows 11 Pro
Version 24H2
OS Build 26100.2605

Thanks again.

Rich

[admin]

Hi Rich,

glad to hear that fixed it - this sort of thing can sometimes happen when you uninstall a version and the uninstall routine doesn't clean up properly, particularly if you go back to an older version after uninstalling.

If you experience problems in other programs that are 32 bit rather than 64 bit, you may also need to do the same for the 32-bit registration for the iOptron driver. You'll find that at the following registry key

Code: Select all

HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{C13F2FED-7D46-479C-ADB1-A199E40F787C}\InprocServer32

cheers,

Robin

[AngusMcDuff]

Robin

Thank you.

Rich Novak