Qlik Community

Ask a Question

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
LINKEDIN LIVE: Democratizing data to enhance customer-centricity. JULY 29TH REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
linushansen
Contributor II
Contributor II

"Unknown Error" appears randomly after switching to Legacy Mode on Qlik Sense Server

Hello!

We have built an application that runs smooth with python scripts on Qlik Sense Desktop, but when we should deploy it on Qlik Sense Server and changed from Standard Mode to Legacy Mode (first with QMC and then change Settings.ini to OverrideScriptSecurity=1 + a blank line) some strange "unknown error" appeared. (and the python scripts didnt runt but qlik didnt see any issues other than "unknown error") We have restarded the qlik sense engine services and all other qlik sense services and also tried to put it back to standard mode, but the "unknown error" still appears, and not only when loading python scripts but when loading regular apps as well. What could this issue be?

Sometimes the data gets loaded and search indexes creates successfully and then the "unknown error" pops up, sometimes the "unknown error" pops up and the data is not able to load. (exact same app) Sometimes the changes in the scripts isnt saving automatically.

When the application is ran in debug mode the "unknown error" does not appear.

 

1 Solution

Accepted Solutions
linushansen
Contributor II
Contributor II
Author

By cleaning out a lot of unnecessary files and setting the Qlik server settings back to original and standard mode the problem disappeared, probably a saving issue and something locked the server on saving

View solution in original post

3 Replies
PadmaPriya
Support
Support

Hello @linushansen 

 

Have you tried this:

"Unknown Error" when creating ODBC connection to Pervasive from Qlik Sense

 

Thanks,

Padma Priya

We are just 'like' you and like to be liked when providing a helpful answer. You may press the 'Solution Accepted' button if an answer provided solves your issue.
linushansen
Contributor II
Contributor II
Author

By cleaning out a lot of unnecessary files and setting the Qlik server settings back to original and standard mode the problem disappeared, probably a saving issue and something locked the server on saving

View solution in original post

linushansen
Contributor II
Contributor II
Author

I dont think it is ODBC-related unfortunately, but now I think the issues are resolved for now