SQL Server Error 7411

Error number

7411

Severity

16 (user-correctable error)

State

1

Product

Microsoft SQL Server Database Engine

Versions

All supported SQL Server versions (2016 to 2025), Azure SQL Managed Instance

Category

Linked Servers

Last reviewed

24 October 2026

What it means

Error 7411 means a linked server option blocks what you asked for: "RPC" means rpc out is off, so you cannot run EXEC ... AT or call a remote procedure, and "DATA ACCESS" means the linked server is not enabled for distributed queries.

Every linked server in sys.servers carries switches that SQL Server checks before it even loads the provider. The last word of the message tells you which one failed. RPC is the rpc out option (column is_rpc_out_enabled), needed for EXEC (...) AT server and for calling a procedure by a four-part name. DATA ACCESS is the data access option (is_data_access_enabled), needed for OPENQUERY and four-part SELECT, INSERT, UPDATE and DELETE.

The RPC form surprises people most: a linked server created with sp_addlinkedserver has rpc out switched off (we saw is_rpc_out_enabled = 0 on SQL Server 2025), so the first EXEC ... AT against a new linked server fails even though queries through it work. Because the check is local, the remote server, its logins and the network play no part: the fix is on this server only.

Common causes

• The linked server was created with defaults and rpc out was never enabled, then a script used EXEC (...) AT or a remote procedure call.
• Someone set data access to false, for example to stop ad hoc queries through a linked server that should only run procedures.
• The linked server was scripted from another server without its sp_serveroption calls, so the options differ between environments.
• The name in the query points at the local server entry or an old remote server entry (not a linked server), which has data access off.

Diagnose it

Read-only These queries only read metadata and dynamic management views. They do not change data, permissions or configuration, so they are safe to run first.

SELECT name, product, provider, data_source,
       is_data_access_enabled, is_rpc_out_enabled, is_remote_login_enabled
FROM sys.servers
WHERE server_id > 0
ORDER BY name;

SELECT server_id, name, is_linked, is_data_access_enabled
FROM sys.servers
WHERE server_id = 0;

How to fix it

Each fix is labelled with what it changes. Try read-only checks and the least invasive fix first, and test changes outside production.

EXEC master.dbo.sp_serveroption
     @server = N'SALESSRV01', @optname = N'rpc out', @optvalue = N'true';

EXEC master.dbo.sp_serveroption
     @server = N'SALESSRV01', @optname = N'data access', @optvalue = N'true';

Examples

EXEC ... AT against a new linked server (rpc out is off by default)

-- A throwaway linked server that points back at this instance
EXEC master.dbo.sp_addlinkedserver @server = N'cws_errlab_ls', @srvproduct = N'',
     @provider = N'MSOLEDBSQL', @datasrc = N'localhost';
GO
EXEC (N'SELECT 1 AS x') AT cws_errlab_ls;
GO
EXEC master.dbo.sp_dropserver @server = N'cws_errlab_ls', @droplogins = 'droplogins';

Msg 7411, Level 16, State 1, Line 1
Server 'cws_errlab_ls' is not configured for RPC.

OPENQUERY when data access is switched off

EXEC master.dbo.sp_addlinkedserver @server = N'cws_errlab_ls', @srvproduct = N'',
     @provider = N'MSOLEDBSQL', @datasrc = N'localhost';
EXEC master.dbo.sp_serveroption @server = N'cws_errlab_ls',
     @optname = N'data access', @optvalue = N'false';
GO
SELECT * FROM OPENQUERY(cws_errlab_ls, 'SELECT 1 AS x');
GO
EXEC master.dbo.sp_dropserver @server = N'cws_errlab_ls', @droplogins = 'droplogins';

Msg 7411, Level 16, State 1, Line 1
Server 'cws_errlab_ls' is not configured for DATA ACCESS.

How to prevent it

Create linked servers from a script that sets every option explicitly (data access, rpc out, timeouts) together with the login mapping, and keep it in source control so each environment gets the same definition. Enable rpc out only on linked servers that really need remote execution.

After creating or changing a linked server, test both paths you rely on (OPENQUERY and EXEC ... AT) before handing it to applications.

Common questions

Learn more on CodeWithSQL

• Stored procedures and functions

Official documentation

• sp_serveroption (Transact-SQL)
• EXECUTE (Transact-SQL): AT linked_server_name
• sys.servers (Transact-SQL)
• Database Engine events and errors 7000 to 7999

Last technically reviewed 24 October 2026; examples and diagnostics run on SQL Server 2025 (17.0.1145.4). Message text checked against the engine's sys.messages catalogue.