Error when opening Calypso software

[[Ja...]]

This is the first time I have seen this issue.  Normally, over the weekends, I power down the PC and the CMM, and on Mondays, power everythign up, no issues.

Today however I got this error message

Here is the text from the SDCOconnect.log:

June 22, 2026 at 7:24:53 AM Error code: 0
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The remote computer refused the network connection.)   at Zeiss.IMT.MUMCPP.SDO.TCOSystem..ctor(String ConfName, String Datapath, String EnvironmentName, Boolean mainInstance, Boolean updateDb)

   at Zeiss.IMT.MUMCPP.SDO.MSensorSystem..ctor(String groupname, String pathname, Boolean list)

   at Heeg.SdoProxy.Zeiss_IMT_MUMCPP_SDO_MSensorSystem_New02(SdoProxy* , return_type* vwReturnValue, Char* groupname, Char* pathname, Boolean list)
 

 

When I hit OK, I get this error:

then:

then:

 

Any suiggestions?

[[Ma...]]

I saw this whenever i was starting Calypso as soon as i could.

But in services there is no running MSSQL SDCO.

To check this go to services, find SQL Server (SDCO) and look if there is an "Automatic" start - if there is an "Delayed" change it to Automatic.
Delayed will start that service about 1 minute after start, so you are faster with starting Calypso than is service running.

Edited 3 hours ago

[[Ma...]]

Please sign in to view this username.

 is correct about the first Error Message, which could also lead to the second Error Message.

 

The last 2 could be caused by a corrupted config or in the worst case, by an actual broken sensor. 

[[Ja...]]

I dont see either one running under services, but when I go tot eh SQL Server Configuration Manager, it shows it running as Automatic(Delayed) but I cannot change it.

[[Ma...]]

It should be running - if not then run it.

I think you would need to have an admin rights to change these settings.

[[DW...]]

Please sign in to view this quote.

Please sign in to view this username.

 Zeiss (to my current knowledge) does a not so great job at letting the user know what processes MUST be running for the software to function correctly. This is for Calypso, and Zeiss Inspect (specifically X-Ray Pro in my case). 

If there is a Windows Update, or maybe a configuration change completely unrelated to the inspection software that disrupts the processes needed to run/communicate, please let us know what those processes are so we can re-fire them. The X-ray Pro software for CT acquisition requires very specific processes to run or be written correctly to the registry. If they are interrupted or broken, you have to go into the file folders and manually start the associated .EXE files, except even the escalated help at Zeiss didn't know about these files and how it all worked together. I just poked around in every single folder for a few days until I was able to execute all the needed files for communication again.

If this information is available from Zeiss, please let me know and I will amend my sentiments.