SharePoint: Installation Guide for Application Templates

Did you download the 40 Application Templates for SharePoint? And did you try to install them? If you haven’t then you must rejoice! There are some issues and you do need the installation guide. 😉 Lets look at how you can install these fantastic templates.

=========================================================

To install the Application Template Core solution:

=========================================================

To deploy the Application Template Core solution on a server running Windows SharePoint Services, follow these instructions below. Note that in order to complete the following installation, you must have Administrator rights to both the Windows SharePoint Services site and server on which it is to be installed.

1. Download the solution .EXE file to your computer.

2. Run the .EXE file to unpack the template file to a location on your computer.

3. Select the solution file, ApplicationTemplateCore.wsp, from the extracted distribution. This solution file will be added to the Windows SharePoint Services solution store.

4. On the Windows command line, run “stsadm -o addsolution -filename ApplicationTemplateCore.wsp”.

5. Next, run “stsadm -o deploysolution -name ApplicationTemplateCore.wsp -allowgacdeployment”. Additional attributes may be required based on your Windows SharePoint Services configuration. For example:

· Standalone: [ -local | -time <time to deploy at> ]

· Farm: [ -immediate | -time <time to deploy at> ]

6. Then run “stsadm -o copyappbincontent”.

7. The Application Template Core solution has now been added to the solution store and deployed on the server.

=========================================================

To install a server admin Application Template:

=========================================================

Each server admin Application Template is deployed in the Windows SharePoint Services environment as a solution. To deploy a solution on a server running Windows SharePoint Services, follow these instructions. Note that in order to complete the following installation, you must have Administrator rights to both the Windows SharePoint Services site and server on which it is to be installed.

1. Before installing any Application Template, you must first install the Application Template Core solution, ApplicationTemplateCore.wsp. If you have already installed this solution, proceed to Step 2. Otherwise, go here to download the Application Template Core solution:

2. Download the application template solution EXE file to your computer.

3. Run the EXE file to unpack the template file to a location on your computer.

4. Select the solution file, <template_name>.wsp, from the extracted distribution. This solution file will be added to the Windows SharePoint Services solution store.

5. Via command line, run “stsadm -o addsolution -filename <template_name>.wsp”

6. Next, run “stsadm -o deploysolution -name <template_name>.wsp -allowgacdeployment”. Additional attributes may be required based on your Windows SharePoint Services configuration. For example:

· Standalone: [ -local | -time <time to deploy at> ]

· Farm: [ -immediate | -time <time to deploy at> ]

7. To check deployment status by browsing to WSS Central Administration, click the “Operations” tab and then click “Solution Management” under Global Configuration.

8. After the solution is marked “Globally deployed,” run “iisreset” from the command line.

This was the official installation guide from MS SharePoint Team Blog

Now lets look around the web for some other work around, before MS STB came up with this guide. ….

Dustin Miller shares his expertise on how to get around the installation dramas! In his update, he has Added -allowgacdeploy to step 2.

Follow these instructions, and you should be golden. These steps assume that you’ve already opened a command prompt and navigated to the directory where your WSP files are (and that all of them are in the same directory). It also assumes that stsadm.exe is in your path. Finally, these steps assume you downloaded the package that contains all of the server admin templates, since there is a required WSP, applicationtemplatecore.wsp, that seems to be missing from some of the individual downloads. Unfortunately, you need to register to download the correct package (BOO!).

  1. stsadm -o addsolution -filename applicationtemplatecore.wsp
  2. stsadm -o deploysolution -immediate -allowgacdeployment -name applicationtemplatecore.wsp
  3. (I’m doing these first because they are dependencies, though honestly, you could probably get away with skipping down to step 7, and coming back to step 2 before you run step 9. If that’s not clear, just move on to step 4. :P)
  4. Open your browser to Central Administration, click the Operations tab, and then click “Solution management” on the right site, under “Global Configuration”
  5. Verify that the “applicationtemplatecore.wsp” solution is marked as “Deployed”. If it’s not, wait ten more seconds or so, and refresh again to see if it’s finished. Once it’s “Deployed”, move on.
  6. Back to the command prompt!
  7. for %f in (*.wsp) do stsadm -o addsolution -filename %f
  8. You’ll see an error when it tries to add the applicationcoretemplate.wsp solution (since it’s already there) — ignore it. Once it’s done, move on to step 9.
  9. for %f in (*.wsp) do stsadm -o deploysolution -allowgacdeployment -immediate -name %f
  10. And wait. Go get a cup of coffee. This can take anywhere from a minute or so with super-fast hardware to ten or more minutes with slower boxes. When you come back, go back to your browser and refresh that Solution Management page. Once the timers are finished running — you might have to refresh a few times over a few minutes to verify this — you may find some solutions that didn’t deploy, or that had an error deploying. You can re-run the command line in step 9 if you want (you’ll just get quick errors on the ones that are already deployed, it’s safe to ignore them), or manually deploy the solutions using your browser.

Thank you Dustin. You rock!

UPDATE: I have written a script here to do all of this at one go.

Alpesh Nakar

23 Replies to “SharePoint: Installation Guide for Application Templates”

  1. I get stuck at this step:

    4. Select the solution file, .wsp, from the extracted distribution. This solution file will be added to the Windows SharePoint Services solution store.

    How does the solution file get added to the windows share point services solution by just selecting. Are there step by step instructions with screenshots

  2. Why doesn’t my stsadm.exe work. I also always get command line error messege when i run the command stsadm –o addsolution –filename ApplicationTemplateCore.wsp. Please help

  3. Hi, I have used the “stsadm -o addsolution -filename ApplicationTemplateCore.wsp” string and the status in Central Administration\Solution Management shows staus = error deployed to none… Can you point me in any direction to rectify this.

  4. Hope someone can help. I’m trying to install the ApplicationTemplateCore on small business server 2003 r2. I have seen examples of how to do this by going to:

    \program files\common files\microsoft shared\web server extension\12\bin

    and running the stsadm command there. The problem is I don’t have a “12” folder, I have a “50” and “60” folder; the “60” folder has stsadm.exe in it, but the command “addsolution” is not available. I’ve done all updates for sbs 2003 r2.

    What do I need to do?

    PS I am by no means an IT pro, just a regular guy trying to keep a business going.

  5. Hi Charley,

    Thanks for your comment. I have now fixed the dead link. Having moved provider, I still have few issues to sort.

  6. I keep getting this error when deploying the expensereimbursementapproval template:

    SERVER : Error: The creation of this directory failed: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\ERListInstances.
    This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again.
    SERVER : This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again.

    Any help is appreciated.
    Jack

  7. Is the same steps applicable for Sharepoint 2010? Since I have added both applicationtemplatecore.wsp and my custom wsp. While creating site I cannot see the application template tab whereas I can see that in Central Administration

  8. Hi,

    I followed instructions very similar to yours to install a HelloWorldWebPart.wsp file. The solution shows on the Solution Management page within WSS Central Administration site. Yet, when I try to use the web part in a page I cannot see it; I only see the 14 web parts the site had originally.

    Any suggestion on what step is missing to make the web part visible when I use the Edit Page command in SharePoint?

    Thanks in advance

  9. Hi,

    I downloaded these Application Templates and installed step-by-step as this article stated. While creating a new site, i can also see the Application Template (newly deployed) tab, but when i select that Application Template and try to create the site, it shows me an error. Following are the details of that error, can you please help me ASAP (would be good if you reply at my email address, saadumair@gmail.com) in this regard. (please note that i’ve installed these Application Templates on MOSS 2010 Beta)

    Error
    Cannot complete this action.

    Please try again.

    Troubleshoot issues with Windows SharePoint Services.

    Correlation ID: c184c56d-899c-4add-bf25-8102e1fab8e4

    Date and Time: 3/20/2010 11:40:32 AM

  10. I keep getting “Access Denied” when I run the wsp script. I never had this problem before at my old job. This new job is using VMWare and Win2k8.

    Any ideas?

Comments are closed.