topic Re: Repair Got Stuck at Service Dispatcher in Management & Governance

Repair Got Stuck at Service Dispatcher

Rockstar7 — Thu, 08 Feb 2024 07:13:53 GMT

I am doing the repair of Qlik Sense (Feb 2023) and it got at Service dispatcher for more than 2 hours. In the Logs, i found the following,

MSI (s) (20:A0) [10:59:43:389]: Dir (target): Key: dirD54F78A3CCFC9BFD7B73D2A61EB113CE , Object: C:\Program Files\Qlik\Sense\ServiceDispatcher\dotnet\shared\
MSI (s) (20:A0) [10:59:43:389]: Dir (target): Key: dir6AF034159C65843ECFDF8F18AFE959D1 , Object: C:\Program Files\Qlik\Sense\ServiceDispatcher\dotnet\shared\Microsoft.NETCore.App\
MSI (s) (20:A0) [10:59:43:389]: Dir (target): Key: dir13A01FCAFDB5CB306EAC3226380A2857 , Object: C:\Program Files\Qlik\Sense\ServiceDispatcher\dotnet\shared\Microsoft.NETCore.App\3.1.25\
MSI (s) (20:A0) [10:59:43:389]: Dir (target): Key: dirB02FA4D212241B71CAADCCA70F2538D7 , Object: C:\Program Files\Qlik\Sense\ServiceDispatcher\dotnet\host\
MSI (s) (20:A0) [10:59:43:389]: Dir (target): Key: dir0CD087AF87DBE366B04A2FBCFE8B6D5C , Object: C:\Program Files\Qlik\Sense\ServiceDispatcher\dotnet\host\fxr\
MSI (s) (20:A0) [10:59:43:389]: Dir (target): Key: dirB25BD788E5EFC49C9F64CE39D0FB78BC , Object: C:\Program Files\Qlik\Sense\ServiceDispatcher\dotnet\host\fxr\3.1.25\
MSI (s) (20:A0) [10:59:43:389]: PROPERTY CHANGE: Adding INSTALLLEVEL property. Its value is '1'.
MSI (s) (20:A0) [11:00:43:315]: Allowing installation of component: {52005601-B1C7-5B37-BDCA-6503E4CB104E} even though a modified unversioned keyfile exists and file versioning rules would disable the component
MSI (s) (20:A0) [11:01:24:847]: Allowing installation of component: {11628A9F-D730-5FEB-B037-5F0E5F8B3775} even though a modified unversioned keyfile exists and file versioning rules would disable the component
Installer is no longer responding.
Installer is no longer responding.

Suggest me how to resolve this. This is very Urgent

Re: Repair Got Stuck at Service Dispatcher

Anil_Babu_Samineni — Thu, 08 Feb 2024 08:23:30 GMT

@Rockstar7 When you do repair, Hope you have stopped all the services in all nodes (If it is multi node setup).

For me this sounds like,

- Dispatcher.exe is still running somewhere in the processor (Please force end the process)

- And, there could be few key in your registry for this service, That you need to find out and change the attribute to 0 for time meaning to go ahead silent repair.

Re: Repair Got Stuck at Service Dispatcher

Rockstar7 — Thu, 08 Feb 2024 08:43:32 GMT

@Anil_Babu_Samineni the setup is still running, may force Kill it and start the silent repair? and also suggest me how to identify those keys in the registry

Re: Repair Got Stuck at Service Dispatcher

Anil_Babu_Samineni — Thu, 08 Feb 2024 09:25:50 GMT

@Rockstar7 I assume you have already backup for your Site and repository?

Re: Repair Got Stuck at Service Dispatcher

Rockstar7 — Thu, 08 Feb 2024 09:30:38 GMT

yes i have a backup of those

Re: Repair Got Stuck at Service Dispatcher

Filippo_Nicolussi_P — Wed, 26 Jun 2024 10:03:14 GMT

Hello @Anil_Babu_Samineni

Perhaps you soon solved; would be curios since component mentioned is Dotnet to verify if you have some other version on the System ( https://learn.microsoft.com/en-us/dotnet/core/install/how-to-detect-installed-versions?pivots=os-windows )

that could cause for some reason conflict with the one the installer is trying to repair.