SharePoint Experts, Information Architects, Expert Witness

SICG provides a broad array of business and technology consulting from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. We focus on the "How", not just the possible. Contact me direct: or call 704-873-8846 x704.

Search This Blog

Wednesday, March 23, 2011

SharePoint State Service (2013 and 2010)

When setting up SharePoint, it is necessary to start up the State Service for SharePoint to work correctly. You'll see this specifically in SharePoint 2013 Health Analyzer - it will indicate that InfoPath forms won't work because no State Service has been established.

Fixing this is done using the SharePoint Management PowerShell using the following script:

PS C:\users\SPFarmAcct> $theServiceApp = New-SPStateServiceApplication -Name “State Service”

Where "State Service" is the name of the service - usually State Service but doesn't have to be.

IF YOU RECEIVE “The Specified Name is not unique” you can skip next step and simply exit (it means the service is already running). If not however, you have to create the State Service Database and associate it with a service application:

PS C:\users\SPFarmAcct> New-SPStateServiceDatabase -Name ”StateServiceDatabase” -ServiceApplication $theServiceApp

Where "StateServiceDatabase" is the name you want to use (be sure to use any standards in naming if you have them - and you should!).

Once the database has been created, you need to create the State Service Application Proxy and associate it with the service application:

PS C:\users\SPFarmAcct> New-SPStateServiceApplicationProxy -Name ”State Service” -ServiceApplication $theServiceApp –DefaultProxyGroup

Where "State Service" is the name of the service (must match the one you used on the first command).

1 comment:

Vincent said...

You are a goll-dern lifesaver!