Tech Tip:  eHealth command will not run from MKS (bash/sh/ksh) shell on Windows

Document created by kk_sup Employee on Oct 16, 2014Last modified by SamCreek on Dec 17, 2016
Version 2Show Document
  • View in full screen mode

When executing a command at the Windows command-line, Windows will execute the .exe or .bat version in the order found in  %PATHEXT%


The MKS environment provides a unix like scripting environment.


When in an MKS shell, if you have a file with no extension in your %PATH% which is the same as an eHealth command, this would be executed before

the exe, .bat version as the shell environment does not require file extensions.


For example, nhDiscover would be executed before nhDiscover.exe.


We have seen cases where there is a zero byte file with no extension created somewhere in the %PATH% in this manner.


In this case, the MKS shell would execute the blank extension-less file, which is basically running an empty shell script.


To resolve this problem, remove the zero byte file.