sqlserv.exe lauscht nicht - Client kann nicht connecten SQL Server 2012 Hilfe!

Neodym

Sehr aktives Mitglied
13. Februar 2012
1.167
95
Berlin
Hallo,
wir haben den vorherigen Clienten zum Server gemacht und den vorherigen Server zum Clienten.
Da haben wir gleich mal beim neuen Server vom SQL 2008 auf Server SQL 2012 upgegradet. .bak-datei eingebunden und die Warenwirtschaft 0.99923 auf dem neuen Server funktioniert nun tadellos. (win7/64bit)

NUR: Sämtliche Clienten im Netzwerk können nicht zu dem neuen Server connecten.
Ich habe die ODBC-Verbindungen angepasst, die Servernamen, Firewall aus und mehrfach alles neu gestartet - es geht nicht.
Der ODBC - Test funktioniert auch nicht.
Also habe ich auf dem Server den netstat-Befehl mit einer output.txt eingegeben.
Dort findet sich keine sqlserv.exe die lauscht. Es lauscht dort gar kein SQL Server!

Im SQL Konfigurationsprogramm ist TCP/IP aktiviert.

Was mache ich falsch?
 

L.Mechler

Gut bekanntes Mitglied
14. August 2013
183
1
AW: sqlserv.exe lauscht nicht - Client kann nicht connecten SQL Server 2012 Hilfe!

Hi,

du musst den Dienst "SQL Server Browser" starten und Starttyp auf automatisch stellen damit du verbinden kannst, der steht soweit ich weiß standartmäßig auf manuell. Findest du unter "Verwaltung"->"Dienste"
 

ag-websolutions.de

Sehr aktives Mitglied
29. Dezember 2009
14.548
232
AW: sqlserv.exe lauscht nicht - Client kann nicht connecten SQL Server 2012 Hilfe!

Der SQL SERVER BROWSER Dienst ist für den Betrieb der WaWi nicht erforderlich
 

Neodym

Sehr aktives Mitglied
13. Februar 2012
1.167
95
Berlin
AW: sqlserv.exe lauscht nicht - Client kann nicht connecten SQL Server 2012 Hilfe!

Ja ich habe eine feste IP vergeben und ja ich habe ihn mal neu gestartet.

Das gibt der Errorlog aus:


Code: 
2015-06-26 10:30:00.47 Server      Microsoft SQL Server 2012 - 11.0.2100.60 (X64) 
    Feb 10 2012 19:39:15 
    Copyright (c) Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2015-06-26 10:30:00.47 Server      (c) Microsoft Corporation.
2015-06-26 10:30:00.47 Server      All rights reserved.
2015-06-26 10:30:00.47 Server      Server process ID is 2136.
2015-06-26 10:30:00.47 Server      Authentication mode is MIXED.
2015-06-26 10:30:00.47 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL11.JTLWAWI\MSSQL\Log\ERRORLOG'.
2015-06-26 10:30:00.48 Server      The service account is 'NT Service\MSSQL$JTLWAWI'. This is an informational message; no user action is required.
2015-06-26 10:30:00.48 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
2015-06-26 10:30:00.48 Server      Command Line Startup Parameters:
     -s "JTLWAWI"
2015-06-26 10:30:02.24 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-06-26 10:30:02.24 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-06-26 10:30:02.24 Server      Detected 3992 MB of RAM. This is an informational message; no user action is required.
2015-06-26 10:30:02.24 Server      Using conventional memory in the memory manager.
2015-06-26 10:30:02.56 Server      This instance of SQL Server last reported using a process ID of 2152 at 26.06.2015 10:29:32 (local) 26.06.2015 08:29:32 (UTC). This is an informational message only; no user action is required.
2015-06-26 10:30:02.56 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-06-26 10:30:02.57 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-06-26 10:30:02.59 Server      Software Usage Metrics is disabled.
2015-06-26 10:30:02.62 spid8s      Starting up database 'master'.
2015-06-26 10:30:02.73 Server      CLR version v4.0.30319 loaded.
2015-06-26 10:30:03.08 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-06-26 10:30:03.23 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-06-26 10:30:03.23 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-06-26 10:30:03.28 spid8s      SQL Trace ID 1 was started by login "sa".
2015-06-26 10:30:03.29 spid8s      Server name is 'SERV-PC\JTLWAWI'. This is an informational message only. No user action is required.
2015-06-26 10:30:03.64 spid12s     A self-generated certificate was successfully loaded for encryption.
2015-06-26 10:30:03.67 spid12s     Server is listening on [ 'any' <ipv6> 1433].
2015-06-26 10:30:03.68 spid12s     Server is listening on [ 'any' <ipv4> 1433].
2015-06-26 10:30:03.69 spid12s     Server is listening on [ 'any' <ipv6> 49275].
2015-06-26 10:30:03.71 spid12s     Server is listening on [ 'any' <ipv4> 49275].
2015-06-26 10:30:03.75 spid12s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\JTLWAWI ].
2015-06-26 10:30:03.76 spid12s     Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$JTLWAWI\sql\query ].
2015-06-26 10:30:03.79 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-06-26 10:30:03.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-06-26 10:30:03.80 spid12s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-06-26 10:30:03.80 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Serv-PC: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-06-26 10:30:03.80 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Serv-PC: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-06-26 10:30:13.24             Fehler: 18456, Schweregrad: 14, Status: 38.
2015-06-26 10:30:13.24             Login failed for user 'NT SERVICE\ReportServer$JTLWAWI'.Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank 'ReportServer$JTLWAWI'. [CLIENT: <local machine>]
2015-06-26 10:30:15.50             Fehler: 18456, Schweregrad: 14, Status: 38.
2015-06-26 10:30:15.50             Login failed for user 'NT SERVICE\ReportServer$JTLWAWI'.Ursache: Fehler beim Öffnen der explizit angegebenen Datenbank 'ReportServer$JTLWAWI'. [CLIENT: <local machine>]
2015-06-26 10:30:17.47 spid13s     A new instance of the full-text filter daemon host process has been successfully started.
2015-06-26 10:30:17.75 spid9s      Starting up database 'mssqlsystemresource'.
2015-06-26 10:30:17.75 spid16s     Starting up database 'msdb'.
2015-06-26 10:30:17.75 spid17s     Starting up database 'ReportServer$JTLWAWI'.
2015-06-26 10:30:17.78 spid9s      The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
2015-06-26 10:30:17.82 spid17s     1 transactions rolled forward in database 'ReportServer$JTLWAWI' (5:0). This is an informational message only. No user action is required.
2015-06-26 10:30:17.83 spid17s     0 transactions rolled back in database 'ReportServer$JTLWAWI' (5:0). This is an informational message only. No user action is required.
2015-06-26 10:30:17.83 spid9s      Starting up database 'model'.
2015-06-26 10:30:17.91 spid9s      Clearing tempdb database.
2015-06-26 10:30:18.11 spid9s      Starting up database 'tempdb'.
2015-06-26 10:30:18.26 spid18s     The Service Broker endpoint is in disabled or stopped state.
2015-06-26 10:30:18.26 spid18s     The Database Mirroring endpoint is in disabled or stopped state.
2015-06-26 10:30:18.30 spid18s     Service Broker manager has started.
2015-06-26 10:30:18.45 spid8s      Recovery is complete. This is an informational message only. No user action is required.
2015-06-26 10:30:21.10 spid51      Starting up database 'ReportServer$JTLWAWI'.
2015-06-26 10:30:22.12 spid51      Starting up database 'ReportServer$JTLWAWITempDB'.
2015-06-26 10:30:23.10 spid53      Starting up database 'ReportServer$JTLWAWITempDB'.


da funktioniert irgendwas nicht.
 
Du musst Dich einloggen oder registrieren um hier antworten zu können.
Top Bottom