Hi Tim, am particularly interested in this as we've experienced issues with the May 2025 security updates for SQL 2022 as well.
Just to recap my understanding: -
If you're using <mssql-advanced-monitoring>1</mssql-advanced-monitoring> in Agent - Advanced Configuration, then you introduce a dependency of correct Agent functioning on ACP updates.
Each ACP is validated only against specific supported SQL Server builds.
If you apply a Microsoft security update before the supporting ACP is available then you end up with the dreaded "Agent does not support this MSSQL version".
Imperva's advice therefore is to coordinate the MSSQL patching with the availability of the ACP that supports that patch level.
In my opinion that's quite an ask, because the imperative with a critical Microsoft security update may be to deploy it across your SQL Server estate as soon as possible.
So it looks like Imperva DAM users are being asked to make a decision to either
a) delay the deployment a critical security patch, or
b) deploy the patch, and accept that your Imperva DAM agents will be non-functional until the ACP is available
Here's a specific case: - on May 12th Microsoft released critical security update KB5089900 for SQL Server 2022. The supporting ACP was not released until 1st June. That's a long wait if you go for option b).
I find it hard to believe that customers are being constrained in their deployment of critical security updates in this fashion, and would be interested to hear how other organisations are managing this situation.
------------------------------
Ghanesh Narine
Database Administrator
Royal London Mutual Insurance Society Limited
London
------------------------------
Original Message:
Sent: 05-29-2026 14:22
From: Tim Sneed
Subject: Imperva Agent Error After Latest MS SQL Patch – "Agent does not support this MSSQL version"
This message started showing up for us this week May 25 or so. Never seen it before in the years of using Imperva DAM, so in this case it seems like the April or May SQL patches, to SQL 2019 and SQL 2022 caused the error. For now waiting too see how many agents do it once all the servers have the same patches and we'll see if a new ACP comes out to address it since we are at the latest ACP as of today and we updated DAM just a month ago.
------------------------------
Tim Sneed
Systems Solution Engineer
Michigan Education Special Services Association (MESSA)
------------------------------