Hi Folks
remote Named Pipes in a side-by-side 2014 Express & 2016 RC3 installation (on Windows 2012 Server) is not functional (programmatically).
Details:
13.0.1400.361 RC3 Developer Edition (64-bit) - 2016
12.0.4449.0 SP1 Express Edition (64-bit) - 2014
(I've done several dozen of installs over the last 20 years, so I'd like to think I have a handle on this, but can't figure this one out.)
Named Pipes was functional (remotely for 2014), but after the install of 2016, this protocol is not functional remotely (no error message, just times out now for both 2014 and 2016). Named Pipes works locally (on the Windows 2012 Server for both 2014 and 2016).
My firewall settings:
Write-host ========= SQL Server Ports ===================
Write-host Enabling SQLServer default instance port 1433
New-NetFirewallRule -DisplayName "Allow SQLServer inbound TCP Port 1433" –Direction inbound –LocalPort 1433 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQLServer outbound TCP Port 1433" –Direction outbound –LocalPort 1433 -Protocol TCP -Action Allow
Write-host Enabling Dedicated Admin Connection port 1434
New-NetFirewallRule -DisplayName "Allow SQL Admin inbound TCP Port 1434" -Direction inbound –LocalPort 1434 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQL Admin outbound TCP Port 1434" -Direction outbound –LocalPort 1434 -Protocol TCP -Action Allow
Write-host Enabling conventional SQL Server Service Broker port 4022
New-NetFirewallRule -DisplayName "Allow SQL Server Service Broker inbound TCP Port 4022" -Direction inbound –LocalPort 4022 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQL Server Service Broker outbound TCP Port 4022" -Direction outbound –LocalPort 4022 -Protocol TCP -Action Allow
Write-host Enabling Transact-SQL Debugger/RPC port 135
New-NetFirewallRule -DisplayName "Allow Transact-SQL Debugger/RPC inbound TCP Port 135" -Direction inbound –LocalPort 135 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow Transact-SQL Debugger/RPC outbound TCP Port 135" -Direction outbound –LocalPort 135 -Protocol TCP -Action Allow
Write-host Enabling Named Pipes port 445
#SQLServer 2016
New-NetFirewallRule -DisplayName "Allow SQLServer 2016 inbound Named Pipes Port 445" –Direction inbound -Program "c:\Program Files\Microsoft SQL Server\MSSQL13.INTTIMEKEEPING\MSSQL\Binn\sqlservr.exe" –LocalPort 445 -Protocol TCP -Action
Allow
New-NetFirewallRule -DisplayName "Allow SQLServer 2016 outbound Named Pipes Port 445" –Direction outbound -Program "c:\Program Files\Microsoft SQL Server\MSSQL13.INTTIMEKEEPING\MSSQL\Binn\sqlservr.exe" –LocalPort 445 -Protocol TCP -Action
Allow
#SQLServer 2014
New-NetFirewallRule -DisplayName "Allow SQLServer 2014 inbound Named Pipes Port 445" –Direction inbound -Program "c:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" –LocalPort 445 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQLServer 2014 outbound Named Pipes Port 445" –Direction outbound -Program "c:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" –LocalPort 445 -Protocol TCP -Action Allow
Write-host ========= Analysis Services Ports ==============
Write-host Enabling SSAS Default Instance port 2383
New-NetFirewallRule -DisplayName "Allow SSAS Default Instance inbound TCP Port 2383" -Direction inbound –LocalPort 2383 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SSAS Default Instance outbound TCP Port 2383" -Direction outbound –LocalPort 2383 -Protocol TCP -Action Allow
Write-host Enabling SQL Server Browser Service port 2382
New-NetFirewallRule -DisplayName "Allow SQL Server Browser Service inbound TCP Port 2382" -Direction inbound –LocalPort 2382 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQL Server Browser Service outbound TCP Port 2382" -Direction outbound –LocalPort 2382 -Protocol TCP -Action Allow
Write-host ========= Misc Applications ==============
Write-host Enabling HTTP port 80
New-NetFirewallRule -DisplayName "Allow HTTP inbound TCP Port 80" -Direction inbound –LocalPort 80 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow HTTP outbound TCP Port 80" -Direction outbound –LocalPort 80 -Protocol TCP -Action Allow
Write-host Enabling SSL port 443
New-NetFirewallRule -DisplayName "Allow SSL inbound TCP Port 443" -Direction inbound –LocalPort 443 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SSL outbound TCP Port 443" -Direction outbound –LocalPort 443 -Protocol TCP -Action Allow
Write-host Enabling port for SQL Server Browser Service's 'Browse
New-NetFirewallRule -DisplayName "Allow SQL Browser inbound UDP Port 1434" -Direction inbound –LocalPort 1434 -Protocol UDP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQL Browser outbound UDP Port 1434" -Direction outbound –LocalPort 1434 -Protocol UDP -Action Allow
#==end of script==
I've tried all of the developer and admin logins directly from SSMS w/o issue.
I've tried every support url that seemed relevant (like http://stackoverflow.com/questions/9945409/how-do-i-fix-the-error-named-pipes-provider-error-40-could-not-open-a-connec)
Are there any "triage utilities" like Oracle's TNS Ping (for SQL Server 2014 and 2016)?
I'm not seeing anything in the Windows Event Log on the Windows Server 2012.
Thanks
Rob
Rob K