I’m a new user of SGPro. Trying to figure out how to get a response from SGP itself.
My problem is that while SGP works fine on my Win 10 computer, I cannot connect cameras on my licensed SGP on a new Win 11 BeeLink mini computer. My AP mount and RoboFocus connect jus fine on the Win 11 mini. But my QSI 683 wsg-8 and StarlightXpress 674 will not connect.
Clicking on Settings for the cameras generates this error: “RPC server is unavailable (Exception from HRESULT 0X800706BA.)”
What does his error code signify?
I understand RPC refers to Remote Procedure Call. I have reviewed the Windows 11 service.msc file list according to online instructions and have confirmed that (1) RPC in Windows is running; (2) RPC Endpoint Mapper is running and set on auto; (3) DCOM Server Process Launcher is running and set on auto.
I have also updated Win 11.
I suspect the problem is not with SGP but with the computer, as the QSI camera did – to my surprise – connect once a few days ago, but not since then.
I would be glad to provide a link via Dropbox to a log file, but Dropbox requires me to insert an email address for a receipient. But I haven’t seen such an address on the SGP Forum.
Errors like this can present themselves as for many reasons unfortunately. Here’s some reasons why and some things to check:
Drivers. In addition to installing the camera drivers, you’ll also need to make sure that you are selecting the matching driver in SGPro. This is especially true with QSI as those cameras we not always ASCOM compliant and still have their own “native” option in the camera selector. If you are using legacy QSI drivers (unlikely unless you saved them), you’ll select QSI CCD Camera from the camera dropdown. If you are using the more modern ASCOM driver’s you’ll want to select the QSI option that is NOT that (I forget the exact text used for QSI ASCOM).
Bitness. Make sure that all of your “bitness” selections align. First start with the OS itself. It is almost certainly a 64-bit OS, but 32-bit variants of Windows 11 do exist. Select as follows:
If OS is 32-bit, stop reading and install 32-bit SGPRO; use ALL 32-bit drivers
If OS is 64-bit, you may select either 64 or 32
If ANY of your equipment drivers are offered in ONLY 32-bit stop reading and install 32-bit SGPRO; use ALL 32-bit drivers
If ALL of your drivers are offered in 64-bit stop reading and install 64-bit SGPRO; use ALL 64-bit drivers
COM Failure. The architecture ASCOM uses to communicate with drivers is Windows COM. In order to communicate through COM, the driver’s MUST register themselves as Windows COM devices and they do this during install. In case there was an error during install, fully uninstall the drivers, use ASCOM profile explorer to ensure they are gone and then re-install.