Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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
Hi Tyler, thanks for the info.
i have procution server on sense 2.0.1
After rebooting the operating system faced the same problem that occurs.
To me it is essential to have information about the system. I'll try to fix it.
But I am outraged that such an important diagnostic tool was not checked.
tnx twa
License montor works
I stopped the service, added to his right ntfs and removed two files
AuditActivity_Engine.txt and QixCounter_Engine.txt
but Operation monitor reload failed with error
Error: Field not found - <ProxyPackageId>
2015-07-18 23:03:18 General Script Error
2015-07-18 23:03:18 Execution Failed
2015-07-18 23:03:18 Execution finished.
What can I fix it?
i fix it.
I had to remove 3 last log files (session, system and perfomance) in folder
Archived Logs\servname\Engine\Trace
upgrade my server to 2.0.2 and test it!
I updated my cluster and again faced with the same problem. I'll be corrected in the same way and I hope that this problem will not arise again.
Very pleased that the update was correctly the first time.
Alexander,
Even with the upgrade you need to remove any bad log files from 2.0.1 or you will continue to get the error. Once the bad files are deleted, you will not experience the issue again.
The next release of the Monitoring Apps will make it so that you do not have to remove bad log files, but this improvement was not part of 2.0.2.
Tyler
Had this issue as well, together with too much errors regarding connection lost with the Sense Engine.
So I started to do everything described in this thread. That took a lot of work and longer than I'd hoped...
End result:
Short update: The ongoing migration for that remaining app failed after about 15-20 minutes. But then restarting the migration succeeded within a second just like the others. Good news: every app successfully migrated to 2.0.2.
We have seen this in house as well but it is a tough problem to reproduce and because of that we have not gotten far with it. I will forward this on to the developers so they can see a field based scenario where it failed as well.