
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Qlik Sense Repository Error
Hi guys
I´ve been trying for quite som time now to get the QMC started but with no success. I get an error message like this:
"Fatal exception. Unable to start the request handling process".....
Attached is the log.
All services are up and running. I first though there was something interfering with the service, for example another web server, but I can´t find anything.
Grateful for ideas.
/M
Accepted Solutions

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks to support, I have found a solution.
The Repository service was unable to listen - on port 4444 - because another service (Good Sync Service) was already listening on that port. Unfortunately, I didn't realise that 4444 was a port to look for as I had been looking for just 4242.
Running a command window with admin privilege and running:
NETSTAT -ab > c:\temp\netstatab.txt
Allows you to see a list of the ports that are in use and the name of the processes that are using them.
Regards,
Stephen

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Marcus,
Send in the issue to support, so we can handle it, man to man 🙂

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Guys,
Was there a resolution to this?
Seeing a similar issue:
13 | 20140929T230347.061+0100 | ERROR | BABEL | System.Repository.Repository.QRSMain | 2468 | d1ea2ce8-bf19-4dda-b779-fe9a2a8ca33e | BABEL\qvservice | Fatal exception | Unable to start the request handling process. | at Qlik.Sense.Common.Communication.Server.HTTPConnectionHandler.Start()↵↓ at Qlik.Sense.Common.Communication.REST.Server.RESTEngine.Activate()↵↓ at Repository.Core.Services.Service.Initialize()↵↓ at Repository.Core.Core.Setup_CentralNode()↵↓ at Repository.Core.Core.Setup()↵↓ at Repository.Core.Core.Inner(ManualResetEvent shutdownRequestedEvent)↵↓ at Repository.QRSMain.<Main>b__6(ICore core)↵↓ at Qlik.Sense.Common.Ioc.WorkScope.Work | d1ea2ce8-bf19-4dda-b779-fe9a2a8ca33e |
Wouldn't be the "cleanest" of systems (various versions of QlikView have been installed in the past), but the account is a local administrator so shouldn't have a problem?
Regards,
Stephen

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would suggest to open a Case with Support so we can have a closer look at it. There was no response from the Thread opener or Case.
.png)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I agree with Daniel on opening a Support case, but you can try this -
One thing you can try is going to the Services MMC -> Qlik Sense Repository Database -> Right click / Properties -> Log On tab - and try checking the Allow service to interact with the desktop - Apply / Ok and restart the services.
Though, if you have a valid Sense Server license you can open a case with Qlik Support.
Please mark the appropriate replies as helpful / correct so our team and other members know that your question(s) has been answered to your satisfaction.
Pierce

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Make sure the repository is running under local system and not a service account.

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks but unfortunately that hasn't made any difference.
I'm going to open a support request.
Stephen

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is running as the Local System.

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks to support, I have found a solution.
The Repository service was unable to listen - on port 4444 - because another service (Good Sync Service) was already listening on that port. Unfortunately, I didn't realise that 4444 was a port to look for as I had been looking for just 4242.
Running a command window with admin privilege and running:
NETSTAT -ab > c:\temp\netstatab.txt
Allows you to see a list of the ports that are in use and the name of the processes that are using them.
Regards,
Stephen
.png)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Stephen,
Thank you very much for sharing with this with us.
Pierce
