November 22, 2016 at 6:17 am
We have installed SQL Server 2016 Web Edition (64-bit) on a new virtualised database server running Windows Server 2016 Standard. We have an existing web server running Windows Server 2008 R2 and IIS Version 7.5.7600.16385.
When we attempt to connect to a named instance on the database server from the web server, the following error is raised in the IIS Log:
Error occurred in LoginButton_Click : System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.) ---> System.ComponentModel.Win32Exception (0x80004005): An existing connection was forcibly closed by the remote host
We configured the SQL instance on the database server to log both successful and unsuccessful logins. However, no unsuccessful login attempts appear in the SQL Server logs.
When we attempt to connect to the same named instance on the database server from a web server running Windows Server 2012 and IIS Version 8.5.9600.16384, the connection succeeds.
The results above are irrespective of the firewall being up or down on any of the servers.
We have tried installing the latest MDAC/ODBC and SQL Server Native Client (Version 11) on the Windows 2008 R2 web server, however this has not helped.
When we ping the database server from either web server, we receive a response using the both the IP and the FQDN.
All the servers mentioned above are within the same domain, and the accounts we are using are domain accounts. SQL Server is set to use Windows Authentication only.
Has anyone else experienced the same issues, and is there a way to resolve this?
November 22, 2016 at 6:48 am
We have installed SQL Server 2016 Web Edition (64-bit) on a new virtualised database server running Windows Server 2016 Standard. We have an existing web server running Windows Server 2008 R2 and IIS Version 7.5.7600.16385.
SQL Server 2016 has four editions: Enterprise, Standard, Developer and Express.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
November 22, 2016 at 7:01 am
Phil Parkin (11/22/2016)
We have installed SQL Server 2016 Web Edition (64-bit) on a new virtualised database server running Windows Server 2016 Standard. We have an existing web server running Windows Server 2008 R2 and IIS Version 7.5.7600.16385.
SQL Server 2016 has four editions: Enterprise, Standard, Developer and Express.
Web is also a valid version: Editions and Components of SQL Server 2016.
You've described the error you get at the web interface, but haven't given anything SQL side. Do you have any logs for your authentication attempt. Do the logs show the user authenticated successfully?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 22, 2016 at 7:15 am
Thom A (11/22/2016)
Phil Parkin (11/22/2016)
We have installed SQL Server 2016 Web Edition (64-bit) on a new virtualised database server running Windows Server 2016 Standard. We have an existing web server running Windows Server 2008 R2 and IIS Version 7.5.7600.16385.
SQL Server 2016 has four editions: Enterprise, Standard, Developer and Express.
Web is also a valid version: Editions and Components of SQL Server 2016.
You've described the error you get at the web interface, but haven't given anything SQL side. Do you have any logs for your authentication attempt. Do the logs show the user authenticated successfully?
Thank you for the correction. I looked here, but did not scroll down to the end :blush:
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
November 22, 2016 at 8:17 am
Phil Parkin (11/22/2016)
We have installed SQL Server 2016 Web Edition (64-bit) on a new virtualised database server running Windows Server 2016 Standard. We have an existing web server running Windows Server 2008 R2 and IIS Version 7.5.7600.16385.
SQL Server 2016 has four editions: Enterprise, Standard, Developer and Express.
SELECT @@VERSION;
GO
Microsoft SQL Server 2016 (RTM-GDR) (KB3194716) - 13.0.1722.0 (X64) Sep 26 2016 13:17:23 Copyright (c) Microsoft Corporation Web Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: ) (Hypervisor)
November 22, 2016 at 8:19 am
Thom A (11/22/2016)
Phil Parkin (11/22/2016)
We have installed SQL Server 2016 Web Edition (64-bit) on a new virtualised database server running Windows Server 2016 Standard. We have an existing web server running Windows Server 2008 R2 and IIS Version 7.5.7600.16385.
SQL Server 2016 has four editions: Enterprise, Standard, Developer and Express.
Web is also a valid version: Editions and Components of SQL Server 2016.
You've described the error you get at the web interface, but haven't given anything SQL side. Do you have any logs for your authentication attempt. Do the logs show the user authenticated successfully?
We configured the SQL instance on the database server to log both successful and unsuccessful logins. However, no login attempts appear in the SQL Server logs.
November 22, 2016 at 8:23 am
zoggling (11/22/2016)
Phil Parkin (11/22/2016)
We have installed SQL Server 2016 Web Edition (64-bit) on a new virtualised database server running Windows Server 2016 Standard. We have an existing web server running Windows Server 2008 R2 and IIS Version 7.5.7600.16385.
SQL Server 2016 has four editions: Enterprise, Standard, Developer and Express.
SELECT @@VERSION;GO
Microsoft SQL Server 2016 (RTM-GDR) (KB3194716) - 13.0.1722.0 (X64) Sep 26 2016 13:17:23 Copyright (c) Microsoft Corporation Web Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: ) (Hypervisor)
Oh come on! I've already issued my apology 🙂
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
November 22, 2016 at 8:40 am
zoggling (11/22/2016)
...When we attempt to connect to a named instance on the database server from the web server, the following error is raised in the IIS Log:
Error occurred in LoginButton_Click : System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.) ---> System.ComponentModel.Win32Exception (0x80004005): An existing connection was forcibly closed by the remote host
We configured the SQL instance on the database server to log both successful and unsuccessful logins. However, no unsuccessful login attempts appear in the SQL Server logs.
When we attempt to connect to the same named instance on the database server from a web server running Windows Server 2012 and IIS Version 8.5.9600.16384, the connection succeeds.
Considering the error you posted is an SSL Provider error, not a SQL Server error, it looks like the connection reaches the computer running SQL Server but doesn't actually get to SQL Server itself, something else in the networking setup is stopping it. Any more information you can share about the networking between the computers?
November 22, 2016 at 8:43 am
Wondering if it's an SSL error, or that named pipes or that TCP/IP is disabled.
Do you have any issues connecting to the SQL Server instance from any other computer on the network (not the Server itself)?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 22, 2016 at 8:51 am
Phil Parkin (11/22/2016)
zoggling (11/22/2016)
Phil Parkin (11/22/2016)
We have installed SQL Server 2016 Web Edition (64-bit) on a new virtualised database server running Windows Server 2016 Standard. We have an existing web server running Windows Server 2008 R2 and IIS Version 7.5.7600.16385.
SQL Server 2016 has four editions: Enterprise, Standard, Developer and Express.
SELECT @@VERSION;GO
Microsoft SQL Server 2016 (RTM-GDR) (KB3194716) - 13.0.1722.0 (X64) Sep 26 2016 13:17:23 Copyright (c) Microsoft Corporation Web Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: ) (Hypervisor)
Oh come on! I've already issued my apology 🙂
Accepted! Sorry, I was just working my way down through the responses! 😀
November 22, 2016 at 8:59 am
Chris Harshman (11/22/2016)
zoggling (11/22/2016)
...When we attempt to connect to a named instance on the database server from the web server, the following error is raised in the IIS Log:
Error occurred in LoginButton_Click : System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.) ---> System.ComponentModel.Win32Exception (0x80004005): An existing connection was forcibly closed by the remote host
We configured the SQL instance on the database server to log both successful and unsuccessful logins. However, no unsuccessful login attempts appear in the SQL Server logs.
When we attempt to connect to the same named instance on the database server from a web server running Windows Server 2012 and IIS Version 8.5.9600.16384, the connection succeeds.
Considering the error you posted is an SSL Provider error, not a SQL Server error, it looks like the connection reaches the computer running SQL Server but doesn't actually get to SQL Server itself, something else in the networking setup is stopping it. Any more information you can share about the networking between the computers?
We can connect to the named instance from a web application server running Windows Server 2012, but not from a web application server running Windows Server 2008 R2. Could this be anything to do with the SQL Server Native Client (SNAC) not being supported beyond SQL Server 2012? We can also connect to both the named and default instances using SQL Server Management Studio from other client machines on the network without issue.
I will come back to you tomorrow on the network setup once I have heard back from infrastructure.
Here is some information on the ODBC Data Source drivers installed on each of the web servers:
Windows Server 2008 R2 (web applications CANNOT connect to SQL Server 2016 named instance)
- ODBC Driver 13 for SQL Server (Version 2015.131.811.168) - MSODBCSQL13.DLL
- SQL Server (Version 6.01.7601.17514) - SQLSRV32.DLL
- SQL Server Native Client 10.0 (Version 2007.100.1600.22) - SQLNCLI10.DLL
- SQL Server Native Client 11.0 (Version 2011.110.6538.00) - SQLNCLI11.DLL
Windows Server 2012 R2 (web applications CAN connect to SQL Server 2016 named instance)
-SQL Server (Version 6.03.9600.17415) - SQLSRV32.DLL
November 25, 2016 at 3:54 am
Sadly something was changed infrastructure-side which resulted in this error disappearing without explanation. I cannot provide a solution to this now unfortunately, suffice to say that we have now got the remainder of things working via a few instance security permissions and firewall rules.
Thank you for your help.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply