Jump to content
You are not logged in. Please click here to Sign In ×
Forum update!

SDCO error Stylus Database

---

By [To...] ,
in General

 Share

Recommended Posts

---

[To...]

Posted
Posted
I installed 2022 on my DuraMax but wasn't connected to machine. I'm getting a connection error whenever I try to connect. I re-created the DuraMax machine tab and still get the same error. I create a new tab with a different name and it connects ok. There seems to be something holding onto the old DuraMax config.

I un-installed Calypso and re-installed it with the same results.

Below is log file:
---------------------------------------------------------------------------------------
November 4, 2022 at 3:46:54 PM Error code: 0
Cannot open database "sdotcodata_DuraMax" requested by the login. The login failed.
Login failed for user 'IMT_OCS_ADMIN'. at Zeiss.IMT.MUMCPP.SDO.TCOSystem.CheckVersion(Int32[] versionNo)
at Zeiss.IMT.MUMCPP.SDO.TCOSystem.CheckVersion(String versionNo)
at Zeiss.IMT.MUMCPP.SDO.Update.CheckFirstUse()
at Zeiss.IMT.MUMCPP.SDO.Update..ctor(TCOSystem instance)
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)

DuraMax Connect Issue 1.JPG

Link to comment
Share on other sites
---

[Th...]

Posted
Posted
If your setup isn't too complex, consider backing up the Calypso configs and etc, uninstalling and completely removing the folder from public docs, then reinstalling and creating the machine tab. In my experience, it's easier to just nuke a software installation and start over than try to figure out what's broken.
Link to comment
Share on other sites
---

[Wo...]

Posted
Posted
Do you loose anything important by nuking the machine and starting from scratch? Aside from stylus systems. Like config files made during Zeiss calibration or anything like that.
All my plans and results are kept on the server so not worried about that either.
I always back up public zeiss folder, upgrade to newer version and if anything screws up jus overwrite it from backup.
Link to comment
Share on other sites
---

[To...]

Posted
  • Author
Posted

Please sign in to view this quote.

Thank you Nicolas. I was able to do some of the things on this document but not all. Maybe because this is for a 2014 installation of SQL Server, things might be different with 2017 versions.
Link to comment
Share on other sites
---

[Br...]

Posted
Posted
When you uninstalled Calypso did you uninstall all of the Microsoft SQL instances too?

Another shot in the dark is checking that Microsoft Edge is updated. I ran into this once installing a later version of Calypso (can't remember which) and the SQL Server installation portion got jammed up. After reading up on the error logs and Googling it turned out that some security setting Windows 10 gets updated with Edge and SQL needed it too.
Link to comment
Share on other sites
---

[La...]

Posted
Posted
If it's not too much work (not sure how many stylus systems you have, or preferences saved, etc etc) I would just go into the C:\Users\Public\Documents\Zeiss\CALYPSO 7.4 folder and change the config folder to config_old

When Calypso launches it will ask you to sign the EULA again, but it will give you the ability to go in and create a brand new machine tab.

I usually will name the machine tab something different, to try and avoid any "hanging up" of old naming conventions. So I'd name it Duramax11072022 or something. Not sure if this is necessary but I am generally a worst-case-scenario thinker so I try to foresee anything that could go wrong.

Hopefully this works for you
Link to comment
Share on other sites
---

[To...]

Posted
  • Author
Posted
UPDATE - CRISIS SOLVED

In 20 words or less, the Zeiss Tech ended up uninstalling and re-installing SQL Server 2017. I watched him do it and there was quite a lot involved so I wouldn't be able to detail everything he did.
Link to comment
Share on other sites
---

[No...]

Posted
Posted

Please sign in to view this quote.

Yes, now I know the admin ID of the probe database and am just a password away from manipulating it, har har 🤬
Oh, did I just write this? Darn, I shouldn't type while thinking 🫣

Well, the useful info is that Calypso can't log into the db 🤠 Possible reasons are numerous. SQL Server seems to put system exclusive permissions on a db file while accessing it and sometimes "forgets" to restore the previous state. This must have been a constant problem for Zeiss in the past and affected the Calypso backup function, which is probably why they changed the way data is exported in a recent release. But this only happens on the file system level and shouldn't affect login permissions. But who knows.
Link to comment
Share on other sites
  • 1 year later...
---

[Ri...]

Posted
Posted

Please sign in to view this quote.

That's what Zeiss needs!
Seriously, an SDCO uninstall package.
The SDCO for v2024 failed terribly, crashing Calypso to the floor. I am now trying to rid my system of any version of SDCO in hope I can install it clean.
I am afraid I'm at the point of "Control Alt SledgeHammer". 😱

Anyone know how to remove SDCO for a clean install?
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...