Overview

This article describes the issue and its resolution, which occurs when inconsistent results are returned while searching within GFI Archiver using Chinese, Japanese, or Korean (CJK) languages.

Environment

• GFI Archiver
• Chinese, Japanese or Korean (CJK) environments
  
  

Root Cause

Settings of indexing, word-breaking, and therefore searching are not set to optimal values for Chinese, Japanese, or Korean (CJK) languages.

Resolution

This can be fixed by forcing the indexing engine to index archived items differently.

NOTE: This procedure requires to edit files manually. If edited incorrectly, it can leave the product in a non-operational state. Please keep backups of any file which is edited throughout this article before saving any changes to them.

GFI Archiver 2015 SR1 and newer

1. Open the web page.
2. Navigate to Configuration > Archive Stores > Index Management
3. Ensure that the following option is set/enabled: Enable built-in word breaker (recommended)
4. Open the file ..\GFI\Archiver\Search\Data\product.config in Notepad.
5. Add the following key before the last line </appSettings>:
   <add key="TextFlags" value="36"/>
6. Restart the GFI Archiver Search Service.
7. Rebuild all indexes.
   
   

GFI Archiver 2015 and older

NOTE: It is recommended to upgrade to GFI Archiver 2015 SR1 or newer for this issue. Please consider upgrading instead of following the section below for an old version.

1. Stop GFI Archiver Search Service.
2. Move all files found in ..\GFI\Archiver\Search\Viewers out of this folder (for example, to the desktop).
3. Open the file ..\GFI\Archiver\Search\Data\product.config in Notepad.
4. Add the following key before the last line </appSettings>:
   <add key="TextFlags" value="36"/>
5. Start the GFI Archiver Search Service.
6. Rebuild all indexes.
   
   

IMPORTANT!

• It is not suggested to rebuild all indexes at the same time since it will create extra load on the server to rebuild all indexes at the same time.
• When upgrading to a newer version of GFI Archiver, installation files mentioned in this procedure will be overwritten with default versions making the changes void and ineffective. It is therefore suggested to keep a record of this procedure and follow it once again directly after upgrading to keep this functionality intact.