locked
Microsoft Access 2010 AppV 5.0 Virtualisation Issue with Word Merge Features RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    We have tried to sequence Microsoft Access 2010 Application in AppV 5.0 Sequencer. We are facing issue when we try to Use WORD MERGE Feature through the Virtual App . We have Office Professional 2010 as part of our builds without Access Feature Enabled.

    When we press the Word Merge Button, We are getting the below error .

    On Clicked OK , Below error is popping up.

    Kindly Let us know If there is any solutions, !!

    Monday, September 28, 2015 3:11 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    You can disable FTA's in your appv package, by making a change to the deploymeny/userconfig and apply it, like:
        <FileTypeAssociations Enabled="true">
      <Extensions>
        <Extension Category="AppV.FileTypeAssociation">
          <FileTypeAssociation>
            <ProgId>
              <Name>Adobe.SVGBehaviorFactory</Name>
              <Description>Factory Class</Description>
              <CurrentVersionProgId>Adobe.SVGBehaviorFactory.3</CurrentVersionProgId>
            </ProgId>
          </FileTypeAssociation>
        </Extension>
    Just change enabled, to FALSE. If you want to, you can also remove the FTA you do not want.

    Thursday, October 1, 2015 6:16 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You have not included an error screenshot

    First thing, I would ask regardless is if you've run ProcMon against this?

    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Monday, September 28, 2015 3:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you install Office (like in your base image) on your sequencer, prior to starting your sequence? Also did you start the office apps at least once? Did this action work while sequencing? Did you configure any COM-settings?
    Monday, September 28, 2015 6:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes we had put lots of troubleshooting in this with procmon...but nothing couldn't helpout we have sequenced it on an XP build with 4.6 sequencer and converted it to AppV 5.0 and that's it worked out flawlessly....

    Now we are running into another issue we have Office 365 as physical and EXCEL 2010 as virtual we are testing the FTA's by opening a .xlsx or any excel workbook and it opens with virtual against the physical install. Our client has a specific requirement for these different requests to co-exist.

    The requirement is to open some workbooks with AppV shortcut and rest should open with default physical install.

    Thursday, October 1, 2015 1:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes we have installed office as base line and nothing helpedout...all we did is sequenced it on an XP build with 4.6 sequencer and converted it to AppV 5.0 and that's it worked out flawlessly....

    Now we are running into another issue we have Office 365 as physical and EXCEL 2010 as virtual we are testing the FTA's by opening a .xlsx or any excel workbook and it opens with virtual against the physical install. Our client has a specific requirement for these different requests to co-exist.

    The requirement is to open some workbooks with AppV shortcut and rest should open with default physical install.

    Thursday, October 1, 2015 1:19 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    You can disable FTA's in your appv package, by making a change to the deploymeny/userconfig and apply it, like:
        <FileTypeAssociations Enabled="true">
      <Extensions>
        <Extension Category="AppV.FileTypeAssociation">
          <FileTypeAssociation>
            <ProgId>
              <Name>Adobe.SVGBehaviorFactory</Name>
              <Description>Factory Class</Description>
              <CurrentVersionProgId>Adobe.SVGBehaviorFactory.3</CurrentVersionProgId>
            </ProgId>
          </FileTypeAssociation>
        </Extension>
    Just change enabled, to FALSE. If you want to, you can also remove the FTA you do not want.

    Thursday, October 1, 2015 6:16 PM