none
Uploading SharePoint Online solutions (wsp). RRS feed

  • Question

  • I have a folder which I compress into a .CAB file, rename this .CAB file to .wsp. Then I try to upload this WSP file to my solutions in my site collection, but when activating, it fails with the following message:

    Error: Cannot find this file specified in the manifest file. I'd add a screenshot, but my account hasn't been verified yet.


    • Edited by Rudy_ Thursday, January 12, 2017 5:22 PM Correction.
    Thursday, January 12, 2017 5:21 PM

All replies

  • What file is specified in the error message?  Also, does your folder contain any sub folders?  If it does, how did you compress it into a .CAB?  Some methods for making .CABs don't preserve the folder structure inside the .CAB so if the XML manifest specifies a path containing a folder then you won't be able to find it.

    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    Thursday, January 12, 2017 5:26 PM
  • Hi, Paul,

    The full error message is as follows:

    Error: Cannot find this file specified in the manifest file: PremierWednesdayTemplateListInstances\resources\resources.en-US.resx

    The .CAB file does maintain the folder structure, I confirmed this. And then rename it to .WSP, and try uploading this. The error occurs upon activation.

    -Rudy.

    Thursday, January 12, 2017 5:33 PM
  • What is the line in the manifest.xml that mentions that file?  I suspect something is off in the path reference.

    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    Thursday, January 12, 2017 5:37 PM
  • This is the line in the manifest.xml file:

    <FeatureManifest Location="PremierWednesdayTemplateListInstances\Feature.xml" />

    Thursday, January 12, 2017 6:45 PM
  • Hi,

    Please check the articles below:

    Removing Code-Based Sandbox Solutions in SharePoint Online

    https://dev.office.com/blogs/removing-code-based-sandbox-solutions-in-sharepoint-online

    SharePoint Online Sandboxed Solutions Disabled

    https://blogs.technet.microsoft.com/marios_mo_betta_blog/2016/08/02/sharepoint-online-sandboxed-solutions-disabled/

    I suggest you transition your sandbox solution to add-in model or pure client-side development, which provide highly-scalable, cloud-first approaches to extending SharePoint.

    If your solution is a farm solution in SharePoint on premise, please check the article below:

    https://platinumdogs.me/2010/08/09/using-sharepoint-provisioning-and-application-resource-resx-files/

    Best Regards,

    Dennis


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Friday, January 13, 2017 2:36 AM
    Moderator
  • But you said its complaining about a resource file?  Don't you have a line in the manifest that is specific to the resources being used?  If not then that is the problem.  Please review the following walkthorough on localizing features.

    https://msdn.microsoft.com/en-us/library/office/ff955226(v=office.14).aspx


    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    Friday, January 13, 2017 12:41 PM
  • Thanks, Dennis, I'll review this in a bit.

    Hi Paul,

    The error I posted is what pops up when I try to activate the uploaded template. Yes, I mistakenly only looked at the manifest.xml file. What I did now was a findstr within the folder, and found that the file is referenced from the Feature.xml file located in PremierWednesdayTemplateListInstances\, which is the location pointed to in the error. The following is the line from this XML file:

    <ElementFile Location="resources\resources.en-US.resx" />

    The location is valid, and the file is there as well.

    Friday, January 13, 2017 3:05 PM
  • Hi Paul,

    So I read another suggestion that accomplishes my goal. Basically, it sounded like having two lists, one with the site 'variables' (placeholders), and the other containing the list of subsite 'offices'. And finally, we flow (workflow?) that would create the subsite based on the content added to the latter. Would you recommend this approach? Thanks.

    -Rudy.

    Monday, January 16, 2017 4:51 PM
  • I'm not sure what that solution has to do with a resource file not being found in a .WSP when you deploy it.  But if it accomplishes your goal then that's fine.

    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    Monday, January 16, 2017 9:29 PM