Tuesday, February 4, 2014

State service error message

SharePoint makes it easy to modify your list input forms using the new design the form page in InfoPath 2010 option

You can just open your list and click Customize form button in ribbon.

But sometimes while publishing the form you may see the error message as

"The form cannot be rendered. This may be due to Misconfiguration of the Microsoft SharePoint state service. For more information contact your server administrator" 

one possible cause of this error could be that the SharePoint 2010 farm was created manually without running the PS configuration wizard.

To configure the SharePoint 2010 state service using the PowerShell try the following:

1. open your Central Administration in the Browser.
2. On task bar, click Start, select Administrative tools and then windows PowerShell modules, this will launch PowerShell and load all required modules.
3. In windows PowerShell window create an application by typing this command.
   $serviceapp =New-SPStateServiceApplication -Name "State Service"

4. Associate a Database with this application

New- SPStateServiceDatabase -Name "StateServiceDatabase" -ServiceApplication $serviceapp

5. Create a State Service Application Proxy and associate it with service application by typing the Following command

New-SPStateServiceApplicationProxy -Name "State Service" -ServiceApplication $serviceApp -DefaultProxyGroup.

This will create the State service Application in CA

next you need to check is that you application is associated with this state service application.

just go ahead and publish your InfoPath form, it should work now :)

No comments:

Popular Posts


The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.