When the backslash is there, all is well; when it's absent, the following line:
Code: Select all
if not "%CATALINA_HOME%" == "" goto gotHomeThe root cause isMSI (s) (DC:98) [14:48:44:201]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI4F25.tmp, Entrypoint: CreateExeProcess
/f" == "" goto gotHome was unexpected at this time.
Code: Select all
cmd.exe /c reg add "hkcu\Environment" /v CATALINA_HOME /t reg_sz /d "[APPDIR]" /fOriginally I'd found that per user installation paths didn't contain the training backspace and per machine install paths did, so i'd setup my install button in my dialog to call the custom action with either "[APPDIR]" or "[APPDIR]\" as required, but it seems that per machine installations sometimes contain the backslash and sometimes don't (when upgrading the installer to a new version and installing over top of an existing installation I'll get a failure the first time but re-running it will result in a clean re-installation).
FOLLOW US
Get the latest news in Application Packaging