SharePoint 2013 State Service Configuration

“The State Service is a shared service that is used by some Microsoft SharePoint Server 2010 components to store temporary data across related HTTP requests in a SQL Server database. In SharePoint Server 2010, the State Service is required by InfoPath Forms Services (including out of the box and custom workflow forms), the SharePoint Server 2010 Chart Web Part, and certain Microsoft Visio 2010 scenarios that do not use Microsoft Silverlight 3.”

The above quote detailing the SharePoint 2010 State service, which best I can tell serves the same purpose in 2013, comes from this technet article:

Update: I recently found this quote… “The State Service must be properly configured for the Search Administration Crawl and Query Health Reports to function properly.”

on this wiki

I think it is pretty clear that this is something that needs to be configured for every SharePoint 2013 install.

Just like in SharePoint 2010 there are only 2 ways to provision the State Service.  One is with the Wizard that provisions everything else, and the other is with powershell.  Since I never use the wizard, I’m left with Powershell as my only option.

To do this simply change the names to whatever you want, copy each line below individually into the command shell and press enter after each.

$stateName = “State Service”

$stateDBName = “SP2013_State_Service”

$stateDB = New-SPStateServiceDatabase -Name $stateDBName

$state = New-SPStateServiceApplication -Name $stateName -Database $stateDB

New-SPStateServiceApplicationProxy -Name “$stateName Proxy” -ServiceApplication $state –DefaultProxyGroup

When you have successfully configured the State Service you will see this in your powershell window:



About tbithell
I am the Chief Technical Architect of Portals at B2B Technologies, LLC in Atlanta GA. I first started working on SharePoint in 2005, and have built SharePoint portals and developed custom solutions for a wide variety of users. I have a MS in Computer Science and am a SharePoint 2010 MCITP and MCPD. I am very excited about the new version, and will be blogging about it on a regular basis as I explore the newly released Preview and future releases.

7 Responses to SharePoint 2013 State Service Configuration

  1. Askanoulis says:

    Power Shell wont do the trick I think. It has to be SharePoint Management Shell. Otherwise the New-SPStateServiceApplication wont be recognized.

  2. Bill Burke says:

    Worked nicely, thank you. (Yes, used Sharepoint 2013 Management Shell)

  3. mcbadass says:

    This worked great! Thanks for posting this.

  4. Pingback: Blog de Juan Carlos González en Geeks.MS

  5. HI. I know this is an old posting but I have a question. When configuring the state service, say on a farm that has two web front-end server and two application servers, does this service application need to be configured on each server or just once and it should work for all servers?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: