Microsoft KB Archive/247948

From BetaArchive Wiki
Knowledge Base

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

Article ID: 247948

Article Last Modified on 9/23/2005


  • Microsoft Site Server 3.0 Standard Edition
  • Microsoft Site Server 3.0 Commerce Edition

This article was previously published under Q247948

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry


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.


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:

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


To resolve this problem, obtain the latest service pack for Site Server version 3.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

219292 How to Obtain the Latest Site Server 3.0 Service Pack


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 Site Server 3.0 Service Pack 4.


WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

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

  1. Start Registry Editor (Regedt32.exe).
  2. Locate the following key in the registry:

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

     Value Name: dsAutoTranslate
     Data Type: REG_SZ
     Value: NO
  4. Quit Registry Editor.
  5. Restart the LDAP service.

Keywords: kbbug kbfix kbqfe kbsiteserv300sp4fix kbhotfixserver KB247948