Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
Not applicable

QlikView 11 and IIS 7, QlikView Webserver won't start

After installing QlikView 11 (actually upgrading an existing version 10, which is uninstalled during the installation of version 11) the QlikView Webserver service won't start, which probably causes the Access Point to be loading content forever.

Logging from the Event Viewer: 

Service cannot be started. System.ServiceModel.AddressAlreadyInUseException: HTTP could not register URL http://+:4750/QVWS/Service/. Another application has already registered this URL with HTTP.SYS. ---> System.Net.HttpListenerException: Failed to listen on prefix 'http://+:4750/QVWS/Service/' because it conflicts with an existing registration on the machine.

Any suggestions how to solve this issue? Looks like version 10 was not removed correctly/entirely? Thanks in advance for your support.

1 Solution

Accepted Solutions
Highlighted
Not applicable

QlikView 11 and IIS 7, QlikView Webserver won't start

The Webserver service was not properly removed by uninstalling version 10 by means of the QlikView installer of version 11. So we uninstalled the fresh install of version 11 and manually removed all the c:\ProgramData\QlikTech folders. And installed version 11 again.

Next to that we installed windows authentication in IIS and now both issues (QV Webserver and Acces Point loading content forever) were solved.

1 Reply
Highlighted
Not applicable

QlikView 11 and IIS 7, QlikView Webserver won't start

The Webserver service was not properly removed by uninstalling version 10 by means of the QlikView installer of version 11. So we uninstalled the fresh install of version 11 and manually removed all the c:\ProgramData\QlikTech folders. And installed version 11 again.

Next to that we installed windows authentication in IIS and now both issues (QV Webserver and Acces Point loading content forever) were solved.

Community Browser