(NOTE: I will not recommend this solution because of some known issues. The Microsoft support article will guide you through the process of patches and updates you need to install.
INSTALL SQL SERVER 2014 SSIS AND SSRS INSTALL
This article will help you to find the cumulative update and other components needed for every version of SQL Server and install them to support TLS 1.2. If you are planning to find a solution without upgrading SQL Server to 2016 or having a separate sever for MS SQL, then you may need to follow the Microsoft article. The above solution may not always possible for everyone. Enable TLS 1.2 support for SQL Server 2012 or 2014 (I chose this option for my server as it has less impact and viable in my case) 3.
INSTALL SQL SERVER 2014 SSIS AND SSRS UPGRADE
Upgrade the SQL Server to a TLS 1.2 supported versionĪnother solution is to upgrade to SQL Server 2016 or higher which by default supports TLS 1.2. In such a scenario, you can try the below solutions. Budget constraints may force you to have a single server with both SQL Server and IIS. However, it is not be always possible to have a separate server for MS SQL. Segregating SQL Server from IIS Server is a best practice for security and performance of the website. The best solution is to segregate the SQL Server from IIS server. I have listed the solutions below so as it will be helpful for someone. Then on looking for a permanent solution, I have identified tree solutions. Information about possible related problems.Īs a temporary solution, I quickly enabled SSL 3.0 and TLS 1.0 protocols and restarted the server to bring back the website up and running. SQL Server could not spawn FRunCommunicationsManager thread.Ĭheck the SQL Server error log and the Windows event logs for To determine the cause, review the errors immediately preceding this one in the error log. The group or resource is not in the correct state to perform the requested operation.Ĭould not start the network library because of an internal error in the network library. Reason: Unable to initialize SSL support. TDSSNIClient initialization failed with error 0x139f, status code 0x80. Verify that security.dll exists on the system. The server was unable to initialize encryption because of a problem with a security library. Finally, on checking the event logs, I found a series or error messages. I manually tried starting the server with no success. So, I checked the SQL Server Service and found that it is not yet started. On trying to login to the SQL server using SQL Server Management Studio (SSMS), I got an error message saying that the server is not available. The web site log has entries related to unable to connect the SQL Server.
After restarting the server the website was not working.
0 kommentar(er)
