Forum

Bildirimler

Hepsini Temizle

SQL Server is terminating because of fatal exception c0000005

SQL Server

Son Cevaplar gön: ahmet151 16 yıl önce

7 Yazılar

3 Üyeler

0 Reactions

1,361 Görüntüleme

RSS

ahmet151

(@ahmet151)

Gönderiler: 11

Active Member

Konu başlatıcı

arkadaşlar son zamanlarda bu hata sık sık tekrarlanır oldu. sql 2005 std kullanıyoruz. bu hatanın tam olarak neden kaynaklandığını ve çözümünü bilen arkadaşlar varsa yardım rica ediyorum. teşekkürler.

SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).

bununla birlikte bu hataları da verdi

SQL Server Assertion: File: <srvproc.cpp>, line=288 Failed Assertion = '1 <= cTrackedRef'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.

Error: 7884, Severity: 20, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

Gönderildi : 29/04/2009 15:07

Sinan KAHRAMAN

(@sinankahraman)

Gönderiler: 5225

Illustrious Member

http://support.microsoft.com/kb/918222/en-us?spid=2855 inceler misiniz?

Gönderildi : 29/04/2009 15:26

ahmet151

(@ahmet151)

Gönderiler: 11

Active Member

Konu başlatıcı

çok teşekkür ederim. eline sağlık

Gönderildi : 29/04/2009 15:52

Sinan KAHRAMAN

(@sinankahraman)

Gönderiler: 5225

Illustrious Member

Rica ederiz.

Gönderildi : 29/04/2009 16:39

ahmet151

(@ahmet151)

Gönderiler: 11

Active Member

Konu başlatıcı

hocam çok pardon

ban bu tolları indirdim ama kudrurmuyor

kurulum sırasında "this setup program dedected the following sql server 2005 fetures.

diyor. ilerisine gidemiyoruz

sanırım tespit ettim diyor ve update için seçim yaptırmıyor.

Gönderildi : 29/04/2009 19:26

Hatice AKGUL

(@haticeakgul)

Gönderiler: 983

Noble Member

15 Aralık 2008 de SQL Server 2005 SP3(9.0.4035) yayınlamıştır. http://www.microsoft.com/downloads/details.aspx?FamilyId=AE7387C3-348C-4FAA-8AE5-949FDFBE59C4&displaylang=en

SQL Server Service Pack ve Cumulative Update lerinin listesini http://sqlserverbuilds.blogspot.com/ adresinde bulabilirsiniz.

Bu service pack ile SQL Serverda ortaya çıkan hatalar düzeltilmiştir. Ayrıca query performansları da artırılmıştır.

Bunlardan en ölümcül olanlarından bir kaç örnek vermek gerekirse.

50003965

956686 ( http://support.microsoft.com/kb/956686/ )

FIX: When you run a query that contains a JOIN operation in SQL Server 2005, and the ON clause of the JOIN operator contains a LIKE predicate, the query runs slower than in SQL Server 2000

50001602

940545 ( http://support.microsoft.com/kb/940545/ )

FIX: The performance of insert operations against a table that contains an identity column may be slow in SQL Server 2005

50001639

940943 ( http://support.microsoft.com/kb/940943/ )

FIX: The performance of a query that performs an insert operation or an update operation is much slower in SQL Server 2005 SP2 than in earlier versions of SQL Server 2005

274802

963684 ( http://support.microsoft.com/kb/963684/ )

FIX: The execution plan does not use the forced index when you use the INDEX optimizer hint in a query that runs against a synonym in SQL Server 2005

50002864

953569 ( http://support.microsoft.com/kb/953569/LN/ )

FIX: The compilation time of some queries is very long in an x64-based version of SQL Server 2005

002517

951184 ( http://support.microsoft.com/kb/951184/ )

FIX: A query may run much slower in SQL Server 2005 than in SQL Server 2000 when you use a cursor to run the query

50002331

948658 ( http://support.microsoft.com/kb/948658/ )

FIX: Some rows are not returned when you run a complex query that uses the DISTINCT keyword in Microsoft SQL Server 2005

959019 ( http://support.microsoft.com/kb/959019/ )

FIX: You receive an incorrect result when you run a query that uses the LIKE operator in SQL Server 2005

FIX: Performance is very slow when the same stored procedure is executed at the same time in many connections on a multiple-processor computer that is running SQL Server 2005

FIX: When you run a complex query in SQL Server 2005, the query performance is slow if the execution plan of the query contains semi join operators

FIX: When you run a stored procedure that uses some views in SQL Server 2005, the performance is slow compared to SQL Server 2000 if the views use the JOIN operator and contain subqueries

Analysis Servarla ilgili olanları yazmıyorum.

Bir an önce sp3 geçmenizi tavsiye ederim . Sp3 yükselttikten sonra log ları düzenli olarak izleyin yaşanacak sorunları iletirseniz Yardımcı olmaya çalışırız.

İyi çalışmalar.

Gönderildi : 29/04/2009 21:06