I am using App Volumes 2.12.0.70 and Java 8u121 doesn't seem to work properly. Webstart (javaws.exe) applications don't launch properly when deployed via an appstack. If I use an older version of java i.e. java 8u101 it works fine. Has anyone else seen this issue? Know a fix for it?
I have not heard or aware of this Java issue in 2.12.
Could you please check and confirm if the application works outside of the AppStack please. Just to double check if this is an App Volumes issue or with the native application.
If I run a VM and install Java 8u121 locally I can run the webstart applications just fine. If I then revert snapshot and attach the appstack with 8u121 I cannot run the webstart applications. If I then remove the appstack with 8u121 and attach an appstack with 8u101 the applications launch fine. If you have anything else you would like me to try let me know.
It looks like a bug in 2.12 version. Please file a support request with VMware to troubleshoot this issue.
I am experiencing this issue with AppVolumes 2.11 as well.
I am having the same issue with App Volumes 2.12.1. Anyone find a workaround?
I'd suggest testing 2.13, but just update the agent to see if it does the trick.
I've seen this in 2.10 as well, so low priority I haven't looked into it yet for us.
Hi,
This should work with App Volumes 2.13.x, please give this a try.
Raymond
Hi Shapplle,
Small question, how many java versions you are installing or using? [for example are you using Java 6 and Java 8?]
Regards,
Vkmr.
Hi Tbro,
what is your Java_Home path and version it was pointing?
Regards,
Vkmr.
Hi Vkmr,
We have Java 8 u151. Java Home_Path is C:\Program Files (x86)\Java\jre1.8.0_151. Only using 1 version of Java.
We have one version of Java. Installing the 2.13 agent seems to have fixed the issue. But just to be clear any version of Java equal to or later than 8u121 has the issue if you are using App Volumes agent 2.11, 2.12, or 2.12.1 and maybe more. I haven't used App Volumes 2.10 so I can't say about that.
Only one version. I created a test 8u101 appstack and layered it on top, then modified deployment.properties to use that one, and JNLP worked fine.
This was on 2.11
Now, I have a new environment with 2.13, and I can't even install Java! I see a WerFault.exe in process explorer as java installer is called, then it all dies. Windows Error Reporting is OFF.
Anyone else seeing this issue with 2.13 not even able to run java install? Silverlight also failed. I had to remove SEP to get Chrome to work due to known GEM issue.
what else is running on your Appvol 2.13 provisioning machine? I can't get Java installs to run at all.
I have the appvolumes 2.13 agent running on the appvolumes provisioning desktop and Microsoft Office 2016. That is all. Are you using the new 2.13 templates?
I am using the new templates. Having the issue with Win7. Had an issue with Chrome installing but that was due to Symantec's GEM tool. However, Java installer just attempts to launch and dies.
I have always tried to have a provisioning machine that closely matches my production master image (sans Horizon agent). I may have to start with a fresh win7 vm and see what happens.
error log shows this (for any java exe I try):
Version=1
EventType=APPCRASH
EventTime=131544703965912794
ReportType=2
Consent=1
UploadTime=131544703966224848
ReportIdentifier=559e4565-c329-11e7-a115-00090faa0001
IntegratorReportIdentifier=559e4564-c329-11e7-a115-00090faa0001
WOW64=1
Response.BucketId=1680277864
Response.BucketTable=25
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=jre-8u144-windows-i586.exe
Sig[1].Name=Application Version
Sig[1].Value=8.0.1440.1
Sig[2].Name=Application Timestamp
Sig[2].Value=5972eb57
Sig[3].Name=Fault Module Name
Sig[3].Value=jre-8u144-windows-i586.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=8.0.1440.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5972eb57
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00036ca1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Users\ADMINI~1\AppData\Local\Temp\jds2083736.tmp\jre-8u144-windows-i586.exe
UI[3]=Java Platform SE binary 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[0]=C:\Users\ADMINI~1\AppData\Local\Temp\jds2083736.tmp\jre-8u144-windows-i586.exe
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\ADVAPI32.dll
LoadedModule[5]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[6]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[7]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[8]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[9]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[10]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.23403_none_2b180b30457f196c\COMCTL32.dll
LoadedModule[11]=C:\Windows\syswow64\GDI32.dll
LoadedModule[12]=C:\Windows\syswow64\USER32.dll
LoadedModule[13]=C:\Windows\syswow64\LPK.dll
LoadedModule[14]=C:\Windows\syswow64\USP10.dll
LoadedModule[15]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[16]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[17]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[18]=C:\Windows\system32\msi.dll
LoadedModule[19]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[20]=C:\Windows\syswow64\ole32.dll
LoadedModule[21]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[22]=C:\Windows\system32\VERSION.dll
LoadedModule[23]=C:\Windows\syswow64\WININET.dll
LoadedModule[24]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[25]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[26]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[27]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[28]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[29]=C:\Windows\syswow64\iertutil.dll
LoadedModule[30]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[31]=C:\Windows\syswow64\USERENV.dll
LoadedModule[32]=C:\Windows\syswow64\profapi.dll
LoadedModule[33]=C:\Windows\system32\IMM32.DLL
LoadedModule[34]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[35]=C:\Windows\system32\apphelp.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=1680277864/nBucketTable=25/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Java Platform SE binary
AppPath=C:\Users\ADMINI~1\AppData\Local\Temp\jds2083736.tmp\jre-8u144-windows-i586.exe
If you are using one universal version of Java please consider moving Java to parent image if you are not planning to do App vol update
I use Java 8 U111 with no issue on parent image
Hi,
thanks for information, if you are using one version of Java, please move it to parent image if your team is good with this idea.
Regards,
Vkmr.