Host Account Cache Requires Configuration of Master/Backup Role

 Last reviewed: April 14, 1997
Article ID: Q164912
The information in this article applies to:
  • Microsoft SNA Server for Windows NT version 3.0

SYMPTOMS

When you install the SNA Server Host Account Cache service (SnaDatabase) on a Windows NT Primary Domain Controller (PDC) or Backup Domain Controller (BDC) server (using the SNA Server Host Security Setup program), the administrator must manually configure the role as master or backup.

CAUSE

The SNA Server Host Account Cache service relies on static configuration of its role.

RESOLUTION

An update to SNA Server 3.0 is available to correct this problem.

The SNA Host Account Cache service (for example, SnaDatabase) now regularly checks the following two conditions:

  • It determines whether its role within the registry has been changed by checking the following registry key: 

          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SnaDatabase\
      Parameters\Master: REG_DWORD:  (1 = master, 0 = backup/secondary)
  • If determines whether the computer on which it is running has become a Windows NT PDC or has been demoted to a BDC.

If either condition is true (with the registry setting taking precedence), the SnaDatabase service performs an internal shutdown and restarts in the new role.

Also, the Host Account Cache role dialog has been removed from the Host Security setup script.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0. This problem was corrected in the latest Microsoft SNA Server 3.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Keywords : kbbug3.00 kbfix3.00.sp1 kbnetwork prodsna
Version : 3.0
Platform : winnt
Issue type : kbbug
Resolution 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: April 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.