Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everyone,
I have a problem upgrading qlik sense on windows (server 2019), I hope someone of you could help me.
While I try to install Qlik Sense February 2022 from November 2021 the upgrade process fails.
I would upgrade from original version November 2021 to May 2023 with an intermediate step by February 2022 to upgrade the repository service.
I get the following error:
Error 0x80070643: Failed to install MSI package.
Error 0x80070643: Failed to execute MSI package.
Error 0x80070643: Failed to configure per-machine MSI package.
Detected failing msi: PostgreSQL125
I access to the server with the user id used for the first installation, few years ago.
I stopped the services as described in the link:
Then I run the Qlik_Sense_setup.exe as Administrator.
The process end with a failed label when it's Upgrading Repository Database.
System requirements seem to be satisfied, but with a strange situation for .NET framework that needs to be v 4.8 or higher.
I see v4 from Registry Editor HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\
But I see Core 6 from Registry Editor KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NET
If I try to install .NET framework 4.8 from offline installer the installation process ends because it's already installed.
I also find out that 4.8 cause many problems on server that can be solved importing key registry, as explained in the link
But it do not solves my problem.
Qlik folder it's not in the default path C:\Program Files\... but in a custom folder in D:\ ...
I also check the Connection string editor from dyagnostic tool.
Initially it returns an error because the tool searched the Repository.exe.config in the default path. After I copied the Qlik folder in the Program Files path, keeping the old one, the dyagnostic tool doesn't show any error.
I also tried to change "Personal" registry entry as described in the links
But it doesn't work.
I'm not able to understand the problem and the solution,
have you any suggestions?
Thanks a lot
Claudia
Hi @Ray_Strother ,
I check the article and I see the powershell path in the Environment Variables. Powershell.exe can be evoked successfully from the path.
At the end of the article the author suggests to Install the Web Platform Installer Extension (WebPI) but following the link to the Microsoft page I find out that the WebPI was retired so I can't download it.