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

by

Troubleshooting Guide: SQL Server Error 12701 – Failed to Lock External Data Source Object

Why This Error Happens

Error 12701 typically occurs when SQL Server 2025 cannot acquire the required lock on an External Data Source (EDS) object because another session or background process is already holding a conflicting lock (such as a schema or exclusive lock) during a PolyBase or Data Virtualization operation. This is often triggered by concurrent DDL operations, a stalled external table refresh, or a long-running query that has not released its lock within the timeout window. In some cases, orphaned metadata from an improperly terminated external data source connection can also cause lock contention to persist indefinitely.

Step-by-Step Resolution Guide

Step 1: Identify Blocking Sessions

  • Open SQL Server Management Studio (SSMS) connected to the instance reporting the error.
  • Run sp_who2 or query sys.dm_tran_locks filtered by resource_type = 'EXTERNAL_DATA_SOURCE' to identify the session ID (SPID) holding the conflicting lock.
  • Cross-reference the SPID with sys.dm_exec_requests to check the query text and status (e.g., SUSPENDED, RUNNABLE).

Step 2: Terminate or Wait Out the Conflicting Session

  • If the blocking session is a legitimate long-running job, allow it to complete or reschedule the conflicting operation to a non-peak window.
  • If the session is orphaned or hung, terminate it safely using KILL <SPID>; in a new query window.
  • Avoid killing system session IDs (below 50) as this can destabilize the instance.

Step 3: Validate External Data Source Configuration

  • Navigate to the SQL Server Configuration Manager (available via Start > Microsoft SQL Server 2025 > SQL Server Configuration Manager on Windows Server 2025/Windows 11).
  • Confirm the PolyBase or Data Virtualization service is running without restart loops, as repeated service crashes can leave stale EDS locks.
  • Re-run DROP EXTERNAL DATA SOURCE and recreate the object using CREATE EXTERNAL DATA SOURCE with the correct LOCATION and CREDENTIAL parameters to clear any corrupted metadata.

Step 4: Adjust Lock Timeout Settings

  • If timeouts are caused by high concurrency, increase the LOCK_TIMEOUT setting at the session level using SET LOCK_TIMEOUT 5000; (value in milliseconds) before executing the EDS-dependent query.
  • For persistent environment-wide issues, review the max worker threads and locks configuration under sp_configure to ensure the instance has sufficient resources.

Step 5: Restart the SQL Server Service (If Necessary)

  • As a last resort, restart the SQL Server service via services.msc on Windows Server 2025 to clear any in-memory lock table corruption.
  • Ensure no critical transactions are pending before restarting the service.

Alternative or Verification Steps

  • Verify the fix by re-running the original query or ETL job that referenced the EDS object; the operation should now complete without throwing Error 12701.
  • If the error persists after killing sessions and recreating the external data source, check the SQL Server error log (ERRORLOG file located in C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\) for underlying I/O or network timeout issues related to the external data connection.