Issue with the Unmanaged Device Discovery (UDD) module crashing in the Landesk console

Version 4

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6Endpoint Manager 2016.x



    The Unmanaged Device Discovery (UDD) module crashes when you select the option in the Landesk console.


    As a result, you are not able to edit the current UDD configurations or even create a new one


    Additionally, the console.exe.log file located in the "ManagementSuite\logs" folder on the core server shows the following entries:


    INFO  2088:Main Thread RollingLog : FormMain: NagForDeliquency

    INFO  2088:Main Thread RollingLog : FormMain: Leave LoadUserData()

    INFO  2088:Main Thread RollingLog : FormMain: Load User Data (layouts, etc) end

    INFO  2088:Main Thread RollingLog : FormMain: Leave FormMain_Load

    INFO  2088:Main Thread RollingLog : Starting _discdll.dll

    INFO  2088:_DiscDllStart main thread RollingLog : Critical Exception: System.ArgumentException: An entry with the same key already exists.





    Most probably, this issue is caused by one or several duplicate entries in the LD_TASK_CONFIG table in the SQL database of the core server.


    For instance, 2 IP ranges configuration in the Scan Network module might have the same name.





    Here is how to fix the issue:


    Step 1: Make sure you have a backup of the SQL database before proceeding.


    Step 2: Install and run Microsoft Management Studio to access the database


    Step 3: Once connected to the database, search for the LD_TASK_CONFIG table. This is the table where all tasks configuration - including UDD configurations records - are stored


    Step 4: Edit the content of the LD_TASK_CONFIG table and search for any duplicate entries. These might be one or more UDD configurations sharing the same name.


    Step 5: You can then delete the duplicate entries or just rename them using a SQL query.



    Try to restart the Landesk console and select the UDD option. Now it should work fine.