IBM Support

Windows STAP 12.2.0.x, 12.1.x, 12.0.x, and 11.5.x can cause unexpected MSSQL server termination when partial or malformed TDS PDUs are processed

News


Abstract

Upgrading or installing Windows STAP v12.2.0.x, v12.1.x, v12.0.x and v11.5.x could cause instability on the MSSQL server.

Content

MSSQL Server service interruption can occur when using one of the following Windows STAP versions v12.2.0.x, v12.1.x, v12.0.x. This issue is observed only when the STAP process encounters unusual or corrupted SQL communication, which can trigger an unexpected disruption of the SQL Server service.  

 Remediation

Resolution: Fix for this issue is released with the following Windows STAP: 

  • v12.2.1 : Windows STAP 12.2.1.205  (see release note)

  • v12.1 : Windows STAP 12.1.23.263 (see release note)

  • v12.0 : ETA End of May/2026

  • v11.5 : Windows STAP 11.5.10.528 (see release note)

 Workaround:

Listed below is the workarounds to implement while preparing environment to upgrade to the upcoming fixed version

 Step1 :  Stop STAP

Step2: Set WFP_PROCESS_RESOLVE_MODE=1 in INI file. 

Step3 : Restart STAP

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"ARM Category":[{"code":"a8m0z000000Gp0IAAS","label":"STAP"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"11.5.0;12.0.0;12.1.0;12.2.0"}]

Document Information

Modified date:
30 April 2026

UID

ibm17259591

Page Feedback