Solving: The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator.

To solve this error, you have first to configure the SharePoint State Service using PowerShell as the following:

1. Open SharePoint (SSSE) PowerShell as Administrator.

2. Run the below cmdlet to create a new SharePoint State Service.

    $serviceApp = New-SPStateServiceApplication -Name "State Service Application"
   

3. Again, run the below cmdlet to create the SharePoint State Service Database.

    New-SPStateServiceDatabase -Name "SharePoint_Service_StateDB" -ServiceApplication $serviceApp
   

4. Finally, run the below cmdlet to create a new SharePoint State Service Proxy and attach it with the newly created SharePoint State Service.

    New-SPStateServiceApplicationProxy -Name "State Service Application Proxy" -ServiceApplication $serviceApp -DefaultProxyGroup
   

5. Open SharePoint Central Administration > Application Management > Manage Service Application, Make sure that the SharePoint State Service is listed with its proxy and started properly.

Also here: The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service - deBUG.to

If you cannot create a SharePoint Search Application in Central Admin and see this message.

Clear the cache as explained here!

1. Open the Services.msc panel, and then look for the SharePoint Timer Service.
2. Stop this service.
3. Open Windows Explorer, and then navigate to the cache folder at: C:\ProgramData\Microsoft\SharePoint\Config.
4. Look for the most recent cache folder, and then open it.
5. Delete all files in this folder EXCEPT cache.ini.
6. Open the cache.ini file in a text editor, and then randomly modify the number, but keep it at the same number of digits.
7. Save the cache.ini file.
8. Start the SharePoint Timer Service.
9. Open a command prompt as Administrator.
10. Run the following command: Psconfig.exe -cmd upgrade -inplace b2b -wait -force
11. Check the Upgrade Status. 

I recently got this error when trying to run the SharePoint Subscription Edition Search.

The solution for me was items 1 and 2 in this blog post https://social.technet.microsoft.com/wiki/contents/articles/25863.access-is-denied-verify-that-either-the-default-content-access-account-has-access-to-this-repository-or-add-a-crawl-rule-to-crawl-this-repository.aspx

This is the post, just in case it ever disappears.

Introduction

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository.

Issue

Once we configure Search and started all the Related services, when we start the Crawl and crawl failed and shows one of the errors below. This contains all the issues and solutions related to “search crawling” in one plate that everyone can easily able to get the solution quick. All the issues and resolutions are below.

Errors

1. Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled. (HttpStatusCode Unauthorized The request failed with HTTP Status 401: Unauthorized.)
2. “An unrecognized HTTP response was received when attempting to crawl this item. Verify whether the item can be accessed using your browser.”
3. “The secure sockets layer (SSL) certificate sent by the server was invalid and this item will not be crawled.”
4. The URL of the item could not be resolved. The repository might be unavailable, or the crawler proxy settings are not configured.
5. The SharePoint item being crawled returned an error when requesting data from the web service.

Solutions

There could be many reasons that search is not working properly even when we configured everything good. This article is providing all the relevant and related solutions to check. Every solution that you need to take into consideration and apply to resolve the issues. One of the mentioned solutions that definitely work and resolve the issue.

Solution 1

Disable Loopback Check: It is actually a security feature that prevents access to a web application with a fully qualified domain name to from the host server. Follow these steps to disable this feature

· Click Start, click Run, type regedit, and then click OK.
· In Registry Editor, locate and then click the following registry key:
· HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
· Right-click Lsa, point to New, and then click DWORD(32-bit) Value.
· Type DisableLoopbackCheck, and then press ENTER.
· Right-click DisableLoopbackCheck, and then click Modify.
· In the Value data box, type 1, and then click OK.
· Quit Registry Editor, and then restart your computer.

Solution 2

Specify host names: To specify the host names that are mapped to the loopback address and can connect to Web sites. This method would be preferred for NTLM authentications.

· Click Start, click Run, type regedit, and then click OK.
· In Registry Editor, locate and then click the following registry key:
· HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
· Right-click MSV1_0, point to New, and then click Multi-String Value.
· Type BackConnectionHostNames, and then press ENTER.
· Right-click BackConnectionHostNames, and then click Modify.
· In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
· Quit Registry Editor, and then restart the IISAdmin Service

Solution 3

Check the Permissions correctly: This item should need to check in many areas. Be patient and check one-by-one to ensure that all set correctly

Check 1

When you’re crawling the search. Make sure that the default content access account (crawl account) has access to the User Profile Service
· Open the Central Administration and go to Application Management
· Click Manage service application in the Service Application section
· Select the User Profile Service Application and click on Administrators
· Add your content access account and give it the Retrieve People Data for Search Crawlers permission

Check 2

When you’re crawling the search. Make sure that the default content access account (crawl account) has access to the Search service.

· Open the Central Administration and go to Application Management
· Click Manage service application in the Service Application section
· Select the Search Service Application and click on Administrators
· Add your content access account and give it the Full control permission

Check 3

When you’re crawling the search. Make sure that the default content access account (crawl account) has access to the web applications that are crawling.
· Open the Central Administration and go to Application Management
· Click on web applications
· Select the web application -> check the user policy on Ribbon
· Add your content access account and give it the Full control permission

Solution 4

Host Headers: If you’re using a multi-server farm, having the below servers in farm.
· Server A - Application server
· Server B – WFE
· Server C- Crawl server

We need to create the Host headers in All the WFE, Crawl servers to crawl the Content. Go to below path and create the headers. Refer below article:
http://expertsharepoint.blogspot.de/2013/10/path-for-host-file.html

In the Headers,
· For WFE servers- Need to put the Server IP of the local server
· For Crawl Server- Need to put the Server IP of the WFE server

If you have multiple WFE,Crawl servers. You need to choose one of WFE server IP and put the same IP in all WFE, crawl servers also.
Note: We can apply these solutions one after one and test the status of crawl.
See more at: http://expertsharepoint.blogspot.de/2014/05/access-is-denied-verify-that-either.html

Note: Resolved the issue by above method. If you find a different solution, please report it as a comment to this post. This will be useful to SharePoint community. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.