"The app you have specified could not be found
" error message is seen when attempting to open an App from the hub.
Number 3 above correlates to bug QLIK-73792.
During start of the services the engine picks a default Apps folder instead of the shared location. This happens if the engine service starts before the repository is ready.
This issue was resolved in the June release and forward.
Depending on the source of the problem will determine the resolution, some of the reasons and solutions are below.
An issue is resolved in the June 2017 release and forward, but other causes are also possible ... 1-(Sync Persistence) The (default) in engine configuration for the App Storage directory does not match the expected location.
-> http://help.qlik.com/en-US/sense/3.2/Subsystems/ManagementConsole/Content/edit-engine.htm 2-(Shared Persistence) Shared folder is not configured properly.
-> http://help.qlik.com/en-US/sense/3.2/Subsystems/PlanningQlikSenseDeployments/Content/Server/Server-Deployment-Scenarios-Multi-Node-Site_SP.htm 3- (Shared Persistence) If the Shared folder is on a RIM, after a restart, the apps become inaccessible on a previously working environment.
-> do the following on the node the hub is pointing to.
-> - Go to "services", navigate to the 'Qlik' services.
- Stop the Database repository service, stop the dispatcher service after all remaining services have stopped.
- Start the repository service ( the repository should also start), start the dispatcher service, stall all remaining Qlik services. 4- (Shared Persistence) DFS not configured properly (a DFS is an optional fileshare structure)
-> - Check the DFS sharefolder access from each node, ensure that each node can access ALL folders in the share.
- If there is a RIM that can't access or has partial access (only some folders in the QlikShare are visible) contact the client infrastructure team to fix. 5- Qlik Sense Engine service is "Suspended":
-> Go to "Services" and attempt to stop/restart the Qlik Sense Engine service.
-> If the service stop control fails due to timeout, check...
-> Task Manager (processes or details tab) and look for Engine.exe. If there is a subprocess in "Suspended" mode holding RAM, end the process
-> Back in Services, properly stop Qlik Sense Engine and start it again 6- Troubleshooting - is the problem intermittent?
-> Check the Virtual proxy and see what engine nodes are being used for load balancing.
-> Go to the service cluster and copy the location of the shared folder.
i.e. \\Server\ShareFolder\Apps <-- copy this to clipboard
-> RDP to each engine node, open file explorer and paste the share folder location in, hit <enter>.
*if it doesn't do anything right away, wait, it may take a few moments to time out. If it times out then this is the problem.
*if it finds the files, move to the next engine RIM testing to find one not working.
NOTE: you can't load balance to an engine node that doesn't have access to the Apps folder in the Shared location.