Site Configuration Manager Does Not Start After System Reboot

 Last reviewed: April 24, 1997
Article ID: Q141237
The information in this article applies to:
  • Microsoft Systems Management Server versions 1.0, 1.1, and 1.2

SYMPTOMS

After you shutdown and restart Systems Management Server, Site Configuration Manager service does not start.

CAUSE

This problem occurs if your computer does the following: 

   - Slow disk and memory throughout
   - Constant paging to disk as Windows NT and Systems Management
     Server services are loading
   - Many applications are starting during startup
Site Configuration Manager may time out due to the above configuration.

WORKAROUND

To work around this problem:

  1. Start applications manually. Do not start applications during Windows NT startup.

  2. Reduce the number of Windows NT Server services to start automatically. You may start the default Windows NT Server services automatically.

  3. Increase disk and memory throughput. This may require hardware upgrades such as hard disk and controller with faster data transfer rate, and additional memory.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server versions 1.0, 1.1 and 1.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: prodsms
Keywords : kbbug1.00 kbbug1.10 kbbug1.20 kbnetwork smssiteconfigman
Version : 1.0 1.1 1.2
Platform : WINDOWS

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