question

sree.dba avatar image
sree.dba asked

MSSQLSERVER Services terminated unexpectedly.It has done 3 time(s)

Can anyone suggest and provide solution: > The MSSQLSERVER Services terminated > unexpectedly. it has done 3 time(s). > > Sqlserver 2008R2 RTM 10.50.1617.0 > (X64) > > > Standard Edition (64-bit) on Windows > NT 6.1 (Build 7601: Service Pack 1) > (Hypervisor) > System Manufacturer: 'VMware, Inc.', > System Model: 'VMware Virtual > Platform'. > > Description: Event Logs : System > Time:24/05/2014 9:25:27PM and > 12/06/2014 10:01:12AM Event Type : > Error Event Id : 7034 > Event Message : The SQL Server > (MSSQLSERVER) service terminated > unexpectedly. It has done this 3 > time(s). > > > > Any help would be greatly appreciated > since it is a production server. if u > want any extra informaion i will > provide . > > > > Errorlog: > > 2014-05-24 21:25:32.61 Server > Microsoft SQL Server 2008 R2 (RTM) - > 10.50.1617.0 (X64) Apr 22 2011 19:23:43 Copyright (c) Microsoft > Corporation Standard Edition (64-bit) > on Windows NT 6.1 (Build 7601: > Service Pack 1) (Hypervisor) > > 2014-05-24 21:25:32.61 Server (c) > Microsoft Corporation. 2014-05-24 > 21:25:32.61 Server All rights > reserved. 2014-05-24 21:25:32.61 > Server Server process ID is > 19696. 2014-05-24 21:25:32.61 Server System Manufacturer: 'VMware, Inc.', > System Model: 'VMware Virtual > Platform'. 2014-05-24 21:25:32.61 > Server Authentication mode is > MIXED. 2014-05-24 21:25:32.61 Server > Logging SQL Server messages in file > 'C:\Program Files\Microsoft SQL > Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'. > 2014-05-24 21:25:32.61 Server > This instance of SQL Server last > reported using a process ID of 7388 at > 24/05/2014 9:24:40 PM (local) > 24/05/2014 11:24:40 AM (UTC). This is > an informational message only; no user > action is required. 2014-05-24 > 21:25:32.63 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 2014-05-24 21:25:32.63 Server SQL > Server is starting at normal priority > base (=7). This is an informational > message only. No user action is > required. 2014-05-24 21:25:32.63 > Server Detected 2 CPUs. This is > an informational message; no user > action is required. 2014-05-24 > 21:25:32.73 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. 2014-05-24 > 21:25:32.78 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. 2014-05-24 > 21:25:32.81 spid5s Starting up > database 'master'. 2014-05-24 > 21:25:32.95 spid5s 97 > transactions rolled forward in > database 'master' (1). This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:32.97 spid5s 0 transactions > rolled back in database 'master' (1). > This is an informational message only. > No user action is required. 2014-05-24 > 21:25:32.97 spid5s Recovery is > writing a checkpoint in database > 'master' (1). This is an informational > message only. No user action is > required. 2014-05-24 21:25:33.10 > spid5s FILESTREAM: effective > level = 0, configured level = 0, file > system access share name = > 'MSSQLSERVER'. 2014-05-24 21:25:33.12 > spid5s SQL Trace ID 1 was started > by login "sa". 2014-05-24 21:25:33.13 > spid5s Starting up database > 'mssqlsystemresource'. 2014-05-24 > 21:25:33.14 spid5s The resource > database build version is 10.50.1617. > This is an informational message only. > No user action is required. 2014-05-24 > 21:25:33.69 spid10s Starting up > database 'model'. 2014-05-24 > 21:25:33.70 spid5s Server name is > 'AUPROC01'. This is an informational > message only. No user action is > required. 2014-05-24 21:25:34.03 > Server A self-generated > certificate was successfully loaded > for encryption. 2014-05-24 21:25:34.04 > Server Server is listening on [ > 'any' 1433]. 2014-05-24 21:25:34.04 > Server Server is listening on [ > 'any' 1433]. 2014-05-24 21:25:34.05 > Server Server local connection > provider is ready to accept connection > on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. > 2014-05-24 21:25:34.05 Server > Server local connection provider is > ready to accept connection on [ > \\.\pipe\sql\query ]. 2014-05-24 > 21:25:34.05 Server Server is > listening on [ ::1 1434]. 2014-05-24 > 21:25:34.05 Server Server is > listening on [ 127.0.0.1 1434]. > 2014-05-24 21:25:34.05 Server > Dedicated admin connection support was > established for listening locally on > port 1434. 2014-05-24 21:25:34.20 > spid13s A new instance of the > full-text filter daemon host process > has been successfully started. > 2014-05-24 21:25:34.22 Server The > SQL Server Network Interface library > could not register the Service > Principal Name (SPN) for the SQL > Server service. Error: 0x2098, state: > 15. 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. 2014-05-24 > 21:25:34.22 Server SQL Server is > now ready for client connections. This > is an informational message; no user > action is required. 2014-05-24 > 21:25:34.27 spid14s Starting up > database 'ReportServer'. 2014-05-24 > 21:25:34.27 spid15s Starting up > database 'ReportServerTempDB'. > 2014-05-24 21:25:34.28 spid13s > Starting up database 'msdb'. > 2014-05-24 21:25:34.28 spid16s > Starting up database 'FileProcess'. > 2014-05-24 21:25:34.28 spid17s > Starting up database 'SSIS_TASK'. > 2014-05-24 21:25:34.29 spid18s > Starting up database 'DDS_MSG'. > 2014-05-24 21:25:34.69 spid13s 670 > transactions rolled forward in > database 'msdb' (4). This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:34.71 spid10s Clearing > tempdb database. 2014-05-24 > 21:25:34.71 spid13s 0 transactions > rolled back in database 'msdb' (4). > This is an informational message only. > No user action is required. 2014-05-24 > 21:25:34.71 spid13s Recovery is > writing a checkpoint in database > 'msdb' (4). This is an informational > message only. No user action is > required. 2014-05-24 21:25:35.00 > spid51 Attempting to load library > 'xpstar.dll' into memory. This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:35.05 spid10s Starting up > database 'tempdb'. 2014-05-24 > 21:25:35.06 spid51 Using > 'xpstar.dll' version '2009.100.1600' > to execute extended stored procedure > 'xp_sqlagent_monitor'. This is an > informational message only; no user > action is required. 2014-05-24 > 21:25:35.06 spid16s 104 > transactions rolled forward in > database 'FileProcess' (7). This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:35.09 spid16s 0 transactions > rolled back in database 'FileProcess' > (7). This is an informational message > only. No user action is required. > 2014-05-24 21:25:35.09 spid16s > Recovery is writing a checkpoint in > database 'FileProcess' (7). This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:35.18 spid13s The Service > Broker protocol transport is disabled > or not configured. 2014-05-24 > 21:25:35.18 spid13s The Database > Mirroring protocol transport is > disabled or not configured. 2014-05-24 > 21:25:35.21 spid13s Service Broker > manager has started. 2014-05-24 > 21:25:37.59 spid17s Recovery of > database 'SSIS_TASK' (8) is 2% > complete (approximately 8 seconds > remain). Phase 1 of 3. This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:37.72 spid17s Recovery of > database 'SSIS_TASK' (8) is 4% > complete (approximately 8 seconds > remain). Phase 1 of 3. This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:38.58 spid17s 561 > transactions rolled forward in > database 'SSIS_TASK' (8). This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:38.59 spid17s 0 transactions > rolled back in database 'SSIS_TASK' > (8). This is an informational message > only. No user action is required. > 2014-05-24 21:25:38.59 spid17s > Recovery is writing a checkpoint in > database 'SSIS_TASK' (8). This is an > informational message only. No user > action is required. 2014-05-24 > 21:25:38.63 spid17s Recovery > completed for database SSIS_TASK > (database ID 8) in 1 second(s) > (analysis 404 ms, redo 858 ms, undo 7 > ms.) This is an informational message > only. No user action is required. > 2014-05-24 21:25:38.67 spid5s > Recovery is complete. This is an > informational message only. No user > action is required. 2014-05-25 > 00:00:53.82 spid20s This instance > of SQL Server has been using a process > ID of 19696 since 24/05/2014 9:25:38 > PM (local) 24/05/2014 11:25:38 AM > (UTC). This is an informational > message only; no user action is > required. 2014-05-25 05:00:26.60 > spid58 Error: 7393, Severity: 16, > State: 1. 2014-05-25 05:00:26.60 > spid58 The OLE DB provider > "SQLNCLI10" for linked server > "AUEXEHP" reported an error 0x8000FFFF > aborting the current transaction. > 2014-05-26 00:00:20.18 spid18s > This instance of SQL Server has been > using a process ID of 19696 since > 24/05/2014 9:25:38 PM (local) > 24/05/2014 11:25:38 AM (UTC). This is > an informational message only; no user > action is required. 2014-05-26 > 10:12:24.39 Logon Error: 18456, > Severity: 14, State: 5. 2014-05-26 > 10:12:24.39 Logon Login failed > for user 'vamsida'. Reason: Could not > find a login matching the name > provided. [CLIENT: 10.215.18.1] > 2014-05-26 10:12:39.87 Logon > Error: 18456, Severity: 14, State: 5. > 2014-05-26 10:12:39.87 Logon > Login failed for user 'sqladmin'. > Reason: Could not find a login > matching the name provided. [CLIENT: > 10.215.18.1] 2014-05-27 00:00:40.88 spid18s This instance of SQL > Server has been using a process ID of > 19696 since 24/05/2014 9:25:38 PM > (local) 24/05/2014 11:25:38 AM (UTC). > This is an informational message only; > no user action is required. 2014-05-28 > 00:00:39.59 spid21s This instance > of SQL Server has been using a process > ID of 19696 since 24/05/2014 9:25:38 > PM (local) 24/05/2014 11:25:38 AM > (UTC). This is an informational > message only; no user action is > required. 2014-05-28 15:55:12.67 > spid55 Attempting to load library > 'xplog70.dll' into memory. This is an > informational message only. No user > action is required. 2014-05-28 > 15:55:12.71 spid55 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. 2014-05-29 00:00:34.93 > spid20s This instance of SQL > Server has been using a process ID of > 19696 since 24/05/2014 9:25:38 PM > (local) 24/05/2014 11:25:38 AM (UTC). > This is an informational message only; > no user action is required. 2014-05-29 > 15:57:08.71 spid60 Error: 18054, > Severity: 16, State: 1. 2014-05-29 > 15:57:08.71 spid60 Error 50010, > severity 10, state 1 was raised, but > no message with that error number was > found in sys.messages. If error is > larger than 50000, make sure the > user-defined message is added using > sp_addmessage. 2014-05-30 00:00:15.82 > spid16s This instance of SQL > Server has been using a process ID of > 19696 since 24/05/2014 9:25:38 PM > (local) 24/05/2014 11:25:38 AM (UTC). > This is an informational message only; > no user action is required. 2014-05-30 > 10:41:47.09 Logon Error: 18456, > Severity: 14, State: 5. 2014-05-30 > 10:41:47.09 Logon Login failed > for user 'visuser1'. Reason: Could not > find a login matching the name > provided. [CLIENT: 10.213.172.121] > 2014-05-31 00:00:36.46 spid18s > This instance of SQL Server has been > using a process ID of 19696 since > 24/05/2014 9:25:38 PM (local) > 24/05/2014 11:25:38 AM (UTC). This is > an informational message only; no user > action is required. 2014-05-31 > 17:06:07.86 Logon Error: 18456, > Severity: 14, State: 8. 2014-05-31 > 17:06:07.86 Logon Login failed > for user 'linkedsrvradmin'. Reason: > Password did not match that for the > login provided. [CLIENT: > 10.215.222.121] 2014-06-01 00:00:49.59 spid20s This instance of SQL > Server has been using a process ID of > 19696 since 24/05/2014 9:25:38 PM > (local) 24/05/2014 11:25:38 AM (UTC). > This is an informational message only; > no user action is required. 2014-06-02 > 00:00:19.86 spid21s This instance > of SQL Server has been using a process > ID of 19696 since 24/05/2014 9:25:38 > PM (local) 24/05/2014 11:25:38 AM > (UTC). This is an informational > message only; no user action is > required. 2014-06-02 12:37:44.64 Logon > Error: 18456, Severity: 14, State: 8. > 2014-06-02 12:37:44.64 Logon > Login failed for user > 'linkedsrvradmin'. Reason: Password > did not match that for the login > provided. [CLIENT: 10.215.222.121] > 2014-06-02 12:37:48.09 Logon > Error: 18456, Severity: 14, State: 8. > 2014-06-02 12:37:48.09 Logon > Login failed for user > 'linkedsrvradmin'. Reason: Password > did not match that for the login > provided. [CLIENT: 10.215.222.121] > 2014-06-02 12:38:15.96 Logon > Error: 18456, Severity: 14, State: 8. > 2014-06-02 12:38:15.96 Logon > Login failed for user > 'linkedsrvradmin'. Reason: Password > did not match that for the login > provided. [CLIENT: 10.215.222.121] > 2014-06-02 12:39:36.73 Logon > Error: 18456, Severity: 14, State: 8. > 2014-06-02 12:39:36.73 Logon > Login failed for user > 'linkedsrvradmin'. Reason: Password > did not match that for the login > provided. [CLIENT: 10.215.222.121] > 2014-06-03 00:01:00.98 spid18s > This instance of SQL Server has been > using a process ID of 19696 since > 24/05/2014 9:25:38 PM (local) > 24/05/2014 11:25:38 AM (UTC). This is > an informational message only; no user > action is required. 2014-06-04 > 00:00:30.66 spid16s This instance > of SQL Server has been using a process > ID of 19696 since 24/05/2014 9:25:38 > PM (local) 24/05/2014 11:25:38 AM > (UTC). This is an informational > message only; no user action is > required. 2014-06-05 00:00:57.90 > spid19s This instance of SQL > Server has been using a process ID of > 19696 since 24/05/2014 9:25:38 PM > (local) 24/05/2014 11:25:38 AM (UTC). > This is an informational message only; > no user action is required. 2014-06-06 > 00:00:25.99 spid20s This instance > of SQL Server has been using a process > ID of 19696 since 24/05/2014 9:25:38 > PM (local) 24/05/2014 11:25:38 AM > (UTC). This is an informational > message only; no user action is > required. 2014-06-07 00:00:59.51 > spid22s This instance of SQL > Server has been using a process ID of > 19696 since 24/05/2014 9:25:38 PM > (local) 24/05/2014 11:25:38 AM (UTC). > This is an informational message only; > no user action is required. 2014-06-08 > 00:00:53.11 spid24s This instance > of SQL Server has been using a process > ID of 19696 since 24/05/2014 9:25:38 > PM (local) 24/05/2014 11:25:38 AM > (UTC). This is an informational > message only; no user action is > required. 2014-06-09 00:00:08.88 > spid18s This instance of SQL > Server has been using a process ID of > 19696 since 24/05/2014 9:25:38 PM > (local) 24/05/2014 11:25:38 AM (UTC). > This is an informational message only; > no user action is required. 2014-06-10 > 00:00:30.30 spid22s This instance > of SQL Server has been using a process > ID of 19696 since 24/05/2014 9:25:38 > PM (local) 24/05/2014 11:25:38 AM > (UTC). This is an informational > message only; no user action is > required. 2014-06-11 00:00:57.04 > spid19s This instance of SQL > Server has been using a process ID of > 19696 since 24/05/2014 9:25:38 PM > (local) 24/05/2014 11:25:38 AM (UTC). > This is an informational message only; > no user action is required. 2014-06-12 > 00:00:14.17 spid18s This instance > of SQL Server has been using a process > ID of 19696 since 24/05/2014 9:25:38 > PM (local) 24/05/2014 11:25:38 AM > (UTC). This is an informational > message only; no user action is > required. > > > > > > 2014-06-12 10:01:16.35 Server > Microsoft SQL Server 2008 R2 (RTM) - > 10.50.1617.0 (X64) Apr 22 2011 19:23:43 Copyright (c) Microsoft > Corporation Standard Edition (64-bit) > on Windows NT 6.1 (Build 7601: > Service Pack 1) (Hypervisor) > > 2014-06-12 10:01:16.36 Server (c) > Microsoft Corporation. 2014-06-12 > 10:01:16.36 Server All rights > reserved. 2014-06-12 10:01:16.36 > Server Server process ID is > 14668. 2014-06-12 10:01:16.36 Server System Manufacturer: 'VMware, Inc.', > System Model: 'VMware Virtual > Platform'. 2014-06-12 10:01:16.36 > Server Authentication mode is > MIXED. 2014-06-12 10:01:16.36 Server > Logging SQL Server messages in file > 'C:\Program Files\Microsoft SQL > Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'. > 2014-06-12 10:01:16.36 Server > This instance of SQL Server last > reported using a process ID of 19696 > at 12/06/2014 10:00:35 AM (local) > 12/06/2014 12:00:35 AM (UTC). This is > an informational message only; no user > action is required. 2014-06-12 > 10:01:16.36 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 2014-06-12 10:01:16.41 Server SQL > Server is starting at normal priority > base (=7). This is an informational > message only. No user action is > required. 2014-06-12 10:01:16.41 > Server Detected 2 CPUs. This is > an informational message; no user > action is required. 2014-06-12 > 10:01:16.56 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. 2014-06-12 > 10:01:16.62 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. 2014-06-12 > 10:01:16.64 spid5s Starting up > database 'master'. 2014-06-12 > 10:01:16.82 spid5s 62 > transactions rolled forward in > database 'master' (1). This is an > informational message only. No user > action is required. 2014-06-12 > 10:01:16.91 spid5s 0 transactions > rolled back in database 'master' (1). > This is an informational message only. > No user action is required. 2014-06-12 > 10:01:16.91 spid5s Recovery is > writing a checkpoint in database > 'master' (1). This is an informational > message only. No user action is > required. 2014-06-12 10:01:17.07 > spid5s FILESTREAM: effective > level = 0, configured level = 0, file > system access share name = > 'MSSQLSERVER'. 2014-06-12 10:01:17.09 > spid5s SQL Trace ID 1 was started > by login "sa". 2014-06-12 10:01:17.09 > spid5s Starting up database > 'mssqlsystemresource'. 2014-06-12 > 10:01:17.11 spid5s The resource > database build version is 10.50.1617. > This is an informational message only. > No user action is required. 2014-06-12 > 10:01:17.52 spid10s Starting up > database 'model'. 2014-06-12 > 10:01:17.52 spid5s Server name is > 'AUPROC01'. This is an informational > message only. No user action is > required. 2014-06-12 10:01:17.80 > Server A self-generated > certificate was successfully loaded > for encryption. 2014-06-12 10:01:17.93 > Server Server is listening on [ > 'any' 1433]. 2014-06-12 10:01:17.93 > Server Server is listening on [ > 'any' 1433]. 2014-06-12 10:01:17.94 > Server Server local connection > provider is ready to accept connection > on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. > 2014-06-12 10:01:17.94 Server > Server local connection provider is > ready to accept connection on [ > \\.\pipe\sql\query ]. 2014-06-12 > 10:01:17.94 Server Server is > listening on [ ::1 1434]. 2014-06-12 > 10:01:17.95 Server Server is > listening on [ 127.0.0.1 1434]. > 2014-06-12 10:01:17.95 Server > Dedicated admin connection support was > established for listening locally on > port 1434. 2014-06-12 10:01:17.98 > Server The SQL Server Network > Interface library could not register > the Service Principal Name (SPN) for > the SQL Server service. Error: 0x2098, > state: 15. 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. 2014-06-12 > 10:01:17.98 Server SQL Server is > now ready for client connections. This > is an informational message; no user > action is required. 2014-06-12 > 10:01:18.31 spid13s A new instance > of the full-text filter daemon host > process has been successfully started. > 2014-06-12 10:01:18.40 Logon > Error: 18456, Severity: 14, State: 38. > 2014-06-12 10:01:18.40 Logon > Login failed for user > 'SCHLOGAU\sqladmin'. Reason: Failed to > open the explicitly specified > database. [CLIENT: > fe80::47f:a6c0:1e92:9a2%18] 2014-06-12 > 10:01:18.42 spid13s Starting up > database 'msdb'. 2014-06-12 > 10:01:18.42 spid14s Starting up > database 'ReportServer'. 2014-06-12 > 10:01:18.42 spid15s Starting up > database 'ReportServerTempDB'. > 2014-06-12 10:01:18.43 spid16s > Starting up database 'FileProcess'. > 2014-06-12 10:01:18.45 spid17s > Starting up database 'SSIS_TASK'. > 2014-06-12 10:01:18.45 spid18s > Starting up database 'DDS_MSG'. > 2014-06-12 10:01:19.06 spid10s > Clearing tempdb database. 2014-06-12 > 10:01:19.08 spid13s 391 > transactions rolled forward in > database 'msdb' (4). This is an > informational message only. No user > action is required. 2014-06-12 > 10:01:19.28 spid13s 0 transactions > rolled back in database 'msdb' (4). > This is an informational message only. > No user action is required. 2014-06-12 > 10:01:19.28 spid13s Recovery is > writing a checkpoint in database > 'msdb' (4). This is an informational > message only. No user action is > required. 2014-06-12 10:01:19.58 > spid10s Starting up database > 'tempdb'. 2014-06-12 10:01:19.69 > spid51 Attempting to load library > 'xpstar.dll' into memory. This is an > informational message only. No user > action is required. 2014-06-12 > 10:01:19.71 spid16s 749 > transactions rolled forward in > database 'FileProcess' (7). This is an > informational message only. No user > action is required. 2014-06-12 > 10:01:19.84 spid51 Using > 'xpstar.dll' version '2009.100.1600' > to execute extended stored procedure > 'xp_sqlagent_monitor'. This is an > informational message only; no user > action is required. 2014-06-12 > 10:01:19.84 spid16s 0 transactions > rolled back in database 'FileProcess' > (7). This is an informational message > only. No user action is required. > 2014-06-12 10:01:19.85 spid16s > Recovery is writing a checkpoint in > database 'FileProcess' (7). This is an > informational message only. No user > action is required. 2014-06-12 > 10:01:20.00 spid13s The Service > Broker protocol transport is disabled > or not configured. 2014-06-12 > 10:01:20.00 spid13s The Database > Mirroring protocol transport is > disabled or not configured. 2014-06-12 > 10:01:20.03 spid13s Service Broker > manager has started. 2014-06-12 > 10:01:22.03 Logon Error: 18456, > Severity: 14, State: 38. 2014-06-12 > 10:01:22.03 Logon Login failed > for user 'SCHLOGAU\sqladmin'. Reason: > Failed to open the explicitly > specified database. [CLIENT: ] > 2014-06-12 10:01:23.17 spid17s 173 > transactions rolled forward in > database 'SSIS_TASK' (8). This is an > informational message only. No user > action is required. 2014-06-12 > 10:01:23.18 spid17s 0 transactions > rolled back in database 'SSIS_TASK' > (8). This is an informational message > only. No user action is required. > 2014-06-12 10:01:23.19 spid17s > Recovery is writing a checkpoint in > database 'SSIS_TASK' (8). This is an > informational message only. No user > action is required. 2014-06-12 > 10:01:23.25 spid5s Recovery is > complete. This is an informational > message only. No user action is > required. 2014-06-12 17:26:04.04 Logon > Error: 18456, Severity: 14, State: 5. > 2014-06-12 17:26:04.04 Logon > Login failed for user 'sqladmin'. > Reason: Could not find a login > matching the name provided. [CLIENT: > 10.213.172.205] 2014-06-12 17:26:32.57 Logon Error: 18456, Severity: > 14, State: 5. 2014-06-12 17:26:32.57 > Logon Login failed for user > 'sqladmin'. Reason: Could not find a > login matching the name provided. > [CLIENT: 10.213.172.205] 2014-06-12 > 17:27:21.93 Logon Error: 18456, > Severity: 14, State: 5. 2014-06-12 > 17:27:21.93 Logon Login failed > for user 'vamsida'. Reason: Could not > find a login matching the name > provided. [CLIENT: 10.213.172.205] > 2014-06-12 17:28:37.94 Logon > Error: 18456, Severity: 14, State: 5. > 2014-06-12 17:28:37.94 Logon > Login failed for user 'vamsida'. > Reason: Could not find a login > matching the name provided. [CLIENT: ] > 2014-06-13 00:00:44.25 spid21s > This instance of SQL Server has been > using a process ID of 14668 since > 12/06/2014 10:01:23 AM (local) > 12/06/2014 12:01:23 AM (UTC). This is > an informational message only; no user > action is required. 2014-06-13 > 13:46:36.58 Logon Error: 17806, > Severity: 20, State: 14. 2014-06-13 > 13:46:36.58 Logon SSPI handshake > failed with error code 0x8009030c, > state 14 while establishing a > connection with integrated security; > the connection has been closed. > Reason: AcceptSecurityContext failed. > The Windows error code indicates the > cause of failure. [CLIENT: > 10.215.192.149]. 2014-06-13 13:46:36.58 Logon Error: 18452, > Severity: 14, State: 1. 2014-06-13 > 13:46:36.58 Logon Login failed. > The login is from an untrusted domain > and cannot be used with Windows > authentication. [CLIENT: > 10.215.192.149] 2014-06-13 15:49:56.75 Logon Error: 17806, Severity: > 20, State: 14. 2014-06-13 15:49:56.75 > Logon SSPI handshake failed with > error code 0x8009030c, state 14 while > establishing a connection with > integrated security; the connection > has been closed. Reason: > AcceptSecurityContext failed. The > Windows error code indicates the cause > of failure. [CLIENT: 10.215.192.149]. > 2014-06-13 15:49:56.75 Logon > Error: 18452, Severity: 14, State: 1. > 2014-06-13 15:49:56.75 Logon > Login failed. The login is from an > untrusted domain and cannot be used > with Windows authentication. [CLIENT: > 10.215.192.149] 2014-06-14 00:00:26.55 spid18s This instance of SQL > Server has been using a process ID of > 14668 since 12/06/2014 10:01:23 AM > (local) 12/06/2014 12:01:23 AM (UTC). > This is an informational message only; > no user action is required. 2014-06-15 > 00:00:24.34 spid22s This instance > of SQL Server has been using a process > ID of 14668 since 12/06/2014 10:01:23 > AM (local) 12/06/2014 12:01:23 AM > (UTC). This is an informational > message only; no user action is > required. 2014-06-15 05:00:17.17 > spid60 Error: 7393, Severity: 16, > State: 1. 2014-06-15 05:00:17.17 > spid60 The OLE DB provider > "SQLNCLI10" for linked server > "AUEXEHP" reported an error 0x8000FFFF > aborting the current transaction. > 2014-06-16 00:00:40.26 spid24s > This instance of SQL Server has been > using a process ID of 14668 since > 12/06/2014 10:01:23 AM (local) > 12/06/2014 12:01:23 AM (UTC). This is > an informational message only; no user > action is required.
administration
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ramesh 1 avatar image
ramesh 1 answered
did any one change linkedsrvradmin password ,if yes fix it
5 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

linkedserver admin causing the SQLSRVER Services termination?
0 Likes 0 ·
how did you start your SQL Server Services with a user Name local Service
0 Likes 0 ·
SQLAdmin user is used as
0 Likes 0 ·
SQLADMIN user name
0 Likes 0 ·
can u please give me a solution to this issue
0 Likes 0 ·
Grant Fritchey avatar image
Grant Fritchey answered
There's not enough stuff in the error log to understand why the server is going offline. You should also look to the Windows error log. It does look like you're hitting a series of login failures, but there's no indication that's what's causing the server to fail (at least that I can see, it's hard to read through a couple of hundred lines of raw text). The Windows error log may provide more. Fact is, most of these two error logs are showing us the server coming online, not the crash. Since this is a VM, you should also look to the VMware logs, there may be indications there.
2 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

I got this error from windows event logs. Event ID=7034. In sqlserver errorlog there is no information about this issue that's why i'm struggling
0 Likes 0 ·
Is there any Servicepack problem for not updating the failure information in errorlog
0 Likes 0 ·
shwetha avatar image
shwetha answered
Check if the account is locked then unlock it.
1 comment
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

How to check if account is expired or locked
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.