Error: "8DB50001 - Sdclient.exe or the installation program was terminated at the client" when deploying .EXE software package

Version 8

    Verified Product Versions

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

    Issue

    Error: "8DB50001 - Sdclient.exe or the installation program was terminated at the client" when deploying .EXE software package

     

    Cause

     

    8DB50001 is a status code that Ivanti EPM interprets as a failure.  However, what this really means is that the package closed without reporting an actual return code to Ivanti EPM.  What this is actually saying is that the software install stopped but did not tell Ivanti EPM whether it was a success or failure.

     

    Example from the SDClient_Taskxxx.log:

    Fri, 20 Apr 2012 09:56:22 6316 6712 Processing generic executable

    Fri, 20 Apr 2012 09:56:22 6316 6712 Launched application 'C:\Program Files\LANDESK\LDClient\sdmcache\packages\Testpackage\Setup.exe' result 1

    Fri, 20 Apr 2012 09:56:22 6316 6712 Installation result 8DB50001

    Fri, 20 Apr 2012 09:56:24 6316 6712 Sending task status, cmd line -coreandip=CORE96SP2:10.0.0.10 -taskid=82 -retcode=-1917517823 -complete -pkgid=20

    Fri, 20 Apr 2012 09:56:25 6316 6712 processing of package is complete, result -1917517823 (0x8db50001 - code 1)

    The executable may be stopped unexpectedly.  Common causes for this would be a system crash or BSOD.  If the executable is stopped unexpectedly, it would not return a code.

     

    However, the most common reason for this status is that the software manufacturer did not code any return codes into their .EXE package.

     

    More Information

     

    MSI packages have a standardized set of switches and return codes.  But this is not true for .EXE packages.  The software engineers who build the .exe can code in any switches and return codes they want, or none.  It is important to contact the vendor of your software and determine what switches are required for their software, and also what return codes you should expect for success and failure.  This is especially true if you see an unusual return code.

     

    Ivanti EPM treats unknown or unrecognized return codes, by default, as failures.

     

    Resolution

     

    First, you must determine what return codes you should expect to see from the .EXE software that you are installing.  Visiting the manufacturer's support website and searching is often successful for common software.  If the .EXE doesn't return any code, then LANDESK will not be able to validate whether the software installed successfully or not.  We must rely on the .EXE returning a code to tell us what happened during the install.  In cases like this, you will need to manually verify that the software installed.  Then, if you wish, you can use a return code mapping to cause the software to report back as a success:

     

    How to create a new Return Code Template - Video

     

    Be aware that, even with a return code mapping to success, Ivanti EPM is still not able to actually verify that the software was successful or not.  This will simply cause it to show success instead of failure for every attempt that returns the 8DB50001 code.

     

    If you determine that the .EXE you are using should be reporting return codes, you will need to troubleshoot why the client closed the .EXE without warning.  This could be a BSOD or application crash.  It could also be caused by an Antivirus or Endpoint Protection system triggering on the .EXE, or someone ending task on it in Task Manager.