Hiiiilllfffeee kann nicht im SQL Managment Studio connecten

[Einzelstueck]

Guten Tag, versuche mich Lokal im managment studio einzuloggen aber es geht nicht .

Das ist der error log

2015-07-28 08:37:44.46 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)

Feb 10 2012 19:39:15

Copyright © Microsoft Corporation

Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2015-07-28 08:37:44.46 Server © Microsoft Corporation.

2015-07-28 08:37:44.46 Server All rights reserved.

2015-07-28 08:37:44.46 Server Server process ID is 3480.

2015-07-28 08:37:44.46 Server System Manufacturer: 'Dell Inc.', System Model: 'Latitude E5540'.

2015-07-28 08:37:44.46 Server Authentication mode is MIXED.

2015-07-28 08:37:44.46 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.

2015-07-28 08:37:44.46 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.

2015-07-28 08:37:44.46 Server Registry startup parameters:

-d c:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf

-e c:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG

-l c:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf

2015-07-28 08:37:44.46 Server Command Line Startup Parameters:

-s "MSSQLSERVER"

2015-07-28 08:37:44.72 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2015-07-28 08:37:44.72 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2015-07-28 08:37:44.72 Server Detected 4001 MB of RAM. This is an informational message; no user action is required.

2015-07-28 08:37:44.72 Server Using conventional memory in the memory manager.

2015-07-28 08:37:44.77 Server This instance of SQL Server last reported using a process ID of 5076 at 28.07.2015 08:37:44 (local) 28.07.2015 06:37:44 (UTC). This is an informational message only; no user action is required.

2015-07-28 08:37:44.77 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f: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-07-28 08:37:44.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.

2015-07-28 08:37:44.78 Server Software Usage Metrics is disabled.

2015-07-28 08:37:44.78 spid7s Starting up database 'master'.

2015-07-28 08:37:44.87 Server CLR version v4.0.30319 loaded.

2015-07-28 08:37:44.91 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.

2015-07-28 08:37:45.12 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

2015-07-28 08:37:45.12 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.

2015-07-28 08:37:45.13 spid7s SQL Trace ID 1 was started by login "sa".

2015-07-28 08:37:45.13 spid7s Server name is 'VKFISBNB02'. This is an informational message only. No user action is required.

2015-07-28 08:37:45.14 spid7s Failed to verify Authenticode signature on DLL 'c:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\ftimport.dll'.

2015-07-28 08:37:45.15 spid7s Starting up database 'msdb'.

2015-07-28 08:37:45.15 spid9s Starting up database 'mssqlsystemresource'.

2015-07-28 08:37:45.15 spid9s The resource database build version is 11.00.2100. This is an informational message only. No user action is required.

2015-07-28 08:37:45.17 spid9s Starting up database 'model'.

2015-07-28 08:37:45.19 spid9s Clearing tempdb database.

2015-07-28 08:37:45.25 spid9s Starting up database 'tempdb'.

2015-07-28 08:37:45.32 spid12s A self-generated certificate was successfully loaded for encryption.

2015-07-28 08:37:45.32 spid12s Server is listening on [ 'any' <ipv6> 1433].

2015-07-28 08:37:45.32 spid12s Server is listening on [ 'any' <ipv4> 1433].

2015-07-28 08:37:45.32 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].

2015-07-28 08:37:45.32 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].

2015-07-28 08:37:45.33 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.

2015-07-28 08:37:45.33 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-07-28 08:37:45.33 spid12s SQL Server is now ready for client connections. This is an informational message; no user action is required.

2015-07-28 08:37:45.33 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/VKFISBNB02 ] 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-07-28 08:37:45.33 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/VKFISBNB02: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-07-28 08:37:45.34 spid15s The Service Broker endpoint is in disabled or stopped state.

2015-07-28 08:37:45.34 spid15s The Database Mirroring endpoint is in disabled or stopped state.

2015-07-28 08:37:45.34 spid15s Service Broker manager has started.

2015-07-28 08:37:45.35 spid7s Recovery is complete. This is an informational message only. No user action is required.

[Einzelstueck]

TCP ist aktiviert

[Einzelstueck]

Netzwerkbezogener oder instsanzspezifischer Fehler beim Herstellen einer Verbindung mit SQL Server........error 25, (microsoft SQL Server, Fehler:87 )

[Mttkrb]

Guten Morgen,

ist der Port 1433 in der Firewall freigegeben?

gruß

Jogibaer0411

PS: Deine Tastatur scheint defekt zu sein. Du solltest diese mal tauschen. ;-)

[Einzelstueck]

ja unter wf.msc habe ich als eingehende regel port 1433 freigegeben.

Ich hatte es vorher installiert, hab einen instanz namen gegeben. Habe alles dann deinstalliert, und neuinstalliert mit default instanz Namen.

Seit dem kann ich nicht mehr connecten.

Habe alles deinstalliert und alle ordner die mit SQL zutun hatten gelöscht.

[Einzelstueck]

Aber ich hatte vorher auch kein Port freigegeben und es lief.

Habe das jetzt aus verzweifelung gemacht :-(

Wenn ich das Managment studio starte, hat er auch die falsche instanz ( xxxx\SQLEXPRESS )

statt xxxx\MSSQLSERVER ( den default den ich genommen haben ).

[Mttkrb]

Du kannst beim Verbinden auch explizit eine Instanz angeben. Was dort in der Vorauswahl steht kann überschrieben werden.

[Einzelstueck]

Jep habe ich ja, also die defualt instanz MSSQLSERVER. mit Windows authetifizierung, habe auch mixed mode eingestellt. Komme weder mit SA noch mit Windows Benutzer rein

[Einzelstueck]

Habe auch SQL Server dienst neugestartet nachdem ich TCP/IP aktiviert habe... ist zum verzweifeln :\

[Einzelstueck]

Glaube habe den Fehler gefunden ?

Wenn ich unter Servername nur mein Lokalen Rechner angebe z.b MeinPc1 , und verbinde über windows authentifizierung dann gehts.

Wenn ich aber MeinPc1\MSSQLSERVER , also die Instanz angebe dann gehts nicht.

[Einzelstueck]

Alles klar! Funktioniert!