BUG: DCOMCNFG Fails on a Backup Domain Controller

Last reviewed: June 24, 1997
Article ID: Q170432
The information in this article applies to:

- Microsoft OLE Libraries 4.0 included with:

   - Microsoft Win32 Software Development Kit (SDK)

SYMPTOMS

When using DCOMCNFG.EXE to set the identity of a COM server to a specific user account on a Windows NT server that is a Backup Domain Controller(BDC), it displays an error message "Incorrect Function" or "Invalid Function". When a client attempts to launch the server, the activation fails.

CAUSE

This is caused by a bug in DCOMCNFG.EXE. DCOMCNFG tries to grant a specific right("SeBatchLogonRight") to the user account on the BDC. This is an invalid operation for a BDC because a BDC has a read-only copy of the user accounts database. Any change to the accounts database must be done on the Primary Domain Controller(PDC). Then the change is replicated to the BDC.

RESOLUTION

Use DCOMCNFG to set the COM server to the specific user account. Click OK to dismiss the error message dialog box. Now, while running in a domain administrator's account, use the User Manager for Domains tool on the BDC to grant the "Logon as a batch job" right to the specific user account. This allows the server to be launched in the specific user account (you may need to wait for some time to allow the replication process to take place).

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.


Keywords : BseSecurity LeTwoTls
Version : 4.0
Platform : NT WINDOWS
Issue type : kbbug


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: June 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.