Search the VMware Knowledge Base (KB)
View by Article ID

Licensing errors when deploying virtual Office to a system with Office installed natively (2107369)

  • 10 Ratings

Symptoms

When you deploy a Microsoft Office 2010 or Office 2013 family product to a system that already has Office installed natively, you experience these symptoms:

  • Office initiates a repair procedure.
  • An error message indicates that licensing cannot be verified.
  • Office terminates after a licensing error is displayed.
  • You see the error:

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

Resolution

Note: ThinApp only supports Microsoft Office 2013 on Windows 7. It is not supported on any other operating system.

Validate that each statement is true for your environment. If it is not, take corrective action as necessary and test your package again.

Perform these steps If you continue to see a licensing error:

  1. Download 2107369_TAOffice.zip file attached to this article and extract the contents.

    Note: This zip file contains TAOffice-32.exe for 32-bit Office and TAOffice-64.exe for 64-bit Office. Determine which file is appropriate for your environment. In the steps below the tool is referred to as simply TAOffice and should be replaced with the correct version.

  2. Edit the Package.ini in the project directory.

    1. Locate the section of text that starts with cmd.exe.
    2. If the section of text contains the line Disabled=1 change it to Disabled=0.
    3. Rebuild the package.

  3. Choose or create a directory on the deployment machine where the licensing error occurs.
  4. Copy these to the directory created in step 3:

    1. The files in the bin directory.
    2. HKEY_LOCAL_MACHINE.txt file from the project directory.
    3. The TAOffice tool.

  5. Double-click cmd.exe.
  6. Type TAOffice, where TAOffice is replaced with the correct version for your environment, and press Enter.
  7. Copy the modified HKEY_LOCAL_MACHINE.txt file back to the project, replacing the original version.

    Note: TAOffice makes a copy of the original version.

  8. (Optional) Edit Package.ini and undo the changes made in step 2.
  9. Rebuild the package.

If your problem still exists after following the steps in this article, file a support request with VMware Support and note this KB Article ID (2107369 problem description. For more information, see How to Submit a Support Request.

See Also

Attachments

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 10 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 10 Ratings
Actions
KB: