InfoPath 2013 form feature into 15 hive folder?


  • I have created sample InfoPath form 2013 and deployed in SharePoint 2013 farm. Form deployed to the farm successfully but I have observed that the InfoPath feature folder was created in 14 hive folder. 

    My question here is, InfoPath 2013 form feature folder should create in 15 hive folder.

    Please let me know if my assumption is wrong or any suggestions?

    Thursday, July 11, 2013 9:24 PM

All replies

  • Did you ever find a solution for this?  Same Issue when deploying through Central Admin.

    The only solution I came up with was

    Install-SPSolution 4f426b58-6f42-af62-2678-8b3c33bb722c.wsp  -CompatibilityLevel 15 -force 

    Thursday, August 14, 2014 9:16 PM
  • It's by design. All InfoPath forms in 2013 - even if you're using InfoPath 2013 and .Net 4 - go into the 14 hive.
    Tuesday, June 23, 2015 4:33 AM
  • Understandable, I suppose. But why design all of these errors?!  I mean the upgrade still goes through, but very annoying to have these for every form.

    [MissingSetupFile] File [Features\FT-01-0fdb6008-7646-3869-e589-42b873f6e05e\solution.xsn] is referenced [1] times in the database [WSS_Content], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains this file to the latest version.

    Should we deploy with powershell to 14 & 15?  or ignore the mess of errors?

    • Edited by aoneil Tuesday, August 11, 2015 4:01 PM
    Tuesday, August 11, 2015 3:58 PM