Installation Problem Qlik Sense Desktop

[Anonymous]

Hi All,

I'm new in Qlik and try to install the demo version (Qlik Sense Desktop) which i got from www.qlik.com (Qlik_Sense_Desktop_setup.exe - 571 MB) but still failed to install. I already tried to change location in registry likeRe: Installation problem (always rolls back)‌, and my .NET Framework version already 4.5.2. My OS Win 7 64 bit, when installed i using 'Run as Administrator', already tried turn off Firewall, and already tried 'Normal Install (defined installation location)' or 'Custom Installation (custom installation location to drive D)'

I've attached the logs to this post, can someone please assist in identifying the problem?

Many Thanks

[Alexis_Touet]

Hey Rhenasantoso, 

Do you still need help on this ?

Looking to the log file, it shows the error  after trying to execute commands within powershell.

MSI (s) (D8:20) [14:20:52:132]: Executing op: CustomActionSchedule(Action=CA_ConvertToUTF8,ActionType=1025,Source=BinaryData,Target=CAQuietExec,CustomActionData="powershell" -NoLogo -NonInteractive -InputFormat None –ExecutionPolicy Unrestricted -Command "if (Test-Path -path 'D:\Qlik\Sense\Engine\Settings.ini') {{ (Get-Content 'D:\Qlik\Sense\Engine\Settings.ini') | Set-Content -Encoding UTF8 -Force 'D:\Qlik\Sense\Engine\Settings.ini'" }})

MSI (s) (D8:20) [14:25:03:620]: Note: 1: 1708
MSI (s) (D8:20) [14:25:03:620]: Note: 1: 2205 2: 3: Error
MSI (s) (D8:20) [14:25:03:620]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708
MSI (s) (D8:20) [14:25:03:620]: Note: 1: 2205 2: 3: Error
MSI (s) (D8:20) [14:25:03:620]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (D8:20) [14:25:03:620]: Product: Qlik Sense Desktop -- Installation failed.

MSI (s) (D8:20) [14:25:03:620]: Windows Installer installed the product. Product Name: Qlik Sense Desktop. Product Version: 12.26.1. Product Language: 1033. Manufacturer: QlikTech International AB. Installation success or error status: 1603.

I´ve  had several cases with customers with similar log files and the root cause was the path to Powershell.exe in system environment variable named PATH that was incorrect. 

One way to test this would be to try open powershell, by just going to windows start > run > typer powershell.exe and press enter. 

If it fails, retry to launch powerhsell.exe from %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ , see if it works  fine.

Hope this can help!