Source code of Windows XP (NT5)
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head><title>Microsoft Index Server Guide: Error Detection and Recovery</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="errorhlp.htm"><img src="previous.gif" alt="Previous" align=middle border=0 width=32 height=31></a> <a href="glossary.htm"><img src="next.gif" alt="Next" align=middle border=0 width=32 height=31></a> </p><hr><!--Headerend--><p><a name="ErrorDetectionandRecovery"><font size=6><strong>Error Detection and Recovery</strong></font></a></p><p align=left><!--Chaptoc--></p><blockquote><p><a href="errhandl.htm#LostFileNotifications">Lost File Notifications</a> <br><a href="errhandl.htm#DroppedNetworkConnections">Dropped Network Connections</a> <br><a href="errhandl.htm#CorruptedFilesandFaultyFilter DLLs">Corrupted Files and Faulty Filter DLLs</a> <br><a href="errhandl.htm#Disk-FullCondition">Disk-Full Condition</a> <br><a href="errhandl.htm#CorruptedPropertyCache">Corrupted Property Cache</a> <br><a href="errhandl.htm#DataCorruptionandInternalInconsistencies">Data Corruption and Internal Inconsistencies</a> <br></p></blockquote><hr><!--ChaptocEnd--><p>Several kinds of errors are automatically detected by Microsoft Index Server and recovered. Other than hardware failures and situations where the catalog drive runs out of disk space, no manual intervention is needed.</p><hr><h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="LostFileNotifications">Lost File Notifications</a></h1><p>During normal operation of Index Server, all changes to the documents in the <a href="glossary.htm#IndexedDirectory"><em>indexed directories</em></a> are automatically tracked if the indexed directories are on computers running Windows NT. If the rate of file modification is very high, it is possible to lose some notifications due to buffer overflows. In that case, Index Server automatically schedules an <a href="scanhlp.htm#IncrementalScan">incremental scan</a> on the scope that lost notifications. No manual intervention is needed.</p><hr><h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="DroppedNetworkConnections">Dropped Network Connections</a></h1><p>If a virtual root is pointing to a remote share and the connection to the remote share is lost, it is called a <em>disconnected path</em>. Index Server detects this situation and <a href="reghelp.htm#ForcedNetPathScanInterval">periodically</a> scans the remote shares to see if the connection is active. No manual intervention is needed.</p><hr><h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="CorruptedFilesandFaultyFilter DLLs">Corrupted Files and Faulty Filter DLLs</a></h1><p>If corrupted files are detected by the <a href="filtrhlp.htm#CiDaemon">CiDaemon</a> process, the files will be marked as <em>unfiltered</em>. You can get a list of unfiltered<em> </em>files by issuing an <a href="adminhlp.htm#UnfilteredFiles">adminstrative command</a> to list the unfiltered files. There might also be a problem with the <a href="filtrhlp.htm#FilterDLLs">filter DLL</a> used to filter those files. If a particular type of file is consistently not being filtered, you should contact the vendor of that filter DLL.</p><hr><h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="Disk-FullCondition">Disk-Full Condition</a></h1><p>If the <a href="glossary.htm#CatalogDrive">catalog drive</a> starts getting full, indexing is temporarily paused. <a href="filtrhlp.htm">Filtering</a> cannot continue unless disk space is freed up on the catalog drive. A message is written to the <a href="errorhlp.htm#LowDiskEvent">event log</a> when the disk starts getting full. Administrators should monitor the event log for these messages and take corrective action. To avoid a disk-full condition, follow the <a href="install.htm#RecommendedConfiguration">configuration guidelines</a> given in the <a href="install.htm">installation page</a>.</p><hr><h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="CorruptedPropertyCache">Corrupted Property Cache</a></h1><p>If Index Server is shut down abruptly or a corruption is detected during normal operation, the <a href="indexhlp.htm#PropertyCache">property cache</a> will be marked as corrupted. A recovery action will be performed on the property cache when Index Server is restarted. One <a href="errorhlp.htm#RecoveryStart">event log message</a> is written at the beginning of the recovery action and another at the <a href="errorhlp.htm#RecoveryEnd">end of recovery</a>. During recovery, queries will be allowed but <a href="filtrhlp.htm">filtering</a> will not start until the recovery is completed. No manual intervention is needed.</p><hr><h1><a href="#TOP"><img src="up.gif" alt="To Top" align=middle border=0 width=14 height=11></a><a name="DataCorruptionandInternalInconsistencies">Data Corruption and Internal Inconsistencies</a></h1><p>As a result of a power failure or other catastophic event, the index data may become corrupted beyond repair. In that situation, existing Index Server data is deleted and all the documents are refiltered. If corruption is detected during Index Server startup, the refiltering will happen automatically. However, if corruption is detected during normal operation, an <a href="errorhlp.htm#CorruptRestart">event log message</a> is written and no further queries are allowed. When this event is written to the event log, administrators should <a href="install.htm#StopAndStart">stop and restart Index Server</a>. </p><p>When automatic recovery is performed by Index Server, an <a href="errorhlp.htm#CorruptCatalog">event</a> is written to the event log. If the catalog specified in the event log message had default settings and all the virtual roots were indexed, no action is required.</p><p><strong>Note</strong>   If some virtual roots were marked not to be indexed, administrators have to explicitly disable indexing on those virtual roots again. Use the <a href="/scripts/srchadm/admin.idq?">virtual root configuration</a> option from the <a href="/srchadm/admin.htm">administrative Web page.</a></p><!--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="errorhlp.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="glossary.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.</em> <!--Footerend--></p></body>
</html>
|
