SQL Server der WaWi beendet sich

[Mike79]

Seit der neuen Version der WaWi 0.99714 beendet sich während des Arbeitens der SQL Server.
Die WaWi stürzt dann klarerweise mit einem Fehler ab.

Es läuft noch ein zweiter Dienst meines Logistikpartners, der aber ohne Probleme funktioniert.
Ich muss dann den SQL Server Dienst der WaWi neu starten und dann läuft es stabil.

Habe bisher noch nicht herausgefunden, ob eine gewisse Aktion dies verursacht, aber es ist meist 5 bis 10 Minuten, nachdem ich mich das erste Mal in die WaWi eingeloggt habe

 

[Janusch]

AW: SQL Server der WaWi beendet sich

Hallo,

Bitte im SQL-Server log (Ordner ..../MSSQL/Logs/) prüfen ob dort etwas steht.
Weiterhin die Ereignisanzeige kann Hinweise auf Probleme mit System / Anwendungen geben.

Wenn der Dienst selber beendet wird, deutet dies meist auf schwerwiegende Systemfehler hin. Imemr Backup der Datenabnken erstellen.

 

[Mike79]

AW: SQL Server der WaWi beendet sich

Hier mal das Logfi von gestern:

2011-01-30 10:23:25.11 Server Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
Nov 24 2008 13:01:59
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.1 (Build 7600: )
2011-01-30 10:23:25.48 Server (c) 2005 Microsoft Corporation.
2011-01-30 10:23:25.48 Server All rights reserved.
2011-01-30 10:23:25.48 Server Server process ID is 1808.
2011-01-30 10:23:25.48 Server Authentication mode is MIXED.
2011-01-30 10:23:25.48 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\ LOG\ERRORLOG'.
2011-01-30 10:23:25.48 Server This instance of SQL Server last reported using a process ID of 11988 at 29.01.2011 23:24:49 (local) 29.01.2011 22:24:49 (UTC). This is an informational message only; no user action is required.
2011-01-30 10:23:25.48 Server Registry startup parameters:
2011-01-30 10:23:25.51 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2011-01-30 10:23:25.51 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2011-01-30 10:23:25.51 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2011-01-30 10:23:25.51 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-01-30 10:23:25.51 Server Detected 2 CPUs. This is an informational message; no user action is required.
2011-01-30 10:23:30.91 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-01-30 10:23:31.72 Server Database mirroring has been enabled on this instance of SQL Server.
2011-01-30 10:23:31.75 spid5s Starting up database 'master'.
2011-01-30 10:23:32.22 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-01-30 10:23:32.27 spid5s SQL Trace ID 1 was started by login "sa".
2011-01-30 10:23:32.31 spid5s Starting up database 'mssqlsystemresource'.
2011-01-30 10:23:32.34 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2011-01-30 10:23:32.80 spid8s Starting up database 'model'.
2011-01-30 10:23:34.10 Server A self-generated certificate was successfully loaded for encryption.
2011-01-30 10:23:34.10 Server Server is listening on [ 'any' <ipv6> 49222].
2011-01-30 10:23:34.10 Server Server is listening on [ 'any' <ipv4> 49222].
2011-01-30 10:23:34.10 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\JTLWAWI ].
2011-01-30 10:23:34.10 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$JTLWAWI\sql\query ].
2011-01-30 10:23:35.01 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2011-01-30 10:23:35.02 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2011-01-30 10:23:35.02 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-01-30 10:23:35.13 spid5s Server name is 'BURN\JTLWAWI'. This is an informational message only. No user action is required.
2011-01-30 10:23:35.13 spid5s Starting up database 'msdb'.
2011-01-30 10:23:37.15 spid8s Clearing tempdb database.
2011-01-30 10:23:46.44 spid8s Starting up database 'tempdb'.
2011-01-30 10:23:46.86 spid5s Recovery is complete. This is an informational message only. No user action is required.
2011-01-30 10:23:46.88 spid11s The Service Broker protocol transport is disabled or not configured.
2011-01-30 10:23:46.88 spid11s The Database Mirroring protocol transport is disabled or not configured.
2011-01-30 10:23:46.95 spid11s Service Broker manager has started.
2011-01-30 10:25:12.18 Server Server resumed execution after being idle 50 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-01-30 10:25:12.41 spid51 Starting up database 'eazybusiness'.
2011-01-30 14:07:12.95 Server Server resumed execution after being idle 12256 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-01-30 14:56:20.88 Server Server resumed execution after being idle 1485 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-01-30 18:12:15.12 Server Server resumed execution after being idle 10064 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-01-30 19:52:00.66 Server Server resumed execution after being idle 3091 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-01-30 20:25:13.72 Server Server resumed execution after being idle 968 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-01-30 22:03:41.79 Server Server resumed execution after being idle 3893 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-01-30 22:06:34.53 spid20s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-01-30 22:06:37.78 spid20s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-01-30 22:06:37.94 spid20s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-01-30 22:11:09.98 spid11s Service Broker manager has shut down.
2011-01-30 22:11:11.21 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2011-01-30 22:11:11.26 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

 

[Janusch]

AW: SQL Server der WaWi beendet sich

Hallo,

Ursache kann hier verschieden sein. Von zu enig virt. Speicher bis hin zu defekten Netzwerkkarten.

Da hilft nur nach
"SQL Server is terminating in response to a 'stop' request from Service Control Manager"
googeln un ddie einzelnen Fälle zu prüfen.