none
SQL Datenbank funktioniert erst nach Neustarten des Dienstes wieder. RRS feed

 > 

  • Allgemeine Diskussion

  • Discussion
    Anmelden
    0
    Anmelden

    Hallo

    Folgendes Problem:

    Wir verwalten auf deinem SBS2008 Server eine MSSQL 2008 Datenbank. Der Server wird nicht von uns Administriert!

    Alle 30 bis 50 Tage hängt sich der SQL-Dienst auf. Der Client hat keine Verbinundg mehr zur Datenbank. Der Server-Dienst muss neu gestartet werden. Dann läuft es wieder.

    Weiss jemand bescheid? Habe schon div. Lösungsansätze ausgeführt jedoch noch ohne Erfolg. Es ist schwer zu sagen ob eine Lösung funktioniert weil das Problem selten auftriff.

    Folgendes befindet sich jeweil im Log:

    2013-10-05 00:59:54.53 spid1s      Server resumed execution after being idle 29140 seconds. Reason: timer event.

    2013-10-05 08:15:41.19 Server      Server resumed execution after being idle 25226 seconds: user activity awakened the server. This is an informational message only. No user action is required.

    2013-10-05 08:15:41.20 spid51      Starting up database 'europa3000'.

    2013-10-05 09:01:01.03 Server      Server resumed execution after being idle 1040 seconds: user activity awakened the server. This is an informational message only. No user action is required.

    2013-10-05 09:01:01.06 spid51      Starting up database 'europa3000'.

    2013-10-05 09:18:55.89 spid51      Starting up database 'europa3000'.

    2013-10-05 09:19:11.13 spid51      Error: 17204, Severity: 16, State: 1.

    2013-10-05 09:19:11.13 spid51      FCB::Open failed: Could not open file E:\Daten\europa3000\FT3\data\db\europa3000_Data_log.LDF for file number 2.  OS error: 32(failed to retrieve text for this error. Reason: 15100).

    2013-10-05 09:19:11.22 spid51      Error: 5105, Severity: 16, State: 1.

    2013-10-05 09:19:11.22 spid51      A file activation error occurred. The physical file name 'E:\Daten\europa3000\FT3\data\db\europa3000_Data_log.LDF' may be incorrect. Diagnose and correct additional errors, and retry the operation.

    2013-10-05 09:19:11.33 spid51      Error: 5170, Severity: 16, State: 1.

    2013-10-05 09:19:11.33 spid51      Cannot create file 'E:\Daten\europa3000\FT3\data\db\europa3000_Data_log.LDF' because it already exists. Change the file path or the file name, and retry the operation.

    2013-10-05 09:19:11.35 spid51      Error: 5170, Severity: 16, State: 1.

    2013-10-05 09:19:11.35 spid51      Cannot create file 'E:\Daten\europa3000\FT3\data\db\europa3000_Data_log.LDF' because it already exists. Change the file path or the file name, and retry the operation.

    2013-10-05 09:19:11.44 Logon       Error: 18456, Severity: 14, State: 38.

    2013-10-05 09:19:11.44 Logon       Login failed for user 'SAG\marlis.schelbert'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.119]

    2013-10-05 09:19:14.23 Logon       Error: 18456, Severity: 14, State: 38.

    2013-10-05 09:19:14.23 Logon       Login failed for user 'SAG\marlis.schelbert'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.119]

    2013-10-05 09:19:21.74 Logon       Error: 18456, Severity: 14, State: 38.

    2013-10-05 09:19:21.74 Logon       Login failed for user 'SAG\marlis.schelbert'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.119]

    2013-10-05 10:38:48.19 Server      Server resumed execution after being idle 3849 seconds: user activity awakened the server. This is an informational message only. No user action is required.

    2013-10-05 10:38:48.20 Logon       Error: 18456, Severity: 14, State: 38.

    2013-10-05 10:38:48.20 Logon       Login failed for user 'SAG\marlis.schelbert'. Reason: Failed to open the explicitly specified database. [CLIENT: 192.168.0.119]

    • Typ geändert Ciprian Bogdan Dienstag, 11. März 2014 20:38 Keine Rückmeldung des Fragenstellender
    Montag, 7. Oktober 2013 09:31
    |

Alle Antworten