We're running AppVolumes 4 v2303.1 and seeing the below errors in the system messages of our appvol managers. An AD domain has been configured with a list specifying 2x controllers, both are healthy and in a connected status. Periodically we see the below error in the system log, usually just 1x instance per DC within a 48 hour period. It's not service affecting but it's annoying.

LDAP bind failed for "DOMAIN x' and 1=2 union select '202cb962ac59075b964b071S2d234b70' ,'1" on "domaincontroller.org (Id

dc.org error "49": 8009030C: LdapErr: DSlD-OC090590, comment: Acceptsecuritycontext error, data 52e, v258

I've read through the below and adjoining KBs. The only configured policy setting on the DC that relates to this issue is  LDAPServerIntegrity set to 1 . I don't believe this to be the issue, the other policy LdapEnforceChannelBinding is not set on either DC. There are no backup jobs running or anything that might cause latency/connection flap. 

I've tried to configure:

• LDAPS (failed),
• LDAP over TLS but there's no root cert available on the manager node (this is a customer environment).
• Re-entered the credentials for the AD bind. The account isn't locked, credentials are accepted.

Hoping someone has some other ideas?

2020 and 2023 LDAP channel binding and LDAP signing requirements for Windows (KB4520412) - Microsoft...

Solved: LDAP Channel binding failed login - VMware Technology Network VMTN