首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >如何修复错误“SQL Server (MSSQLSERVER)自动停止?

如何修复错误“SQL Server (MSSQLSERVER)自动停止?
EN

Stack Overflow用户
提问于 2016-05-24 15:11:15
回答 5查看 23.1K关注 0票数 0

我无法登录我的SQL服务器。当我尝试连接它时,收到此错误消息。

建立与SQL Server的连接时发生与网络有关的错误或特定于实例的错误。服务器找不到或无法访问。请验证实例名称是否正确,以及SQL Server是否配置为允许远程连接。(提供程序:命名管道提供程序,错误: 40 -无法打开到SQL Server的连接) (Microsoft SQL Server,错误: 2)

当我查看SQL Server配置管理器时,我观察到我的"SQL SERVER (MSSQLSERVER)“在几秒钟内被自动停止。我已经尝试开始了,但还是被停止了。

有没有人对此有任何想法。

在此处输入图像描述

这里的错误日志也

代码语言:javascript
复制
> 2016-05-24 12:56:11.01 Server      Microsoft SQL Server 2014 -
> 12.0.4213.0 (Intel X86)   Jun  9 2015 12:17:04    Copyright (c) Microsoft Corporation     Standard Edition on Windows NT 6.1  (Build
> 7601: ) (WOW64)
> 
> 2016-05-24 12:56:11.01 Server      UTC adjustment: 5:30 2016-05-24
> 12:56:11.01 Server      (c) Microsoft Corporation. 2016-05-24
> 12:56:11.01 Server      All rights reserved. 2016-05-24 12:56:11.01
> Server      Server process ID is 3840. 2016-05-24 12:56:11.01 Server  
> System Manufacturer: 'Gigabyte Technology Co., Ltd.', System Model:
> 'To be filled by O.E.M.'. 2016-05-24 12:56:11.01 Server     
> Authentication mode is MIXED. 2016-05-24 12:56:11.01 Server     
> Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft
> SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'. 2016-05-24
> 12:56:11.01 Server      The service account is 'NT
> Service\MSSQLSERVER'. This is an informational message; no user action
> is required. 2016-05-24 12:56:11.01 Server      Registry startup
> parameters:    -d C:\Program Files (x86)\Microsoft SQL
> Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf   -e C:\Program Files
> (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG      -l
> C:\Program Files (x86)\Microsoft SQL
> Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf 2016-05-24
> 12:56:11.01 Server      Command Line Startup Parameters:   -s
> "MSSQLSERVER" 2016-05-24 12:56:11.23 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. 2016-05-24 12:56:11.23 Server      SQL Server is starting at
> normal priority base (=7). This is an informational message only. No
> user action is required. 2016-05-24 12:56:11.23 Server      Detected
> 3989 MB of RAM. This is an informational message; no user action is
> required. 2016-05-24 12:56:11.23 Server      Using conventional memory
> in the memory manager. 2016-05-24 12:56:11.24 Server      Buffer pool
> extension is not supported on the 32-bit architecture. 2016-05-24
> 12:56:11.24 Server      Default collation:
> SQL_Latin1_General_CP1_CI_AS (us_english 1033) 2016-05-24 12:56:11.26
> Server      The maximum number of dedicated administrator connections
> for this instance is '1' 2016-05-24 12:56:11.26 Server      This
> instance of SQL Server last reported using a process ID of 2632 at
> 5/24/2016 12:51:45 PM (local) 5/24/2016 7:21:45 AM (UTC). This is an
> informational message only; no user action is required. 2016-05-24
> 12:56:11.26 Server      Node configuration: node 0: CPU mask:
> 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a
> description of the NUMA configuration for this computer. This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:11.26 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.
> 2016-05-24 12:56:11.27 Server      Software Usage Metrics is disabled.
> 2016-05-24 12:56:11.27 spid11s     Starting up database 'master'.
> 2016-05-24 12:56:11.31 spid11s     28 transactions rolled forward in
> database 'master' (1:0). This is an informational message only. No
> user action is required. 2016-05-24 12:56:11.31 spid11s     0
> transactions rolled back in database 'master' (1:0). This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:11.37 Server      CLR version v4.0.30319 loaded. 2016-05-24
> 12:56:11.41 Server      Common language runtime (CLR) functionality
> initialized using CLR version v4.0.30319 from
> C:\Windows\Microsoft.NET\Framework\v4.0.30319\. 2016-05-24 12:56:11.52
> spid11s     SQL Server Audit is starting the audits. This is an
> informational message. No user action is required. 2016-05-24
> 12:56:11.52 spid11s     SQL Server Audit has started the audits. This
> is an informational message. No user action is required. 2016-05-24
> 12:56:11.53 spid11s     SQL Trace ID 1 was started by login "sa".
> 2016-05-24 12:56:11.53 spid11s     Server name is 'AZURE'. This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:11.66 spid17s     A new instance of the full-text filter daemon
> host process has been successfully started. 2016-05-24 12:56:11.81
> spid19s     Starting up database 'msdb'. 2016-05-24 12:56:11.81
> spid20s     Starting up database 'ReportServer'. 2016-05-24
> 12:56:11.81 spid21s     Starting up database 'ReportServerTempDB'.
> 2016-05-24 12:56:11.81 spid16s     A self-generated certificate was
> successfully loaded for encryption. 2016-05-24 12:56:11.81 spid22s    
> Starting up database '360IT'. 2016-05-24 12:56:11.81 spid23s    
> Starting up database 'True_Athuntication_Release_1'. 2016-05-24
> 12:56:11.82 spid16s     Server is listening on [ 'any'  1433].
> 2016-05-24 12:56:11.82 spid16s     Server is listening on [ 'any'
>  1433]. 2016-05-24 12:56:11.82 spid16s     Server local
> connection provider is ready to accept connection on [
> \\.\pipe\SQLLocal\MSSQLSERVER ]. 2016-05-24 12:56:11.82 spid16s    
> Server named pipe provider is ready to accept connection on [
> \\.\pipe\sql\query ]. 2016-05-24 12:56:11.82 Server      Server is
> listening on [ ::1  1434]. 2016-05-24 12:56:11.82 Server     
> Server is listening on [ 127.0.0.1  1434]. 2016-05-24
> 12:56:11.82 Server      Dedicated admin connection support was
> established for listening locally on port 1434. 2016-05-24 12:56:11.82
> spid16s     SQL Server is now ready for client connections. This is an
> informational message; no user action is required. 2016-05-24
> 12:56:11.82 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. 2016-05-24 12:56:11.82 Server      The SQL Server Network
> Interface library could not register the Service Principal Name (SPN)
> [ MSSQLSvc/azure ] 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. 2016-05-24 12:56:11.82 Server     
> The SQL Server Network Interface library could not register the
> Service Principal Name (SPN) [ MSSQLSvc/azure: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. 2016-05-24 12:56:11.83 spid24s     Starting up database
> 'True_Talent__staging_Release_1'. 2016-05-24 12:56:11.83 spid12s    
> Starting up database 'mssqlsystemresource'. 2016-05-24 12:56:11.83
> spid35s     Starting up database 'pkk'. 2016-05-24 12:56:11.83 spid32s
> Starting up database 'True_Athuntication_ver_1'. 2016-05-24
> 12:56:11.83 spid30s     Starting up database 'truehrms_actualdata'.
> 2016-05-24 12:56:11.83 spid31s     Starting up database
> 'TRUEHRM_DEMO'. 2016-05-24 12:56:11.83 spid27s     Starting up
> database 'True_Talent_Internal_1'. 2016-05-24 12:56:11.83 spid29s    
> Starting up database 'DEMO_TEST'. 2016-05-24 12:56:11.83 spid28s    
> Starting up database 'ATSAuthentication_live'. 2016-05-24 12:56:11.83
> spid25s     Starting up database 'True_Athuntication_Internal_1'.
> 2016-05-24 12:56:11.83 spid33s     Starting up database
> 'True_Talent_ver_1'. 2016-05-24 12:56:11.83 spid34s     Starting up
> database 'hrmlog'. 2016-05-24 12:56:12.05 spid12s     The resource
> database build version is 12.00.4100. This is an informational message
> only. No user action is required. 2016-05-24 12:56:12.87 spid21s     1
> transactions rolled forward in database 'ReportServerTempDB' (6:0).
> This is an informational message only. No user action is required.
> 2016-05-24 12:56:12.92 spid29s     1 transactions rolled forward in
> database 'DEMO_TEST' (13:0). This is an informational message only. No
> user action is required. 2016-05-24 12:56:12.97 spid34s     1
> transactions rolled forward in database 'hrmlog' (18:0). This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:13.23 spid23s     1 transactions rolled forward in database
> 'True_Athuntication_Release_1' (8:0). This is an informational message
> only. No user action is required. 2016-05-24 12:56:13.29 spid28s     2
> transactions rolled forward in database 'ATSAuthentication_live'
> (12:0). This is an informational message only. No user action is
> required. 2016-05-24 12:56:13.48 spid21s     0 transactions rolled
> back in database 'ReportServerTempDB' (6:0). This is an informational
> message only. No user action is required. 2016-05-24 12:56:13.50
> spid12s     Recovery completed for database mssqlsystemresource
> (database ID 32767) in 1 second(s) (analysis 380 ms, redo 0 ms, undo
> 218 ms.) This is an informational message only. No user action is
> required. 2016-05-24 12:56:13.60 spid29s     0 transactions rolled
> back in database 'DEMO_TEST' (13:0). This is an informational message
> only. No user action is required. 2016-05-24 12:56:13.60 spid28s     0
> transactions rolled back in database 'ATSAuthentication_live' (12:0).
> This is an informational message only. No user action is required.
> 2016-05-24 12:56:13.83 spid25s     49 transactions rolled forward in
> database 'True_Athuntication_Internal_1' (10:0). This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:13.86 spid35s     Recovery completed for database pkk (database
> ID 19) in 1 second(s) (analysis 165 ms, redo 0 ms, undo 216 ms.) This
> is an informational message only. No user action is required.
> 2016-05-24 12:56:14.15 spid23s     0 transactions rolled back in
> database 'True_Athuntication_Release_1' (8:0). This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:14.15 spid23s     Recovery completed for database
> True_Athuntication_Release_1 (database ID 8) in 1 second(s) (analysis
> 261 ms, redo 0 ms, undo 276 ms.) This is an informational message
> only. No user action is required. 2016-05-24 12:56:14.76 spid34s     0
> transactions rolled back in database 'hrmlog' (18:0). This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:14.76 spid34s     Recovery completed for database hrmlog
> (database ID 18) in 2 second(s) (analysis 186 ms, redo 89 ms, undo
> 1171 ms.) This is an informational message only. No user action is
> required. 2016-05-24 12:56:14.94 spid20s     1 transactions rolled
> forward in database 'ReportServer' (5:0). This is an informational
> message only. No user action is required. 2016-05-24 12:56:15.17 Logon
> Error: 18456, Severity: 14, State: 38. 2016-05-24 12:56:15.17 Logon   
> Login failed for user 'NT SERVICE\ReportServer'. Reason: Failed to
> open the explicitly specified database 'ReportServer'. [CLIENT:
> fe80::4cb1:8acf:dce2:e32a%11] 2016-05-24 12:56:15.23 spid32s     1
> transactions rolled forward in database 'True_Athuntication_ver_1'
> (16:0). This is an informational message only. No user action is
> required. 2016-05-24 12:56:15.47 spid25s     0 transactions rolled
> back in database 'True_Athuntication_Internal_1' (10:0). This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:15.47 spid25s     Recovery completed for database
> True_Athuntication_Internal_1 (database ID 10) in 1 second(s)
> (analysis 264 ms, redo 50 ms, undo 1412 ms.) This is an informational
> message only. No user action is required. 2016-05-24 12:56:15.66
> spid20s     0 transactions rolled back in database 'ReportServer'
> (5:0). This is an informational message only. No user action is
> required. 2016-05-24 12:56:15.77 spid12s     Starting up database
> 'model'. 2016-05-24 12:56:15.81 spid32s     0 transactions rolled back
> in database 'True_Athuntication_ver_1' (16:0). This is an
> informational message only. No user action is required. 2016-05-24
> 12:56:16.30 spid12s     Error: 9003, Severity: 20, State: 1.
> 2016-05-24 12:56:16.30 spid12s     The log scan number (35:376:1)
> passed to log scan in database 'model' is not valid. This error may
> indicate data corruption or that the log file (.ldf) does not match
> the data file (.mdf). If this error occurred during replication,
> re-create the publication. Otherwise, restore from backup if the
> problem results in a failure during startup. 2016-05-24 12:56:16.30
> spid12s     SQL Server shutdown has been initiated 2016-05-24
> 12:56:16.30 spid12s     SQL Trace was stopped due to server shutdown.
> Trace ID = '1'. This is an informational message only; no user action
> is required.
EN

回答 5

Stack Overflow用户

发布于 2016-05-24 15:18:00

这很可能是SQL Server服务的问题。您的服务可能处于已停止状态。

要解决此问题,请使用以下步骤:

  1. 按窗口按钮+R
  2. Services.msc类型
  3. 搜索SQL Server服务
  4. 选择您的SQL Server服务实例,然后单击左面板上的start。
  5. 通过右键单击,在属性中将此服务设置为自动启动/延迟启动。

希望这能解决你的问题。如果仍然无法连接到SQL Server,请检查实例的错误日志。假设是默认实例,则应在C:\Program Files\Microsoft SQL Server\MSSQL11.SQLSERVER2012\MSSQL\Log中查找

如果没有任何帮助,您的安装似乎确实被破坏了。我会在Installation Center中尝试repair选项。

你也可以从这里

票数 2
EN

Stack Overflow用户

发布于 2016-05-24 16:04:33

传递到数据库中日志扫描的日志扫描编号(35:376:1)‘'model’无效。此错误可能表示数据损坏或日志文件(.ldf)与数据文件(.mdf)不匹配。如果在复制过程中发生此错误,请重新创建publication.Otherwise;如果问题导致在启动过程中失败,请从备份还原。

所以原因是你的model数据库已损坏。重新安装、修复或在链接答案中使用提示:

https://serverfault.com/a/497488/229754

重新创建损坏的模型数据库可能很棘手,因为您需要使用启动标志–T3608 –T3608和SQLCMD如下所述。

票数 1
EN

Stack Overflow用户

发布于 2020-07-23 15:16:24

转到您的服务器的服务实例开始-->服务->您的服务器尝试启动依赖"SQL server代理“,如果启动,则启动您的服务器实例。如果启动服务器代理失败,请转到服务器代理属性(右键单击,然后单击属性),提供您的pC密码,应用,然后尝试启动。它应该可以工作

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/37406698

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档