403 lines
54 KiB
HTML
403 lines
54 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
|
|
|
<html>
|
|
|
|
<head>
|
|
<title>Microsoft Index Server Guide: Error Messages</title>
|
|
<meta name="FORMATTER" content="Microsoft FrontPage 1.1">
|
|
<meta name="GENERATOR" content="Microsoft FrontPage 1.1">
|
|
</head>
|
|
|
|
<body bgcolor="#FFFFFF">
|
|
<!--Headerbegin--><p align=center><a name="TOP"><img src="onepix.gif" alt="Space" align=middle width=1 height=1></a> <a href="default.htm#Top"><img src="toc.gif" alt=" Contents" align=middle border=0 width=89 height=31></a> <a href="reghelp.htm"><img src="previous.gif" alt="Previous" align=middle border=0 width=32 height=31></a> <a href="errhandl.htm"><img src="next.gif" alt="Next" align=middle border=0 width=32 height=31></a> </p>
|
|
<hr>
|
|
<!--Headerend--><p><a name="ErrorMessages"><font size=6><strong>Error Messages</strong></font></a></p>
|
|
<p align=left><!--Chaptoc--></p>
|
|
<blockquote>
|
|
<p><a href="errorhlp.htm#HTMLErrorPages">HTML Error Pages</a> <br>
|
|
<a href="errorhlp.htm#WindowsNTEventLogReporting">Windows NT Event Log Reporting</a> <br>
|
|
<a href="errorhlp.htm#SyntaxError">Query Syntax Errors</a> <br>
|
|
<a href="errorhlp.htm#.IdqFileErrors">.Idq File Errors</a> <br>
|
|
<a href="errorhlp.htm#.HtxFileErrors">.Htx File Errors<br>
|
|
</a><a href="errorhlp.htm#Hit-HighlightingErrors">Hit-Highlighting Errors</a><br>
|
|
<a href="errorhlp.htm#OtherErrors">Other Errors</a> <br>
|
|
<a href="errorhlp.htm#EventLogMessages">Event Log Messages</a> <br>
|
|
</p>
|
|
</blockquote>
|
|
<hr>
|
|
<!--ChaptocEnd--><p>Microsoft Index Server errors fall into several classes: query syntax errors, .idq syntax errors, .htx syntax errors,
|
|
out-of-resource errors, and other system errors. They are also reported through two mechanisms: HTML pages and the
|
|
Windows NT event log. The only errors a user is likely to see are query syntax errors, and even these can be minimized
|
|
through use of HTML forms.</p>
|
|
<hr>
|
|
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="HTMLErrorPages">HTML Error Pages</a></h1>
|
|
<p>The first three classes of error (query syntax, .idq syntax, and .htx syntax) always generate an HTML error page. The page
|
|
returned for each class of error is specified in the <a href="reghelp.htm#Language-SpecificRegistrySettings">Language-Specific Registry Settings</a> on the “Registry” page. Registry keys
|
|
are under the following path:</p>
|
|
<blockquote>
|
|
<pre>HKEY_LOCAL_MACHINE\SYSTEM
|
|
 \SYSTEM
|
|
  \CurrentControlSet
|
|
   \Control
|
|
    \ContentIndex
|
|
     \Language
|
|
      \<language></pre>
|
|
</blockquote>
|
|
<p>The keys are:</p>
|
|
<dl>
|
|
<dd><strong>ISAPIHTXErrorFile, ISAPIIDQErrofFile, </strong>and<strong> ISAPIRestrictionErrorFile</strong></dd>
|
|
<dd>Configure .htx errors, .idq (and .ida) errors and query syntax errors, respectively.</dd>
|
|
<dd> </dd>
|
|
<dd><strong>ISAPIDefaultErrorFile</strong></dd>
|
|
<dd>Reports other errors.</dd>
|
|
</dl>
|
|
<p>These pages are standard, completely customizable .htx pages. The variable <strong>CiErrorMessage</strong> contains a localized string
|
|
describing the specific error, and CiErrorNumber contains the error code. </p>
|
|
<hr>
|
|
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="WindowsNTEventLogReporting">Windows NT Event Log Reporting</a></h1>
|
|
<p>Index Server system errors are reported in the application event log under the Ci Filter Service category. System errors
|
|
reported here include page filtering (indexing) problems, out-of-resource conditions, index corruption, and so on. See <a href="#EventLogMessages">Event
|
|
Log Messages</a> later in this chapter for a complete list of messages.</p>
|
|
<hr>
|
|
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="SyntaxError">Query Syntax Errors</a></h1>
|
|
<p>These messages are returned by use of the CiErrorMessage variable, accessible from .htx error pages.</p>
|
|
<div align=left>
|
|
<table border=1 cellpadding=5 cellspacing=0 width=100%>
|
|
<tr><th align=left valign=bottom width=20%><font size=2>Message</font></th><th align=left valign=bottom width=80%><font size=2>Explanation</font></th></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting closing
|
|
parenthesis ‘)’.</font></td><td valign=top width=80%><font size=2>Occurs when parentheses are mismatched.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting closing square
|
|
bracket ‘]’.</font></td><td valign=top width=80%><font size=2>An opening square bracket was not followed by a closing square bracket. Usually the result of an ill-formed
|
|
weight.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting comma.</font></td><td valign=top width=80%><font size=2>Occurs when a reserved token or end-of-string occurs before the closing brace of a vector property. Example:
|
|
</font><font size=3><code>@VectorString = {A1, B@}</code></font><font size=2>.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting currency.</font></td><td valign=top width=80%><font size=2>A currency value was expected but not found. Occurs when a property of type DBTYPE_CY is fed incorrect
|
|
input. Correct format for currency is <tt>#.#</tt>.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting date.</font></td><td valign=top width=80%><font size=2>A date was expected but not found. Occurs when a property of type DBTYPE_DATE is fed incorrect input.
|
|
Allowed formats for dates are </font><font size=3><em><tt>yyyy/mm/dd</tt></em><em>, </em><em><tt>yyyy/mm/dd hh:mm:ss</tt></em></font><font size=2>, and relative dates </font><font size=3>(<tt>-#y</tt>, <tt>-#m</tt>, <tt>-#w</tt>,
|
|
<tt>-#d</tt>, <tt>-#h</tt>, <tt>-#n</tt>, <tt>-#s</tt>)</font><font size=2>.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting end of string.</font></td><td valign=top width=80%><font size=2>A complete restriction has been parsed, and there is still more input. Example:</font><font size=3><tt> </tt><code>(@size = 100)</code><tt> sample</tt></font><font size=2>.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting GUID.</font></td><td valign=top width=80%><font size=2>A GUID (Globally Unique Identifier) was expected but not found. Occurs when a property of DBTYPE_GUID is
|
|
fed incorrect input. Property format for a GUID is </font><font size=3><em><tt>XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX</tt></em></font><font size=2>.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting integer.</font></td><td valign=top width=80%><font size=2>An integer was expected but not found. Occurs when a property of an integer type (DBTYPE_I4, and so on) is
|
|
fed a nonnumeric value, or a nonnumeric vector weight is entered.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting phrase.</font></td><td valign=top width=80%><font size=2>A textual phrase was expected and not found. This error occurs in a variety of situations where the query parser
|
|
is expecting plain text and is given a special token instead.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting property name.</font></td><td valign=top width=80%><font size=2>Occurs when a correctly formed property name is not found after an @ sign.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting real number.</font></td><td valign=top width=80%><font size=2>A real number was expected but not found. Occurs when a property of a real type (DBTYPE_R4, and so on) if fed
|
|
a nonnumeric value.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Expecting regular
|
|
expression.</font></td><td valign=top width=80%><font size=2>Similar to <em>Expecting phrase</em>. Used when in regular-expression parsing mode.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Invalid literal.</font></td><td valign=top width=80%><font size=2>Occurs only when a query property is formatted poorly. Almost all conditions are covered by <em>Expecting Integer</em>,
|
|
<em>Expecting Date</em>, and so on.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>No such property.</font></td><td valign=top width=80%><font size=2>Property specified after @, #, or $ does not exist. It is not a default property and is not specified in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>]
|
|
section of the .idq file.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Not yet implemented.</font></td><td valign=top width=80%><font size=2>An unimplemented feature of Index Server.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Out of memory.</font></td><td valign=top width=80%><font size=2>The server ran out of memory processing the CiRestriction.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Regular expressions
|
|
require a property of type
|
|
string.</font></td><td valign=top width=80%><font size=2>A property of a nontextual type (DBTYPE_I4, DBTYPE_GUID, and so on) was selected for regular expression
|
|
mode. For example, </font><font size=3><code>#size 100*</code> </font><font size=2>will cause this error.</font></td></tr>
|
|
<tr><td valign=top><font size=2>The file <em><file></em> is on a
|
|
remote UNC share. .Idq,
|
|
.ida, and .htx files cannot
|
|
be placed on a remote
|
|
UNC share.</font></td><td valign=top><font size=2>An .idq, .ida, or .htx file was found on a remote UNC share. None of these files can be on a remote UNC share.</font></td></tr>
|
|
<tr><td valign=top width=20%><font size=2>Unsupported property
|
|
type.</font></td><td valign=top width=80%><font size=2>For future expansion. Will occur when a display-only property type is used in a query restriction.</font></td></tr>
|
|
<tr><td><font size=2>Weight must be between 0
|
|
and 1000.</font></td><td valign=top width=80%><font size=2>Occurs when a query term weight is outside the legal range of 0 to 1000.</font></td></tr>
|
|
</table>
|
|
</div>
|
|
<hr>
|
|
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name=".IdqFileErrors">.Idq File Errors</a></h1>
|
|
<p>These messages are returned by use of the <strong>CiErrorMessage</strong> variable, accessible from .htx error pages.</p>
|
|
<table border=1 cellpadding=5 cellspacing=0 width=100%>
|
|
<tr><th align=left valign=bottom width=40%><font size=2>Message</font></th><th align=left valign=bottom width=60%><font size=2>Explanation</font></th></tr>
|
|
<tr><td valign=top width=40%><font size=2>DBTYPE_BYREF must be used with DBTYPE_STR,
|
|
DBTYPE_WSTR, DBTYPE_GUID or DBTYPE_UI1
|
|
types on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>DBTYPE_BYREF must always be used in conjunction with an indirect type in the
|
|
[</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Duplicate property name on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The same property was defined twice in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting an equal sign ‘=’ on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>Incorrectly formatted entry in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section of .idq file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting closing parenthesis on line <<em>line</em>> in file
|
|
<<em>file</em>>.</font></td><td valign=top width=60%><font size=2>Opening parenthesis in [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section is not followed by closing parenthesis in
|
|
.idq file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting GUID on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>Incorrectly formatted entry in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section of .idq file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting integer on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>Incorrectly formatted entry in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section of .idq file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting property name on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>Incorrectly formatted entry in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section of .idq file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting property specifier on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>Invalid or missing property specifier in [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section. Property is named either by
|
|
PROPID (integer) or string.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting type specifier on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>Incorrectly formatted entry in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section of .idq file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Invalid GUID on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>A poorly formatted GUID was found on the specified line.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The .htx file specified could not be found in any virtual
|
|
or physical path.</font></td><td valign=top width=60%><font size=2>The file specified in the CiTemplate parameter could not be located.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Invalid property found in the ‘CiSort=’ specification in
|
|
file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>A property specified in the CiSort parameter is not a standard property and is not
|
|
listed in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section of the .idq file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An invalid sort order was specified on the ‘CiSort=’ line
|
|
in file <<em>file</em>>. Only [a] and [d] are supported.</font></td><td valign=top width=60%><font size=2>A sort-order specification following a property name in the CiSort parameter was
|
|
unrecognized. Only </font><font size=3><tt>[a]</tt></font><font size=2> (for ascending) and </font><font size=3><tt>[d]</tt></font><font size=2> (for descending) are allowed.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Invalid property found in the ‘CiColumns=’
|
|
specification in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>A property specified in the CiColumns parameter is not a standard property and is
|
|
not listed in the [</font><a href="idqhelp.htm#namesection"><font size=2>Names</font></a><font size=2>] section of the .idq file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Duplicate column, possibly by a column alias, found in
|
|
the ‘CiColumns=’ specification in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The same property was named more than once in the CiColumns line. It may have
|
|
been mentioned with different friendly names that refer to the same property.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>One or more output columns must be specified in the
|
|
.idq file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The CiColumns parameter is missing or empty. At least one output column must be
|
|
specified for the query.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Read error in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>I/O error occured reading the file. Generally caused by hardware failure.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>A restriction must be specified in the .idq file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The CiRestriction parameter is missing or empty. Every query must have a
|
|
restriction. A restriction such as<tt> </tt></font><font size=3><tt>#vpath *.*</tt></font><font size=2> will match all pages.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>A scope must be specified in the .idq file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The CiScope parameter is missing or empty. Every query must have a scope. The
|
|
scope / will match every page.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Failed to set property in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>A resource failure. Usually out-of-memory.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>A template file must be specified in the .idq file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The CiTemplate parameter is missing or empty. Every query must have a template
|
|
(.htx) file.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The template file cannot be found in the location
|
|
specified by ‘CiTemplate=’ in file <<em>file</em>></font></td><td valign=top width=60%><font size=2>An attempt to open a .htx file at the location specified by the CiTemplate parameter
|
|
failed. The path may be invalid, it may specify a directory, or it may resolve to NULL
|
|
after parameter replacement. </font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The catalog directory cannot be found in the location
|
|
specified by ‘CiCatalog=’ in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The catalog location specified by the CiCatalog paraemeter did not contain a valid
|
|
content index catalog.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The IDQ file <<em>file</em>> contains a duplicate entry on line
|
|
<<em>line</em>>.</font></td><td valign=top width=60%><font size=2>A parameter in the [</font><a href="idqhelp.htm#qrysection"><font size=2>query</font></a><font size=2>] section of the .idq file was given more than once.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting TRUE or FALSE in .idq file <<em>file</em>> on line
|
|
‘CiForceUseCi=’</font></td><td valign=top width=60%><font size=2>The CiForceUseCi parameter has a value other than </font><font size=3><tt>TRUE</tt></font><font size=2> or </font><font size=3><tt>FALSE</tt></font><font size=2>.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting SHALLOW or DEEP in .idq file <<em>file</em>> on line
|
|
‘CiFlags=’.</font></td><td valign=top width=60%><font size=2>The CiFlags parameter has a value other than </font><font size=3><tt>SHALLOW</tt></font><font size=2> or </font><font size=3><tt>DEEP</tt></font><font size=2>.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An invalid locale was specified on the ‘CiLocale=’ line
|
|
in .idq file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The locale ID specified by the CiLocale parameter was not recognized as a valid
|
|
locale ID.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Unrecognized type on line <<em>line</em>> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>Type specifed is not one of the valid </font><a href="idqhelp.htm#namesection"><font size=2>types</font></a><font size=2> (DBTYPE_I4, DBTYPE_GUID, and so
|
|
on).</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>DBTYPE_VECTOR or DBTYPE_BYREF used alone on
|
|
line <i> in file <<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The VECTOR and BYREF property modifiers must always be used with a type.
|
|
Example: DBTYPE_I4 | DBTYPE_VECTOR</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>You must specify ‘MaxRecordsPerPage’ in the .idq file
|
|
<<em>file</em>>.</font></td><td valign=top width=60%><font size=2>The CiMaxRecordsPerPage parameter is missing or empty. Every query must specify
|
|
the number of records per page.</font></td></tr>
|
|
</table>
|
|
<hr>
|
|
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name=".HtxFileErrors">.Htx File Errors</a></h1>
|
|
<p>These messages are returned by use of the <strong>CiErrorMessage</strong> variable, accessible from .htx error pages.</p>
|
|
<div align=left>
|
|
<table border=1 cellpadding=5 cellspacing=0 width=100%>
|
|
<tr><th align=left valign=bottom width=40%><font size=2>Message</font></th><th align=left valign=bottom width=60%><font size=2>Explanation</font></th></tr>
|
|
<tr><td valign=top width=40%><font size=2>A <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>BeginDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> section was found on line
|
|
<<em>number></em> in the .htx file <em><file></em>, without a matching
|
|
<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>EndDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> section.</font></td><td valign=top width=60%><font size=2>The <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>BeginDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag must be followed by a matching <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --><!--steve-->
|
|
</font><font size=3><code>EndDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>else<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> or <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>endif<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> was found
|
|
without a matching <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>if...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2>.</font></td><td valign=top width=60%><font size=2>An <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>else<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> or <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>endif<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag was found without a matching <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>if
|
|
<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>EndDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> section was found on line
|
|
<<em>number></em> in the .htx file <em><file></em> before the <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan -->
|
|
</font><font size=3><code>BeginDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> section.</font></td><td valign=top width=60%><font size=2>The <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>BeginDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag must precede the <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>EndDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>EndDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> section was found on line
|
|
<<em>number></em> in the .htx file <em><file></em>, without a matching
|
|
<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>BeginDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> section.</font></td><td valign=top width=60%><font size=2>The <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>EndDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag must be preceded by a matching <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan -->
|
|
</font><font size=3><code>BeginDetail<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>if<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> was found without a matching <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan -->
|
|
</font><font size=3><code>else<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> or</font> <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --><font size=3><code>endif<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2>.</font></td><td valign=top width=60%><font size=2>The <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>if...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag must be followed by an <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>endif<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag, with an
|
|
optional <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>else<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag in between.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An opening bracket “{” was found without a matching
|
|
closing bracket.</font></td><td valign=top width=60%><font size=2>A vector in an <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>if...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag is missing the closing brace.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An opening quote (“) was found without a matching
|
|
closing quote.</font></td><td valign=top width=60%><font size=2>A quoted phrase in an <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>if...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag is missing the closing quote.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Constants used in IsTypeEq conditions must be
|
|
unsigned integers, not floats, GUIDs, and so on.</font></td><td valign=top width=60%><font size=2>One or more of the constants in the IsTypeEq condition is a float, GUID, and so on,
|
|
but should be an unsigned integer.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Expecting an operator in <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>if<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> statement.</font></td><td valign=top width=60%><font size=2>The operator in an <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>if...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag was missing. ‘If’ must be followed by one of
|
|
EQ, NE, LT, LE, GT, GE, contains, or IsTypeEq.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>One of the values in a IsTypeEq condition must be a
|
|
variable. You used two constants.</font></td><td valign=top width=60%><font size=2>One of the values in the IsTypeEq condition is not a variable.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The .htx file <em><file></em> contains an ill-formed include
|
|
statement on line <<em>number></em>.</font></td><td valign=top width=60%><font size=2>Usually caused by a <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>include...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag without the closing <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan -->.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The .htx file specified could not be found in any virtual
|
|
or physical path.</font></td><td valign=top width=60%><font size=2>The .htx file specified in an <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>include...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag could not be located.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The .htx file <em><file></em> uses too many includes on line
|
|
<<em>number></em>.</font></td><td valign=top width=60%><font size=2>A maximum of 32 files can be included by use of the <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>include...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The include file name is invalid in file <em><file></em> on line
|
|
<<em>number></em>.</font></td><td valign=top width=60%><font size=2>Usually caused by a <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code><%</code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></font><font size=3><code>include...<!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan --></code></font><font size=2> tag missing the closing <!--VERMEER BOT=HTMLMarkup StartSpan --><font size=3><code>%></code></font><!--VERMEER BOT=HTMLMarkup EndSpan -->.</font></td></tr>
|
|
</table>
|
|
</div>
|
|
<hr>
|
|
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="Hit-HighlightingErrors">Hit-Highlighting Errors</a></h1>
|
|
<p>The following messages are written to the Windows NT application event log.</p>
|
|
<div align=left>
|
|
<table border=1 cellpadding=5 cellspacing=0 width=100%>
|
|
<tr><th align=left valign=bottom width=40%><font size=2>Message</font></th><th align=left valign=bottom width=60%><font size=2>Explanation</font></th></tr>
|
|
<tr><td valign=top width=40%><font size=2>The path specified is incorrect.</font></td><td valign=top width=60%><font size=2>Webhits.exe failed to get one of the CGI variables PATH_TRANSLATED or
|
|
PATH_INFO.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The query issued is invalid.</font></td><td valign=top width=60%><font size=2>Webhits.exe failed to get the CGI variable QUERY_STRING, or CiRestriction is not
|
|
specified in QUERY_STRING.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An invalid variable name was found in
|
|
QUERY_STRING.</font></td><td valign=top width=60%><font size=2>While parsing QUERY_STRING, Webhits.exe encountered a parameter whose name
|
|
it did not recognize.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The format of QUERY_STRING is invalid.</font></td><td valign=top width=60%><font size=2>The specification of Webhits parameters in QUERY_STRING does not conform to
|
|
the format:</font><pre><font size=3>[ws][Name of Parameter][ws][=][ws][escaped value of parameter][ws</font><font size=2>]</font><font size=3>[&] </font></pre>
|
|
<p><font size=2>where this is repeated for each command-line parameter, and [ws] (whitespace) is
|
|
optional. </font> </p>
|
|
</td></tr>
|
|
<tr><td valign=top width=40%><font size=2>No such property.</font></td><td valign=top width=60%><font size=2>The query involves a custom property, but does not specify an .idq file with a
|
|
[Names] section describing this property, or the property name was not found in the
|
|
[Names] section of the specified .idq file.</font></td></tr>
|
|
</table>
|
|
</div>
|
|
<hr>
|
|
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="OtherErrors">Other Errors</a></h1>
|
|
<table border=1 cellpadding=5 cellspacing=0 width=100%>
|
|
<tr><th align=left valign=bottom width=40%><font size=2>Message</font></th><th align=left valign=bottom width=60%><font size=2>Explanation</font></th></tr>
|
|
<tr><td valign=top width=40%><font size=2>The query failed because the Web server is busy
|
|
processing other requests.</font></td><td valign=top width=60%><font size=2>There are too many queries waiting to be processed. This query has been rejected.
|
|
The user can try again later when the server is less busy.</font></td></tr>
|
|
</table>
|
|
<hr>
|
|
<h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="EventLogMessages">Event Log Messages</a></h1>
|
|
<p>The following messages are written to the Windows NT application event log.</p>
|
|
<div align=left>
|
|
<table border=1 cellpadding=5 cellspacing=0 width=100%>
|
|
<tr><th align=left valign=bottom width=40%><font size=2>Message</font></th><th align=left valign=bottom width=60%><font size=2>Explanation</font></th></tr>
|
|
<tr><td valign=top width=40%><font size=2>CI has started on <<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>An informational message logged when Index Server is started successfully.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>A content scan has completed on <<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>A content scan of the catalog has been completed successfully.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>A full content scan has started on <<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>A complete rescan of the catalog has been initiated.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>An error has been detected on <<em>catalog</em>> that requires
|
|
a full content scan.</font></td><td valign=top width=60%><font size=2>The catalog lost a change notification, usually due to lack of resources (disk space)
|
|
or hardware failure. The complete scope of the catalog will be </font><a href="scanhlp.htm"><font size=2>scanned</font></a><font size=2>, and all
|
|
documents will be refiltered. This action is deferred until a suitable time.</font></td></tr>
|
|
<tr><td valign=top width=40%><a name="UnknownExtension"><font size=2><em>Class for extension</em></font></a><font size=2><em> </em><<em>extension</em>> unknown. Sample file:
|
|
<<em>file</em>></font></td><td valign=top width=60%><font size=2>This is a warning that files with the specified extension are being filtered with the
|
|
default (text) filter. This can lead to addition of unnecessary data in the index.
|
|
Consider turning off filtering for this extension. The full physical path of a
|
|
representative file is included in the message. </font><p><font size=2>Generation of this message can be disabled by turning on a special flag in
|
|
ContentIndex registry. See the </font><a href="reghelp.htm"><font size=2>Registry</font></a><font size=2> page for details. </font></p>
|
|
</td></tr>
|
|
<tr><td valign=top width=40%><a name="CorruptCatalog"><font size=2><em>Cleaning</em></font></a><font size=2><em> </em>up corrupted content index metadata on
|
|
<<em>catalog</em>>. Index will be automatically restored by
|
|
refiltering all documents.</font></td><td valign=top width=60%><font size=2>A catastrophic data corruption error was detected on the specified catalog. The
|
|
catalog will be rebuilt. This is usually caused by hardware failure, but can also occur
|
|
in rare circumstances because of abrupt shutdown or power failure. Recovery will
|
|
occur automatically.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Content index on <<em>catalog</em>> could not be initialized.
|
|
Error <<em>number</em>>.</font></td><td valign=top width=60%><font size=2>Unknown, possibly catastrophic error. Please report the error number to product
|
|
support. To recover, delete all files under <<em>catalog</em>> and re-index.</font></td></tr>
|
|
<tr><td valign=top width=40%><a name="CorruptRestart"><font size=2><em>Content index</em></font></a><font size=2><em> </em>on <<em>catalog</em>> is corrupted. Please shut
|
|
down and restart Web server.</font></td><td valign=top width=60%><font size=2>A catastrophic data corruption error was detected on the specified catalog. The
|
|
catalog will be rebuilt. This is usually caused by hardware failure, but can also occur
|
|
in rare circumstances because of abrupt shutdown or power failure. You must shut
|
|
down and restart the Web server for recovery to occur.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Error <<em>number</em>> detected in content index on
|
|
<<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>Unknown, possibly catastrophic error. Please report error number to product
|
|
support. To recover, delete all files under <<em>catalog</em>> and start over.</font></td></tr>
|
|
<tr><td valign=top width=40%><a name="MasterMergeEvents"><font size=2><em>Master merge has been paused on </em></font></a><font size=2><<em>catalog</em>>. It will be
|
|
rescheduled later.</font></td><td valign=top width=60%><font size=2>A </font><a href=" indexhlp.htm#MasterMerge "><font size=2>master merge</font></a><font size=2> has been temporarily halted on the specified catalog. Often occurs
|
|
when a merge runs out of system resources (disk space, memory, and so on).</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Master merge has completed on <<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>A </font><a href=" indexhlp.htm#MasterMerge "><font size=2>master merge</font></a><font size=2> has been completed on the specified catalog. This is an
|
|
informational message.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Master merge cannot be started on <<em>catalog</em>> due to
|
|
error <<em>number</em>>.</font></td><td valign=top width=60%><font size=2>A </font><a href="indexhlp.htm#MasterMerge"><font size=2>master merge</font></a><font size=2> cannot be started on the specified catalog. The error code gives the
|
|
reason.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Master merge cannot be restarted on <<em>catalog</em>> due to
|
|
error <<em>number</em>>.</font></td><td valign=top width=60%><font size=2>A </font><a href="indexhlp.htm#MasterMerge"><font size=2>master merge</font></a><font size=2> cannot be restarted on the specified catalog. The error code gives
|
|
the reason. </font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Master merge has restarted on <<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>A paused </font><a href=" indexhlp.htm#MasterMerge "><font size=2>master merge</font></a><font size=2> has been restarted.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Master merge has started on <<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>A </font><a href=" indexhlp.htm#MasterMerge "><font size=2>master merge</font></a><font size=2> has been initiated on the specified catalog. This is an informational
|
|
message.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Master merge was started on <<em>catalog</em>> because more
|
|
than <<em>number</em>> documents have changed since the last
|
|
master merge.</font></td><td valign=top width=60%><font size=2>A </font><a href=" indexhlp.htm#MasterMerge e"><font size=2>master merge</font></a><font size=2> was started because the number of documents changed since the
|
|
last master merge exceeded the maximum </font><a href="reghelp.htm#MaxFreshCount"><font size=2>threshold</font></a><font size=2>.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Master merge was started on <<em>catalog</em>> because the
|
|
amount of remaining disk space was less than
|
|
<<em>number</em>>%.</font></td><td valign=top width=60%><font size=2>A </font><a href=" indexhlp.htm#MasterMerge "><font size=2>master merge</font></a><font size=2> was started because the amount of free space on the catalog volume
|
|
dropped below a minimum </font><a href="reghelp.htm#MaxShadowFreeForceMerge"><font size=2>threshold</font></a><font size=2>. The total free disk space should be increased
|
|
after the master merge completes.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Master merge was started on <<em>catalog</em>> because the
|
|
size of the shadow indexes is more than <<em>number</em>>%
|
|
the disk.</font></td><td valign=top width=60%><font size=2>A </font><a href=" indexhlp.htm#MasterMerge e"><font size=2>master merge</font></a><font size=2> was started because the amount of data in </font><a href="indexhlp.htm#merge"><font size=2>shadow indexes</font></a><font size=2>
|
|
exceeded the maximum </font><a href="reghelp.htm#MaxShadowIndexSize"><font size=2>threshold</font></a><font size=2>.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>Notifications are not enabled on <<em>pathname</em>> because
|
|
this is a DFS aware share. This scope will be
|
|
periodically scanned.</font></td><td valign=top width=60%><font size=2>If a virtual root points to a distributed file system (DFS) share, notifications are
|
|
disabled for the entire DFS share because DFS does not support notifications. </font></td></tr>
|
|
<tr><td valign=top width=40%><a name="UnfilteredEmbeddings"><font size=2><em>One or more</em></font></a><font size=2><em> </em>embeddings in file <<em>file</em>> could not be
|
|
filtered.</font></td><td valign=top width=60%><font size=2>The specified file was filtered correctly, but several of the embedded objects could
|
|
not be filtered. This is usually caused by embedded objects without a registered
|
|
filter. Text within unfiltered embedded objects is not searchable. Generation of this
|
|
message can be disabled by turning on a special flag in ContentIndex registry. See
|
|
</font><a href="reghelp.htm#EventLogFlagsMasks"><font size=2>Registry parameters</font></a><font size=2> for details.</font></td></tr>
|
|
<tr><td valign=top width=40%><a name="RecoveryStart"><font size=2><em>Recovery</em></font></a><font size=2><em> </em>is starting on PropertyStore in catalog
|
|
<<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>Corruption was detected in the </font><a href="indexhlp.htm#PropertyCache"><font size=2>property cache</font></a><font size=2>. Recovery is starting on the property
|
|
cache. This can take a long time depending upon the size of the property cache.</font></td></tr>
|
|
<tr><td valign=top width=40%><a name="PropStoreInconsistency"><font size=2><em>PropertyStore</em></font></a><font size=2><em> </em>inconsistency detected in catalog
|
|
<<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>Corruption was detected in the </font><a href="indexhlp.htm#PropertyCache"><font size=2>property cache</font></a><font size=2>. Recovery is automatically
|
|
scheduled. Usually the result of hardware failure or abrupt shutdown.</font></td></tr>
|
|
<tr><td valign=top width=40%><a name="RecoveryEnd"><font size=2><em>Recovery</em></font></a><font size=2><em> </em>was performed successfully on PropertyStore
|
|
in catalog <<em>catalog</em>>.</font></td><td valign=top width=60%><font size=2>Corruption was detected in the </font><a href="indexhlp.htm#PropertyCache"><font size=2>property cache</font></a><font size=2>. The errata has been fixed. Usually
|
|
the result of hardware failure or abrupt shutdown.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2><<em>number</em>> inconsistencies were detected in
|
|
PropertyStore during recovery of catalog <<em>catalog</em>><em>.</em></font></td><td valign=top width=60%><font size=2>Corruption was detected in the </font><a href="indexhlp.htm#PropertyCache"><font size=2>property cache</font></a><font size=2> during startup. Recovery is
|
|
automatically scheduled. Usually the result of hardware failure or abrupt shutdown.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The CI filter daemon has prematurely stopped and will
|
|
be and subsequently restarted.</font></td><td valign=top width=60%><font size=2>The filter daemon (Cidaemon.exe) stoped unexpectedly. It will be automatically
|
|
restarted. This can be caused by poorly written filters, or experimentation with the
|
|
Windows NT Task Manager.</font></td></tr>
|
|
<tr><td valign=top width=40%><a name="MaxRetries"><font size=2>The content</font></a><font size=2><em> </em>index could not filter file <<em>file</em>>. The filter
|
|
operation was retried <<em>number</em>> times without success.</font></td><td valign=top width=60%><font size=2>The specified document failed to successfully filter <<em>number</em>> times. This usually
|
|
indicates a corrupted document or corrupted properties. In rare cases, filtering may
|
|
fail because the document was in use for a long period of time.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The content index filter for file “<<em>file</em>>” generated
|
|
content data more than <<em>size</em>> times the file’s size.</font></td><td valign=top width=60%><font size=2>Filtering of the specified document generated more than the </font><a href="reghelp.htm#MaxFilesizeMultiplier"><font size=2>allowed maximum</font></a><font size=2>
|
|
amount of output. This is usually caused by a poorly written filter, a corrupted
|
|
document, or both.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The content index filter stopped while filtering “<<em>file</em>>”.
|
|
The CI daemon was restarted. Please check the validity
|
|
of the filter for objects of this class.</font></td><td valign=top width=60%><font size=2>Filtering of the specified document was started, but did not finish before the </font><a href="reghelp.htm#DaemonResponseTimeout"><font size=2>timout
|
|
period</font></a><font size=2> expired. This is usually caused by a poorly written filter, a corrupted
|
|
document, or both.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The filter service could not run since file <<em>file</em>> could
|
|
not be found on your system.</font></td><td valign=top width=60%><font size=2>An executable or DLL required for filtering cannot be found, usually because
|
|
Cidaemon.exe is not on the path.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>The path <<em>pathname</em>> is too long for content index.</font></td><td valign=top width=60%><font size=2>The content index detected a path that was longer than the maximum number of
|
|
characters allowed for a pathname as determined by the constant MAX_PATH (260
|
|
characters). As a result, no documents from that path will be returned or indexed.</font></td></tr>
|
|
<tr><td valign=top width=40%><a name="LowDiskEvent"><font size=2><em>Very low disk</em></font></a><font size=2><em> </em>space was detected on drive <<em>drive</em>>.
|
|
Please free up at least <<em>number</em>> MB of space for
|
|
content index to continue.</font></td><td valign=top width=60%><font size=2>Free space has fallen below the minimum </font><a href="reghelp.htm#MinDiskFreeForceMerge"><font size=2>threshold</font></a><font size=2> required for successful merge.
|
|
This is just a warning, but no merges will be initiated until space is freed up. Filtering
|
|
will also stop.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>File change notifications are turned off for scope
|
|
“<<em>scope</em>>” because of error <<em>number</em>>. This scope will
|
|
be periodically rescanned.</font></td><td valign=top width=60%><font size=2>An error prevented reestablishing automatic change notifications for the specified
|
|
directory scope. To determine documents that changed in the scope, periodic
|
|
</font><a href="scanhlp.htm#IncrementalScan"><font size=2><em>incremental scans</em></font></a><font size=2> will be done by Index Server. The </font><a href="reghelp.htm#ForcedNetPathScanInterval"><font size=2>rescan interval</font></a><font size=2> is specified in
|
|
the registry.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2>File change notificationsfor scope “<<em>scope</em>>” are not
|
|
enabled because of error <<em>number</em>>. This scope will be
|
|
periodically rescanned. </font></td><td valign=top width=60%><font size=2>An error prevented establishment of automatic change notifications for the specified
|
|
directory scope. This usually happens with virtual roots that point to remote shares
|
|
on file servers that do not support automatic change notifications. To determine
|
|
which documents changed in the scope, periodic </font><a href="scanhlp.htm#IncrementalScan"><font size=2><em>incremental scans</em></font></a><font size=2> will be done by
|
|
Index Server. The </font><a href="reghelp.htm#ForcedNetPathScanInterval"><font size=2>rescan interval</font></a><font size=2> is specified in the registry.</font></td></tr>
|
|
<tr><td valign=top width=40%><font size=2><<em>Process-Name</em>> failed to logon <<em>UserId</em>> because of
|
|
error <<em>number</em>>.</font></td><td valign=top width=60%><font size=2>The specified process (Index Server SearchEngine or CiDaemon) failed to log on the
|
|
specified user because of an error. The remote shares for which the UserId is used
|
|
will not be filtered correctly. This can happen if either the password is wrong or the
|
|
validity of the password could not be verified due to network errors.</font></td></tr>
|
|
<tr><td valign=top><font size=2>Please check your system time. It might be set to an
|
|
invalid value.</font></td><td valign=top><font size=2>This event is generated when the system time is invalid, for example, when set to a
|
|
date before January 1, 1980. When the system time is invalid, the date may appear as
|
|
2096.</font></td></tr>
|
|
</table>
|
|
</div>
|
|
<!--Footerbegin--><hr>
|
|
<p align=center><a href="default.htm#Top"><img src="toc.gif" alt=" Contents" align=middle border=0 width=89 height=31></a> <a href="reghelp.htm"><img src="previous.gif" alt="Previous" align=middle border=0 width=32 height=31></a> <a href="#TOP"><img src="up_end.gif" alt="To Top" align=middle border=0 width=32 height=31></a> <a href="errhandl.htm"><img src="next.gif" alt="Next" align=middle border=0 width=32 height=31></a> </p>
|
|
<hr>
|
|
<p align=center><em>© 1996 by Microsoft Corporation. All rights reserved.<!--Footerend--></em></p>
|
|
</body>
|
|
|
|
</html>
|