VMware Horizon Community
nxion
Enthusiast
Enthusiast

Microsoft Project and Office issues

Hello,

So latly I have run into some issues that I can't explain and I hope someone here can. So I have MS Project 2010 and Office 2010 thinapped in my orginzation. Latly I have been getting this error.

"Microsoft Office cannot verify the license for the application. A repair attempt failed or was canceled by the user. The application will not shut down."

I have no idea what causes this. I can go to a diferant machine and run my Office and Project thinapps and they run and activat fine and I never see this error. I als created two exact vm's with Windows 7. All the same software and patch level It works on one but not the other! I dont understand. I attached the screenshot to the post.

Anyone have any ideas?

Thanks.

Reply
0 Kudos
58 Replies
nxion
Enthusiast
Enthusiast

So how new is that build because I have a differant one that you and I was told that there is no new version coming out.

Is that a recent build?

Reply
0 Kudos
andygoen
Contributor
Contributor

I would assume it's the latest. I just received the download link yesterday.

Reply
0 Kudos
Squidly_Man
VMware Employee
VMware Employee

Please see the below mentioned blog posting for enabling SEND AS.  The blog posting is centered around Office 2007 but others have tested for Office 2010 and it does work so long as the registry value(s) mentioned are modified to accommodate Office 2010 products.

Enabling "Send As Email Attachment" in ThinApp packages when Outlook is installed natively

-Dean F. https://www.vmware.com/support/pubs/identitymanager-pubs.html
Reply
0 Kudos
nxion
Enthusiast
Enthusiast

andygoen wrote:

we manage to thinapp Visio and Project 2010 without license issue for W7 x86 with Office 2010 x86 natively installed using ThinApp 4.7.0 build 588339 - Thanks to VMWare Technical Support. However, we are unable to get Visio/Project 2010 to do "Send as Attachment". Anyone else tried this?

So on the Vmware downlad site the latest build is 519532, SO yu have a new version. So I guess ill call my TAM...

Reply
0 Kudos
nxion
Enthusiast
Enthusiast

So the build on the site is a old build. I have a hotfix that was given to me to address the activation issue. The build that was given to me was 556319 I believe. The one you have is a new hotfix it looks like. I really hope this one works...

I've been sadly disappointed by vmware lately.

Reply
0 Kudos
admin
Immortal
Immortal

nxion, the hot fix build you had, I believe it should be 556613, should be the latest hotfix build. Although 588339 has a newer number but it has no more change from 556613.

What is your URL of the hotfix build?

Reply
0 Kudos
TobyFruthParson
Enthusiast
Enthusiast

I did a fresh capture of Visio Pro 2010 yesterday with ThinApp hotfix build 556613 and the HKLM delete keys.  Visio KMS activation failed right away.  I added one more delete line to the top of HKLM and the activation error disappeared.  I added:

deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\

YMMV (your mileage may vary)

I would like to encourage you that, rather than be disappointed in VMware, consider that they

  • Don't own the source code for Windows
  • Don't own the source code for Office 2010
  • Don't own the source code for the KMS server
  • Are, in many cases, not able to exactly reproduce every single customer environment

yet

  • They can provide multiple versions of virtual IE running side-by-side on multiple Windows version (something Microsoft doesn't offer, and they do own all the source)
  • ThinApp uses a runtime baked in to the compiled package - no agent to manage
  • ThinApp doesn't require a massive infrastructure to get started, and integrates well with existing infrastructure
  • If you attempt to virtualize Office 2010 with Microsoft or Citrix, you still have to make use of the APP-V Deployment Kit for Office 2010

I'm a customer, just like you.  I'm not a reseller or an employee of VMware.  I've investigated no fewer than six application virtualization products.  I think that ThinApp is right at the top in terms of ROI and simplicity.  The products that can handle kernel-mode drivers (a.k.a. Acrobat) typically require an agent and a backend infrastructure.

My encouragement to you is to be patient.  I've been working on virtualizing Office 2010 components (Project and Visio) for several months.  I believe we (VMware and its customers) are turning a corner with this latest hotfix and registry entries, and soon we'll see consistent success in virtualizing these products.  With build 556613 and the registry entries, I'm able to run virtualized Project 2010 and virtualized Visio 2010 together and in conjunction with native Office 2010 without any KMS activation issues.  I didn't have to use any agents (APP-V kit), any servers (Citrix/Terminal Services), or any Visual Basic scripting (to control OSPPSVC.)  This is a big step in the direction that many VMware customers have been seeking to go and now we are.

I hope you find this message is encouraging, as that is its intent.  I firmly believe this community and VMware are dedicated to solving issues and advancing the cause of application virtualization.

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

Thanks!!! Awesome write-up!

Dean Flaming | 253.256.DEAN | 253.256.3326 | DFlaming@vmware.com

vmware | ThinApp & Horizon Global Product Specialist

ThinApp Documentation - http://pubs.vmware.com/thinapp4/help/

Horizon Documentation - http://pubs.vmware.com/horizon-administration-help/index.jsp

ThinApp Info Smartphone App - http://wbxapp.com/thinapp-info (browse here on your smartphone!)

-Dean F. https://www.vmware.com/support/pubs/identitymanager-pubs.html
Reply
0 Kudos
andygoen
Contributor
Contributor

Thanks Squidly Man. That KB did helps me, though only halfway.

After days of troubleshooting I managed to get Project 2010 to recognize natively installed Outlook 2010 and attach file successfully.

I did the Project 2010 capture on a clean win7. There's no need to do a capture on top of Office 2010 installation. Here's what I did.

Do a capture on Project 2010 full installation. I did not launch the application. Simply stop the osppsvc, then do a post-scan.

In package.ini, just uncomment VirtualizeExternalOutOfProcessCOM=0

Set the following to MERGED, as per KB

%APPDATA%\MICROSOFT\AddIns\

%APPDATA%\MICROSOFT\Office\

%APPDATA%\MICROSOFT\Outlook\

%LOCAL APPDATA%\MICROSOFT\Outlook\

%LOCAL APPDATA%\MICROSOFT\FORMS\

%TEMP%\

Set the following folder and subfolders to WRITECOPY

%Program Files Common%
%ProgramFilesDir%

Content of my HKCU

isolation_writecopy HKEY_CURRENT_USER\Environment

  Value=ALLUSERSPROFILE

  REG_SZ~%Common AppData%

isolation_merged HKEY_CURRENT_USER\Identities

isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Office

isolation_merged HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Security

isolation_merged HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem

and on HKLM, added the registry given by VMWare Support (same as previous post) and also add

isolation_full HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Search\Preferences

  Value=PreventIndexingOutlook

  REG_DWORD=#01#00#00#00

isolation_merged HKEY_LOCAL_MACHINE\Software\Clients

isolation_merged HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\00004109A10090400000000000F01FEC

isolation_merged HKEY_LOCAL_MACHINE\Software\Classes\Installer\Components\0470D1FF722D1D114A0B000680FA28E0

isolation_writecopy HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\User Settings\Outlook_Intl

  Value=Count

  REG_DWORD=#01#00#00#00

  Value=Order

  REG_DWORD=#01#00#00#00

then change isolation_full to isolation writecopy on HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\User Settings and all its subkey.

Message was edited by: andygoen. Incorrectly paste HKCU key on HKLM section

Reply
0 Kudos
TobyFruthParson
Enthusiast
Enthusiast

Thanks for the info.  This got my Visio 2010 build closer to sending email thru native Outlook 2010.  I know your post is in regards to Project 2010, but I figured why not try it out on Visio 2010.

In virtual Visio 2010 I click 'Save & Send -> Send as attachment', the native Outlook MUI installer pops up and runs for a second and goes away.

outlook_mui_visio_2010.jpg

Toby Fruth, Sr. Specialist, The Parsons Corporation
Reply
0 Kudos
andygoen
Contributor
Contributor

@TobyFruthPars

We did capture Visio 2010 and applied the same method and the Send as Attachment worked fine.

I got the same Outlook MUI installer as yours initially, then I checked the event viewer for the answer. It should tell you why the installer was run.

Reply
0 Kudos
TobyFruthParson
Enthusiast
Enthusiast

On Windows XP SP3 testing VM with Outlook 2007 the Save & Send function for Visio Standard 2010 ThinApp is working fine.  I am now tracking down the Outlook 2010 MUI installer issue.

Current suspect cause (from event viewer):

"Detection of product '{90140000-001A-0409-0000-0000000FF1CE}', feature 'OutlookMAPI2Intl_1033' failed during request for component '{BC5551FA-8420-403D-99D7-1EAC191169EA}'"

Toby Fruth, Sr. Specialist, The Parsons Corporation
Reply
0 Kudos
Lakshman
Champion
Champion

Please try the new ThinApp release 4.7.1.

Release notes - https://www.vmware.com/support/thinapp4/doc/releasenotes_thinapp471.html

Reply
0 Kudos
projekttasse
Contributor
Contributor

Hello,

i already downloaded the Version, but still the same issues. Can VMware deliver a handout for virtualization of Office related Apps?

Tim

Reply
0 Kudos
Lakshman
Champion
Champion

Tim,

Along with 4.7.1, please follow the step by step instructions posted here:

http://blogs.vmware.com/thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-46...

Follow the KB article http://kb.vmware.com/kb/1022287.

Add the text entries in the attachment to HKEY_LOCAL_MACHINE.txt file in the ThinApp Project folder.

Reply
0 Kudos
projekttasse
Contributor
Contributor

Okay,

MS i tried MS Visio2010 and still some issues.

Will try later Project 2010.

Tim

Reply
0 Kudos
rjtd
Contributor
Contributor

About Visio 2010, was anyone was successfull with using the Visual Reports with native Excel 2010?

I also had some issues with 2010 that I was able to fix:

- If using scripts (ex.: the timebomb script from thinapp blog), Office will not activate unless you cleanup WshShell.

- If your sandbox is redirected to network or on user roaming profile, activation will fail on a different computer unless you cleanup the sandbox on startup.

Reply
0 Kudos
Mapleaf
Contributor
Contributor

I have read through this thread and reviewed the KB article to attempt a fix for MS Office not able to verify the license.  I am glad to hear this seems to help some users in specific cases.

I would like to put a different spin on the issue.  I am also receiving the licensing issue but I am not capturing any Office 2010 products.  Instead I only need to have a Thin capture of IE6 to run a web application in Windows 7.  I used a squeeky clean fully patched install of XP SP3 and the only app captured is IE6 using the built in feature of ThinApp to create it.

When I test the captured IE6, it load fine.  However, when I try to export data from within the web application, my native fully licensed Excel 2010 load and tries to open the .CSV file.  The Microsoft error that MS Office cannot verify the license for the application is displayed and Excel shuts down.

Also, the performance of the application slowed down so much it is not unusable.

My work around was to recapture IE6 using version 4.7.0.  No licensing issues and the performance is flawless.  I am not sure what was "Fixed" for the licensing issue in 4.7.1, but do hope they can fix the fix.

Reply
0 Kudos
Squidly_Man
VMware Employee
VMware Employee

@MapleLeaf - In your case you need to do the following to the IE project:

1.  Set all desired processes to run natively, not letting them default to running within the virtual bubble.  This is done by use of the "ChildProcessEnvironmentDefault" and "ChildProcessEnvironmentExceptions" build option settings.

2.  Additionally, so external processes can see these files from the virtual IE app, you'll need to customize the folder isolation settings for the following folders.

%Temp% - create this if it doesn't exist.  Set the isolation to MERGED in the ##ATTRIBUTES.INI file.  Delete all other contents.

%Cache% (or IE Cache folder) - set to MERGED isolation and delete all contents except ##ATTRIBUTES.INI file.

Probably need to do the same for %Profile% if exists or just delete it.

Depending upon where else IE stores files for web apps, you may need to do the above for other folders.  You may also need to set VirtualizeExternalOutOfProcessCOM=0 as a build option.

As for the licensing issue, once you get the processes launching externally, you won't have the licensing issue with Office.

Then build, wipe your sandbox, and rest.

-Dean F. https://www.vmware.com/support/pubs/identitymanager-pubs.html
Reply
0 Kudos