Sqlserver.exe 已停止工作 [英] Sqlserver.exe has stopped working
问题描述
自从安装 Visual Studio 2015 Update 3 以来，我一直收到以下错误.它仅在 Visual Studio 2015 打开时发生，并且无论我是否以本地管理员身份运行都会发生.它很频繁而且很烦人，但似乎不会影响我正在做的任何工作.代码、服务器资源管理器、VS 都可以正常工作，但弹出的错误消息和 Microsoft 错误报告在此过程中占用了我 50% 的 CPU 使用率.
Since installing Visual Studio 2015 Update 3 I have been getting the below error. It happens only when Visual Studio 2015 is open and happens whether I am running as a local admin or not. It is frequent and is irritating, but does not seem to affect any work that I am doing. Code, Server Explorer, VS all work fine bat the error messages popping up and Microsoft Error Reporting taking up long periods of 50% usage of my CPU in the process.
有谁知道如何解决这个问题?我不想花几个小时试图解决它.
Does anyone know how to fix this? I don't want to spend hours trying to resolve it.
错误信息:
在我的应用程序事件日志中，我看到以下内容:
故障存储区 126419871336，类型 5 事件名称:SQLException64 响应:不可用驾驶室 ID:0
Fault bucket 126419871336, type 5 Event Name: SQLException64 Response: Not available Cab Id: 0
问题签名:P1:sqlservr.exe P2:0.0.0.0 P3:0000000000000000P4:sqlmin.dll P5:2015.130.1601.5 P6:000000005724AE98 P7:-1073741819 P8:0000000000064BB2 P9:00000001D8D946AB P10:
Problem signature: P1: sqlservr.exe P2: 0.0.0.0 P3: 0000000000000000 P4: sqlmin.dll P5: 2015.130.1601.5 P6: 000000005724AE98 P7: -1073741819 P8: 0000000000064BB2 P9: 00000001D8D946AB P10:
附加文件:?C:Usersm_fAppDataLocalMicrosoftMicrosoft SQL服务器本地 DBInstancesProjectsV13SQLDump0100.mdmp?C:Usersm_fAppDataLocalMicrosoftMicrosoft SQL Server 本地DBInstancesProjectsV13SQLDump0100.txt?C:Usersm_fAppDataLocalMicrosoftMicrosoft SQL Server 本地DBInstancesProjectsV13SQLDump0100.log?C:ProgramDataMicrosoftWindowsWERTempWERE021.tmp.WERInternalMetadata.xml
Attached files: ?C:Usersm_fAppDataLocalMicrosoftMicrosoft SQL Server Local DBInstancesProjectsV13SQLDump0100.mdmp ?C:Usersm_fAppDataLocalMicrosoftMicrosoft SQL Server Local DBInstancesProjectsV13SQLDump0100.txt ?C:Usersm_fAppDataLocalMicrosoftMicrosoft SQL Server Local DBInstancesProjectsV13SQLDump0100.log ?C:ProgramDataMicrosoftWindowsWERTempWERE021.tmp.WERInternalMetadata.xml
这些文件可以在这里找到:C:ProgramDataMicrosoftWindowsWERReportArchiveCritical_sqlservr.exe_7113a987f49ac660cb71f97cb4183ea19827ef0_00000000_0bd7e949
These files may be available here: C:ProgramDataMicrosoftWindowsWERReportArchiveCritical_sqlservr.exe_7113a987f49ac660cb71f97cb4183ea19827ef0_00000000_0bd7e949
分析符号:重新检查溶液:0 报告 ID:3e38065a-5d62-11e6-89a7-97ade4354400 报告状态:1 散列存储桶:ff995718a61d049a3664662b84518798
Analysis symbol: Rechecking for solution: 0 Report ID: 3e38065a-5d62-11e6-89a7-97ade4354400 Report Status: 1 Hashed bucket: ff995718a61d049a3664662b84518798
并在 SQL 日志中:
进程49产生致命异常c0000005EXCEPTION_ACCESS_VIOLATION.SQL Server 正在终止此进程.
Process 49 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
这似乎也是一个已知问题 - 请参阅这篇 Microsoft KB 文章 说它已被修补.
Is also seems to have been a known issue - see this Microsoft KB Article that says it has been patched.
我的系统在操作系统、补丁、安全更新、Visual Studio 更新等方面尽可能保持最新状态，但我仍然看到问题.希望有人之前已经解决了这个问题，并且可以让我在尝试对其进行排序时避免一些挫折！
My system is as up to date as possible in terms of OS, patches, security updates, Visual Studio updates etc but I still see the issue. Hopefully someone has solved this before and can save me some frustration trying to get it sorted!
谢谢
推荐答案
Microsoft 的 MSDN 论坛上有一个关于此崩溃的持续主题:
There is an ongoing thread about this crash on Microsoft's MSDN forum:
显然，此崩溃是在升级到最新版本的 SSDT (14.0.60525.0) 后发生的.
Apparently, this crash occurs after upgrading to the most recent version of SSDT (14.0.60525.0).
一位 Microsoft 员工建议将此作为修复:
A Microsoft employee suggested this as a fix:
我们已经调查并相信在 localdb 服务器的任何数据库中启用查询存储功能时会发生这种情况.您可以通过在所有 localdb 数据库实例中禁用查询存储功能来解决此问题.要查找启用了查询存储的数据库的名称，请运行以下查询:
We've investigated and believe that this happens when the query store feature is enabled in any database in the localdb server. You can work around this problem by disabling the query store feature in all localdb database instances. To find the names of databases that have query store enabled, run this query:
select [name] from sys.databases where is_query_store_on=1
然后对于每个数据库，通过执行如下查询来禁用查询存储:
Then for each database, disable query store by executing a query like so:
alter database DBNAME set query_store=off
有些人报告说这并没有为他们解决问题，其他人则说确实如此，因此您的成功可能会有所不同.
Some reported this did not fix the issue for them, others that it did, so your success may vary.
请参阅下面的 Microsoft 员工 Kevin Cunnane 的评论:
See Microsoft employee Kevin Cunnane's comment below:
修复的 LocalDB.msi 包含在 8 月版本中 - 可从 msdn.microsoft.com/en-us/library/mt204009.aspx 获得，并在接下来的几周内通过 Visual Studio 扩展和更新频道进行更新.
The fixed LocalDB.msi is included in the August release - available from msdn.microsoft.com/en-us/library/mt204009.aspx with update via the Visual Studio Extensions and Updates channel due in the next few weeks.
这篇关于Sqlserver.exe 已停止工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
