Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

MSI Installer

May
130
1
I'm having trouble installing v20 b17. is there any chance I can download the MSI package from somewhere
 
Thanks,
Have you ever seen this error or do you have an idea of what's going on why is it trying to get JPSoft\TCMD20?

this is the log:

MSI (c) (74:B4) [20:59:31:648]: Product: Take Command x64 20.0 -- Error 1606. Could not access network location JPSoft\TCMD20.

MSI (c) (74:B4) [20:59:31:649]: Note: 1: 1314 2: JPSoft\TCMD20
MSI (c) (74:B4) [20:59:31:649]: Note: 1: 1606 2: JPSoft\TCMD20
MSI (c) (74:B4) [20:59:32:399]: Product: Take Command x64 20.0 -- Error 1606. Could not access network location JPSoft\TCMD20.

MSI (c) (74:B4) [20:59:32:400]: Note: 1: 1314 2: JPSoft\TCMD20
MSI (c) (74:B4) [20:59:32:400]: Note: 1: 1606 2: JPSoft\TCMD20
MSI (c) (74:B4) [20:59:34:114]: Product: Take Command x64 20.0 -- Error 1606. Could not access network location JPSoft\TCMD20.

MSI (c) (74:B4) [20:59:34:115]: Note: 1: 1606 2: JPSoft\TCMD20
MSI (c) (74:B4) [20:59:37:755]: Product: Take Command x64 20.0 -- Error 1606. Could not access network location JPSoft\TCMD20.

Action ended 20:59:37: CostFinalize. Return value 3.
MSI (c) (74:B4) [20:59:37:760]: Doing action: FatalError
Action start 20:59:37: FatalError.
Info 2826. Control Bitmap on dialog FatalError extends beyond the boundaries of the dialog on the bottom by 1 pixels.
MSI (c) (74:F4) [20:59:37:783]: Note: 1: 2731 2: 0
MSI (c) (74:D8) [20:59:40:440]: Doing action: AI_SHOW_LOG
 
MSI error 1314 and 1606 mean that some directory path is not "physically" available (for illustrations: error 1315 would mean folder exists, but "access denied" ).


Most probable cause: some (user) shell folder is not - or wrong - defined.
You can find these in the registry under:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
(Where the Current User is of course the (administrator) installation account
Just check if all these folders actually exist. If not: create them and re-run the installer.

Easy access to these registry keys through REG.exe:
Code:
reg.exe query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders"

Good luck!

If that doesn't do the trick: There's an option to set the logginglevel to "debug". That will give a lot more detail for what might cause this behaviour.
 
Little CMD script (assuming no TCMD available because of installation issues) to list missing Shell folders:

(The backslash at the end of "if not exist %%y\ " is to make sure %%y is a folder and not a file that goes by the same name.)

Code:
@echo off
cls
set DUMP=%temp%\dump.txt

for %%a in ("HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" ^
            "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders"  ^
            ) DO CALL :CHECKREG %%a
::DONE
del "%DUMP%"
goto :EOF              

:CHECKREG
   REG.exe export %1 ""%DUMP%"" /y >nul
   type "%DUMP%"
   for /f "usebackq skip=3 tokens=2 delims==" %%y in (`type "%DUMP%"`) DO (if not exist %%y\ echo MISSING : %%y )
echo.----------------------------------------------------------
goto :EOF
 

Similar threads

Back
Top