Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We use the Windows task scheduler to reload sets of reports (batch files with "QV.exe /r xxx.qvw" statements), which are mostly scheduled to run during the night, and some on a repetitive schedule during the day as well. Usually this works fine, except from time to time reload fails with an error in the event viewer. Qv.exe is then 'stuck' in Windows task manager with no cpu usage and little memory usage. After this, consecutive reloads often (always?) fail as well, leading to a big number of stuck QV.exe instances. To get things running again, I need to kill all these processes in task manager, stop all pending tasks in task scheduler. Usually everything works fine then (at least for a few days).
I can't really pinpoint a specific report that causes the issue or a certain day or time. It all seems quite random and happens every few days. Below I have listed information about the server, about our Qlikview client and server software and the errors as shown in the Windows event viewer. These errors are always the same, except for the start time and process ID.
I do suspect that when the error comes up, it comes up right after or when opening a QVW, so not when reloading is already happening.
I hope someone is able to help is with these tough issues!
Error shown in Windows event viewer:
Faulting application name: Qv.exe, version: 11.20.13206.0, time stamp: 0x56560d0d
Faulting module name: Qv.exe, version: 11.20.13206.0, time stamp: 0x56560d0d
Exception code: 0x40000015
Fault offset: 0x000000000154ea99
Faulting process id: 0x1fd4
Faulting application start time: 0x01d1a96a7d10ea16
Faulting application path: C:\Program Files\QlikView\Qv.exe
Faulting module path: C:\Program Files\QlikView\Qv.exe
Report Id: bb8f45f1-155d-11e6-944c-00155d60e077
Faulting package full name:
Faulting package-relative application ID:
General info:
OS: Windows Server 2012 Datacenter edition (virtualized)
RAM: 118 GB
Disk space: >100GB free
Qlikview client version: 11.20.13206.0 SR13 64-bit Edition (x64)
User running the reload batch: local administrator and memeber of 'Qlikview administrators' on the server)
QVS info:
Server System Info
Operating System Windows Server 2012 Datacenter (64 bit edition)
Operating System Version 6.2.9200
Wow64 mode Not using Wow64
QlikTech Product QlikViewServer 64-bit Edition (x64)
Product Version 11.20.12742.0
Server License Key *************
CPU Target x64
Country 1 United States United States
Language 0409 English (United States) English
Server Collaboration Enabled
Number of CPUs 16
CPU 0 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 1 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 2 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 3 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 4 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 5 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 6 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 7 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 8 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 9 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 10 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 11 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 12 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 13 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 14 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
CPU 15 Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2200MHz
Physical RAM(MB) 120831
VMCommitted(MB) 11093
VMAllocated(MB) 13243
VMFree(MB) 101154
VMLargestFreeBlock(MB) 101154
Local Time 2016-05-10 10:48
GMT Time 2016-05-10 08:48
A variety of reasons can be the cause of this problem. Once a QV Desktop is stuck in memory, it's no use to start others as they will all queue up.
A common cause for a stuck QV Desktop in batch mode is when QV Desktop suddenly asks you what to do with (unsafe) macros. Since batch mode means that QV Desktop is run in a black box without terminal, there is no-one available to make a selection or press a button. The best way to capture that problem is to start the same Desktop reload from the command line once instead of from a batch file.
On the other hand, the event log reports error 0x40000015 which means "Unknown Software Exception". Does the reload generate a document log?
Peter
Thanks for your reply, Peter. When I start the desktop reload from the command line, it seems to work fine. But also usually from the task scheduler it works OK. It seems strange that it would sometimes see unsafe macros, as these QVW's never change. Also when the problem occurs, and I simply restart the scheduled jobs, it works correctly, for a few days.
The document logs show me nothing. There is not even a log created when the issue occurs. So it seems that the qv.exe crashes already when starting or loading the document.
One other odd thing that I found; When I open the client, and immediately close it again (when the splash screen is still showing) this also leads to an appcrash. This happens on the server, but also on my notebook (Windows 7 64 bit). It may or not be related. The problem details of this specific crash (on my notebook):
Problem signature:
Problem Event Name: APPCRASH
Application Name: Qv.exe
Application Version: 11.20.12742.0
Application Timestamp: 54be64a0
Fault Module Name: Qv.exe
Fault Module Version: 11.20.12742.0
Fault Module Timestamp: 54be64a0
Exception Code: c0000005
Exception Offset: 000000000026321a
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: cef0
Additional Information 2: cef07e423c65de8cc0115fb0d62a5538
Additional Information 3: b15f
Additional Information 4: b15f7992202df9cc2bd07d24893aaf4a
Strange... Two different QlikView releases experiencing the same random problem: application crashes.
Have all recent Windows updates been installed on both OS? Did you try reinstalling QV Desktop on your laptop? By preference SR13 (you're running SR10 at the moment).
If it doesn't work or - better - it it doesn't remain stable, don't spend too much time on trying to figure out yourself what is going wrong. Contact your partner or Qlik Support.
Peter
PS. Why are you using Windows Task Scheduler on the server? Special reload schedules and no Publisher?
Hi Thijs,
have you tried the solution presented by Marco Pikiri in the following thread:
Server 2012 R2 data reload problem through Task scheduler
Trying it now for myself as I have the exact same problem.
Kind regards,
Yves
Hello.
Did you manage to resolve your problem?
I ask because I have the same problem, apparently.
Hi Mihai,
one of our hired consultants found the solution.
Appearantly, since/with windows server 2012, scheduled tasks that 'interact' with the screen (show a window in the is case) are no longer allowed. But you can reactivate this.
As I understood what you need to do:
find and download a program called psexec
in de cmd windowd, run following command: psexec -i -s -d cmd.exe
--> this gives the cmd.exe process the privelige of running programs from schedlued task that interact with the screen.
That should do the trick, if i paid enough attention and didn't miss anything.
Regards,
Yves