Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
gdevarashettyhf
Contributor III
Contributor III

Qliksense 3.0 Install and Configuration

Hello Folks,

I just installed QS 3.0 from the exe. Not able to open QMC - https://SVR.DOMAIN.COM/qmc/  - get 404 page not found. To be honest, I am sure its not as simple install. If anyone can guide any quick install steps, would be greatly appreciated.

Server: 2008 R2 Enterprise

Only thing I see is - Qliksense services show as started but with Delayed Start option - that may not be an issue. And I got Nprinting 17 installed on this machine.

Any ideas, THANKS ALOT IN ADVANCE.

Ganesh

1 Solution

Accepted Solutions
korsikov
Partner - Specialist III
Partner - Specialist III

Perhaps what the application uses port 443. Check using the command netstat -a -b or  tcpview sysintrnal utility

View solution in original post

4 Replies
gdevarashettyhf
Contributor III
Contributor III
Author

ALSO ADDED - WIndows Application Log has this warning message if it helps:

The description for Event ID 300 from source Qlik Sense Service Dispatcher cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

 

If the event originated on another computer, the display information had to be saved with the event.

 

The following information was included with the event:

 

Unexpected termination (0) for process 0

Facility = Data Preparation

ExePath = Node\node.exe

Script = ..\DataServices\src\service.js

rittermd
Master
Master

By default the services show as Delayed.  That is not your issue.

Is this a new install or an upgrade?

I just went through an upgrade and had no problems.

korsikov
Partner - Specialist III
Partner - Specialist III

Perhaps what the application uses port 443. Check using the command netstat -a -b or  tcpview sysintrnal utility

gdevarashettyhf
Contributor III
Contributor III
Author

Yes, we resolved it and that was the issue. Port 443 was getting used by VM..


Looks to be working. 


Thank you for your reply.