HOME | SOLUTIONS | INDUSTRIES | SERVICES | ABOUT US | NEWS & EVENTS | SUPPORT CENTER | CONTACT

 
Product Documentation
Dovetail SelfService
Knowledge Base
Support Forums
Employee Blogs
Contact Us

Using seek.exe to do a complete rebuild of the indexes can cause a HTTP 500 error when simultaneously trying to perform a search. (Article # 339)

View products that this article applies to.

Problem:

By default, Seek (the indexer) and Seeker (the web search service) use the same directory for index files.
The index file directory is defined by the  fileSystemIndexDirectory property in C:\Program Files\Dovetail Software\Seeker\config\properties.config

If Seek is rebuilding indexes, and Seeker is simultaneously trying to perform a search, an error can be thrown by the Seeker web application.

Resolution:

By default, Seek (the indexer) and Seeker (the web search service) use the same directory for index files.
The index file directory is defined by the  fileSystemIndexDirectory property in C:\Program Files\Dovetail Software\Seeker\config\properties.config

You can separate the index directory used by both Seek and Seeker.
This way, Seek can rebuild a complete set of indexes, while Seeker continues to serve up search results.
When rebuilding is complete, the new index files can be copied to the correct directory, or Seeker’s config can be changed so that it uses the new index directory.

To use different index directories for Seek and Seeker;

1. Copy $seeker/config/properties.config to $seeker/bin/seek.properties.config

2. Modify $seeker/bin/seek.properties.config, setting the fileSystemIndexDirectory to your new index directory.

3. Modify $seek/bin/Seek.exe.config, so that it uses a different config file.
Change this line:
                <include uri="file://../config/properties.config" /> 
To this:
                <include uri="file://seek.properties.config" />

So, this allows Seek (the indexer) to use a different fileSystemIndexDirectory than Seeker (the web app).

Applies To:

Copyright © 2008 Dovetail Software, Inc. All rights reserved.

 

support center | blogs | terms & conditions | contact