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

by

Troubleshooting Guide: SQL Server Error 10755

Why This Error Happens

Error 10755 occurs when a T-SQL statement calls a built-in or user-defined function with an incorrect number of arguments, violating the function’s defined signature. This is typically caused by a syntax mistake in recently modified or migrated code, a mismatched function overload, or a stored procedure/script that was written against a different version of a function definition (e.g., after an in-place upgrade to SQL Server 2025 where a function signature changed). In some cases, corrupted or outdated cached execution plans on Windows Server 2025 / Windows 11 environments can also reference stale function metadata, triggering this error incorrectly.

Step-by-Step Resolution Guide

Step 1: Identify the Exact Function and Statement

  • Open SQL Server Management Studio (SSMS) and locate the full error message in the Messages tab, noting the function name and the batch/line number.
  • Run the failing query in isolation to confirm reproducibility.
  • Use SELECT OBJECT_DEFINITION(OBJECT_ID('YourFunctionName')) to inspect the function’s current definition if it is user-defined.

Step 2: Validate the Function Signature

  • Compare the number of arguments in your calling code against the official syntax.
  • For system functions, check Microsoft’s official SQL Server 2025 documentation, as argument requirements may have changed between versions (e.g., CONCAT, FORMAT, JSON_OBJECT, etc.).
  • For user-defined functions (UDFs), run:
  SELECT ROUTINE_NAME, DATA_TYPE, ORDINAL_POSITION, PARAMETER_NAME
  FROM INFORMATION_SCHEMA.PARAMETERS
  WHERE SPECIFIC_NAME = 'YourFunctionName';
  • Correct the calling statement to match the expected minimum/maximum argument count shown in the error message.

Step 3: Clear Cached Execution Plans (If Applicable)

  • If the function was recently altered but the error persists, clear stale plan cache entries:
  DBCC FREEPROCCACHE;
  • Alternatively, target a specific plan using DBCC FREEPROCCACHE (plan_handle) to avoid a full cache flush on production servers.
  • Restart the SQL Server (MSSQLSERVER) service via Services.msc on Windows Server 2025 if the issue persists after cache clearing.

Step 4: Recompile and Redeploy the Function

  • If the function is user-defined, drop and recreate it with the corrected parameter list:
  DROP FUNCTION IF EXISTS dbo.YourFunctionName;
  GO
  CREATE FUNCTION dbo.YourFunctionName (@Param1 INT, @Param2 VARCHAR(50))
  RETURNS INT
  AS
  BEGIN
      -- function body
  END;
  • Redeploy any dependent stored procedures or views that reference this function using sp_refreshsqlmodule.

Step 5: Check Application/ORM Layer

  • If the call originates from an application (e.g., Entity Framework, a .NET service, or a reporting tool), verify that the ORM-generated query matches the updated function signature.
  • Update any hardcoded SQL strings in application code and redeploy the application on Windows 11 development machines or Windows Server 2025 hosts.

Alternative or Verification Steps

  • Re-run the originally failing query/stored procedure and confirm no Error 10755 appears in SSMS or the SQL Server Error Log (via EXEC sp_readerrorlog).
  • As a quick verification, use sys.dm_exec_describe_first_result_set or sp_help 'FunctionName' to confirm the function now accepts the correct argument range before rolling the fix out to production.