Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
josecardenas
Contributor III
Contributor III

Monitoring Apps 2.0.1 fail on reload - missing fields

Hi Tyler

I've updated qlik sense to 2.0.1 and I've found an error reloading license and operations monitor

On License monitor I'm getting field not found - <CounterName>

On operations monitor I'm getting Field not found - <ProxySessionId>

Please check the scripts logs downloaded

Thanks

Jose

26 Replies
janvlasveld
Partner - Contributor II
Partner - Contributor II

Hi Tyler,

I used the Set errormode = 0  and it worked.

thxs,

Jan

osse_aam
Contributor II
Contributor II

We have run into the same issue with our Qlik Sense installation. Both of the monitoring applications' tasks failed to complete and the task logs identified various log files as the issue. It may be helpful for others or Tyler to know that we started off with 1.0.0 but made in place updates from 1.0.0 to 1.1.0, then 2.0.0 and finally 2.0.2. After upgrading to the latest version we removed the following set of log files and we were able to successfully run the reload tasks:

  • All content in C:\ProgramData\Qlik\Sense\Log\Engine
  • ArchivedLogs\Engine\Audit\OSSESSRSPRD01_AuditActivity_Engine
  • ArchivedLogs\Engine\Audit\OSSESSRSPRD01_QixCounter_Engine
  • ArchivedLogs\Engine\System\OSSESSRSPRD01_Service_Engine
  • ArchivedLogs\Engine\Trace\OSSESSRSPRD01_Performance_Engine
  • ArchivedLogs\Engine\Trace\OSSESSRSPRD01_Session_Engine
Tyler_Waterfall
Employee
Employee

Thanks for the post Aaditya.

We have found similar results in house and have a fix for this upgrade-specific issue.

The root problem here is that some services were writing a log file improperly when restarted (fixed with 2.0.2). Even if you upgraded to 2.0.2, those old, bad logs were left behind and would cause problems.  With the next release of the Monitoring Apps, the apps won't fail to reload when they encounter these bad logs.

Not applicable

I am having the same problem and have contacted rep for what version to go up to. my question is how do I know the logs are bad without going through every single one of them?  Should I just remove them all?  We have only been working with QlikSense for a month.

Tyler_Waterfall
Employee
Employee

Cathy - you are running 2.0.1?

If so, can you upgrade to 2.0.5 or 2.1?

Not applicable

We are on 2.0.1

My rep is going to have a tech specialist get on our system tomorrow to make sure everything is setup and look at the logs. I think we need to do the upgrade

Cathy Swanberg

System Analyst

PH: 253.375.0707

FX: 253.375.0807

www.NorthwestDoor.com<http://www.NorthwestDoor.com>

Tyler_Waterfall
Employee
Employee

Yes, concerning the Operations Monitor failing on the missing fields - this was addressed in 2.1.

Tyler