c# - Sqlserver.exe has stopped working -
since installing visual studio 2015 update 3 have been getting below error. happens when visual studio 2015 open , happens whether running local admin or not. frequent , irritating, not seem affect work doing. code, server explorer, vs work fine bat error messages popping , microsoft error reporting taking long periods of 50% usage of cpu in process.
does know how fix this? don't want spend hours trying resolve it.
error message:
in application event log see following:
fault bucket 126419871336, type 5 event name: sqlexception64 response: not available cab id: 0
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:
attached files: \?\c:\users\m_f\appdata\local\microsoft\microsoft sql server local db\instances\projectsv13\sqldump0100.mdmp \?\c:\users\m_f\appdata\local\microsoft\microsoft sql server local db\instances\projectsv13\sqldump0100.txt \?\c:\users\m_f\appdata\local\microsoft\microsoft sql server local db\instances\projectsv13\sqldump0100.log \?\c:\programdata\microsoft\windows\wer\temp\were021.tmp.werinternalmetadata.xml
these files may available here: c:\programdata\microsoft\windows\wer\reportarchive\critical_sqlservr.exe_7113a987f49ac660cb71f97cb4183ea19827ef0_00000000_0bd7e949
analysis symbol: rechecking solution: 0 report id: 3e38065a-5d62-11e6-89a7-97ade4354400 report status: 1 hashed bucket: ff995718a61d049a3664662b84518798
and in sql log:
process 49 generated fatal exception c0000005 exception_access_violation. sql server terminating process.
is seems have been known issue - see this microsoft kb article says has been patched.
my system date possible in terms of os, patches, security updates, visual studio updates etc still see issue. has solved before , can save me frustration trying sorted!
thanks
there ongoing thread crash on microsoft's msdn forum:
apparently, crash occurs after upgrading recent version of ssdt (14.0.60525.0).
a microsoft employee suggested fix:
we've investigated , believe happens when query store feature enabled in database in localdb server. can work around problem disabling query store feature in localdb database instances. find names of databases have query store enabled, run query:
select [name] sys.databases is_query_store_on=1
then each database, disable query store executing query so:
alter database dbname set query_store=off
some reported did not fix issue them, others did, success may vary.
see microsoft employee kevin cunnane's comment below:
the fixed localdb.msi included in august release - available msdn.microsoft.com/en-us/library/mt204009.aspx update via visual studio extensions , updates channel due in next few weeks.
Comments
Post a Comment