QVX_UNEXPECTED_END_OF_DATA

[zbeauchemin]

Unable to reload License Monitor & Operations Monitor. Ram is at 87% percent usage with just the QMC open & no data loads or other people logged into the QlikSense environment. Is this normal? Server was 25GB of Ram installed. 379GB of storage installed with 335GB available.

Any ideas? Is it Ram related. Engine.exe is taking up all of the ram.

[rubenmarin]

Hi Zachary, Ram use can be normal if the server has been running for some days, the server is configured to use ram until it reaches the % defined in qmc, wich usually is set to 70%-90%, each selection is stored in cache to make next queries faster.

This video can help to understand: QlikView Memory Management

When is this error shown? reading a qvd? how big is that qvd? reading in an empty app also gives the error?..

[zbeauchemin]

This only happens when running a reload on the license monitor or operations monitor apps. Isn't reading a QVD and we don't get the error when reloading other apps.

[rubenmarin]

In case of monitoring apps it can be differenct issues, mainly because of the rest connector, it can be beacuse of a differnt port used to access Sense or the password saved in the rest data connection has changed, chek this:

https://help.qlik.com/en-US/sense/June2018/Subsystems/Monitoring/Content/Troubleshooting/troubleshoo...

(under Message: "Error: QVX_UNEXPECTED_END_OF_DATA..." title)

In qmc->Data connections, try resetting the password of rest connector and/or setting the correct port in Rest connector.

Another possibility is that you are using monitoring apps for an older version of Sense, not the current version. Usually there is a copy of the apps in ProgramData\Qlik\Sense\Repository\DefaultApps\.

[zbeauchemin]

Definitely not a old version of the monitoring apps. Double checked the connection strings are they look to be fine and include appropriate ports. tried the http and https variations. Reloads are still failing with the same log error. Any ideas?

[zbeauchemin · Accepted solution]

Resolved! double checked existing monitor app connection strings then reentered username and password for account used to start services in each of those connections. Don't forget to use machinename\service account