You need to be a site collection administrator to set this property.

Issue Description

Recently I was trying to add a site collection administrator to a site and I got the belowmessage

You need to be a site collection administrator to set this property.   at Microsoft.SharePoint.ApplicationPages.ManageSiteAdminPage.BtnSubmit_Click(Object sender, EventArgs e)

   at System.Web.UI.WebControls.Button.OnClick(EventArgs e)

   at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)

   at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)

   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

I was already the site collection administrator to the site and it did not make any sense.

Fix

On further trouble shooting, I found the solution for this.Browse to Central Administration - > Site Collection Quotas and Locks.

The options available here are:

       Not locked

Adding content prevented

Read-only (blocks additions, updates, and deletions)

No access

This site collection was in Read-only status. Unlock it (Change the status to  "Not Locked")

How to change the URL for SharePoint Central Administration site

If you extend the Central Administration web application (using GUI or psconfig command) to run on multiple servers, and when you click on SharePoint Central Administration icon you're still redirected to the first SharePoint server where Central Administration is hosted.

The URL has to be changed via registry on all SharePoint servers to fix this.

To change the URL for SharePoint Central Administration URL:

1) Open Registry editor

2) Backup the registry before making changes

3) Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS and change the value of CentralAdministrationURL to the new URL

Setsitelock: Stsadm operation

Sets a value that specifies whether the site collection is locked and unavailable for read or write access. This operation should be used in conjunction with the Getsitelock operation. For more information, see the Examples section.

Syntax

stsadm -o setsitelock

   -url <URL name>

   -lock {none | noadditions | readonly | noaccess}

None: Sets the site collection to unlock.

Noadditions: Permits changes that reduce the size of the data.

For example, if you had an announcement list item whose body consisted of 50 characters, you could successfully edit the list item so that the body was reduced to 25 characters. However, if you tried to edit the list item so that they body was increased to 100 characters, that would be blocked.

Readonly: Sets the site collection to read-only.

Noaccess: Sets the site collection unavailable to all users.

Examples

To determine the lock status of the site, you can use the following getsitelock syntax:

stsadm -o getsitelock -url http://server_name

Once the lock status of the site collection is determined, you can use the noaccess parameter of the setsitelock operation to lock out all users to the site:

stsadm -o setsitelock -url http://server_name -lock noaccess

Reference

SharePoint Recycle Bin � First Stage and Second Stage

SharePoint Recycle Bin stores and keeps a track of the items deleted from the site. When an item is deleted in SharePoint, it is not completely deleted, it is actually stored in a Recycle Bin . The main idea of a Recycle Bin is to restore contents that are accidentally deleted or retrieve data that should not have been deleted. There are 2 stages to the Recycle Bin.

First Stage Recycle Bin

Whenever an item is deleted from the site it goes to the Recycle Bin (users� Recycle Bin) of the site and stays there till it is restored or it expires. By default the items are stored in the Recycle bin for 30 days. This setting is configured at the web application level from Central Administration. You can access a site's Recycle Bin by clicking on the Recycle Bin link on the left navigation (Quick Launch).

Normal user's Recycle Bin URL - /_layouts/recyclebin.aspx

If an item is deleted from the User�s Recycle Bin (First Stage Recycle Bin), it goes to the Site Collection Recycle Bin (Second Stage Recycle Bin).

Second Stage Recycle Bin

When an item is deleted from a site's Recycle Bin it goes to Site Collection Recycle Bin and stays there till it is restored or it expires. By default the items are stored in the Recycle bin for 30 days. If the item is deleted from here, it is deleted forever. To access the Site Collection Recycle Bin, browse to Site Settings -> Site Collection Administration -> Recycle Bin.

This Recycle Bin has two views: End User Recycle Bin Items view displays all the contents of all the recycle bins of all the sites under that particular site collection whereas Deleted From End User Recycle Bin view displays all the items which have been deleted from the sites recycle bins

Site Collection's Recycle Bin has two views :

End user Recycle Bin items URL - /_layouts/AdminRecycleBin.aspx

Deleted from end user Recycle Bin URL - /_layouts/AdminRecycleBin.aspx?View=2

Note:

- If an end user deletes and item, it will go to his Recycle Bin. Other users will not be able to see another users� recycle bin.

- When you disable the Recycle Bin feature, all the items existing in it will be removed permanently.

How to Deactivate a SharePoint feature using PowerShell or STSADM

To Disable a SharePoint Feature, you must first determine the scope of the feature. If the scope is Web-based or is a site collection scope, the URL parameter is required. However, if the scope is farm-based, the URL parameter is not required.

Syntax - PowerShell

Disable-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Url <String>] [-WhatIf [<SwitchParameter>]]

This example disables the "MyCustom" Web site scoped feature at http://somesite.

Disable-SPFeature -identity "MyCustom" -URL http://somesite

This example disables all features in the subsite at http://somesite/myweb.

$w = Get-SPWeb http://somesite/myweb | ForEach{ $_.URL }

Get-SPFeature -Web $w |%{ Disable-SPFeature -Identity $_ -URL $w}

Syntax - STSADM

stsadm -o deactivatefeature

   -filename

   -name <feature folder>

   -id <feature ID>

   [-url] <URL name>

   [-force]

Parameter	Value	Description
filename	A valid file path, such as "MyFeature\Feature.xml"	Path to feature must be a relative path to the 14\Template\Features directory. Can be any standard character that the Windows system supports for a file name.
name	Name of the feature directory, such as �MyFeature�	Name of the feature folder located in the 14\Template\Features directory
id	A valid GUID, e.g.  �11d186e-7306-4902-a825-0eb7609e9280�	GUID that identifies the feature to activate
url	A valid URL, such as http://server_name	URL of the Web application, site collection, or Web site to which the feature is being activated

How to Activate a SharePoint feature using PowerShell or STSADM

To Enable a SharePoint Feature, you must first determine the scope of the feature. If the scope is Web-based or is a site collection scope, the URL parameter is required. However, if the scope is farm-based, the URL parameter is not required.

Syntax - PowerShell

Enable-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-CompatibilityLevel <Int32>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-PassThru <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

This example enables the "MyCustom" site scoped SharePoint Feature at http://somesite.

Enable-SPFeature -identity "MyCustom" -URL http:// sitename

This example enables all SharePoint Features in the subsite at http://somesite/myweb.

$w = Get-SPWeb http://somesite/myweb | ForEach{ $_.URL }

Get-SPFeature -Web $w |%{ Enable-SPFeature -Identity $_ -URL $w}

Syntax - STSADM

stsadm -o activatefeature

   {-filename <relative path to Feature.xml> | -name <feature folder> | -id <feature ID>}

   [-url] <URL name>

   [-force]

Parameter	Value	Description
filename	A valid file path, such as "MyFeature\Feature.xml"	Path to feature must be a relative path to the 14\Template\Features directory. Can be any standard character that the Windows system supports for a file name.
name	Name of the feature directory, such as �MyFeature�	Name of the feature folder located in the 14\Template\Features directory
id	A valid GUID, e.g.  �11d186e-7306-4902-a825-0eb7609e9280�	GUID that identifies the feature to activate
url	A valid URL, such as http://server_name	URL of the Web application, site collection, or Web site to which the feature is being activated

Note : If you try to use the Url parameter on a farm-scoped feature, you receive the following error message:

The feature �<feature name>� applies to the entire farm; the Url parameter cannot be used with farm-scoped features.

SharePoint Group - Site Owner (Full Control)

When a SharePoint site is created, by default 3 SharePoint groups are created

Site Owners - Full control

Site Members - Contribute

Site Visitors - Read

Below are the permissions you get when you are a Site Owner (Full Control)

List Permissions

Manage Lists - Create and delete lists, add or remove columns in a list, and add or remove public views of a list.

Override Check Out - Discard or check in a document which is checked out to another user.

Add Items - Add items to lists and add documents to document libraries.

Edit Items - Edit items in lists, edit documents in document libraries, and customize Web Part Pages in document libraries.

Delete Items - Delete items from a list and documents from a document library.

View Items - View items in lists and documents in document libraries.

Approve Items - Approve a minor version of a list item or document.

Open Items - View the source of documents with server-side file handlers.

View Versions - View past versions of a list item or document.

Delete Versions - Delete past versions of a list item or document.

Create Alerts - Create alerts.

View Application Pages - View forms, views, and application pages. Enumerate lists.

Site Permissions

Manage Permissions - Create and change permission levels on the Web site and assign permissions to users and groups.

View Web Analytics Data - View reports on Web site usage.

Create Subsites - Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.

Manage Web Site - Grants the ability to perform all administration tasks for the Web site as well as manage content.

Add and Customize Pages - Add, change, or delete HTML pages or Web Part Pages, and edit the Web site using a Microsoft SharePoint Foundation-compatible editor.

Apply Themes and Borders - Apply a theme or borders to the entire Web site.

Apply Style Sheets - Apply a style sheet (.CSS file) to the Web site.

Create Groups - Create a group of users that can be used anywhere within the site collection.

Browse Directories - Enumerate files and folders in a Web site using SharePoint Designer and Web DAV interfaces.

View Pages - View pages in a Web site.

Enumerate Permissions - Enumerate permissions on the Web site, list, folder, document, or list item.

Browse User Information - View information about users of the Web site.

Manage Alerts - Manage alerts for all users of the Web site.

Use Remote Interfaces - Use SOAP, Web DAV, the Client Object Model or SharePoint Designer interfaces to access the Web site.

Use Client Integration Features - Use features which launch client applications. Without this permission, users will have to work on documents locally and upload their changes.

Open - Allows users to open a Web site, list, or folder in order to access items inside that container.

Edit Personal User Information - Allows a user to change his or her own user information, such as adding a picture.

Personal Permissions

Manage Personal Views - Create, change, and delete personal views of lists.

Add/Remove Personal Web Parts - Add or remove personal Web Parts on a Web Part Page.

Update Personal Web Parts - Update Web Parts to display personalized information.

SharePoint Group - Site Member (Contribute)

When a SharePoint site is created, by default 3 SharePoint groups are created

Site Owners - Full control

Site Members - Contribute

Site Visitors - Read

Below are the permissions you get when you are a Site Member (Contribute)

List Permissions

Add Items - Add items to lists and add documents to document libraries.

Edit Items - Edit items in lists, edit documents in document libraries, and customize Web Part Pages in document libraries.

Delete Items - Delete items from a list and documents from a document library.

View Items - View items in lists and documents in document libraries.

Open Items - View the source of documents with server-side file handlers.

View Versions - View past versions of a list item or document.

Delete Versions - Delete past versions of a list item or document.

Create Alerts - Create alerts.

View Application Pages - View forms, views, and application pages. Enumerate lists.

Site Permissions

Browse Directories - Enumerate files and folders in a Web site using SharePoint Designer and Web DAV interfaces.

View Pages - View pages in a Web site.

Browse User Information - View information about users of the Web site.

Use Remote Interfaces - Use SOAP, Web DAV, the Client Object Model or SharePoint Designer interfaces to access the Web site.

Use Client Integration Features - Use features which launch client applications. Without this permission, users will have to work on documents locally and upload their changes.

Open - Allows users to open a Web site, list, or folder in order to access items inside that container.

Edit Personal User Information - Allows a user to change his or her own user information, such as adding a picture.

Personal Permissions

Manage Personal Views - Create, change, and delete personal views of lists.

Add/Remove Personal Web Parts - Add or remove personal Web Parts on a Web Part Page.

Update Personal Web Parts - Update Web Parts to display personalized information.

SharePoint Group - Site Visitor (Read)

When a SharePoint site is created, by default 3 SharePoint groups are created

Site Owners - Full control

Site Members - Contribute

Site Visitors - Read

Below are the permissions you get when you are a Site Visitor (Read)

List Permissions

View Items - View items in lists and documents in document libraries.

Open Items - View the source of documents with server-side file handlers.

View Versions - View past versions of a list item or document.

Create Alerts - Create alerts.

View Application Pages - View forms, views, and application pages. Enumerate lists.

Site Permissions

View Pages - View pages in a Web site.

Browse User Information - View information about users of the Web site.

Use Remote Interfaces - Use SOAP, Web DAV, the Client Object Model or SharePoint Designer interfaces to access the Web site.

Use Client Integration Features - Use features which launch client applications. Without this permission, users will have to work on documents locally and upload their changes.

Open - Allows users to open a Web site, list, or folder in order to access items inside that container. 

Downloading/Extracting WSP (Solution) from SharePoint

Background

Last week I was working on a SharePoint project where I had to get all the wsp�s deployed in the farm and I was not able to find few .wsp files anywhere in the Central Administration server. In the Central Administration Solution Properties screen, there is an option to Retract the solution but no option to Download the solution

Solution

I am not sure if there is a way to do this using stsadm. But definitely we can do this using SharePoint PowerShell.To run this command, you need to be a member of the Farm Administrators group and have permission to the configuration database

$farm = Get-SPFarm

$file = $farm.Solutions.Item("deployedsolutionname.wsp").SolutionFile

$file.SaveAs("c:\temp\deployedsolutionname.wsp")

Hiding Title Column in a SharePoint list

1. Navigate to the SharePoint list page that contains the Title data you want to hide.

2. Go to the Settings menu at the top of the page and select List Settings.

3. Click on the link labeled Advanced Settings.

4. Select the Yes radio button next to Allow the Management of Content Types. Then click OK.

5. Click on Item from the Content Types section of the page.

6. Click on the item labeled Title.

7. Scroll down to the Column Settings section and choose the Hidden radio button.

8. Click OK to save the settings.

Retrieving the COM class factory for component with CLSID {BDEADEE2-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 800703fa.

Issue Description

I was getting the above error while browsing to Central Administration

Server Error in �/� Application.

Retrieving the COM class factory for component with CLSID (BDEADEE2- C265- .11 DO- SCED- OOAOC9OAB5OFJ failed due to the following error: 800703 fa.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where �t originated in the code.

Exception Details: System.Runtime.lnteropservices.COMException: Retrieving the COM class factory for component wh CLSID (ODEADEE2-C265-1 I DO-BCED-OOAOC9OAOSOF)failed due to the following error: 800703fa.

Source Error:

An unhandled exception was generated during the execution of the current web request. Inforniation regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[COMException (0x800703fa): Retrieving the C0M class factory for component with CLSID {BDEADEE2-C265-llDO-BCED-OOAOC9OABSOF} failed due to the following error: 800703f a.]

Microsoft.SharePoint.Library.SPRequest. .ctorO tiO4

Microsoft.SharePoint.SPGlobal.CreatesPRequestAndSetldentity(Boolean bNotGlobalAdminCode, String strUrl , Sedean bNotAddToContext, Byte[] UserToken, String userName, Soolean blgnoreTokenTimeout, Soolean bAsAnonyntus) �238

Microsoft.SharePoint.SPWeb.InitializeSPRequest() .455

Microsoft. SharePoi nt. SPWeb. EnsureSPRequestQ �75

Microsoft. SharePoi nt. SPWeb. get_Request() �74

Microsoft.SharePoint.WebControls.SPControl .SPwebEnsureSPControl(HttpContext context) +613

Microsoft.Sharepoint.WebControls.SPControl .c5etContextweb(HttpContext context) .41

Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostResolveRequestCacheHandler(Object osender, EventArgs ea) �595

System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) �171

Version Informdtion: Microsoft NET Framework Version:2.O.50727.4234; ASP.NET Yersion:2.U.5U727.4223

Resolution

Perform an IISRESET on all the web servers in the farm.

Error 0x800700DF: The file size exceeds the limit allowed and cannot be saved.

Problem Description

I was trying to copy items from SharePoint Windows explorer view to my local drive and I got this error message. All files were pretty big. (More than 50 MB).

Copy Folder

An unexpected error is keeping you from copying the folder. If you continue to receive this error, you can use the error code to search for help with this problem.

Error 0x800700DF: The file size exceeds the limit allowed and cannot be saved.

<file name>

Try again Cancel

Cause

You receive a folder copy error message when you try to download a file that is larger than 50000000 bytes from a Web folder. I was using Windows 7 Operating System

Resolution

Follow this KB article and run the Fix IT by downloading and running the executable.

P.S.: When you run the Fix it wizard, you need to enter a FileSizeLimitInBytes (I changed it to 500MB by adding an additional zero) value that is larger than the size of the file that you want to download.