Every night I am seeing the below error followed by a restart of SQL.  This 
occurs at 10:05 PM.

Any ideas?
Thanks,
Bob


Event Type:	Error
Event Source:	MSSQLSERVER
Event Category:	(2)
Event ID:	17055
Date:		10/11/2007
Time:		10:05:28 PM
Description:
17066 :
SQL Server Assertion: File: , line=563 
Failed Assertion = 'm_busyCnt == 1'.

This is often a SQL Server bug, and I'd talk to the MS SQL support.

Linchi

"BobW" wrote:

> Every night I am seeing the below error followed by a restart of SQL.  This 
> occurs at 10:05 PM.
> 
> Any ideas?
> Thanks,
> Bob
> 
> 
> Event Type:	Error
> Event Source:	MSSQLSERVER
> Event Category:	(2)
> Event ID:	17055
> Date:		10/11/2007
> Time:		10:05:28 PM
> Description:
> 17066 :
> SQL Server Assertion: File: , line=563 
> Failed Assertion = 'm_busyCnt == 1'.

I did find article KB914298 and requested the hotfix.  What I find 
troublesome is I have two SQL servers are very close to identical and only 
one is exhibiting the behavior

Thanks,
Bob

"Linchi Shea" wrote:

> This is often a SQL Server bug, and I'd talk to the MS SQL support.
> 
> Linchi
> 
> "BobW" wrote:
> 
> > Every night I am seeing the below error followed by a restart of SQL.  This 
> > occurs at 10:05 PM.
> > 
> > Any ideas?
> > Thanks,
> > Bob
> > 
> > 
> > Event Type:	Error
> > Event Source:	MSSQLSERVER
> > Event Category:	(2)
> > Event ID:	17055
> > Date:		10/11/2007
> > Time:		10:05:28 PM
> > Description:
> > 17066 :
> > SQL Server Assertion: File: , line=563 
> > Failed Assertion = 'm_busyCnt == 1'.

Dear Bob, 

Thank you for posting here. 

Before going further, I would like to know you load the data into database 
by which method? As KB914298 described, you can workaround this issue by 
using either the Bulk-Copy program or Data Transformation Service (DTS) to 
import the data. Does this information helps?

Based on my experience, this issue seems to be a data corruption. According 
to your situation, we can first attempt to install the hotfix KB914298 and 
also run the "DBCC CheckDB" to do the database check. If the issue 
persists, we may need to analyze the crash dump file to determine the root 
cause. Unfortunately, we cannot help you analyze the dump file in newsgroup 
and you may need to speak directly with a Microsoft Support Professional so 
that the crash dump can be analyzed. Regarding this point, I'll appreciate 
your understanding. 

For current situation, my suggestion is:

1. Install the Hotfix KB914298
2. Use "DBCC CheckDB" command to check the allocation and structural 
integrity of all the objects in the database. I suggest you check all 
databases.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
dbcc_00gy.asp

Please let me know the exact output of DBCC CheckDB. Meanwhile, please pack 
the SQL error log and System & Application event log into a zip file. Send 
me this zip file to v-adamqu@microsoft.com I hope we can find any clues 
from these.

Have a nice day!

Best regards,

Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so 
that others may learn and benefit from your issue. 
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Event 17055:  SQL Server Assertion error
| thread-index: AcgVAug1OJA0yFz4TWe2zKieAYot/g==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?Qm9iVw==?= 
| References:  <4C12F2AF-6B8E-403B-BA80-76C5A48B6C3E@microsoft.com> 
<035A5E8F-8CBB-4255-AACD-83CE90F93846@microsoft.com>
| Subject: RE: Event 17055:  SQL Server Assertion error
| Date: Mon, 22 Oct 2007 16:26:01 -0700
| Lines: 33
| Message-ID: <3C62397A-B661-4F51-82C9-6FF74BE36F21@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| 	charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2929
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:28508
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.sqlserver.server
| 
| I did find article KB914298 and requested the hotfix.  What I find 
| troublesome is I have two SQL servers are very close to identical and 
only 
| one is exhibiting the behavior
| 
| Thanks,
| Bob
| 
| "Linchi Shea" wrote:
| 
| > This is often a SQL Server bug, and I'd talk to the MS SQL support.
| > 
| > Linchi
| > 
| > "BobW" wrote:
| > 
| > > Every night I am seeing the below error followed by a restart of SQL. 
 This 
| > > occurs at 10:05 PM.
| > > 
| > > Any ideas?
| > > Thanks,
| > > Bob
| > > 
| > > 
| > > Event Type:	Error
| > > Event Source:	MSSQLSERVER
| > > Event Category:	(2)
| > > Event ID:	17055
| > > Date:		10/11/2007
| > > Time:		10:05:28 PM
| > > Description:
| > > 17066 :
| > > SQL Server Assertion: File: , line=563 
| > > Failed Assertion = 'm_busyCnt == 1'.
|