KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q153597: XADM: Japanese Version Cannot use "Service" as Service Account

Article: Q153597
Product(s): Microsoft Exchange
Version(s): winnt:4.0
Operating System(s): 
Keyword(s): kbsetup
Last Modified: 31-MAR-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Exchange Server, version 4.0, Japanese version 
-------------------------------------------------------------------------------

SYMPTOMS
========

In Microsoft Exchange Japanese version 4.0, running on the Japanese version of
Microsoft Windows NT 3.51, if the Windows NT Primary Domain Controller (PDC) is
Japanese and the Microsoft Exchange Service Account is specified as "service",
Microsoft Exchange will use "NT AUTHORITY\SERVICE" as the Microsoft Exchange
Service Account, rather than "service".

WORKAROUND
==========

You can use any name other than "service" as the Microsoft Exchange Service
Account.

STATUS
======

Microsoft has confirmed this to be a problem in Microsoft Exchange Japanese
version 4.0. We are researching this problem and will post new information here
in the Microsoft Knowledge Base as it becomes available.



Additional query words: Service, Japanese, DBCS

======================================================================
Keywords          : kbsetup 
Technology        : kbHLangJapanese kbExchangeSearch kbExchange400 kbZNotKeyword2
Version           : winnt:4.0

=============================================================================

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.