Non-US Locales Cause Index Server Queries to Not Work (231930)

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/windows/servicepacks/ -or-
152734 how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. 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://support.microsoft.com/directory/overview.asp

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

WORKAROUND

To work around this problem, add a LCID (Locale Identifier) to the connection string.

For example:

cn.ConnectionString = "PROVIDER=msidxs;Locale Identifier=1033" //US English
cn.ConnectionString = "PROVIDER=msidxs;Locale Identifier=1024" //Neutral

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

MORE INFORMATION

This is only a problem when your locale in the Control Panel Regional Settings tool is set to a non-US setting (such as English (Australian)).

Also, this is a know problem in the OLE DB provider for Index Server, Msidxs.dll.