VMware Horizon Community
jasonngteck
Contributor
Contributor

Kernelbase.dll error

We are using VMware View to assign our ThinApp applications. I have an applicaiton package that is working in with our 32-bit and 64-bit staging workstations. But once I assign the application to my test pool, I am getting an AppCrash when trying to launch the application. This is a custom application. Looks like the cause of the crash is kernelbase.dll according to the crash report. I am not sure why it is doing this and am a bit stuck on how to get this resolved. Here's the crash report. Anyone came across any similar errors?? Thanks.


Version=1

EventType=APPCRASH
EventTime=130051802017698084
ReportType=2
Consent=1
UploadTime=130051802633033076
ReportIdentifier=0263c8aa-7560-11e2-a820-005056b23387
Response.BucketId=3410756237
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Daxti.Kiosk.exe
Sig[1].Name=Application Version
Sig[1].Value=2.0.0.86
Sig[2].Name=Application Timestamp
Sig[2].Value=4f6b673d
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.17651
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4e211319
Sig[6].Name=Exception Code
Sig[6].Value=e0434f4d
Sig[7].Name=Exception Offset
Sig[7].Value=0000b9bc
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files (x86)\Daxti\Bin\Daxti.Kiosk.exe
UI[3]=Daxti.Kiosk has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\system32\IMM32.DLL
LoadedModule[15]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[16]=C:\Windows\SysWOW64\vmwsci.dll
LoadedModule[17]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[18]=C:\Windows\syswow64\oleaut32.dll
LoadedModule[19]=C:\Windows\syswow64\ole32.dll
LoadedModule[20]=C:\Windows\system32\secur32.dll
LoadedModule[21]=C:\Windows\system32\mscoree.dll
LoadedModule[22]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[23]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[24]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCR80.dll
LoadedModule[25]=C:\Windows\syswow64\shell32.dll
LoadedModule[26]=C:\Windows\system32\profapi.dll
LoadedModule[27]=C:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll
LoadedModule[28]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[29]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[30]=C:\Windows\system32\rsaenh.dll
LoadedModule[31]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[32]=C:\Windows\system32\VERSION.dll
LoadedModule[33]=C:\Windows\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
LoadedModule[34]=C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll
LoadedModule[35]=C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll
LoadedModule[36]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\diasymreader.dll
LoadedModule[37]=C:\Windows\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll
LoadedModule[38]=C:\Windows\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll
LoadedModule[39]=C:\Windows\system32\apphelp.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-884211059/nBucketTable=1/nResponse=1/n
FriendlyEventName=APPCRASH
ConsentKey=APPCRASH
AppName=Daxti.Kiosk
AppPath=C:\Program Files (x86)\Daxti\Bin\Daxti.Kiosk.exe
ReportDescription=Stopped working
0 Kudos
2 Replies
oliAH
Enthusiast
Enthusiast

I'm assuming you made a pool of linked-clones so isn't this related to the configuration of your golden image? What applications or frameworks are installed on your 'staging workstation' that are not installed in the virtual machines of your test pool? In short, the difference.

Did you really use a vanilla XP to capture your app?

Blog: http://oliah.net >> Twitter: @olivier_ahson
jasonngteck
Contributor
Contributor

Ok I've resolved the issue. Turns out the custom application requires .NET framework 3.5+ and the pool is running 2.0 only. The applicaiton is now working once I got the .NET Framework sorted out.

0 Kudos