You are currently offline, waiting for your internet to reconnect

Error message when a user of your Web page performs a search in FrontPage: "HTTP/1.1 404 Object Not Found"

Support for Office 2003 has ended

Microsoft ended support for Office 2003 on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q317390
SYMPTOMS
When you configure the Microsoft FrontPage Search component to use the Index server, users of your Web page receive the following error message when they click the Search button on your Web page:
HTTP/1.1 404 Object Not Found

/_vti_script/pagename.html0.idq cannot be found
CAUSE
This behavior occurs if the setting to allow access to Internet Data Query (.idq) files is turned off. This setting is often turned off for security reasons. To turn this setting on or off, run the Internet Information Services (IIS) Lockdown Wizard (Iislockd.exe).
RESOLUTION
To resolve this issue, use any of the following methods.

Method 1: Allow users to gain access to .idq files

To reverse the changes made by the IIS Lockdown Wizard, run the wizard again. To do so, follow these steps:
  1. To obtain the IIS Lockdown Wizard and learn more about it, visit the following Microsoft Web site:
  2. Go to the link at the bottom of the page, download the Iislockd.exe file, and then follow the on-screen instructions to undo the changes that were made by the wizard.

Method 2: Use the FreeWAIS search engine to perform searches

If you prefer to retain the security level generated by the IIS Lockdown Wizard, you can configure FrontPage Server Extensions to use the FreeWAIS (Wide Area Information Service) search engine, which is included with FrontPage. Use the appropriate method for your situation.

Method 2a: Search all Webs across all virtual roots on the Web server

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\All Ports
  4. Right-click All Ports, point to New, and then click String Value.
  5. For the name of the string, type noindexserver.
  6. Double-click the string.
  7. In the Value Data box, type 1, and then click OK.
  8. Quit Registry Editor.
  9. Recalculate the hyperlinks for each virtual server to rebuild the text indexes. To do this, follow these steps:
    1. Start FrontPage.
    2. Open a Web site.
    3. On the Tools menu, click Recalculate Hyperlinks.

      Repeat steps b and c for each Web site.

Method 2b: Search a specific Web site or virtual root on the Web server

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate the following registry subkey
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Ports\Port /LM/W3SVC/xx
    where xx is the instance number for the virtual root. For more information about how to determine the instance number, click the following article number to view the article in the Microsoft Knowledge Base:
    197891 Enumerating the names of IIS Web sites using WSH
  4. Right-click All Ports, point to New, and then click String Value.
  5. For the name of the string, type noindexserver.
  6. Double-click the string.
  7. In the Value Data box, type 1, and then click OK.
  8. Quit Registry Editor.
  9. Recalculate the hyperlinks for the virtual server to rebuild the text indexes. To do this, follow these steps:
    1. Start FrontPage.
    2. Open the Web site that you want to recalculate.
    3. On the Tools menu, click Recalculate Hyperlinks.
front page prb FP2002 FP2003
Properties

Article ID: 317390 - Last Review: 01/31/2007 19:40:36 - Revision: 3.2

  • Microsoft FrontPage 2002 Standard Edition
  • Microsoft Office FrontPage 2003
  • kbpermissions kbregistry kberrmsg kbprb KB317390
Feedback