Failure Cause: The database schema version is less than the minimum backwards compatibility schema version that is supported for this component. To resolve this problem upgrade this database.

If you get this error, go to PowerShell Command, and type the following:

(get-spserver $env:computername).NeedsUpgrade

then, if it false, run the following from VSS Administrative command prompt:

PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

SharePoint 2010 website requires you to log in - error

add <computer name\server>\users Read & Execute, List Folder Contents and Read permissions.

Enable Document Sets for a site collection

Enable Document Sets for a site collection

If the Document Sets feature has not been activated for your site collection, you will need to activate it before you can create or configure new Document Set content types. You must be a Site Collection Administrator to activate the Document Sets feature.

1. Go to the top-level site in the site collection for which you want to enable Document Sets.
2. On the Site Actions menu, click Site Settings.
3. Under Site Collection Administration, click Site collection features.
4. Find Document Sets in the list, and then click Activate.

Turn on support for multiple content types in a list or library

Turn on multiple content types in a list

1. Open the list or calendar for which you want to enable multiple content types.
2. On the ribbon, under List Tools, click the List tab.
3. In the Settings group, click List settings.
4. In the General Settings section, select Advanced Settings.
5. In the Content Types section, click Yes under Allow management of content types?
6. Change any other settings that you want, and then click OK.

This website has been configured to disallow editing with SharePoint Designer 2010

For site collection administrators on the web application

This disables SharePoint Designer for site collection administrators and as a result, all users, of the web application and its site collections.

1. Log on to Central Administration.
   Note For more information on accessing Central Administration, see Central Administration Help.
2. In the left navigation, click General Application Settings.
3. On the General Application Settings page, click Configure SharePoint Designer settings.
4. To change the web application where you want to apply your settings, click the currently selected application and choose Change Web Application. Then on the Select Web Application screen, click the application you want to use.
5. On the SharePoint Designer Settings page, uncheck the box Enable SharePoint Designer.
6. Click OK.

To configure browser-enabled user form templates by using Windows PowerShell

To configure browser-enabled user form templates by using Windows PowerShell

1.     Verify that you meet the following minimum requirements: See Add-SPShellAdmin.

2.     On the Start menu, click All Programs.

3.     Click Microsoft SharePoint 2010 Products.

4.     Click SharePoint 2010 Management Shell.

5.     At the Windows PowerShell command prompt, type the following command:

Set-SPInfoPathFormsService -AllowUserFormBrowserEnabling <BrowserEnablingSetting> -AllowUserFormBrowserRendering <BrowserRenderingSetting>

more details @ 

Creating Trusted Login Providers (SAML Sign-in) for SharePoint 2010

The following links explain how to create a custom security token service (STS) and then set up a trust relationship between a SharePoint 2010 farm and the custom STS.






http://blogs.msdn.com/b/kaevans/archive/2010/07/09/creating-a-custom-login-page-for-sharepoint-2010.aspx
http://blogs.msdn.com/b/kaevans/archive/2010/07/09/sql-server-provider-for-claims-based-authentication-in-sharepoint-2010.aspx
http://www.devx.com/enterprise/Article/35068



http://msdn.microsoft.com/en-us/library/gg615945(v=office.14).aspx
http://blogs.msdn.com/b/kaevans/archive/2010/07/09/creating-a-custom-login-page-for-sharepoint-2010.aspx
http://msdn.microsoft.com/en-us/library/ff955607.aspx
http://blogs.southworks.net/aortega/2010/08/13/sharepoint-2010-and-adfs-sign-in-as-a-different-user/

Creating a Custom Login Page for SharePoint 2010/Manage external sharing for your SharePoint online environment

http://msdn.microsoft.com/en-us/library/gg317440(v=office.14).aspx

http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/manage-external-sharing-for-your-sharepoint-online-environment-HA102849864.aspx

http://blogs.msdn.com/b/kaevans/archive/2010/07/09/creating-a-custom-login-page-for-sharepoint-
2010.aspx

SharePoint Online for enterprise

SharePoint Online for small business

ON by default, can be turned off SharePoint Online Administer “allows” for whole company. Individual site owners choose to activate the “external user invitation” feature for their group’s use. Site owner invites via any email using Site Actionsà Share Site. Invitee accepts invitation with a LiveID-based user name and password (@live.com, @hotmail.com, @msn.com and all regional derivatives). Collaboration ensues. Undo step 1 or 2 at any time.

OFF by default, can be turned on Site owner invites via any email using Site Actionsà Share Site. Invitee accepts invitation with a LiveID-based user name and password. (@live.com, @hotmail.com, @msn.com and all regional derivatives). Collaboration ensues. Deactivate the “external user invitation” feature at any time.

http://community.office365.com/en-us/blogs/office_365_technical_blog/archive/2011/12/08/did-you-know-you-can-share-sharepoint-online-s-external-sharing-capabilities.aspx

HTTP 403 Forbidden Error After Installing .NET Framework 3.5 SP1 on Windows Server 2003 SP2 running MOSS 2007

Solution:
http://sharepointsircar.blogspot.com/2009/02/http-403-forbidden-error-after.html

SharePoint 2010 and LiveLink Integration - Information

SharePoint Foundation 2010 supports authentication methods that were included in previous versions and also introduces token-based authentication that is based on Security Assertion Markup Language (SAML) as an option. The following table lists the supported authentication methods.

Application that support Windows integrated authentication (NTLM or Kerberos, as described in http://spnego.sourceforge.net/

For more, please review http://msdn.microsoft.com/en-us/magazine/ff872350.aspx andhttp://www.codeproject.com/Articles/106439/Single-Sign-On-SSO-for-cross-domain-ASP-NET-applic

SharePoint and LiveLink Integration: Part 1How to use WCF Livelink web services to create a quasi single sign on or login with cookie equivalent of lapiUnderstanding WS-Federation

SharePoint 2010 : Context Menu Duplicating Menu Items:

I haven’t find any solutions other than the steps below, which can fix the issues that related to context menu duplicating items:

1.       Locate the folder in the production server : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033.

2.       Locate the “core.js” and “core.debug.js” file and make a backup core.js and core.debug.js files [Important: Do not edit the existing core.js file].

3.       Edit the .js file and search the string for each menu item, if founds comment  the function (/*…*/).

4.       Reset IIS.

I have tested in my VMware and you can see the changes before and after, the “Alert Me” button is not showing up now:

And the result goes as below:

there is one drawback – the change made will affect all the web applications that we have on the server.  Also, it is in production server, so we be in very CAREFUL. 

SharePoint 2010 - Refresh the parent page using Server side API !

1.  Add the following code in elements.xml 

function openSitePropertyDialog(url) { 
       var dialogOptions = SP.UI.$create_DialogOptions(); 
       dialogOptions.width = 800; 
       dialogOptions.height = 400; 
       dialogOptions.dialogReturnValueCallback = Function.createDelegate(null, sitePropertiesDialogCallback); 
       commonModalDialogOpen( 
               url, 
               dialogOptions, 
               sitePropertiesDialogCallback, 
               null); 
   } 
   function sitePropertiesDialogCallback(dialogResult, returnValue) { 
       if (returnValue != null) { 
           var notificationId = SP.UI.Notify.addNotification(returnValue, false); 
       } 
       SP.UI.ModalDialog.RefreshPage(dialogResult); 
       //refreshUpdatePanelOnDialogCallback(dialogResult); 
   } 
   function refreshUpdatePanelOnDialogCallback(dialogResult) { 
       if (dialogResult == SP.UI.DialogResult.OK) { 
           __doPostBack(<%SPHttpUtility.AddQuote(SPHttpUtility.NoEncode(SitePropertiesUpdatePanel.ClientID),Response.Output);%>); 
       } 
   } 

2.  In code-behind do the following

if (!Page.IsValid) 
           { 
               return; 
           } 
 
           //Get propertyName and propertyValue to add 
           string propertyName = NameInputFormTextBox.Text.Trim(); 
           string propertyValue = ValueInputFormTextBox.Text.Trim(); 
 
 
           if (String.IsNullOrEmpty(propertyName)) 
           { 
               NameErrorLabel.Text = "Site property name cannot be empty."; 
               return; 
           } 
 
 
           try 
           { 
               if (Web.GetProperty(propertyName) != null) 
               { 
                   NameErrorLabel.Text = "Site property name already exists."; 
                   return; 
               } 
 
 
               Web.AddProperty(propertyName, propertyValue); 
               Web.Update(); 
           } 
           catch (Exception ex) 
           { 
               throw new SPException(ex.Message); 
           } 
 
 
           //Refresh the page when the dialog is closed by write JS directly to the 
           //http Response object that will close the dialog          
           if (SPContext.Current.IsPopUI) 
           { 
               Response.Clear(); 
               Response.Write(String.Format(@"<script language=""javascript"" type=""text/javascript""> 
 
               window.frameElement.commonModalDialogClose(1, ""{0}"");</script>", "Site property is successfully added.")); 
               Response.End(); 
           } 
           else 
           { 
               SPUtility.Redirect(strSource, SPRedirectFlags.UseSource, this.Context); 
           }           

Click here to download code from MSDN

SharePoint 2010 - Add Popup In SharePoint 2010

Create a new element and copy the following script into your element.xml file.

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<CustomAction ScriptSrc="~site/Scripts/main.js" Location="ScriptLink" Sequence="100">
</CustomAction>
<CustomAction
 Id="CreateDS"
 RegistrationType="ContentType"
 RegistrationId="0x0101"
 Location="EditControlBlock"
 Title="Create Data Set - Beta V 1.0"
 ImageUrl="/_layouts/images/FOLDER16.GIF"
 Sequence="0"
 Rights ="EditListItems">
<UrlAction Url="javascript:showDSWindow();
var statusId;
function notifyMe(msg)
{
var statusId = SP.UI.Status.addStatus(msg);         
visibleStatusIds.push(statusId); 
enableRemoveStatusButton(); 
RefreshCommandUI();
}
 
function RemoveStatus() {
SP.UI.Status.removeStatus(this.statusId);
}
function demoCallback(dialogResult, returnValue)
{    
 /*alert(returnValue);
 this.statusId = SP.UI.Status.addStatus('DataSet Created','New Data Set Created.',true);
 SP.UI.Status.setStatusPriColor(this.statusId, 'Green');
 setTimeout(RemoveStatus, 1000);*/
 SP.UI.ModalDialog.RefreshPage(SP.UI.DialogResult.OK);
}

function CreateDSWindow()
{
var ctx = SP.ClientContext.get_current();
var items = SP.ListOperation.Selection.getSelectedItems(ctx);
var myItems = '';
var k;
var enable = true;
if (items.length=='0'){alert('You must select at least one document to continue.');return;}
for (k in items)
{
myItems += '|' + items[k].id;
if (items[k].fsObjType != 0)
enable = false;
}
if (!enable) {alert(' The files will NOT be moved to new Document Set, unselect the DataSet/Folder ...');return;}
var options = {              
url: '{SiteUrl}/_layouts/CreateDocumentSet/ChooseDS.aspx?ListId={ListId}&amp;items=' + myItems + '&amp;source=' + SP.ListOperation.Selection.getSelectedList(),
tite: 'Move Documents - Stellar Demo V 1.0',
allowMaximize: false,
showClose: true,
width: 500,
height: 380,
dialogReturnValueCallback: demoCallback };
SP.UI.ModalDialog.showModalDialog(options);}

function showDSWindow()
{
CreateDSWindow();
}   
" />
</CustomAction>
</Elements>

2. Create an ASPX file called ChooseDS.aspx