Zoom Search Engine FAQ - Troubleshooting problems
Second, make sure you have not selected "Do not generate" for the Search Form option in the Configuration Window (under the "Search Page" tab). If so, change this back to "Basic form" or "Advanced form" and re-index and upload your files for the change to take effect.
Note: Some web authoring applications such as FrontPage and MS Word (see here for more issues with MS Word) have options which "compresses" the HTML by removing code it considers to be irrelevant. Often, these options will remove important code required by Zoom. Make sure you have these options disabled when dealing with Zoom related files.
GoLive CS is another application that has been found to be a culprit of this behaviour. The offending option in GoLive CS can be turned off under "Export Site Options"->"Strip Options..." and unchecking the "Comments" box.
If you suspect your search template ("search_template.html" or "search.html" ) has been corrupted, rename the file (for backup purposes - eg. "search_template_old.html"), and re-index your site to the same output directory. The Indexer will generate a new default search template when it finds that it is missing. You can then compare the two files to see if anything important was removed, or just start from scratch with the new default template - making sure to not remove the required lines of code again.
The best way to determine why a page was found but then skipped is to turn on "Skipped" messages on the Indexer's "Log" tab. Now when you index your website, the indexer will display the files it skips, and most importantly, the reason they are skipped.
The main reasons for files being skipped and not indexed are:
The spider indexing mode finds webpages to index by following the text links it comes across as it scans through your website, starting from the start URL you specified in the indexer. So if there are parts of your website that can not be found by clicking on links going from page-to-page of the start URL, then the spider will similarly fail to find them.
There are several other common scenarios in which the spider mode will be unable to follow the links (note that most of these also apply to external search engines such as Google, etc):
A sure-fire way to make sure that everything you want will be indexed with the spider mode will be to have a site map page - containing links to every page of your website, and using that as the start URL. This improves your website's usability and accessibility, letting more of your visitors (as well as search engines), get around your website better.
it would fail on the above examples. It is not possible to predict
or simulate the user behaviour with the mouse or data entry. So
being invisible to search engines.
By contrast, links generated dynamically on the server with CGI's, PHP or ASP will always be OK. This is becasue the code has been fully executed before it gets to the client.
Q. I get the error, [No files found to spider] Check that the URL exists and satisfies the settings in the configuration window
No file was found to index on your web site. Normally this means there is something wrong with the web server or the start point URL is wrong. But there can be many reasons for this error. See the FAQ's above regarding page skipping and the spiders not finding pages for troubleshooting.
Q. I've indexed the site, uploaded the files, but I only see the search script code when I open the search page in my browser (or get a prompt asking if i want to download it) - what's wrong?
Q. I am seeing the wrong text appear in the search results (or the results look strange and messed up)
This is most commonly caused by a corrupted set of index files. You may have either:
You should also make sure you are using the same version (and build) of the search script or CGI as the index files generated. This should be ensured if you followed the above requirements (uploading all the files listed in "Required files", etc.)
This is usually because you have either: (a) removed the necessary CSS from your search template page, or (b) upgraded from a previous version of Zoom with an old template page which is missing the new CSS.
For more information on customizing the appearance of your search results with CSS, please see this FAQ.
These files may not have last modified date and time information available. This may be because:
In both of these cases, you can use a last-modified Meta tag to specify a more meaningful date and time for the file. For more information, see chapter 6.7 of our Users Guide.
Q. When I click on a link in the search results, I get a 404 "Page Not Found" or "Page Cannot Be Found" error.
This is most likely due to an incorrect Base URL setting.
If you are indexing in Offline Mode, you need to specify a base URL that corresponds to the location of your web pages when they are hosted. This needs to be correct for the search result links to point to the correct location of the files.
If you are indexing in Spider Mode, the base URL should be automatically determined for you unless you have changed it manually.
For more information on specifying the correct base URL, please refer to the "Base URL" chapter in the Users Guide.
This is a non-critical warning message that indicates Zoom found a problem in the HTML source code of your web page.
If you do not understand nor wish to learn HTML, then technically, you can ignore this. Zoom will try its best to index the content on your page as best it can. But basic HTML knowledge is really essential for all web developers.
Mistakes in your HTML source can mean one or more of the following issues:
There are many tools out there to help you check your page for HTML errors. The W3C offer an article explaining the need to validate ("W3C: Why Validate?") and also the most definitive and comprehensive online HTML validator (validator.w3.org), but simpler HTML checking tools such as this one can also be a quick way to find your mistake.
Your IIS server is configured to use JScript for the default ASP language. Zoom's ASP search script however, uses VBScript.
You can change your IIS configuration to use VBScript from the IIS Control Panel (Start -> Settings -> Control Panel -> Administrative Tools -> Internet Information Services). Expand the tree and locate your website. Right click on the website, and select "Properties" -> "Home Directory". Click on "Configuration" -> "Options" and next to "Default ASP language:", replace the "JScript" text here with "VBScript". Click OK to apply. Note that doing this will default all your other ASP scripts to be parsed by the VBScript scripting engine.
An alternative would be to specify the scripting language within "search.asp" itself. This would allow you to have multiple ASP scripts that use different scripting languages within the same website/folder/application. However, this method requires modifying the search script source code (from Zoom, with ASP selected, click on "Templates" -> "Modify search script source code"). Add the following line to the very top of the file:
<%@ LANGUAGE="VBScript" %>
Save your changes and re-index. Note that this second method can cause issues if you are trying to include the search script within another ASP page using server-side includes. This is because the line must appear at the very beginning of the script output. So if this is the case, move this line somewhere appropriate (like the beginning of your include file).
Q. My search page is showing up blank and there is strange code in the source of my template page (eg. "<!--[if gte mso 9]>", "<o:DocumentProperties>", etc.)
This is caused by editing the search_template.html (or search_template_src.html) file in Microsoft Word or Office 2000, which has a known problem with producing corrupt HTML. This bug in Microsoft Word creates web pages that can not be opened/viewed correctly in certain versions of IE or even FrontPage.
You can check if you have this problem by opening the search_template.html file in IE, where you will see a blank page. If you "View Source", you will see the additional Office-specific markup ("gte mso 9", "DocumentProperties", etc.) which has been added to the file by Microsoft Word.
What you should do is either:
Q. I am seeing an error like, "... is not a valid Win32 application", when installing or trying to launch the Indexer (is Windows 2000 supported?)
This means you tried to install or run Zoom on a computer running Windows 2000 or an older operating system (such as Windows XP without SP2 installed).
While Zoom previously supported these operating systems, we eventually had to switch our development environment to the latest version from Microsoft. Unfortunately, Microsoft decided to drop support for Windows 2000 in their development tools (as they have also dropped user support for Windows 2000 sometime ago). So we were forced in to such a situation.
The last build of Zoom which supports Windows 2000 can be downloaded from here (V6.0 build 1024). Note that there have been subsequent bug fixes since that build, and further improvements will only be available in later builds.
Q. "Unable to locate component - This application has failed to start because Normaliz.dll was not found. ..."
Normaliz.dll is a Microsoft Windows component that comes with Windows and IE7 or later. If you are missing the file, it may be because you are using an older version of Windows (such as XP), or you have never updated to IE7 or later, or the system file was simply deleted.
You can typically fix this by installing IE7 or later. Microsoft also has a patch download which includes this DLL (as part of their Microsoft Internationalized Domain Names (IDN) Mitigation API) which you can download from here.
Please consult the Users Guide (PDF). We have tried to make this as comprehensive as possible, but if you still have problems, contact us at .
Return to the Zoom Search Engine Support page