Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Need Help:Error log Expand / Collapse
Author
Message
Posted Thursday, June 20, 2013 6:10 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 7:46 AM
Points: 190, Visits: 474
Hi all,

when i checked my error log it has taken 100 gb of space and my disk is out of space. when i checked log folder location i found so many sqldump mdmp files. i am not sure whats going on... i deleted all those files and started sql server.. but i can see they are still generating mdmp files and falling in to the log folder.
Post #1465618
Posted Thursday, June 20, 2013 6:42 AM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, January 23, 2014 6:37 AM
Points: 49, Visits: 116
Is it possible to attach a screen shot of the folder(set the view to details so that we can see the name,date modified, type, size
and also the path/location where your looking at these files.
Post #1465651
Posted Thursday, June 20, 2013 6:47 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 7:46 AM
Points: 190, Visits: 474
here is the error log

2013-06-20 17:33:47.470 Server Microsoft SQL Server 2008 R2 (SP1) - 10.50.2796.0 (X64) Dec 9 2011 11:27:20 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2013-06-20 17:33:47.470 Server (c) Microsoft Corporation.
2013-06-20 17:33:47.470 Server All rights reserved.
2013-06-20 17:33:47.470 Server Server process ID is 3220.
2013-06-20 17:33:47.470 Server System Manufacturer: 'Dell Inc.', System Model: 'OptiPlex 330'.
2013-06-20 17:33:47.470 Server Authentication mode is MIXED.
2013-06-20 17:33:47.490 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-06-20 17:33:47.500 Server This instance of SQL Server last reported using a process ID of 1140 at 6/20/2013 5:32:05 PM (local) 6/20/2013 12:02:05 PM (UTC). This is an informational message only; no user action is required.
2013-06-20 17:33:47.500 Server Registry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2013-06-20 17:33:47.540 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-06-20 17:33:47.540 Server Detected 2 CPUs. This is an informational message; no user action is required.
2013-06-20 17:33:47.630 Server Using locked pages for buffer pool.
2013-06-20 17:33:47.850 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.
2013-06-20 17:33:48.310 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-20 17:33:48.430 spid7s Starting up database 'master'.
2013-06-20 17:33:48.690 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2013-06-20 17:33:49.040 spid7s Resource governor reconfiguration succeeded.
2013-06-20 17:33:49.060 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2013-06-20 17:33:49.060 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2013-06-20 17:33:49.080 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-06-20 17:33:49.210 spid7s SQL Trace ID 1 was started by login "sa".
2013-06-20 17:33:49.230 spid7s Starting up database 'mssqlsystemresource'.
2013-06-20 17:33:49.250 spid7s The resource database build version is 10.50.2796. This is an informational message only. No user action is required.
2013-06-20 17:33:49.550 spid10s Starting up database 'model'.
2013-06-20 17:33:49.610 spid7s Server name is 'QBSNEWSVR'. This is an informational message only. No user action is required.
2013-06-20 17:33:50.290 spid10s Clearing tempdb database.
2013-06-20 17:33:50.850 Server The certificate [Cert Hash(sha1) "1667465C3D9F7AA06A8E4A71C829C12C8D495B3B"] was successfully loaded for encryption.
2013-06-20 17:33:51.020 Server Server is listening on [ 'any' <ipv6> 1433].
2013-06-20 17:33:51.030 Server Server is listening on [ 'any' <ipv4> 1433].
2013-06-20 17:33:51.030 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2013-06-20 17:33:51.030 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2013-06-20 17:33:51.030 Server Server is listening on [ ::1 <ipv6> 1434].
2013-06-20 17:33:51.030 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2013-06-20 17:33:51.030 Server Dedicated admin connection support was established for listening locally on port 1434.
2013-06-20 17:33:51.200 Logon Error: 17187, Severity: 16, State: 1.
2013-06-20 17:33:51.200 Logon SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: 192.168.1.163]
2013-06-20 17:33:51.230 Logon Error: 17187, Severity: 16, State: 1.
2013-06-20 17:33:51.230 Logon SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: ::1]
2013-06-20 17:33:51.230 Logon Error: 17187, Severity: 16, State: 1.
2013-06-20 17:33:51.230 Logon SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: 192.168.1.163]
2013-06-20 17:33:51.270 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/qbsnewsvr.QBSTRUST.COM ] for the SQL Server service.
2013-06-20 17:33:51.270 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/qbsnewsvr.QBSTRUST.COM:1433 ] for the SQL Server service.
2013-06-20 17:33:51.270 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-06-20 17:33:52.630 spid13s A new instance of the full-text filter daemon host process has been successfully started.
2013-06-20 17:33:52.770 spid10s Starting up database 'tempdb'.
2013-06-20 17:33:52.980 spid13s Starting up database 'msdb'.
2013-06-20 17:33:52.980 spid14s Starting up database 'IncuityStore'.
2013-06-20 17:33:52.980 spid15s Starting up database 'IncuitySample'.
2013-06-20 17:33:52.990 spid16s Starting up database 'IncuityHistory'.
2013-06-20 17:33:53.010 spid17s Starting up database 'IncuityDiagnostics'.
2013-06-20 17:33:53.010 spid18s Starting up database 'Tfs_Configuration_Old'.
2013-06-20 17:33:53.010 spid19s Starting up database 'Tfs_Rockwell IPE Tool'.
2013-06-20 17:33:53.010 spid20s Starting up database 'Tfs_Rockwell IPE Tool Phase0'.
2013-06-20 17:33:53.710 spid21s The Service Broker protocol transport is disabled or not configured.
2013-06-20 17:33:53.710 spid21s Server is listening on [ 'any' <ipv6> 5022].
2013-06-20 17:33:53.710 spid21s Server is listening on [ 'any' <ipv4> 5022].
2013-06-20 17:33:53.710 spid21s The Database Mirroring protocol transport is now listening for connections.
2013-06-20 17:33:54.560 spid21s Service Broker manager has started.
2013-06-20 17:33:57.610 spid16s Starting up database 'Tfs_Rockwell IPE Tool Phase2'.
2013-06-20 17:33:57.970 Logon Error: 18456, Severity: 14, State: 38.
2013-06-20 17:33:57.970 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:33:57.970 Logon Error: 18456, Severity: 14, State: 38.
2013-06-20 17:33:57.970 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:33:57.970 spid17s Starting up database 'IPE_MASTER'.
2013-06-20 17:33:57.970 spid15s Starting up database 'IPE_QUOTE'.
2013-06-20 17:34:00.530 spid7s Recovery completed for database IPE_QUOTE (database ID 14) in 1 second(s) (analysis 322 ms, redo 0 ms, undo 319 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:01.680 spid7s Recovery completed for database Tfs_Rockwell IPE Tool (database ID 10) in 1 second(s) (analysis 329 ms, redo 0 ms, undo 322 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:02.620 spid15s Recovery completed for database Tfs_Configuration_Old (database ID 9) in 1 second(s) (analysis 329 ms, redo 0 ms, undo 248 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:02.630 spid15s Starting up database 'IPE_QUOTE_OCT_17'.
2013-06-20 17:34:03.350 spid7s Recovery completed for database IncuityStore (database ID 5) in 1 second(s) (analysis 321 ms, redo 0 ms, undo 359 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:04.840 spid18s Starting up database 'IPE_MASTER_OCT_17'.
2013-06-20 17:34:05.860 spid14s Recovery completed for database IPE_QUOTE_OCT_17 (database ID 15) in 1 second(s) (analysis 644 ms, redo 0 ms, undo 310 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:05.860 spid14s Starting up database 'Tfs_SilverlightProjects'.
2013-06-20 17:34:06.670 spid19s Starting up database 'RhythemSociety'.
2013-06-20 17:34:07.550 spid15s Starting up database 'Tfs_SilverlightProjects1'.
2013-06-20 17:34:08.060 Logon Error: 18456, Severity: 14, State: 38.
2013-06-20 17:34:08.060 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:34:08.060 Logon Error: 18456, Severity: 14, State: 38.
2013-06-20 17:34:08.060 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:34:08.630 spid7s Recovery completed for database msdb (database ID 4) in 1 second(s) (analysis 303 ms, redo 0 ms, undo 397 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:11.060 spid13s Starting up database 'IPE_MASTER_MAR_22'.
2013-06-20 17:34:13.280 spid51 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2013-06-20 17:34:13.280 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2013-06-20 17:34:13.710 spid7s Recovery completed for database Tfs_Rockwell IPE Tool Phase0 (database ID 11) in 1 second(s) (analysis 774 ms, redo 0 ms, undo 397 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:13.810 spid7s Recovery completed for database RhythemSociety (database ID 18) in 1 second(s) (analysis 464 ms, redo 0 ms, undo 485 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:15.950 spid19s Starting up database 'IPE_QUOTE_MAR_22'.
2013-06-20 17:34:16.340 spid7s Recovery completed for database Tfs_SilverlightProjects1 (database ID 19) in 1 second(s) (analysis 260 ms, redo 0 ms, undo 375 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:18.950 spid20s Recovery completed for database IPE_QUOTE_MAR_22 (database ID 21) in 1 second(s) (analysis 309 ms, redo 0 ms, undo 155 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:18.950 spid20s Starting up database 'Test'.
2013-06-20 17:34:19.390 spid7s Recovery completed for database Tfs_Rockwell IPE Tool Phase2 (database ID 12) in 1 second(s) (analysis 291 ms, redo 0 ms, undo 296 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:20.080 spid14s Starting up database 'Tfs_Configuration'.
2013-06-20 17:34:21.190 spid15s Starting up database 'Tfs_Silverlight'.
2013-06-20 17:34:21.550 spid51 Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2013-06-20 17:34:21.550 spid51 Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2013-06-20 17:34:21.980 spid19s Starting up database 'Tfs_DotNetProjects'.
2013-06-20 17:34:23.950 spid7s Recovery completed for database Test (database ID 23) in 1 second(s) (analysis 446 ms, redo 0 ms, undo 344 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:24.610 spid16s Starting up database 'IPE_QUOTE_MAY_31'.
2013-06-20 17:34:27.340 spid20s Starting up database 'IPE_QUOTE_OCT_1'.
2013-06-20 17:34:27.680 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2013-06-20 17:34:27.750 spid51 Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2013-06-20 17:34:29.770 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2013-06-20 17:34:30.050 spid51 Using 'xplog70.dll' version '2009.100.1600' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2013-06-20 17:34:30.400 Logon Error: 18456, Severity: 14, State: 38.
2013-06-20 17:34:30.400 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:34:30.400 Logon Error: 18456, Severity: 14, State: 38.
2013-06-20 17:34:30.400 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2013-06-20 17:34:31.220 spid7s Recovery completed for database Tfs_DotNetProjects (database ID 29) in 1 second(s) (analysis 277 ms, redo 0 ms, undo 862 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:31.890 spid7s Recovery completed for database IPE_QUOTE_MAY_31 (database ID 31) in 1 second(s) (analysis 596 ms, redo 0 ms, undo 355 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:32.740 spid7s Recovery is writing a checkpoint in database 'Tfs_Configuration' (27). This is an informational message only. No user action is required.
2013-06-20 17:34:32.740 spid7s Recovery completed for database Tfs_Configuration (database ID 27) in 1 second(s) (analysis 327 ms, redo 220 ms, undo 63 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:34.250 spid16s Starting up database 'IPE_QUOTE_20130613'.
2013-06-20 17:34:34.370 spid14s Starting up database 'KovaiCRM_1'.
2013-06-20 17:34:35.710 spid7s Recovery completed for database IPE_MASTER_MAR_22 (database ID 20) in 1 second(s) (analysis 353 ms, redo 0 ms, undo 351 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:37.020 spid7s Recovery completed for database IPE_MASTER_OCT_17 (database ID 16) in 1 second(s) (analysis 423 ms, redo 0 ms, undo 485 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:37.580 spid18s CHECKDB for database 'IPE_MASTER_OCT_17' finished without errors on 2013-05-15 10:32:37.900 (local time). This is an informational message only; no user action is required.
2013-06-20 17:34:37.640 spid7s Recovery completed for database KovaiCRM_1 (database ID 34) in 1 second(s) (analysis 723 ms, redo 0 ms, undo 488 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:38.550 spid7s Recovery completed for database IPE_MASTER (database ID 13) in 1 second(s) (analysis 215 ms, redo 0 ms, undo 286 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:42.480 spid7s Recovery is writing a checkpoint in database 'IPE_QUOTE_20130613' (33). This is an informational message only. No user action is required.
2013-06-20 17:34:42.480 spid7s Recovery completed for database IPE_QUOTE_20130613 (database ID 33) in 1 second(s) (analysis 348 ms, redo 333 ms, undo 95 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:43.760 spid7s Recovery is writing a checkpoint in database 'Tfs_Silverlight' (28). This is an informational message only. No user action is required.
2013-06-20 17:34:43.760 spid7s Recovery completed for database Tfs_Silverlight (database ID 28) in 1 second(s) (analysis 195 ms, redo 256 ms, undo 18 ms.) This is an informational message only. No user action is required.
2013-06-20 17:34:49.360 spid7s Recovery is complete. This is an informational message only. No user action is required.
2013-06-20 17:34:54.870 spid17s ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22, attempting to create symptom dump
2013-06-20 17:34:54.870 spid17s Using 'dbghelp.dll' version '4.0.5'
2013-06-20 17:34:54.870 spid17s **Dump thread - spid = 0, EC = 0x0000000082596B20
2013-06-20 17:34:54.870 spid17s *
2013-06-20 17:34:54.870 spid17s * User initiated stack dump. This is not a server exception dump.
2013-06-20 17:34:54.870 spid17s *
2013-06-20 17:34:54.870 spid17s ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt
2013-06-20 17:34:54.870 spid17s * *******************************************************************************
2013-06-20 17:34:54.870 spid17s *
2013-06-20 17:34:54.870 spid17s * BEGIN STACK DUMP:
2013-06-20 17:34:54.870 spid17s * 06/20/13 17:34:54 spid 17
2013-06-20 17:34:54.870 spid17s *
2013-06-20 17:34:54.870 spid17s * ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22
2013-06-20 17:34:54.870 spid17s *
2013-06-20 17:34:54.870 spid17s *
2013-06-20 17:34:54.870 spid17s *
2013-06-20 17:34:54.870 spid17s * MODULE BASE END SIZE
2013-06-20 17:34:54.870 spid17s * sqlservr 0000000000D60000 0000000004944FFF 03be5000
2013-06-20 17:34:54.870 spid17s * ntdll 00000000776C0000 0000000077868FFF 001a9000
2013-06-20 17:34:54.870 spid17s * kernel32 00000000775A0000 00000000776BEFFF 0011f000
2013-06-20 17:34:54.870 spid17s * KERNELBASE 000007FEFD550000 000007FEFD5BAFFF 0006b000
2013-06-20 17:34:54.870 spid17s * ADVAPI32 000007FEFEAD0000 000007FEFEBAAFFF 000db000
2013-06-20 17:34:54.870 spid17s * msvcrt 000007FEFEEA0000 000007FEFEF3EFFF 0009f000
2013-06-20 17:34:54.870 spid17s * sechost 000007FEFD910000 000007FEFD92EFFF 0001f000
2013-06-20 17:34:54.870 spid17s * RPCRT4 000007FEFF3F0000 000007FEFF51CFFF 0012d000
2013-06-20 17:34:54.870 spid17s * MSVCR80 00000000751F0000 00000000752B8FFF 000c9000
2013-06-20 17:34:54.870 spid17s * MSVCP80 00000000740C0000 00000000741C8FFF 00109000
2013-06-20 17:34:54.870 spid17s * sqlos 0000000073EF0000 0000000073EF6FFF 00007000
2013-06-20 17:34:54.870 spid17s * Secur32 000007FEFD130000 000007FEFD13AFFF 0000b000
2013-06-20 17:34:54.870 spid17s * SSPICLI
Post #1465656
Posted Thursday, June 20, 2013 6:54 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 7:46 AM
Points: 190, Visits: 474
one of the dump file information due to space constrait only top portion of dump is pasted. i dont know how to attach a file to this forum



Current time is 18:22:48 06/20/13.
=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server
version 10.50.2796.0
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 Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz.
Bios Version is DELL - 15
Phoenix ROM BIOS PLUS Version 1.10 A03
2 X64 level 8664, 2 Mhz processor (s).
Windows NT 6.1 Build 7601 CSD Service Pack 1.

Memory
MemoryLoad = 92%
Total Physical = 2036 MB
Available Physical = 161 MB
Total Page File = 4073 MB
Available Page File = 1284 MB
Total Virtual = 8388607 MB
Available Virtual = 8386208 MB
**Dump thread - spid = 0, EC = 0x0000000094D6CB20
*
* User initiated stack dump. This is not a server exception dump.
*
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0288.tx
t
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 06/20/13 18:22:48 spid 16
*
* ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22
*
*
*
* MODULE BASE END SIZE
* sqlservr 0000000000D60000 0000000004944FFF 03be5000
* ntdll 00000000776C0000 0000000077868FFF 001a9000
* kernel32 00000000775A0000 00000000776BEFFF 0011f000
* KERNELBASE 000007FEFD550000 000007FEFD5BAFFF 0006b000
* ADVAPI32 000007FEFEAD0000 000007FEFEBAAFFF 000db000
Post #1465663
Posted Thursday, June 20, 2013 7:31 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 7:46 AM
Points: 190, Visits: 474
in event viewer

administrative event it is showing


An error occurred while writing a trace event to the file, \\?\C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log\FlightRecorderCurrent.trc.

An error occurred while closing the trace output file, \\?\C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log\FlightRecorderCurrent.trc.
Post #1465692
Posted Thursday, June 20, 2013 7:56 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 10:19 AM
Points: 43,026, Visits: 36,192
Call Product Support and open a case, you're getting SQL dumping stack dumps, this is potentially a severe problem.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1465716
Posted Thursday, June 20, 2013 7:33 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 12, 2014 7:46 AM
Points: 190, Visits: 474
Hi,

I am planning to migrate from this server to another does this solve this issue ...
Post #1466016
Posted Friday, June 21, 2013 12:40 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 10:19 AM
Points: 43,026, Visits: 36,192
Maybe, maybe not. Depends on what the root cause is.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1466065
Posted Friday, June 21, 2013 4:30 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, September 2, 2014 8:14 AM
Points: 62, Visits: 234
why don’t you recycle SQL error log by exec sp_cycle_errorlog.

SQL will recycle the log and the physical log file will be inactive (it can be deleted).

my recommendation would be .....recycle the error log.....delete the old files (so that you can have free space back on disk)

now monitor if the error log is still growing. if so that go through the logs and see what causing it to grow. Hopefully it should be fine after recycle.
Post #1466117
Posted Friday, June 21, 2013 4:35 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 10:19 AM
Points: 43,026, Visits: 36,192
DKG-967908 (6/21/2013)
why don’t you recycle SQL error log by exec sp_cycle_errorlog.


It's not that his error log is growing, it's that SQL is stack dumping and writing large stack dumps into the error log directory. The running out of space is a symptom, the problem is that SQL is stack dumping.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1466121
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse