-
Title
In 2.5.918 when the "Windows Active Dir" platform is configured to "Use Domain Account"; an "Unhandled Exception" error may be returned when running LDAP Mappings. -
Description
This affects 2.5.918: When the functional account on a "Windows Active Dir" platform is set to a domain account (via "Use Domain Account" dropdown), an error may be returned when running an LDAP mapping via Auto Discovery.
The error returned:
"Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at PerlRuntime.Interpreter.destroy(Int32 perl) at PerlRuntime.Interpreter.ProcessExit(Object sender, EventArgs e)"
It may also not be possible to use the 'magnifying glass' to locate the mapping - the page with the "LDAP Directory Explorer" may load but not progress to the point where selecting the specific target within AD is possible.
-
Cause
The ability to use a Domain Account as a functional account for "Windows Active Dir" platforms was added in 2.5.918; however there are further updates to the Auto Discovery portion related to this change that are expected to be included in a future release of the product. -
Resolution
WORKAROUND: Change the "Windows Active Dir" platform to have a local functional account rather than using the "Use Domain Account" dropdown.
STATUS: BFER 9328 has been addressed in TPAM 2.5.919. From the TPAM 2.5.919 Release Notes 'Resolved Issues' section: "Auto Discovery for Windows Active Directory systems not working using a domain account."
-
Change Request
9328