How to troubleshoot Core Installation

Version 4

    Verified Product Versions

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

    Core Installation is a multi-step process proper troubleshooting requires the user to know what part of the process they are in and where to find the proper log files.


    Installation Part 1:  Autorun


    The Autorun part of the installation starts with the execution of Autorun.exe from the installation media, when this is started it will create an Autorun.log it can be found in %temp%.


    Autorun.log will show the start of the process which will include pre-requisite detection and steps that come after.


    The next section of the Autorun part will lead us to database setup.


    Installation Part 2:  Database Setup / CoreDBUtil


    Database Setup calls the LANDesk Database Schema installer which is called CoreDBUtil.exe.


    CoreDBUtil.exe is typically called from the \..\Program Files\LANDesk\Management Suite\ directory in LANDesk but in this case the schema is built from a temporary directory that is built in C:\Program Files\landesk\DBConfigVApp.   The name of the log is CoreDBUtil.exe.log.


    This log shows the successful completion or failure of communication and build of the database schema.


    Common failures are typically things such as incorrect ports:


    Or insufficient privileges for the specified user:


    An overlooked troubleshooting step could include replacing the ..\Program Files\LANDesk\ManagementSuite\datamart.xml, with the datamart.xml located in the original installation media folder of the current core version. A successful run of coredbutil.exe once again may indicate the current datamart.xml is corrupted. Of course, it is recommended to backup the current datamart.xml before this step.


    After database setup has been completed we will enter the MSI Setup section of setup.


    Installation Part 3:  MSI Setup


    MSI Setup includes the laying down of necessary LANDesk files, setup of registry keys, registry of DLL's, web server setup, and running of secondary processes.


    This includes many logs, the following section will describe them.


    These logs will be placed in either %temp% or %windir%\temp\ or %ldmsdir%\Install Only Files\.


    %temp%\msi*.log - Actual MSI log from the setup, %temp%\LANDesk.Install.YYYY.MM.DD>TTTTTT.log shows same logging with more information.

    %temp%\LANDesk.Install.YYYY.MM.DD.TTTTTT.log - MSI log from actual setup, shows complete information of setup and many PostSetupConfig actions.


    Installation Part 4:  PostSetupConfig


    PostSetupConfig.exe is called by the LANDesk MSI, so it could be considered a sub-step of setup, but for purposes of this article we will describe it as a separate setup step.  PostSetupConfig.exe is used to call setup actions that are not performed by the MSI and happen after the major part of installation.  These actions will in reality take much of the installation time they include steps such as the setup of AMP, which we will discuss specifically.


    %temp%\PostSetupConfig.exe.log - This log shows the steps taken as described by the PostSetupConfig.xml, and will show errors related to each action.

    \..\LANDesk\ManagementSuite\InstallOnlyFiles\PostSetupConfig.xml - This is essentially a script of the actions that PostSetupConfig will perform.

    %temp%\LDCreateApplicationPool.exe.log - Shows the creation of Application Pools in IIS and any related errors.

    %temp%\amp_install.log - Shows the setup of AMP and any related errors.