Monitoring Apps 2.0.1 fail on reload - missing fields

[josecardenas]

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

[fosuzuki]

Hi Tyler, thanks for the info.

[korsikov]

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.

[korsikov]

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?

[korsikov]

i fix it.

I had to remove 3 last log files (session, system and perfomance) in folder

Archived Logs\servname\Engine\Trace

[korsikov]

upgrade my server to 2.0.2 and test it!

[korsikov]

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.

[Tyler_Waterfall]

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

[Allardata]

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...

1. Removed all of the log files that both monitors complained about
2. Updated Sense Server to 2.0.2
   After that update, almost all my reload tasks failed with the notification "App is not enabled".
   Unclear what that means during this step; but after finishing it's clearly stated in the (44-page) installation guide.
   Strange to me that only the License Monitor and my LDAP sync tasks succeeded.
   
3. A hint was a yellow indicator in the QMC next to the "Apps" menu button
   Turns out, after close inspection and some random clicking-around...
   Applications have to be Migrated! There's an action button that I can't remember seeing before.
   Probably my fault rushing through the server update and not reading the entire installation guide.
   
4. So I migrated an application, just to see what happens...
   Including the Operations Monitor! Which is kindof strange, but okay.
   That worked! "Successfully migrated selected apps"
   
   The Yellow indicator next to the "Apps" menu item counted down with 1.
   Using the column selector I could select the column "Migration status"
   
   All except one finished within a second.
   That other one is going on for 10 minutes already, let's see what happens there.
5. And now the reload tasks for the migrated apps work!
   
6. Also there are now two new monitor applications added; with the suffix "_1.0.0.0"
   There's even a third License monitor "_2.0.1.0", can't remember if that was already there before the update to 2.0.2
   

End result:

• Server is updated to 2.0.2 SR.
• Monitor apps reload and work, although a lot of history is lost.
• Other apps are migrated (1 still ongoing), reload and are accessible.

[Allardata]

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.

[#11]

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.