Membership: DBCS Account Names Not Allowed

Last reviewed: February 3, 1998
Article ID: Q170504

The information in this article applies to:

  • Microsoft Commercial Internet System, version 1.0

SYMPTOMS

An administrator attempts to create a user name in a language that uses the double-byte character set (DBCS), such as Korean, Chinese, Japanese and so on. The administrator creates the user name in Membership Server through the Createusr.asp file; the creation of the account fails.

CAUSE

Membership Server currently only supports the use of standard character languages (for example English, French, German and so on). DBCS account names are not currently supported in Membership Server version 1.0.

RESOLUTION

To resolve this problem:

  • Use an account name in the single-byte character set (SBCS). Because current Internet RFC Standards require that e-mail accounts be in standard SBCS, it may be convenient to give users the same account name as their e-mail address. If using the e-mail address is not acceptable, use another SBCS account name as appropriate.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Commercial Internet System version 1.0. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.


Additional query words: MBS Netscape
Keywords : kbother
Version : 1.0
Platform : winnt
Issue type : kbbug
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.