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

by

Troubleshooting Guide: Error 7306 – Cannot Open Table from OLE DB Provider for Linked Server

Why This Error Happens

Error 7306 occurs when SQL Server cannot establish a valid connection to a table or view on a linked server through the specified OLE DB provider. This typically stems from insufficient permissions on the remote data source, a misconfigured provider (missing “Allow InProcess” or security context settings), or the underlying table/schema having changed or been dropped on the remote server. In Windows Server 2025 / SQL Server 2025 environments, this is also frequently triggered by stricter default security policies blocking impersonation or ad hoc distributed queries.

Step-by-Step Resolution Guide

Step 1: Verify Linked Server Login Mappings and Security Context

  • Open SQL Server Management Studio (SSMS) and navigate to Server Objects > Linked Servers > [Your Linked Server] > Properties.
  • Under the Security tab, confirm that the login mapping uses a valid remote user with explicit SELECT permissions on the target table.
  • If using “Be made using this security context,” re-enter the remote credentials to rule out expired or changed passwords.
  • Run the following T-SQL to test the context explicitly:
  EXEC sp_testlinkedserver 'YourLinkedServerName';

Step 2: Check OLE DB Provider Configuration (Provider Options)

  • Navigate to Server Objects > Linked Servers > Providers > [Provider Name] (e.g., MSOLEDBSQL, OraOLEDB).
  • Right-click and select Properties, then ensure “Allow InProcess” is checked. This is often disabled by default in new SQL Server 2025 installations for security hardening.
  • Restart the SQL Server service via services.msc or run:
  Restart-Service MSSQLSERVER -Force

Step 3: Validate the Remote Table/Schema Existence

  • Connect directly to the remote server (bypassing the link) and verify the table referenced in the error (%ls) still exists in the expected schema.
  • Check if the table was renamed, dropped, or moved to a different schema, as SQL Server 2025 strictly validates object metadata caching.
  • Run sp_refreshsqlmodule or drop/recreate the linked server definition if metadata is stale.

Step 4: Review Windows Firewall and Network Connectivity

  • On Windows Server 2025, open Windows Defender Firewall with Advanced Security.
  • Ensure TCP Port 1433 (or the custom port used by the remote instance) is open for both Inbound and Outbound rules.
  • Test raw connectivity using PowerShell:
  Test-NetConnection -ComputerName RemoteServerName -Port 1433

Alternative or Verification Steps

  • Verification: Run a simple distributed query (SELECT * FROM [LinkedServerName].[DatabaseName].[dbo].[TableName]) to confirm the connection resolves without throwing Error 7306.
  • Alternative: If permissions and connectivity are confirmed correct but the error persists, try switching the Linked Server provider from the native client (e.g., SQLNCLI11) to the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL), as legacy drivers are often deprecated or restricted in Windows Server 2025 environments.