@davecrewe17 Have you restarted the environment after doing rebuild?

Did you enabled the feature?

Hi Manikanta,

I did not restart, I didn’t think a restart was necessary. However I have just restarted and rebuilt, and the warning is still there. 

With regard to enabling the feature, my understanding was that ‘Process All’ on the ‘Rebuild Full-Text Entity Index’ screen would do that. I don’t see the feature on ‘Enable/Disable Features’

@davecrewe17 

Here is the knowledgebase document on this.

After going through the steps, it is likely you will need to do a restart application.

Hope this helps.

Ed

Thanks Ed, but as I mentioned I have already performed the Restart Full-Text Search, which is the only step that the KB article offers for R2022 onwards.

@davecrewe17 

have you done the below shown one 

Yes, I have done that. I mentioned this in the original post…

“I have run ‘Process All’ on the ‘Rebuild Full-Text Entity Index’ screen, and I have also tried the ‘Restart Full-Text Search’ option, but I am still seeing the warning.”

Hello @davecrewe17 

Step 1: Run the following MS SQL script to determine does the full-text search enabled on the database server.

SELECT *

FROM   sys.fulltext_indexes 

If this query returned an empty result, then the full-text search is disabled.

Step 2: Run the following MS SQL script to enable the full-text search.

EXEC Pp_disablefulltext

go

EXEC Pp_enablefulltext 

I was wondering if that was OK to run in 2024 version, as the other link suggests that it is for 2022 and earlier.

• I ran the first SQL and the result was empty. 
• I ran the second SQL and get the following:

(101705 rows affected)

(0 rows affected)

(11880 rows affected)

Completion time: 2024-10-17T10:35:48.7081348-06:00

• I ran the first command again, and it’s still empty, and I still have the same problem in the UI.
• I restarted the application but I still have the same issue.

Thanks,

Dave.

Hi ​@davecrewe17 were you able to find a solution? Thank you!

Nope, the issue is still there, even in a fresh deployment of 2024 R2

Hi ​@davecrewe17 , not sure if this will help, but make sure the full text search feature is actually installed within the sql server first. That’s what our issue was after restarting the search feature multiple times and had no luck. 

By that do you mean the steps in the KB article?

How to resolve the issue when a full-text search is not working | Community

Because I did already try that. Would be interested if there’s another way.

Hello- I’m experiencing the same issue and tried all the suggestions provided in these replies without success. ​@davecrewe17 Have you tried starting completely over with a new sql database? That’s the only option I can think of as left for me to try but it would mean losing a large amount of invested time.

​@s3raph777 have you restarted the application?

Yes. I attempted all the fixes mentioned in this forum.

Has anyone found a resolution to this?

I have a local instance of Acumatica 2025 R1.

I have tried “Restart Full Text Search”

I have tried “Process All”

I have tried “Restart Application”

I have tried the SQL script to disable and re-enable indexes

I have tried restarting the computer and IIS restart.

I have tried all these in various combinations and orders, but still get the following:

I was able to resolve this issue with my local instance.

For anyone looking for an answer, what I had to was completely uninstalled Acumatica AND SQL Server (both SQLEXPRESS and the SQLSERVER instances) from my local computer, then reinstall SQLServer ONLY (Not Express), then after basic installation, updated the feature selection to include "Full-Text and Semantic Extractions for Search".  After that, I installed Acumatica 2025 R1, rebuilt the full text entity index and viola the universal search now works without the error message.

Just so you know, I had tried to update the SQL instance with this checkbox while Acumatica was installed and that didn't work, so I think the key here is to have the feature installed/enabled on SQL before creating the Acumatica DB instance. 

Thank you for sharing your solution with the community ​@aslagle96!

​@davecrewe17 - On a local 24.114 instance, I needed to enable the Full Text Search in SQL Server 2019 (Developer) first.  Here’s a step by step - https://www.mssqltips.com/sqlservertip/6841/add-full-text-search-sql-server/

Both of these queries should give you a 1 in the results:

SELECT SERVERPROPERTY('IsFullTextInstalled') AS eFullTextSearchInstalled]

SELECT name, is_fulltext_enabled FROM sys.databases WHERE name = 'Your database name'

Then, I installed Acumatica 24.114 and opened the Configuration Wizard. I selected the 24.114 site and clicked on the Upgrade button even though it is already on 24.114.  Let the wizard complete and check for the message now - it should be gone.

Running this query should give you some records:

SELECT * FROM sys.fulltext_indexes

Hope this helps…..