다음을 통해 공유

SharePoint 2016 InfoPath Troubleshooting: "There has been an error while processing the form"

  • 아티클

Warning There has been an error while processing the form. click OK to resume filling out the form. You may want to check your form data for errors.

https://manojviduranga.files.wordpress.com/2017/03/clip_image0016_thumb.png?w=452&h=351

Let me guess, you have gone through all possible verifications on data sources and form fields and everything pretty well developed and verified ? same goes for me. one of my colleague was developing a form and she came up with this error on SharePoint 2016 recently.

She was using GetUserProfileByName SOAP Web Service to fetch current user’s group in to a field, and that’s where this error prompts. that was verified by removing the particular connection and rules filling up data.

After verifying form fields, Data connections and other basics, I decided to inspect the infrastructure step by step. SharePoint logs and Event Log did not had any relevant entry. Finally in the lonely boat, I took following steps one after one to sail towards an island.

1. Enabled all InfoPath services from CA (General Application Settings) – Everything is already set

https://manojviduranga.files.wordpress.com/2017/03/clip_image0018_thumb.png?w=610&h=202

https://manojviduranga.files.wordpress.com/2017/03/clip_image002_thumb.png?w=441&h=258

https://manojviduranga.files.wordpress.com/2017/03/clip_image003_thumb.png?w=896&h=274

2. Registered the HTMLCHKR – no luck

regsvr32 “C:\Program Files\Common Files\Microsoft Shared\OFFICE14\htmlchkr.dll”

  1. 3. Added the target site to InfoPath application’s trusted Locations – no luck
  2.  
  3. https://manojviduranga.files.wordpress.com/2017/03/clip_image00110_thumb.png?w=516&h=202https://manojviduranga.files.wordpress.com/2017/03/clip_image0026_thumb.png?w=819&h=239
  5. 4. Restarted and recycled Security Token Service Application/pool for all WFEs – no luck
  6. https://manojviduranga.files.wordpress.com/2017/03/image_thumb.png?w=602&h=398
  7. 5. Restarted Servers – no luck

Two last steps were able to shed some lights !

6. Disabled loopback check

What is Loopback check?. If you have been prompted continuously for credentials in a SharePoint server when you try to access your site within that server, that’s obviously because of loopback.

Microsoft: Windows Server 2003 SP1 introduced a loopback security check. This feature is obviously also present in Windows Server 2008/12. The feature prevents access to a web application using a fully qualified domain name (FQDN) if an attempt to access it takes place from a machine that hosts that application. The end result is a 401.1 Access Denied from the web server and a logon failure in the event log.
Unfortunately 401.1 is not really helpful as this error code means there is a problem with the user credentials. Of course, the HTTP spec doesn’t know about security features in a vendor’s implementation so there can’t be a HTTP error code for such a feature. This can lead to much banging of the head on the desk. It’s one of numerous causes of the 401.1 which are nothing to do with invalid credentials (e.g. attempting to use Kernel Mode Authentication with domain account in IIS7).

Option1 : Logged in to target SharePoint Server/s and launch PowerShell as administrator, then ran – New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -value “1” -PropertyType dword)

You don’t need to add it if its exists (means loopback is already disabled)

https://manojviduranga.files.wordpress.com/2017/03/clip_image0014_thumb.png?w=839&h=141

  1. Option 2: You can also Add this registry entry manually
  2. Click Start, click Run, type regedit, and then click OK
  3. In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  4. Right-click Lsa, point to New, and then click DWORD Value. (In Win 2008, its DWORD 32bit)

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.

  1. Then I ran SharePoint Product Configuration wizard on SharePoint Server just to give it a refreshment.

After restarting Servers, added the form connection and rules back and InfoPath form loaded perfectly normally !