SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL

FIXED – SharePoint 2013 rule “SharePoint installation requirements for PowerPivot for SharePoint” failed

While attempting to install PowerPivot SQL2012 for a new SharePoint 2013 farm I came across this interesting error.  Basically, PowerPivot checks for SharePoint 2010 because that’s what existed when the SQL2012 product shipped.  However, we now have SharePoint 2013 version 15.0 to think about.  The workaround detailed below adds a few placeholder registry keys in order bypass the SQL rule check and keep moving forward.

Rule “SharePoint installation requirements for PowerPivot for SharePoint” failed.  SharePoint Server 2010 is not installed on this computer.  Please install SharePoint before you install PowerPivot for SharePoint.

Just save the below text as a .REG file and double click.  Hope that helps! 



  • With backslashes…

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0] “SharePoint”=”Installed”
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0SecureConfigDB] “dsn”=”OK”
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0WSSInstalledProducts] “{90140000-1014-0000-1000-0000000FF1CE}”=”BEED1F75-C398-4447-AEF1-E66E1F0DF91E” “{90140000-110D-0000-1000-0000000FF1CE}”=”D5595F62-449B-4061-B0B2-0CBAD410BB51” “{90140000-112D-0000-1000-0000000FF1CE}”=”926E4E17-087B-47D1-8BD7-91A394BC6196”

    • Grontoblios

      Thanks SPJeff, Jean-Pierre, and everyone!

      One more tiny correction:

      The line shown above as

      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0SecureConfigDB] “dsn”=”OK”

      should include one more backslash between Secure and ConfigDB, to read as follows:

      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0SecureConfigDB] “dsn”=”OK”

      With this fix, the resulting .reg file has been tested in our environment and does in fact work.

      For completeness, below is the entire content of the required .reg file as validated here:

      Windows Registry Editor Version 5.00
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0]”SharePoint”=”Installed”
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0InstalledLanguages]”1033″=”15.0.4420.1017″
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0Secure]
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0SecureConfigDB]”dsn”=”OK”
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0WSS]
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions14.0WSSInstalledProducts]”{90140000-1014-0000-1000-0000000FF1CE}”=”BEED1F75-C398-4447-AEF1-E66E1F0DF91E””{90140000-110D-0000-1000-0000000FF1CE}”=”D5595F62-449B-4061-B0B2-0CBAD410BB51″”{90140000-112D-0000-1000-0000000FF1CE}”=”926E4E17-087B-47D1-8BD7-91A394BC6196″

      Not sure the InstalledLanguages key is required for installation, but it is there on our server, so I included it here.  Hope this helps somebody.

      • Philip

        This file is more close the correct, but in my situation, the all node change to
        [HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftShared ToolsWeb Server Extensions14.0]
        use the tool procmon.exe can find in each instance installation, the article has some wrong in code writing, like:
        14.0WSSInstalledProducts –>>14.0WSSInstalledProducts
        14.0SecureConfigDB –>> 14.0SecureConfigDB

        • Thanks guys!

          I updated the REG file in the original post with everyone’s feedback.

    • Grontoblios

      And thanks to SPJeff and thecodeattic, there is just one more thing:

      When you are installing the POWERPIVOT instance of SQL Server 2012, in the Instance Rule Check step in the wizard, you may get a warning from the “SharePoint version requirement for PowerPivot for SharePoint” item to the effect that “SharePoint 2010 SP1 is not installed.”

      You can proceed with the installation but when the time comes to configure PowerPivot, configuration will fail with the same error.

      There is yet another registry hack required to get around this bogosity:

      Windows Registry Editor Version 5.00
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice Server14.0]”BuildVersion”=”14.0.6123.5000″

      We get yet another warning at this point from the “Verification that Database Engine Is Needed” item that SharePoint is already configured.  Only problem there is that SharePoint is NOT configured at this point, no databases have been created, etc.  So we’re going ahead, in the belief that this is just another defect in the customer-focused and absolutely delightful SharePoint 2013 setup routine.

      If we learn anything else we’ll put it here.  All the best — gront

  • AG Triyanto

    Thank you…

  • Aminlv

    🙁 not working for me still say same error

  • Aminlv

    never mind found the issue since copy from web there is no enter between each lines add enters and it work thanks for your good article 😉

  • Kel2525m

    Thank you very much. Wonder not found this work around in MSDN.

  • Pingback: SharePoint 2013 PowerPivot Install Issue: “Please install SharePoint before you install PowerPivot for SharePoint” « Andrew Whitten's Enterprise Microsoft Blog()

  • I updated to include backslashes.  Not sure how that happened.  Probably a side effect of WordPress XML import.  Thanks for all the feedback guys.  Glad this post was helpful.

  • Bob

    Thanks for sharing! But it doesn’t work for my case.
    MS has released SQL 2012 SP1, if you use the FullSlipstream version for new installation, everything will be OK.
    They fix this bug on SQL 2012 SP1, I have verified that.


  • Cameron Beatley

    thank you Jonesy

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲