June 4, 2014 at 9:46 pm
Thank you your support i am using sqlserver 2008R2 with sp1 and regular basisc i have creted fullbackup and differetailbackup and dont have clr in server..please help me
June 4, 2014 at 9:50 pm
rajesh.mekala (6/4/2014)
Thank you your support i am using sqlserver 2008R2 with sp1 and regular basisc i have creted fullbackup and differetailbackup and dont have clr in server..please help me
Back to the unanswered question.
What is running at the time that these mdmp files are created? Have you tried to correlate what is running at those times yet?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 4, 2014 at 9:50 pm
please tel me yaar how to reslove this issue permently please give explain brefily
June 4, 2014 at 9:53 pm
This is the producation server, this server using billing the data mart
June 4, 2014 at 9:56 pm
rajesh.mekala (6/4/2014)
please tel me yaar how to reslove this issue permently please give explain brefily
We can't tell you how to fix it because we don't have near enough information.
You need to start investigating and troubleshooting. Start by getting the timestamps of the mdmp files. Next step might be to setup a server side trace to find what runs at the same time as the next mdmp file gets created.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 4, 2014 at 10:54 pm
contiously created new mdmdp files
June 5, 2014 at 2:17 am
SQLRNNR (6/4/2014)
rajesh.mekala (6/4/2014)
please tel me yaar how to reslove this issue permently please give explain brefilyWe can't tell you how to fix it because we don't have near enough information.
You need to start investigating and troubleshooting. Start by getting the timestamps of the mdmp files. Next step might be to setup a server side trace to find what runs at the same time as the next mdmp file gets created.
+1 to what Jason said. In addition, you can look at the SQL Server log to see what is being logged just prior to the mini-dump being created. Are you running DBCC CHECKDB on a regular basis and if so, is it reporting any database corruption? I know that a dump file is created in this scenario (not sure if it's a mini-dump though). You might also want to take a look at this link: http://support.microsoft.com/kb/2699013 to see if it is applicable to your situation.
Regards
Lempster
June 5, 2014 at 3:51 am
rajesh.mekala (6/4/2014)
please tel me yaar how to reslove this issue permently please give explain brefily
Call Microsoft Support, open a case.
Alternatively, if you want free help maybe give us the details we're asking for.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 5, 2014 at 7:28 am
GilaMonster (6/5/2014)
rajesh.mekala (6/4/2014)
please tel me yaar how to reslove this issue permently please give explain brefilyCall Microsoft Support, open a case.
Alternatively, if you want free help maybe give us the details we're asking for.
+10
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 19, 2014 at 9:00 pm
Dear all,
I am Jacob from China, I ecounter the same problem. if you have fixed it. kindly pls help to share.
my log folder grows so fast. the log (the MSSQL\LOG\SQLDmpr10000.mdmp) and SQLDUMPER_ERRORLOG grow fast.
below is error log:
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 0000000004333628
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2232
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0000000004333628
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x0000000000000000
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x0000000000000000
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated with file D:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.ECLAIMSGIW\MSSQL\LOG\SQLDump10000.txt
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2544:2848) 06/20/14 10:35:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2544:2848) 06/20/14 10:35:22, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2544:2848) 06/20/14 10:35:22, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: D:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.ECLAIMSGIW\MSSQL\LOG\SQLDmpr0897.mdmp
(2544:2848) 06/20/14 10:35:22, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll'
(2544:2848) 06/20/14 10:35:22, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(2544:2848) 06/20/14 10:35:22, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(2544:2848) 06/20/14 10:35:22, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE'
(2544:2848) 06/20/14 10:35:22, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '2009.100:1600.1'
(2544:2848) 06/20/14 10:35:22, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '10.50:1600.1'
(2544:2848) 06/20/14 10:35:22, ACTION, sqlservr.exe, Watson Invoke: No
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 2232
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 0000000004333628
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2232
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0000000004333628
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x0000000000000000
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x0000000000000000
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated with file D:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.ECLAIMSGIW\MSSQL\LOG\SQLDump10000.txt
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2440:25F0) 06/20/14 10:35:24, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2440:25F0) 06/20/14 10:35:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2440:25F0) 06/20/14 10:35:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: D:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.ECLAIMSGIW\MSSQL\LOG\SQLDmpr0898.mdmp
(2440:25F0) 06/20/14 10:35:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll'
(2440:25F0) 06/20/14 10:35:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(2440:25F0) 06/20/14 10:35:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(2440:25F0) 06/20/14 10:35:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE'
(2440:25F0) 06/20/14 10:35:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '2009.100:1600.1'
(2440:25F0) 06/20/14 10:35:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '10.50:1600.1'
(2440:25F0) 06/20/14 10:35:25, ACTION, sqlservr.exe, Watson Invoke: No
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 2232
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 0000000004333628
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2232
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0000000004333628
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x0000000000000000
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x0000000000000000
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated with file D:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.ECLAIMSGIW\MSSQL\LOG\SQLDump10000.txt
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: D:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.ECLAIMSGIW\MSSQL\LOG\SQLDmpr0899.mdmp
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll'
(16F4:1538) 06/20/14 10:35:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
(
Viewing 10 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply