Hub cannot be opened "The page cannot be displayed" System.Net.HttpListenerException (0x80004005)
Article Number: 000042768 | Last Modified: 2018/09/13
Description
Qlik Sense hub fails to open with the error "The page cannot be displayed". This happened after a fresh install. Repository logs show following exception:
Unhandled exception: System.Net.HttpListenerException (0x80004005): The process cannot access the file because it is being used by another process↵↓ at System.Net.HttpListener.AddAllPrefixes()↵↓ at System.Net.HttpListener.Start()↵↓ at Qlik.Sense.Common.Communication.Server.HTTPConnectionHandler.Start()↵↓ at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)↵↓ at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)↵↓ at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()↵↓ at System.Threading.ThreadPoolWorkQueue.Dispatch()
Cause
This issue occurs if port 42xx is being used by some other process.
Note: Qlik Sense Proxy Service (QPS) uses following ports starting with 42* hence they must not be used by other processes. 4248 = Http windows authentication 4244 = Https windows authentication 4243 = QPS API
Qlik Sense Repository Service uses following ports starting with 42* hence they must not be used by other processes. Also check port 4444 is not being used by another process.
Resolution
Open an elevated command prompt and run the following command to find out other process which might be using the ports mentioned above.
netstat -ano | findstr 42
Eliminate such processes so that ports required for Qlik Sense are available to use.
Get Answers
Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.