Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Virtualizing Adobe Products: Acrobat X, CS5, Adobe Drive 2

Created: 25 Jul 2013 • Updated: 25 Jul 2013 | 2 comments

I'm wondering if anyone, here, has had any luck with virtualizing Acrobat 10, Adobe CS5 Design Premium, or Adobe Drive 2.  I have created SWS packages for these products, which work when I import and activate the layers on a Windows 7 machine, using SWV Admin.  However, when I stream the applications using the SWS Agent, I am seeing the following behavior.

Logged-in as a Domain Admin, the applications launch, initially, but if they are closed and then re-launched they will crash with these errors:
Acrobat=Fatal Error – "Acrobat failed to load its core dll."  
Faulting application name: Acrobat.exe, version:, time stamp: 0x518c95a8
Faulting module name: amtservices.dll, version:, time stamp: 0x4c91fecd
Exception code: 0xc0000005
Fault offset: 0x00016408
Faulting process id: 0x1110
Faulting application start time: 0x01ce887f5d13d767
Faulting application path: C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\Acrobat.exe
Faulting module path: C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\amtservices.dll
Report Id: a5e672e7-f472-11e2-8120-005056ab252c

Adobe CS5 =
Faulting application name: Photoshop.exe, version:, time stamp: 0x4d9d8f8e
Faulting module name: AdobeSWFL.dll, version:, time stamp: 0x4c6f29ff
Exception code: 0xc0000005
Fault offset: 0x00000000001097aa
Faulting process id: 0x1098
Faulting application start time: 0x01ce887f2031b0b7
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CS5 (64 Bit)\Photoshop.exe
Faulting module path: C:\Program Files\Common Files\Adobe\APE\3.1\AdobeSWFL.dll
Report Id: 8df48917-f472-11e2-8120-005056ab252c

If I login as a Standard Domain User, the application will launch, then crash after about 30 seconds with the following errors:

Acrobat = "A problem has occurred with the licensing of this product.  Restart your computer and re-launch the product. Error: 213:19"
Faulting application name: Acrobat.exe, version:, time stamp: 0x518c95a8
Faulting module name: Acrobat.dll, version:, time stamp: 0x518ca2aa
Exception code: 0xc0000005
Fault offset: 0x002ddd37
Faulting process id: 0x10f0
Faulting application start time: 0x01ce88825f6c4545
Faulting application path: C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\Acrobat.exe
Faulting module path: C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\Acrobat.dll
Report Id: e9127447-f475-11e2-9088-005056ab6af2

Adobe CS5 = "Adobe CS5 has stopped working"

For the Adobe Drive 2 issue, it may be network-related, but the application streams and launches, it just does not connect to our Version Cue server. "The server could not be connected."  

I'm using Symantec Virtual Composer, Version 6.1 SP8, to create the packages and am using Windows 7 x64 for both the packaging machine as well as the VM's in our VDI environment.  The Workspace streaming agent is version  If anyone has any ideas to remedy this or has had similar experience, I would be very grateful for your comments and suggestions!  Thank you!

Operating Systems:

Comments 2 CommentsJump to latest comment

EdT's picture

Are you using single licenses for the Adobe apps or do you have a site license? Adobe, like other vendors, now lock their installs to the specific hardware they are installed on when the activation takes place, and as soon as you deploy to a different machine (eg different bios serial number or different MAC address), then it will cause the license to be invalid.

Another thing that I am seeing increasingly with the Adobe apps, is the release of separate installers for 32 bit and 64 bit operating systems, and a 32 bit install is not going to work properly on a 64 bit operating system as this is the way Adobe have coded the apps.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

michael cole's picture

If you can import that layer to multiple hardware then perhaps look at the % streamed figure to see if SWS needs to learn the startup blocks better. Check by settting the config to stream the entirety of the package.

Other than that my gut is saying this is packaging or something vendor specific as EdT is pursuing above.

Michael Cole

Principal Business Critical Engineer

Business Critical Services