Mini Kabibi Habibi

Current Path : C:/Windows/System32/en-US/

Current File : C:/Windows/System32/en-US/tquery.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!�

�0@ �8.rdata�@@.rsrc� �@@����
T88����$��8.rdata8x.rdata$zzzdbg �.rsrc$01�!��.rsrc$02 ����(E�ͱrӗ�`��� �2Dπ�6�������0�H�p���������
���� 0 @ P ` p ��!��P"��8#��$@�X$\����d�MUI�����i�j9�x�͢s�X���W�j����Ւ�ǡ�/���MUIen-US
Annotation(Cleanup Url) AnnotationAnnotation has no targetRecovery Phase %s (0x%08x - %s)
Details:
PA
%s (0x%08x)
$Context: %s Application, %s Catalog
Context: %s Application
Merge Flush CorruptionPAUnspecifiedOther �
��h�0hh�kl�|�<��/ H �
!
�$
$
D!+
+
�!0
0
�"3
3
$6
6
$V
V
<$g
j
�$l
l
T(n
n
�(p
q
)x
x
*�
�
�*�
�
D+�
�
�+�
�
D,�
�
�,�
�
\/�/�1��T3�4 5�6�7(8�8%%�8�9
D:13;55�<::=<<l=���=��h>?D?%&�?))�@+,A00�A`B&&�C&&�C55�D668E"6"6�F%6%6,H+6+6�H.6.6�I<6<6JF6F6xJW6Y6�J�N. . �ODQ88�R�@�@�R�@�@HT�@�@�T�@�@LU�@�@�U�@�@�W�@�@�W�@�@�X�@�@ Z�@�@|Z�@�@$\ @ @�]@@<^@@X_@@�`*@*@TaC@G@�aX@X@hfi@i@�f�@�@Dg�@�@h�@�@xh�@�@�i@@�j�����j�����k����,o��Tp���p����|t�����v����y����Hy����{����������p���Ć�� �����
�
�Ԍ�����܎H�H�T�g�g���j�j�0�m�m�t�����В������+#�+#� �'�'���$'�('�Ԗ�������
�$��������Ч��4�� ����
�����\��(�0����������L�����������������������
�
�L�

�
���

�
��"
�#
��%
�'
��*
�*
� ,
�,
�� .
�/
��
1
�2
��4
�5
��7
�9
��@
�A
��C
�I
��P
�U
�XW
�Y
�t!`
�c
�H$e
�f
�)k
�k
��*m
�m
��,o
�o
��-r
�t
�4.v
�w
�p1y
�{
�4�
��
�P7�
��
�l:�
��
��;�
��
��<�
��
�`?�
��
�|K�
��
�xN�
��
��Q�
��
�lR�
��
��R�
��
��U���V���i��(l� �Pt��xv�����x�����������,�
��؟��x�������̩#�$�H���ȫ�����������ıQ�^��r�r���������t����0�0���6�9�@�;�;���=�>�����������d������
�
�(���H�� ��'�(���*�*���/�/�h��������� � ��!�!���"�"���$�$���$�$�H�%�%���&�&�H�&� &���&�&���&�&�D�&�&�p�'�'��(�(���3�3���4� 4��5�5�X�5� 5�8�6� 6���6�6�6�6��
6�6�D
!6�!6�<$6�$6��&6�*6�,6�-6�,/6�;6��=6�E6�D H6�V6�\&@�@��/����B�����F���O�����O����DQ�����Q�����R�����T�����U�����U����h[����\^����_����le�����e����0g�����g�����h��tk���l���m�
�n��p�!�(}��0� �
��Y�Y��b�e�t�o�p��s�t��}�}�����P�����������������������L�����0�����l�(#�*#���)'�,'�l��
��
���4�4���� �Ȟ!�$���-�.���1�3�x�Z6�Z6�ԥPNOTE: This dummy error message is necessary to force MC to output

the above defines inside the FACILITY_WINDOWS guard instead

of leaving it empty.

(Search service

Collator

Gatherer

4Content index server

dThe application was successfully restored.%1

dThe application was successfully backed up.%1

Index propagation to search server <%2> succeeded. The service is now waiting for the search server to accept the propagation.%1

lThe search server <%2> was successfully added.%1

pThe search server <%2> was successfully removed.%1

LThe MAPI service is unavailable.

tNo connection to a Search server can be established.

dNo matching items were found for this query.

\The query term was successfully ignored.

�The query found some matching items, but is unable to compile the entire result set.

$Parser Error

`The PASSTHROUGH query is not allowed: '%1'

lThe syntax near '%1' is incorrect. SQLSTATE=42000

�The syntax near '%1' is incorrect. Expected %2. SQLSTATE=42000

�Multiple statement commands are not supported. SQLSTATE=42000

�ORDER BY ordinal (%1) must be between 1 and %2. SQLSTATE=42000

|View '%1' was not defined in catalog '%2'. SQLSTATE=42S02

`Column '%1' was not defined. SQLSTATE=42S22

�The view name conflicts with a predefined view definition.

$Out of memory

LSELECT * is only allowed on views

�<content search condition> OR NOT <content boolean term> is not allowed

P'%1'cannot be converted to type %2

H%1 is out of range for type %2

|The specification of <relative interval> must be negative

`'%1' is not a column in the view definition

�The property name conflicts with a predefined property definition

\Weight value must be between 0.0 and 1.0

TThe matches string contains an error.

�The property name cannot be set because it is already being used in a VIEW. SQLSTATE=42000

�View '%1' already exists in the index '%2' and cannot be redefined. SQLSTATE=42S01

hThe index name '%1' is invalid. SQLSTATE=42000

pThe select list for the coalesce table is invalid.

tThe literal value cannot cast to the requested type.

�The relative interval given in the DATEADD function is too large.

PThe IN GROUP identifier is invalid.

�The status change request was ignored, because the same status change is already pending.

,The update ended.

Reset

8Preparing to propagate

Resume

Pause

|The gatherer has finished filtering standard properties.

�The update cannot begin without content sources. Add at least one content source that is not used for alerts.

`Failed to load document into IFilter. Possibly caused by unrecognized document format or document corruption. Only metadata obtained from the document storage was indexed.

Stop

$Start Update

tThe index configuration contains account information.

The content was not likely to be modified during the adaptive update, so the gatherer is not going to check the document for changes.

�The update will start as soon as all content sources are released by other updates that are already in progress.

�The transaction was ignored as redundant, because another transaction for the same URL was active at the same time.

�The gatherer started getting properties using the filter from the protocol handler.

PThis file link cannot be followed.

hSome parts of this document cannot be accessed.

pThe process notify queue was stopped successfully.

�The gatherer started getting properties using the document filter.

�Some parts of the document were modified, and others were not. The gatherer will refilter the entire document.

Full

Incremental

Adaptive

�Content for this URL is excluded by the server because a no-index attribute.

by user

for upgrade

$low resources

�This document is a child of another document. It will not be cataloged separately.

�The document contains text that can not be broken into words. The document won't be indexed.

�This is a success code that indicates that the MIME filter should be used to filter the document stream. This is an internal error code and should not be reported to users. Call Microsoft Product Support.

0for profile import

There is no update in progress. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

LThe Search server already exists.

The search server does not exist. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

xThe search server was added successfully, but cannot be contacted. Check that the search service is executing on the remote computer, and that you can connect to the remote computer.

�The content index server detected a previously crawled document with the same content. This is an internal error code and should not be reported to users. Call Microsoft Product Support.

@The content did not change.

�Filtering of this file ended because the file reached the maximum filter output limit. Check that the filter does not generate a large amount of data relative to the size of the document.

�The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled.

�The Access Control List was successfully changed to be readable by everyone.

dYou must use Rosebud to access this address.

hSome parts of this document cannot be accessed.

�The item should be accessed while impersonating a user. Protocol handler is expected to implement IUrlAccessor3.

dThe moniker doesn't cover the entire region.

`This is the last text in the current chunk.

dThis is the last value in the current chunk.

�A partial content scan of the disk must be scheduled for immediate execution.

�A full content scan of the disk must be scheduled for immediate execution.

�A content scan of the disk needs to be scheduled for execution later.

<The disk is almost full.

PThe document has no property sets.

\The document has no security descriptor.

�The word exceeds the maximum length, and may be truncated by the word sink.

�The word exceeds the maximum length, and may be truncated by the phrase sink.

8The workid is deleted.

\There are no more documents to enumerate.

�Administrative connections from client were not associated with a document store.

@The index has been stopped.

xThis is a new entry in the auxiliary metadata storage.

pThe client requested that the document be stopped.

`The client can now try to crawl a document.

�The catalog was reset due to diacritic difference or corruption.

8At least one content index definition was not initialized. Check the amount of free disk space, and verify that the registry configuration is correct.

dThe group or person was successfully ignored.

�One or more Lotus Notes database forms cannot be read. Some fields might not be available.

|The URL was redirected and will be handled automatically.

pThe Full Text Engine's input queue is getting full. This batch has been accepted for processing. This success code is intended to help pause input until the queue is less full.

�The Full Text Engine's input queue is full. This batch has been accepted for processing; however, the Full Text Engine will soon go into a forced paused state until the queue is less full.

�This transaction was superseded by a subsequent transaction, so it will not be completed.

�The project state has changed or is changing due to a status change request.

xThis is an internal error: The project will be resumed.

tThe enumeration has finished for the property store.

tThe catalog has been opened for read-only operations.

�Internal Success Code. Crawl is done. Chunk buffers can be flushed; there is no additional input data.

dThe property requested from the catalog blob received doesn't match the current value of the catalog property.

The property value used by the catalog was successfully returned.

The caller should either call SetProperty with the value returned or dismount the catalog and mount it back with the blob.

xOne or more properties were reset to the default value.

PNOTE: This dummy error message is necessary to force MC to output

the above defines inside the FACILITY_WINDOWS guard instead

of leaving it empty.

PNOTE: This dummy error message is necessary to force MC to output

the above defines inside the FACILITY_WINDOWS guard instead

of leaving it empty.

PNOTE: This dummy error message is necessary to force MC to output

the above defines inside the FACILITY_WINDOWS guard instead

of leaving it empty.

Classic

TThe Windows Search Service started.%1

�The Windows Search service is creating the new search index {Reason: %2}. %1

�The Windows Search Service has successfully created the new search index. %1

�The Windows Search Service has successfully removed the old search index. %1

`Windows Search Service stopped normally.%1

�The Windows Search Service successfully moved index files from %2 to %3. %1

�The update is complete. The gatherer successfully processed %2 documents totaling %3K. It failed to filter %4 documents. %5 documents were modified. %6 URLs were not found or denied access.%1

4The update started.%1

@The index is being reset.%1

TThe gatherer index was interrupted.%1

DThe gatherer index resumed.%1

�The incremental update is complete. The gatherer successfully processed %2 documents totaling %3K. It failed to filter %4 documents. %5 documents were modified. %6 URLs were not found or denied access.%1

\The crawl was requested to be stopped.%1

�An update cannot begin because the content source <%2> is in use by another update already in progress. The update will start as soon as all its content sources are released by updates already in progress.%1

�The adaptive update is complete. The gatherer successfully processed %2 documents totaling %3K. It failed to filter %4 documents. %5 documents were modified. %6 URLs were not found or denied access.%1

|Notifications for the scope %2 have been reactivated. %1

�The group %2\%3 contains %4 members. Groups over %5 members are not expanded. %1

pThe local groups cache was flushed, because %2. %1

d%1A master merge has started for catalog %2.

h%1A master merge has completed for catalog %2.

�%1A master merge has been paused for catalog %2 due to error %3.

It will be rescheduled later.

h%1A master merge has restarted for catalog %2.

�An index corruption was detected in component %2 in catalog %3.%1

P%1A master merge has been paused for catalog %2 due to low disk space.

The merge will be rescheduled later. Please free some disk space for indexing to continue.

�%1Catalog: %2. A master merge was started due to an external request.

%1Catalog: %2.

A master merge was started because the catalog reached the maximum number of indexes on the last level (%3).

�%1Catalog: %2.

A master merge was started because the expected number of documents in the catalog (%3) were indexed.

�%1Catalog: %2. The master merge was started because of internal reason number %3.

lThe content index service started successfully.%1

pIndex propagation to search server <%2> started.%1

�The Windows Search Service is being stopped because there is a problem with the indexer: %2.%1

lThe index already exists on search server <%2>.%1

�The index is being copied to the drop location in preparation for propagation.%1

�The index was completely copied. The index will now be propagated.%1

�Index propagation was committed to at least one target search server.%1

DIndex propagation stopped.%1

PThe %1 message facility is running.

�The Windows Search Service is starting up and attempting to remove the old search index {Reason: %2}. %1

\The Windows Search Service has failed to create one or more path rules.

The service will continue creating the SystemIndex search index.

Debug information: <%2>. %1

Event ID %2 for the Windows Search Service has been suppressed %3 time(s) since %4. This event is used to suppress Windows Search Service events that have occurred frequently within a short period of time. See Event ID %2 for further details on this event.%1

(While rolling back the index, the Windows Search Service encountered the following error: <%4,%5>. Index files were not moved from %2 to %3. %1

hAn error occurred in configuration file <%2>.%1

`The account used to start the Windows Search Service does not have the

rights to operate the service. The account must be either the LocalSystem

account or a member of the Administrators group. Use the Services tab in the

Control Panel to change the startup account for the search service.%1

`The system exception %1 occurred, and will be handled.

If this causes problems, contact Microsoft Product Support Services and include the stack trace in the event. %2.

$The update cannot be started because all of the content sources were excluded by site path rules, or removed from the index configuration.%1

�The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.%1

xCrawl could not be completed on content source <%2>.%1

tCrawl could not be started on content source <%2>.%1

lThe gatherer is unable to read the registry %2.%1

A request to start the update has been ignored because the update is already in progress or is scheduled on one or more content sources.%1

8The index was paused.%1

�The automatic description length was adjusted from %2 to %3.%1

4The update for the index cannot be started because the specified content sources were not configured for updates. Add at least one content source.%1

The previous update was reset, or was otherwise interrupted. A full update of all content sources will be automatically started. %1

�The update has been delayed because a disk is full. Check the system default temp location and the drive on which search catalog is created. The system default temp location is used for creation of temporary files during crawling. If it is full, crawling pauses. If the system default temp location is full, change the location to a disk with more free space and restart the computer. Changes to the system temp location do not take effect for system services until the computer is restarted.%1

|The gatherer property mapping file cannot be opened. The default values are being used. You may have to copy the property mapping file from the setup CD, or reinstall the application.%1

The automatic description encoding tag value is invalid. The gatherer is setting this value to "yes"". Fix the gthrprm.txt file.%1

TThe gatherer log cannot be created.%1

xThe word breaker for language <%2> cannot be loaded.%1

lPropagation failed while copying <%2> to <%3>.%1

�The Topic Assistant training database could not be created.%1

�The Topic Assistant training database could not be compiled.%1

�Propagation of the Topic Assistant training database to <%2:%3:%4> failed.%1

TThe gatherer is using the word breaker for language id <%2> for text in language id <%3>. The corresponding language resources are not installed on your computer.%1

DThe gatherer is recovering after an improper shutdown. This will delay availability of gathering functions, and may result in some noncritical data loss.%1

The gatherer detected pages in the history during recovery that cannot be read, and repaired them. However, statistical data for some URLs may have been lost. This can be caused by restarting a computer without first shutting down Windows, or by disk failure.%1

xThe Windows Search service stopped the Protocol Host process because it was consuming too many resources. A new Protocol Host process will be started. No user action is required.%1

<Notifications for the scope %2 are not active. The event logging threshold for this scope was exceeded. No further events will be sent for one hour. %1

@Notifications for the scope %2 were reactivated. The event logging threshold for this scope was exceeded. No further events will be sent for one hour. %1

�The system locale has changed. Existing data will be deleted and the index must be recreated.%1

xSecurity information was not obtained from server %2.%1

P%1 Unable to create the query engine's first request item due to error %2. It's possible that the MSFTESQL service account is invalid or the password has expired.

�Index propagation to search server <%2> was stopped by a user.%1

DThere are no search servers selected. Reconfigure the index to identify a suitable search server. If the problem persists, delete and recreate the index.%1

\The search server <%2> cannot be added.%1

�Search server <%2> cannot be contacted. However, <%2> was successfully added as a propagation recipient.%1

pThe search server <%2> cannot be brought online.%1

tThe Windows Search Service cannot initialize multi-instancing in Jet. If the application is used in a cluster environment, all applications using Jet will fail in the same group.%1

TThe noise files cannot be renamed.%1

pThe noise file "%2"" cannot be renamed to ""%3"".%1

|%2Unexpected Win32 error: %3 failed in %4. Error: %5. %1

�Performance Counters could not be loaded for %1 for instance %2 %3 due to the following error: %4.

�Could not get performance counter registry info for %1 for instance %2 %3 due to the following error: %4.

Performance counters will not be loaded because the named objects (shared memory or events) are in use for %1 for instance %2 %3.

�The protocol host process %2 did not respond and is being forcibly terminated {filter host process %3}. %1

�The filter host process %2 did not respond and is being forcibly terminated. %1

@MAPI: This is not supported

LMAPI: The character width is bad.

DMAPI: The string is too long.

xMAPI: The caller passed an invalid parameter or flag.

DMAPI: The entry ID is invalid

DThe MAPI object is invalid.

HThe MAPI object was changed.

DThe MAPI object was deleted.

<MAPI: The server is busy

XMAPI: The computer is out of disk space

�MAPI: Not enough system resources were available to complete the operation.

HThe MAPI object was not found.

�The version of OLE installed on the workstation is not compatible with this version of MAPI.

4MAPI: Logon failed.

XMAPI: The session limit was exceeded.

\MAPI: The user cancelled the operation.

XMAPI: The operation cannot be stopped.

LMAPI: A network error occurred.

DMAPI: A disk error occurred.

�The calling process is an NT service, and registry keys required by MAPI could not be initialized.

LMAPI: A bad column was requested.

PMAPI:An extended error occurred.

(MAPI: Computed

@MAPI: The data is corrupt.

4MAPI: Not configured

TMAPI: At least one provider failed.

LMAPI: A code page ID is unknown.

HMAPI: A locale ID is unknown.

dMAPI: Access is denied. Change your password.

�MAPI: Access is denied, because the password has expired.

�MAPI: Access is denied, because the workstation account is invalid.

�MAPI: Access is denied, because the access time is invalid.

|MAPI: Access is denied, because the account is disabled.

DMAPI: The session has ended.

HMAPI: An entry ID is unknown.

TMAPI: A required column is missing.

dA network read or write operation has failed.

tThe network connection was lost. Try the query again.

TThe parameters passed were not valid.

�Another operation is already in progress on this socket. Try the query again.

LThere is no more data to return.

�The requested content index name is not valid. Use a valid content index name.

TThe requested content index is disabled on the search server. Contact the system administrator to enable the content index. Check the event log for possible errors.

hThe query was cancelled at the user's request.

HThe request code is not valid.

|The request data is not valid for the given request type.

@The request cannot be processed, because the system is low on resources. Try again later, or contact your system administrator to free up system resources.

�The request or function call is out of sequence. Check for programming errors.

DThe query text is too long.

�The request cannot be processed because of an error in the search server.

�The configuration file for the content index is not valid.

�The search server cannot find one or more catalog files. Check the event log for related failures.

DThe SetStatus operation cannot be completed, because another SetStatus operation is already in progress. Try again after the current operation is completed.

8The content index cannot be created, because another content index with the same name already exists. Create the content index using a different name.

�The content index cannot be created, because the limit on the number of indexes was reached.

The search server cannot read or write to the registry. Check that the search server is running with administrative privileges.

�The content index cannot be removed in the current state. Disable and remove the content index.

�The tag database is not valid. Contact your system administrator.

�The content index name is in the wrong format. Use a name without spaces or punctuation.

hThe configuration file is not the correct type.

�There is a mismatch in the protocol between the search service and the client. Install the correct version of the client.

HThe index is already enabled.

�The content index directory structure cannot be created. See the event log for related errors.

TThe value exceeds the maximum length.

PThe requested parameter is unknown.

<The buffer is too small.

TThe parameter value is out of range.

XThe content index is already disabled.

�The operation cannot be completed, because one or more queries failed to terminate in a timely manner.

8The result is invalid.

�The registry data cannot be written. Check that the search service is running with administrator privileges.

@DS_E_CANNOTREMOVECONCURRENT

DThe content index cannot be created because an index with the same name already exists on the search server. Create the content index using a different name.

�The content index cannot be enabled because its propagation version cannot be verified against the dedicated index server. This can occur when either the dedicated index server is offline or the content index is out-of-date.

pThe requested operation is not valid at this time.

LThere is no more data to return.

�The query cannot be collated, because columns using the same name have different types.

�Not enough buffer space is available to collate search results.

DThe result row is corrupted.

�The search server did not return a column required for collation.

LThe database ID is a duplicate.

�The data source merge exceeded the number of result columns.

@No default index was set.

�The maximum number of open provider connections was exceeded.

xThe limit on the number of search servers was reached.

lThe limit on the number of indexes was reached.

xNo query connections to the server can be established.

\The requested content index is disabled.

�The network timed out trying to acquire a connection to a search server.

XThe specified server cannot be found.

dThe Windows NT registry cannot be accessed.

�The requested content index is empty or has not been added to the search server.

4The query timed out.

�The buffer area passed to the function is not large enough.

HThe query syntax is not valid.

�The column type in the search query does not match the column type in the index.

TThe query type specified is unknown.

pThe number of columns requested exceeds the limit.

lThe query contained too many content index IDs.

�The query start hit is larger than the total number of results.

PThe query contains too many terms.

@No indexes were specified.

HThe query operation timed out.

pThe query specified sorting a non-sortable column.

xThe query specified searching a non-searchable column.

`The query specified a nonexistent column.

lThe query data is not valid or is inconsistent.

hA query term begins with a wildcard character.

�A query term contains an invalid embedded wildcard character.

�A wildcard term in the query does not contain a sufficiently long prefix.

pThe search server is unable to process the query.

�The search criteria are too general or matched too many terms.

|The query does not contain any meaningful restrictions.

hThe query did not specify any return columns.

�The scopes specified for the query were incorrectly formatted.

�The indexes specified for the query were incorrectly formatted.

hThe number of scopes or depths was not valid.

lThe operation is invalid in the current context.

HAn invalid path was supplied.

TThe log manager is not initialized.

pAn invalid interval was passed to the log manager.

`No log manager was attached to the logger.

4The configuration file attempted to load a reserved column. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�The configuration file cannot be found. Reinstall the application.

�The tag nesting configuration for the application is not valid. Reinstall the application.

�The configuration file for the application contains an invalid tag. Reinstall the application.

�The configuration file version number for the application is invalid. Reinstall the application.

�The output configuration file cannot be created. Stop and restart the system, and then reinstall the application.

0Data cannot be written to the output configuration file. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�The configuration file for the application contains invalid information. Reinstall the application.

�The configuration file type for the application is not recognized. Reinstall the application.

�The configuration file column data type for the application is not recognized. Reinstall the application.

The noise word file cannot be created. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

8There was an error writing to the temporary noise word file. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�The specified column name already exists. The application's configuration was corrupted. Reinstall the application.

�The value for the attribute is invalid. The application's configuration was corrupted. Reinstall the application.

�The property set GUID is invalid. The application's configuration was corrupted. Reinstall the application.

�No more columns. This is an internal error code and should not be reported to users. Call Microsoft Product Support.

tThe system cannot write to the configuration file, because it was modified since it was last read. Stop and restart the search service. If this problem persists, reinstall search.

�The specified column name is invalid. The application's configuration has been corrupted. Reinstall the application.

�The property ID specified is invalid. The application's configuration has been corrupted. Reinstall the application.

HAn invalid attribute was specified for this tag, or a required attribute is missing. The application's configuration was corrupted. Reinstall the application.

The specified file name is invalid. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

0A column having the specified property set and PID already exists. The application's configuration has been corrupted. Reinstall the application.

The configuration describing a language and sublanguage contains unexpected duplicate information. The application's configuration may be corrupted. Though basic functionality is unlikely to be impacted, it is recommended that you reinstall the application.

�The object you are trying to create already exists. Try again using a different name.

(The registry value cannot be read because the configuration is invalid. Recreate the content index configuration by removing the content index.

�The value cannot be set, because the object was already deleted or was not initialized properly. Check that the object reference is still valid, increase the registry size, or recreate the content index configuration.

Performance monitoring cannot be initialized. This affects performance counters only. Try restarting the service or restarting the server.

�The specified object cannot be found. Specify the name of an existing object.

�The specified address was excluded from the index. The site path rules may have to be modified to include this address.

A duplicate index entry exists in the registry. No other indexes are affected, but it is recommended that the duplicate entry be deleted.

A duplicate extension entry exists in the registry. The duplicate extension should be deleted, but all other extensions are unaffected.

tThe URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add.

The gatherer attempted to create more gatherer plug-in objects than are allowed. Remove another plug-in before adding this one.

4The function is not implemented in this context, and cannot be called. This error is internal, and cannot normally occur. Reinstall the application.

�The plug-in did not provide a filter sink object. You may have installed a custom plug-in that is not supported.

�The filtering process ended and is now unavailable. The address will be retried, but it is possible that the system is low in resources. Free some system resources, or restart the update when resources are available.

�An unexpected message was received from the filtering process. The address will be retried, but if this occurs frequently, your system is low on resources. Free some system resources, or restart the update when resources are available.

�The filtering process returned an unsupported property type. Fix the filter to allow successful use of the document.

The specified name for this object exceeds the maximum length, which is usually 2047 characters. Use a shorter name for the object.

�The user agent or e-mail address was not specified. Specify the e-mail address to use in the protocol headers.

�A filter for the document cannot be created. Install the corresponding filter for this document format.

�All threads in the filtering process are currently in use.

The ProgID for a protocol handler cannot be obtained, and the protocol handler registration is invalid. Reregister the protocol handlers.

�The filtering process was stopped because its memory quota was exceeded.

�The protocol handler cannot be found. Check that the handler has been installed.

The gatherer index was not initialized. The content index must be remounted. If the index is still not initialized, remove it.

�The catalog name is invalid. Choose a catalog name that is shorter or does not contain special characters.

HThe gatherer is shutting down.

The requested value was not set by the filter process. This is a recoverable internal error. The document may still succeed.

�All valid document IDs were used. Recreate the content index.

�This content source cannot be crawled, because its is set up to accept alerts.

�The property mapping is duplicated in the schema. Remove the duplicate property schema.

�The specified account information is incorrect or invalid. Check that the correct account and password are being used.

The document cannot be filtered, because the document and filter versions do not appear to match. Install a matching document filter.

�The specified account name cannot be used because it contains invalid characters, such as '\'. Use a valid account name.

�The proxy server name is missing. Specify a proxy server, and try again.

<The server is unavailable and cannot be accessed. The server is probably disconnected from the network. Access attempts will be delayed for ten minutes.

�This path does not correspond to the selected site. Use a path name that matches the site, or use a wildcard (*).

The document cannot be filtered, because the required code page is not installed. Install the code page for this document.

�No protocol handler is available. Install a protocol handler that can process this URL type.

�Internet Explorer is set to offline mode. Change Internet Explorer to online mode, and continue.

�The filter process cannot be started. The system is most likely low on resources, or the filter process binary was modified. If the resources are available, check the search binaries with an antivirus program.

�The specified URL mapping is invalid. The "from"" mapping is empty, or the ""from"" mapping is the same as the ""to"" mapping. Specify a valid ""from"" mapping that differs from the ""to"" mapping.

DThe user agent string was not specified or contains invalid characters. Specify a user agent which is not empty and does not contain double quotation marks.

xThe e-mail address is missing. Type an e-mail address.

�The specified number of logs to keep is invalid. Set the number of logs to be greater than zero.

4The extension string is not specified or is invalid. Specify an extension string that does not contain the following characters: [./?*:\#] or spaces.

�The specified maximum grow factor is invalid. Set the maximum grow factor to be greater than or equal to zero.

�The specified time out value is invalid. Set the time out value to be greater than or equal to zero.

�The specified retry limit value is invalid. Set the retry limit value to be greater than or equal to zero.

�The gatherer log file name is not specified. Specify a log file name.

The site name is not specified or is invalid. Specify a site name that does not contain the following characters: [/\\@#|] or spaces.

�The content source is not specified or is invalid. Type a host name that does not contain * or spaces.

�A catalog with the name specified already exists. Create the catalog using a different name.

The path is not specified or contains invalid characters, such as ["" ?*]. Specify a path that does not contain these characters.

�The filtering was stopped because of a user action, such as stopping the crawl.

�The specified port for the HTTP proxy is invalid. Specify a port between 0 and 0xffff

�The account password was not specified. Specify the password.

�The path expression cannot contain the reserved escape character '|'. Use an expression without reserved characters.

|' - a reserved escape character. Use an expression without reserved characters.

�The specification for the content source is missing the host name. Specify a valid URL.

,The path specification for the content source cannot contain wildcard characters, such as [?*]. Remove all wildcards from the path specification.

The specified gatherer application cannot be found. Use the name of an existing application, or reinstall the application.

pThe application plug-in manager cannot be removed, because one or more content indexes was configured to use the plug-in. Remove all indexes, and then remove the plug-in manager.

The application name is invalid, because it contains special characters. Specify a different application name without special characters.

�The data size returned by the filter is greater than the allocated buffer. Download and install an update for the filter.

�The object cannot be created on a non-fixed drive. Create the object on another drive.

The system attempted to load a filter marked as apartment in a multi-threaded filter daemon. The document will be retried in a single-threaded filter. Since multithreaded filtering is more efficient, try to obtain the version of the filter that is multi-threaded.

�The identified content was not crawled for this address. Recreate the content index.

�The gatherer cannot handle the alert stream. All alert sources will be crawled again.

A duplicate of this document was detected, and the document will be retried. If this problem persists, recreate the content index.

<The administrative data from the Exchange store or registry cannot be read. Check that the Exchange store is started, and that it was properly restored.

�Read access to the Exchange store is temporarily unavailable. If this message persists, restart the Exchange store.

XThe function is unavailable, because it was called while the word breaker was attempting to fill the text buffer. Download and install an update for the word breaker.

DThe property list for the content class of this document cannot be loaded, and the schema cannot be accessed. Check that the schema is correctly configured.

�Crawling cannot continue because the local server is not responding. Restart Microsoft SQL Server 2000.

Schema/schema cache error (%1) occurred. Schema collection ref: %2, content class: %3. This error is internal, for debugging.

hDocument filtering cannot be completed because the document server did not respond within the specified timeout. Try crawling the server later, or increase the timeout values.

�The content source for this alert must refer to a valid file system directory

lAlerts for this content source are not supported.

�Alerts for this content source cannot be established because information about the file share cannot be obtained.

Alerts for a content source with a local address are only supported for a fixed media drive type. Use the UNC name for remote file shares.

(The new content index cannot be added because there is not enough disk space. Free up at least 10 megabytes of free space, and then try again.

�The document received an invalid document resource ID. The document must be crawled again.

�Hierarchical content sources such as those in the file system cannot be nested.

�The first attempt to crawl this object failed. Another attempt is being made.

�Backup and restore failed during an ESE database phase. For more detailed information, check the event log.

,The plug-in is not properly registered on this computer. Check that the application is properly installed, or contact Microsoft Product Support.

�Alerts for this scope were interrupted so that authentication tokens can be updated.

File system alerts were not initialized successfully If the problem persists after restarting the service, try rerunning Setup.

�File system alerts for this scope are stopped because the scope is being removed.

\Alerts failed because of network failures or because the internal cache size was exceeded. If the problem persists, change the content source type to adaptive or crawl.

�The operation could not be completed because the specified path is invalid. Try again using a valid path.

There were not enough keywords in the sample documents to train the Topic Assistant. Try again when more sample documents are available.

(The Topic Assistant requires sample documents from at least two categories. Try again when sample documents for more categories are available.

�There were not enough sample documents to train the Topic Assistant. Try again when more sample documents are available.

�An error occurred using the topic assistant. Check the event log for related failures.

PThe system attempted to load a filter marked as apartment from an embedded component in a multi-threaded filter daemon. The document will be retried in a single-threaded filter. Since multithreaded filtering is more efficient, try to obtain the version of the filter that is multi-threaded.

�The data for this folder will not be crawled because it is configured to be crawled by (%1).

�The security descriptor for this document only contained built-in access control entries. The built-in ACEs have to be removed because they won't be valid for this document during queries.

�The context for this object is no longer valid. Refresh the context for this object.

The checkpoint cannot be enabled, because the content index is not idle. Wait until the index is idle, and then try again.

�The maximum number of search scopes was reached. Use one of the existing scopes.

�Maximum number of properties per document has been reached. The document is most likely corrupt, or it represents a denial of service threat, the indexing of this document has been aborted.

�The start address is invalid because it is a local path. Please enter a valid start address.

\The filtering process has been terminated

DThe backup image cannot be verified because the image may be corrupted. To preserve your data, it is recommended that you run Data Backup and Restore again.

�The filter host process cannot be started. The system is most likely low on resources, or the filter host process binary was modified. If the resources are available, check the search binaries with an antivirus program.

dThe per-user filter pool could not be found.

�Some of the links were not successfully added to the queue. Parent transaction will be retried.

�The tag is invalid. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�The propagation configuration file cannot be read. Check that the same versions of search are used on both the content index and search servers. If the problem persists, recrawl and repropagate the content index.

�The number of search servers exceeded the limit. Ensure that the number of propagated content indexes is less than the documented maximum. If so, start and restart the search service, and then try again.

The specified search server already exists. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

An update is already in progress. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

The index list file cannot be read. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

pA registry entry required for content index creation cannot be read or created. Delete and recreate the content index. If the problem persists, you may need to reinstall search.

`One or more files required for content index creation were not found. Stop and restart the search service. If the problem persists, delete and recreate the content index.

LThe search server was not found. Stop and restart the search service. If propagation is being used, stop and restart the search service on the remote computers.

�A word breaker was not found for the given language. Check your current language settings and ensure that search supports the current language. If the problem persists, reinstall search.

,A noise word list was not found for the given language. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

A stemmer was not found for the given language. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�Index propagation was stopped. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�The disk is full. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�The index data is invalid. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�The index data is corrupt. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

The property store cannot be initialized. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

The propagation state information cannot be read. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�The content index is not loaded. Stop and restart the search service. If the problem persists, review other errors in the event log. If necessary, delete and recreate the content index.

�There is a mismatch in the major version number. Check that the same versions of search are used on both the content index and search servers. If necessary, crawl the index again and repropagate the index.

(The index is a mismatch in the minor version number. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

�A connection with the Search service on a remote machine could not be established. Check the connectivity with the remote machine. If necessary, stop and restart the Search service on the remote machine.

Crawling of documents was stopped. This is an internal error code and should not be reported to users. Call Microsoft Product Support.

The index was dismounted because it is being removed or the search service stopped. If the problem persists, restart the search service.

�No index level information exists for this index. Use application level tables for this index.

`Information for this content class was not found. Use the default content class. This error is obsolete and should no longer be reported. Call Microsoft Product Support.

The content index server cannot update or access information because of a database error. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index.

HThe content index server cannot find a description of the content index in its database. Search will automatically attempt to recreate the content index description. If this problem persists, stop and restart the search service and, if necessary, delete and recreate the content index.

�The content index server cannot find needed information in its database. Reset and recrawl the content index.

�The content index server cannot update or access its database, because the version store has insufficient resources. Increase the system resource usage setting for the search service. If the problem persists, stop and restart the search service.

�The content index server cannot update or access its database because sessions are unavailable. Increase the system resource usage setting for the search service. If the problem persists, stop and restart the search service.

�The content index server cannot update or access its database because insufficient system resources are available. Increase the system resource usage setting for the search service. If the problem persists, stop and restart the search service.

The content index server cannot update an unrecognized or recently defined property attribute. Reset and recrawl the content index.

$The property store was unable to open, close, or delete a data file used in propagation. Check that your index volume has enough disk space.

�The property store encountered propagation data files that cannot be used. Try propagation again.

�There is a mismatch in the property store version numbers. Ensure that the same versions of search are used on both the content index and search servers. If necessary, recrawl the content index and try to propagate the content index again.

(The content index server cannot update or access information because of a sharing violation. Stop and restart the search service. If the problem persists, reset and recrawl the content index. In some cases it may be necessary to delete and recreate the content index.

�The configuration properties for Microsoft Exchange 5.5 were not set. Specify these properties, and then try again.

\The name of the Microsoft Exchange 5.5 server specified in the content source does not match the Exchange server specified in the Microsoft Exchange 5.5 configuration properties. Change the name of the Exchange server in the content source or configuration properties to match, and then try again.

4There is insufficient privilege to access the Microsoft Exchange 5.5 server. Check that the Microsoft Exchange 5.5 configuration is valid and that the search service is running in the context of a user having administrative privileges on the Exchange server configuration node.

(The Microsoft Exchange 5.5 server name specified in the address does not match the one specified in the Microsoft Exchange 5.5 configuration.

8There is insufficient privilege to access the Microsoft Exchange 5.5 Server. Verify that the Microsoft Exchange 5.5 configuration is valid and that the Search Service is running in the context of a user having administrative privileges on the Exchange Server configuration node.

�The service cannot access the Exchange 5.5 server. The configured Microsoft Exchange 5.5 server name may be invalid, the Exchange 5.5 server may be temporarily unavailable, or the account used by the search service may not have administrative access to the Exchange 5.5 server. Check all of these properties, and then try again.

�The service cannot access the Exchange 5.5 service. The account used by the search service may not be an Exchange administrator, or the site or organization settings on the search host may be invalid.

Outlook is not installed on this machine, or is missing the CDO or MSEMS components. Please install and configure Outlook, then try again.

The account information specified for accessing the Exchange 5.5 server cannot be used. Verify the account and password information.

HA communication error occurred.

<The object was not found.

�The options used are not supported. Check that your version of Internet Explorer is supported.

�An unrecognized HTTP status was received. Check that the address can be accessed using Internet Explorer.

�Access is denied. Check that the Default Content Access Account in Windows Search Central Administration is correct, or follow the "Exclude and Include Content" link to add a rule to specify the proper crawling account to access this URL.

�A server error occurred. Check that the server is available.

You have been redirected to an address that does not exist. Check that the source address is redirecting to an accessible address.

�The address appears to be in error. Check that the address is valid.

�Cannot Connect to the server. Please make sure the site is accessible.

�The address cannot be accessed. Check that the address can be accessed from Internet Explorer.

`The attempt to access the URL again failed.

�The URL was excluded because its content type (multipart/x-mixed-replace) is not supported.

XSearch was unable to convert the Access Control List of the crawled store into a Windows NT Access Control List. Check that local information is not used in the store.

�An object cannot be processed because search cannot convert a Notes Access-Denied entry in the Access Control List into a Windows NT identity. Check the Notes to Windows NT identity mapping.

�The item will not be crawled because the Access Control List allows no one to read the item. Check that this is intended.

Search cannot crawl the item, because its Access Control List exceeded 64 KB. Check that the item has a valid Access Control List.

The item cannot be processed further because search failed to find one of its properties. Check that the item is valid in the store.

�The database cannot be opened. Check that the database is functional.

�Filtering was interrupted because of a sharing conflict with another process. Crawl the file again when it is not in use.

XThe protocol handler cannot be loaded.

`The protocol handler cannot be initialized.

\The volume mount point is not supported.

�Some data was truncated. Check that the content can still be read.

|An internal error occurred while expanding local groups.

�Error found in the Secure Sockets Layer (SSL) certificate sent by the server.

�Accessing this site requires a client certificate. Specify a client certificate in the site path rules.

�The Exchange search provider cannot be initialized. You may have to reinstall the application.

�The security provider was not initialized. You may have to reinstall the application.

�The search service is running as a local System service. To access Exchange documents, check that the search service is running in a user account with administrative privileges on the Exchange server.

�Access is denied. You may not have sufficient privileges to perform the operation.

DAn unexpected error occurred.

xThere is an unmatched parenthesis on the command line.

@The parameter is too long.

�The object is not initialized. Call Init() first to initialize the object.

PThe object is already initialized.

HThere are too many parameters.

XThe call failed for an unknown reason.

<The parameter is invalid.

XThe query restriction cannot be parsed.

TAn invalid sort order was requested.

hAn invalid categorization order was requested.

�A clause of the query contained only words that are ignored.

\The query was too complex to be executed.

dThe query exceeded its execution time limit.

�One or more columns in the output column list is a duplicate.

�One or more columns in the output column list is not valid.

HThe directory name is invalid.

lThe specified directory is on a removable medium.

�The index is still being crawled, but queries are no longer allowed.

�The relevant specified documents were not found, because a clause of the query contained only words that are ignored.

�None of the relevant documents specified in the query can be found.

8No information was found in the relevant documents with the specified properties, because a clause of the query contained only words that are ignored.

�No relevant information is found in the relevant documents with the specified properties for this query.

xThe same relevant document is specified multiple times.

`The reldoc specification is not supported.

hThe specified document identifier is not valid.

�The server is running an older version of software that cannot handle this query.

�Scopes should be the same in all of the components of a coalesce query

�Order by list should be same in all the components of a coalesce query.

Coalesce is either not used properly or this form is not currently supported. Check for possible mixing of grouping with coalesce

�Queries are disabled because the index is being updated. Try your query again in a few minutes.

@Aggregate is not supported.

�The top level group does not support ORDER IN GROUP since there is no parent group.

dEach name for a ranged label must be unique.

@The file cannot be opened.

0Read error in file.

<Expecting property name.

<Expecting type specifier.

0Unrecognized type.

0Expecting integer.

HExpecting closing parenthesis.

(Expecting GUID.

$Invalid guid.

DExpecting property specifier.

DFailed to set property name.

<Duplicate property name.

\DBTYPE_VECTOR or DBTYPE_BYREF used alone.

�DBTYPE_BYREF must be used with DBTYPE_STR, DBTYPE_WSTR, DBTYPE_GUID

or DBTYPE_UI1 types.

<Unexpected end of string.

|There are no more chunks of text available in the object.

dThere is no more text available in the chunk.

|There are no more property values available in the chunk.

HThe object cannot be accessed.

XThere is no text in the current chunk.

\There are no values in the current chunk.

tThe Ifilter for the embedded object cannot be bound.

pThe Ifilter for the linked object cannot be bound.

tThe file was not filtered due to password protection.

tThe document format is not recognized by the filter.

LThe file is too large to filter.

�The file cannot be opened, because another file is already open.

@The file is not reachable.

`The document is in use by another process.

<The document is not open.

\There is no property with the given GUID.

<The document is offline.

�The document was too large to filter completely. Portions of the document were not emitted.

`End of text was reached in the text source.

dThis feature is only available in query mode.

tThe buffer is too small to hold the composed phrase.

lThe language database/cache file cannot be found.

`Initialization of the word breaker failed.

TFeature only available in query mode.

dThis feature is only available in index mode.

hThe attachment type is beyond the valid range.

PThe object is already initialized.

HThe object is not initialized.

<The buffer is too small.

LThe given property is not cached.

PThe object is not in a valid state.

dFiltering is disabled for this content index.

�The disk is full and the specified operation cannot be completed.

XThe content index service was stopped.

<The workid is not valid.

<The object was not found.

`The passed-in property id is not supported.

`There were two alerts for the same workid.

�A document update was rejected because updates were disabled.

hThe combination of flags specified is invalid.

�The incremental data given to Load is not valid. It may be out of sequence.

lA sharing or locking violation caused a failure.

hA logon permission violation caused a failure.

The index does not exist or is currently unavailable. Try again later. If this problem persists, contact the system administrator.

�Page size is not an integral multiple of the sector size of the volume where the index is located.

<The service is too busy.

@The service is not running.

�The cardinality of machine, indexes, and scopes is mismatched.

lThe disk has reached its configured space limit.

�The property store is not configured to handle auxiliary metadata storage.

|The specified index list version is outdated or invalid.

�A catalog with the name specified already exists. Choose another name to create a new catalog.

The account cannot be granted a privilege to "log on as service"" on the domain controller. The domain security administrator needs to grant the default account this privilege. All of the default accounts specified for the server need this account privilege.

HThe selected content index definition did not initialize and cannot be used. Check server status, content index configuration, and user access to the server.

DThe chunk type was not text.

PThe property ID type was not name.

XThe property ID type was not numeric.

DThe chunk type is not value.

�The chunk does not allow changes. To set properties on a chunk, create it using IGatherScriptFilterSink::CreateChunk

hThe resource completion code was already set.

�The specified application name is not valid. Check to see whether a search application with that name already exists.

�The specified search application name was not found. It may have already been deleted.

�The search application name already exists. Use a different name.

�The specified catalog was not found. Check to see if it was deleted, or if there are errors in your application code.

�The content index cannot be deleted while the search service is stopped. Restart the search service and try again.

�This file is shorter than 2 bytes. Unicode text file must begin with a wide character that indicates byte order.

TThe specified catalog already exists.

�This scope has no default namespace. Add a default namespace before continuing.

4The SXQL is invalid.

�An unexpected error occurred in the filtering process. Contact Microsoft Product Support.

�The document IFilter cannot provide the needed interface. The IFilter may contain errors.

�A document IFilter cannot be initialized. The document or IFilter may contain errors.

\An encrypted document cannot be filtered.

pThe password for the content access account cannot be decrypted because it was stored with different credentials. Re-type the password for the account used to crawl this content.

�A custom error (%1) in the OLEDB provider has occurred. %2.

�An unexpected error occurred in the Notes protocol handler while processing the URL.

�Only rich text, HTML, and text types are supported for the content field.

HA requested item is not found.

�The Notes data cannot be accessed. Check that the server is properly configured for accessing Notes data.

dOne or more attachments cannot be processed.

XThe Windows NT identity does not exist.

�Access to %1 is denied to user %1. To allow access, contact your Notes administrator.

�The user name mapping cannot be read. Check that the database, view, and column names are correct, that the Notes database is accessible, and that the sort option is enabled. For more information, see the Administrator's Guide.

HUnknown Lotus Notes Error: %1.

,Stop Parsing XML

PError in the Site Data Web Service.

LError in PortalCrawl Web Service.

�An unexpected error occurred in the exstore protocol handler. Contact Microsoft Product Support.

�Cannot find or access the client certificate specified for crawling this site.

�An unexpected error occurred in the in-memory schema cache.

�The property mapping information on the content source cannot be read.

�The content source information code contains unexpected null pointers.

�Parallel vectors for property mapping information on the content source have different dimensions.

�The content class information for the content source cannot be read.

�An unexpected exception occurred in the content source information code.

lThe content class of the content source is empty.

�An unknown data type was found when reading content class information from the content source.

�A request for property mapping information is out of range.

tEmpty or null URIs are not valid as property mapping.

�This is an internal error code. A method was called when it should not be. Call Microsoft Product Support.

�A security update was attempted on an address that was redirected to a different server.

\An address was redirected more than once.

lThe requested property does not exist on the row.

tThe requested read type does not match the data type.

�The status of the request data is unexpected. Call Microsoft Product Support.

�An unknown data type was found. Call Microsoft Product Support.

�An unexpected filter state occurred. Call Microsoft Product Support.

�A duplicate property was found. Call Microsoft support if this error is encountered.

�The account password was not specified. Specify the password.

�The named pipe used to communicate with the filter daemon has not been connected.

�The configuration data given to the MSFTESQL service is corrupt.

TThe system attempted to load an apartment threading model filter marked in a multi-threaded filter daemon. The document will be retried in a single-threaded filter daemon process. Since multithreaded filtering is more efficient, try to obtain the version of the filter that is multi-threaded.

�The value cannot be set, because the object was already deleted or was not initialized properly. Make sure the object reference is still valid, increase the registry size, or recreate the catalog configuration.

�An internal interface is being used after the corresponding catalog has been shutdown. The operation will be aborted.

�An internal interface is being used prior to being initialized. The operation will be aborted.

�Data transferred between the MSFTESQL service and a filter daemon process is corrupted. This is an internal error.

�This is an internal error: The URB has exceeded the maximum size.

�This is an internal error: Document IDs should be greater than 0 and less than or equal to 0x7fffffff.

�An external status change has put the catalog in a paused state.

�A status change is occurring or the project is in a force paused state, so MSFTESQL cannot accept input at this time.

�The MSFTEFD process was launched but did not connect with the MSFTESQL service.

This is an internal error: Initialization of the datasink is incorrect. At least one protocol handler PROGID is required.

This is an internal error: A static thread has gotten invalid arguments and will force batches to be aborted and retried.

�A catalog already exists with this name, so another can be created or mounted.

�A file path exceeds the maximum limit for paths in Windows, so it can't be used.

�Access is denied to the caller of this administration interface.

hSignature validation cannot be performed on modules loaded by COM, so the object will not be created. The object is likely a filter, wordbreaker, stemmer, or protocol handler.

XThe processor affinity mask is invalid.

This is an internal error that should be handled. The FD has been killed and this chunk buffer has already been reassigned.

�The maximum number of plug-ins has been exceeded, so a new plug-in can't be loaded.

An object could not be inserted because it was a duplicate of an existing object. The object may be a catalog or other named entity.

|The transaction that superseded this one ended in error.

�This is an internal error: This request cannot be completed because the Filter Daemon has been shutdown.

�The catalog does not exist, so the operation can't be performed.

�There are no plug-in components in the indexing pipeline, so the data collected will not be used.

�Processing of this batch of transactions has been aborted.

A status change is active on another thread. Since only one status change is allowed at a time this request can't be handled.

�A previous error prevented further processing of the batch.

The filter daemon process MSFTEFD timed out for an unknown reason. This may indicate a bug in a filter, wordbreaker, or protocol handler.

�This is an internal error: This activity is no longer valid because the resource is shutdown.

PThe property specified is invalid.

DThere are no more properties.

The plug-in specified is not known likely because it isn't loaded, so the operation can't succeed. Only specify plug-ins that are loaded.

tThe performance monitor library could not be loaded.

�There are no more slots available for this performance monitor instance

�The filter daemon process MSFTEFD was not able to create an accessor object for the batch.

$The property type specified is incorrect for this property. Please see the product documentation for the correct data type for this property.

�The value specified is out of range. Please see the product documentation for the valid range.

dThe property store for upgrade is corrupted.

hThe workid is not valid for the property store.

hThe gatherer hash map for upgrade is corrupted.

dThe key is not cached in the property store.

lThe upgrade interface has already been shutdown.

�The upgrade interface has already been instantiated. Only one instance of the upgrade interface is allowed.

tThe stack for a thread in this process is corrupted due to a programming bug. This may be a security threat and indicate your system has been attacked. The process will be shutdown.

�The protocol handler index passed to the OnDataChange function is invalid.

dThe serial stream being indexed is corrupted.

�The catalog is opened for read-only operations. Writing is prohibited to this catalog.

�The performance monitor counters cannot be unloaded because they are not loaded in the first place.

�This huge document will be retried in dedicated filter daemon MSFTEFD process.

�This is an internal error: The filter daemon MSFTEFD type is unknown or invalid.

�There are not enough resources to process the document or row.

�This is an internal error: Datatype misalignment was detected likely due to a programming error.

PThe object is already initialized.

�The filter daemon process MSFTEFD used too much memory and will be terminated.

�The MSFTESQL service process exited unexpectedly.

Here is the stack Trace:

�High memory pressure was detected by the MSFTESQL memory manager.

�A batch flagged to isolate a previous error had too many transactions in it.

�msftesql should reprocess this document in an isolated fashion to confirm the error.

�An internal identifier for naming catalogs has been corrupted.

�A failure occurred when tracking the completion of wordlists which will cause current activity to be aborted.

�The specified code page is not installed or not available.

�Internal Error Code: Filter Daemon is terminated because it is idle.

�Filter Daemon was unresponsive to a directive to shut itself down.

�The user profile database connection cannot be made, because of error %1.

@No data source is defined.

�The data source definition cannot be retrieved, because of error %1.

`No data source property mapping is defined.

�Data source mapping cannot be retrieved. Check to see that the mapping entry is valid.

pDatatype (%1) in the data source is not supported.

X(%1) cannot be converted to type (%2).

lIncremental import information cannot be updated.

�A zero-length cookie was retrieved at the end of a Dirsync search. The account may not have the appropriate rights.

pThe specified LDAP distinguished name is too long.

HThe canonical URL is too long.

(The user account name can not be resolved within the Active Directory. You would need to verify whether the user is a real user or just a temporary user object generated for some application purpose. You might be able to refine the LDAP search filter to avoid this error.

\Error (%1) occurred, which may have resulted from the unavailability of directory service server (%2). If the auto discovery option is turned on, import will re-try it with the newly discovered domain controller. Otherwise, verify your import settings and make sure the server is still available.

lThe attempt to discover domain controller for domain (%1) was failed with error (%2). Please make sure whether there is problem in network connectivity or the domain is renamed.

�Fail to retrieve locale from site database - Error (%1) occured.

�The specified domain (%1) has been removed from import configuration.

Access was denied on domain: (%1), and user information from the domain was not imported. Check the user name and password of the access account specified on the Configure Profile Import page. If incremental import is enabled and you are importing from a Windows 2000 domain, check that the access account has the Replicate Changes permission for Active Directory directory services.

�You do not have sufficient permissions for incremental import, or the DirSync cookie stored in the user profile database is corrupt. If you are importing from a Windows 2000 domain, check that the import account has the Replicate Changes permission for Active Directory directory services. If the import account has the permission, start a full import to refresh the cookie.

�This is an internal error: The chunk buffer is out of memory.

�This is an internal error: The chunk buffer id is out of bounds.

There is not enough available physical or virtual memory for chunk buffers. Chunk buffers are needed to index data. Please free up memory.

dThere is not enough occurrence buffer memory available. Possible causes include too many processors, too many filter threads, or the occurrence buffer is not being returned.

�The in-memory wordlist is corrupted. This is due to a faulty filter, wordbreaker, or other indexing component.

�The IPersistStream and IPersistFile interfaces were unavailable from an IFilter filter DLL to load data for indexing.

\The IFilter::Init() function call failed.

�The filter daemon MSFTEFD failed to load an IFilter interface for document, so it can't be indexed.

�The document being indexed timed out for an unknown reason. This may be due to a bug in a filter or wordbreaker.

�The filter daemon process MSFTEFD exited unexpectedly.

Here is the stack trace:

$The filter daemon process MSFTEFD exited unexpectedly because of document %1.

Batch Id: %2

Locale Id: %3

Property Id: %4

Stack Trace:

�The system failed to load the text filter for parsing a noise word file.

�The system failed to load noise words stream into text filter because text filter does not support IPersistStream.

�The system failed to load noise words stream into text filter because the IPersistStream::Load() function failed.

�The system failed to load noise words stream into text filter because IFilter::Init() function failed.

tOccurrence counter overflow, document is not indexed.

`The filter has caused a sharing violation.

<Microsoft-Windows-Search

Application

�The Windows Search Service has failed to create the new search index. Internal error <%2, %3, %4>. %1

�The Windows Search Service was unable to allocate memory.%1

�An exception occurred in %2. Check other related Event Log messages.%1

�The Windows Search Service has failed to remove the old search index. Internal error <%2,%3>. %1

�The Windows Search Service failed to move Index files from %2 to %3 with the following error: <%4,%5>. This might be because the target directory is not empty, or because the SYSTEM account doesn't have write access to the target directory. %1

�Windows Search Service failed to process the list of included and excluded locations with the error <%2, %3, "%4">. %1

LA configuration error occurred.%1

�Performance monitoring cannot be initialized for the gatherer service, because the counters are not loaded or the shared memory object cannot be opened. This only affects availability of the perfmon counters. Restart the computer.%1

�Performance monitoring cannot be initialized for the gatherer object, because the counters are not loaded or the shared memory object cannot be opened. This only affects availability of the perfmon counters. Restart the computer.%1

tThe entry <%2> cannot be inserted into the history.%1

`The transaction object cannot be created.%1

�The transaction cannot be appended to the queue. File: %2.%1

�The transaction cannot be updated in the queue. File: %2.%1

pThe entry <%2> in the hash map cannot be updated.%1

,An exception occurred. ID: %2. This is an internal error. Reproduce the error with the debugger attached and enable exceptions, then contact product support. One of the components loaded in your system is bad. You may be able to avoid the problem by recreating the index.%1

XThe transaction file cannot be read.%1

�Internal gatherer error %2 occurred. Please contact Microsoft Product Support Services.%1

(Critical error %2 occurred, and the index was shut down. The system is probably low on resources. Free up resources and restart the service.%1

�Advise Status Change failed. The system is probably low on resources. Free up resources and restart the service.%1

LThe URL <%2> cannot be crawled.%1

dThe gatherer object cannot be initialized.%1

dThe plug-in in <%2> cannot be initialized.%1

dThe gatherer service cannot be initialized.%1

TA document ID cannot be allocated.%1

LA document ID cannot be freed.%1

TA new queue file cannot be created.%1

�The registry version does not match with the expected <%2>, or the registry cannot be accessed because the service account does not have the correct permissions. Uninstall the previous version before installing the new one.%1

pThe status change request %2 cannot be processed.%1

TNo documents were accessed because no e-mail address is specified in the content index server properties. Specify the e-mail address in the service configuration.%1

�Unvisited items cannot be deleted from the history after a full update.%1

lThe plug-in manager <%2> cannot be initialized.%1

\The application cannot be initialized.%1

PThe update cannot be initialized.%1

�The index cannot be restored. You may need to delete and recreate the index.%1

�Performance monitoring cannot be initialized for the topic assistant object, because the counters are not loaded or the shared memory object cannot be opened. This only affects availability of the perfmon counters. Restart the computer.%1

pThe application restore failed. This can be caused by system errors (indicated by previously logged events), or a corrupt backup image (retry restore with valid backup image). %1

�The application cannot be backed up. You may be unable to restore from the backup image.%1

pNotifications for the volume %2 are not active. %1

�The protocol handler %2 cannot be loaded. Error description: %3. %1

�Failed to load protocol handler %2. Error description: %3. %1

�The application network access account is invalid. Update the account with a valid username and password. %1

�The gatherer files cannot be flushed, and this action cannot be completed. The gatherer will attempt to flush files again. If the problem persists, restart the service, free system resources or verify that your hardware is working properly. %1

The checkpoint record cannot be updated, and this action cannot be completed. The gatherer will attempt to update the checkpoint record again. If the problem persists, restart the service, free system resources or verify that your hardware is working properly. %1

�The gatherer files cannot be saved, and this action cannot be completed. The gatherer will attempt to save the files again. If the problem persists, restart the service, free system resources or verify that your hardware is working properly. %1

8The gatherer files from the previous checkpoint cannot be restored, and this action cannot be completed. The gatherer will attempt to restore the files again. If the problem persists, restart the service, free system resources or verify that your hardware is working properly. %1

�The checkpoint record cannot be read, and this action cannot be completed. If the problem persists, restart the service, free system resources or verify that your hardware is working properly. %1

pThe project cannot be initialized, because the checkpoint record cannot be read. The data structures on the disk will be reset. Verify that your hardware is working properly. %1

�The project cannot be initialized, because one of the checkpoint files is missing. The data structures on the disk will be reset. Check to see if someone is manually deleting files, and verify that your hardware is working properly. %1

|The gatherer did not connect to the SQLServer instance.%1

�Unable to create file share to accept topic assistant training data. Reason: %2.%1

�Unable to terminate notifications normally. Restart the service or contact Product Support.%1

�Unable to initialize the filter host process. Terminating.%1

lThe filter host process could not be terminated.

�The per-user filter pool for session %2 could not be added.%1

�The per-user filter pool for session %2 could not be removed.%1

�Enumerating user sessions to generate filter pools failed.%1

�The per-user filter pool for session %2 could not be added <%3,%4>.%1

�The audience compilation process cannot start. The error code is "%2" .%1

Error ID %2 happened in Windows Search recovery stage, please restart the service. If this error persists, please recreate the index.%1

�%1A master merge cannot be started for catalog %2 due to error %3.

�%1A master merge cannot be re-started for catalog %2 due to error %3.

lThe schema file <%2> cannot be copied to <%3>.%1

PThe index cannot be initialized.%1

�Directory location <%2> is invalid. The application configuration cannot be read. Reinstall the application.%1

�An error occurred while propagating to search server <%2>.%1

�The update was paused because the disk <%2> is full. Free up disk space to continue crawling the index.%1

`The search server <%2> cannot be removed.%1

�Failed to inform the search server <%2> about a propagation error.%1

�The index cannot be copied, and propagation cannot start.%1

tThe content index server cannot read the registry.%1

\The property store was not initialized.%1

TThe content index cannot be loaded.%1

TThe search service has detected corrupted data files in the index {id=%2}. The service will attempt to automatically correct this problem by rebuilding the index.%1

DThe index cannot be loaded.%1

tPropagation stopped because the propagation state for search server <%2> cannot be read. Try propagation again. If this error persists, delete and recreate the propagated index.%1

�The content index server received an "Access Denied"" error while propagating to the <%2> search server. This usually results from an incorrect configuration of the propagation account. Check that the propagation account is valid.%1

�Performance monitoring cannot be initialized because the counters are not loaded or the shared memory object cannot be opened. Stop and restart the search service. If this error continues, reinstall the application.%1

�Configuration directory %2 is missing, and disaster recovery must be performed. If there are existing indexes, they must be restored from the last backup. If there is no backup of index data, then delete the catalogs and recreate them.%1

$The registry cannot be read, possibly because the registry keys for this index are missing. You may have to delete and recreate the index %1.

XThe content index %1 cannot be removed.

`The Windows Search Service added catalog %1

`The Windows Search Service removed index %1

LIndex propagation failed to commit to any of the search servers. The Windows Search Service is now trying to revert the search servers to the previous index. %1

�The Windows Search Service cannot open the Jet property store.%1

�The Windows Search Service cannot create a Jet property store.%1

�The Windows Search Service cannot load the property store information.%1

pThe search service has failed to create database instance for the index {%1} due to maximum number of instance reached. Please re-configure maximum value and restart the service.

,The search service has failed to configure maximum number of database instance. {%1}. Please re-configure maximum value and restart the service.

�The search service has failed to create or load catalog for an user with SID {%2}. Please inspect a profile directory for the user is accessible. You should re-start the search service after fixing any issue found from the profile directory. %1

�The search service has failed to unload catalog for an user with SID {%2}. %1

XNotification client is not subscribed.

�The content index cannot be read. A content scan will be scheduled after chkdsk or autochk is run.

XThe content index database is corrupt.

TThe content index catalog is corrupt.

XThe content index partition is invalid.

<The priority is invalid.

<There is no starting key.

XThe content index is out of index ids.

0There is no index.

LThe filter buffer cannot be read.

4The index is invalid.

lInconsistency was detected in the property store.

|The content index data on disk is for the wrong version.

hEnumeration was already started for this query.

�The specified variable length property is too large for the property cache.

xThe filtering of the object was stopped by the client.

LThe forward index cannot be read.

xCatalog was created with different diacritic settings.

PThe catalog manager does not exist.

tThe transaction in catalog is found as inconsistent.

�Protected catalog for the user is not available due to key drop status.

�Property Store is not found in the indexer. The possible causes are that the call came during a catalog reset or that the property store plug-in failed to load during indexer initialization.

d4VS_VERSION_INFO��aJaJ?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationXFileDescriptionMicrosoft Tripoli Queryf#FileVersion7.0.19041.1 (WinBuild.160101.0800)6InternalNameTQUERY.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.FOriginalFilenameTQUERY.dll.mui@ProductNameWindows� Search<ProductVersion7.0.19041.1DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX