FIX: Full-Text Rows Missing After Crawl Due to Full Disk

Article translations Article translations
Article ID: 290592 - View products that this article applies to.
This article was previously published under Q290592
BUG #: 351081 (SHILOH_bugs)
Expand all | Collapse all


If you run out of disk space for the transaction log while populating a Full-Text catalog, you may end up missing rows in the Full-Text catalog. You can see the following error message by using the Gthrlog.vbs scripting tool located in the C:\Program Files\Common Files\System\MSSearch\Bin folder:
00-11-12 1:05:06 AM MSSQL75://SQLServer/75d7831f/000F0F7B Add Error fetching URL, (80041818 - A document update was rejected because updates were disabled.)


If you run out of disk space during the crawl (population), the updates to MSSearch are disabled or paused. The crawl is entirely notification based and if the notifications are accepted by MSSearch, the data processed eventually whether the catalog is paused or not. However, because SQL Server does not retry the failed notifications later, as a result of the full disk issue, the gatherer does not resume and you may lose rows.


To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack


Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.


Article ID: 290592 - Last Review: November 6, 2003 - Revision: 3.2
  • Microsoft SQL Server 2000 Standard Edition
kbbug kbfix kbsqlserv2000sp1fix KB290592

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from