Troubleshooting -- dtSearch Web server error codes

Last Reviewed: August 5, 2013

Article: DTS0178

 

Applies to: dtSearch Web 6, 7

1. Find the error code on the error page

HTTP Error 401 - "Access Denied" or "Unauthorized"

Check the NTFS folder permissions for the dtSearch folder on your web site (i.e., c:\inetpub\wwwroot\dtsearch), the index folders, and the documents. If the indexes or documents are located on another server, please see this article for information on accessing documents between servers: dtSearch Web Document Access problems

If you cannot determine what the source of the error is from the message, see "How to find errors in the IIS logs" below.

HTTP Error 404 - "Not Found"

A 404 error means that the dtSearch Web files were not found.  Possible reasons for a 404 error when you try to search include:
(1) The search form created for one web site is being used with another.   If you have more than one web site on a server, you may have installed dtSearch Web on site "A" but not on site "B", so when a user tries to use the search form with site "B", the dtSearch Web application is not found.  To fix this problem,

(a) Run dtSearch Web Setup,

(b) Select site "B",

(c) Click the Install button to install dtSearch Web

(d) Generate a new search form for site "B"

(2) You have installed dtSearch Web under Windows Server and it is not registered as a Web Services Extension.  See these articles for instructions to resolve this problem:  

How to install dtSearch Web on Windows Server 2012 or Windows Server 2008

How to install dtSearch Web on Windows 2003 Server

HTTP Error 405 - Method Not Allowed

A 405 error means that the folder where dtSearch Web is installed does not have "Execute" permission enabled. To fix the problem:

(1) Start dtSearch Web Setup
(2) Select the web site where dtSearch Web is to be installed.

(3) Click the Install button. This will install the dtSearch Web files and will also set the "Execute" permission for the folder where dtSearch Web is installed.
(4) Open Internet Services Manager and check the folder where dtSearch Web was installed to verify that "Execute" permission is enabled.  
    In IIS 7.x, to check for "Execute" permission, select the "dtSearch" folder, click the "Handler Mappings" icon, and then click the "Permissions..." link on the right.
    In older versions of IIS, right-click the dtSearch folder and select "Properties" and check the "Virtual Directory" tab.

dtSearch Web error -- the file could not be accessed because it is not in a virtual directory

See dtSearch Web Document access problems.

0x800700c1 error in 64-bit Windows Server

An "0x800700c1" error when you try to search indicates that you are trying to run the 64-bit version of dtSearch Web in a 32-bit application pool.  To run the 64-bit version of dtSearch Web on a 64-bit version of Windows Server, in Internet Information Services select the application pool used with dtSearch Web, select "Advanced Settings", and set "Enable 32-bit Applications" to "false".

0x8007007f error in Windows Server

Error code 0x8007007f occurs if you register a dtSearch component (dtisapi6.dll, dtengine64.dll, or dten600.dll) as an "ISAPI Filter" in IIS.  dtSearch does not have any ISAPI filters, so when you register a dtSearch DLL this way, IIS will try to load it as an ISAPI filter and will display error code 0x8007007f when it cannot find the exported functions that ISAPI filters are required to have.  (The component dtisapi6.dll is an ISAPI extension, not a filter.)

To fix the problem, un-register any dtSearch DLLs that you have registered as ISAPI filters.

Http Error 500 - Internal Server Error

To interpret a 500 error, check the Event Viewer to obtain more information about the error that occurred (see below).

If there is nothing in the Event Viewer, check the location of dtisapi6.dll on your web server and on the search form.  If dtisapi6.dll is not in the location given in the search form, the server may return a 500 error without logging anything.  For example, if the search form references /scripts/dtSearch/dtisapi6.dll and dtSearch Web is really in /dtSearch/dtisapi6.dll, the server will not find dtisapi6.dll when a search is started and will return the 500 error.  If the server has more than one web site, check that the virtual directory where dtisapi6.dll is located is defined for the server that is being used for the search.

2. How to check the Windows Event Viewer

The Event Viewer records errors affecting Windows components and will sometimes have useful information about IIS problems.

To access the Event Viewer, click Start > Settings > Control Panel > Administrative Tools > Event Viewer. Look in the System log for an error at the same time the message appeared. The log entry will contain an Event ID that you can use to determine the source of the problem.

The Event Viewer often has tens of thousands of entries, which can make it difficult to find the relevant entry.  To look for an entry that relates to an error, first try to reproduce the error and then sort the event log by date so the most recent errors will appear at the top of the list.

Event ID 36 Server failed to load application '  '.  The error was '80004005'.

This error occurs when an application does not have a name specified or does not have execute permission enabled.  To fix the problem,

(1) Open Internet Information Services Manager

(2) Open the web site

(3) Open the /scripts/dtSearch application

(4) Under Application Configuration, click "Create"

(5) Enter "dtSearch" as the name

(6) Make sure "Execute" permission is set.

(7) Close the Properties dialog box

For more information, see:

Err Msg: Server Failed to Load Application, 80004005
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q200514

3.  How to find errors in the IIS logs

IIS records every request and the result of that request in a set of text log files.  These files can help it identify the source of "Access Denied" or "Not Found" errors because the log entry will record the file that IIS was trying to access when the error occurred.  

To find the log files,

1.  Open Start > Administrative Tools > Internet Information Services Manager

2.  Select a web site from the list of sites.

3.  Select the Logging icon in the list of icons under "IIS" to the right of the web site list.

4.  Look for the location of the log files folder, which will usually be %SystemDrive%\inetpub\logs\LogFiles

5.  Open this folder and look under it for the folder that corresponds to the web site (the folders for each web site on the server will be named W3SVC1, W3SVC2, etc.).

6.  Inside the W3SVC folder, find the most recent .log file, and open it in notepad.

Each line in the log represents a request what the web server received.  The line with include the path of the file that was requested and, at the end of the line, a set of numbers indicating the result.  If an HTTP error occurred such as 401, 404, or 405, then this number will appear.  If the result was successful, then "200" will appear.

Additional Resources

Microsoft support site (search for "Event ID NN" where NN is the event ID from the Event Viewer).
http://search.microsoft.com/advanced_search.asp?siteid=us/dev

General information on fixing problems in Internet Information Server
http://www.iisfaq.com