Problem
Environment:
Citrix XenDesktop Version: 5.6
Citrix XenDesktop VDA Agent Version: 5.6.300
Adobe Flash Player Version on VDI: 12.0.0.77
Adobe Flash Player Version on VDI: 12.0.0.77
Internet Explorer Version: 9.0.8112.16421
You’ve recently updated the Adobe Flash Player on the Citrix XenDesktop 5.6 VDI and HP Thin client t610 from 11.7.xxx.xxx to 12.0.0.77 and noticed that as soon as you use Internet Explorer 9 to browse a page with an embedded Adobe Flash video:
Internet Explorer has stopped working
A problem caused the program to stop working correctly. Please close the program.
Close the program
The following error is logged in the Application log of the VDI:
Log Name: Application
Source: Application Error
Event ID: 1000
Level: Error
Faulting application name: iexplore.exe, version: 9.0.8112.16533, time stamp: 0x52f1fb14
Faulting module name: PseudoServerInproc2.dll, version: 6.3.300.17, time stamp: 0x51bb6818
Exception code: 0x4000001f
Fault offset: 0x0010987f
Faulting process id: 0x530
Faulting application start time: 0x01cf481e433dff05
Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Faulting module path: C:\Program Files\Citrix\ICAService\PseudoServerInproc2.dll
Report Id: 86127455-b411-11e3-804a-0050569116f7
Solution
Option #1:
A search on the internet brought me to the following forum post:
… where users indicated that reverting back to 11.7.700.169 corrected the problem so I went ahead and tried reverting back to 11.7.700.272 as shown in the following screenshots:
http://get.adobe.com/flashplayer/
**Note that it is important to run the uninstall executable first or you’ll receive the following error:
The installation encountered errors:
The version of Adobe Flash Player that you are trying to install is not the most current version. Please visit the Player Download Center to obtain the latest, most secure version.
Reverting the Adobe Flash Player to an earlier version stopped Internet Explorer from crashing:
Option #2:
Not being satisfied with reverting to an earlier version, I decided to test upgrading the 5.6.300 VDA agent to the latest 5.6.400 version:
… and noticed that this also fixed the issue.
No comments:
Post a Comment