Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Not applicable

APPCRASH qv.exe

Hi all,

I am finding regular APPCRASH events for qv.exe on my server. These all occur on qvd builder reloads.

Several different builders, fail but all eventually run successfully after one or several failures. Also, they do not fail every day. In other words, I cannot find a pattern.

At first I thought it was an out of memory issue but it occurs even when 80 percent ram free.

Typically, the exit codes are: 529697949 and 1073740771

The Event Log text and an appcrash report are below.

Thanks for any thoughts.

EVENT INFO:

Faulting application name: Qv.exe, version: 9.0.7646.9, time stamp: 0x4c9cdfb7

Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0

Exception code: 0xe06d7363

Fault offset: 0x000000000000aa7d

Faulting process id: 0x1b38

Faulting application start time: 0x01cbdbf1cfd64442

Faulting application path: C:\Program Files\QlikViewDesktop\Qv.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 104828e2-47e5-11e0-95a9-0017a477044e

CRASH REPORT INFO:

Version=1

EventType=APPCRASH

EventTime=129438845977674274

ReportType=2

Consent=1

ReportIdentifier=104828e3-47e5-11e0-95a9-0017a477044e

IntegratorReportIdentifier=104828e2-47e5-11e0-95a9-0017a477044e

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=Qv.exe

Sig[1].Name=Application Version

Sig[1].Value=9.0.7646.9

Sig[2].Name=Application Timestamp

Sig[2].Value=4c9cdfb7

Sig[3].Name=Fault Module Name

Sig[3].Value=KERNELBASE.dll

Sig[4].Name=Fault Module Version

Sig[4].Value=6.1.7600.16385

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=4a5bdfe0

Sig[6].Name=Exception Code

Sig[6].Value=e06d7363

Sig[7].Name=Exception Offset

Sig[7].Value=000000000000aa7d

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7600.2.0.0.274.10

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Name=Additional Information 1

DynamicSig[22].Value=5248

DynamicSig[23].Name=Additional Information 2

DynamicSig[23].Value=524829f28589da0dd2b9dd41580f2c11

DynamicSig[24].Name=Additional Information 3

DynamicSig[24].Value=d9eb

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=d9eb82620d6328e35ec6645c2b7ac081

UI[2]=C:\Program Files\QlikViewDesktop\Qv.exe

LoadedModule[0]=C:\Program Files\QlikViewDesktop\Qv.exe

LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll

LoadedModule[2]=C:\Windows\system32\kernel32.dll

LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll

LoadedModule[4]=C:\Windows\system32\USP10.dll

LoadedModule[5]=C:\Windows\system32\msvcrt.dll

LoadedModule[6]=C:\Windows\system32\USER32.dll

LoadedModule[7]=C:\Windows\system32\GDI32.dll

LoadedModule[8]=C:\Windows\system32\LPK.dll

LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7600.16385_none_2b4f45e87195fcc4\gdiplus.dll

LoadedModule[10]=C:\Windows\system32\ole32.dll

LoadedModule[11]=C:\Windows\system32\RPCRT4.dll

LoadedModule[12]=C:\Windows\system32\VERSION.dll

LoadedModule[13]=C:\Windows\system32\PSAPI.DLL

LoadedModule[14]=C:\Windows\system32\COMDLG32.dll

LoadedModule[15]=C:\Windows\system32\SHLWAPI.dll

LoadedModule[16]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6\COMCTL32.dll

LoadedModule[17]=C:\Windows\system32\SHELL32.dll

LoadedModule[18]=C:\Windows\system32\WINSPOOL.DRV

LoadedModule[19]=C:\Windows\system32\ADVAPI32.dll

LoadedModule[20]=C:\Windows\SYSTEM32\sechost.dll

LoadedModule[21]=C:\Windows\system32\oledlg.dll

LoadedModule[22]=C:\Windows\system32\OLEAUT32.dll

LoadedModule[23]=C:\Windows\system32\urlmon.dll

LoadedModule[24]=C:\Windows\system32\CRYPT32.dll

LoadedModule[25]=C:\Windows\system32\MSASN1.dll

LoadedModule[26]=C:\Windows\system32\iertutil.dll

LoadedModule[27]=C:\Windows\system32\WSOCK32.dll

LoadedModule[28]=C:\Windows\system32\WS2_32.dll

LoadedModule[29]=C:\Windows\system32\NSI.dll

LoadedModule[30]=C:\Windows\system32\ODBC32.dll

LoadedModule[31]=C:\Windows\system32\dbghelp.dll

LoadedModule[32]=C:\Windows\system32\WININET.dll

LoadedModule[33]=C:\Windows\system32\Normaliz.dll

LoadedModule[34]=C:\Windows\system32\WINMM.dll

LoadedModule[35]=C:\Windows\system32\IMM32.DLL

LoadedModule[36]=C:\Windows\system32\MSCTF.dll

LoadedModule[37]=C:\Windows\system32\odbcint.dll

LoadedModule[38]=C:\Windows\system32\IPHLPAPI.DLL

LoadedModule[39]=C:\Windows\system32\WINNSI.DLL

LoadedModule[40]=C:\Windows\system32\dhcpcsvc.DLL

LoadedModule[41]=C:\Windows\system32\RICHED20.DLL

LoadedModule[42]=C:\Windows\system32\ntmarta.dll

LoadedModule[43]=C:\Windows\system32\WLDAP32.dll

LoadedModule[44]=C:\Windows\system32\CRYPTBASE.dll

LoadedModule[45]=C:\Windows\system32\UxTheme.dll

LoadedModule[46]=C:\Windows\system32\SXS.DLL

LoadedModule[47]=C:\Windows\system32\CLBCatQ.DLL

LoadedModule[48]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[49]=C:\Windows\system32\rsaenh.dll

LoadedModule[50]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[51]=C:\Windows\system32\wbem\wbemprox.dll

LoadedModule[52]=C:\Windows\system32\wbemcomn.dll

LoadedModule[53]=C:\Windows\system32\wbem\wbemsvc.dll

LoadedModule[54]=C:\Windows\system32\wbem\fastprox.dll

LoadedModule[55]=C:\Windows\system32\NTDSAPI.dll

LoadedModule[56]=C:\Windows\system32\WindowsCodecs.dll

LoadedModule[57]=C:\Windows\system32\apphelp.dll

LoadedModule[58]=C:\Windows\system32\NetworkExplorer.dll

LoadedModule[59]=C:\Windows\system32\PROPSYS.dll

LoadedModule[60]=C:\Windows\system32\MPR.dll

LoadedModule[61]=C:\Windows\System32\drprov.dll

LoadedModule[62]=C:\Windows\System32\WINSTA.dll

LoadedModule[63]=C:\Windows\System32\ntlanman.dll

LoadedModule[64]=C:\Windows\system32\netutils.dll

LoadedModule[65]=C:\Windows\system32\cscapi.dll

LoadedModule[66]=C:\Windows\system32\srvcli.dll

LoadedModule[67]=C:\Windows\system32\profapi.dll

LoadedModule[68]=C:\Windows\system32\SspiCli.dll

LoadedModule[69]=C:\Windows\system32\NETAPI32.dll

LoadedModule[70]=C:\Windows\system32\wkscli.dll

FriendlyEventName=Stopped working

ConsentKey=APPCRASH

AppName=QlikView 9.00 SR6

AppPath=C:\Program Files\QlikViewDesktop\Qv.exe



10 Replies
Employee
Employee

APPCRASH qv.exe

The binary qv.exe is the Developer/Desktop tool, and not part of Qlikview Server, which is why I wonder exactly how you trigger your tasks. And are you using a licensed Publisher?

Not applicable

APPCRASH qv.exe

batch file

Not applicable

APPCRASH qv.exe

i tried to post a more extensive answer but keep getting a "primary filegroup full" error

suniljain
Honored Contributor

APPCRASH qv.exe

Employee
Employee

APPCRASH qv.exe

Sunil; that will probably not be of much help. Smiley Wink

Tod; we need to review the QV document script log files for the time of the crash. Can you post them here? Make sure to get the ones from the time when the issue occurred.

Not applicable

APPCRASH qv.exe

the forum database appears to be back now.

I'll get that info and post it in a few minutes.

we have all the appropriate licenses. I'll be glad to send that to you offline if you wish.

one of the options in the documentation is to use the /r switch in the command line reloads. this is what I am doing with powershell.

i use a database driven routine to control qvd reloads based on data readiness in several source systems. it allows for scheduling of qvds and application reloads based on how early in the day an application is needed in our system.

for instance, if the data for 10 qvd's is ready but only 5 of them are needed for the most important application in Qlikview, the routine will run ensure that all of those are loading before moving on to the other 5.

The app crashes are not good but do not bring the system to a halt. It is not optimal but while I'm investigating this issue, I log that the crash occurs and call the reload again. So far, they always reload after an attempt or two.



Not applicable

APPCRASH qv.exe

when the app crashes, is there a log file generated ?

all of my builders have generate logfile checked but not the date stamp so the subsequent runs would overwrite the original log.

Not applicable

APPCRASH qv.exe

I should have some files tomorrow morning

Not applicable

APPCRASH qv.exe

nothing failed last night..... of course.

I'll post a log as soon as I can catch one

Community Browser