asked on

SQL Server error

Can any one help me in this error?

SOLUTION

Pawan Kumar

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Éric Moreau

do you have access to Harris-PC? Is there a firewall preventing you from accessing the server? Are you sure you can use Windows Authentication? Try out by entering valid SQL credentials first

Ann K

ASKER

Is their anything I am missing here.

Ann K

ASKER

>Try out by entering valid SQL credentials first

Where can I find out SQL credentials?

Ann K

ASKER

I tried sa with sa password and also without password but it doesn't work.

Ann K

ASKER

How to check the firewall

>Is there a firewall preventing you from accessing the server?

sameer2010

You can go to Control Panel->All Control Panel Items->Windows Firewall->Advanced Settings->Allow a specific program to connect in inbound and outbound connections. Check if 1433, 1434 is enabled in firewall to be accessible outside the server.

Ann K

ASKER

Where is that option?
>Allow a specific program to connect in inbound and outbound connections. Check if 1433, 1434 is enabled in firewall to be accessible outside the server.

Nakul Vachhrajani

Based on the screenshot, your SQL Server service itself is stopped. Try starting the service from the SQL Server Configuration Manager.

Ann K

ASKER

Error when trying to start service.

Éric Moreau

have you checked the error logs as indicated by the error message?

Ann K

ASKER

How to check the error log?

SOLUTION

Éric Moreau

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Ann K

ASKER

Where I check for the error?

SOLUTION

sameer2010

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Ann K

ASKER

How to check if 1433, 1434 is enabled in firewall to be accessible outside the server.

SOLUTION

Daniel Jones

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Nakul Vachhrajani

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Ann K

ASKER

I can't find this in control panel.

Go to control panel -> Open Local services window -> select MSSQLSERVER service and restart.

ASKER CERTIFIED SOLUTION

Vitor Montalvão

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Ann K

ASKER

2016-12-18 10:39:30.25 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (Intel X86) 
	Feb 20 2014 19:20:46 
	Copyright (c) Microsoft Corporation
	Enterprise Edition on Windows NT 6.1 <X64> (Build 7601: ) (WOW64)

2016-12-18 10:39:30.25 Server      UTC adjustment: -5:00
2016-12-18 10:39:30.25 Server      (c) Microsoft Corporation.
2016-12-18 10:39:30.25 Server      All rights reserved.
2016-12-18 10:39:30.25 Server      Server process ID is 336.
2016-12-18 10:39:30.25 Server      System Manufacturer: 'Dell Inc.', System Model: 'Latitude E4300'.
2016-12-18 10:39:30.25 Server      Authentication mode is WINDOWS-ONLY.
2016-12-18 10:39:30.25 Server      Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-12-18 10:39:30.25 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2016-12-18 10:39:30.25 Server      Registry startup parameters: 
	 -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
	 -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
	 -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2016-12-18 10:39:30.25 Server      Command Line Startup Parameters:
	 -s "MSSQLSERVER"
2016-12-18 10:39:35.44 Server      SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-12-18 10:39:35.44 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-12-18 10:39:35.44 Server      Detected 8079 MB of RAM. This is an informational message; no user action is required.
2016-12-18 10:39:35.44 Server      Using conventional memory in the memory manager.
2016-12-18 10:39:35.46 Server      Buffer pool extension is not supported on the 32-bit architecture.
2016-12-18 10:39:35.95 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-12-18 10:39:36.46 Server      Query Store settings initialized with enabled = 1, 
2016-12-18 10:39:36.53 Server      The maximum number of dedicated administrator connections for this instance is '1'
2016-12-18 10:39:36.54 Server      This instance of SQL Server last reported using a process ID of 2324 at 12/16/2016 2:46:51 PM (local) 12/16/2016 7:46:51 PM (UTC). This is an informational message only; no user action is required.
2016-12-18 10:39:36.54 Server      Node configuration: node 0: CPU mask: 0x00000003:0 Active CPU mask: 0x00000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-12-18 10:39:36.54 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.
2016-12-18 10:39:36.69 Server      Software Usage Metrics is disabled.
2016-12-18 10:39:36.69 spid7s      Starting up database 'master'.
2016-12-18 10:39:38.16 Server      CLR version v4.0.30319 loaded.
2016-12-18 10:39:39.41 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework\v4.0.30319\.
2016-12-18 10:39:47.78 spid7s      Resource governor reconfiguration succeeded.
2016-12-18 10:39:47.78 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-12-18 10:39:47.86 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-12-18 10:39:48.11 spid7s      SQL Trace ID 1 was started by login "sa".
2016-12-18 10:39:48.43 spid7s      Server name is 'HARRIS-PC'. This is an informational message only. No user action is required.
2016-12-18 10:39:49.53 spid16s     A self-generated certificate was successfully loaded for encryption.
2016-12-18 10:39:49.54 spid16s     Server is listening on [ 'any' <ipv6> 1433].
2016-12-18 10:39:49.54 spid16s     Server is listening on [ 'any' <ipv4> 1433].
2016-12-18 10:39:49.54 spid16s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2016-12-18 10:39:49.54 spid16s     Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2016-12-18 10:39:49.55 Server      Server is listening on [ ::1 <ipv6> 1434].
2016-12-18 10:39:49.55 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2016-12-18 10:39:49.55 Server      Dedicated admin connection support was established for listening locally on port 1434.
2016-12-18 10:39:49.68 spid16s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-12-18 10:39:49.68 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2016-12-18 10:39:49.68 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Harris-PC ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2016-12-18 10:39:49.68 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Harris-PC:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2016-12-18 10:40:24.34 spid20s     Starting up database 'msdb'.
2016-12-18 10:40:24.34 spid21s     Starting up database 'ReportServer'.
2016-12-18 10:40:24.34 spid8s      Starting up database 'mssqlsystemresource'.
2016-12-18 10:40:24.34 spid23s     Starting up database 'ReportServerTempDB'.
2016-12-18 10:40:24.64 spid8s      The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2016-12-18 10:40:26.14 spid8s      Starting up database 'model'.
2016-12-18 10:40:26.75 spid8s      Clearing tempdb database.
2016-12-18 10:40:30.83 spid8s      Starting up database 'tempdb'.
2016-12-18 10:40:33.44 spid24s     The Service Broker endpoint is in disabled or stopped state.
2016-12-18 10:40:33.44 spid24s     The Database Mirroring endpoint is in disabled or stopped state.
2016-12-18 10:40:33.68 spid24s     Service Broker manager has started.
2016-12-18 10:40:33.70 spid7s      Recovery is complete. This is an informational message only. No user action is required.
2016-12-18 10:41:36.16 spid17s     A new instance of the full-text filter daemon host process has been successfully started.
2016-12-19 00:00:55.37 spid18s     This instance of SQL Server has been using a process ID of 336 since 12/18/2016 10:40:33 AM (local) 12/18/2016 3:40:33 PM (UTC). This is an informational message only; no user action is required.
2016-12-19 02:53:59.61 Server      SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2016-12-19 02:54:03.36 Logon       Error: 18456, Severity: 14, State: 23.
2016-12-19 02:54:03.36 Logon       Login failed for user 'NT SERVICE\ReportServer'. Reason: Access to server validation failed while revalidating the login on the connection. [CLIENT: <local machine>]
2016-12-19 02:54:04.54 spid52      Error: 17054, Severity: 16, State: 1.
2016-12-19 02:54:04.54 spid52      The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
2016-12-19 02:54:04.68 spid52      Error: 18056, Severity: 20, State: 23.
2016-12-19 02:54:04.68 spid52      The client was unable to reuse a session with SPID 52, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
2016-12-19 02:54:05.32 spid24s     Service Broker manager has shut down.
2016-12-19 02:54:06.04 spid7s      .NET Framework runtime has been stopped.
2016-12-19 02:54:16.94 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Open in new window

Vitor Montalvão

You got the SQL Server instance up and running for almost 14h and suddenly it just terminate because of a system shutdown (2016-12-19 02:53:59.61). Can you tell us why the system went down? It was a manual shutdown?
By the list of files you posted I can't see any new error log file after the shutdown. This might mean you didn't try to start the SQL Server again. Did you?

How much disk space is available on the server?

Ann K

ASKER

Its installed in my home computer.

Vitor Montalvão

Can you try to start the SQL Server now and check if a new ERRORLOG file is generated (check the file timestamp)?

Ann K

ASKER

2016-12-18 10:39:30.25 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (Intel X86) 
	Feb 20 2014 19:20:46 
	Copyright (c) Microsoft Corporation
	Enterprise Edition on Windows NT 6.1 <X64> (Build 7601: ) (WOW64)

2016-12-18 10:39:30.25 Server      UTC adjustment: -5:00
2016-12-18 10:39:30.25 Server      (c) Microsoft Corporation.
2016-12-18 10:39:30.25 Server      All rights reserved.
2016-12-18 10:39:30.25 Server      Server process ID is 336.
2016-12-18 10:39:30.25 Server      System Manufacturer: 'Dell Inc.', System Model: 'Latitude E4300'.
2016-12-18 10:39:30.25 Server      Authentication mode is WINDOWS-ONLY.
2016-12-18 10:39:30.25 Server      Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-12-18 10:39:30.25 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2016-12-18 10:39:30.25 Server      Registry startup parameters: 
	 -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
	 -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
	 -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2016-12-18 10:39:30.25 Server      Command Line Startup Parameters:
	 -s "MSSQLSERVER"
2016-12-18 10:39:35.44 Server      SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-12-18 10:39:35.44 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-12-18 10:39:35.44 Server      Detected 8079 MB of RAM. This is an informational message; no user action is required.
2016-12-18 10:39:35.44 Server      Using conventional memory in the memory manager.
2016-12-18 10:39:35.46 Server      Buffer pool extension is not supported on the 32-bit architecture.
2016-12-18 10:39:35.95 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-12-18 10:39:36.46 Server      Query Store settings initialized with enabled = 1, 
2016-12-18 10:39:36.53 Server      The maximum number of dedicated administrator connections for this instance is '1'
2016-12-18 10:39:36.54 Server      This instance of SQL Server last reported using a process ID of 2324 at 12/16/2016 2:46:51 PM (local) 12/16/2016 7:46:51 PM (UTC). This is an informational message only; no user action is required.
2016-12-18 10:39:36.54 Server      Node configuration: node 0: CPU mask: 0x00000003:0 Active CPU mask: 0x00000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-12-18 10:39:36.54 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.
2016-12-18 10:39:36.69 Server      Software Usage Metrics is disabled.
2016-12-18 10:39:36.69 spid7s      Starting up database 'master'.
2016-12-18 10:39:38.16 Server      CLR version v4.0.30319 loaded.
2016-12-18 10:39:39.41 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework\v4.0.30319\.
2016-12-18 10:39:47.78 spid7s      Resource governor reconfiguration succeeded.
2016-12-18 10:39:47.78 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-12-18 10:39:47.86 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-12-18 10:39:48.11 spid7s      SQL Trace ID 1 was started by login "sa".
2016-12-18 10:39:48.43 spid7s      Server name is 'HARRIS-PC'. This is an informational message only. No user action is required.
2016-12-18 10:39:49.53 spid16s     A self-generated certificate was successfully loaded for encryption.
2016-12-18 10:39:49.54 spid16s     Server is listening on [ 'any' <ipv6> 1433].
2016-12-18 10:39:49.54 spid16s     Server is listening on [ 'any' <ipv4> 1433].
2016-12-18 10:39:49.54 spid16s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2016-12-18 10:39:49.54 spid16s     Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2016-12-18 10:39:49.55 Server      Server is listening on [ ::1 <ipv6> 1434].
2016-12-18 10:39:49.55 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2016-12-18 10:39:49.55 Server      Dedicated admin connection support was established for listening locally on port 1434.
2016-12-18 10:39:49.68 spid16s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-12-18 10:39:49.68 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2016-12-18 10:39:49.68 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Harris-PC ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2016-12-18 10:39:49.68 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Harris-PC:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2016-12-18 10:40:24.34 spid20s     Starting up database 'msdb'.
2016-12-18 10:40:24.34 spid21s     Starting up database 'ReportServer'.
2016-12-18 10:40:24.34 spid8s      Starting up database 'mssqlsystemresource'.
2016-12-18 10:40:24.34 spid23s     Starting up database 'ReportServerTempDB'.
2016-12-18 10:40:24.64 spid8s      The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2016-12-18 10:40:26.14 spid8s      Starting up database 'model'.
2016-12-18 10:40:26.75 spid8s      Clearing tempdb database.
2016-12-18 10:40:30.83 spid8s      Starting up database 'tempdb'.
2016-12-18 10:40:33.44 spid24s     The Service Broker endpoint is in disabled or stopped state.
2016-12-18 10:40:33.44 spid24s     The Database Mirroring endpoint is in disabled or stopped state.
2016-12-18 10:40:33.68 spid24s     Service Broker manager has started.
2016-12-18 10:40:33.70 spid7s      Recovery is complete. This is an informational message only. No user action is required.
2016-12-18 10:41:36.16 spid17s     A new instance of the full-text filter daemon host process has been successfully started.
2016-12-19 00:00:55.37 spid18s     This instance of SQL Server has been using a process ID of 336 since 12/18/2016 10:40:33 AM (local) 12/18/2016 3:40:33 PM (UTC). This is an informational message only; no user action is required.
2016-12-19 02:53:59.61 Server      SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
2016-12-19 02:54:03.36 Logon       Error: 18456, Severity: 14, State: 23.
2016-12-19 02:54:03.36 Logon       Login failed for user 'NT SERVICE\ReportServer'. Reason: Access to server validation failed while revalidating the login on the connection. [CLIENT: <local machine>]
2016-12-19 02:54:04.54 spid52      Error: 17054, Severity: 16, State: 1.
2016-12-19 02:54:04.54 spid52      The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
2016-12-19 02:54:04.68 spid52      Error: 18056, Severity: 20, State: 23.
2016-12-19 02:54:04.68 spid52      The client was unable to reuse a session with SPID 52, which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
2016-12-19 02:54:05.32 spid24s     Service Broker manager has shut down.
2016-12-19 02:54:06.04 spid7s      .NET Framework runtime has been stopped.
2016-12-19 02:54:16.94 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Open in new window

Vitor Montalvão

You didn't start the SQL Server. The above screen is only a login attempt.
You need to proceed as you did in your comment 41929584