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

by

Troubleshooting Guide: SQL Server Error 2743 — “%ls option requires %S_MSG parameter”

Why This Error Happens

Error 2743 occurs when a command-line setup or configuration action is executed with an incomplete argument set, specifically when a required parameter is missing for a given command-line switch. This typically happens during SQL Server 2025 installation, patching, or silent-install scripting when a flag such as /ACTION, /FEATURES, or /INSTANCENAME is passed without its corresponding mandatory value. It can also surface if a batch file, PowerShell script, or deployment tool (like SCCM or DSC) has malformed or truncated command syntax due to copy-paste errors or encoding issues.

Step-by-Step Resolution Guide

Step 1: Identify the Exact Command That Triggered the Error

  • Open the Setup Bootstrap log located at C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\<timestamp>\Summary.txt.
  • Look for the Command Line Arguments section to see exactly which switch was passed without its required value.
  • Cross-reference the flagged parameter against the official syntax list in setup.exe /? or setup.exe /ConfigurationFile.ini.

Step 2: Correct the Command-Line Syntax

  • Re-check switches like /ACTION=Install, /INSTANCENAME=<InstanceName>, /FEATURES=SQLENGINE, or /SAPWD=<password> to ensure every flag has a correctly quoted value immediately following it.
  • If using a ConfigurationFile.ini, open it in Notepad and confirm no line ends with a trailing = or blank value (e.g., INSTANCENAME= is invalid; it must be INSTANCENAME=MSSQLSERVER).
  • For PowerShell-based automation, wrap all values containing spaces or special characters in double quotes, e.g., "/SAPWD=P@ssw0rd!".

Step 3: Re-run Setup with Verbose Logging

  • Execute setup again from an elevated Command Prompt with logging enabled:
  • setup.exe /ACTION=Install /ConfigurationFile=C:\SQLConfig\ConfigurationFile.ini /INDICATEPROGRESS
  • Monitor the console output in real time; it will now specify the exact missing %S_MSG value if the parameter is still malformed.

Step 4: Validate Group Policy or Deployment Tool Overrides

  • If deploying via SCCM, Intune, or a third-party automation tool on Windows Server 2025, check the deployment task sequence for variable substitution issues (e.g., an empty environment variable being injected into the command line).
  • Confirm that any %VariableName% placeholders in batch scripts are resolving correctly by running echo %VariableName% before the setup call.

Alternative or Verification Steps

  • Run setup.exe /ConfigurationFile=<path> /Action=Install /Quiet and check the exit code (0 indicates success); review Detail.txt in the same Bootstrap Log folder to confirm no further missing-parameter warnings appear.
  • If the error persists, bypass the command line entirely and use the SQL Server Installation Wizard GUI to manually step through options — this isolates whether the issue is a scripting error or a corrupted setup.exe/configuration file, which can be resolved by re-extracting the installation media.