Microsoft SharePoint Team Blog

Even the new instructions to install the templates might as well be in short hand, can somebody please supply a comprehensive install post that does not assume almost everything?

Lawrence has just posted the completion to the Completing the "Fantastic 40" – 20 remaining application...

All 40 application templates are now available for download from Microsoft, this is composed of 20 Site...

I get an "Object reference not set to an instance of an object" error when I try to add the applicationtemplatecore.wsp using the stsadm - o addsolution command.

Also, what does step 3  "Select the solution file, ApplicationTemplateCore.wsp, from the extracted distribution". mean? Does this mean that you select the file and copy it somewhere specific, or does it just mean that you note the file name for use in your command line statement?

I'm sure I'm missing something very obvious, but it's pretty frustrating.

I'm trying this, too, and keep getting the error:

"ApplicationTemplateCore" does not exist in the solution store.

after the deploysolution step.

Does anyone know what is causing this?

We have a standalone WSS 3.0 server.

I followed the updated installation guide and it worked without a hitch.

I didn't even have to run steps 7 and 8 to install the server admin application templates.

I followed the included readme_stp to install the .stp files without an issue either.

I've tried everything but I get a very informative "Command line error" error message when I run the first command (ie addsolution). I tried copying the files to the BIN folder, I hve admin privelages, etc, etc...nothing.

So, basically, I'm giving up on these templates. Oh well.

Anybody got an answer to the very good questions above. I think the documentation is very poor indeed including the above updated version

I cannot make sense of step 3 and running step 4 produces syntax error. I have tried to place the WSP file in various locations and specify the path after the -filename including the ..\bin location(no path as others have suggested) without success. is there specific location the ATC.wsp needs to be placed after extraction?

What is the point of selecting something but not doing anything with the file??

Hi...

I got command line error weverytime I paste the thinggy....to addsolution....it sux...

Think i got the addsolution to work,,,

must type in manually instead of pasting

STSADM.EXE -o addsolution -filename ApplicationTemplateCore.wsp

take note it is caps in front...wonder why....

I got STSADM.EXE -help addsolution to work 1st before trying this out....

=)

Hi I've downloaded the 40 templates for Windows Sahrepount Services 3.0 but when I want to Install them I kind of get lost :P the problem I have is with the step: "Pull the solution file, ApplicationTemplateCore.wsp, from the extracted distribution. This solution file will be added to the solution store, a table in the Windows SharePoint Services configuration store that holds solution files." So then I can "Via command line, run stsadm –o addsolution –filename ApplicationTemplateCore.wsp", please cpould you help me I have really no idea on what is the solution store...please some help .... my mail es johana85@gmail.com. I would really appreceate some help.

 I installed all 20 server admin templates

and it opration sucessful

bot application tab for template selection not seen in the tab section

but i installed site admin templates and custom tab for this template selection see on the tab

please help and give a solution

If anyone is having the problem where the jobs just sit in the Solutions Managment page and do not get deployed, try executing this command:

stsadm.exe -o execadmsvcjobs

When I add the .WSP Templates to the WSS system, it won't register the template with a Template ID. Like:

SportLeague - Language: 1033 - Site Template: _GLOBAL_#0 - Template Id: 1

I use _GLOBAL_#0 to provision WSS sites. Can this be done? Because when I use "stsadm -addtemplate -filename <template.wsp> -title <Template Title>" I'm getting a Parse error.

Mark

Well I installed a template. And according to sharepoint it was fully deployed. Even when I look in sharepoint I see that it states that it has been deployed. So I thought well everything is okay, well no. As stated I can now create a new site with this template. So I follow the instructions to create a site with the new template but as soon as I click create it starts ratteling and then I get an error message that has more letter and numbers in it then I can write down. And that is all I can find on the error. Even in the log it just states the error. I just can not find out what the error means. Anyone got any suggestions?

All 40 application templates are now available for download from Microsoft, this is composed of 20 Site

These are the worst instructions I have ever seen.

Point

3.     Select the solution file,

[What does this mean? Select the file? Right click? Click on?? Nothing works......]

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

[How can it be added if you can't select it??]

4.     On the Windows command line,

[Where is this???? Do you mean - Click The Start Button? Then Run? Then Type the Command? Still dosen't work.]

run "stsadm -o addsolution -filename ApplicationTemplateCore.wsp".

As I said - worst instructions ever.

Thank you Bala - my error was "Command line error." but your line worked!!!!

BTW: I had also copied the wsp file(s) to the bin directory and was running the command prompt in bin.

Once again, MS people should be dragged out into the sunlight every few months and forced to breathe real-world air.  How farking hard is it to write an instruction set for a *clean* SPS 3 install???

I've only been doing Sharepoint stuff for about a month now, so I guess I could have a fresh spin on this as I did also struggle....

When it says you have to run the command:

stsadm –o addsolution –filename ApplicationTemplateCore.wsp

What it is taking for granted is that you have added the file path to stsadm.exe into your Envirnmental Variables of windows. To do this follow these steps:

click START>CONTROL PANEL>SYSTEM

on the system properties page click the ADVANCED tab at the top, then at the bottom click ENVIRONMENT VARIABLES.

On the new window (Environment variables funnily enough) under SYSTEM VARIABLES scroll down until you see the entry for PATH. Click PATH and then EDIT underneath it.

Leave the VARIABLE NAME as it is and scroll to the end of the VARIABLE VALUE entry. at the end add the following (including the ; symbol)

;C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\WEB SERVER EXTENSIONS\12\BIN

What this does is let you run any executables in that folder from any other folder in a command line :0)

2007 MOSS Resource Links (Microsoft Office SharePoint Server) Here is an assortment of various 2007 Microsoft

"Command line error" ..... TOO BAD........ :(

I've installed an Application  Template Core Solution but have an error while deploying it. Maybe in the server farm config. I've tried to uninstall it but it still in the system. I've tried uninstalling the sharepoint and the .net itself, but still, when i've installed the application template core, it produces an error sayin that the application template core is running. How can I uninstall this application template core completely. ? Please help.

"command line error"

I had the same problem.

More then likely you are using the wrong command.

The command is CaSe SeNsItIvE!

when you T-Y-P-E the command stsadm, make sure it is ALL CAPS!

STSADM.exe -----------> CORRECT

stsadm.exe -----------> NOT CORRECT

Also, make sure you are in the right folder:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm

I want to remove the ApplicationTemplateCore and do the reinstall again.  How is that done?

STSADM.exe and dont cut and paste..

thanx everyone

I have deployed the core, first under -immediate, then redeployed under -local.  When I run enumdeployments I get 0 returned, and the application tab is not present when creating sites.  ApplicationTemplateCore.wsp is globally deployed in the admin console.

I'm at a loss on how to proceed.  Any ideas?

I had the same command line error problem, the solution for me was to execute stsadm within the directory where ApplicationTemplateCore.wsp was located.  The command stsadm -o addsolution -filename c:\tmp\ApplicationTemplateCore.wsp doesn't work.

So there are a few issues here:

1. if you are not a developer or a sys admin - which alot of times Sharepoint people are not, you probably don't know about the commandline and directory paths etc... (unless you had a commador 64 as a kid) so the whole thing about the environment variable and having the wsp file in the same directory as the STSADM.EXE file - might be a bit hard to grasp but if you read about environment vars and running batch files you will get it. Basically this is the deal:

The wsp file needs to be in the smae location as the stsadm.exe file and you need to be in the dir where they are when you give the command.

2. There is also the issue with the "typing" the command rather than pasting it. That part is critical - the paste seems to mess up the hyphen character. - So once I fixed all the hyphens in my bat file - things worked great!

Yes the documentation leaves a bit to be desired but it's really more a matter of understanding what you are trying to do.

The first statement

STSADM.EXE -o addsolution -filename ApplicationTemplateCore.wsp seems to be putting the solution into the "store" (whatever that means)

the second statement

STSADM.EXE -o deploysolution -name ApplicationTemplateCore.wsp -immediate -allowgacdeployment

is then deploying that solution - I had to put the full path to my wsp file in the first statement - but NOT in the deploy statement

here is what my bat file looks like:

FOR THE TEPMLATE CORE

STSADM.EXE -o addsolution -filename ApplicationTemplateCore.wsp

STSADM.EXE -o deploysolution -name ApplicationTemplateCore.wsp -immediate -allowgacdeployment

and FOR THE TEMPLATES:

STSADM.EXE -o addsolution -filename wsps\AbsenceVacationSchedule.wsp

STSADM.EXE -o deploysolution -name AbsenceVacationSchedule.wsp -immediate -allowgacdeployment

The wsps\ bit is because I put all the wsp files in a directory  named wsps notice that it is missing from the deploy statment - because that one is looking for it by name in the "store"

Hope this helps instead of making it more confusing

Just a quick note, well done on the hyphenation thing.  solved the problem

Hi Prabhat,

You are getting command line error because the %20 is interpreded by the command line as a parameter; instead replace the whole %20 with an space like this:

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o restore -url "http://devserver:12935/departments/Business Technology" -filename  D:\temp\company\BackupMOSSportal\backup_BT.bkp

That should work...

I have this problem where when I try and load a template, it gives me the following error:

Object reference not set to an instance of an object.

d:\templates\applicationtemplatecore.wsp: The Solution installation failed.

I see this is a little bit common, but no one seem to know how to fix it, can someone help?  Thanks!

After following all of the tips, I am still receiving errors. the addsolution operation is not even an option when I request help. There is addpath or addtemplate, but no addsolution. Any ideas?

Command Line errors here too, seems pasting command in is nto a good idea, typing them in works. Go MS!! Programming Idiots! They need to work in the real world once in a while.

The SharePoint command-line utility stsadm.exe was driving me crazy for the last two days. I'm automating

making the stsadmin to upper case work for me..

STSADM.EXE -o addsolution -filename ApplicationTemplateCore.wsp

Strange, why case should be a problem in WINDOWS that too in EXE file????

Kevan Broderick Thanks, you has solved the problem in my case, replacing the "-" works fine! ;)

It's case sensitive for the executable.

Must have been a Linux developer wrote STSADM.  

STSADM.EXE -o addsolution -filename ApplicationTemplateCore.wsp

It is case sensitive and after deploying the templates it should be activated at Site Action > Site Administration > Site features....

But I have one more question. How to get User Login Name in Form Authenticated site using WSS object model. I am getting the login name in SPUserCollection, but not the logged-user Name.

"addsolution" is not a valid option for my stsadm.exe, STSADM.exe or STSADM.EXE file.   Of course they're all the same file. ;)

I have "addalternatedomain", "addpath", "addtemplate", "adduser", "addwppack" and "addzoneurl" but "addsolution" is not part of my particular exe file according to its own help statement.

how is it that MY fresh install of SBS2003 and subsequent upgrade to Sharepoint 3.0 doesn't have a /12/ directory either?  Mine is /60/bin/ to find the stsadm.exe file.  

why oh why must MY installations always be THE EXCEPTION?   WTF where is my /12/ directory?   I have /50/ and /60/.   nothing more.