[Pa...] Posted Wednesday at 07:11 AM Share Posted Wednesday at 07:11 AM (edited) Hello Everyone, I am at a customer trying to install last version of Calypso 2025 SP 8.0.08.The customer have their own operating system Win 11 LTSC.The station is added in their network.During Calypso installation the MySQL server 2022 does not want to finish installation.Checked the logs and it is says something about firewall.I got in touch with their IT department they are still investigating but no luck until now.Also tried with a local user with lan cable disconnected but because of internal GPO same issue.Has anyone encountered this issue.How did you solve it? Thank you! Edited Wednesday at 07:14 AM Link to comment Share on other sites More sharing options...
[Sv...] Posted Wednesday at 07:40 AM Share Posted Wednesday at 07:40 AM Check the sector size of your hard drive. If even one sector is larger than 4096 bytes, SQL Server will not work because it cannot process larger sectors. Microsoft provides instructions at the following link: SQL Server 2022: Hardware- und Softwareanforderungen - SQL Server | Microsoft Learn Link to comment Share on other sites More sharing options...
[Jo...] Posted Thursday at 07:19 PM Share Posted Thursday at 07:19 PM I'm running into the same issue. I checked the sector size and I'm at 512 bytes, so that's not my issue. I have also tried installing different versions of Calypso to see if the Calypso version is the problem of is this just a Win 11 thing. Does anyone have any insights on how to rectify this? Link to comment Share on other sites More sharing options...
[DW...] Posted Friday at 05:39 PM Share Posted Friday at 05:39 PM Please sign in to view this username. Please sign in to view this username. It's been a long time since I encountered this, but I believe the fix was to uninstall (from add/remove programs) any and all versions of Microsoft SQL server on the machine, and then let Calypso try to install SQL via the installer. Link to comment Share on other sites More sharing options...
[Je...] Posted Friday at 11:59 PM Share Posted Friday at 11:59 PM I advise you contact your local SW support team. SQL installations/run time issues are very difficult to diagnose (there are around 10-11 common IT related settings that can cause problems - many more uncommon ones). I will re-iterate, again, that this is why SW Support recommends ZEISS sourced workstations. The hardware and OS image they are provided with is significantly more reliable related to installation and run-time problems alone. In the US, more than 92% of the installation and run-time problems reported are on non-ZEISS sourced PCs (knowing this, it seems silly to save $300 by having your IT guy source one elsewhere). Save yourself the preventable down-time. It is expensive. For those using their own sourced workstations/PCs, here are the Windows related problems you may experience with installing CALYPSO. I'll try to point out some places to start (the ZEISS Portal Knowledge Base will help with all of these too) The big ones: Install: Inadequate installation privileges - when you install, right-click on setup file and run as administrator. This helps in some situations, otherwise, get with IT. Legacy registry values that require being removed. Error logs will point to this. Invalid sector sizes on SSDs (Windows will lie to you if you dont have admin credentials when you check, it emulates 512kb sector) Pending Reboot required (this is the MOST common by far) - any changes to SQL requires a reboot to implement. Always reboot before and after install. OLE drivers remaining from previous installs Run-time: SQL EXPRESS 2022 set to "Delayed Start" is default - resolvable if needed but just wait 2-3 minutes after reboot and this goes away PC name greater than 15 characters (prevents MSMQ services from starting > prevents SQL services from starting) SQL/SDCO Services not started - Condition of the two above or various other problems Ports 1433 or 1434 blocked Improper migration of 'config' directory from a PC/machine tab move. SQL MUST BE OFF to migrate a config. If you see a "2 files were not copied" message, that config is going to fail 100% of the time. Install - unrelated to SQL but with CALYPSO itself and important: Due to 256 character limit on Windows files, Put the install media at root level directory (C:\temp\) or similar. There are very long file paths, specifically Linescan driver files for instance, that will fail install if you put the install media in longer folder paths like C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\inspections\ZEISS CALYPSO 2025 full version incl sp (8.0.08)\ - (just as an example) INSTALL THE "FULL VERSION W SERVICE PACK"! The Service Packs are complete installs. No need to install the "base version" any longer if a Service Pack has been released. If you are experiencing errors or problems you believe are not as-designed performance, make sure you are on the most current Service Pack for that version of CALYPSO before reporting to support. (I promise, this will be the first thing they ask you. Next will be if you've rebooted). 1 Link to comment Share on other sites More sharing options...
[Pa...] Posted 2 hours ago Author Share Posted 2 hours ago What customer's question:Is it possible to migrate the Calypso DB to an SQL server that is already created into their network?Can Calypso work like that or it needs local DB? Link to comment Share on other sites More sharing options...
[Ma...] Posted 1 hour ago Share Posted 1 hour ago As far as i know Calypso is using MSSQL and it's running local file. Similar thing is PiWeb. So i don't think there will be a file/settings defining connection, to be editable. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in