Index Server Process Terminates Unexpectedly with Japanese Wordbreaker

ID: Q227881

The information in this article applies to:

Microsoft Index Server version 1.1

SYMPTOMS

The Japanese Wordbreaker feature may cause the Index Server process to terminate unexpectedly.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Date      Time                 Size    File name     Platform
   -------------------------------------------------------------
   01/05/99  06:34p               122,961 Msir2jp.dll   (Alpha)
   01/05/99  06:34p             1,218,388 Msir2jp.lex   (Alpha)


   01/05/99  06:33p                86,097 Msir2jp.dll   (i386)
   01/05/99  06:33p             1,218,388 Msir2jp.lex   (i386)

These files replace the Nlgwbrkr.dll file.

NOTE: You must run the following command from a command prompt after installing the fix:

Regsvr32 /s MSIR2JP.DLL

STATUS

Microsoft has confirmed this to be a problem in Index Server version 1.1.

MORE INFORMATION

Index Server has the ability to search text in multiple languages. The Wordbreaker is part of the technology that allows Index Server to do that.

This problem does not occur with the version of the Japanese Wordbreaker feature included in Index Server 2.0.

The Japanese Wordbreaker version 1.0 was packaged in a DLL named Nlgwbrkr.dll. The fix for this problem is to replace the Wordbreaker version 1.0 with the Wordbreaker version 2.0. The Wordbreaker 2.0 is packaged in a DLL named Msir2jp.dll and has an associated data file named Msir2p.lex. Register the DLL with Regsvr32 to handle the file name differences.

Additional query words: 4.00 crash crashes c rashed

Keywords : kbbug4.00 kbfix4.00
Version : winnt:1.1
Platform : winnt
Issue type : kbbug