Good morning Yann,
You may need to uninstall a recent Windows update.
We have reason to believe that KB5039227 is to blame here for Server 2022. It appears the corresponding update for 2019 is KB5039211. I use the term corresponding loosely. They are unique updates. However, they were released on the same day (June 11th, 2024), and the notes suggest they created at least one identifcal bug in each respective OS.
One June 25th, Microsoft also released KB5039299. This could also be your culprit as once again it shares the same introduced bug. However, this is a preview build and it is less likely that you would have applied it.
My company is in the process of configuring a new network. We were able to succesffully implement the AD LDS (ADAM) instance on our LDAPS server. Unfortunately, two days later the instance began to fail.
Yesterday (July 7th, 2024) I posed a question to the Active Directory subRedditin hopes someone could assist in troubleshooting this. If you would like to see what troubleshooting steps I have taken thus far, follow the link. Aside from an automated moderator's reply, there are no responses yet. You can follow that link, or read the quoted text below for details on what troubleshooting I had completed up to this point.
This morning, I decided that the only item that remained was to one-by-one to remove the updates I had applied on the new VM prior to creating the instance. After removing all updates and reapplying them one-by-one, we determined that KB5039227 introduces some breaking change here. The full removal of the update allowed us to create another ADAM instance.
I have not begun further troubleshooting to see what is going on yet, but this gets it working again. You may want to consider rolling back recent updates, if possible.