17 May, 2013

The security validation for this page has timed out. Click Back in your Web browser, refresh the page, and try your operation again.

Problem Description:
The security validation for this page has timed out" error message when a user submits data to Windows SharePoint Services

Guys, this is an informative article this time as I faced this error message with respect to session time out exception while adding webparts.

Error Message:
The security validation for this page has timed out. Click back in your Web browser, refresh the page, and try your operation again.

if you are facing this error message then Microsoft has already published an article on this which is very useful and resolves your issues. Million thanks to Microsoft for publishing this detail information along with root cause.

Thank you Microsoft…


If you have any questions regarding the above mentioned information then please let me know.

I would be more than happy to help you as well as resolves your issues, Thank you.

15 May, 2013

Create Site Collections, Subsites, Custom List by using PowerShell- SharePoint 2010


Creating of subsites, site collections, custom lists, and document libraries can be easily created by using GUI (i.e. Graphical User Interface) – very easy-correct? But let me tell you guys that all this activities are easier if you do it by using PowerShell. That’s why I am sharing the same so that you can use the following things in day to day activities.



What we are going to check in this article?
-Creation of site collections
-Creation of subsites
-Creation of custom list’s

HOW TO CREATE A SUBSITE IN SHAREPOINT 2010 BY USING POWERSHELL?

New-SPWeb –url<new site url> -name <new site name> -template <template name>

SUBSITE CREATION ALONG WITH SOME ADDITIONAL PARAMETERS:

New-SPWeb –url http://sharepoint2010/sites/MOSS2010/SUB2010 -name "All about SUBSITES" -template STS#0 –AddToTopNav –UniquePermissions –UseParentTopNav

HOW TO CREATE SITE COLLECTION IN SHAREPOINT 2010 USING POWERSHELL?

$siteURL = “http://sharepoint2010/sites/MOSS2010;

$owner = “moss2010/SPAdministrator1”

$secondOwner = “moss2010/SPAdministrator2”

$template = “STS#0″

$description = “PowerShell created Site Collection”

New-SPSite $siteURL -OwnerAlias $owner -SecondaryOwnerAlias $secondOwner -name “PowerShell for SharePoint” -Template $template -Description $description

HOW TO CREATE A CUSTOM LIST IN SHAREPOINT 2010 BY USING POWERSHELL?

$SPAssignment = Start-SPAssignment

$SPWeb = Get-SPWeb http://siteURL -AssignmentCollection $spAssignment

$SPWeb.ListTemplates | Select Name, Description

$SPTemplate = $SPWeb.ListTemplates["Custom List"]

$SPWeb.Lists.Add("List Title","Description",$SPTemplate)

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you.

12 May, 2013

Deletion of Subsite, Site Collection, Document Library, SharePoint List- SharePoint 2010

Most commonly used entities in SharePoint are Subsite, site collection, list and libraries. 

GUI mode will be the easiest mode to do any functional activities associated with them. In this article, i am more concentrating on the PowerShell mode because its very easy and efficient way to clean the activity directly from the database. 

Let's try to explore some deletion functionalities by means of PowerShell.

How to delete a site collection by using PowerShell?
Remove-SPSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DeleteADAccounts <SwitchParameter>] [-GradualDelete <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

Example: Remove-SPSite -Identity http://SharePoint2010/sites/test2010

Where:
SharePoint2010: web application URL.
Sites: wildcard entry.
test2010: site collection that you want to delete.

Note: The above will completely deletes an existing site collection and all subsites. This operation cannot be undone.

How to delete a Subsite by using PowerShell?
Remove-SPWeb [-Identity] <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Recycle <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

Example: Remove-SPWeb -Identity http://SharePoint2010/sites/test2010/subtest2010

Where:
SharePoint2010: web application URL.
Sites: wildcard entry.
test2010: site collection
subtest2010: Subsite that you want to delete.

If you want to delete multiple subsites in a single shot from a site collection then please refer the following site: http://get-spscripts.com/2010/10/delete-sharepoint-sub-sites-using.html

How to delete a Document Library by using PowerShell?
Please refer the following code by which you can delete a document library without any issues...

$web = Get-SPWeb urlofweb
$library = $web.lists["listname"]
$library.Delete()

How to delete a SharePoint List by using PowerShell?
Get-SPWeb “site collection link” | % {$_.Lists.Delete([System.Guid]$_.Lists["name of list"].ID)}

The above command will delete the mentioned list without any issues...

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you. I would be more than happy to help you as well as resolves your issues...

07 May, 2013

EXECUTE permission was denied on the object 'proc_putObject', database 'SharePoint_Config', schema 'dbo'


Problem Description:
 While I am deploying my solution in to SharePoint, it's throwing an exception as follows:

Error Message:
EXECUTE permission was denied on the object 'proc_putObject', database 'SharePoint_Config', schema 'dbo'

Logs analysis:
The EXECUTE permission was denied on the object 'proc_putObject', database 'SharePoint_Config', schema 'dbo'.   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command)
   at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)
   at Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject obj, Boolean ensure)
   at Microsoft.SharePoint.Administration.SPPersistedObject.Update()

Root cause: Permissions

This error appears to be an issue with the permissions to the SharePoint configuration database.The general recommendation I found was to ensure that the application pool identity of the web application has sufficient permissions on the config database.

Resolution:
Million thanks to Microsoft's Team who has created this article:

Details Steps:
-In order to resolve the issue, I provided Execute permission to the database role “WSS_Content_Application_Pools” into the stored procedure “proc_putObject”. I performed the following steps to do this.
-In the database server, expand SharePoint Config database and naviage to Programmability/Stored Procedures/dbo.proc_putObject using SQL Server Management Studio.
-Right click on the above stored procedure and select Properties.
-On the popup screen, select Permissions on the left and click Search button.
-On the new popup screen, click Search, select [WSS_Content_Application_Pools] database role and click OK.
-Click OK again.
-On the first popup screen, select the role, check Execute permission and click OK.

If you have any queries/questions then please let me know, thank you.