Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QlikView 10 Server Issue

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?

Thanks,

Alex

32 Replies
sicilianif
Creator II
Creator II

I am having a similiar issue. Just now in fact the QVS.exe was consuming all 8 cores at 99%. At that point users are not able open any new documents. From what I can tell in the audit logs, there were no users in at the time and there were no reloads occuring.

Any ideas?

Here is info about our install:

QV v10 R3

Windows 2003 Server

8 cores

64 bit

16GB ram

Thanks,

Frank

StefanBackstrand
Partner - Specialist
Partner - Specialist

QVS will not under any normal circumstances consume 100% CPU if nothing is actively happening on the server, like a reload or distribution or clients making use of documents. Do you have any other integrations, like WebParts or Workbench? API calls?

Also make sure what process is responsible for the CPU usage.

sicilianif
Creator II
Creator II

Stefan,

I went back to the performance logs and found that just before it spiked at 99%, it jumped to 75%. There were 3 users logged in & 2 active sessions.

The next two performance records (10 minutes), the users drop off, there are no active sessions and it spikes to 99%.

Nothing else was happening. No loads or distributions. We have no WebParts, Workbench, or API calls.

When I asked the last active user if he was doing anythig out of the ordinary, he said no.

This is the second time that this has happened this month.

Where else can I look for information on what could have caused this?

Frank

StefanBackstrand
Partner - Specialist
Partner - Specialist

It might be that users, if using stateless clients like Ajax Zfc, make selections that keep the server occupied for a prolonged period of time during the calculation phase, even if their sessions are terminated.

Otherwise, it's just to monitor the session logs, event logs (set verbosity to high/debug) and see what is going on in the server.

As I said before, the server doesn't do large calculations on its own. If you have more issues, I would suggest to register a support case via www.qlik.com.

sicilianif
Creator II
Creator II

We only use the plugin currently so it can't be the Ajax.

I will continue to monitor.

It's just weird. Our average CPU usage, even at our heaviest usage is under 5%, so I can not even begin to guess what would cause it to spike so high for so long.

If it happens again, I will definitely open a case. I was just hoping someone here would have already jumped through the hoops and have the easy answer.

niklas_hedlund
Contributor II
Contributor II

I have a very similar problem. Occasionaly when a user tries to access an app at the access point the memory of QVS.exe goes up to 7 GB and cpu is 100% (normally memory consumtion is about 1 GB and no problem to start application) and the user can never access the application. The whole server crashes and has to be restarted. Shared-files on the access point have to be deleted in order to make the server work again. This started happening when upgrading from QV 9 to QV 10 on the server. Stefan there is a case filed with support on this, 00074044. Recently we have thought the problem might have to do with session recovery functionality and have checked "Prohibit session recovery" in the QEMC. This has kept the server stable for a couple of days now but we are still evaluating it. Anyone has any more info on what causes this problem?

Anonymous
Not applicable
Author

Niklas.hedlund,  Thanks for the advice on deleting the .shared file.  We have been working with one analytic that would not open and never even thought to delete the .shared file.  Now does anyone know how to recover a corrupt .share file?

Our symptoms were very much like yours.  When a users would try and access this document, the memory would gradually grow to the limits of the Server and make the entire system unstable.   The users would get a white screen in the plugin and the application would never load.  A restart of all the services was the only way to fix it.  

Since upgrading to QV 10 SR3, we are restarting the server more frequently.   We just cant seem to determine why!

Thanks,

JS 

StefanBackstrand
Partner - Specialist
Partner - Specialist

Niklas.hedlund & jsomsen: Look at the SharedFileViewer tool in the Power Tools suite that you can find here at the community. Open the file in that tool and look for "red" items (see the bottom right option "Color on top" for sorting). Anything marked erroneous there?

PS. Take a backup/copy of the .shared file and operated on that instead, to not conflict with QVS. DS.

Anonymous
Not applicable
Author

Stefan,

I opened up the corrupted .shared file with the PowerTool and I get nothing marked as erroneous.   Will the Defrag tool help at all?

Thanks,

JS

StefanBackstrand
Partner - Specialist
Partner - Specialist

You never know. If you have a lot or turnaround of creating/deleting objects, it might have grown. You can certainly try it and see if it helps.

Stefan Bäckstrand

Serviceability & Labs Manager, Global Support

Email: Support@qlik.com<mailto:Support@qlik.com>

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

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.