How to fix missing languages on Full text indexes

Question

How to fix missing languages on Full text indexes

Wade Buckthorp 0

Our SQL Server went down after a failed patch `and locked the server instance in ChangePending state, we rolled back the VM and got the DB back to being operational with the exception of the full text indexes... I have run the repair tool checked to see if the languages can be queried restarted the server and still no dice on the full text indexes working. What other options do I have aside from a fresh install of the SQL server

Wade Buckthorp 0 Reputation points

2026-02-06T12:04:32.0066667+00:00

That has all already been done I can't set the language cause there are not any languages recognised as the meta data is corrupt
Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-06T21:19:23.31+00:00

If you rolled back the VM, one likes to think that the state would be like before the patch failure. So if something is corrupt now, and it wasn't corrupt before the, that induces some lack of faith in the rollback feature of the VM software.

Anyway, one idea is that since fulltext is an optional feature, you could try uninstalling fulltext and re-install it. But by all means, clone the VM and test this first. Just because something can be uninstalled in theory, does not mean that it works in practice. I have an SQL 2019 instance on my home machine from which I once tried to uninstall Polybase, and that crashed badly.

Since you apparently have fulltext databases on your instance, you may have to drop/detach these databases first and then restore from backup.
Wade Buckthorp 0 Reputation points

2026-02-09T14:01:09.9133333+00:00

HI @Erland Sommarskog that is correct I rolled the vm back to the last stable version of the VM that we had where there were no issues on it... With regards to uninstalling and reinstalling the Full text feature it doesn't allow me to even select it anymore the component is disabled and cannot select or unselect the feature
Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-09T22:07:56.4966667+00:00

That sounds as if it thinks that full-text is not installed at all. Maybe you should try adding the feature?

As you may understand, I'm clutching at straws here. It may be that there is no better way out than to open a support case. Or bite the bullet and take a back up of all databases, including the system databases and re-install SQL Server including CUs.
Wade Buckthorp 0 Reputation points

2026-02-10T06:05:57.54+00:00

Hi erland yea I know what you mean grasping at straws here. the full text index feature is installed, I can create full text indexes but cannot add columns as it can't decide what the default language it should use to for the word breakers

I have read a few resources that say that upgrading the SQL Server instance can also fix it as it will reinstall the full text feature, but thought I would bring the issue here and see if there was anything else I may have missed before going in that direction
Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-10T21:33:03.1466667+00:00

The upgrade path is something I would try, if I was planning to upgrade anyway. It might work, but if the full-text installation is an unknown state, the entire upgrade may fail and leave you in an even bigger mess. The best protection against that is restore a backup/snapshot of the VM, but you've been through that already.

If you try the upgrade path, absolutely take backups of all databases and make sure they are stored outside the VM, in case you need to nuke the VM entirely.
Akhil Gajavelly 1,570 Reputation points Microsoft External Staff Moderator

2026-02-12T11:13:49.6966667+00:00

Hi @Wade Buckthorp ,

Thanks @Erland Sommarskog for your continued guidance and detailed explanations throughout the thread much appreciated.

Glad to hear the regular backups and snapshots are already in place. That’s definitely the right approach before performing an upgrade.

Since your question has been addressed and the solution worked for you, I would recommend marking Erland’s reply as the accepted answer so it can help others facing a similar situation.

Thanks again to everyone who contributed.

Thanks,
Akhil.
Wade Buckthorp 0 Reputation points

2026-02-12T11:24:40.15+00:00

Hi Akhil,

I will mark it as the accepted answer once we have gone through the upgrade process and if it works... We have the downtime scheduled just need to get final approvals before we can do anything and has to be done during non peak hours for us.

Answer recommended by moderator

2 additional answers

Your answer

Wade Buckthorp 0 Reputation points

2026-02-06T12:04:32.0066667+00:00

That has all already been done I can't set the language cause there are not any languages recognised as the meta data is corrupt
Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-06T21:19:23.31+00:00

If you rolled back the VM, one likes to think that the state would be like before the patch failure. So if something is corrupt now, and it wasn't corrupt before the, that induces some lack of faith in the rollback feature of the VM software.

Anyway, one idea is that since fulltext is an optional feature, you could try uninstalling fulltext and re-install it. But by all means, clone the VM and test this first. Just because something can be uninstalled in theory, does not mean that it works in practice. I have an SQL 2019 instance on my home machine from which I once tried to uninstall Polybase, and that crashed badly.

Since you apparently have fulltext databases on your instance, you may have to drop/detach these databases first and then restore from backup.
Wade Buckthorp 0 Reputation points

2026-02-09T14:01:09.9133333+00:00

HI @Erland Sommarskog that is correct I rolled the vm back to the last stable version of the VM that we had where there were no issues on it... With regards to uninstalling and reinstalling the Full text feature it doesn't allow me to even select it anymore the component is disabled and cannot select or unselect the feature
Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-09T22:07:56.4966667+00:00

That sounds as if it thinks that full-text is not installed at all. Maybe you should try adding the feature?

As you may understand, I'm clutching at straws here. It may be that there is no better way out than to open a support case. Or bite the bullet and take a back up of all databases, including the system databases and re-install SQL Server including CUs.
Wade Buckthorp 0 Reputation points

2026-02-10T06:05:57.54+00:00

Hi erland yea I know what you mean grasping at straws here. the full text index feature is installed, I can create full text indexes but cannot add columns as it can't decide what the default language it should use to for the word breakers

I have read a few resources that say that upgrading the SQL Server instance can also fix it as it will reinstall the full text feature, but thought I would bring the issue here and see if there was anything else I may have missed before going in that direction
Erland Sommarskog 133.2K Reputation points MVP Volunteer Moderator

2026-02-10T21:33:03.1466667+00:00

The upgrade path is something I would try, if I was planning to upgrade anyway. It might work, but if the full-text installation is an unknown state, the entire upgrade may fail and leave you in an even bigger mess. The best protection against that is restore a backup/snapshot of the VM, but you've been through that already.

If you try the upgrade path, absolutely take backups of all databases and make sure they are stored outside the VM, in case you need to nuke the VM entirely.
Akhil Gajavelly 1,570 Reputation points Microsoft External Staff Moderator

2026-02-12T11:13:49.6966667+00:00

Hi @Wade Buckthorp ,

Thanks @Erland Sommarskog for your continued guidance and detailed explanations throughout the thread much appreciated.

Glad to hear the regular backups and snapshots are already in place. That’s definitely the right approach before performing an upgrade.

Since your question has been addressed and the solution worked for you, I would recommend marking Erland’s reply as the accepted answer so it can help others facing a similar situation.

Thanks again to everyone who contributed.

Thanks,
Akhil.
Wade Buckthorp 0 Reputation points

2026-02-12T11:24:40.15+00:00

Hi Akhil,

I will mark it as the accepted answer once we have gone through the upgrade process and if it works... We have the downtime scheduled just need to get final approvals before we can do anything and has to be done during non peak hours for us.

Answer 1

Wade Buckthorp 0

Ok perfect thanks Erland, We do take regular backups and they are stored on a separate disk and also have snapshots in place to rollback to if the db does end up in a bigger mess due to the upgrade failing

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

To address the issue of missing languages on full-text indexes in SQL Server after a rollback, you can try the following steps:

Check Full-Text Language Configuration: Ensure that the default full-text language is set correctly. You can do this using SQL Server Management Studio (SSMS) or Transact-SQL. In SSMS, right-click the server in Object Explorer, select Properties, then go to the Advanced page to check the Default Full-Text Language.
Rebuild Full-Text Indexes: If the full-text indexes are still not functioning, you may need to rebuild them. This can be done using the following SQL command:
```
   ALTER FULLTEXT INDEX ON [YourTableName] REBUILD;
```
Replace [YourTableName] with the actual name of your table.
Verify Language Support: Make sure that the languages you are trying to use are supported and properly installed. You can check the supported languages using the sys.fulltext_languages view.
Repair Full-Text Catalogs: If the indexes are still not working, consider repairing the full-text catalogs. You can use the following command:
```
   ALTER FULLTEXT CATALOG [YourCatalogName] REBUILD;
```
Replace [YourCatalogName] with the name of your full-text catalog.
Check for Errors: Review the SQL Server error logs for any messages related to full-text search that might provide additional insights into the problem.
Consider SQL Server Repair: If none of the above solutions work, you might consider running a repair on the SQL Server installation. This can be done through the SQL Server installation media by selecting the repair option.
Fresh Install as Last Resort: If all else fails and the full-text indexes are still not operational, a fresh install of SQL Server may be necessary, but this should be the last resort after exhausting other options.

These steps should help you troubleshoot and potentially resolve the issue with missing languages on your full-text indexes.

Share via

How to fix missing languages on Full text indexes

2 additional answers

Your answer