There are a lot of Active Directory
errors out there. Way too many, right?

You as a sysadmin know that for sure – LDAP errors, Active Directory replication errors,
problems with the domain services and various other internal Active Directory error codes.

Here's a list of the most common errors around Active Directory and the proven solution to them:

Active Directory error 0x800708c5
Active Directory error 0x51
Active Directory error 80040e37

And you'll find the solution to get rid of ALL active directory errors – forever: Test PRTG and get started within minutes!

1. Active Directory error:

"Active Directory error 0x800708c5"

Quick fix

The password does not meet the password policy requirements.

The error 0x800708c5 occurs because the password being set does not comply with the Password Policies set on the domain.

Check the minimum password length, password complexity, and password history requirements.
From the account go to the Password tab and choose "Past Passwords" - select the failed entry and go the "Password" tab
Confirm the password complies with the Password Policy set on the domain or fine-grained password policy.

Hint: Also, ensure the "Minumum Password Age" has been taken into account.

Proper fix

Switch to PRTG: PRTG network monitor offers integrated, complete active directory monitoring in real time.

Find out how PRTG's Active Directory Monitoring can help you get rid of those errors

2. Active Directory error:

"Active Directory error 0x51"

Quick fix

Get the error message "Active directory response: The LDAP server is unavailable"?

Create a new "global catalog" on the 2nd domain controller, that will fix the problem 0x51.

Step by step:

On the domain controller where you want the new global catalog, start the Active Directory Sites and Services snap-in. To start the snap-in, click Start, point to Programs, point to Administrative Tools, and then click Active Directory Sites and Services.
In the console tree, double-click Sites, and then double-click <var>sitename</var>
Double-click Servers, click your domain controller, right-click NTDS Settings, and then click Properties.
On the General tab, click to select the Global catalog checkbox to assign the role of global catalog to this server.
Restart the domain controller.

Proper fix

Switch to PRTG: PRTG network monitor offers integrated, complete active directory monitoring in real time.

Find out how PRTG's Active Directory Monitoring can help you get rid of LDAP server errors

3. Active Directory error:

"Active Directory error 80040e37"

Quick fix

Error 80040E37 (Variation: Error 800401E4) means there is an error with the LDAP domain database table.

Hint: It's most likely that there is a syntax error in the LDAP:/domain line.

This error code 80040E37 basically occurs when you execute a VBScript. You are probably using a WSH method to connect to LDAP. It means an incorrect reference to the domain in an LDAP command.

Check the Line in your script that references the 'Provider'. If necessary, work back for previous LDAP occurrences.

Hint: Double-check Char 1. The error just means that the whole line will not execute. In the case of runtime errors you can use this work around. Add this line: On Error Resume Next.