Monthly Archives - May 2012

How to Create Custom Permission Levels in SharePoint 2010

In this article I am going to give you an overview of permission levels in SharePoint 2010, what are default permission levels, how to create custom permission level, how to create group in SharePoint , assign custom permission level to this group and add some users to group.
So let’s start :)
SharePoint Server 2010 provides many default permission levels, these permission levels are actually rights and capability which users and groups can perform.
Following table illustrates default permission levels in SharePoint Server 2010 and capability of each permission level.
Note: Some of permission levels are only available in publishing template.
Permission Level
Site Template
Description of Capabilities
Limited Access
Team or Publishing Template
Specific lists, document libraries, list items, folders, or documents may be viewed; but access to all elements of the site are not granted.
Read
Team or Publishing Template
Items can be viewed on the site pages.
Contribute
Team or Publishing Template
Users can add or change items on the site pages or in existing lists or document libraries.
Design
Team or Publishing Template
Page layout can be modified by members in the browser or from within SharePoint Designer 2010.
Full Control
Team or Publishing Template
All capabilities are provided including permission management.
View Only
Publishing Template
Users may view pages, list items, and documents.
Approve
Publishing Template
Users may approve pages, list items, or documents submitted by others.
Manage Hierarchy
Publishing Template
Users may edit pages, list items, and documents. Manage Hierarchy permissions also allow the users to create sites.
Restricted Read
Publishing Template
Users may view pages and documents; however, historical versions are not available
Read more...

How to Create New SharePoint 2010 Web Application and Configuring Claim Based Authentication

In this post I am going to explain how to create new SharePoint 2010 web application and configure claim based authentication for newly created web App.

Please follow these steps:

1. Launch Central Administration.

2. Select the Application Management section from the left menu.

3. In the Web Applications collection, select Manage Web Applications.

4. On the Web Applications tab of the Ribbon, select New.

5. In the New Web Application screen, select Claims Based Authentication.

     6.  Accept all other defaults and click OK. Be patient. The process of creating a new WebApp can take several minutes.

     7. The Application Created screen will be displayed. Read the provided information and click OK.  

New SharePoint 2010 Web Application

    Note:  You cannot switch from claims based authentication to classic mode authentication. It is possible to convert from classic mode authentication to claims based authentication. 

 The following TechNet article explains the CMA to CBA conversion process: http://technet.microsoft.com/en-us/library/gg251985.aspx.

Read more...

SQL Server Error database principal owns schema cannot be dropped

Recently i was working on one of my SQL Server database project and i got this error message

"The database principal owns a schema in the database, and cannot be dropped. (Microsoft SQL Server, Error: 15138)"

I spent good couple of hours to dig the problem and finally find the solution. The reason for error is quite clear from the error message as there were schema associated with the user and that needs to be transferred to another user.

Lets suppose we have a database 'SharePoint2010' and we are trying to delete user 'uahmed'

Run following query against SharePoint2010 database

USE SharePoint2010;

SELECT s.name
FROM sys.schemas s
WHERE s.principal_id = USER_ID('uahmed');

As a result i am getting these two schema

SQL Server Schema

Now we need to alter authorization of this schema to other schema so that we could drop database owner. In our scenario we have to run alter authorization query twice.

ALTER AUTHORIZATION ON SCHEMA::db_denydatareader TO dbo;

ALTER AUTHORIZATION ON SCHEMA::db_denydatawriter TO dbo;

Now if you will try to drop database owner it will not throw error message.

I hope this post will help you to solve this error message quickly without wasting any time. Please post your comments thanks

Read more...

Error SharePoint Designer does not support editing non-SharePoint sites

Some error messages look complex but some time simple solution can fix it. In this article i am going to explain one of the simple solutions which worked for me to fix SharePoint Designer Error when Designer was complaining, it does not support editing non-SharePoint site.

It happened after installing SharePoint Designer 2010 when i was trying to open a SharePoint 2010 Team Site. The exact error message was: “Microsoft SharePoint Designer does not support editing non-SharePoint sites.” 

Microsoft’s KB describes a way to fix this, but I had already performed the step in this KB through SharePoint 2010 Central Admin. but error message persisted in SharePoint Designer 2010.

Guess What fixed the issue? Simply closing SharePoint Designer and then reopening it :)

SharePoint Designer Error

 

 

Read more...