Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Friday, October 9, 2015 9:53 AM
Hi,
unfortunately one of the my sql server services stopped. and try to start sql server services getting below error message and services are not starting yet.
please help me on this.
Error:
The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
Thanks in advance!!!
mastanvali shaik
Thursday, October 15, 2015 9:49 AM ✅Answered
Hi mastanvali,
Please follow the steps in this article to add your local administer account to SQL Server and grant it sysadmin permission. Then use the account to log in SQL Server, reset sa password, check if NT Service\SQLSERVERAGENT is the member of sysadmin role and check the existence & permission of login ('username' or 'userid').
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support
Friday, October 9, 2015 10:07 AM
Have you checked out this post, which is a recap from working directly with a MSFT engineer to resolve this issue?
http://www.dbforums.com/showthread.php?1695894-2008-R2-SQL-startup-error-resolution
Thanks,
Sam Lester (MSFT)
http://blogs.msdn.com/b/samlester
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.
Friday, October 9, 2015 10:47 AM
yes, tried but no luck.
mastanvali shaik
Monday, October 12, 2015 3:24 AM
Hi mastanvali,
What version of your SQL Server?
Based on my research, the above error could occur when TLS 1.0 and SSL 3.0 are disabled on the Server and there is corruption with security.dll file.
To troubleshoot this issue, please perform the following steps.
1. Please enable TLS 1.0 and SSL 3.0 if you use SQL Server 2008 R2 or prior version. If you use SQL Server 2012 or later and want to use TLS 1.1 & TLS 1.2 instead of TLS 1.0 & SSL 3.0, please install the cumulative update of SQL Server as described in this article: https://support.microsoft.com/en-us/kb/3052404.
2. Copy the security.dll from a working machine and check if the issue still persists.
3. Check if there is a OS corruption issue.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support
Thursday, October 15, 2015 5:22 AM
Hi Lydia,
Thanks for help.after applying patches sql services started sucesfully but sql agent not started and also unable to login sql server.
getting login failure message for both SQL and WINDOWS logins.
mastanvali shaik
Thursday, October 15, 2015 6:57 AM
Hi mastanvali,
Could you please help to post the full error messages that you encounter?
You can check error messages from event viewer and SQL Server Error Log which locates in C:\Program Files\Microsoft SQL Server\MSSQL<version number>.MSSQLSERVER\MSSQL\Log
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support
Thursday, October 15, 2015 7:32 AM
Hi Lydia,
i got this from error message from event viewer.
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
from sql logs:
2015-10-13 10:26:21.76 Server Microsoft SQL Server 2014 - 12.0.2546.0 (X64)
Jun 6 2015 00:57:37
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
2015-10-13 10:26:21.77 Server UTC adjustment: 5:30
2015-10-13 10:26:21.77 Server (c) Microsoft Corporation.
2015-10-13 10:26:21.77 Server All rights reserved.
2015-10-13 10:26:21.79 Server Server process ID is 1780.
2015-10-13 10:26:21.79 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2015-10-13 10:26:21.82 Server Authentication mode is MIXED.
2015-10-13 10:26:21.82 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2015-10-13 10:26:21.82 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2015-10-13 10:26:21.84 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2015-10-13 10:26:21.84 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2015-10-13 10:26:33.33 Server SQL Server detected 4 sockets with 1 cores per socket and 1 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2015-10-13 10:26:33.33 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-10-13 10:26:33.33 Server Detected 8191 MB of RAM. This is an informational message; no user action is required.
2015-10-13 10:26:33.37 Server Using conventional memory in the memory manager.
2015-10-13 10:26:35.42 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2015-10-13 10:26:38.21 Server Query Store settings initialized with enabled = 1,
2015-10-13 10:26:39.00 Server The maximum number of dedicated administrator connections for this instance is '1'
2015-10-13 10:26:39.02 Server This instance of SQL Server last reported using a process ID of 4176 at 10/13/2015 10:24:39 AM (local) 10/13/2015 4:54:39 AM (UTC). This is an informational message only; no user action is required.
2015-10-13 10:26:39.03 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-10-13 10:26:39.92 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.
2015-10-13 10:26:40.06 Server Software Usage Metrics is disabled.
2015-10-13 10:26:41.37 Server CLR version v4.0.30319 loaded.
2015-10-13 10:26:41.48 spid11s Starting up database 'master'.
2015-10-13 10:26:43.61 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
2015-10-13 10:26:54.71 spid11s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-10-13 10:26:54.75 spid11s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-10-13 10:26:56.66 spid11s SQL Trace ID 1 was started by login "sa".
2015-10-13 10:26:56.81 spid11s Server name is 'server name'. This is an informational message only. No user action is required.
2015-10-13 10:26:58.31 spid16s A self-generated certificate was successfully loaded for encryption.
2015-10-13 10:26:58.34 spid16s Server is listening on [ 'any' <ipv6> 1433].
2015-10-13 10:26:58.48 spid16s Server is listening on [ 'any' <ipv4> 1433].
2015-10-13 10:26:58.49 spid16s Server local connection provider is ready to accept connection on [ \.\pipe\SQLLocal\MSSQLSERVER ].
2015-10-13 10:26:58.50 spid16s Server named pipe provider is ready to accept connection on [ \.\pipe\sql\query ].
2015-10-13 10:26:58.93 Server Server is listening on [ ::1 <ipv6> 1434].
2015-10-13 10:26:59.19 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2015-10-13 10:26:59.58 Server Dedicated admin connection support was established for listening locally on port 1434.
2015-10-13 10:26:59.63 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.
2015-10-13 10:26:59.63 spid16s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-10-13 10:27:00.46 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ abc.domainname.name.com] for the SQL Server service.
2015-10-13 10:27:00.46 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ abc.domainname.name.com:1433 ] for the SQL Server service.
2015-10-13 10:27:06.98 spid17s A new instance of the full-text filter daemon host process has been successfully started.
2015-10-13 10:27:07.26 spid11s Starting up database 'msdb'.
2015-10-13 10:27:07.27 spid12s Starting up database 'mssqlsystemresource'.
2015-10-13 10:27:07.56 spid12s The resource database build version is 12.00.2546. This is an informational message only. No user action is required.
2015-10-13 10:27:07.87 spid12s Starting up database 'model'.
2015-10-13 10:27:08.05 spid12s Clearing tempdb database.
2015-10-13 10:27:08.54 spid12s Starting up database 'tempdb'.
2015-10-13 10:27:08.79 spid19s The Service Broker endpoint is in disabled or stopped state.
2015-10-13 10:27:08.80 spid19s The Database Mirroring endpoint is in disabled or stopped state.
2015-10-13 10:27:08.92 spid19s Service Broker manager has started.
2015-10-13 10:27:08.94 spid11s Recovery is complete. This is an informational message only. No user action is required.
2015-10-13 10:29:50.53 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:29:50.53 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:30:09.60 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:30:09.60 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:30:27.98 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:30:27.98 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:38:17.78 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:38:17.78 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:38:17.81 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:38:17.81 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:39:24.87 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:39:24.87 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:39:24.93 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:39:24.93 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:44:23.78 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:44:23.78 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:44:36.42 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:44:36.42 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:47:17.30 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:47:17.30 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:47:40.08 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:47:40.08 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:48:20.98 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:48:20.98 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:52:49.87 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:52:49.87 Logon Login failed for user 'username'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:55:05.52 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:55:05.52 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:55:05.57 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:55:05.57 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:55:44.83 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:55:44.83 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:55:44.89 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:55:44.89 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 10:57:15.71 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 10:57:15.71 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 10:57:54.87 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 10:57:54.87 Logon Login failed for user 'username'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 11:25:01.57 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 11:25:01.57 Logon Login failed for user 'username'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 11:25:33.30 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 11:25:33.30 Logon Login failed for user 'username'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 11:29:13.28 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 11:29:13.28 Logon Login failed for user 'username'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 11:29:39.61 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 11:29:39.61 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 11:29:50.71 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 11:29:50.71 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 11:50:31.51 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 11:50:31.51 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 11:52:51.99 Logon Error: 18456, Severity: 14, State: 8.
2015-10-13 11:52:51.99 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-13 12:49:59.55 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 12:49:59.55 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-13 12:49:59.62 Logon Error: 18456, Severity: 14, State: 5.
2015-10-13 12:49:59.62 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-14 00:00:16.98 spid35s This instance of SQL Server has been using a process ID of 1780 since 10/13/2015 10:27:08 AM (local) 10/13/2015 4:57:08 AM (UTC). This is an informational message only; no user action is required.
2015-10-14 01:00:14.59 Logon Error: 18456, Severity: 14, State: 5.
2015-10-14 01:00:14.59 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-15 00:00:55.65 spid24s This instance of SQL Server has been using a process ID of 1780 since 10/13/2015 10:27:08 AM (local) 10/13/2015 4:57:08 AM (UTC). This is an informational message only; no user action is required.
2015-10-15 01:00:22.18 Logon Error: 18456, Severity: 14, State: 5.
2015-10-15 01:00:22.18 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-15 10:45:59.53 Logon Error: 18456, Severity: 14, State: 5.
2015-10-15 10:45:59.53 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-15 10:45:59.57 Logon Error: 18456, Severity: 14, State: 5.
2015-10-15 10:45:59.57 Logon Login failed for user 'userid'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-15 10:47:04.25 Logon Error: 18456, Severity: 14, State: 5.
2015-10-15 10:47:04.25 Logon Login failed for user 'username'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2015-10-15 10:47:14.46 Logon Error: 18456, Severity: 14, State: 8.
2015-10-15 10:47:14.46 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2015-10-15 11:41:00.25 Logon Error: 18456, Severity: 14, State: 38.
2015-10-15 11:41:00.25 Logon Login failed for user 'sa'. Reason: Failed to open the explicitly specified database ''. [CLIENT: ]
mastanvali shaik
Thursday, October 15, 2015 8:26 AM
Hi mastanvali,
Firstly, what account you use to run SQL Server Agent Service? If SQL Server Agent Service runs under a domain or computer account, make sure that the password of the account is correct, also the account should have System Administrators (sysadmin) privileges in SQL Server. In addition, enter the actual instance name as value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\ MSSQL12.MSSQLSERVER \SQLServerAgent\ServerHost.
However, if SQL Serve Agent Service still fails to start, please help to post the full error message of SQL Agent Log (C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\SQLAgent.OUT).
Secondly, regarding to the login failure issue, it is caused by that the password of ‘sa’ is incorrect and the login('username' or 'userid') does not exist in SQL Server. Please enter the correct password of ‘sa’ to log in SQL Server and check if you have created 'username' and 'userid' logins. For more details about troubleshooting 18456 error, please review this blog.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support
Thursday, October 15, 2015 9:39 AM
Hi Lydia,
2015-10-15 13:19:40 - ? [100] Microsoft SQLServerAgent version 12.0.2546.0 (X64 unicode retail build) : Process ID 3396
2015-10-15 13:19:40 - ? [495] The SQL Server Agent startup service account is NT Service\SQLSERVERAGENT.
2015-10-15 13:19:41 - ! [150] SQL Server does not accept the connection (error: 18456). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2015-10-15 13:19:41 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2015-10-15 13:19:41 - ! [298] SQLServer Error: 18456, Login failed for user 'userid'. [SQLSTATE 28000]
2015-10-15 13:19:41 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2015-10-15 13:19:41 - ? [098] SQLServerAgent terminated (normally)
SA and users have full admin access ,i am entering correct pwd for SA login .
mastanvali shaik