nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Starting indexing kills Teamsite Service

System

I can start up all the Teamsite Services and the Teamsite Search services fine unless I add a branch for indexing. As soon as I try to do an initial index with a branch specifed in the config file it kills the main Teamsite service. Logs aren't telling me anything of use except that it stopped unexpectidly.

Anyone else having troubles with indexing killing their main Teamsite service?

Find more posts tagged with

Comments

Adam Stoller

I can start up all the Teamsite Services and the Teamsite Search services fine unless I add a branch for indexing. As soon as I try to do an initial index with a branch specifed in the config file it kills the main Teamsite service. Logs aren't telling me anything of use except that it stopped unexpectidly.

Anyone else having troubles with indexing killing their main Teamsite service?

Open a support case

Migrateduser

Already did, they had me re-install patches and other stuff. What I have finally found is that I am able to index all my branches except one. The indexing service and the Teamsite Service croakes within a minute of starting the initial indexing of the branch. I'm going to try and do some cleanup, run some of the store utility clts and if I'm lucky it will start indexing.

ravio

...What I have finally found is that I am able to index all my branches except one. The indexing service and the Teamsite Service croakes within a minute of starting the initial indexing of the branch....

Does the server log show any error when that happens?

bpg

Have you split the Teamsite and Search components onto separate servers?

The recommended infrastructure is to keep them separate as the search utility will eat up a lot of the CPU cycles, especially on initialisation, and if your server isn't meaty enough to deal with this then it could potentially cause the Teamsite services to crash.

Regards,

Brendan

Migrateduser

The server is brand new and has 4gb or ram and at least a 3ghz cpu. I'm positive it's something with the data since it's dying when I add the one branch. The other branch indexes just fine. I'm going to give up on it for now and just let my users use the Search on the first branch. Maybe I'll try to index it in a month when after the new install/upgrad/migrate settles down a little.

nipper

Only time I saw somethinglike this, the customer had installed SP1 for TS but not for Search. What patches did you install ?

Migrateduser

I've installed SP2 for both Search and Teamsite. I originally didn't install them in the recommended order, so I uninstalled all the patches and SP's and re-installed in the correct order. Still having the issue. Since this is in production and I just set it up I'm not willing to uninstall the entire thing, delete the leftover iw-home and begin again.

It may very well have been the incorrect installation order, but I guess I'll never know.