DBCS Data May Not Be Stored Correctly in the Membership Directory After MDAC 2.1 Update

ID: Q247948

The information in this article applies to:

Microsoft Site Server version 3.0
Microsoft Site Server version 3.0, Commerce Edition

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

After updating the MDAC 2.1 or later version on Site Server 3.0 LDAP Server, DBCS characters may not be stored correctly in the Membership Directory if SQL Server does not have the same code page as LDAP Server.

CAUSE

When using the MDAC 2.1 or later version, the SQL Server ODBC driver (version 3.70.0623 or later) or the OLEDB provider (version 7.01.0623 or later) translates character data from the client code page to the server code page automatically by default. This may cause a problem between Site Server LDAP and SQL server for Membership Directory if each server has the different code page. For more information on Auto translation, you can refer to the following Microsoft Knowledge Base article:

Q234748 PRB: SQL Server ODBC Driver Converts Language Events to Unicode

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 Site Server 3.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    Version       Size     File name     Platform
   ---------------------------------------------------------------
   12-4-99  02:59a  7.0.1280.0    399,120   storedb.dll   x86
   12-4-99  02:57a  7.0.1280.0    490,768   storedb.dll   alpha

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

After installing Site Server 3.0 Service Pack 3 and the above hotfix, you should perform the following steps:

Start Registry Editor (Regedt32.exe).

Locate the following key in the registry:


HKLM\SYSTEM\CurrentControlSet\Services\LDAPSVC\Parameters

On the Edit menu, click Add Value, and then add the following registry value:


 Value Name: dsAutoTranslate
 Data Type: REG_SZ
 Value: NO

Quit Registry Editor.

Restart the LDAP service.

Additional query words:

Keywords :
Version : winnt:3.0
Platform : winnt
Issue type : kbbug