“The Qlikview web server service on Local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.”
When you are trying to start the Qlikview webserver if above error message is displayed, that means there are some other service run on the port (normally 80) that Qlikview webserver trying to acquire. The running application on that port can be another server like IIS, Browser Application, Facebook, Skype, Ammyy, Teamviewer, etc. . In the qlikview server while using http:// the port will be 80 and for https:// the port is 443. But in IP it’s showing 4750 or something as the port and it is the internal port of using for QV server and it’s not the port that webserver is accessing. Webserver is always accessing 80 or 443 according to the protocol.
We need to stop whatever the services running on the port and start the qlikview Webserver service. To do that, follow the steps given below.
1. Check what are running services on that port. Use netstat –aon | findstr [port no] command in command prompt. -aDisplays all active connections and the TCP and UDP ports on which the computer is listening. -oDisplays active TCP connections and includes the process ID (PID) for each connection. -n Displays active TCP connections, however, addresses and port numbers are expressed numerically and no attempt is made to determine names.
2. Get the Process ID of the services running on that port (Process ID will be displayed in the column to the right).
3. Open the Task Manager and go to Processes and end the Processes which is carrying PIDs those using that port.
4. Restart the service and enjoy qlikview.
When you are opening the services using above cmd command, there will be two default services running on that port. Those can be IIS, TCP/IP. And you cannot find those in task manger too.
Actually what happening is when you start qlikview webserver service, from there on wards qlikview application is not going to function. But an application like skype or other is always using that port since it got started. So what the system doing is start the service and check running threads on that service, if not found then switch to the previous service running on that port. So ultimately service get started and stopped within no time.