Skip to content

AWS RDS Linked Server not working

0

We have 2 MS SQL server instances:

Instance 1: MS SQL Server Standard Edition - db.r5.large Instance 2: MS SQL Server Web Edition- db.r5.large Both these instances are in the same VPC and they both configured for port 1433

This is the script we used to create the linked server on instance 2:

EXEC master .dbo.sp_addlinkedserver @server = N'IR_Gaming', @srvproduct= N'', @provider= N'SQLNCLI', @datasrc= N'[our domain name for instance 1]' go EXEC master .dbo.sp_addlinkedsrvlogin @rmtsrvname=N'IR_Gaming' ,@useself=N'False' ,@locallogin=NULL,@rmtuser =N'admin',@rmtpassword='*******' go

When we "Test Connection" or try to query the linked server. We get the following errror:

OLE DB provider "MSOLEDBSQL" for linked server "IR_Gaming" returned message "Login timeout expired". OLE DB provider "MSOLEDBSQL" for linked server "IR_Gaming" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". Msg 53, Level 16, State 1, Line 0 Named Pipes Provider: Could not open a connection to SQL Server [53].

1 Answer
0
Accepted Answer

Just has to add rule in security group

answered 3 years ago
  • Hello, I have the same problem. I tried several rules but none worked. What would be the specific rule for releasing linked server?

  • Hello, I am facing the same problem. Trying to create Linked between SQL to SSAS hosted on same RDS and getting above similar errors. Could you please mention steps to identify the missing security group or name of the security group that you included?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.