Issues Installing Full-Test for my SQL Server 2016 - error code 1624

Question

Hello everyone,

I'm struggling with setting up full-text in my testing SQL server 2016. I am attempting to install it as the admin of my domain. I only just installed the server on a clean Windows Server 2016 VM. I don't have much of any experience installing SQL, so I could easily have missed something.

I keep seeing this error:

The link attached to the error leads to a page that doesn't exist anymore. The associated logs say:

=== Verbose logging started: 3/1/2023  10:59:41  Build type: SHIP UNICODE 5.00.10011.00  Calling process: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\SQLServer2016\x64\ScenarioEngine.exe ===
MSI (c) (78:B8) [10:59:41:425]: Resetting cached policy values
MSI (c) (78:B8) [10:59:41:425]: Machine policy value 'Debug' is 0
MSI (c) (78:B8) [10:59:41:425]: ******* RunEngine:
           ******* Product: E:\MS SQL Server 2016 SE\new installer\x64\setup\sql_fulltext.msi
           ******* Action: 
           ******* CommandLine: **********
MSI (c) (78:B8) [10:59:41:425]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (78:B8) [10:59:41:425]: Grabbed execution mutex.
MSI (c) (78:B8) [10:59:41:456]: Cloaking enabled.
MSI (c) (78:B8) [10:59:41:456]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (78:B8) [10:59:41:472]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (DC:EC) [10:59:41:472]: Running installation inside multi-package transaction E:\MS SQL Server 2016 SE\new installer\x64\setup\sql_fulltext.msi
MSI (s) (DC:EC) [10:59:41:472]: Grabbed execution mutex.
MSI (s) (DC:24) [10:59:41:487]: Resetting cached policy values
MSI (s) (DC:24) [10:59:41:487]: Machine policy value 'Debug' is 0
MSI (s) (DC:24) [10:59:41:487]: ******* RunEngine:
           ******* Product: E:\MS SQL Server 2016 SE\new installer\x64\setup\sql_fulltext.msi
           ******* Action: 
           ******* CommandLine: **********
MSI (s) (DC:24) [10:59:41:487]: Machine policy value 'TransformsSecure' is 1
MSI (s) (DC:24) [10:59:41:487]: Note: 1: 2203 2: SqlRun01.mst 3: -2147286775 
MSI (s) (DC:24) [10:59:41:487]: MainEngineThread is returning 1624
MSI (s) (DC:EC) [10:59:41:487]: User policy value 'DisableRollback' is 0
MSI (s) (DC:EC) [10:59:41:487]: Machine policy value 'DisableRollback' is 0
MSI (s) (DC:EC) [10:59:41:487]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (DC:EC) [10:59:41:487]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (DC:EC) [10:59:41:487]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (DC:EC) [10:59:41:487]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (78:B8) [10:59:41:487]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (78:B8) [10:59:41:487]: MainEngineThread is returning 1624
=== Verbose logging stopped: 3/1/2023  10:59:41 ===

I double checked my TEMP folders and they both have system read / write permissions. I ensured I do in fact have the Full-Text MSI, and I do under x64>Setup:

Thank you for your time.

Answer 1

Yes, so I did try to install it as I installed the SQL server but it failed in the same way. So, I tried it again after rebooting the machine and adding it as a feature but it still didn't work.

Hm, it seems that your machine is messed up in some way. It could be that your IT folks have installed something that gets in the way. Or it is just an accident that happened to your machine.

Possibly, you could talk to your IT people and ask them to open a support case. But it may be easier to create a virtual machine and install SQL Server with full-text on that machine.

Answer 2

Not a very helpful error message. Eror 1624, "Error applying transforms. Verify that the specified transform paths are valid." apparently comes from the MSI installer, and it is a generic message that tells us that something is broken.

What, I have no idea.

What does "SELECT @@version" report?

Possibly, you could consider opening a support case, but with SQL 2016 being out of mainstream support your chances may not be that good.

Answer 3

Hi @Karina,

Do you have a particular reason why you need to use SQL Server 2016? If not, it is recommended that you install SQL Server 2019 or 2022. Windows Server 2016 is supported for both versions. For other prerequisites, you can check this document. The navigation bar on the left side allows you to quickly view the prerequisites for other versions.

https://learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2022?view=sql-server-ver16

Error code 1624 usually indicates that there is a problem with the installation package for SQL Server 2016.

You can follow the steps below to uninstall it and reinstall a new SQL Server.

What is more, you can disable antivirus software. Sometimes, antivirus software can interfere with the installation process.

Please follow the below steps to remove all components of previous installed SQL Server completely:

1. Remove all SQL Server components from 'Programs and Features'
2. Backup the registry
3. Delete the following keys in regedit:

--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer

4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server
5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server
6. Reboot the machine

In addition, please use an administrator account to reinstall SQL Server on your computer(Right click->run as administrator).

Best regards,

Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".