Quantcast
Channel: Forum Getting started with SQL Server
Viewing all articles
Browse latest Browse all 7129

ISSUES WITH SQL SERVER 2008 R2

$
0
0

Hello, <g class="gr_ gr_60 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="60" id="60">i</g> have a server that has been having issues!  This is the <g class="gr_ gr_81 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="81" id="81">errror</g> log. 

Date,Source,Severity,Message
03/21/2019 10:21:34,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.63.63]
03/21/2019 10:21:34,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:21:34,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.63.63].
03/21/2019 10:21:34,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:21:27,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.93.122]
03/21/2019 10:21:27,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:21:27,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.93.122].
03/21/2019 10:21:27,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:21:18,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.93.122]
03/21/2019 10:21:18,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:21:18,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.93.122].
03/21/2019 10:21:18,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:21:09,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.93.122]
03/21/2019 10:21:09,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:21:09,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.93.122].
03/21/2019 10:21:09,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:21:03,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.63.63]
03/21/2019 10:21:03,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:21:03,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.63.63]
03/21/2019 10:21:03,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:21:03,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.93.122]
03/21/2019 10:21:03,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:21:03,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.93.122]
03/21/2019 10:21:03,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:21:03,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.63.63].
03/21/2019 10:21:03,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:21:03,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.63.63].
03/21/2019 10:21:03,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:21:03,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.93.122].
03/21/2019 10:21:03,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:21:03,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.93.122].
03/21/2019 10:21:03,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:12:13,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.92.251]
03/21/2019 10:12:13,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:12:13,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.92.251].
03/21/2019 10:12:13,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:11:45,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.92.251]
03/21/2019 10:11:45,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:11:45,Logon,Unknown,Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.92.251]
03/21/2019 10:11:45,Logon,Unknown,Error: 18452<c/> Severity: 14<c/> State: 1.
03/21/2019 10:11:45,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.92.251].
03/21/2019 10:11:45,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 10:11:45,Logon,Unknown,SSPI handshake failed with error code 0x80090311<c/> 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.10.92.251].
03/21/2019 10:11:45,Logon,Unknown,Error: 17806<c/> Severity: 20<c/> State: 14.
03/21/2019 00:00:41,spid34s,Unknown,This instance of SQL Server has been using a process ID of 12556 since 3/19/2019 9:43:25 AM (local) 3/19/2019 12:43:25 PM (UTC). This is an informational message only; no user action is required.
03/20/2019 22:07:23,Backup,Unknown,Database backed up. Database: Lincoln_XE<c/> creation date(time): 2016/07/19(10:41:13)<c/> pages dumped: 2681568<c/> first LSN: 608266:201406:46<c/> last LSN: 608266:201426:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\Lincoln_XE\Lincoln_XE_backup_2019_03_20_220001_5427969.bak'}). This is an informational message only. No user action is required.
03/20/2019 22:00:27,Backup,Unknown,Database backed up. Database: lansweeperdb<c/> creation date(time): 2016/07/20(15:53:14)<c/> pages dumped: 109838<c/> first LSN: 589560:229:203<c/> last LSN: 589560:312:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\lansweeperdb\lansweeperdb_backup_2019_03_20_220001_5427969.bak'}). This is an informational message only. No user action is required.
03/20/2019 22:00:04,Backup,Unknown,Database backed up. Database: HealthRecords<c/> creation date(time): 2016/07/20(11:03:30)<c/> pages dumped: 1802<c/> first LSN: 7308:434:37<c/> last LSN: 7308:450:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\HealthRecords\HealthRecords_backup_2019_03_20_220001_5427969.bak'}). This is an informational message only. No user action is required.
03/20/2019 22:00:04,Backup,Unknown,Database backed up. Database: CITI<c/> creation date(time): 2016/07/19(10:34:17)<c/> pages dumped: 938<c/> first LSN: 411:490:37<c/> last LSN: 411:506:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\CITI\CITI_backup_2019_03_20_220001_5427969.bak'}). This is an informational message only. No user action is required.
03/20/2019 22:00:03,Backup,Unknown,Database backed up. Database: CANOPUS<c/> creation date(time): 2016/07/19(13:38:11)<c/> pages dumped: 12501<c/> first LSN: 3822:1240:167<c/> last LSN: 3822:1305:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\CANOPUS\CANOPUS_backup_2019_03_20_220001_5272109.bak'}). This is an informational message only. No user action is required.
03/20/2019 22:00:02,Backup,Unknown,Database backed up. Database: BigBangAcad<c/> creation date(time): 2016/07/19(13:28:34)<c/> pages dumped: 1546<c/> first LSN: 7825:311:37<c/> last LSN: 7825:327:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\BigBangAcad\BigBangAcad_backup_2019_03_20_220001_5272109.bak'}). This is an informational message only. No user action is required.
03/20/2019 22:00:02,Backup,Unknown,Database backed up. Database: Bigbang<c/> creation date(time): 2016/07/19(13:28:26)<c/> pages dumped: 17034<c/> first LSN: 14292:139:194<c/> last LSN: 14292:214:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\Bigbang\Bigbang_backup_2019_03_20_220001_5272109.bak'}). This is an informational message only. No user action is required.
03/20/2019 21:08:26,Logon,Unknown,Login failed for user 'LINCOLN-EDU-AR\services'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 10.10.4.4]
03/20/2019 21:08:26,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 11.
03/20/2019 21:08:26,Logon,Unknown,Login failed for user 'LINCOLN-EDU-AR\services'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
03/20/2019 21:08:26,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 11.
03/20/2019 18:11:06,spid67,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 18:10:11,spid59,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 18:00:34,spid59,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:59:56,spid54,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 17:46:23,spid61,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:45:35,spid59,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 17:36:50,spid59,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:36:41,spid54,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 17:34:36,spid65,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:33:53,spid54,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 17:33:21,spid61,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:33:09,spid54,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 17:33:05,spid61,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:31:22,spid54,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 17:30:23,spid59,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:29:54,spid54,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 17:26:44,spid63,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:26:08,spid54,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 17:25:17,spid61,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'CanopusUserLincoln'.
03/20/2019 17:24:34,spid54,Unknown,SQL Trace ID 2 was started by login "CanopusUserLincoln".
03/20/2019 10:09:45,Logon,Unknown,Login failed for user 'FLORENCIA.LAZORENCO'. Reason: Could not find a login matching the name provided. [CLIENT: 10.10.91.106]
03/20/2019 10:09:45,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
03/20/2019 10:09:40,Logon,Unknown,Login failed for user 'FLORENCIA.LAZORENCO'. Reason: Could not find a login matching the name provided. [CLIENT: 10.10.91.106]
03/20/2019 10:09:40,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 5.
03/20/2019 00:00:32,spid29s,Unknown,This instance of SQL Server has been using a process ID of 12556 since 3/19/2019 9:43:25 AM (local) 3/19/2019 12:43:25 PM (UTC). This is an informational message only; no user action is required.
03/19/2019 22:07:21,Backup,Unknown,Database backed up. Database: Lincoln_XE<c/> creation date(time): 2016/07/19(10:41:13)<c/> pages dumped: 2679391<c/> first LSN: 608266:184580:32<c/> last LSN: 608266:184595:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\Lincoln_XE\Lincoln_XE_backup_2019_03_19_220002_0091581.bak'}). This is an informational message only. No user action is required.
03/19/2019 22:00:23,Backup,Unknown,Database backed up. Database: lansweeperdb<c/> creation date(time): 2016/07/20(15:53:14)<c/> pages dumped: 109710<c/> first LSN: 589357:523:182<c/> last LSN: 589357:600:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\lansweeperdb\lansweeperdb_backup_2019_03_19_220001_9935583.bak'}). This is an informational message only. No user action is required.
03/19/2019 22:00:04,Backup,Unknown,Database backed up. Database: HealthRecords<c/> creation date(time): 2016/07/20(11:03:30)<c/> pages dumped: 1802<c/> first LSN: 7308:359:37<c/> last LSN: 7308:375:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\HealthRecords\HealthRecords_backup_2019_03_19_220001_9935583.bak'}). This is an informational message only. No user action is required.
03/19/2019 22:00:04,Backup,Unknown,Database backed up. Database: CITI<c/> creation date(time): 2016/07/19(10:34:17)<c/> pages dumped: 938<c/> first LSN: 411:467:37<c/> last LSN: 411:483:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\CITI\CITI_backup_2019_03_19_220001_9935583.bak'}). This is an informational message only. No user action is required.
03/19/2019 22:00:04,Backup,Unknown,Database backed up. Database: CANOPUS<c/> creation date(time): 2016/07/19(13:38:11)<c/> pages dumped: 12501<c/> first LSN: 3821:6320:115<c/> last LSN: 3821:6364:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\CANOPUS\CANOPUS_backup_2019_03_19_220001_9935583.bak'}). This is an informational message only. No user action is required.
03/19/2019 22:00:03,Backup,Unknown,Database backed up. Database: BigBangAcad<c/> creation date(time): 2016/07/19(13:28:34)<c/> pages dumped: 1546<c/> first LSN: 7825:227:37<c/> last LSN: 7825:243:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\BigBangAcad\BigBangAcad_backup_2019_03_19_220001_9779585.bak'}). This is an informational message only. No user action is required.
03/19/2019 22:00:03,Backup,Unknown,Database backed up. Database: Bigbang<c/> creation date(time): 2016/07/19(13:28:26)<c/> pages dumped: 17034<c/> first LSN: 14291:393:202<c/> last LSN: 14291:473:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\BAS_DB_BACKUPS\Bigbang\Bigbang_backup_2019_03_19_220001_9779585.bak'}). This is an informational message only. No user action is required.
03/19/2019 21:07:12,Logon,Unknown,Login failed for user 'LINCOLN-EDU-AR\services'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 10.10.4.4]
03/19/2019 21:07:12,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 11.
03/19/2019 21:07:12,Logon,Unknown,Login failed for user 'LINCOLN-EDU-AR\services'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
03/19/2019 21:07:12,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 11.
03/19/2019 14:23:42,Logon,Unknown,Login failed for user 'Maximiliano.Reboreda'. Reason: Password did not match that for the login provided. [CLIENT: 10.10.94.110]
03/19/2019 14:23:42,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
03/19/2019 14:23:42,Logon,Unknown,Login failed for user 'Maximiliano.Reboreda'. Reason: Password did not match that for the login provided. [CLIENT: 10.10.94.110]
03/19/2019 14:23:42,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
03/19/2019 14:23:41,Logon,Unknown,Login failed for user 'Maximiliano.Reboreda'. Reason: Password did not match that for the login provided. [CLIENT: 10.10.94.110]
03/19/2019 14:23:41,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
03/19/2019 14:23:37,Logon,Unknown,Login failed for user 'Maximiliano.Reboreda'. Reason: Password did not match that for the login provided. [CLIENT: 10.10.94.110]
03/19/2019 14:23:37,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 8.
03/19/2019 13:07:38,Backup,Unknown,Database backed up. Database: CANOPUS<c/> creation date(time): 2016/07/19(13:38:11)<c/> pages dumped: 12501<c/> first LSN: 3821:4582:81<c/> last LSN: 3821:4614:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\BAS\Distribucion\bkcanopus.bak'}). This is an informational message only. No user action is required.
03/19/2019 11:31:54,spid68,Unknown,SQL Trace stopped. Trace ID = '2'. Login Name = 'LINCOLN-EDU-AR\Administrator'.
03/19/2019 11:30:52,spid76,Unknown,SQL Trace ID 2 was started by login "LINCOLN-EDU-AR\Administrator".
03/19/2019 09:43:59,spid51,Unknown,Using 'xplog70.dll' version '2009.100.6000' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
03/19/2019 09:43:59,spid51,Unknown,Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
03/19/2019 09:43:58,spid51,Unknown,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.
03/19/2019 09:43:58,spid51,Unknown,Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
03/19/2019 09:43:58,spid51,Unknown,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.
03/19/2019 09:43:58,spid51,Unknown,Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
03/19/2019 09:43:58,spid51,Unknown,FILESTREAM: effective level = 3<c/> configured level = 3<c/> file system access share name = 'MSSQLSERVER'.
03/19/2019 09:43:58,spid51,Unknown,Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
03/19/2019 09:43:57,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
03/19/2019 09:43:57,Server,Unknown,The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/APPLICATIONS.lincoln.edu.ar:1433 ] for the SQL Server service.
03/19/2019 09:43:57,Server,Unknown,The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/APPLICATIONS.lincoln.edu.ar ] for the SQL Server service.
03/19/2019 09:43:43,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: <local machine>]
03/19/2019 09:43:43,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:42,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: <local machine>]
03/19/2019 09:43:42,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:39,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: <local machine>]
03/19/2019 09:43:39,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:30,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.93.122]
03/19/2019 09:43:30,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:30,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.93.122]
03/19/2019 09:43:30,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:25,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.93.122]
03/19/2019 09:43:25,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:25,spid9s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
03/19/2019 09:43:25,spid40s,Unknown,CHECKDB for database 'Lincoln_XE' finished without errors on 2019-03-17 01:00:45.230 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:25,spid9s,Unknown,Recovery is writing a checkpoint in database 'Lincoln_XE' (9). This is an informational message only. No user action is required.
03/19/2019 09:43:24,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.93.122]
03/19/2019 09:43:24,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:24,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.93.122]
03/19/2019 09:43:24,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:23,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:23,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:23,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:23,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:23,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:23,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:23,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:23,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:23,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:23,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:23,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:23,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:23,spid39s,Unknown,CHECKDB for database 'Lincoln' finished without errors on 2015-10-03 02:00:10.357 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:19,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.93.122]
03/19/2019 09:43:19,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:19,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.93.122]
03/19/2019 09:43:19,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:19,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: <local machine>]
03/19/2019 09:43:19,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:19,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: <local machine>]
03/19/2019 09:43:19,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:18,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:18,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:18,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:18,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:18,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:18,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:18,spid42s,Unknown,CHECKDB for database 'Lincoln_XE_test' finished without errors on 2016-07-02 02:13:59.820 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:18,spid43s,Unknown,CHECKDB for database 'Lincoln_XE_test_440' finished without errors on 2016-07-02 02:18:59.217 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:17,spid41s,Unknown,CHECKDB for database 'Lincoln_XE_440' finished without errors on 2016-07-02 02:09:59.867 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:17,spid44s,Unknown,CHECKDB for database 'lansweeperdb' finished without errors on 2016-07-02 02:13:28.383 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:17,spid9s,Unknown,Recovery is writing a checkpoint in database 'lansweeperdb' (13). This is an informational message only. No user action is required.
03/19/2019 09:43:16,spid46s,Unknown,CHECKDB for database 'HealthRecordsTraining' finished without errors on 2016-07-02 02:18:57.510 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:16,spid48s,Unknown,CHECKDB for database '2016AHealthRecordsArchive' finished without errors on 2016-07-02 02:13:53.187 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:16,spid49s,Unknown,CHECKDB for database '2016BHealthRecordsArchive' finished without errors on 2016-07-02 02:18:48.933 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:16,spid53s,Unknown,CHECKDB for database '2016CHealthRecordsArchive' finished without errors on 2016-07-02 02:23:56.890 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:16,spid45s,Unknown,CHECKDB for database 'HealthRecords' finished without errors on 2016-07-20 11:48:26.950 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:16,spid50s,Unknown,CHECKDB for database 'Bigbang' finished without errors on 2018-01-30 12:24:58.283 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:16,spid47s,Unknown,CHECKDB for database '2015AHealthRecordsArchive' finished without errors on 2016-07-02 02:05:02.750 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:16,spid38s,Unknown,CHECKDB for database 'CITI' finished without errors on 2016-07-02 02:18:48.107 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:16,spid51s,Unknown,Recovery is writing a checkpoint in database 'Bigbang' (19). This is an informational message only. No user action is required.
03/19/2019 09:43:16,spid51s,Unknown,CHECKDB for database 'BigBangAcad' finished without errors on 2016-07-02 02:18:53.040 (local time). This is an informational message only; no user action is required.
03/19/2019 09:43:15,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:15,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:15,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:15,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:15,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:15,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:15,spid56s,Unknown,Starting up database 'SUSDB'.
03/19/2019 09:43:15,Logon,Unknown,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<c/> look for the informational message that indicates that SQL Server is ready before trying to connect again.  [CLIENT: 10.10.94.43]
03/19/2019 09:43:15,Logon,Unknown,Error: 17187<c/> Severity: 16<c/> State: 1.
03/19/2019 09:43:15,spid55s,Unknown,Starting up database 'CANOPUS.LINCOLN.MAR17'.
03/19/2019 09:43:15,spid54s,Unknown,Starting up database 'BASAP'.
03/19/2019 09:43:15,spid53s,Unknown,Starting up database '2016CHealthRecordsArchive'.
03/19/2019 09:43:15,spid52s,Unknown,Starting up database 'CANOPUS'.
03/19/2019 09:43:15,spid51s,Unknown,Starting up database 'BigBangAcad'.
03/19/2019 09:43:15,spid50s,Unknown,Starting up database 'Bigbang'.
03/19/2019 09:43:15,spid49s,Unknown,Starting up database '2016BHealthRecordsArchive'.
03/19/2019 09:43:15,spid48s,Unknown,Starting up database '2016AHealthRecordsArchive'.
03/19/2019 09:43:15,spid47s,Unknown,Starting up database '2015AHealthRecordsArchive'.
03/19/2019 09:43:15,spid46s,Unknown,Starting up database 'HealthRecordsTraining'.
03/19/2019 09:43:15,spid45s,Unknown,Starting up database 'HealthRecords'.
03/19/2019 09:43:15,spid44s,Unknown,Starting up database 'lansweeperdb'.
03/19/2019 09:43:15,spid43s,Unknown,Starting up database 'Lincoln_XE_test_440'.
03/19/2019 09:43:15,spid42s,Unknown,Starting up database 'Lincoln_XE_test'.
03/19/2019 09:43:15,spid41s,Unknown,Starting up database 'Lincoln_XE_440'.
03/19/2019 09:43:15,spid40s,Unknown,Starting up database 'Lincoln_XE'.
03/19/2019 09:43:15,spid39s,Unknown,Starting up database 'Lincoln'.
03/19/2019 09:43:15,spid38s,Unknown,Starting up database 'CITI'.
03/19/2019 09:43:15,spid37s,Unknown,Starting up database 'ReportServerTempDB'.
03/19/2019 09:43:15,spid36s,Unknown,Starting up database 'ReportServer'.
03/19/2019 09:43:15,spid35s,Unknown,Starting up database 'msdb'.
03/19/2019 09:43:15,spid35s,Unknown,A new instance of the full-text filter daemon host process has been successfully started.
03/19/2019 09:43:15,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
03/19/2019 09:43:15,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
03/19/2019 09:43:15,Server,Unknown,Server is listening on [ ::1 <ipv6> 1434].
03/19/2019 09:43:15,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
03/19/2019 09:43:15,Server,Unknown,Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
03/19/2019 09:43:15,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
03/19/2019 09:43:15,Server,Unknown,Server is listening on [ 'any' <ipv6> 1433].
03/19/2019 09:43:15,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
03/19/2019 09:43:15,spid20s,Unknown,Service Broker manager has started.
03/19/2019 09:43:15,spid20s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
03/19/2019 09:43:15,spid20s,Unknown,The Service Broker protocol transport is disabled or not configured.
03/19/2019 09:43:15,spid17s,Unknown,Starting up database 'tempdb'.
03/19/2019 09:43:15,spid17s,Unknown,Clearing tempdb database.
03/19/2019 09:43:15,spid17s,Unknown,Starting up database 'model'.
03/19/2019 09:43:15,spid9s,Unknown,Server name is 'APPLICATIONS'. This is an informational message only. No user action is required.
03/19/2019 09:43:15,spid9s,Unknown,The resource database build version is 10.50.6000. This is an informational message only. No user action is required.
03/19/2019 09:43:15,spid9s,Unknown,Starting up database 'mssqlsystemresource'.
03/19/2019 09:43:15,spid9s,Unknown,SQL Trace ID 1 was started by login "sa".
03/19/2019 09:43:15,spid9s,Unknown,FILESTREAM: effective level = 3<c/> configured level = 3<c/> file system access share name = 'MSSQLSERVER'.
03/19/2019 09:43:15,spid9s,Unknown,SQL Server Audit has started the audits. This is an informational message. No user action is required.<nl/><{39B75A24-0837-4CEC-AFDF-B960027AE07E}>RsFxNso initialized. InstanceId = 00000002<nl/><{50080099-5EC4-4EAF-A2A2-63C3DA97F8EB}>FsAgent is initialized<nl/><{09C4480B-DBA4-49B7-956F-68A8B8B2445D}>FsAgent is up and running
03/19/2019 09:43:15,spid9s,Unknown,SQL Server Audit is starting the audits. This is an informational message. No user action is required.
03/19/2019 09:43:15,spid9s,Unknown,Resource governor reconfiguration succeeded.
03/19/2019 09:43:15,spid9s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
03/19/2019 09:43:15,spid9s,Unknown,Starting up database 'master'.
03/19/2019 09:43:15,Server,Unknown,Node configuration: node 1: CPU mask: 0x000000000000003f:0 Active CPU mask: 0x000000000000003f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
03/19/2019 09:43:15,Server,Unknown,Node configuration: node 0: CPU mask: 0x0000000000000fc0:0 Active CPU mask: 0x0000000000000fc0:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
03/19/2019 09:43:14,Server,Unknown,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.
03/19/2019 09:43:14,Server,Unknown,Using locked pages for buffer pool.
03/19/2019 09:43:14,Server,Unknown,Large Page Allocated: 32MB
03/19/2019 09:43:14,Server,Unknown,Large Page Allocated: 32MB
03/19/2019 09:43:14,Server,Unknown,Large Page Granularity: 2097152
03/19/2019 09:43:14,Server,Unknown,Large Page Extensions enabled.
03/19/2019 09:43:14,Server,Unknown,Detected 12 CPUs. This is an informational message; no user action is required.
03/19/2019 09:43:14,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
03/19/2019 09:43:14,Server,Unknown,Registry startup parameters: <nl/>-d D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf<nl/>-e D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG<nl/>-l D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
03/19/2019 09:43:14,Server,Unknown,This instance of SQL Server last reported using a process ID of 2464 at 3/19/2019 9:42:28 AM (local) 3/19/2019 12:42:28 PM (UTC). This is an informational message only; no user action is required.
03/19/2019 09:43:14,Server,Unknown,Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
03/19/2019 09:43:14,Server,Unknown,Authentication mode is MIXED.
03/19/2019 09:43:14,Server,Unknown,System Manufacturer: 'Dell Inc.'<c/> System Model: 'PowerEdge R730xd'.
03/19/2019 09:43:14,Server,Unknown,Server process ID is 12556.
03/19/2019 09:43:14,Server,Unknown,All rights reserved.
03/19/2019 09:43:14,Server,Unknown,(c) Microsoft Corporation.
03/19/2019 09:43:14,Server,Unknown,Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64) <nl/>Aug 19 2014 12:21:34 <nl/>Copyright (c) Microsoft Corporation<nl/>Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

Can someone help? Or give me a clue on how to fix this?


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>