Database Repair Utility (DBRepair.exe download)

Version 45

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2017.xEndpoint Manager 2018.x

    Download


    Download dbrepair06022011.zip for LANDESK 9.0 and 9.5 databases. Compatible with 9.0 supported Core OS's: Windows Server 2003 32 bit and Windows Server 2008 R2x64. This dbrepair includes the new snapshot function as described in UsingSnapshotInDbrepairRev1.pdf.

     

    Download DBRepair9.5 For Landesk9.5

     

    Download 96DBRepair.zip for LANDESK 9.6

     

    Download 9.6SP1dbrepair.zip for LANDESK 9.6 SP1, SP2 & SP3

     

    Download DBRepairLDMS2016.0.zip for LANDESK Management & Security 2016.0

     

    Download DBRepairLDMS2016.3.zip for LANDESK Management & Security 2016.3

     

    Download DBRepairEPM2017.1.zip for Ivanti Endpoint Manager 2017.1

     

    Download DBRepairEPM2017.3.zip for Ivanti Endpoint Manager 2017.3

     

    Download DBRepairEPM2018.1.zip for Ivanti Endpoint Manager 2018.1

     

    DISCLAIMER

    USE OF THE DBRepair.EXE APPLICATION SOFTWARE IS SOLELY AT THE USER’S AND/OR COMPANY’S OWN RISK.  THIS SOFTWARE APPLICATION IS AVAILABLE “AS IS,” AND LANDESK SPECIFICALLY DISCLAIMS ALL WARRANTIES INCLUDING ANY IMPLIED WARRANTIES.

     

    For LDMS 9 it should only need to be run initially after upgrading because 9.0 doesn't allow client scanner corruption to enter the database unless configured otherwise. See DOC-7456 for more information on how this is accomplished and how to allow custom unmodeled data into the database. In some circumstances it may be necessary to allow unknown items, in those cases using snapshot and a scheduled dbrepair is useful. This is also described in the UsingSnapshotInDbrepair pdf.

     

    Download the appropriate attachment and extract dbrepair.exe to the ManagementSuite directory on the core server. The path to the ManagementSuite directory is by default C:\Program Files\LANDesk\ManagementSuite.

     

    Instructions for Use

    1. Stop the inventory server service on the core server before running DBRepair.

     

    2. Verify that DBRepair.exe is in the ManagementSuite directory.

     

    3. Double click DBRepair.exe to run it.

     

    Note: Once DBRepair.exe opens, anything that appears in the tree is unmodeleddata. This includes either custom data that you have deliberately added (via a custom data form or by modifying ldappl3.ini) or data corruption.

     

    4. Delete database corruption if if is present as it can cause various issues.

     

    Note: If you have no custom data that you want to keep, then click on Computer at the top of the window and click the 'clean' button. If you have some custom data that you want to keep, click on the data you do  *NOT* want to keep, and click the 'clean' button.  You will need to remove (clean) each unwanted item individually.

     

    5. Close DBrepair.exe.

     

    6. Restart the Inventory Server service.

    Example

    If an item in the DBRepair.exe tree list appears to be a valid

    part of the inventory tree, it's not. Keep in mind that everything

    listed is unmodeleddata, so it can be safely removed. You only need to

    keep the items that you have added specifically as Custom Data.

     

    DBRepair.exe that looks like this:

     

    Computer

    -Custom Data

    -Motherboard

    -Loftwa6re

     

    Normally there is no such value as Loftwa6re. Clearly, the Loftwa6re item represents database corruption. However, even though Motherboard looks valid, by virtue of it being in this list, it is not valid and it should be removed.