Jump to content

2018 Calypso 6.6 install on new Win 11 machine


---
 Share

Recommended Posts

Hi,

Has anyone had SQL error when loading an older Calypso version, 6.6 in my case, on a new Windows 11 machine. I've looked the log file and it's a little conflicting for what it's telling me and what the error code says when i look it up. Calypso 2018 download from Zeiss site. No SMA. Company purchased new PC's with Win 11.

Logfile says:

"The specified sa password does not meet strong password requirements. For more information about strong password requirements, see "Database Engine Configuration - Account Provisioning" in Setup Help or in %SQL_PRODUCT_SHORT_NAME% Books Online."
    HResult : 0x851a0013

 

0x851a0013 error code look up says:

"On systems running Windows 11, some new storage devices and device drivers will expose a disk sector size greater than the supported 4 KB sector size.

When this occurs, SQL Server will be unable to start due to the unsupported file system as SQL Server currently supports sector storage sizes of 512 bytes and 4 KB."

 

Thanks!!

SQL error.jpg

  • Like! 1
Link to comment
Share on other sites

Please sign in to view this quote.

Thanks. I figured it was something like that. The setup.exe file for 2018 Calypso automatically wants to install that 2014 version

  • Like! 1
Link to comment
Share on other sites

New computers, or rather hard drives, have larger sector sizes available for services. However, SQL can only handle a maximum of 4KB. It can't handle more than that. There's a trick to see the sector sizes and limit them. Then it works. At least I had the problem. The link is in German.

 

Fehlerbehebung bei einer Betriebssystem-Laufwerk-Sektorgröße über 4 KB - SQL Server | Microsoft Learn

  • Like! 1
  • Thank you! 1
Link to comment
Share on other sites

  • 1 year later...

I had a similar issue when re-installing Calypso 2018 on my laptop that was recently re-staged. SQL Server 2014 was faulting out with a Powershell 2.0 not installed. Turns out this version of Powershell is deemed a security risk and was removed from the Windows 11 entirely.  Regardless, I used the 2017 SQL server express  from the 2020 Calypso installation folder and as Lucas said above, a skipped over this and cleanly installed 2018. Props to Lucas!

Link to comment
Share on other sites

How to fix SQL after a failed install.

Ive had to fix SQL too many times after a failed Calypso install, so I wrote down what steps I took to fix it.

The zip file contains docx and reg files. The reg file fixes some entries that get corrupted.

As always BACK UP YOUR REGISTRY PRIOR TO USING.

After re-installing SQL 2014, you should now be able to cleanly install SQL 2022.

 

SQL SDCO Registry repair after a failed installation of a newer version of SQL SDCO.zip

Edited
Link to comment
Share on other sites

 Share

×
×
  • Create New...