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

by

Troubleshooting Guide: SQL Server Error 7223 – ‘remote proc trans’ Not Supported

Why This Error Happens

This warning occurs because the remote proc trans configuration option, historically used to enable distributed transactions for remote stored procedure calls (via sp_configure), has been deprecated and is no longer functionally supported in modern SQL Server builds, including SQL Server 2025. The engine recognizes the configuration flag being set to 1 during instance startup or configuration change, but since the underlying MS DTC (Microsoft Distributed Transaction Coordinator) handling for this specific legacy mechanism has been removed, the server silently reverts the setting to 0 (disabled) rather than crashing. This typically happens when legacy scripts, old T-SQL migration files, or third-party applications attempt to configure an instance using syntax designed for SQL Server 2000/2005 environments.

Step-by-Step Resolution Guide

Step 1: Identify the Source of the Configuration Call

  • Check SQL Server Agent Job steps, specifically “Transact-SQL script” steps, for the command EXEC sp_configure 'remote proc trans', 1;.
  • Review any startup stored procedures or sqlcmd deployment scripts that may be executing this legacy command on service restart.
  • Search application connection strings or ORM migration scripts (e.g., Entity Framework, Liquibase) for references to this specific legacy flag.

Step 2: Remove the Deprecated Configuration Command

  • Open SQL Server Management Studio (SSMS) and connect to the instance via a New Query window.
  • Execute the following to clean up the configuration state and suppress the “show advanced options” dependency: 
  EXEC sp_configure 'show advanced options', 1;
  RECONFIGURE;
  EXEC sp_configure 'remote proc trans', 0;
  RECONFIGURE;
  • Physically delete or comment out the specific line calling this command from the source script file so it does not re-trigger the warning on the next deployment cycle.

Step 3: Replace Logic with Modern MS DTC Configuration

  • Since this flag is non-functional, ensure your distributed transaction logic relies on the native, modern distributed transaction coordinator instead.
  • Open the Component Services manager on Windows Server 2025 (dcomcnfg.exe).
  • Navigate to Component Services > Computers > My Computer > Distributed Transaction Coordinator > Local DTC.
  • Right-click Local DTC, select Properties, and ensure “Network DTC Access” is enabled if cross-server transactions are actually required for your workload.

Step 4: Restart the SQL Server Service to Clear Cache

  • Open SQL Server Configuration Manager (search SQLServerManager17.msc or the relevant version for 2025).
  • Select SQL Server Services, right-click your specific instance (e.g., MSSQLSERVER), and select Restart.
  • This ensures the configuration cache is fully refreshed and the deprecated flag does not reappear in the SQL Server Error Log on the next boot cycle.

Alternative or Verification Steps

  • Verification: Run EXEC sp_configure 'remote proc trans'; in a new query window. The run_value and config_value columns should both display 0, and the SQL Server Error Log (viewable via SSMS Object Explorer > Management > SQL Server Logs) should no longer show Error 7223 on the next restart.
  • Alternative: If the warning persists due to a third-party vendor application hardcoding this legacy call, contact the vendor for a patch, as modifying vendor-locked scripts directly may be unsupported; in the interim, this specific warning can be safely ignored as it does not impact standard local transaction performance.