SharePoint Cheat Sheet

How to create custom 404 error pages for MOSS applications?

2009-03-10T08:20:00.000-07:00

Based on my scenario. I had couple different applications and I was needed to specify different custom 404 error pages under each one. In order to implement it you need to follow steps below.

1. By default you can find error page under location below:

%systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\LangID - sps404.html

2. Make two copies of this page and paste under the same location.

3. I assumed that you have by this time two custom pages you. In IIS under each application create Virtual Directory. For example "Custom Errors" and paste your custom build error pages in each application.

4. Than go to step 2 and make changes in each page (copied from sps404.html)

Change the name of the page:

STSNavigate("/_layouts/spsredirect.aspx?oldUrl=" + requestedUrl);

To:

STSNavigate("/_layouts/NameofYourCustomErrorPage.aspx?oldUrl=" + requestedUrl);

Save it (Do the same for both pages)

5. Time to use CodePlex application (you can download SharePoint Manager 2007 here).

Run it. Select Application you need. In the properties window find the field - FileNotFoundPage and paste the name of error page (copied from sps404.html). Do that for both applications and save it. That's it - You all set.

_________________________________________________________________

Microsoft suggest follow steps below. You can find original article here.

How to point to a custom 404 error Web page in Windows SharePoint Services 3.0 or in Microsoft Office SharePoint Server 2007

To configure Windows SharePoint Services 3.0 or SharePoint Server 2007 to point to a custom 404 error Web page, follow these steps.

Note Because of a design limitation, the custom 404 error Web page does not work when you access invalid site collections.

Log on to the computer that is running SharePoint Server 2007 by using an account that has administrative permissions.
In Windows Explorer, locate the following folder:

%systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\LangID

Notes

In this path, %systemdrive% represents the actual drive name of the drive on which the operating system is installed.
In this path, LangID represents the actual language ID of the language that you use. For example, 1033 is the language ID for U.S. English.

Create the custom HTML file. To do this, use the appropriate method.

Microsoft Office SharePoint Server 2007

loadTOCNode(3, 'moreinformation');
1. On the computer that is running SharePoint Server 2007, copy the Sps404.html file to a temporary folder.
2. Rename the Sps404.html file. For example, give the file the following name:
  
  Custom404.html
3. Add the custom content to the Custom404.html file.
4. Copy the Custom404.html file to the %systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\LangID folder.
Windows SharePoint Services 3.0

loadTOCNode(3, 'moreinformation');

On the computer that is running Windows SharePoint Services 3.0, locate the existing Error.htm file in the following folder:

%systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\LangID

Notes

In this path, %systemdrive% represents the actual drive name of the drive on which the operating system is installed.
In this path, LangID represents the actual language ID of the language that you use. For example, 1033 is the language ID for U.S. English.

Copy the Error.htm file to a temporary folder.
Rename the Error.htm file. For example, give the file the following name:

Custom404.htm

Modify the Custom404.htm file as required.
Copy the Custom404.htm file to the %systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\LangID folder.

Create a custom console application by using Microsoft Visual Studio 2005 Professional Edition or Microsoft Visual Studio 2005 Standard Edition. Then, add the following code to the custom console application.


// The following code assumes that a reference is made to Microsoft.SharePoint.



Microsoft.SharePoint.Administration.SPWebApplication webapp =

Microsoft.SharePoint.Administration.SPWebApplication.Lookup(new Uri("http://"));

            webapp.FileNotFoundPage = "";

            webapp.Update();

Notes

In this code, <serverurl> represents the actual URL of the computer that is running SharePoint Server 2007.
In this code, <Custom404.htm> represents the actual name that you created for the custom HTML file.

For more information about how to create a custom console application by using Visual Studio 2005, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/ms438026.aspx

(http://msdn2.microsoft.com/en-us/library/ms438026.aspx)

Note By default in Windows SharePoint Services 3.0 and in SharePoint Server 2007, the FileNotFoundPage property is set to the "null" setting.

Run the custom console application on the computer that is running SharePoint Server 2007.

Note By default in Windows Internet Explorer, the Show friendly HTTP error messages setting is turned on. In this case, the custom error page may not appear. For more information about this setting, click the following article number to view the article in the Microsoft

CabLib Compress ERROR: Could not flush cabinet: Could not create cabinet file Title is required

2009-02-09T18:05:00.000-08:00

If you get this error during building WSP it is because your files have “read only" properties. Check Out files (in Visual Studio or another editor) or Right Click folder -> Properties and Uncheck "Read only".
Build WSP again.

The search request was unable to connect to the Search Service.

2009-01-24T14:58:00.000-08:00

In order to resolve this error "The search request was unable to connect to the Search Service.":
1. Go to the server:
Run > Type “Services.msc” - >
- Start a SharePoint search service;
- Start Indexing service;
- IISReset

Sharepoint Service Error: A deployment or retraction is already under way for the solution *.wsp

2009-01-23T06:53:00.000-08:00

Sharepoint Service Error: A deployment or retraction is already under way for the solution *.wsp

To resolve this problem do the next steps:

Click "Start", click "Run" type cmd

The operation below shows you all runnig deploying process:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o enumdeployments

Base on GUI of process you can cancel it. Use next operation for that:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o canceldeployment -id "GUID job ID"

Security Classes

2009-01-13T17:17:00.000-08:00

SPGroup
SPUser
SPRoleAssignment
SPRoleDefinition

Setting Unique Folder Permissions

2009-01-13T17:14:00.000-08:00

SPPrincipal principal = userToAdd;
SPFolderCollection submissions = web.GetFolder("Submissions").SubFolders;
SPFolder newFolder = submissions.Add("testfolder");

SPListItem folderItem = newFolder.Item;
folderItem.BreakRoleInheritance(true);
folderItem.Update();
SPRoleAssignment folderRoleAssignment = new SPRoleAssignment(principal); SPRoleAssignmentCollection folderRoleAssignments = folderItem.RoleAssignments; SPRoleDefinitionBindingCollection folderRoleDefBindings = folderRoleAssignment.RoleDefinitionBindings;
folderRoleDefBindings.Add(roleDefinitions["Contribute"]);
folderRoleAssignments.Add(folderRoleAssignment);

Adding User to a SharePoint Group

2009-01-13T17:13:00.000-08:00

web.AllowUnsafeUpdates = true;
SPGroup studentsGroup = web.Groups["Students"];
SPUser userToAdd = web.SiteUsers["pilothouse\\testgroup"];
studentsGroup.AddUser(userToAdd);
Response.Write("Added user successfully");

Role Assignments For the Site

2009-01-13T17:09:00.000-08:00

SPRoleAssignmentCollection webRoleAssignments =
web.RoleAssignments;

Response.Write("All role assignments in this site: " + "
");

foreach (SPRoleAssignment webRoleAssignment in webRoleAssignments)
{
Response.Write(webRoleAssignment.Member.Name + " "
+ webRoleAssignment.RoleDefinitionBindings[0].Name + " "
+ webRoleAssignment.Parent.ToString() + "
");
}

Role Definitions

2009-01-13T17:08:00.000-08:00

// Role definitions are represented as "Permissions Levels"
// in user interface
SPRoleDefinitionCollection roleDefinitions = web.RoleDefinitions;
Response.Write("All role definitions in this site: " + "
");
foreach (SPRoleDefinition roleDefinition in roleDefinitions)
{
Response.Write(roleDefinition.Name + "
");
}

SharePoint Group Users

2009-01-13T17:05:00.000-08:00

// All users in "Students" SharePoint group
users = web.Groups["Students"].Users;

Response.Write("All users in \"Students\" SharePoint group: " + "
");
foreach (SPUser user in users)
{
Response.Write(user.Name + "
");
}

SharePoint Group Security Principals

2009-01-13T17:00:00.000-08:00

// SharePoint Groups that are Security Principals on this website
SPGroupCollection groups = web.Groups;
Response.Write("All SharePoint groups in this site: "+"
");
foreach (SPGroup group in groups)
{
Response.Write(group.Name + "
");
}

// All SharePoint Groups in this site collection
groups = web.SiteGroups;
Response.Write("All SharePoint groups in this site collection: " + "
"); foreach (SPGroup group in groups)
{
Response.Write(group.Name + "
");
}

Domain User and Group Security Principals

2009-01-13T16:53:00.000-08:00

// All domain users and groups
// that are Security Principals for the website
// This is the list you see in /_layouts/user.aspx
SPUserCollection users = web.Users;
Response.Write("All domain user principals in this site: " + "
");
foreach (SPUser user in users)
{
Response.Write(user.Name + "
");
}

// All domain users and groups within the site collection
users = web.SiteUsers;
Response.Write("All users in this site collection: " + "
");
foreach (SPUser user in users)
{
Response.Write(user.Name + "
" );
}

Security Permission Inheritance

2009-01-13T16:49:00.000-08:00

SPSite site = SPContext.Current.Site;
SPWeb web = SPContext.Current.Web;

// Test to see if the site has unique permissions
if (web.HasUniqueRoleAssignments)
{
Response.Write(web.Title + " does not inherit permissions
" );
}
else
{
Response.Write(web.Title + " inherits permissions
" );
}

Uncustomized and Customized Pages

2009-01-12T06:51:00.000-08:00

Ghosted - Uncustomized
Unghosted - Customized

In WSS v3 pages exist in one of two states: customized or uncustomized. An uncustomized page is one that is listed in the site's contents database, but the actual source of the page (the file) resides on the file system, and the content database simply contains a link pointing to the file. A customized page is also listed in the content database, but the source of the page is also stored in the database. Future requests for that page (in the context of a specific site) will be served from the database, not from the file system.

SharePoint Development using C#

2009-01-10T08:32:00.000-08:00

Before you start developing you need a reference to "using Microsoft.SharePoint;" namespace.

Working with a list

Short description of some classes:

Site Organization Classes
SPContext -
SPWebCollection -
SPListCollection -
SPWeb - represents site;
SPSite - represents site collection;
SPList -

List Classes
SPField -
SPView -
SPListItem -

Getting the Current Website
SPWeb web = SPContext.Current.Web;

Site Collection Navigation

SPSite siteCollection = SPContext.Current.Site;
SPWeb rootWeb = siteCollection.RootWeb;
TreeNode rootNode = new TreeNode(rootWeb.Title);
treeSiteCollection.Nodes.Add(rootNode);
addSubWebsToTree(rootWeb, rootNode);

Create a list
SPWeb web = SPContext.Current.Web;
web.AllowUnsafeUpdates = true;

SPList list;
try
{
list = web.Lists["Student Assignments"];
}

catch(Exception ex)
{
System.Guid listID
= web.Lists.Add("Student Assignments", "", SPListTemplateType.Tasks);
list = web.Lists[listID];
}

Creating a column in a list
SPFieldCollection fields = list.Fields;
SPField gradeField;
if (fields.ContainsField("Grade"))
{
gradeField = fields["Grade"];
}
else
{
fields.Add("Grade", SPFieldType.Number, false);
}

Adding Field to default view of the list
SPView defaultView = list.DefaultView;
if (!defaultView.ViewFields.Exists("Grade"))
{
defaultView.ViewFields.Add("Grade");
defaultView.Update();
}

Creating a new list item
SPListItemCollection items = list.Items;
SPListItem newItem = items.Add();
newItem["Title"] = "Homework 1";
newItem["DueDate"] = System.DateTime.Now;
newItem["Grade"] = 5; newItem.Update();

Single Sign On Administration

2009-01-04T07:39:00.000-08:00

Single Sign On –allow users to authenticate once into SharePoint and then access other applications such as Siebel or SAP using mapped credentials from encrypted credentials database. Administrators and developers use supporting application interfaces to manage single sign on credentials

Application Definition – metadata (username, passwords, group) about an application that that will be accessible through single sign on.

Solution Deployment

2009-01-03T17:50:00.000-08:00

Solution is a cab file with a manifest file that contains:

Feature definitions
Site Definitions
Resources –Assemblies (DLLs) that implement related functionality

Solution is very similar to a web part package in SharePoint 2003

The “Global” Template

2009-01-03T17:00:00.000-08:00

SharePoint provisions “Global” template before any other template

The template includes:

– Base type list schema definitions
•Generic List
•Document Library
•Discussion Forum
•Issues List
•Survey List

- Gallery Lists
•Master Page Gallery
•Web Part Gallery – only at the root site
•List Template Gallery – only at the root site
•Site Template Gallery – only at the root site
•User Information List – only at the root site

- Features
•Content Types
•Site Columns (Fields)
•Mobile Redirect

Site Definitions in 2007: Folder Structure

2009-01-03T16:45:00.000-08:00

Program files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\

•GLOBAL – contains “Global Template” site definition

•SiteTemplates
- STS
- default.aspx
- XML
- onet.xml – references features
- does not contain base types
- does not contain list templates
- MPS

•FEATURES – contains all SharePoint and custom features
- CustomList
- Navigation
- DocumentLibrary – document library feature
- ListTemplates
- DocLib.xml
- DocLib
- Schema.xml – DOES NOT CONTAIN
- Upload.aspx
- No allitems.aspx or editform.aspx

3 configuration changes needed to enable anonymous access for a public-facing MOSS site

2008-12-11T12:24:00.000-08:00

1. IIS - Grant Read rights to the Internet Guest Account (that is used in inetmgr anonymous access settings) for the site’s physical folder under inetpub

2. Central Admin – Navigate to Application Management -> Authentication Providers. Edit the “Default” zone and select “Enable Anonymous Access”

3. Site Collection – Navigate to Site Actions -> Site Settings -> Advanced Permissions. Navigate to Settings -> Anonymous Access. Select “Entire Web site”.

How to create a new scope in SharePoint?

2008-11-27T12:30:00.000-08:00

In order to create and activate new scope, you have to do next steps:

First step:

You have to create "Metadata property mappings"

Go to SSP, Click on the "Search Settings";

Click "Metadata property mappings";

Click "New Managed Property";

Give "Property Name", type;

Also in our example you need to "Add Mapping"

Click "Add Mapping", Choose category "People" and select a crawled property "People:FirstName(Text)";

And Check "Allow this property to be used in scopes"

Second Step:

Next Go to SSP, Click on the "Search Settings"

Go to the Scopes area and Click "View scopes"

Click "New Scope"

Specified "Title" and click "OK"

Then Click on the Scope that you just created and choose "Edit Properties"

Now you need to specify "Rule". Click "Empty - Add rules"

In our example we using "Property Query"

Now you have to update, Click "Start Update Now"

Choose from "Property Query" area Managed Property that you created in First Step = FirstName (For Example: Eugene)

Third Step:

Go to you site collections:

Click SiteActions -> Site Settings -> Modify All Site Settings

Then Click "Search Scopes" in Site Collection Administration area.

Click "Search Dropdown" and check your scope.

Click OK

and in order to see changes in dropdown list you need to do iisreset.

Ctrl+R and type iisreset

Done

Search Architecture Terminology

2008-11-27T10:28:00.000-08:00

Index Engine - processes the chunks of text and properties filtered from content sources, storing them in the content index and property store.

Query Engine - executes keyword and SQL syntax queries against the content index and search configuration data.

Content Index - stores information about words and their location in a content item.

Property Store - stores a table of properties and associated values.

Search Configuration Database - stores information used by the Search service, including crawl configuration, property schema, scopes, and so on.

Wordbreakers - used by the query and index engines to break compound words and phrases into individual words or tokens.

Sharepoint - SQL Server

2008-11-22T07:13:00.000-08:00

SQL Server provides unified storage by storing all user and config data with exception of search indices and site definitions (XML files)

Configuration Database – info about web farm configuration
Content Database (Site) –sites, lists, list items, and documents
Profile Database – user profiles and audience targeting
Services database – search configuration info
Single Sign On (SSO) – credentials to access other line of business apps

Some tables from one application in your database:

dbo.Sites - Stored Site Collection

dbo.Webs - Stored Each Individual Site in the Site Collection

dbo.Lists - All the lists within all sites collection

dbo.AllUserData - Stored list's items

dbo.AllDocs - Stored documents and information about

Sharepoint Server Glossary

2008-11-22T06:29:00.000-08:00

1. Application page is an a template page from _layouts virtual directory with following characteristics:

it is available within every site
only one copy of this page on the server
It is not accessible through Designer when editing a site
It is accessible through IIS

2. Safe page is a template page that comes from site definitions (For example: default.aspx in “Team Site” template).

it exists only on sites where it’s been specified by a template or created by a user
many copies can exist on the server
It is accessible through Designer when editing a site
It is not accessible through IIS

SharePoint Web Application is an IIS website that has a SharePoint Web Application Service running

Basic Web Application – such as default web site or external site (extranet.company.com), stores site collections where end-users and site administrators work

Central Administration – used by system administrators to manage the server farm

Shared Services – manages features that are common to all web applications such as search, user profiles, business data catalog

Personal Sites – contains personal user site collection (one per user)

Sharepoint Designer - Contributor Settings

2008-11-19T16:39:00.001-08:00

Let’s take a look at the next scenario. You need to create new group for users which will have the full control in the browser. But will limited for using specific folders, creating files with specific extensions etc. in SharePoint Designer.

In this case we need to use Contributor Settings (Contributor Mode)

First Step.

Create New Permissions Level (Site Settings > Permissions > Permission Levels)

Click "Add a Permission Level"

Second Step.

Create Group using Permission Level that you created in previous step (Site Settings > Permissions)

Click "New Group"

Third Step.

Open SharePoint Designer.

Go to "Site" menu > "Contributor Settings"

Setup "Site Manager" as default and delete others Groups.

Then Click "Add" new group

Give the name and choose site permissions level that you created in the first step. After that switching menu on the right chooses the settings that you need.

Click Ok

How to Back Up and Restore IIS

2008-11-17T08:54:00.000-08:00

Back Up the IIS Configuration

To back up your IIS configuration, follow these steps:

In the IIS snap-in on the local computer, click the Computer icon under Internet Information Services.
Click Action and select Backup/Restore Configuration.
Click Create backup, choose a name for your backup file, and then click OK. NOTE: The default location of the backup is the %SystemRoot%\system32\inetsrv\MetaBack folder. If you want to save your backup file to another location, you can copy the file from this default location to another location. Keep a copy in the default location to allow for an easy restoration.
Click Close. NOTE: This backup method provides a way to restore only your IIS settings, not your content files. This backup method does not work if you reinstall your operating system. Backup files cannot be used to restore an IIS configuration on other computers that are running Windows 2000.

Restoring the IIS Configuration Without an IIS Reinstallation

To restore your IIS configuration if you have not removed and reinstalled IIS, follow these steps:

In the IIS snap-in on the local computer, click the Computer icon under Internet Information Services.
Click Action and select Backup/Restore Configuration.
In the Configuration Backup Name dialog box, select a backup file and click Restore. When you are asked if you want to restore your configuration settings, click Yes.

Restoring the IIS Configuration After an IIS Reinstallation

To restore your IIS configuration after you have removed and reinstalled IIS, follow these steps:

In the IIS snap-in on the local computer, click the Computer icon under Internet Information Services.
Click Action and select Backup/Restore Configuration.
In the Configuration Backup Name dialog box, select the backup file that you created and click Restore. Although an error message states that the restoration has failed, a portion of your backed-up configuration is restored.
At a command prompt, type the following: cscript.exe X:\InetPub\AdminScripts\Adsutil.vbs enum w3svcwhere X is the letter of the drive on which IIS is installed. From the listed settings, locate the WamUserName and the associated WAMUserPass value.NOTE: To use the Adsutil.vbs utility, you must have Windows Script Host installed.
Click Start, point to Settings, click Control Panel, double-click Administrative Tools, and then double-click Computer Management. Click Local User Managers and click Users.
Double-click the IWAM_computername user account. Type the WAMUserPass value that you retrieved from the previous step and click OK.
In the Configuration Backup Name dialog box, select the backup file that you created and click Restore. This fully restores your configuration.NOTE: If you change the identity of your out-of-process applications, those applications revert back to the previous IWAM user name.

Mostly used short cuts and file locations working with Sharepoint

2008-11-14T07:55:00.000-08:00

Run commands

mstsc - Remote Desctop Connection
inetmgr - IIS Manager (Internet Information Services Manager);
run - windows key + R
cmd - command prompt
iisreset - Reseting Internet Information Services

Host File - C:\WINDOWS\system32\drivers\etc
GAC (Global Assembly Cache) - C:\Windows\assembly

Applications Locations (by Default) - C:\Inetpub\wwwroot\wss\VirtualDirectories

Copy dll files from the GAC - Open Run Window, and type C:\Windows\assembly\gac\

How to get PublicKeyToken? right-click on the assembly name and open the properties dialog box to view the assembly name and public key.

Direct links to some of pages in sharepoint site

Web Part Gallery Page
http://yourserver/sitecol/_catalogs/wp/Forms/AllItems.aspx

Visual Studio 2005 (useful short cuts)
Code Reformating - Select the code, and click Ctrl+K & Ctrl+F;

How to Deploy Web Parts?

2008-11-14T05:58:00.000-08:00

Deployment for Development Purposes*

manually copy the web part’s signed assembly (.dll) to the
Global Assembly Cache (GAC);
manually add the corresponding element to
SharePoint’s Web.config file;
use a site collection’s web-part gallery pages to add the
web part.

Moving to Production (You need to create a solution package to deploy it to your SharePoint farm). For creating solution, we have to use Microsoft add-in called Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions, Version 1.1. Click Here to Download it.

*The preferred method for deploying a web part for an entire SharePoint web application or web farm is through a SharePoint solution.

Adventure Works SQL Server 2005 SP2a sample databases

2008-11-12T16:14:00.000-08:00

Here you can find all sample databases:

Visit the SQL Server Samples and Community Projects page on CodePlex at:

http://codeplex.com/SqlServerSamples

For those people who looking something specific as follow the same link above, you can see the original names of databases below. And also you can see step by step manual how to install and attach database to your SQL server.

AdventureWorks - AdventureWorksDB.msi

AdventureWorksDW - AdventureWorksBI.msi

Northwind and pubs Sample Databases for SQL Server 2000 Download

(by default after installation completed you can find northwind database, under this location

C:\SQL Server 2000 Sample Databases\. For installation in more detail click here)

First Step. Download the file you need. Install (by default it will install it C:\Program Files\Microsoft SQL server\MSSQL.1\MSSQL\Data\nameofdatabase.mdf)

Next Step. Open SQL server, right click on Databases (on your left). Select Attach then press add button. Select database that you need and press OK.

Feature '75a0fea7-cd50-401e-af0e-782f3662a299' is not installed in this farm, and can not be added to this scope.

2008-11-11T19:05:00.000-08:00

When I was trying to create Top-Level site using "Help Desk" template I got next error "Feature '75a0fea7-cd50-401e-af0e-782f3662a299' is not installed in this farm, and can not be added to this scope"

One of the ways to resolve this issue to install Windows SharePoint Services 3.0 Application Template: Application Template Core.

Install:

stsadm -o addsolution -filename path\mySolution.wsp

stsadm -o execadmsvcjobs

stsadm -o deploysolution -name mySolution.wsp -immediate -allowGacDeployment -force

Uninstall:

stsadm -o retractsolution -name mySolution.wsp -immediate

stsadm -o execadmsvcjobs

stsadm -o deletesolution -name mySolution.wsp -override

stsadm -o execadmsvcjobs

Web Template IDs in Sharepoint

2008-11-11T10:59:00.000-08:00

STS#0 Team site
STS#1 Blank site
STS#2 Document workspace
MPS#0 Basic meeting workspace
MPS#1 Blank meeting workspace
MPS#2 Decision meeting workspace
MPS#3 Social meeting workspace
MPS#4 Multipage meeting workspace
WIKI#0 Wiki
BLOG#0 Blog

BDR#0 Document center—A central document management location for an enterprise
OFFILE#0 Records center—A central location in which records
OFFILE#1 managers can define routes for incoming files
CMSPUBLISHING#0 Publishing site
BLANKINTERNET#0 Publishing site—A site for publishing web pages on a schedule with workflow features enabled
BLANKINTERNET#1 Press releases site
BLANKINTERNET#2 Publishing site with workflow—A publishing site for web pages using approval workflows
SPSNHOME#0 A site for publishing news and articles
SPSREPORTCENTER#0 Report center—A site for creating, managing, and delivering web pages, dashboards, and Key Performance Indicators (KPIs)
SPSPORTAL#0 A starter hierarchy for an intranet divisional portal
PROFILES#0 A profile site that includes page layouts with zones
BLANKINTERNETCONTAINER#0 Publishing portal—a site collection preconfigured for revision-controlled, secure content creation and publication

How to see the actual error in SharePoint

2008-11-10T13:28:00.000-08:00

In order to see the actual error you need to make a few modifications of web.config file. Take the web.config file from application\site that gives the error.

Open in Notepad:
First, change customErrors mode in "Off"

Second, change CallStack="true"

Refresh the page with error

FatalError: Could not find Feature S2SiteAdmin.

2008-11-10T11:56:00.000-08:00

I was importing one of my site and I got the next message:

Problem:

Progress: Initializing Import.

FatalError: Could not find Feature S2SiteAdmin.

Solution:

You need to install "Infrastructure Update for Microsoft Office Servers (KB951297)"

Brief Description

The Infrastructure Update for Microsoft Office Servers (KB951297) includes the latest performance updates and fixes for the Microsoft Office Servers.

Download

How to create host name top level site with stsadm

2008-11-10T06:49:00.000-08:00

For example, if you have a Web application named http://sharepoint.com and you want to add a host-named site collection with the URL http://about.sharepoint.com, use the following command:

stsadm.exe -o createsite -url http://about.sharepoint.com -ownerlogin domain\siteowner -owneremail siteowner@sharepoint.com -hhurl http://sharepoint.com

Renaming Site
stsadm -o renamesite -oldUrl http://www.name.com -newUrl http://www.newname.com

How to install and unistall WSP solution template using stsadm

2008-11-09T07:42:00.002-08:00

Install:

stsadm -o addsolution -filename path\mySolution.wsp

stsadm -o execadmsvcjobs

stsadm -o deploysolution -name mySolution.wsp -immediate -allowGacDeployment -force

Uninstall:

stsadm -o retractsolution -name mySolution.wsp -immediate

stsadm -o execadmsvcjobs

stsadm -o deletesolution -name mySolution.wsp -override

stsadm -o execadmsvcjobs

Key classes in the SharePoint object model

2008-11-09T07:42:00.001-08:00

Document Libraries (Microsoft.Sharepoint)

SPDocumentLibrary

SPPictureLibrary

Features (Microsoft.Sharepoint)

SPFeatureDefinition

SPElementDefinition

SPFeatureProperty

SPFeatureScope

SPFeature

Sites (Microsoft.SharePoint)

SPSite

SPSiteCollection

SPSiteAdministration

SPWeb

Business Data Catalog (Microsoft.Office.Server.ApplicationRegistry.Administration)

EntityCollection

ApplicationRegistry

Meetings (Microsoft.SharePoint.Meetings)

SPMeeting

MtgUtility

Solutions (Microsoft.SharePoint.Administration)

SPSolution

SPFeatureReceiver

SPSolutionCollection

Lists (Microsoft.SharePoint)

SPList

SPListItem

SPListItemCollection

User Profiles (Microsoft.Office.Server.UserProfiles)

UserProfile

UserProfileManager