Browsing Solutions For 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.

  • HOW TO: Reset the Dovetail Seeker indexing process

    The following solution discusses potential issues that can occur when performing live edits to the Seeker document specifications file while the Seeker Indexer service is running. Any edit of the Seeker document specifications file (documentSpecifications.xml) will cause a re-index of the document specification (search domain) that was edited. A re-index of a document specification has the potential to push a large number of messages onto the message queue. For example, if you edited the "case" document specification, and you had 100,000 cases in your system, then 100,000 messages will be pushed onto the message queue. Each message represents a case that needs to be re-indexed. If another edit is done to the same document specification (even if its a revert of the edit made previously), another re-index of the entire specification will be queued up, which will occur after the previous re-index finishes. This is essentially doubling the work that Seeker is doing. For large indexes the best thing to do at this point is to reset the indexing and restart the indexing.

  • Using a non-Clarify column as part of the documentSelectionCriteria in Seeker

    Using a non-Clarify column as part of the documentSelectionCriteria in Seeker i.e. a column that exists in the database, but is not part of the Clarify schema?

  • Refreshing Dovetail SDK Caches

    Applications which use Dovetail SDK (which are pretty much all applications shipped by Dovetail Software) cache commonly used data to avoid repeated lookups in to the database. Each cache is loaded once, during application initialization. It is common to have objects that are cached get modified during the application's lifespan. When this happens the outdated cache should be refreshed. This article will show you how to refresh the caches at the application level and programatically in your own applications using the Dovetail SDK.

  • How many processors should my Dovetail application server have?

    A customer recently asked if they should provision multiple CPUs on virtual machines hosting Dovetail applications. Dovetail web and service applications can utilize more than one processor to get more work done concurrently.

  • Seeker performance: How do I limit the number of objects indexed concurrently?

    As of version 2.0 Dovetail Seeker's indexer has been tuned to have less impact on your database server while indexing many objects (think cases) concurrently. If you are having performance concerns with Seeker I first recommend that you ensure that you are following this solution making sure all selection criteria database fields are being indexed: http://support.dovetailsoftware.com/selfservice/solutions/show/449 Seeker divides up the indexing work it does into work to be done as messages and queues them up using Microsoft Message Queueing (MSMQ). The windows service watches the message queue for work to be done. Many message consumers are started to concurrently process the work queue. The default number of concurrent message consumers (indexing content) is 4 times the number of processors. This includes hypertheading processors. For example at Dovetail we have a quad-core PC which is hyperthreaded which means that it has 8 virtual cores. This means that Seeker on this machine is (2 times 8) is processing 16 messages at once by default. While this may seem like a lot. The default is intended to maximize the potential utilization of the application server. Some customers wish to reduce the number of message consumers to slow down the indexing process to reduce the load on the application and database server.

  • Seeker: How do I limit what cases or other objects get indexed by date?

    Seeker administrators can control what Clarify database objects get indexed by editing the Document Selection Criteria in the documentSpecifications.xml configuration file. http://support.dovetailsoftware.com/documentation/Dovetail%20Seeker/2.0.12/html/2849.htm Here is the default case document selection criteria: creation_time > ${lastIndexUpdate} OR modify_stmp > ${lastIndexUpdate} Think of the document selection criteria like a SQL where clause for the following query: SELECT id_number FROM table_case WHERE {document selection criteria} You can test out your criteria by popping it into the query above. Swapping out the last update date with a "recent" date time. On the first index run the last updated date will initially be 01-01-1753 or something similar and on subsequent runs will be set the last date time the index was updated.

  • Can I use Seeker to search database tables that are not part of the Clarify schema?

    Can I use Seeker to search database tables that are not part of the Clarify schema?

  • Installing web applications on IIS7 (Vista and Widows Server 2008) fails.

    Changes to how Internet Information Server (IIS) is configured have caused problems with installers for Dovetail applications which create virtual web directories. These installer were designed to create virtual directories on IIS 6 You may get an error "Cannot connect to Internet Information Server" or "Failed to read IIsWebs table"

  • Some objects in my database are not getting re-indexed

    When Dovetail Seeker indexes your objects in your Dovetail CRM database it is possible that some objects will not get re-indexed because the last modified timestamp of the object is not getting updated. Dovetail Seeker typically uses the last modified timestamp of an entity to determine when an object should get re-indexed. If the timestamp is newer that the last time the indexer ran, then the object will get re-indexed. However, not all operations on an object will update the timestamp, especially when using different clients, older clients, or custom scripts. For example, adding an attachment to the case using the Clarify Classic Client does not update the last modified timestamp of the case (table_case.modify_stmp)

  • Using Dovetail Software products with 32bit Oracle drivers can cause ORA-12154 error

    When running a Dovetail Product that is using 32bit Oracle drivers, a user may encounter a message as follows: ORA-12154: TNS:could not resolve the connect identifier specified The above message should be displayed to the user, or located in log files for the product being used. As an example, Dovetail Schema Editor shows the following: "Error Occurred : Database settings in "Default.SchemaEditor" are not valid. Please confirm that database type and connection string are correct." Within the SchemaEditor.log file, the following exists: 2010-10-12 14:44:51,259 ERROR Dovetail.DataDictionary.Persistence.Database.SqlHelperAdapter - Database connection could not be made: ORA-12154: TNS:could not resolve the connect identifier specified System.Data.OracleClient.OracleException: ORA-12154: TNS:could not resolve the connect identifier specified This issue is not specific to Dovetail applications, but is a known Oracle bug with respect to the path used for Oracle 32 bit software. Typically this occurs in 64bit OS environments where (by default) Windows likes to install 32-bit apps into the C:\Program Files (x86)\... folder. The problem is in the C:\Program Files (x86)\ directory name - specifically, the parenthesis. Calls made to the 32bit drivers fail because the calling program information is passed to Oracle, where it takes the () as a special command. Oracle Article ID 334528.1 provides detailed information (login required): https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=334528.1

  • Dovetail Seeker Indexing - Document selection is taking a long time

    If you are experiencing slow performance when Dovetail Seeker is indexing documents. In particular if you are seeing logs like this (from our case example included with Seeker) with no activity after it: Getting identifiers needing indexing for domain case for identification field id_number. Adding document selection criteria 'creation_time > ${lastIndexUpdate} OR modify_stmp > ${lastIndexUpdate}'. This step in the indexing is where Dovetail Seeker determines what database objects need to be indexed. When this is the first index run or a re-indexing this step can take a long time when there is no index on any of the database fields involved in the document selection criteria.

  • After installing SeekerProxy, other web applications return HTTP Error 500.0 - Internal Server Error

    After installing SeekerProxy, other web applications return HTTP Error 500.0 - Internal Server Error HTTP Error 500.0 - Internal Server Error Calling LoadLibraryEx on ISAPI filter "C:\apps\Dovetail Software\SeekerProxy\IIRF.dll" failed Module IIS Web Core Notification Unknown Handler StaticFile Error Code 0x80070005 keywords: seeker proxy iirf iirf.ini iirf.dll

  • Some objects in my database are not getting indexed.

    When Dovetail Seeker indexes your objects in your Dovetail CRM database it is possible that some objects will not get indexed when they have NULL values in the fields used to determine if that object has been added or modified. For example the out of the box document specification for indexing cases uses the creation_time and modify_stmp database fields to determine if the case is new or updated. <documentSelectionCriteria><![CDATA[creation_time > ${lastIndexUpdate} OR modify_stmp > ${lastIndexUpdate}]]></documentSelectionCriteria> When a case has a NULL value for both of these fields it will not get added to the index. This happens because the SQL query executed requires that a value be present in either of these fields otherwise no row will ever be retrurned.

  • Some objects in my database are always updated by the Dovetail Seeker indexer

    When Dovetail Seeker indexes your objects in your Dovetail CRM database it is possible that some objects will always get indexed when they future datetime values in the fields used to determine if that object has been added or modified. For example the out of the box document specification for indexing cases uses the creation_time and modify_stmp database fields to determine if the case is new or updated. <documentSelectionCriteria><![CDATA[creation_time > ${lastIndexUpdate} OR modify_stmp > ${lastIndexUpdate}]]></documentSelectionCriteria> When a case has a future value for either of these fields the search index be updated for that case during ever index update. This happens because the SQL query always return a row when any one of the document selection criteria fields is in the future.

  • How do I enable logging of windows installer failures?

    Problems can crop up with windows installers. If you do not have permissions or a required subsystem is missing you can get weird errors. When you open a case with us regarding installation issues we will likely ask that you send us an installer log. Below are instructions on how to get a log of the results of an failure to install one of our MSI installers.

  • How do I avoid rebooting during my Seeker Proxy uninstall

    When uninstalling the Seeker Proxy, you will likely be prompted to reboot the server. This is not desirable in a production environment. The reason this is happening is because the web application uses an ISAPI filter at the web site level. If any web applications are running, the uninstall will prompt you to do a reboot after the uninstall has finished.

  • How do I avoid rebooting during my Dovetail Seeker uninstall

    When uninstalling the Dovetail Seeker, you will likely be prompted to reboot the server. This is not desirable in a production environment. The reason this is happening is because the web application is loaded in an application pool that is currently running.

  • Viewing Dovetail Seeker Search Results Using Curl

    While installing Dovetail Seeker sometimes it is handy to verify to manually run searches against the Seeker search web service. Using a normal browser to do this can be tricky as the search service returns its output as JSON which browsers don't normally like to view.

  • Error installing Dovetail Seeker - Failed to read IIsWebs table. (-2147023728)

    When installing Dovetail Seeker on a server which has non default web site bindings. You can get the following error. Failed to read IIsWebs table. (-2147023728) Web site bindings are the IP, Port, and Host Header Name which IIS is serving pages for. The newest version of Dovetail Seeker installer has the ability to specify the binding of the web site you wish to use.

  • Cannot connect to Internet Information Server

    The following error can occur when a Dovetail application installer is attempting to create an IIS virtual directory for a web application being deployed: Cannot connect to Internet Information Server. One of the reasons this error can occur is related to a name change to the default IIS web site. The installer is looking for a web site named "Default Web Site". When the name of this web site has been changed you will get the error above. To confirm this is the problem you can turn on windows installer logging. The following solution tells you how to do this: http://www.dovetailsoftware.com/resources/solutions/182_How_do_I_enable_logging.aspx Within this log you will see this error when a renamed Default Web Site is to blame: ConfigureIIsExec: A matching web object in memory was found, but the web object in memory has no associated base ConfigureIIsExec: Error 0x80070002: Failed to find Web base ConfigureIIsExec: Error 0x80070002: Failed to get base of web: DefaultWebSite for VirtualDir ConfigureIIsExec: Error 0x80070002: failed while processing WebVirtualDirs

  • Server Error in '/seeker' Application. Configuration Error

    The Dovetail Seeker web application can throw the following error: Server Error in '/seeker' Application. Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load type 'System.Web.Mvc.ViewTypeParserFilter' from assembly 'System.Web.Mvc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'. Source Error: Line 16: <pages Line 17: validateRequest="false" Line 18: pageParserFilterType="System.Web.Mvc.ViewTypeParserFilter, System.Web.Mvc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" Line 19: pageBaseType="System.Web.Mvc.ViewPage, System.Web.Mvc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" Line 20: userControlBaseType="System.Web.Mvc.ViewUserControl, System.Web.Mvc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"> Source File: C:\Program Files\Dovetail Software\Seeker\views\web.config Line: 18 Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082

  • Server Error in '/seeker' Application: Could not find an Instance named "~specifications"

    Viewing the Seeker web application (http://localhost/seeker/~Specifications/List) can result in an error such as: Server Error in '/seeker' Application. ________________________________________ StructureMap Exception Code: 200 Could not find an Instance named "~specifications" for PluginType System.Web.Mvc.IController Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: StructureMap.StructureMapException: StructureMap Exception Code: 200 Could not find an Instance named "~specifications" for PluginType System.Web.Mvc.IController Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [StructureMapException: StructureMap Exception Code: 200 Could not find an Instance named "~specifications" for PluginType System.Web.Mvc.IController] StructureMap.BuildSession.CreateInstance(Type pluginType, String name) +225 StructureMap.Container.GetInstance(Type pluginType, String instanceKey) +60 StructureMap.Container.GetInstance(String instanceKey) +91 StructureMap.ObjectFactory.GetNamedInstance(String name) +105 Dovetail.Search.Web.Configuration.StructureMapControllerFactory.CreateController(RequestContext context, String controllerName) +59 System.Web.Mvc.MvcHandler.ProcessRequest(HttpContextBase httpContext) +88 System.Web.Mvc.MvcHandler.ProcessRequest(HttpContext httpContext) +39 System.Web.Mvc.MvcHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext httpContext) +7 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 ________________________________________ Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082

  • Hosting Dovetail web applications build with Asp.Net MVC using IIS5 on Windows XP

    IIS 5 is not officially supported as a deployment platform for Dovetail web applications built on Asp.Net MVC. These applications currently include: Dovetail Mobile Agent Dovetail Seeker (as of version 1.2) It is possible to use IIS 5.1 on Windows XP do development testing of these applications.

  • Compiler Error Message: CS0012: The type 'Microsoft.JScript.INeedEngine' is defined in an assembly that is not referenced.

    When trying to view the Specifications for Seeker, the following error occurs: Compiler Error Message: CS0012: The type 'Microsoft.JScript.INeedEngine' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.JScript, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.

  • Dovetail Seeker Administration page returns 403 error : You are not authorized to view this page

    Using a browser to view the Dovetail Seeker Administration page (http://server/seeker/) returns a 403 error (you are not authorized to view this page) Error: You are not authorized to view this page You might not have permission to view this directory or page using the credentials you supplied. HTTP Error 403 - Forbidden Internet Explorer This is because there is not a correct default document (default content page) defined that matches to the default document for seeker. Specifically, default.aspx is not defined as a default document. Because there is not a matching default document, the HTTP request looks like a directory listing request, which is typically not allowed, so a 403 (Forbidden) error is returned.

  • Using seek.exe to do a complete rebuild of the indexes can cause a HTTP 500 error when simultaneously trying to perform a search.

    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.

  • Seeker give a "The page cannot be displayed (404) error when performing a search.

    When using a virtual directory for Dovetail Seeker other than the default virtual directory created during the install of the application, the .aspx and .castle application mappings need to be configured manually.

  • Logs are not appearing for web applications.

    Dovetail web applications: Dovetail Agent, Dovetail Admin, Dovetail Seeker have logging mechanisms that are useful for application administrators to provide a detailed view into application behavior. It is common to run into security issues for web applications attempting to write logs out to a file.

  • Seeker web application returns 404 error

    Internet Information Server (IIS) on Windows Server 2003 and Windows Server 2008 default behavior is to have ASP.Net web applications disabled. Dovetail web applications that use ASP.Net require that you have the ASP.Net web extension enabled. If not enabled HTTP status 404 errors will be returned when requesting web pages from the application.