Hi All, When I am applying wsp file (Which I taken from other system) to a new site collection. It giving the following error. The template you have chosen is invalid or cannot be found. at Microsoft.SharePoint.Library.SPRequestInternalClass.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId) at Microsoft.SharePoint.Library.SPRequest.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId)

how are u installing the template ? using stsadm or sharepoint gui ?

I deployed backup.wsp file with STSADM command and it deployed globally. I am able to see in Solution Management as deployed FYI. Now by using backup.wsp I am creating site collection from Central Admin at that time I am getting this error.

check this link http://blogs.neudesic.com/blogs/jason_noble/archive/2007/08/17/15364.aspx hope this helps

Hey Talhak, I am Kishores colleague. No, the link didn't really give us a clue. It is hard to figure out what template that is giving us the issue. which one is invalid? why is it invalid?

the template you select exist or is a custom one? André Lage Microsoft SharePoint, CRM and Sybase Consultant Blog:http://aaclage.blogspot.com Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/

http://www.coderetard.com/2009/02/11/sharepoint-template-error-the-template-you-have-chosen-is-invalid-or-cannot-be-found/ try this...obviously the template you are using is invalid...go to the link and download the tool it says and lemme know if it is of any help..

the template you select exist or is a custom one? André Lage Microsoft SharePoint, CRM and Sybase Consultant Blog:http://aaclage.blogspot.com Codeplex:http://spupload.codeplex.com/http://simplecamlsearch.codeplex.com/ The template we use are custom created ones with lists and libraries set up with custom views, but using applications like documentlibraryreview.wsp. Those webapplications are already installed on the system when deploying our custom wsp.

yes Andre we are using custom one. I have a collection of sites, which I need to give to my client in the form of wsp files (They need in WSP). it is going to consists 4 sites. What I am doing is: By using SharePoint Solution Generator I taken 1st site's wsp file and I went to other system (for testing) and I deployed wsp file. For the first site I am not getting error but when I am deploying 2nd site I am not getting error but when I am creating site collection based on 2nd site's wsp I am getting this template error Please suggest me.

I tried SPInspector and checked template but they are fine. Please see my below post to what I am doing clearly

Hi, You need to be carefull when using VSeWSS with publishing sites the documentation says the following "Note that round tripping of generated sites is not supported for anything but the simplest of sites. Instead some editing may be required , lol? The VSeWSS Documentation is here http://www.microsoft.com/downloads/details.aspx?familyid=FB9D4B85-DA2A-432E-91FB-D505199C49F6&displaylang=en I don’t use VSeWSS due to the ugly XML it generates, its a lot better than it was when it first came out in 2006, but the Site Defs it gens are so convoluted its faster to start with a Site definition like Publishing, Copy it rename make your additions, modifications etc, and package in a wsp. There are a couple of tools that will really help speed things along WSPBuilder, SharePoint Shushi Rocks and there is another tool that will get you everything you need and the XML is much cleaner.. WSPBuilder http://wspbuilder.codeplex.com/ Sushi http://sushi.codeplex.com/ SPExplorer http://spexplorer.codeplex.com/ specifically for saving List definitions, Sites Definitions (All Things XML) Cheers, -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

Hi Ivan Sanders, Thanks for yourr reply, Sushi seems not going to help me in making wsp file. Actually client need in WSP format. How can I use WSPBuilder to build wsp of my whole site collection. Please tell me

There are a couple of issues with what youb are discussing: One issue is one of developing vs solution generation. Generators of all types for all languages have been around for a long time but do not replace the ability to code. Typically the client is reponsible for Content and we wouldnt package "Content" of a site collection. You would Package the parts of the site collection that arte unique (Not OOB) and need to be deployed for the Site Collection to function. Typically all of the branding, site & list definitions, Ctypes, SiteColumns, WFs, event receivers etc should be part of the solution package. If you are looking for content deployment then SharePoint Content Deployment can be used to copy the Site Colection DEV to PROD and keep them in sync after the unique development artifacts have been deployed.. -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.