Can't startup Interwoven TeamSite Index Server service

I have two servers. Search and Index are installed on one and TeamSite is installed on the other.

When I try to startup the Index Service on the Search server it fails and I get a "Listener is unable to connect to the event subsystem" error in the iw.tsindex.log file. On the TeamSite server I get a java.lang.OutOfMemoryError thrown in the eventsubd_err.log file.

It would seem that they are talking to each other somewhat, but the indexer is unable to properly startup.

Any suggestions?

Find more posts tagged with

Comments

Migrateduser

Just found this KB article and am giving it a try. Will report on progress later.

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=56762

Migrateduser

Yep, that fixed the issue.

Migrateduser

Great that you have got this problem resolved which was due to eventSubsystem goinf out of memory. Can you provide details on what database are you using and what are the number of rows in the messages and messages_handles tables. The DB sizing is also known to cause these errors.

Migrateduser

Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

DB size = 1.8 GB
message_handles = over 800,000
messages = over 800,000
all other tables contain less that 10 rows

Migrateduser

This are large numbers. It appears that you have not applie SQL Server dead lock prevention script to your DB and hence there is message piling.If this is the case and you dont have DAS do the following
1.) Stop the eventSubsystem.
2.) Backup the DB.
3) Delete all entries in the Mesages and Messages_handles tables.
4.) Apply the SQL server deadlock prevention script (see devnet, support)
5.) Start the eventSubsystem.

You can run the index refreshbranch CLT to compansate for the lost messages.

Migrateduser

I took your suggestions and also moved our database over to an MSSQL 2005 database (had to follow this KB article https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=56631).

No problems so far and the search engine is indexing again.