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

by

Troubleshooting Guide: Error 7201 – SQL Server Not Configured for Remote Access

Why This Error Happens

This error occurs when the remote access server configuration option is disabled on the target SQL Server instance, preventing it from executing procedures invoked by a remote server via linked server calls or RPC. It can also surface if the Remote Procedure Call (RPC) and RPC Out options are not enabled on the linked server definition itself. Additionally, network-level restrictions or a disabled TCP/IP protocol binding in SQL Server Configuration Manager can trigger this same symptom even when the server-level setting is correctly configured.

Step-by-Step Resolution Guide

Step 1: Enable Remote Access on the Target SQL Server Instance

  • Open SQL Server Management Studio (SSMS) and connect to the target instance.
  • Run the following T-SQL command to check the current setting:
  EXEC sp_configure 'remote access';
  • If the run_value is 0, enable it with:
  EXEC sp_configure 'remote access', 1;
  RECONFIGURE WITH OVERRIDE;
  • Restart the SQL Server service for the change to take effect (via SQL Server Configuration Manager or services.msc).

Step 2: Verify RPC and RPC Out Settings on the Linked Server

  • On the calling server, right-click the linked server in SSMS under Server Objects > Linked Servers and select Properties.
  • Navigate to the Server Options page and ensure both RPC and RPC Out are set to True.
  • Alternatively, run this script to enable both options via T-SQL:
  EXEC sp_serveroption 'LinkedServerName', 'rpc', 'true';
  EXEC sp_serveroption 'LinkedServerName', 'rpc out', 'true';

Step 3: Confirm TCP/IP Protocol and Network Connectivity

  • Open SQL Server Configuration Manager on Windows Server 2025/Windows 11.
  • Under SQL Server Network Configuration > Protocols for [InstanceName], ensure TCP/IP is set to Enabled.
  • Check that the correct port (default 1433) is allowed through Windows Defender Firewall with Advanced Security on both inbound and outbound rules.
  • Restart the SQL Server (MSSQLSERVER) service after any protocol changes.

Step 4: Validate SQL Server Browser Service (Named Instances Only)

  • If using a named instance, confirm the SQL Server Browser service is running via services.msc.
  • This service is required for the client to resolve the correct port for named instances during remote procedure calls.

Alternative or Verification Steps

  • Test the fix by executing a sample remote procedure call (e.g., EXEC [LinkedServerName].DatabaseName.dbo.ProcedureName;) and confirm it completes without Error 7201.
  • If the issue persists, use sp_helpserver to confirm the linked server is registered correctly, and check the SQL Server Error Log for any underlying network-level authentication failures.