Enterprise Search broken

We’re upgrading to 2025.2 soon (yes on-prem…), and I can’t get Enterprise search going. Everything else is working. Ticket open with Epicor for 2 weeks but no help there yet.

There is no ES Index defined yet, so I can’t add it to Company Maintenance. But when I try to make an ES Index, I get this error (client side).

Server-side error is “Connection string for the Enterprise Search database is not specified.”

Any ideas? I can’t find anything in the install/upgrade guides, KB, internet… realize it is probably something super dumb somewhere. Thanks!

1 Like

What’s the config look like in your Epicor Admin Console? Do you have a dB defined there? If you moved to new servers as part of your 25.2 upgrade you have to redeploy ES.

Hi Terry,

Have you deployed Enterprise Search from the Administration Console?

Thanks,

Nathan

Beat me to it!

1 Like

Alright well we’re getting somewhere thanks! It is missing in EAC on the new server… though I’m not seeing how to get it to show up?

I found this… do I really need another local instance of SQL on the app server??

No, you can put the ES dB on your same SQL server that you use for Kinetic.

Yeah that didn’t make sense. Ok so how to find the button to get it to show up in EAC…

Right click your server name and you can create the dB. Then you go under Search Indexes to create your index. Once the index is created it will give you the endpoint to use in Kinetic.

Open Kinetic, search for Enterprise Search configuration Maint.
There is a menu to setup connection string and another menu to create a database.

2 Likes

Man I’m not seeing the option…


Everything was installed too..

Looks like it 25.x it moved. Looks like it’s in Kinetic now as @Olga pointed out.

1 Like

Ok thanks! This isn’t in the help anywhere.

Now I get this error when trying to make the index:

Invalid object name ‘_SearchIndex’.

Start with new db then, recreate index from scratch.

Depending on the version you are coming from this can be a bug. If you look at the table that holds the ES Config you might find that the server column is empty.

In the bug state you can’t even really open the ES Config screen.

Unofficial recommendation that I got from Epicor after some poking is to not use the recurring option built in the screen. Set the processes required to run for 29 minutes and put them on a 30 min interval task agent process that is recurring.

That column can be empty now, when ES is part of app server.

_SearchIndex table is not in this database, it is in ES database. And should be already there for several releases at least.

Nothing functioned until I got that column filled in. These two cases describes the saga of getting ES to work again CS0005022557 and CS0004843853.

The screen would throw exceptions and was all read-only.

2 Likes

Well all I can do is laugh. The search index got corrupted or something, so in ES Config Maintenance I said delete the database. “Are you sure you want to delete the Enterprise Search database?” “Yes.” And it deleted the entire Kinetic Live database…!!

3 Likes

When you did it in EAC you also pointed ES database to the live Kinetic database? It was always separate DB for ES

Yeah there wasn’t another one to choose from. Man where is all this in the help files…

Did you read them?

And there is no search for existing databases anymore. You have to enter it.