#1
  1. Contributing User
    Devshed Beginner (1000 - 1499 posts)

    Join Date
    Mar 2005
    Location
    Tír na nÓg
    Posts
    1,199
    Rep Power
    183

    Office Custom Toolbar - Upgrade from 2010 to 2016


    Hi there,

    Apologise if this is the wrong forum to post in.

    I'm a web developer thrust into the realm of support which is all encompassing.
    The current task at hand is to get custom toolbars for Word, Excel and Powerpoint working on Windows X running Office 2016.
    They currently work on Windows 7 running Office 2010.

    The second line support people tried to simply run the installer used for installing the toolbars on Windows 7 on Windows X but that didn't work as the installers Launch Conditions state a few things need be installed first.
    The suggestion to install Office 2010 was rejected as that defeats the purpose of the exercise.
    I'm not sure what direction to go in with regards a fix.

    Currently there are a "Search Target Machine" instructions, the one causing the installer to fail to run is called "Search for Office 2010 Shared PIA".
    It has the following values:
    (Name) - Search for Office 2010 Shared PIA
    ComponentId - {64E2917E-AA13-4CA4-BFFE-EA6EDA3AFCB4}
    Property - HASSHAREDPIA

    All I've been able to figure out so far is that GUID corresponds to "Office Shared" as per this link
    I'm guessing that this is a specific GUID for Office 2010 Shared.
    If I could find the Office 2016 Shared GUID (which I haven't located yet), would that fix my issue?

    I've just found some manifest files, one for each of Word, Excel and Powerpoint.
    They look a lot like web.config files so that worries me.
    They have dependencies listed like this:
    PHP Code:
    <dependency>
        <
    dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true">
          <
    assemblyIdentity name="Microsoft.Office.Tools" version="10.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" />
        </
    dependentAssembly>
      </
    dependency
    Am I going to have to update all of these to reference the 2016 office equivalents?

    Flying a bit blind here so any and all pointers would be greatly appreciated.
  2. #2
  3. Contributing User
    Devshed Beginner (1000 - 1499 posts)

    Join Date
    Mar 2005
    Location
    Tír na nÓg
    Posts
    1,199
    Rep Power
    183
    Updating the GUID did the trick.
    The Office 2016 Shared PIA is "C845E028-E091-442E-8202-21F596C559A0" (Excel 2016 x86)
  4. #3
  5. No Profile Picture
    Contributing User
    Devshed Novice (500 - 999 posts)

    Join Date
    Oct 2009
    Location
    Nebraska, USA
    Posts
    938
    Rep Power
    281
    thanks for updating us with the fix.

IMN logo majestic logo threadwatch logo seochat tools logo