March 18, 2017 at 8:40 am
I am trying to create a linked server between two instances on the same server and I am getting errors.
Specifications:
Server: Windows 2012
SQL: 2014 SP 2 CU3
TLS 1.2 is the only protocal enabled
Encryption of data in transit enabled on both instances using the same certificate
TDE enabled
I created the Linked Server on InstanceA to connect to Instance B both on the same server in the following way:
Linked Server name: Servername\instance
Linked Server Type: SQL Server
Security: "Be Made using this security context - I put the SQL Login name and password from instanceB
Server Options: RPC and RPC Out set to true.
The problem is that when i attempt to test the connection I am not getting to the instance at all because I am not seeing any event in the SQL Error Log, nor am I getting any activity in SQL Server Profiler . The only thing I see when I attempt to connect are these two errors in the Windows Event Viewer Log (in the system log i believe)
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 43. The Windows SChannel error state is 552.
EVENT ID 36888
The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is [ServerName]. The SSL connection request has failed. The attached data contains the server certificate.
EVENT ID 36888
Any help would be appreciated
Jeff
March 23, 2017 at 6:24 pm
I ended up using a work around to deal with this problem.
I created an ODBC connection to instanceB and then created the linked server using that connection and it worked.
If anybody has any idea of how to deal with the first problem i would love the feedback, but for now I am good.
Jeff
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply