locked
SQLDump01.mdmp files generating huge in log folder RRS feed

  • Question

  • Hi All,

    I am using SQL server 2008R2, SharePoint 2010

    Automatically in my system C drive log files generating with named as SQLDump01.mdmp,SQLDump02.mdmp.....SQLDump3999.mdmp..

    Path : C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\Log

    50GB space occupied in two days.

    I am deleting .mdmp files and immediately .mdmp file generating.

    How  can i stop them ?   


    MD.Liakath ali
    • Edited by Liakath Tuesday, January 10, 2012 6:20 AM
    Tuesday, January 10, 2012 6:09 AM

Answers

  • Hello,

    Those dumps may be related to database corruption, access violation, issues with the scheduler, etc.

    In this case, it seems there is database corruption on WebAnalyticsServiceApplication_StagingDB_61d29ffc-e691-43cc-ba35-867072669ccc.mdf. If you need a quick response try calling Microsoft Support.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com


    Tuesday, January 10, 2012 2:33 PM

All replies

  • You can open that file and see what is written in. Also check out ERROR.LOG and Event Viewer
    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/
    Tuesday, January 10, 2012 6:14 AM
  • Please check these two once.  i am not able to get these

    ERROR LOG:
    2012-01-10 10:06:18.29 Server      Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) 
    Mar 29 2009 10:11:52 
    Copyright (c) 1988-2008 Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )
    2012-01-10 10:06:18.29 Server      (c) 2005 Microsoft Corporation.
    2012-01-10 10:06:18.29 Server      All rights reserved.
    2012-01-10 10:06:18.29 Server      Server process ID is 2936.
    2012-01-10 10:06:18.29 Server      System Manufacturer: 'Hewlett-Packard', System Model: 'HP Pro 3090 Microtower PC'.
    2012-01-10 10:06:18.29 Server      Authentication mode is WINDOWS-ONLY.
    2012-01-10 10:06:18.29 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\Log\ERRORLOG'.
    2012-01-10 10:06:18.29 Server      This instance of SQL Server last reported using a process ID of 2560 at 1/10/2012 10:04:27 AM (local) 1/10/2012 4:34:27 AM (UTC). This is an informational message only; no user action is required.
    2012-01-10 10:06:18.29 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\mastlog.ldf
    2012-01-10 10:06:18.29 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2012-01-10 10:06:18.29 Server      Detected 2 CPUs. This is an informational message; no user action is required.
    2012-01-10 10:06:18.34 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2012-01-10 10:06:18.38 Server      Node configuration: node 0: CPU mask: 0x0000000000000003 Active CPU mask: 0x0000000000000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2012-01-10 10:06:18.43 spid7s      Starting up database 'master'.
    2012-01-10 10:06:18.60 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2012-01-10 10:06:31.38 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SHAREPOINT'.
    2012-01-10 10:06:32.65 spid7s      SQL Trace ID 1 was started by login "sa".
    2012-01-10 10:06:32.93 spid7s      Starting up database 'mssqlsystemresource'.
    2012-01-10 10:06:32.93 spid7s      The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
    2012-01-10 10:06:33.36 spid10s     Starting up database 'model'.
    2012-01-10 10:06:33.53 Server      A self-generated certificate was successfully loaded for encryption.
    2012-01-10 10:06:33.53 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SHAREPOINT ].
    2012-01-10 10:06:33.53 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SHAREPOINT\sql\query ].
    2012-01-10 10:06:33.53 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
    2012-01-10 10:06:33.53 spid7s      Server name is 'AVSDT03\SHAREPOINT'. This is an informational message only. No user action is required.
    2012-01-10 10:06:33.54 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2012-01-10 10:06:33.54 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2012-01-10 10:06:33.54 spid7s      Informational: No full-text supported languages found.
    2012-01-10 10:06:33.54 spid13s     Starting up database 'msdb'.
    2012-01-10 10:06:33.62 spid14s     Starting up database 'WebAnalyticsServiceApplication_StagingDB_61d29ffc-e691-43cc-ba35-867072669ccc'.
    2012-01-10 10:06:34.88 spid10s     Clearing tempdb database.
    2012-01-10 10:06:36.14 spid14s     Error: 824, Severity: 24, State: 2.
    2012-01-10 10:06:36.14 spid14s     SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x9c70dcaa; actual: 0xcc71dcab). It occurred during a read of page (1:23) in database ID 19 at offset 0x0000000002e000 in file 'C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\WebAnalyticsServiceApplication_StagingDB_61d29ffc-e691-43cc-ba35-867072669ccc.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    2012-01-10 10:06:36.47 spid14s     Error: 3313, Severity: 21, State: 2.
    2012-01-10 10:06:36.47 spid14s     During redoing of a logged operation in database 'WebAnalyticsServiceApplication_StagingDB_61d29ffc-e691-43cc-ba35-867072669ccc', an error occurred at log record ID (735:551:74). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
    2012-01-10 10:06:36.47 spid14s     Error: 3414, Severity: 21, State: 1.
    2012-01-10 10:06:36.47 spid14s     An error occurred during recovery, preventing the database 'WebAnalyticsServiceApplication_StagingDB_61d29ffc-e691-43cc-ba35-867072669ccc' (database ID 19) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    2012-01-10 10:07:01.57 spid10s     Starting up database 'tempdb'.
    2012-01-10 10:07:01.77 spid14s     The Service Broker protocol transport is disabled or not configured.
    2012-01-10 10:07:01.78 spid14s     The Database Mirroring protocol transport is disabled or not configured.
    2012-01-10 10:07:01.78 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2012-01-10 10:07:01.78 spid14s     Service Broker manager has started.
    2012-01-10 10:07:31.48 spid52      Starting up database 'SharePoint_Config_00e24210-17ae-4085-8df3-7d821101a96d'.
    2012-01-10 10:09:56.49 spid58      Starting up database 'WSS_Content_cmp24by7'.
    2012-01-10 10:10:00.97 spid58      Recovery is writing a checkpoint in database 'WSS_Content_cmp24by7' (34). This is an informational message only. No user action is required.
    2012-01-10 10:10:03.04 spid59      Starting up database 'WSS_Content_camp24by71'.
    2012-01-10 10:10:05.71 spid59      Recovery is writing a checkpoint in database 'WSS_Content_camp24by71' (36). This is an informational message only. No user action is required.
    2012-01-10 10:10:06.41 spid60      Starting up database 'WSS_Content_butterdemo'.
    2012-01-10 10:10:06.77 spid60      Recovery is writing a checkpoint in database 'WSS_Content_butterdemo' (37). This is an informational message only. No user action is required.
    2012-01-10 10:10:07.96 spid61      Starting up database 'WSS_Content_DhyanSai'.
    2012-01-10 10:10:10.41 spid61      Recovery is writing a checkpoint in database 'WSS_Content_DhyanSai' (27). This is an informational message only. No user action is required.
    2012-01-10 10:10:12.81 spid62      Starting up database 'WSS_Content_Rahim'.
    2012-01-10 10:10:14.25 spid62      Recovery is writing a checkpoint in database 'WSS_Content_Rahim' (31). This is an informational message only. No user action is required.
    2012-01-10 10:10:14.78 spid63      Starting up database 'WSS_Content'.
    2012-01-10 10:10:16.47 Logon       Error: 18456, Severity: 14, State: 38.
    2012-01-10 10:10:16.47 Logon       Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
    2012-01-10 10:10:17.23 Logon       Error: 18456, Severity: 14, State: 38.
    2012-01-10 10:10:17.23 Logon       Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
    2012-01-10 10:10:21.00 spid63      Recovery is writing a checkpoint in database 'WSS_Content' (10). This is an informational message only. No user action is required.
    2012-01-10 10:10:22.11 spid64      Starting up database 'WSS_Content_82dc20cc34314b20b1604048b4a163b5'.
    2012-01-10 10:10:23.35 spid64      Recovery is writing a checkpoint in database 'WSS_Content_82dc20cc34314b20b1604048b4a163b5' (29). This is an informational message only. No user action is required.
    2012-01-10 10:10:23.75 spid65      Starting up database 'WSS_Content_softwareanalyst'.
    2012-01-10 10:10:25.94 spid65      Recovery is writing a checkpoint in database 'WSS_Content_softwareanalyst' (33). This is an informational message only. No user action is required.
    2012-01-10 10:10:30.01 spid66      Starting up database 'SharePoint_AdminContent_fddd44ac-c5af-4ae7-8c6e-39622327193c'.
    2012-01-10 10:10:49.47 spid17s     ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22, attempting to create symptom dump
    2012-01-10 10:10:49.71 spid17s     Using 'dbghelp.dll' version '4.0.5'
    2012-01-10 10:11:27.51 spid17s     **Dump thread - spid = 0, EC = 0x000000008086AB20
    2012-01-10 10:11:27.51 spid17s     * 
    2012-01-10 10:11:27.51 spid17s     * User initiated stack dump.  This is not a server exception dump.
    2012-01-10 10:11:27.51 spid17s     * 
    2012-01-10 10:11:27.57 spid17s     ***Stack Dump being sent to C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\LOG\SQLDump2723.txt
    2012-01-10 10:11:27.57 spid17s     * *******************************************************************************
     

    MD.Liakath ali
    Tuesday, January 10, 2012 6:49 AM
  • Hello,

    Those dumps may be related to database corruption, access violation, issues with the scheduler, etc.

    In this case, it seems there is database corruption on WebAnalyticsServiceApplication_StagingDB_61d29ffc-e691-43cc-ba35-867072669ccc.mdf. If you need a quick response try calling Microsoft Support.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com


    Tuesday, January 10, 2012 2:33 PM