Search Broker

[ibredbeard]

Hi,
When I do a search in Livelink I get the following error:
Livelink Error:
Error in search broker

[Search engine on computername:8500 not available!]

I did read a post here with the same thing, so when I went to Test System Objects for Errors, and did the test, I get the following:
6214 The process has returned an error: Unable to connect to the index server. The process is in an unknown state.

6200
6212
6213
Correction: Enterprise Data Flow Manager
Enterprise Extractor Process
Enterprise HTML Conversion
Enterprise Index Engine
Default
The Index server is running, I checked. I have purged the index and it has been recreated no problem so it is pointing to the right place. Is there anything I can do for this to work? Any service that that needs to be started (Livelink Admin and Livelink Server are running)? Also, Livelink Frontend and the index server is on one computer while the database is on another. Thanks in advance.

 

[appnair]

Port is not available
What OS is this
Did you guys do any snap shot of DB and try configuring
a new Livelink install off of that ?
Otherwise do a netstat -a and look for port 8500 being used
Is Admin going into safe mode ?
Is the indexing directory writable by the user running the Admin service
Have you talked to OT support ?




Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[appnair]

Most silly things in windows will clear after a re-boot like port conflicts

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[ibredbeard]

Hi,
The OS is MS Windows 2000, no we didn't do a snapshot, port 8500 is being used by d:\OPENTEXT\bin\otsearch.exe, admin IS NOT going into safe mode. For your last question, "Is the indexing directory writable by the user running the Admin service" the directory has the EVeryone group with full rights. Haven't talked to OT support either cause it costs to much money. I also have rebooted many times. Hope this helps, thanks.

 

[appnair]

If you want to do this yourself then maybe it is time to turn logs on and look for some tell tale signs.When you click the index engine and try to start it, is that when you see the errors.have you tried a resynchronize on default?.Sometimes an unindexable node gets into the datapool and that causes problems.If you do

select * from kini where inisection like 'otcindex'

if you get -1 then there are no more things to index.If it is stuck at a nodeid then the indexer is trying to index that node and is having difficulty moving it away from the process.There are several other factors that could break it like memory requirements etc but hard to tell without actually observing the logs.I am just trying to help but if I were you and if I could afford it I would just set up indexing on another server to get my processing work.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[appnair]

There are some more indexing checks that OT recommends
Check if there is a livelink.log over 2GB in size.If there is shutdown the indexer and re-start.Check for a livelink.lck in the index directory.If there is shutdown admin server and remove the lck file.There are several other problems which involves deleting the otadmin.pid and otadmin.pid.old also but use all with caution



Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[ibredbeard]

Thanks for the help, I will try. But just to note, I rebuilt the livelink Frontend on another computer (one that never had livelink before) and I still got that error when I tried to search. I can access all the files in the database, but no search. Also, it seems notifications from the workflows doesn't work either. But...I convienced my boss who convienced his boss to shell out the money for OT support so I will hopefully be talking to them this week. Although any more help would cool as well. Again, thanks for the help.

 

[appnair]

Search in a nutshell is made up of a index and not based on your database capability.All the help for search is available in the admin help slice which you cannot access now because of the problem.But that should be available in this path <your livelink paath>\support\adminhelp\otadmin.The admin-help is a directory walker process.Try especially the chapters on re-synchronizing your default admin server.Most data flow problems will go away using that.When you said you built another frontend and installed livelink admin service you probably moved the data index processes from one computer to another.If your Index server is working correctly this query should show you

 select * from kini where inisection like 'AdminServers%'

My guess is that it is still showing your old server's parameters.Now changing that is a whole new experience.There is two page document to accomplish that.Write me off line at appnair at gmail.com or nairkn at gmail.com and I will send you that information.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[BKQc]

You probably already know that but from what we had here, this message occured when the Search Engine was down in the search manager folder of the Data Source folder of the system volume.

If you have many Data Sources, drill down each one until you find the one.