Prev: TSX Servers Error Message in SQL Agent Error Log
Next: Languages supported by single-byte code page.
From: ronnie on 10 Apr 2008 09:41 Thanks. We moved the SQL Server back to the old hardware and everything became normal. Looks like this was an issue with VMWare. "Jason Massie" wrote: > An assertion is almost always a bug with SQL Server. However, you are not > going to get very far with Microsoft support on this being SQL 2000 > especially VMWare. You ought to consider upgrading after the normal testing > cycles. > > -- > Jason Massie > Web: http://statisticsio.com > RSS: http://feeds.feedburner.com/statisticsio > > "ronnie" <ronnie(a)discussions.microsoft.com> wrote in message > news:BED1D5A3-8CFB-41AE-8BE9-999F4CD18D3A(a)microsoft.com... > > Hi, > > > > I recently moved a SQL Server 2000 running SP4 8.00.2187 running on > > Windows > > Server 2003 STD Edition SP1 on to a VMWare installation. It has four > > databases whose tables gets updated by truncating and populating via a > > four > > DTS jobs which run at different times. Yesterday, all the four DTS jobs > > failed, three of them completed when I re-ran the job the second time and > > the > > last one completed when I re-ran the job the third time. The error log > > contains the same error as below for the time when the DTS jobs failed. > > > > In the error log I found these errors: > > 17066 : > > SQL Server Assertion: File: <umsio.cpp>, line=563 Failed Assertion = > > 'm_busyCnt == 1'. > > 17310 : > > SqlDumpExceptionHandler: Process 5780 generated fatal exception c000001d > > EXCEPTION_ILLEGAL_INSTRUCTION. SQL Server is terminating this process. > > 17311 : > > SQL Server is aborting. Fatal exception c000001d caught. > > > > and then the SQL Server restarted. > > > > I have done DBCC CHECKDB and DBCC CHECKCATALOG on all the databases and I > > have found no errors. Any suggestions will be greatly appreciated. > > > |