VMware Horizon Community
Rockees
Contributor
Contributor

Adobe Acrobat Pro X Thinapp issues

Hi Guys,

I thinapp'ed Adobe Acrobat Pro x, the app works fine but seems  "attach to Email " feature and "Create PDF" feature is not working. Did anyone had same issues?

Appreciate your help

Thanks in Advance

Reply
0 Kudos
8 Replies
Lakshman
Champion
Champion

Ross,

A similar issue was fixed in ThinApp 4.7.2 release. What version of ThinApp are you using?

Reply
0 Kudos
Rockees
Contributor
Contributor

4.7.2

Reply
0 Kudos
Cievo
Commander
Commander

What do you mean "not working"?

Are you getting any errors? What does it do when you want to use those things?

***Good question is half of the answer...***
Reply
0 Kudos
kmgp
VMware Employee
VMware Employee

Hi,

I have seen Files of type .jpeg being successfully opened and saved as PDF. In particular what was the file type you tried to convert to PDF.

For the Attach to email to work you have two options;

  • either applink Microsoft office Outlook to Adobe Acrobat Pro x
  • or
  • install the Microsoft outlook on the machine running the Adobe Acrobat Pro.

If outlook installed natively then you have to make Outlook.exe available to the thinapp. Please follow the guidelines in here http://blogs.vmware.com/thinapp/2011/12/enabling-send-as-email-attachment-in-thinapp-packages-when-o...

Hope this helps.

GURU

Views expressed in here are my own.
Reply
0 Kudos
Rockees
Contributor
Contributor

Hi GURU,

I followed the link and built the package again. Here, whenever  I select "Attach to Email"  from the PDF file everytime it tries to configure MS OFFICE 2010. How do I get rid of this everytime configuring Office 2010.

Thanks in Advance

Reply
0 Kudos
Rockees
Contributor
Contributor

Hi,

It gives me an error message " Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run microsoft Outlook and set it as default mail client"

Thanks in Advance

Reply
0 Kudos
TobyFruthParson
Enthusiast
Enthusiast

My apologies in advance if you don't find this post useful.  I did encounter the same errors, and I was running locally installed Outlook 2010.  I managed to solve the problem via Package.ini settings. Try the following.  Your mileage may vary.

ChildProcessEnvironmentExceptions=outlook.exe;svchost.exe;powerpnt.exe
ChildProcessEnvironmentDefault=External
AllowExternalKernelModeServices=1
AllowExternalProcessModifications=1
AllowUnsupportedExternalChildProcesses=1
VirtualizeExternalOutOfProcessCOM=0

We eventually abandoned all hope of a useful, virtualized Acrobat X from any vendor:  Citrix, VMware, or Microsoft.  We haven't tried Unidesk or Spoon. 

If your users want:

  1. Right-click -> Convert to PDF in Explorer context menu, for individual files and whole directories
  2. Right-click -> Convert to PDF in Outlook emails and folders
  3. Save As -> Adobe PDF in Office (Ribbon macro)
  4. Run batch OCR on entire directory structures
  5. Combine multiple disparate file types in to a single PDF via right-click functionality
  6. The list goes on and on

then, until ALL of the issues are worked out and a REAL recipe is delivered by one of the top four app virtualization vendors, give up your futile exercise.

I hope VMware keeps this post up until someone can show a fully-functional Acrobat X package and a COMPLETE build recipe.  Partial functionality will not suffice in our environment.  I lost too many weeks of productivity and sleep trying to make this work.  Eventually, we had to cut our losses.  Application virtualization is now our last resort, not our first.  Too much loss in application functionality, too many hours spent on workarounds.  This is reality.

I'm normally a nice and helpful guy, more than willing to post code, but you'll see this is my first post in months regarding ThinApp.  We now use it as a point solution for those situations where all other methods have been exhausted.  I believe in the idea, the theory of application virtualization.  I just don't have time to deal with the reality.  The VMware team is very helpful, full of great folks.  I only have good things to say about them as people and professionals.  But, we need:

  1. Full application functionality from products like Acrobat X
  2. 64-bit applications
  3. Better recipes and fewer workarounds

I appreciate that what VMware is trying to do is a difficult and challenging endeavor - that is, virtualizing applications they didn't create and to which they are not privy to the source code.  If you have the luxury of going through the challenge with them, then more power to you.  I lack such luxuries.  If someone from VMware thinks I'm being too harsh and wants to reach out to me, please do if:

  1. You can point to a single, step-by-step recipe for Acrobat X that will provide full application functionality.  I don't want ten links pointing to three recipes, four knowledgebase articles, and three more community threads.
  2. You seriously intend to support 64-bit applications in the near future.  I realize this thread is about a 32-bit application, but our need for 64-bit support has been ongoing for years.

I dislike writing this type of post, as much as others probably dislike reading such things.  I think I have a decent rapport with VMware.  They know who I am and that I support the cause of application virtualization.  Our situation is such that we still have 10,000 real desktops with locally installed, native applications.  We are not poised to rip-and-replace all of that with virtualized applications.  We are in what I call "real-world" mode.  ThinApp seems best suited to an environment where just about every application is virtualized, as opposed to our environment where almost all applications are locally, natively installed.  Maybe some day all apps will be delivered through a standards-compliant web browser and all our effort will be expended on the backend.  Until such time, I have to make hard decisions, and for now that means virtualizing applications when no other means of deployment is sufficient.

Toby Fruth, Sr. Specialist, The Parsons Corporation
Reply
0 Kudos
kmgp
VMware Employee
VMware Employee

Hi Rockees,


If you have noted, the documentation was for Outlook 2007 being natively installed while you followed the steps for Outlook 2010 . I hope my assumption is correct.


Now

  • Do you want a solution where a Outlook 2010 is natively installed and that Acrobat Pro X should use this?

or

  • You can visit the scenario again since you can work with Outlook 2007 being installed natively.

I have applied the steps for Adobe Acrobat Pro X and Outlook 2007 being installed natively and was successful in "File ->Attach to Email".

GURU


Views expressed in here are my own.
Reply
0 Kudos