Announcement

Collapse
No announcement yet.

SQL Server is terminating due to 'stop' request from Service Control Manager.

Collapse
X
Collapse
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    SQL Server is terminating due to 'stop' request from Service Control Manager.

    Hallo,
    wenn ich bei mir die MSDE mit einen benamten Instanz installieren will, bekomme ich den folgenden Fehler:
    <PRE>
    SQL Server is terminating due to 'stop' request from Service Control Manager.
    </PRE>

    Was heißt das?

    <PRE>
    server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
    Dec 17 2002 14:22:05
    Copyright (c) 1988-2003 Microsoft Corporation
    Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 3)

    server Copyright (C) 1988-2002 Microsoft Corporation.
    server All rights reserved.
    server Server Process ID is 3448.
    server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL$WEBFACTORY\LOG\ERRORLOG'.
    server SQL Server is starting at priority class 'normal'(1 CPU detected).
    server SQL Server configured for thread mode processing.
    server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
    spid3 Warning ******************
    spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
    spid3 Starting up database 'master'.
    server Using 'SSNETLIB.DLL' version '8.0.760'.
    spid5 Starting up database 'model'.
    spid3 Server name is 'W2K-ANDREAS\WEBFACTORY'.
    spid3 Skipping startup of clean database id 5
    spid3 Skipping startup of clean database id 6
    spid3 Starting up database 'msdb'.
    spid5 Clearing tempdb database.
    server SQL server listening on 192.168.0.75: 1349.
    server SQL server listening on 127.0.0.1: 1349.
    server SQL server listening on TCP, Shared Memory, Named Pipes.
    server SQL Server is ready for client connections
    spid5 Starting up database 'tempdb'.
    spid3 Warning ******************
    spid3 Attempting to change default collation to Latin1_General_CI_AS.
    spid3 Clustered index restored for master.sysdatabases.
    spid3 Non-clustered index restored for master.sysobjects.
    spid3 Non-clustered index restored for master.sysobjects.
    spid3 index restored for master.syscolumns.
    spid3 index restored for master.systypes.
    spid3 index restored for master.sysusers.
    spid3 index restored for master.sysproperties.
    spid3 index restored for master.sysfulltextcatalogs.
    spid3 index restored for master.sysxlogins.
    spid3 index restored for master.sysdevices.
    spid3 index restored for master.sysservers.
    spid3 index restored for master.syslanguages.
    spid3 index restored for master.syscharsets.
    spid3 index restored for master.sysfilegroups.
    spid3 index restored for master.spt_values.
    spid3 index restored for master.MSreplication_options.
    spid3 index restored for master.spt_datatype_info_ext.
    spid3 index restored for master.spt_datatype_info.
    spid3 Non-clustered index restored for tempdb.sysobjects.
    spid3 Non-clustered index restored for tempdb.sysobjects.
    spid3 index restored for tempdb.syscolumns.
    spid3 index restored for tempdb.systypes.
    spid3 index restored for tempdb.sysusers.
    spid3 index restored for tempdb.sysproperties.
    spid3 index restored for tempdb.sysfulltextcatalogs.
    spid3 index restored for tempdb.sysfilegroups.
    spid3 Non-clustered index restored for model.sysobjects.
    spid3 Non-clustered index restored for model.sysobjects.
    spid3 index restored for model.syscolumns.
    spid3 index restored for model.systypes.
    spid3 index restored for model.sysusers.
    spid3 index restored for model.sysproperties.
    spid3 index restored for model.sysfulltextcatalogs.
    spid3 index restored for model.sysfilegroups.
    spid3 Non-clustered index restored for msdb.sysobjects.
    spid3 Non-clustered index restored for msdb.sysobjects.
    spid3 index restored for msdb.syscolumns.
    spid3 index restored for msdb.systypes.
    spid3 index restored for msdb.sysusers.
    spid3 index restored for msdb.sysproperties.
    spid3 index restored for msdb.sysfulltextcatalogs.
    spid3
    Tags: None
  • #2
    Hallo,

    der SCM (Service Control Manager) ist der Betriebssystem-Bestandteil, der für das Starten/Pausieren/Wiederanfahren/Stoppen von Diensten zuständig ist. Die oben genannte Meldung bedeutet, dass die MSDE vom SCM die Aufforderung zum Herunterfachen (Stop) erhalten hat, so dass der eigene Dienst beendet wird.

    &gt;..SQL Server started in single user mode. Updates allowed to system catalogs.

    Das hört sich nicht mach dem Normalfall an. Anscheinend stecken die Datenbanken mitten in einem Restrukturierungs-Prozess, der nicht erfolgreich abgearbeitet werden kann. Im Normalfall sieht das Log etwa so aus:
    <pre>
    2004-04-05 06:21:45.78 server Microsoft SQL Server 2000 - 8.00.384 (Intel X86)
    May 23 2001 00:02:52
    Copyright (c) 1988-2000 Microsoft Corporation
    Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)

    2004-04-05 06:21:45.80 server Copyright (C) 1988-2000 Microsoft Corporation.
    2004-04-05 06:21:45.80 server All rights reserved.
    2004-04-05 06:21:45.80 server Server Process ID is 1424.
    2004-04-05 06:21:45.80 server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL$NetSDK\LOG\ERRORLOG'.
    2004-04-05 06:21:45.84 server SQL Server is starting at priority class 'normal'(1 CPU detected).
    2004-04-05 06:21:46.02 server SQL Server configured for thread mode processing.
    2004-04-05 06:21:46.03 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
    2004-04-05 06:21:46.12 spid3 Starting up database 'master'.
    2004-04-05 06:21:46.94 server Using 'SSNETLIB.DLL' version '8.0.382'.
    2004-04-05 06:21:46.94 spid5 Starting up database 'model'.
    2004-04-05 06:21:47.06 spid3 Server name is 'P4XP\NETSDK'.
    2004-04-05 06:21:47.06 spid3 Skipping startup of clean database id 4
    2004-04-05 06:21:47.06 spid3 Skipping startup of clean database id 5
    2004-04-05 06:21:47.06 spid3 Skipping startup of clean database id 6
    2004-04-05 06:21:47.06 spid3 Skipping startup of clean database id 7
    2004-04-05 06:21:47.06 spid3 Skipping startup of clean database id 8
    2004-04-05 06:21:47.09 server SQL server listening on 192.168.1.12: 1063.
    2004-04-05 06:21:47.09 server SQL server listening on 127.0.0.1: 1063.
    2004-04-05 06:21:47.15 server SQL server listening on TCP, Shared Memory, Named Pipes.
    2004-04-05 06:21:47.17 server SQL Server is ready for client connections
    2004-04-05 06:21:47.77 spid5 Clearing tempdb database.
    2004-04-05 06:21:52.10 spid5 Starting up database 'tempdb'.
    2004-04-05 06:21:53.03 spid3 Recovery complete.
    </pre&gt

    Comment

    • #3
      Und was kann ich tun, damit es funktioniert. Ich habe alles deinstalliert. Es sollte nichts mehr auf den PC sein (wenns funktioniert hat). Ich habe nichts von Hand gelöscht / geändert

      Comment

      • #4
        Hallo,

        &gt;Und was kann ich tun, damit es funktioniert.

        Wenn alle Datenbanken (inklusive MASTER) neu angelegt werden, sollte dieser Spuk verschwinden

        Comment

        Previous template Next
        Working...
        X