locked
SAS Addins 8.2 with Office 2016 - Conflict with native Excel RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    We have created an AppV package with the SAS Addins 8.2 for Office 2016.
    The Addins are VSTO, OS is Windows 2016 and our Office 2016 is installed locally.

    COM integration is set to OOP integrated.
    Excel with the addin is started from a shortcut we added in the package.

    When starting Excel from the shortcut, Excel is started and the addin is loaded.
    No issue so far.
    When you close the Excel with addin and open the native Excel, the native Excel tries to load the SAS addin but (obviously) fails.
    When failing it disables the addin, meaning when opening the Excel with addin, the addin needs to be re-enabled.

    Following Office regkey paths are added to the Passthroughpaths:

    HKEY_CURRENT_USER\Software\Microsoft\Office\16.0
    HKEY_CURRENT_USER\Software\Microsoft\Office\Common
    HKEY_CURRENT_USER\Software\Microsoft\Office\Lync

    I cannot find why this behaviour is happening even with all the info I found on the net.

    Can anyone help or suggest please?

    Thanks
    Stefaan

    Monday, August 24, 2020 6:44 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Is there a reason you use a shortcut instead of configuring RunVirtual?
    Are you 100% sure all excel processes are closed (and the SAS virtual env. is also not "open/running" no more?). The load behavior from the SAS addin should be configured in the package only under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins (for x64 version) and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\Excel\Addins (for x86 version). Could you verify you the SAS addin keys only exist in the app-v package and not outside in the local registry?

    We also virtualised the SAS office addin since appv4, and never had issues like this before.... back then we also used a shortcut to load the SAS addin package, I cant recall the issue you're describing. Nowadays we use appv5 with RunVirtual configured with a diverse set of office addins combined dynamically on 1 connectiongroup. 

    Roy Essers

    Thursday, August 27, 2020 2:57 PM