topic Error 1067 in QlikView

Error 1067

vsharma1 — Mon, 26 Jan 2026 18:19:17 GMT

Hi,

I am getting below error while restarting qlikview web services

error 1067 windows could not start the qlikview web services on local computer

All qlikview services are installed on single machine

Similar error is getting for QMS and QDS

Windows Server 2016

Re: Error 1067

vsharma1 — Sat, 11 Jan 2020 02:42:20 GMT

I had installed Qlikview server with admin credentials

I have added FID user to Qlik Admin group and changed the user in all services but I am still getting same error

Re: Error 1067

Sonja_Bauernfeind — Mon, 13 Jan 2020 08:37:29 GMT

What errors are printed in the Windows application and System logs when the services fail to start?

I'd recommend reviewing our article database for possible root causes, beginning with https://support.qlik.com/articles/000003049

Re: Error 1067

vsharma1 — Tue, 14 Jan 2020 16:10:41 GMT

Hi,

All services are running fine now except Qlikview Webserver.

I checked the Application log and Server Log

Application Log:

Faulting application name: QVWebServer.exe, version: 12.40.20000.0, time stamp: 0x5cc3a37d
Faulting module name: KERNELBASE.dll, version: 10.0.14393.3383, time stamp: 0x5ddcba29
Exception code: 0xe0434352
Fault offset: 0x0000000000034c48
Faulting process id: 0x2324
Faulting application start time: 0x01d5caf46c853e14
Faulting application path: C:\Program Files\QlikView\Server\Web Server\QVWebServer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: d95c2eee-bfcd-4720-8cc6-d9f36b46d965
Faulting package full name:
Faulting package-relative application ID:

Server Log:

The QlikView Webserver service terminated unexpectedly. It has done this 2 time(s).

Re: Error 1067

vsharma1 — Fri, 17 Jan 2020 00:37:10 GMT

I have resolved this by changing the port number

Re: Error 1067

Brett_Bleess — Mon, 10 Feb 2020 22:09:51 GMT

Yeah, you like have an HP utility running on the web server, as that is a common one of which I am aware that shares TCP port 4750. Good catch on things and thanks for posting the final fix, I will mark that as the solution.

An easy way to find this is to run 'netstat -ano' from a CMD dialog on the server in question and go see what the PID is on TCP 4750, if it is not 4, but some other number, then use Windows Task Manager and the Processes tab with the PID column turned on to figure out which service has the port in use, so you know which one you want to try to change...

Here is an Article link on how to change the port too: Change QVWS port

Regards,
Brett