System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

[mikenruiz]

Ok, now everything seems to be working but today i decided to check the log just to be sure and came accros this error "System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable." Now the error has been there since a few days after install. The system was installed on 9/15 and the error started on the 18th. HELP PLEASE!

[Hemoco]

Hi,

Could you please mail us at lansweeper@hemoco.com for a beta 3.5.2 build.

[jbcsystech]

I just did a fresh install for ver. 3.5.2.4 and getting the same error. Running on;

Windows 2008 32bit
SQL 2005
All SPs and fully patched

here is a sample of the log:

12/3/2009 2:58:21 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

12/3/2009 3:13:22 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

12/3/2009 3:28:23 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

12/3/2009 3:43:24 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

12/3/2009 3:58:26 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

12/3/2009 4:04:47 PM: Stopping service

12/3/2009 4:04:49 PM: Database connection successful, starting up service

12/3/2009 4:04:50 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

[Hemoco]

Do you remember your previous version number?

[googoo]

Any follow-up on this error in the log? We also get it...approx 3x/min. In our organization, a number of domain controllers are firewalled and we cannot access, thus we used to have a number of "{domain} {domain controller} The server is not operational" errors. However, those have now stopped and instead we get the LDAP error mentioned in this post. We are also at ver3.5.2.4--are these errors the same, but handled differently due to a Lansweeper version change? I know we did upgrade, but don't remember the specific day. I have not noticed a change in functionality, all seems to be working.

[Hemoco]

Do you notice functionalities not working?

[Hemoco]

Which is your lansweeperservice.exe version?

[mikenruiz]

Lansweeper wrote:
Which is your lansweeperservice.exe version?

It's 3.5.2.4

[Hemoco]

Does the error also states a computer name (domain controller)

This happens when a domain controller could not be reached (because it is down/removed/Wan connection down, ...)

[mikenruiz]

Lansweeper wrote:
Does the error also states a computer name (domain controller)

This happens when a domain controller could not be reached (because it is down/removed/Wan connection down, ...)

Below are the actual lines on the error log. No server name 😞


9/30/2009 6:33:25 AM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

9/30/2009 6:49:20 AM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

9/30/2009 7:40:50 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

10/1/2009 1:13:56 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

10/1/2009 1:30:04 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.

10/1/2009 1:46:20 PM: System.DirectoryServices.Protocols.LdapDirectoryIdentifier The LDAP server is unavailable.