I virtualized the current Adobe Reader 11.0.03 with Cameyo 2.5 Beta under a clean Windows XP SP3 virtual machine (german language). I got the Adobe Reader installer (AdbeRdr11003_de_DE.exe) from http://get.adobe.com/de/reader/completion/?installer=Reader_11.0.03_German_for_Windows.
When I execute the virtualized package, I get the following error:
=========================================== Deploy error - Cannot deploy application. Please make sure it is not currently in use. (5:AcroIEHelper.dll.manifest) ===========================================
The Cameyo package tries to create the file "AcroIEHelper.dll.manifest" in the sandbox-folder "PROG\%Program Files%\Gemeinsame Dateien\Adobe\Acrobat\ActiveX" and the file is in deed there. I traced the process with Sysinternals Process Monitor and it also gives the information that the file "AcroIEHelper.dll.manifest" could be created successfully:
When I ignore the error message, the application opens. Then the first time I open the preferences the application hangs. Then I kill the application and open it again. Now there is no error about the "AcroIEHelper.dll.manifest" anymore and I am able to get into the preferences dialog.
Maybe the whole thing is negligible. But I still would like to report about this issue. Maybe you could tell me the reason for this problem.
Here some details about my Cameyo package:
Virtualization: Disk Mode Isolation Mode: Isolated Startup: C:\AdobeReader11\Reader\AcroRd32.exe Data Storage: Unser the executable's directory Properties of the virtualized file "AcroIEHelper.dll.manifest": Deployed: extracts immediately upon first execution
If you need further information I can deliver them to you.
Thanks in advance for your answer!
Greetings
ScARiD
-- Edited by scarid on Wednesday 3rd of July 2013 01:50:51 AM
thank you for your answer. Your package works perfectly!
There are some differences between your and my package:
- I built it on a german Windows XP. That results in another directory for the file AcroIEHelper.dll.manifest. Your package: "PROG\%Program Files%\Common Files\Adobe\Acrobat\ActiveX" / My package: "PROG\%Program Files%\Gemeinsame Dateien\Adobe\Acrobat\ActiveX"
- I chose "C:\AdobeReader11" as installation directory, you "C:\Program Files\Adobe\Reader 11.0". I did that because I thought it would be a good idea to choose a simple path to avoid problems with the directory structures on target hosts. Is that a good idea?
Is it advisable to package an application on a german Windows XP? I could imagine that it could lead to problems because Windows XP uses localized directory names. Windows Vista and later use universal directory names.
And at least: Could you please tell me a few details about your packaging of this application? What did you customize while capturing the installation process? I saw you deactivated the Sandbox-Feature of Adobe Reader. Were there other things you customized?
- Do you still have the non-working package? No, I packaged it on Windows 8 and now everything works fine
- On which machine (OS / bit) did you try to make the package work? Was there other remainings of a previous Cameyo'd Adobe version? I tried to run my package on the same Windows XP system as I created it on. I tried that immediately after the packaging. So the normal Adobe Reader installation was still present. I also executed my package on a german Windows 7 x64 system on which also a normal installation of Adobe Reader was present.
There is no need to put too much time into this case because I have a working package now. But maybe you can answer my questions of my previous post.
I also would like it if you could deliver packaging examples of some popular applications like Google Chrome etc. on your website. That could give people handy information on how packaging works and what is important to pay attention on. But that is just an idea. Learning by doing is surely still the best.
-- Edited by scarid on Saturday 6th of July 2013 12:59:51 AM
I did not customize the installation. Adobe's sandbox get disabled automatically when running virtualized because it is incompatible with virtualization.
About the language: if your package is to be used on German systems, then that's not a problem. Otherwise it's recommended to package it on a universal OS.
