AD exit code 8440

Question

Hello All,

 I am not sure this is the right place to ask this question. Whenever I try to install Kaspersky Security Center 13 in my Windows Server 2019 it's showing the below error. Please help me to resolve this.   

While synchronizing the Active Directory the '"C:\windows\system32\repadmin.exe" /syncall TRI-SVR-01 /AdeP' utility returned exit code 8440 and provided following output:
Syncing all NC's held on TRI-SVR-01.
Syncing partition:

Answer 1

Hello @Lokesh M ,

Thank you for posting here.

1.Is your AD forest with singal domain? Or do you have single forest with multiple domains?
2.How many DCs in every domains? We can run nltest /dclist:domain.com to check.

You can try to check if your AD environment is healthy firstly.

Run Dcdiag /v on every DC to check every DC health, then check if there is any error message or not.
Run repadmin /syncall /AdeP on any one DC to Force AD replication immediately, then check if there is any error message or not.
Run the following command to check AD replication status in the entire forest.
repadmin /showrepl >c:\repsum1.txt
repadmin /replsum >c:\repsum2.txt
repadmin /showrepl * /csv >c:\repsum.csv

If all above results are OK without any error message, then AD environment is healthy.

Should you have any question or concern, please feel free to let us know.

Best Regards,
Daisy Zhou

Answer 2

Hello @Lokesh M ,

So as I understand, you have an AD forest with a single domain and only one Domain Controller (TRI-SVR-01).

It looks like your AD environment is healthy.

Usually, if you have multiple DCs (For example, if you have two writable DCs, such as DC1 and DC2),

If there is any chage on DC1, DC2 will pull change on DC1 to DC2.
If there is any chage on DC2, DC1 will pull change on DC2 to DC1.

There is no synchronization between DCs because you only have one DC(PDC).

From the screenshot you provided, can you click "OK" button and continue to perform the operation?

Best Regards,
Daisy Zhou

Answer 3

i have the same problem installing ke 13.2.1511 on windows 2019 standard. Could it be a windows 2019 bug?
Claudio

Answer 4

I solved the problem, I had not correctly configured the dns server on the domain server and I did not resolve the fqdn. Also check name servers in forward and reverse lookup zone. Dns restart and installation is ok.