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

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Error message on QlikView server

We are using QlikView Server Small Business Edition in our Organization.

Recently we are getting a peculiar error message on our server. Whenever we try to open a .QVW file, by clicking on it, we get an alert box with the following error message: "Provider type does not match registered value". However, when we click the close the alert box, the file opens successfully.

Due to this error, automatic reloads are not working. When I logged in to the server, I saw that the script had run at the scheduled time, but the execution could not complete because of this error.

We are using this server since October, 2010. Initially we had installed QlikView version 9, then in February, 2011 we upgraded it to version 10. Since then, we have not faced any problem. This issue started coming after 15th Dec, 2011.

Please suggest.

Thanks!!

3 Replies
g_f_bakker
Partner - Contributor
Partner - Contributor

Hello, I have the same error message.

When I open any document for the first time I started QlikView, the error message comes up twice.

First it occurred in QlikView Desktop 10 and after a full reinstall of QlikView Desktop 11 it is still there.

Can anyone help me?

Not applicable
Author

Hi,

Did anybody get the solution of the above problem, as I am facing the same issue.

I changed the Admin password and restarted the server, after that the automatic reloads started but still in running status and not getting executed.

And the same pop up message comes while opening the qlikview documents 'Provider type does not match registered value'.

Any help will be appreciated.

Thanks.

Not applicable
Author

Could this be an IIS issue ?

I'm not entirely convinced it's qlikview - I had this once when I was running scripts of an app reload schedule...as soon as I disabled the script, the error went away.


Sorry, not much help !