I'm running QV 10 Server 10.00 SR 2. And throughout the day the qvs.exe runs and takes up threads and CPU for no reason. Once I reset the QlikView server service, it goes back to normal. This allows the jobs to finish much quicker as the qvs.exe process is not running. Is there any reason why this is occuring? Right now, I have QlikView Publisher and Server on the same machine. I've seen information where this setup is not advised, but that is how the system was setup when i came to the company. Anybody have any recomendations?
If the QVS.exe process itself is using CPU resources continuously, you have user activity on the server (users qliking around in documents) or you have high amounts of distributions from the distribution service that overloads the QVS.exe process, which will be the receiver of documents when doing server distributions. Either way, it is probably expected behavior and most likely induced by any of these factors. QVS does not use CPU resources out of the blue, at least I've never see it before.
Are you sure that it is not the qvb.exe (note the B) that uses the resources? This is the publisher reload engine, and it will use resources whenever a task is triggered in publisher.
I've attached a screenshot of my issues. Right now, there are no users accessing any qv server documents. The qvb process is running, but it's sharing CPU with QVS even though it should not be running at 50% CPU. When I restart the service it clears, and acts normally. When a user access the server, the CPU spikes and then returns to normal levels. But periodically is stays at 50%. Not sure what would be causing this.
I'm going to stick my neck out and guess that you have only two CPU cores in this machine? Is it virtual?
If no users are using the server, it must be distributions creating the load on QVS. And if the QVS load concurs with publisher tasks, that is running qvbs, it's pretty obvious. Try and disable all tasks in publisher or outside triggered tasks, and see if the overload stops.
Yes and yes. I'm a little confused by what you mean by QVS load? Isn't that the same as publisher tasks. Sorry, just a little confused. I will disable the triggers and see what happens. Thanks for the ideas.
Are you running windows server 2008? If so, restart the QVS.exe, open the task manager, wait for the qvs.exe to spin up to the usage you ate seeing, then right click the process and select Create dump file.. Attach that file here.
So I can't attach it. Its 1.8 GB. Not sure why it is so huge. After I did the dump, it suspended the process and now it cleared. Its running the same threads, just with no CPU now. How what can I do to get the dmp file in a more usable format?
I figured that. The QVS.exe memory footprint represents documents and cache in QVS memory. That's why the size. Mini dumps are only possible with debugging tools, this was just a long shot if you had a small footprint.
Are you on a 32 bit environment?
How man CPU cores does the server have?
Is the server virtual?
Are you using preload on any documents?
If you restarted the QVS.exe process, as I said, and the process went up to 1.8 GB directly, you probably have preload on something.
One of my client has QV v10 SR3 built 10.0.9065 and they have similar issue. Noticed quite a few time qvs.exe using very high CPU. I have never seen that behavior in v9 SR6 which we were running earlier. Couple of occasion Qlikview Server service stopped and restarted automatically (as from even viewer). When that happened, services were showing started in Admin tool as well as in QEMC but couldn’t access document from Access point. After restarting the qvs.exe, it has resolved the issue.
Some of the error event description from event log:
Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type D, detected.
Document Load: The document E:\QLIKVIEW\LIVE\Sales.qvw failed to load for unknown reasons (e=-64) [22