A Microsoft SharePoint Server State Service error occurred while processing your request. For more information, contact your server farm administrator in SharePoint 2010

I checked many blogs, everybody telling that -
 
1. SQL server doesn't have enough space to process request, but the answer is partly correct. Not every time we shouldn't blame SQL server team... it's just guess.
2. Somebody telling that, Run "Farm Configuration Wizard". Don't ever do that, if you are already provisioned service applications with different settings.(not with default settings). Run "Farm Configuration Wizard" when you farm belongs to 'single server farm'. This trick will not work with multi server farm.
 
Then how do we resolve?
 
Check following settings in CA
 
1. Check wheather 'State Service' has been provisioned or not in CA. CA--> Manage Service Applications--> Check State Service existence.
 
2. Go to respective web application and click on 'Service Connections' on the ribbon. Check whether 'State Service' is part of assiciations or not?

 
3. If not, associate the State service app.

4. If already associated, choose 'Custom' and select all service applications and save settings.

that's it done!!!.

Note: Above steps don't resolve, follow below steps

1. Go to the WFE server where state service provisioned ---> IIS 7.0 --> Recycle respective app pool for the State service.

Difference between Local vs Global Termsets for Managed Meta Data Service in SP 2010

There is a quite difference between Local vs Global Termsets for Managed Meta Data Service in SP 2010.

global term sets
    When you create a term set from the MMS management interface via Central Administration (CA) it is available to all site collections living in Web applications that are connected via a service application proxy to the MMS instance. We refer to these as global term sets because they are available to all sites & site collections that are connected to the MMS
local term sets
    These are different in that they are scoped locally to a specific site collection and can only be used by that site collection, not by other site collections.Local term sets come in handy when site collection owners want to create their own term sets without having to work with librarians. These can be managed from a link in the site collection's Site Settings page or when you modify a column.

Note: There are disadvantages when you use local tem sets, when it comes to portability & DR (back/restore) senarios these term sets are not friendly.

 

Managed Metadata Column Limitations - SP 2010

Hi All,
As everybody thinks that, SharePoint 2010 managed meta data column is very handy and useful for our all list operations and other SPD changes. However, following are limitations about Managed Meta Data column in SP 2010.
Briefly,
1) No InfoPath Support
2) No SharePoint Workspace Support
3) No Support in Office 2007
4) Cannot Edit Managed Metadata values in Datasheet Mode
5) Limitations in Views
6) Extra care required in SharePoint Designer Workflows
7) Feature deployment of Managed Metadata requires care
8 ) Cannot be used in calculated fields
9) Maximum of 250 terms selected per Managed Metadata Column
10) Caution when restoring a Local Term Set to another Content Database
11) Taxonomy feature is not activated on the Blank Site Template
12) Know capacity boundaries
13) Cannot add a Managed Metadata Column through SharePoint Designer
 
I referred following blog, and check below url for detailed explanation about each point mentioned from above list.
http://www.sharepointanalysthq.com/2011/06/managed-metadata-column-limitations/

 

The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.- SP2010 PoweShell

There are two ways to check/resolve the issue. Basically it's related to the SP PowerShell console being not run for your login account.
 
1. Actually this issue belongs -
PowerShell version being used/installed in SP environment. Generally for SP 2010 the version would be 2.0, however, if you install Windows Management Framework 3.0, which will install PowerShell version 3.0. So we have make sure that , our PowerShell should take 2.0 version.
No worries, it's easy to find and update the same.
To find which version, run following command in your SP PowerShell management console.
 
$version = $host | select version
$version.Version
 
If you receive something like below. If the Major version is not on 2, then you will get this runtime error.
Major Minor Build Revision
—– —– —– ——–
3 0 -1 -1
Which means that, you console is running with 3.0 versions. Relax, there is way to point to 2.0 version.

How?
a) Go back to the SharePoint 2010 Management Shell Shortcut, right click and select “Properties”
Under the Shortcut tab, Target: section, insert "-version 2″ into the path. Make sure its before the -NoExit.
b) C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe -version 2 -NoExit ” & ‘ C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ‘ “
c) Click apply, and then Ok.
d) Launch SP PowerShell console. That’s it.. Done.
 
Note: If this approach doesn't work, please follow point 2 below.
 
2. Check whether your login account had farm access or not by using following PowerShell command
Get-SPShellAdmin - if you get same error, it means that, you don't access to farm.
Then login with account which has full rights on farm and run following command to add the user.
Add-SPShellAdmin -username DOMAIN\userid
And also grant full rights on farm configuration db (generally SharePoint_Config, however, it may vary based on your org needs) & SharePoint admin content db.

 

Naming conventions/format for various SharePoint 2010 components

As a Architect/Admin, in a day to day activities we are supposed to follow few standards to create SP components like

Service accounts

Web Applications

Service applications

Application pools

Content DBs

Solution Packages

Service accounts

Example – SPSVCQADMIN where SP stands for – SharePoint, SVC stands for Service account, Q stands for QA. Likewise we will use same format for DEV & Production as well by replacing Q with D & P respectively. And password should be different for each account.

Please refer following link for remaining naming conventions – http://christoffervonsabsay.wordpress.com/2011/12/28/naming-conventions-for-sharepoint-2010-environments/

 

PowerShell script to deploy Multiple Sandbox solutions

Applies to SPFoundation 2010, SP 2010, SPFoundation 2013,SP 2013

Points to be noted:
1. Replace $siteURL with url
2. All wsps should be in the current directory of the script (.ps1)

Add-PsSnapin Microsoft.SharePoint.PowerShell
$logfile=$CurrentDir + "\log.log"
$siteURL = "xxxxxxx"
Start-Transcript $logfile
#Do not modify anything in the script from here onwards
function Get-ScriptDirectory
{
 $Invocation = (Get-Variable MyInvocation -Scope 1).Value
 Split-Path $Invocation.MyCommand.Path
}
function Deploy-Solution{
param(
[string]$physicalPath,
[string]$name)
$SolutionName = $name
$SolutionPath = Join-Path ($physicalPath) $SolutionName
echo "Extracting information from $physicalPath"
$Solution = Get-SPUserSolution -site $siteURL | Where { ($SolutionName -eq $_.Name) }  -ErrorAction SilentlyContinue
if ($Solution -ne $null)
{
    if($Solution.Status -eq "Activated")
    {
    Write-Host 'Poweshell Script will now retract solution:' $SolutionName
    Uninstall-SPUserSolution -Identity $SolutionName -Site $SiteURL -Confirm:$false
    Write-Host 'Successfully retracted solution:' $SolutionName
    }
    Write-Host 'Removing Solution:' $SolutionName
    Remove-SPUserSolution -Identity $SolutionName -Site $siteURL -Confirm:$false
    Write-Host 'Successfully removed Solution:' $SolutionName
}
Write-Host 'Poweshell Script will now add solution:' $SolutionName
Add-SPUserSolution –LiteralPath $SolutionPath -Site $SiteURL
Write-Host 'Poweshell Script will now deploy solution:' $SolutionName
Install-SPUserSolution -Identity $SolutionName -Site $SiteURL
Write-Host 'Poweshell Script has finished deployment of solution:' $SolutionName
}
#Get Current Physical Path
$currentPhysicalPath = Get-ScriptDirectory
#Iterate through all .wsp files in the current Physical Path to deploy solution
get-childitem $currentPhysicalPath -include *.wsp -recurse | foreach ($_) {Deploy-Solution $currentPhysicalPath $_.name}
Stop-Transcript
#Remove SharePoint Snapin
Remove-PsSnapin Microsoft.SharePoint.PowerShell

Echo Finish

PowerShell script to deploy Sandbox solution

Applies to SPFoundation 2010, SP 2010, SPFoundation 2013,SP 2013

In general we will write a script to deploy farm solutions. But we will upload sandbox solutions into site collection solution gallery. What if, we want to automate the process to deploy sandbox solution without uploading.... here is the script

Points to be noted:
1. The .wsp should be in the current directory of the script (.ps1)
2. Replace $solutionName with your solution name.
3. Replace $SiteURL with your site collection url.

Add-PsSnapin Microsoft.SharePoint.PowerShell
Write-Host 'Poweshell Script will initialize parameters'
$CurrentDir=$args[0]
$solutionName="xxxx.wsp"
$SolutionPath=$CurrentDir + "\"+$solutionName
$logfile=$CurrentDir + "\log.log"
$SiteURL = "xxxxxxx"
Start-Transcript $logfile
$errorActionPreference = 'Inquire'
$solution = Get-SPUserSolution -site $siteURL | Where { ($solutionName -eq $_.Name) }  -ErrorAction SilentlyContinue 
try
{
if ($solution -ne $null)
{
if($solution.Status -eq "Activated")
{
Write-Host 'Poweshell Script will now retract solution:' $solutionName
Uninstall-SPUserSolution -Identity $solutionName -Site $SiteURL -Confirm:$false
Write-Host 'Successfully retracted solution:' $solutionName
}
Write-Host 'Removing Solution:' $solutionName
Remove-SPUserSolution -Identity $solutionName -Site $siteURL -Confirm:$false
Write-Host 'Successfully removed Solution:' $solutionName
}
Write-Host 'Poweshell Script will now add solution:' $solutionName
Add-SPUserSolution –LiteralPath $SolutionPath -Site $SiteURL
Write-Host 'Poweshell Script will now deploy solution:' $solutionName
Install-SPUserSolution -Identity $solutionName -Site $SiteURL
Write-Host 'Poweshell Script has finished deployment of solution:' $solutionName
}

catch [system.Exception]
{
Write-Error 'An Unknown error occured while trying to deploy/redeploying the solution:' $_.Exception.Message
}

Stop-Transcript
Remove-PsSnapin Microsoft.SharePoint.PowerShell

Happy powershell programming......