Unable to add a new LDAP source in the Landesk console

Version 5

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.x



    You need to add a new LDAP source into the Landesk core console.


    You have already entered the full details of the new LDAP directory, however when you click OK to save the settings, you get the following error code:


    "Unable to connect to LDAP directory - An error has occurred while connecting to your_domain directory"



    Additionally the console.exe.log file show the following entries:



    06/09/2016 09:26:10 INFO 10004:Main Thread RollingLog : Verify strong name for <D:\LANDesk\ManagementSuite\directorymanager.ui.dll> returned True. wasVerified: True

    06/09/2016 09:26:26 INFO 10004:Main Thread RollingLog : Main Thread RollingLog : DirManFactory: InvokeMethod exception - An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information

    06/09/2016 09:26:26 INFO 10004:Main Thread RollingLog : DrManAPIFactory: invoke DrManApi failed

    06/09/2016 09:26:26 INFO 10004:Main Thread RollingLog : DrManApi: DrManApiFactory.GetInstance failed.

    06/09/2016 09:26:26 INFO 10004:Main Thread RollingLog : Validating AD connection failure: DrManApiFactory.GetInstance failed.





    Despite what the error code suggests in the log file, this issue is not caused by .NET Framework but Microsoft Streams.


    Please note that this issue is more likely to happen after applying an upgrade to the core server, when several system files have been replaced or updated.





    1. Download Microsoft Streams utility and install it on your core server


    Streams download link


    2. From an admin prompt run the following command line:


    streams.exe -s -d "c:\install_directory_of_LDMS"


    3. Reboot the core server



    The issue should be fixed. If not, please restore a backup of your core server prior to applying the update and "unblock" the upgrade install file as explained in the TECHNOTE below before upgrading your core server:


    Unblock Downloads/Turn Off Streams



    More information about Microsoft Streams can be found here:


    Streams; and why you should remove them.