Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jan 9, 2024 5:07:38 AM
Jan 9, 2024 5:07:38 AM
After a Qlik Sense upgrade, the Qlik Sense Repository service fails to start. The following error is logged in the Windows Application Event log:
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
System.IO.FileLoadException: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5'
at Repository.QRSService.Start(Action`1 terminate)
at
The initial recommendation is to repair the installation. See How to repair an installation.
If the repair does not resolve the problem:
The Qlik.Sense.Logging.dll present in [Installation Qlik Sense folder]\Repository\ was missing required inforamtion.
I experienced this issue also in a patching scenario for Aug 2023 Patch and not only during a release upgrade. Confirm that installation repair resolved.
Thank you.
I had the same issue at one of our customers after updating from August 2022 Patch 17 to February 2024 IR.
Original situation: Qlik sense Enterprise on Windows release August 2022 with Patch 17 was installed on the Windows 2019 server. All the latest patches were applied. The installation was done in the default folders.
Performed a repair of the installation as described and it worked.
When is this issue planned to be resolved? Without needing a repair or a manual copy of the DLL? The issue still remains even with Patch 4 of Qliksense Feb 2024 (Enterprise on Windows).
We faced the issue highlighted in this article and out of the 2 options only a repair solved the issue.
When we use the other option of replacing the Qlik.Sense.Logging DLL. It then surfaces a new issue : The error looks similar to the one noted above, but now, it shows for another DLL
Unhandled exception: Could not load file or assembly 'Qlik.Sense.Communication, Version=37.12.0.0
The only reliable way is to do a repair.
The version we upgraded to was February 2024 Patch 4.
@Ranganath_DR , Can you please let us know about plans to resolve this error as a part of the February 2024 installer?
A repair is time-consuming. Hence, the above query.
We faced same issue while upgrading from Nov2023 to May2024.
It was fixed with repair as described.
We had another two updates that experienced the same issue. One from Aug. 2022 Patch 17 and one from Feb. 2023 IR. Both were upgraded to the Feb 2024 release.
We faced the same issue mentioned above after upgrading from QS May 2022 P2 to QS February 2024. We have found out that certain dll's in <INSTALLATION DIRECTORY>\Qlik\Sense\Repository folder from a healthy test environment had different timestamps from the one having issues. After replacing those, the Repository service started successfully.
I can confirm this is still an issue upgrading from May 2023 > to May 2024 IR, and occurred on 7 of my recent server upgrades.
The repair process resolved the issue but it would be nice not to have to effectively run the install program twice.
Are there any pre-checks we can perform to identify this prior to an upgrade?
Hi,
I encountered this again when upgrading a customer from May 2023 > to November 2024.
Copying the Qlik.Sense.Logging DLL from a working same version system did not resolve the issue, the DLLs had the same timestamp etc.
Performing the repair did resolve the problem; however, it took an additional 30 minutes per server.
Hopefully, the 2025 upgrades will detect and avoid this issue.