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

by

Troubleshooting Guide: SQL Server Error 10035 — “No value was given for one or more of the required parameters”

Why This Error Happens

This error typically occurs when a stored procedure, SSIS package, or application call to SQL Server 2025 omits a required parameter value, often due to a mismatch between the expected parameter schema and the actual call signature. It can also surface when corrupted metadata in a linked server configuration or an outdated OLE DB/ODBC provider fails to map parameters correctly between Windows Server 2025/Windows 11 client drivers and the SQL engine. Additionally, permission restrictions on the executing account can prevent SQL Server from resolving default parameter values, triggering this error instead of a more descriptive access-denied message.

Step-by-Step Resolution Guide

Step 1: Verify Stored Procedure and Query Parameters

  • Open SQL Server Management Studio (SSMS) and locate the exact stored procedure or query triggering the error.
  • Run sp_helptext 'YourProcedureName' to review required parameters.
  • Confirm that every @Parameter in the definition has a corresponding value supplied in the calling application or script.
  • Check for NULL values being passed where a default is not defined.

Step 2: Update or Reconfigure the Data Provider/Driver

  • Navigate to Control Panel > Administrative Tools > ODBC Data Sources (64-bit) on Windows Server 2025 or Windows 11.
  • Ensure the SQL Server Native Client or Microsoft OLE DB Driver 19+ is installed and selected (not a legacy driver).
  • If using a linked server, run:
  EXEC sp_testlinkedserver 'YourLinkedServerName';
  • Reconfigure the linked server provider options via Server Objects > Linked Servers > Properties to ensure “Dynamic parameter” support is enabled.

Step 3: Check Application Connection String and Command Object

  • Inspect the application code (ADO.NET, ODBC, or OLE DB) for missing Parameters.Add() or Command.Parameters.AddWithValue() calls.
  • Ensure parameter order matches the stored procedure definition exactly, especially if using positional (not named) parameters.
  • Validate the connection string does not strip parameter metadata (e.g., missing Provider=SQLNCLI11 or incorrect Initial Catalog values).

Step 4: Review Permissions and Execution Context

  • Confirm the executing Windows account or SQL login has EXECUTE permission on the procedure:
  GRANT EXECUTE ON YourProcedureName TO [YourUser];
  • Check Event Viewer under Windows Logs > Application for correlating Event ID 10035 entries with additional context.

Step 5: Repair or Reinstall Affected Components

  • If the error persists, repair the SQL Server 2025 client tools via Settings > Apps > Installed Apps > Microsoft SQL Server > Modify.
  • Reboot Windows Server 2025/Windows 11 and re-test the failing query or integration job.

Alternative or Verification Steps

  • Re-run the original query or application call with SQL Server Profiler or Extended Events active to confirm no parameter-binding errors remain in the trace output.
  • As an alternative fix, manually recreate the stored procedure or linked server definition from a known-good backup script to rule out metadata corruption.