How to fix Error 7411 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 7411 – “Server is not configured for…”

Why This Error Happens

Error 7411 occurs when a linked server or remote server is being used for a feature—such as RPC (Remote Procedure Call), publishing, subscribing, or distribution—that has not been explicitly enabled at the server configuration level. This is commonly caused by default security settings in SQL Server 2025 that disable remote access options (remote proc transactions, RPC, RPC OUT) to reduce the attack surface. Additionally, this can occur if the server was recently migrated or restored, causing linked server metadata to retain old configuration flags that no longer match the current server’s settings.

Step-by-Step Resolution Guide

Step 1: Verify the Specific Configuration Context

  • Identify exactly which feature is being blocked (e.g., RPC, Replication, or Distributed Transactions) by reading the full text of the error message following “is not configured for.”
  • Open SQL Server Management Studio (SSMS) and connect to the instance reporting the error.
  • Run EXEC sp_helpserver; to view the current configuration flags (rpc, rpc out, dist) for the specific linked server causing the issue.

Step 2: Enable RPC and RPC OUT Settings

  • If the error relates to Remote Procedure Calls, you must update the server options using T-SQL rather than relying on defaults.
  • Execute the following command in a new query window, replacing 'LinkedServerName' with your actual server name:
EXEC sp_serveroption 'LinkedServerName', 'rpc', 'true';
EXEC sp_serveroption 'LinkedServerName', 'rpc out', 'true';
  • Restart the SQL Server Agent service via services.msc on Windows Server 2025 to ensure the Agent recognizes the updated linked server properties.

Step 3: Configure Replication or Distribution Settings

  • If the error pertains to Replication (a common cause in migration scenarios), verify if the server is correctly configured as a Publisher or Distributor.
  • In SSMS, navigate to Replication > right-click Local Publications > select Properties.
  • If the server is missing distributor configuration, run the Configure Distribution Wizard again, ensuring the Snapshot folder path (e.g., C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\ReplData) is accessible and shared correctly on the Windows Server 2025 network.

Step 4: Check Windows Firewall and DCOM Permissions

  • Since Windows 11 and Windows Server 2025 have stricter firewall defaults, ensure that the specific TCP port (usually 1433) or the Named Pipes protocol used for the RPC communication is allowed.
  • Open Windows Defender Firewall with Advanced Security and create an Inbound Rule allowing traffic for sqlservr.exe.
  • Verify that the SQL Server Service Account has the necessary “Access this computer from the network” rights in the Local Security Policy (secpol.msc).

Alternative or Verification Steps

  • To Verify the Fix: Re-run the specific query or job that originally triggered Error 7411. If using RPC, test with a simple remote stored procedure call to confirm the “rpc” and “rpc out” flags are active.
  • Alternative Solution: If sp_serveroption does not resolve the issue, drop and recreate the Linked Server entirely using sp_dropserver followed by sp_addlinkedserver, ensuring the “collation compatible” and “data access” options are explicitly set to true during creation.