Verwiesen an Support Datenbankproblem nach NetFramework Update

[Burnsi]

Hallo liebe User,
nach einem automatischen Update von NetFramework geht gar nichts mehr, die Datenbank schein verschwunden und er startet nicht mal mehr das Server Management Studio

Hier das Fehlerprotokoll...habe schon viel versucht, bin jetzt am Ende von meinem Wissen, ich brauche dringend wieder Zugriff...leider habe ich die letzte Sicherung verpennt, aber das spielt erst Mal keine Rolle

2017-08-01 12:26:45.80 Server      Microsoft SQL Server 2012 (SP3-GDR) (KB3194721) - 11.0.6248.0 (X64)
    Sep 23 2016 15:49:43
    Copyright (c) Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2017-08-01 12:26:45.90 Server      (c) Microsoft Corporation.
2017-08-01 12:26:45.90 Server      All rights reserved.
2017-08-01 12:26:45.91 Server      Server process ID is 2120.s
2017-08-01 12:26:45.91 Server      System Manufacturer: 'Dell Inc.', System Model: 'OptiPlex GX620'.
2017-08-01 12:26:45.95 Server      Authentication mode is MIXED.
2017-08-01 12:26:45.96 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.JTLWAWI\MSSQL\Log\ERRORLOG'.
2017-08-01 12:26:45.96 Server      The service account is 'NT Service\MSSQL$JTLWAWI'. This is an informational message; no user action is required.
2017-08-01 12:26:45.98 Server      Registry startup parameters:
     -d C:\Program Files\Microsoft SQL Server\MSSQL11.JTLWAWI\MSSQL\DATA\master.mdf
     -e C:\Program Files\Microsoft SQL Server\MSSQL11.JTLWAWI\MSSQL\Log\ERRORLOG
     -l C:\Program Files\Microsoft SQL Server\MSSQL11.JTLWAWI\MSSQL\DATA\mastlog.ldf
2017-08-01 12:26:45.98 Server      Command Line Startup Parameters:
     -s "JTLWAWI"
2017-08-01 12:27:16.36 Server      SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-08-01 12:27:16.37 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-08-01 12:27:16.37 Server      Detected 3574 MB of RAM. This is an informational message; no user action is required.
2017-08-01 12:27:16.45 Server      Using conventional memory in the memory manager.
2017-08-01 12:27:28.66 Server      This instance of SQL Server last reported using a process ID of 132 at 22.07.2017 08:21:18 (local) 22.07.2017 06:21:18 (UTC). This is an informational message only; no user action is required.
2017-08-01 12:27:28.76 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-08-01 12:27:28.77 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.
2017-08-01 12:27:28.79 Server      Software Usage Metrics is disabled.
2017-08-01 12:27:29.50 spid7s      Starting up database 'master'.
2017-08-01 12:27:31.54 Server      CLR version v4.0.30319 loaded.
2017-08-01 12:27:34.26 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-08-01 12:27:34.54 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-08-01 12:27:37.60 spid7s      SQL Trace ID 1 was started by login "sa".
2017-08-01 12:27:38.03 spid7s      Server name is 'SERVER\JTLWAWI'. This is an informational message only. No user action is required.
2017-08-01 12:27:38.88 spid7s      Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.JTLWAWI\MSSQL\Binn\ftimport.dll'.
2017-08-01 12:27:38.99 spid7s      Starting up database 'msdb'.
2017-08-01 12:27:38.99 spid9s      Starting up database 'mssqlsystemresource'.
2017-08-01 12:27:39.22 spid9s      The resource database build version is 11.00.6020. This is an informational message only. No user action is required.
2017-08-01 12:27:39.39 spid12s     A self-generated certificate was successfully loaded for encryption.
2017-08-01 12:27:39.51 spid12s     Server is listening on [ 'any' <ipv6> 1433].
2017-08-01 12:27:39.51 spid12s     Server is listening on [ 'any' <ipv4> 1433].
2017-08-01 12:27:39.52 spid12s     Server is listening on [ 'any' <ipv6> 50649].
2017-08-01 12:27:39.52 spid12s     Server is listening on [ 'any' <ipv4> 50649].
2017-08-01 12:27:39.54 spid12s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\JTLWAWI ].
2017-08-01 12:27:39.54 spid12s     Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$JTLWAWI\sql\query ].
2017-08-01 12:27:39.55 spid12s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2017-08-01 12:27:39.61 spid12s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-08-01 12:27:39.61 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2017-08-01 12:27:39.61 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Server:JTLWAWI ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2017-08-01 12:27:39.61 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Server:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2017-08-01 12:27:40.73 spid9s      Starting up database 'model'.
2017-08-01 12:27:42.27 spid9s      Clearing tempdb database.
2017-08-01 12:27:45.07 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2017-08-01 12:27:46.82 spid9s      Starting up database 'tempdb'.
2017-08-01 12:27:47.48 spid15s     The Service Broker endpoint is in disabled or stopped state.
2017-08-01 12:27:47.53 spid15s     The Database Mirroring endpoint is in disabled or stopped state.
2017-08-01 12:27:48.45 spid15s     Service Broker manager has started.
2017-08-01 12:27:48.61 spid7s      Recovery is complete. This is an informational message only. No user action is required.
2017-08-01 13:08:26.74 Server      Server resumed execution after being idle 814 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2017-08-01 13:08:29.33 spid51      Starting up database 'eazybusiness'.
2017-08-01 13:08:35.60 spid53      Starting up database 'eazybusiness'.
2017-08-01 13:19:09.65 spid51      Starting up database 'eazybusiness'.
2017-08-01 13:19:41.06 spid53      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2017-08-01 13:19:41.12 spid53      Configuration option 'max server memory (MB)' changed from 950 to 950. Run the RECONFIGURE statement to install.
2017-08-01 13:19:41.13 spid53      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2017-08-02 01:00:49.21 spid4s      Server resumed execution after being idle 35842 seconds. Reason: timer event.
2017-08-02 03:15:25.22 Server      SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2017-08-02 03:15:28.85 spid7s      Server resumed execution after being idle 7063 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2017-08-02 03:15:29.40 spid7s      Error: 17054, Severity: 16, State: 1.
2017-08-02 03:15:29.40 spid7s      The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
2017-08-02 03:15:33.39 spid15s     Service Broker manager has shut down.
2017-08-02 03:15:36.53 spid7s      .NET Framework runtime has been stopped.
2017-08-02 03:15:42.82 spid7s      SQL Server shutdown has been initiated
2017-08-02 03:15:42.86 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

 

[Rico Giesler]

Bitte direkt an den Support wenden. Die Kollegen schauen sich das an.