The information in this article applies to:
SYMPTOMSUsing the SQL sample that ships with Index Server 2.0 in the Windows NT 4.0 Option Pack, the browser may show formatting problems with some file types in the results of a query. CAUSEIf the display results of the query using Sqlqhit.asp include files with extensions that are unrecognized, Index Server uses the default text filter. If this file contains HTML, the HTML escape characters are not properly recognized by the scripting code in the Sqlqhit.asp file. So, the browser becomes confused and treats these as if they are HTML and this creates formatting problems. RESOLUTION
You can fix this problem by adding three lines of code close to the end of
the Sqlqhit.asp file.
Sample Code
STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATIONSteps to Reproduce BehaviorUsing the SQL sample (that uses the Sqlqhit.asp file), search for a keyword that exists in a file that also contains HTML but the file has a different file extension. One such example is the Ado15.hhk file.For example, you can see this problem occur when you use the SQL sample and run the following query: Select * from fileinfo where CONTAINS('RollbackTrans')>0The bottom row is not formed correctly and the following message displays: This is a result of the browser trying to interpret the results as part of its logic rather than just displaying the results. REFERENCESFor more information, refer to the Index Server documentation in the Windows NT Option Pack documentation. Additional query words: kbDSupport kbIndexServer kbdse
Keywords : |
Last Reviewed: November 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |