Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Not applicable
‎2012-10-17 10:26 PM

error message on loading document in QV Access Point using IE Plug-in

Hi,

I have a little problem with my customer, they having a problem when open document in Access Point using IE Plugin.

It is not always shown but sometimes, so they complaint about it.

The error message says :

"qvp://bi.fb.co.id/fastrata/fb.qvw?iis_authenticate=B5FE3EBE101B0AF40253A1C55A3933274A700F62&tunneler=http%3A//bi.fb.co.id/scripts/QVSTunnel.dll%3Fhost%3Dqvprod could not be opened"

I send the attachment as refference.

Regards,

Effendi

Preview file
215 KB
868 Views
0 Likes
2 Replies
Bill_Britt
Former Employee
Former Employee
‎2012-10-18 09:15 AM

Effendi,

This normally means that port 4747 is not open between the user and the QVS server. It also means that tunneling is not enabled on the server which will tunnel the traffic over port 80 if 4747 is blocked.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
388 Views
0 Likes
Not applicable
‎2015-01-09 04:42 PM
Author

I was able to solve this problem in IE 11 by disabling Protected Mode in the zone in which the QlikView web page ran under.


For me the problem would not happen all the time, only when I had been logged into windows for a while.  Logging out and logging back in would clear up the problem in the short term, but not long.  Not sure why logging out of windows and logging back in had any affect but the fix above solved the problem long term.

388 Views
0 Likes