Specializing in Support and Service Software

Browse blog posts about Dovetail Seeker

• .Net Web application returns HTTP Error 500.19 - Internal Server Error

  After installing a .Net based web application you may see the following error: HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid. This is likely happening because your web application's application pool is not using the correct version of the .Net Framework. When the web application is installed a new application pool for it is created. The default settings of the application pool will come from IIS not the installer. When the application you are installing requires .Net 4.0 and your server has IIS configured to use .Net 2.0 by default you will need to reconfigure the application's app pool to use the correct version of the .Net framework.

• Seeker installer is not finding any IIS websites

  As of Version 2.0 the Dovetail Seeker installer will prompt you for the website where you wish to install the search web service. If you installing Dovetail Seeker on IIS7 and you have not installed the IIS6 Management Compatibility features you will see not see any entries in the dialog for selecting the web site where the Dovetail Seeker search web service will be installed.

• Uninstalling Dovetail Seeker 1.5.1

  How should Dovetail Seeker 1.5.1. be uninstalled? There is not an uninstall utility, and there is no entry in the Control Panel "Add or Remove Programs." The Seeker CHM file mentions a command to uninstall the Seeker Service. However, this will not remove the Seeker application, just the indexing service.

• How much disk space will the Dovetail Seeker index use?

  The size of Dovetail Seeker search indexes is hard to predict ahead of time. The short answer is that it will be proportionate to the content being indexed. This article will try to give you some background to help you plan when trying to predict your search index file size.

• Dovetail Seeker cannot communicate with the message queue

  It is important for each document specification to have document selection criteria which sufficiently constrains the number of documents which will be indexed on every poll. Users who have an empty document selection criteria for a domain could run into the following error: System.Messaging.MessageQueueException: Insufficient resources to perform operation. This is happening due a blank document selection criteria or one that always returns a large number of duplicate objects to index. An example of this happening from the SeekerIndexer log: 15:07:39,165 [ 8] INFO ClarifyDocumentService - Domain Logistics was last indexed at 04/29/2011 15:07:00 15:07:39,758 [ 8] INFO ClarifyDocumentService - Found 316101 Logistics documents requiring indexing. 15:08:09,133 [11] INFO ClarifyDocumentService - Domain Logistics was last indexed at 04/29/2011 15:07:45 15:08:09,899 [11] INFO ClarifyDocumentService - Found 316102 Logistics documents requiring indexing. 15:08:54,336 [ 6] INFO ClarifyDocumentService - Domain Logistics was last indexed at 04/29/2011 15:08:15 15:08:54,774 [ 6] INFO ClarifyDocumentService - Found 316103 Logistics documents requiring indexing. 15:09:39,290 [10] INFO ClarifyDocumentService - Domain Logistics was last indexed at 04/29/2011 15:09:00 When every database poll results in duplicate objects to update. Seeker cannot keep up and queues the work to do in the future. After a long while this will fill up the available space that the message queue can address causing the error above.