Freigeben über

.Idq File Errors

  • Artikel

Note

Indexing Service is no longer supported as of Windows XP and is unavailable for use as of Windows 8. Instead, use Windows Search for client side search and Microsoft Search Server Express for server side search.

 

These messages are returned by use of the CiErrorMessage variable, accessible from .htx error pages.

Message Explanation
The catalog directory cannot be found in the location specified by 'CiCatalog=' in file <file>. The catalog location specified by the CiCatalog parameter did not contain a valid content index catalog.
DBTYPE_BYREF must be used with DBTYPE_STR, DBTYPE_WSTR, DBTYPE_GUID or DBTYPE_UI1 types. DBTYPE_BYREF must always be used in conjunction with an indirect type in the [Names] section.
DBTYPE_VECTOR or DBTYPE_BYREF used alone. The VECTOR and BYREF property modifiers must always be used with a type. Example: DBTYPE_I4 | DBTYPE_VECTOR
Duplicate column, possibly by a column alias, found in the 'CiColumns=' specification in file <file>. The same property was named more than once in the CiColumns variable line. It may have been mentioned with different friendly names that refer to the same property.
Duplicate property name. The same property was defined twice in the [Names] section.
Expecting closing parenthesis. Opening parenthesis in [Names] section is not followed by closing parenthesis in .idq file.
Expecting GUID. Incorrectly formatted entry in the [Names] section of .idq file.
Expecting integer. Incorrectly formatted entry in the [Names] section of .idq file.
Expecting property name. Incorrectly formatted entry in the [Names] section of .idq file.
Expecting property specifier. Invalid or missing property specifier in [Names] section. Property is named either by PROPID (integer) or string.
Expecting SHALLOW or DEEP in .idq file <file> on line 'CiFlags='. The CiFlags parameter has a value other than a value of SHALLOW or DEEP.
Expecting TRUE or FALSE in .idq file <file> on line 'CiForceUseCi=' The CiForceUseCi parameter has a value other than TRUE or FALSE.
Expecting type specifier. Incorrectly formatted entry in the [Names] section of .idq file.
Failed to set property name. A resource failure. Usually out of memory.
The file <file> is on a network share. The .idq, .ida, and .htx files cannot be placed on a network share. You must put these files into a virtual root on the local computer.
The .htx file specified could not be found in any virtual or physical path. The file specified in the CiTemplate parameter could not be located.
The .idq file <file> contains a duplicate entry on line <line>. A parameter in the [query] section of the .idq file was given more than once.
The .idq file <file> could not be found. Check the path to the .idq file and then make sure the .idq file is in that path.
An invalid 'CiScope=' or 'CiCatalog=' was specified in file <file>. The .idq file cannot contain invalid parameters. Correct the condition and try again.
Invalid GUID. A poorly formatted GUID was found in the [Names] section.
An invalid locale identifier (LCID) was specified on the 'CiLocale=' line in .idq file <file>. The LCID specified by the CiLocale parameter was not recognized as valid.
Invalid property found in the 'CiColumns=' specification in file <file>. A property specified in the CiColumns parameter is not a standard property and is not listed in the [Names] section of the .idq file.
Invalid property found in the 'CiSort=' specification in file <file>. A property specified in the CiSort parameter is not a standard property and is not listed in the [Names] section of the .idq file.
An invalid sort order was specified on the 'CiSort=' line in file <file>. Only [a] and [d] are supported. A sort-order specification following a property name in the CiSort parameter was unrecognized. Only [a] (for ascending) and [d] (for descending) are allowed.
One or more output columns must be specified in the .idq file <file>. The CiColumns parameter is missing or empty. At least one output column must be specified for the query.
Operation on line number of .ida file <file>. is invalid. An unrecognized keyword was found in the .ida file.
The query failed because the web server is busy processing other requests. The limit on the number of queries has been exceeded. To allow more queries to wait in the queue for processing, increase the value of the registry key IsapiRequestQueueSize, and to allow more queries to be processed simultaneously, increase the value for the registry key IsapiRequestThresholdFactor.
Read error in file <file>. Input/output (I/O) error occurred reading the file. Generally caused by hardware failure.
A restriction must be specified in the .idq file <file>. The CiRestriction parameter is missing or empty. Every query must have a restriction. A restriction such as #vpath *.* will match all pages.
A scope must be specified in the .idq file <file>. The CiScope parameter is missing or empty. Every query must have a scope. The scope / (forward slash) will match every page in all virtual directories and the scope \ (backslash) will match every page on every physical path.
The template file cannot be found in the location specified by 'CiTemplate=' in file <file> 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.
A template file must be specified in the .idq file <file>. The CiTemplate parameter is missing or empty. Every query must have a template (.htx) file.
Template for IDA file <file> cannot have detail section. A <%BeginDetail%> was found in the .ida file. Please remove it and the entire detail section.
Unrecognized type. Type specified is not one of the valid types (DBTYPE_I4, DBTYPE_GUID, and so on).
You must specify 'MaxRecordsPerPage' in the .idq file <file>. The CiMaxRecordsPerPage parameter is missing or empty. Every query must specify the number of records per page.