Simptomi
Pretpostavimo da koristite Microsoft SQL Server 2012 ili SQL Server 2014. Kada dođe do zastoja u sistemu SQL Server, dobijate sledeću povredu pristupa koju izaziva monitor sa mrtve tačke:
sqldk! CSlotGroup::P shReleasesqldk! CSlotPageMgr::Releasesqllang!commondeletesqllang!delete[]sqllang! CTraceDataSTVF::InternalReleaseResourcessqllang! TTableBase<CTraceDataSTVFInfo>::ReleaseResourcessqllang! CTraceDataSTVF::{dtor}sqllang! CTraceDataSTVF::'s scalar brisanje destructor'sqlmin! CSTVFInternal::Releasesqlmin! CQueryExecContext::~CQueryExecContextsqlmin! CQueryInstance::ShutdownQueryExecContextsqlmin! CQueryScan::ShutdownQueryExecContextsqlmin! CQueryScan::D estroyQueryOnExceptionsqllang! CXStmtQuery::ShutdownOnExceptionsqllang! CXStmtQuery::FinishOnExceptionImpsqllang! GetInterruptTickssqllang! InterruptTicks<nepotpisani __int64>::LoadTickssqllang! SOS_Ticks<InterruptTicks<unsigned __int64>,-3>::LoadTickssqllang!'CMsqlExecContext::FExecute':'1':catch$3msvcr100!_CallSettingFramemsvcr100!__CxxCallCatchBlockntdll! RcFrameConsolidationsqllang! CMsqlExecContext::FExecutesqllang! CSQLSource::Executesqllang! CStmtExecProc::XretLocalExecsqllang! CStmtExecProc::XretExecExecutesqllang! CXStmtExecProc::XretExecutesqllang! CExecStmtLoopVars::ExecuteXStmtAndSetXretReturnsqllang! CMsqlExecContext::ExecuteStmts<1,0>sqllang! CMsqlExecContext::FExecutesqllang! CSQLSource::Executesqllang! IzvršiteSqlsqllang! CSpecProc::ExecuteSpecialsqllang! CSpecProc::Executesqllang!process_requestsqllang!process_commandssqldk! SOS_Task::P aram::Executesqldk! SOS_Scheduler::RunTasksqldk! SOS_Scheduler::P rocessTaskssqldk! PlanerManager::WorkerEntryPointsqldk! SystemThread::RunWorkersqldk! SystemThreadDispatcher::P rocessWorkersqldk! PlanerManager::ThreadEntryPointkernel32! BaseThreadInitThunkntdll! RtlUserThreadStart
Nakon kršenja prava pristupa, dobijate sledeću poruku o grešci iz evidencije grešaka sistema SQL Server:
<Date> <Time> spid<ID> Using 'dbghelp.dll' version '4.0.5'<Date> <Time> spid> <0 ID> **Dump thread - spid = <ID>, EC = 0x0000007F8608E160> <4 Date> <Time> spid> <8 ID> ***Stack Dump is sent to <File Path>\<Dump FileName>.txt> <4 Date> <Time> spid> <8 ID> * > < <*******************************************************************************************************************************************************************************************************************************************************************************************> Time spid> <4 ID> *<Date> <Time> spid<ID> * BEGIN STACK DUMP:<Date> <Time> spid<ID> * <Date> <Time> spid <ID><Date> <Time> spid> <8 ID> *<Date> <Time> spid> <4 ID> * Location: qxcntxt.cpp:1143> <6 Date> <Time> spid> <0 ID> * Expression : !" No exceptions should be raised by this code"<Date> <Time> spid> <6 ID> * SPID: <ID><Date> <Time> spid> <4 ID> * Process ID: 3556> <6 Date> <Time> spid><0 ID> *<Date> <Time> spid><6 ID> * Input Buffer 37 bytes -<Date> <Time> spid> <02 ID> * 16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00> <04 Date> <Time> spid> <08 ID> * ÿÿ & 01 00 00 00 ff ff 0c 00 00 00 00 00 26 04 04 05 00 00> <1 Date> <Time> spid> <5 ID> * 00> <7 Date> <Time> spid> <1 ID> * <Date> <Time> spid> <7 ID> *...<Date> <Time> spid> <3 ID> Stack Signature for the dump is 0x000000014202549F> <5 Date> <Time> spid> <9 ID> [INFO] Početak identiteta | State Result Error Speculate Prepared LazyCommit ReadOnly | ID niti baze transakcija | ReadSet WriteSet ScanSet Savepoint LogSizeRq | CommitDep TotalComm Dependent 0 Dependent 1 Dependent 2 Dependent 3 Dependent 4 Dependent 5 Dependent 6 Dependent 7 | Lokacija oblasti |> <41 Date> <Time> spid> <45 ID> Timeout waiting for external dump process 11800.<Date> <Time> spid> <1 ID> Error: 17066, Ozbiljnost: 16, Stanje: 1.<Datum> <Vreme> spid> <7 ID> SQL Server Tvrdnja: Datoteka: <qxcntxt.cpp>, line=1143 Neuspela potvrda = '!" Nijedan izuzetak ne bi trebalo da bude podignut ovim kodom"'' Ova greška je možda povezana sa vremenskim rasporedom. Ako greška potraje i nakon ponovnog pokretanja izjave, koristite DBCC CHECKDB da biste proverili da li u bazi podataka postoji strukturni integritet ili ponovo pokrenite server da biste se uverili da strukture podataka u memoriji nisu oštećene.
Rešenje
Kumulativne informacije o ažuriranju
Problem je prvi put otklonjen u sledećoj kumulativnoj ispravki sistema SQL Server.
Svaka nova kumulativna ispravka za SQL Server sadrži sve hitne ispravke i sve bezbednosne ispravke koje su bile uključene u prethodnu kumulativnu ispravku. Preporučujemo da preuzmete i instalirate najnovije kumulativne ispravke za SQL Server:
Status
Microsoft je potvrdio da je ovo problem u Microsoft proizvodima koji su navedeni u odeljku "Odnosi se na".
