AW: Probleme mit Remote Zugriff auf SQL Server
Ich habe mir gerade noch mal die Dienste angeschaut und gesehen, dass der SQL Server Agent nicht gestartet werden kann !
Vielleicht liegt dort ja der Hund begraben. Ich habe mal den Fehler angehängt und auch die
Log Datei ( s. Screenshot ).
Wie kann ich das Problem beheben ? Habe gerade schon eine "Fixit" Datei von MS runtergeladen und installiert, leider auch ohne Erfolg
Das sagt das Error log:
2015-09-24 18:45:31.35 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2015-09-24 18:45:31.35 Server UTC adjustment: 2:00
2015-09-24 18:45:31.35 Server (c) Microsoft Corporation.
2015-09-24 18:45:31.35 Server All rights reserved.
2015-09-24 18:45:31.35 Server Server process ID is 4796.
2015-09-24 18:45:31.35 Server System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
2015-09-24 18:45:31.35 Server Authentication mode is MIXED.
2015-09-24 18:45:31.35 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.JTLWAWI\MSSQL\Log\ERRORLOG'.
2015-09-24 18:45:31.35 Server The service account is 'NT Service\MSSQL$JTLWAWI'. This is an informational message; no user action is required.
2015-09-24 18:45:31.35 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.JTLWAWI\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.JTLWAWI\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.JTLWAWI\MSSQL\DATA\mastlog.ldf
2015-09-24 18:45:31.35 Server Command Line Startup Parameters:
-s "JTLWAWI"
2015-09-24 18:45:31.85 Server SQL Server detected 1 sockets with 2 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.
2015-09-24 18:45:31.85 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-09-24 18:45:31.85 Server Detected 4031 MB of RAM. This is an informational message; no user action is required.
2015-09-24 18:45:31.85 Server Using conventional memory in the memory manager.
2015-09-24 18:45:31.86 Server Default collation: Latin1_General_CI_AS (Deutsch 1031)
2015-09-24 18:45:31.90 Server Query Store settings initialized with enabled = 1,
2015-09-24 18:45:31.91 Server The maximum number of dedicated administrator connections for this instance is '1'
2015-09-24 18:45:31.91 Server This instance of SQL Server last reported using a process ID of 1704 at 24.09.2015 18:45:24 (local) 24.09.2015 16:45:24 (UTC). This is an informational message only; no user action is required.
2015-09-24 18:45:31.92 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.
2015-09-24 18:45:31.92 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.
2015-09-24 18:45:31.92 Server Software Usage Metrics is disabled.
2015-09-24 18:45:31.93 spid7s Starting up database 'master'.
2015-09-24 18:45:32.02 Server CLR version v4.0.30319 loaded.
2015-09-24 18:45:32.13 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-09-24 18:45:32.57 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-09-24 18:45:32.57 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
<{39B75A24-0837-4CEC-AFDF-B960027AE07E}>RsFxNso initialized. InstanceId = 00000002
<{50080099-5EC4-4EAF-A2A2-63C3DA97F8EB}>FsAgent is initialized
<{09C4480B-DBA4-49B7-956F-68A8B8B2445D}>FsAgent is up and running
2015-09-24 18:45:32.58 spid7s FILESTREAM: effective level = 2 (remote access enabled), configured level = 2, file system access share name = 'JTLWAWI'.
2015-09-24 18:45:32.60 spid7s SQL Trace ID 1 was started by login "sa".
2015-09-24 18:45:32.65 spid7s Server name is 'ESSEN141\JTLWAWI'. This is an informational message only. No user action is required.
2015-09-24 18:45:32.67 spid7s Starting up database 'msdb'.
2015-09-24 18:45:32.67 spid12s Starting up database 'mssqlsystemresource'.
2015-09-24 18:45:32.69 spid12s The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2015-09-24 18:45:32.79 spid15s A self-generated certificate was successfully loaded for encryption.
2015-09-24 18:45:32.80 spid15s Server is listening on [ 'any' <ipv6> 1433].
2015-09-24 18:45:32.80 spid15s Server is listening on [ 'any' <ipv4> 1433].
2015-09-24 18:45:32.80 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\JTLWAWI ].
2015-09-24 18:45:32.80 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$JTLWAWI\sql\query ].
2015-09-24 18:45:32.80 spid15s 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.
2015-09-24 18:45:32.80 spid15s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-09-24 18:45:32.80 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.
2015-09-24 18:45:32.80 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/essen141.startdedicated.de: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.
2015-09-24 18:45:32.80 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/essen141.startdedicated.de: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.
2015-09-24 18:45:32.94 spid12s Starting up database 'model'.
2015-09-24 18:45:33.02 spid12s Clearing tempdb database.
2015-09-24 18:45:33.20 spid12s Starting up database 'tempdb'.
2015-09-24 18:45:33.38 spid18s The Service Broker endpoint is in disabled or stopped state.
2015-09-24 18:45:33.38 spid18s The Database Mirroring endpoint is in disabled or stopped state.
2015-09-24 18:45:33.42 spid18s Service Broker manager has started.
2015-09-24 18:45:33.44 spid7s Recovery is complete. This is an informational message only. No user action is required.
2015-09-24 18:55:31.81 spid18s Service Broker manager has shut down.
2015-09-24 18:55:31.82 spid7s .NET Framework runtime has been stopped.
2015-09-24 18:55:31.99 spid7s 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.
2015-09-24 18:55:32.00 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
