Issue

In LDMS 2016, you notice an issue when an inventory is run on some managed computers.

A crash of the LDAPWHOAMI.exe process is automatically logged in the Windows events log as follows:

Log name:Application

Source : Application Error

Logged: 01/07/2016 15:33:39

IEvent ID:1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: your_computer_name

 

Description:

Faulting Application Name: ldapwhoami.exe, version: 10.0.1.41, time stamp: 0x56e30a9d

Faulting Module Name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098858e

Exception Code: 0xc0000417

Fault Offset: 0x0009f979

Faulting Process ID: 0x7a0

Faulting Application Start Time: 0x01d1d39d2b0802ce

Faulting Application Path: C:\Program Files (x86)\LANDesk\LDClient\ldapwhoami.exe

Faulting Module Path: C:\Program Files (x86)\LANDesk\LDClient\MSVCR110.dll

Report ID: 6adebb44-3f90-11e6-a99d-c8cbb805dd28

Cause

This is a known issue in LDMS 2016 that is currently being investigated by our engineering team.

The LDAPWHOAMI.exe is the process used in LDMS to resolve users in Active Directory.

The application crashes when the "DistinguishedName" value of the user in AD exceeds a specific number of characters.

Please note that a bug report has already been opened to address this issue.

Customers experiencing this issue are encouraged to contact our support team to have their case added to the bug report.

This is resolved in LDMS 2016.3