none
Microsoft Visual Studio 2010 Tools for Office runtime(x64) package failed

    Question

  • After install of VS 2012 SP1, I couldn't publish a web app via FTP due to "missing FrontPage extensions".

    So I had to run a repair of VS. This completed with the message of the subject here.

    Here is the log on SkyDrive:

    vslog.cab

    OS is Win8 Danish latest version fully updated, full access to the Internet.

    Office 2010 Pro Danish is installed with latest updates.

    No custom firewall/anti-virus, only Windows native firewall and MSE.

    Media is "en_visual_studio_premium_2012_x86_dvd_920758.iso" mounted as a drive. From this, VS2012 has been reinstalled several times with zero errors whenever a new version Win8 came out.

    SP1 has been installed from the link on the website as I couldn't find an ISO download. First time install of this also happened with zero errors. Thus, I guess, all certificates should be in place.

    Any clues, please?

    This is a follow-up to:

    http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/e3966fa7-f5d4-486d-bffd-64ce75f8701b/


    Gustav Brock

    Tuesday, December 04, 2012 1:28 PM

Answers

All replies

  • Win8 is 64-bit. 8 GB ram

    Office 2010 is 32-bit


    Gustav Brock

    Tuesday, December 04, 2012 1:30 PM
  • Hi Gustav Brock,

    Thanks for your post.

    If you mean "Microsoft Visual Studio 2010 Tools for Office runtime(x64) package failed"

    Here are your error info:

     Type:ERROR
    Strings (7):[Produkt: Microsoft Visual Studio 2010 Tools for Office Runtime (x64) -- A later version of Microsoft Visual Studio 2010 Tools for Office Runtime (x64) is already installed.]

    Searched on your OS and found:

    {7E587F58-50BE-3557-89F6-14D99CB5FB2A} Microsoft Visual Studio 2010 Tools for Office Runtime (x64)
       Package code: {4B16F3EA-E72D-407A-8336-355470B6D55C}
       Install date: 2012.11.14
            Version: 10.0.40307

    and also:

    {6C40DDAB-5821-31B4-A26D-E29905C6E57D} Microsoft Visual Studio 2010 Tools for Office Runtime (x64) Language Pack - DAN
       Package code: {09D6E797-0336-41DE-BC7D-1E94AFC53643}

    It is alreay installed on your OS.

    When and where did you download that ISO? Can you provide me the link?

    By the way, do you mean you meet this error when repair Visual Studio 2012?

    The latest version of Microsoft Visual Studio 2010 Tools for Office Runtime (x64) is 10.0.40302. When did you got that 10.0.40307 installed? Can you remove it then try repair?

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.


    Wednesday, December 05, 2012 10:01 AM
  • Hi Barry

    I got the ISO file from MSDN:

    https://msdn.microsoft.com/en-us/subscriptions/securedownloads/hh442898#searchTerm=Visual%20Studio%20Premium%202012&ProductFamilyId=0&Languages=en&PageSize=10&PageIndex=0&FileId=0

    I can't recall from where the Office Tools arrived. Isn't it an option to choose at the VS install? Or to install from within VS? I searched my folder with ISOs and install files but cannot find a trace of the Office Tools.

    I wasn't aware that both the US and DA version should be present. I can try to uninstall those if possible - I don't use them at the moment. If not present in "Add/Remove Programmes", is there a way to clean them out?

    The version numbers of the Office Tools I cannot explain. I only download from official MS mails and sites and MSDN.

    And yes, the error message was shown after an attempt to repair the VS installation.

    Before that I had installed the Update 1 from here:

    http://www.microsoft.com/visualstudio/eng/downloads#d-visual-studio-2012-update

    using the link directly. I wasn't aware of the MSDN download.

    Please don't hesitate if you need more info.


    Gustav Brock

    Wednesday, December 05, 2012 12:15 PM
  • Hi,

    Actually, this tool is installed with Visual Studio. This means it one of the component of Visual Studio.

    Please refer to this blog to find that 10.0.40307 out

    http://blogs.msdn.com/b/astebner/archive/2005/07/01/434814.aspx

    Use msiinv to gather product code and use msiexec /x <product code> to uninstall it.

    Then try repair Visual Studio. Let's check the result.

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by camelCasus Sunday, December 09, 2012 11:40 AM
    Thursday, December 06, 2012 10:03 AM
  • Thanks Barry.

    I'm out of office so it may not happen before the weekend.

    One question: If/as "Microsoft Visual Studio 2010 Tools for Office" is installed with VS2012, is that due to a lack of a final "Microsoft Visual Studio 2012 Tools for Office" package?

    I've noticed it is comming up, now as Preview 2:

    http://blogs.msdn.com/b/officeapps/archive/2012/11/10/announcing-the-latest-release-of-office-developer-tools.aspx


    Gustav Brock

    Thursday, December 06, 2012 10:16 AM
  • Hi Barry

    First I went to ControlPanel to remove the Office Tool and the language pack. They appeared to have been uninstalled.

    Then I ran the msiinv.exe util which revealed the Office Tool as still present:

    Microsoft Visual Studio 2010 Office Developer Tools (x64)
     Product code: {572E796D-C52B-3797-A685-2FB6F895D4BE}
     Product state: (5) Installed.
     Assignment: per machine
     Package code: {F820C949-4FFE-4E23-9551-40EA641716D9}
     Version: 11.0.50727
     Publisher: Microsoft Corporation
     Language: 0
     Installed from: C:\ProgramData\Package Cache\{572E796D-C52B-3797-A685-2FB6F895D4BE}v11.0.50727\packages\VSTO\
         Package: vstodt40_x64.msi
     Help link: http://go.microsoft.com/fwlink/?LinkId=133405
     Instance type: 0
     Local package: C:\Windows\Installer\1320a1.msi
     Install date: 2012\08\31
     0 patch packages.

    Now I ran

    msiinv.exe /x {572E796D-C52B-3797-A685-2FB6F895D4BE}

    to remove it, but it didn't succeed. I tried couple of times.

    So I turned to Microsoft's Windows Cleanup Utility, but when searching for a newer version I found a page noting that it was obsolete and I Microsoft Fix-It should be used.

    This - Fix-It - was ran a couple of times, but in both cases it just ended with a message that it couldn't do anything.

    Then I ran CCleaner which cleaned up more than 90 entries in the Registry.
    It's program uninstall tool showed the Office Tool as still present, thus I tried to use CCleaner to uninstall it. That succeeded.

    Now, in ControlPanel, the Office Tool has vanished, and when I launched the VS2012 install and chose Modify, the Office Tool was unmarked.

    After a reboot, I ran the VS2012 Update 1 repair, and it succeed with no error.
    Finally I ran a VS2012 repair and it also ran with no errors.

    So problem solved.

    As I cannot imagine CCleaner uninstall utility does anything different than similar to:

    msiinv.exe /x {572E796D-C52B-3797-A685-2FB6F895D4BE}

    perhaps the clean-up of the Registry was what was needed?

    Thanks for your efforts and for pointing me in the right direction.


    Gustav Brock

    Sunday, December 09, 2012 11:40 AM
  • Glad to hear you've solved this issue.

    Best regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, December 10, 2012 11:23 AM
  • Gustav,

    This is a very old post but perhaps the problem lies in the command that is run after msiinv utility. Barry suggested to run

    msiexec /x <product code>

    while the command run by Gustav was

    msiinv /x <product code>. 

    I kept doing the same mistake until i closely read through Barry's post again.

    Thank you Barry and Gustav for your help!

     

    Friday, August 02, 2013 7:15 PM