Lost system settings

[[Ro...]]

Yep. Turned on the CMM this morning and the system settings have changed. Wrong units, temp, decimal places, etc. Also, the recent files list is gone except for 1 program, which wasn't even the last one opened.

There have been no Windows updates.

Nothing like having to &^%$ around resetting everything because Collapso decided to break itself. 😡

[[Ow...]]

Make sure it didn't log into a different user other than master, there's always another tab by default. Had that happen on a Duramax a while back when they turned it on. The system never used that tab before (only master) and didn't require a password at start-up.
It never made sense because the person that turned it on wouldn't even know how to change it.

That said, hopefully you have everything backed up because I have seen them lose everything before.

[[Ro...]]

Please sign in to view this quote.

Oh yeah. That's a given for this software. 🤣

[[Ro...]]

Now I have no machine connection and am dead in the water. I did nothing to make this happen. This software is just garbage, apparently. Breaks all on it's own. What a fucking joke...

[[Je...]]

Hello Robert,

We received your call to the Help Desk Hotline and have assigned one of our AEs that specializes in IT related issues. As a rule, when we see issues relating to access of stylus databases or CMM connection issues, it is almost 100% related to a recent change in IT configuration. Typically this is caused by an anti-virus program or firewall setting that is preventing read/write/admin acess to critical files.

Our AE will be in contact with you shortly and assist you in getting your CMM back up and measuring parts as soon as possible.

[[Ro...]]

Hi Jeff,
Someone just called me and solved the problem. I appreciate you guys getting back to me so quickly today. 🙂

For anybody else that gets this error, it's because the SQL Server stopped running. You can go to Services, and look to see that the SQL Server (SDCO) is running and starts automatically.

[[Ro...]]

This is an ongoing problem. The SQL Server (SDCO) refuses to start if the computer is restarted. It's set to Automatic for Startup Type. This never happened before. I suspect it has something to do with Windows updating.

What say you, Zeiss? What's the fix for this? ❓

[[Ke...]]

Please sign in to view this quote.

Curious... did Windows update automatically, due to being hooke up to the internet, or due to an update being pushed by IT (if it is networked)?

[[Ro...]]

Hi Keith,
IT does all the updating. I don't know for a fact that it's an update issue but seeing as Calypso has been working fine since we went to 2021 over a year ago, I don't know what else it could be. I have to manually start the service each time the PC reboots. No bueno. 🙁

[[Je...]]

Robert,

All indications point to a localized IT issue with permissions or user login. Please convene with your company IT tech to confirm that they have not changed an IT settings that affects administrative rights in their relation to SQL access and system resource use. The fact that this occurs each time you reboot would indicate that it is user login rights issue.

If you need a list of services that must be accessible under administrative privileges, I can provide that.

[[Ro...]]

Thanks, Jeff. That makes sense. I'll look into it. I appreciate the response. 🙂

[[Ke...]]

Please sign in to view this quote.

I would like to have that list on hand, as we consider networking our lab equipment.
If it is something that we move forward with, I want the process to be as smooth as possible.

[[Je...]]

Robert Davis;

Your IT should look into the path below at the very minimum. They have likely changed some permissions for your user in relation to SQL access and start.

Administrative Tools > Services > SQL Server(MSSQLSERVER or the name of your instances) > Right Click > Properties > Move to Log On > Set the Log On option using a Local System Account

Link from the Portal Knowledge Base
https://portal.zeiss.com/knowledge-base ... &id=514540
This is for US customers only at this time as we pilot a new Knowledge Base system. I apologize to our International customers that may not be able to access this link.

From the page;
CALYPSO Settings for I.T. to White List

This document will cover the important files, folders, and ports and IT person may want to white list. File locations refer to Calypso 6.8 install. Adapt "6.8" to whichever version you are installing if > "5.6"

Network Card Setting:

TCP/IPv4:

192.4.1.55

Subnet mask:

255.255.255.0 – this will auto-populate after setting the IP Address.

Ports to white list:

czcol1 8881/tcp

czcol2 8882/tcp

czcol3 8883/tcp

czcol4 8884/tcp

ZVICONTROL 8888/tcp

AATServer 8890/tcp

nonCZcontrol 8891/tcp

acis 9953/tcp

qfm 9997/tcp

weprom 9998/tcp

DMECONTROL 1294/tcp

CTConnect 49431/tcp

LKControl 1400/tcp

Applications to white list (*.exe):

(Within "C:\Program Files (x86)\Zeiss\CALYPSO 6.8\bin\")

vwnt.exe

scalypso.exe

MyView.exe

acis29.exe

acis2*.exe

acis3*.exe

qdasconv.exe

QDASConverter.exe

CMM.exe

RunReport.exe

czviewer.exe

CALYPSOMonitor.exe

(Within "C:\Program Files (x86)\Zeiss\ZLAU\Client\")

ZLAU.exe

Folders to white list application files (*.exe):

C:\Program Files (x86)\Zeiss\CALYPSO 6.8\bin\

C:\Program Files (x86)\Zeiss\CALYPSO 6.8\bin\NZDI\

Calypso also relies on accessing a Microsoft SQL Server Express instance. The most recent versions use SQL Server 2014 and the ZEISS interface to it is SDCOScripts.



Files and Folders to back up:

C:\Users\Public\Documents\Zeiss\CALYPSO (There could be a version associated to it, such as 6.8)

Back up the entire directory, but the most important directories are:

…\config

…\protocol

…\workarea

…\data

If there is a need to restore Calypso after installing, those folders are going to save the most time and effort.

Expert Tip:

Restart the PC before making the back up. Occasionally the SQL Server is still communicating and having a fresh restart without opening any applications allows for a clean copy. (Windows 10 gives a sharing violation of two files when the copy fails: sdodata2.mdf and sdodata2_log.ldf)