Article ID: 272763 - Last Review: February 21, 2007 - Revision: 3.3 Index Server Timeout Is Not Reported When You Execute a Query over Multiple CatalogsThis article was previously published under Q272763 SYMPTOMS
If a query over multiple catalogs exceeds the time limit for execution
(the MaxQueryExecution Time registry parameter), Indexing Service does not report that the query timed out before it finished. Because of this, the client program cannot detect that the results returned by the query are incomplete.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910
(http://support.microsoft.com/kb/260910/EN-US/
)
How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:Date Time Version Size File name --------------------------------------------------------- 09/13/2000 01:52a 5.0.2195.2195 1,416,464 Query.dll STATUSMicrosoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 2. MORE INFORMATIONFor additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below
to view the article in the Microsoft Knowledge Base:
249149
(http://support.microsoft.com/kb/249149/EN-US/
)
Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
After you install this hotfix, the "Rowset Query Status" property now returns the STAT_TIME_LIMIT_EXCEEDED (256) flag when the query has timed out.The following Microsoft Visual Basic sample illustrates how to handle the time limit condition by using ADO with the OLE DB Provider for Index Server (MSIDXS): | Article Translations
|
Back to the top
