Microsoft SharePoint Team Blog

PingBack from http://www.virtualassist.net/blog/2007/02/21/completing-the-fantastic-40-%e2%80%93-20-remaining-application-templates-now-available/

Well the rest of the fantastic 40 has been finally released. These are 20 server admin templates...

Finalmente Microsoft ha liberado las 40 plantillas llamadas "Fantastic 40", para crear sitios de...

TemplateCoreSolution and Template installation was successful, i see application templates section in new site templates and everything, but when i tried to install helpdesk.wps, i ended up with following error:

"Feature '75a0fea7-12fe-4cad-a1b2-525fa776c07e' is not installed in this farm, and can not be added to this scope."

What's wrong?

The new Application templates look great. I didn't have any trouble deploying them however you should have mentioned in the readme that after deploying the solution it requires an iisreset (or at least a cycle of the WSS application pool) before the templates are available for site creation. Also once the core application is deployed and the solutions added the rest of the deployment can be managed from Central Admin operations, which some may prefer (these are web applications after all!)

Comme aprés chaque conférence MS, les choses bougent un peu polus vite et plein de bonne choses arrivent

I bet you are! Something slipped by, and if you follow my help here, you should be back on the right...

I cannot get the templates installed.  The readme is absolutely no help.  I got the ApplicationCoreTemplate.wsp installed.  I get the following

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

dm -o addsolution -filename AbsenceVacationSchedule.wsp

Command line error.

Usage:

          stsadm.exe -o <operation> [<parameters>]

          stsadm.exe -help [<operation>]

It looks like your .wsp files are not in the path.  You will need to specify the exact path to them such as C:\Templates\AbsenceVactionSchedule.wsp instead.

WSS 3.0 could be the most significant product out the stable door this year – it has the potential to change the whole end user computing experience and finally deliver on the Cairo vision.

I did an end user demo of WSS today and it’s the first time in years I’ve had someone get excited enough to ask me to leave my laptop behind for them to play with.

In contrast with the excitement I have about the platform the 20 application templates are a huge disappointment.  After spending some time to get them all installed and working through a good 8 to 10 of them there is hardly anything of interest or reusable value to me. In other words they add very little to a base WSS 3.0 install that I would reuse.

The contact tracking template seems nothing more than a sample list – hardly something to waste 15 minutes to install.

Ironically the bug tracking sample is buggy !!!  Click on the resolve icon and you get:

“An error occurred during the processing of /bugs/Lists/Bugs/Resolve.aspx. The resource object with key 'ResolveBugPageTitle' was not found.”

In short I think the application templates fall short of the vision of being used as a starting point for solution builders and end user created solutions.

In my view the time would have been spent better completing the documentation on MSDN / Technet so we can build our own solutions.

(UPDATED 2/23: Added -allowgacdeploy to step 2. I didn't need it, but more than one person posted/contacted...

Microsoft ha liberado las plantillas faltantes del conjunto de plantillas para SharePoint 2007 llamadas

Hard to know exactly how and what the templates are demonstrating.  is there something written somewhere that is a bit more detailed than that offered by the download page?

tx

Here is an assortment of various 2007 Microsoft Office SharePoint Server Documentation / Reference Materials...

The CKS:UGE was pre-announced just this past Wednesday, and the Release Candidate has already been downloaded

What's the differences between Hele Desk and Call Center application?

To add HelpDesk.wsp template

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

dm -o addsolution -filename \\servername\users\administrator\helpdesk.wsp

Operation completed successfully.

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

dm -o deploysolution -name helpdesk.wsp -allowgacdeployment -immediate

Timer job successfully created.

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

dm -o execadmsvcjobs

Operation completed successfully.

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

Instructions for use:

1. Log into your SharePoint site as the site

  Administrator.

2. From the Site Actions drop-down menu in the top right,

  select Site Settings.

3. Under the Site Administration section, select Sites

  and Workspaces.

4. Select Create to create a new site using a site

  template.

5. Complete the new SharePoint site information. In the

  Template Selection section, select the Application

  Templates tab. All deployed Application Template will

  be listed in this tab.

6. Select the template to use for this site and click

  Create.

7. A site has now been created using the application

  template.

I've installed the Application Template core and a Knowledge Base Template, but when I follow the 3rd part of the readme instructions there is no Application Templates tab to use the new template.

If I try to install them again I am told they already exist. Any suggestions?

Here is a helpful little batch file I wrote for installing all those WSP files.

::install.bat for WSP Template files

::Created by Will Pritchard

:START

@ECHO OFF

SET /P INPUT="Please enter the name of the .wsp file you want to deploy: "

ECHO.

ECHO Starting deployment of %INPUT%

:CHOICE

SET /P CHOICE="Are you sure you want to continue? (Y or N): "

if %CHOICE%==Y goto YES

if %CHOICE%==y goto YES

if %CHOICE%==N goto NO

if %CHOICE%==n goto NO

ECHO %CHOICE% is not recognized.  Please re-enter your answer.

goto CHOICE

:YES

ECHO Adding the Solution.

stsadm -o addsolution -filename %INPUT%

ECHO Executing service jobs.

stsadm -o execadmsvcjobs

ECHO Deploying the Solution.

stsadm -o deploysolution -name %INPUT% -immediate -allowGacDeployment -allowCasPolicies

ECHO Final Execution processing.

stsadm -o execadmsvcjobs

GOTO END

:NO

EXIT

:END

ECHO All Done!

:MORE

SET /P MORE="Want to install another solution? (Y or N): "

if %MORE%==Y goto START

if %MORE%==y goto START

if %MORE%==N goto NO

if %MORE%==n goto NO

ECHO %CHOICE% is not recognized.  Please re-enter your answer.

goto MORE

To confirm, there is a bug with the 'Room and Equipment Reservations' template which means that the Reservations screen displays in US date format regardless of what Regional settings are on your site.

Deeply frustrating as we're very keen to implement.

I don't get it. I installed the server and site templates as described everywhere without any error. However I don't see the extra tab in de Template selection Area..... What am I missing? I use a Dutch MOSS 2007.

Regards, Mike

These Master Pages were originally scheduled to be released with the Applications Templates a couple

Hello I have installed 20 Admin Templates. All works find, but I have a problem: I have create a "Budgeting and Tracking Multiple Projects" and I can create or delete Columns in all List of the site, but in the New Form page the new column doesn't appear...I only can fill this column in the "data view"...anyone know why It could be????

Thank you to Will Pritchard (on March 14, 2007) I created this bath file that install all Templates:

Be sure you are in the directory (folder) where all the templates are located. Create a batch file with the following content:

PATH = %PATH%;C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

stsadm -o addsolution -filename helpdesk.wsp

stsadm -o deploysolution -name helpdesk.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename AbsenceVacationSchedule.wsp

stsadm -o deploysolution -name AbsenceVacationSchedule.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename BudgetingTrackingMultipleProjects.wsp

stsadm -o deploysolution -name BudgetingTrackingMultipleProjects.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename BugDatabase.wsp

stsadm -o deploysolution -name BugDatabase.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename CallCenter.wsp

stsadm -o deploysolution -name CallCenter.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename ChangeRequest.wsp

stsadm -o deploysolution -name ChangeRequest.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename ComplianceProcessSupport.wsp

stsadm -o deploysolution -name ComplianceProcessSupport.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename ContactsManagement.wsp

stsadm -o deploysolution -name ContactsManagement.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename DocumentLibraryReview.wsp

stsadm -o deploysolution -name DocumentLibraryReview.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename EventPlanning.wsp

stsadm -o deploysolution -name EventPlanning.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename ExpenseReimbursementApproval.wsp

stsadm -o deploysolution -name ExpenseReimbursementApproval.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename InventoryTracking.wsp

stsadm -o deploysolution -name InventoryTracking.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename ITTeamWorkspace.wsp

stsadm -o deploysolution -name ITTeamWorkspace.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename JobRequisition.wsp

stsadm -o deploysolution -name JobRequisition.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename KnowledgeBase.wsp

stsadm -o deploysolution -name KnowledgeBase.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename LendingLibrary.wsp

stsadm -o deploysolution -name LendingLibrary.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename PhysicalAssetTracking.wsp

stsadm -o deploysolution -name PhysicalAssetTracking.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename ProjectTrackingWorkspace.wsp

stsadm -o deploysolution -name ProjectTrackingWorkspace.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename RoomEquipmentReservations.wsp

stsadm -o deploysolution -name RoomEquipmentReservations.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

stsadm -o addsolution -filename SalesLeadPipeline.wsp

stsadm -o deploysolution -name SalesLeadPipeline.wsp -allowgacdeployment -immediate

stsadm -o execadmsvcjobs

Feature '75a0fea7-2791-45a2-896f-e538f91032d8' is not installed in this farm, and can not be added to this scope.

Anyone know how to fix this?

(UPDATED 2/23: Added -allowgacdeploy to step 2. I didn&#39;t need it, but more than one person posted

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

You have to install the Application Template Core solution before you can install the template. This can be found at:

http://go.microsoft.com/?LinkId=5922037

Both the core solution and the bug database template use the same command line arguments:

stsadm –o addsolution –filename ApplicationTemplateCore.wsp

stsadm –o deploysolution –name ApplicationTemplateCore.wsp -allowgacdeployment

stsadm –o addsolution –filename BugDatabase.wsp

stsadm –o deploysolution –name BugDatabase.wsp -allowgacdeployment

Once those two things job timers are created you can force them to run by typing stsadm.exe -o execadmsvcjobs.

The last step needed would be to copy all the contents in the application bin folder. To do so type:

stsadm -o copyappbincontent

The template should now be installed and good to go...

I'm finding that when you move a site that was created from the Knowledge Base application template from one MOSS 2007 / WSS 3.0 server to another MOSS 2007 / WSS 3.0 server, that some of the links do not correct themselves to the new URL.  This causes the actions of "Write an Article" and "Upload a Document" to fail, or to try to use the old location to perform these tasks.  The URL's reference a GUID which does not exist at the new location.

What is the supported/recommended method for moving a site that was created with the Knowledge Base template?  I've tried both stsadm -export and backup/restore to the new location using SharePoint Designer.

Thanks in advance

David

Wieder mal ist eines der Fantastic 40 Webtemplates genauer analysiert worden: die Sales Pipe Line The

Has anyone else noticed that if you create a folder in a KnowledgeBase site - and enter the folder and "Write An Article"... that the created Article is placed at the root of the site instead of your current location (for example inside a particular folder)?

This is extremely annoying for users to have go back to the root and manually move the file to the correct folder using Explorer.

When you upload documents - they go to your current location.  But created articles do not.

Does anyone have a solution?

Looks like a quiet week on the SharePoint weekly.... Amanda shows us how to Creating a Template Part

Very nice.  These are great for getting business processes up quickly.  I just installed all 40 templates and took screenshots of them in case someone wanted to look at them all in once place.

http://bluesurftech.com/TechBlog/Lists/Posts/Post.aspx?ID=28

Miles Kan

Error : Feature '75a0fea7-2791-45a2-896f-e538f91032d8' is not installed in this farm, and can not be added to this scope.

My cause of this error, was because I had deleted the wsp templates from a temp location after installing, thinking they were no longer needed.  After retrieving them from the recycle bin I could add site templates ok.

Finally what helped to us is as following:

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)Copy ApplicationTemplateCore.wsp file in to

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

4)Click on Start

5)Click on Run

6)Type Cmd

7)Type CD C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

8)Type(Don't paste, that would not work)following command

STSADM.EXE -o addsolution -filename ApplicationTemplateCore.wsp

Enjoy!

Pankaj.sharma@kairaus.com

Kairaus

Kairaus, YOU ROCK!

Reservations are disappearing from the reservations list once the end date has passed. I can't find any setting that would cause this behavior. I want to keep a historical record of what was borrowed, by whom, and when. Reservations are not deleted from the reservation calendar but a list with fields I can sort on is much more convenient. Anyone else experience this behavior?

Room reservation template: Has anyone had this same problem ? Could you fix it ?

The reason you are getting the "Feature not installed" is because the ApplicationTemplateCore.wsp needs to be installed first.  Do this and the rest of your templates will work correctly.

You'd think after a year you would see more of these...

Is there a fix planned for the bugs that cause:

http://www.sharepointblogs.com/sean/archive/2007/09/13/designer-export-fails-with-quot-guid-should-contain-32-digits-quot-error.aspx

I've been playing with content deployment / importing / exporting - and even running through the fixes as listed above, I get the same errors.   Export works, but can't seem to get the import to work again.

Content deployment (simply moving the sites) fails with the same guid errors.

Is there something I'm missing here?

I added this command: stsadm -o execadmsvcjobs

And it worked after that.  This was not on the readme.txt, but I needed it to get it working.

THanks

<quote>Re-type the hyphens for the switches... if you copied/pasted the syntax from the help doc, CMD interprets that character that LOOKS like a hyphen as a ú </quote>

thank you Sean T. thank you - thank you - thank you - thank you

Some of these templates are terrible - specifically the HR / Benefits template.  Creating 4 document libraries and putting them in a web part page does not constitute a revelation in SharePoint templates.

Also - the readme is TERRIBLE.  A lot of people aren't going to know what to do with the .sts files and the difference between that and a .wps file.

Please update the documentation a little better.  You also might want to mention for folks who don't know where the stsadm.exe is.  It didn't autmotically get put into the PATH on my install.

Please double check this stuff before you post it.  We give you a lot of credit that you won't release it if it's a half effort.

Excelente lista de recursos creada por Joel Oleson http://blogs.msdn.com/joelo/archive/2007/10/12/sharepoint

Information Security and Use Policies Samples Configuration Management Considerations (blog post) Tips