Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bogey
Posting Yak Master
166 Posts |
 Posted - 2009-05-15 : 10:59:54
|
| We are receiving MDMP files every second on our server. Here is whats comming out of the sqlDump file. I've not inlcuded the entire file.This file is generated by Microsoft SQL Server version 9.00.3077.00 upon detection of fatal unexpected error. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request. Computer type is AT/AT COMPATIBLE. Bios Version is DELL - 1 Phoenix ROM BIOS PLUS Version 1.10 A04 Current time is 09:32:51 05/15/09. 4 Intel x86 level 15, 3400 Mhz processor (s). Windows NT 5.2 Build 3790 CSD Service Pack 2. Memory MemoryLoad = 56% Total Physical = 4095 MB Available Physical = 1765 MB Total Page File = 5975 MB Available Page File = 3902 MB Total Virtual = 2047 MB Available Virtual = 71 MB **Dump thread - spid = 109, PSS = 0x1AD195C8, EC = 0x1AD195D0 * * User initiated stack dump. This is not a server exception dump. * ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0037.txt * ******************************************************************************* * * BEGIN STACK DUMP: * 05/15/09 09:32:51 spid 109 * * ex_raise2: Exception raised, major=86, minor=24, state=116, severity=16 * * Input Buffer 510 bytes - * select l.*, nc.contentformatid from tblListing l, tblNavigation n, tblNa * vContent nc where l.NavID = n.NavID and n.NavID = nc.NavID and l.NavID * = 1491 and (select count(*) from [HS_Webcalendar]..[sysobjects] where (x * type = char(85)) AND (status >1)) between 0 and 0 and l.ListingStatusID * = 4 order by l.ListingOrder MODULE BASE END SIZE * sqlservr 01000000 02C0BFFF 01c0c000 * ntdll 7C800000 7C8C1FFF 000c2000 * kernel32 77E40000 77F41FFF 00102000 * MSVCR80 78130000 781CAFFF 0009b000 * msvcrt 77BA0000 77BF9FFF 0005a000 * MSVCP80 7C420000 7C4A6FFF 0008700.................... |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2009-05-15 : 11:11:02
|
| Call Microsoft tech support. |
 |
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2009-05-15 : 11:20:30
|
quote:
Originally posted by robvolk
Call Microsoft tech support.
I'm assuming that there is some sort of sql injection going on because of the "type = char(85))" this causes this error"Msg 8624, Level 16, State 116, Line 1Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services."Which in turn causes the sqldumper_errorlog.log, sqldump*.mdmp file which is almost 6MB. All of this can then fill up your drive space. |
|
|
|
tripodal
Constraint Violating Yak Guru
259 Posts |
Posted - 2009-05-15 : 16:56:07
|
| Bugchecks in other situations are usually due to faulty hardware.I use a utility called Memtest86 for stresstesting Ram.http://www.memtest.org/You can also use Prime95 for stability testing, due to the complex math it is an excellent stability tester. http://mersenne.org/freesoft/#newusersThere is a stress testing only option. |
|
|
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2009-05-17 : 19:38:38
|
| How did you know it was dumping every x ...did it show in the logs as sql is dumping a file. Never seen this before.Yes definately call MS and the support fees are really cheap 250 for the entire case and they stay with the case until it fixed.Sorry i wish i had more advice for you.Have you shut down the sql server and brought it back up at all. |
|
|
|
bogey
Posting Yak Master
166 Posts |
Posted - 2009-05-18 : 08:39:58
|
quote:
Originally posted by TRACEYSQL
How did you know it was dumping every x ...did it show in the logs as sql is dumping a file.
Log directory was showing the files. Its definitely a sql injection attack that was not handled properly on the web site. Thought that SQL Server 2005 would not let this happen but it is and we had to fix it on the web end side where it should of been caught in the first place. |
|
|
|
|
|
|
|
|
Immediate Help -- sql dump file every second