Jump to content
Private Messaging is activated - check "How to" on how to disable it ×

error message


---
 Share

Recommended Posts

I would start by trying to restart the SQL Server and the easiest way to do this is by rebooting the PC. You can see that it is running after restart under Services > SQL Server (SDCO) located at C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools. 822_7ce2dfb9a006442e633b5ca7f52f99ed.jpg
Does this happen when starting CALYPSO or when running one program or multiple programs?
Link to comment
Share on other sites

thank you Charles

it happened every week after computer updated to Windows 10 system. most of them occurred on Thursday or Friday. SQL server was running when error popped up. I am doubting if C-98 controller 16Bit board has issue with Windows 10 system? IT department told me there is no APP updates on specific weekday.
Link to comment
Share on other sites

Hello Xinhu,

You said this was a C98 controller? What version of Calypso are you running? Depending on the version, it might be running something that isn't supported on Windows 10.
Link to comment
Share on other sites

Hi Xinhu,

Try the settings of the UTF-8 decoding. I remember that we got the same error 0x200 while the SDCO try to connect to the SQL service.
It´s fast and simple to try 🙂

Have a nice weekend
Karsten
Link to comment
Share on other sites

Please sign in to view this quote.

I'm may be wrong, but this doesn't look like the SDCOError.log I was talking about, but more like a general SQL Server log.
I was talking about the file specified in the Warning window in your first post:

C:\Users\Public\Documents\Zeiss\CALYPSO\config\equip\Prismo_C98\SDCOError.log

This file usually contains only the last error encountered.
Link to comment
Share on other sites

hi Norbert
there is no error message in: C:\Users\Public\Documents\Zeiss\CALYPSO\config\equip\Prismo_C98\SDCOError.log

thank you
Link to comment
Share on other sites

Hello Xinhu,

I'll be honest, I don't know what version of SQL server was in Calypso 5.6, it was a bit before my time, but I would not be surprised if was not supported on Windows 10. This could be just be an issue with compatibility with the operating system.

I can't promise that this will work, but what you can try to do is download CALYPSO 2016 (version 6.2 full version), uninstall SQL from that computer, and then install the SQL file in the 2016 installation files. That should at least get SQL to a version that should work on Windows 10. CALYPSO might not like it though, so be aware of the risk.
Link to comment
Share on other sites

 Share

×
×
  • Create New...