Forum Discussion

sujeetsks's avatar
sujeetsks
Copper Contributor
Apr 16, 2019

SoapServerException error when customizing list form (SPO and SP-onprem) using InfoPath designer

 

 

Symptoms

When you click on the “customize InfoPath” option in a Sharepoint list, you receive the following error:

SOAP response indicates that an error occurred on the server: Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown. [detail][errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/"] List does not exist. The page you selected contains a list that does not exist. It may have been deleted by another user. [/errorstring][errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/"]0x82000006[/errorcode][/detail]

 

Cause

This is a known issue on Windows 10 related to the update that is listed in KB 4489886, and is  documented under the section "Known issues in this update".

 

Workarounds

Workaround 1:

  1. Go to List setting.
  2. Select Form setting.
  3. Select Customize in InfoPath.

Workaround 2:

You can open InfoPath, choose “Customize SharePoint List” from the startup options, and provide the URL of their list to open it in InfoPath directly.

 

More information

Microsoft is aware of the issue. At this point apply the workaround until further update.

15 Replies

  • miridab's avatar
    miridab
    Copper Contributor
    After getting the error message, if you go back to the list ribbon and click Customize Form, the form opens up properly in InfoPath.
  • sujeetsks 

     

    This is also didn't work for me, but found a work around 

    from the list go to “Edit List in SharePoint Designer” then when you open designer go to “Design Form in InfoPhath"

     

    Good luck

    Sameh

    • MHAon's avatar
      MHAon
      Copper Contributor
      Thank you so much! I've been looking for a workaround on this. I've been getting error messages when going to Form settings that "Internet Explorer is needed" for that action (when I was literally working off it). This did the trick!
  • TimLB's avatar
    TimLB
    Iron Contributor

    sujeetsks We actually just got done working with MS troubleshooting this.

     

    Hopefully it isn't a widespread problem...

    Workaround for us was a registry key replacement via GPO.

     

    This one - HKEY_CLASSES_ROOT\ms-infopath\shell\open\command.

     

    Don't want to post the full workaround because if it seems to be effecting others then it would be a good idea for others to open a incident to give them some metrics to track and prioritize a root cause investigation with a fix.

     

     

     

     

    • Sujeet Sharma's avatar
      Sujeet Sharma
      Former Employee

      TimLB 

       

      I am in MS InfoPath team. I am aware about the registry changes workaround. But, have not posted it online since, that is envinronment dependent. The registry changes would change based on versions of office and InfoPath. Also, with our overall testing the registry workaround is not consistent across machines. So, these changes are not recommended around now.

Resources