SOAP message could not be parsed

Over the last few days I have had a problem publishing an InfoPath form to a SharePoint 2010 list, this took me almost 2 days solid work to resolve so I hope this post saves somebody else’s time….

I have a SharePoint list which uses a custom InfoPath form. The list has been used in a production environment for a few months so it has grown to over 30k items.

I had been asked to make a change to the InfoPath form, so I made the change and clicked publish – I get the error “The SOAP message could not be parsed” after some googling I found out this was because of the high amount of items in the list. So I then created an identical list, using content and structure I moved all of the items from the first list (this took ages as it only does it 1000 at a time) I then made the changes to the InfoPath form and published it. Tested it worked (which it did) then I moved all of the items back again using content and structure (I moved the data this way as I needed to retain the created/modified fields).

After moving all of the data back, I tested the form and it had reverted back to how it was before I started this process! grrr

So I decided to check the logs (I know this should have been my first port of call) I could see in the logs that the SOAP message was really just InfoPath’s lack of understanding SharePoint errors and it was really a timeout error. So my next port of call was to edit the web.config file to increase the http timeout, you can do this by going to the drive your IIS stores its data > Inetpub > wwwroot > wss > VirtualDirectories > “your web app” . Edit the web.config file in a text editor like notepad; look for this line of code –

<httpRuntime maxRequestLength=”2097151″ executionTimeout=”3600″ />

Then increase the executionTimeout,  in my case it was already at 3600 (I had already increased this when I built the server) This should have been more than enough, just in case I added a few zeros, saved the file and reset ISS.

I then clicked in my SharePoint list, clicked customize InfoPath form, made my changes and clicked publish……. I got the SOAP message again.

Back to the drawing board again! I then changed the execution time out on the web.config file back to how I found it as it was clear this had not made a difference.

So I knew it was timing out but I wasn’t sure why, after all, the default timeout setting was not causing the issue.

At this point I went through all of the InfoPath service settings which I won’t go into detail on as they were not the problem.

As this particular list had several calculated fields I decided to delete these and try again, after all, as the InfoPath form publishes it updates every item in the list, so it was logical that the calculated fields would then try to update too and cause a long session. When I went to delete these columns I received an error “This page has been modified since you last opened it”. From previous experienced I knew this was a custom branding issue, so I reset my master page back to the out of the box V4 and tried to delete the calculated columns again, this time they deleted fine.

I then clicked on customise form, made the changes to the InfoPath form, clicked publish …. It worked!!

So after all my work it turned out that it was the calculated fields, which in turn had problems due to the custom branding.  After testing the InfoPath input form was working as I wanted it to I then recreated the calculated fields, tested the form again, then set my custom master page as default and again tested the form. It all worked!


19 thoughts on “SOAP message could not be parsed

  1. David says:

    I am new to Sharpoint/Infopath. When I try to use customize form on standard view SP List, it comes back with “Infopath cannot generate a form templage for the SP list. Details – The SOAP message cannot be parsed. Any suggestions how to fix. THANKS.

  2. Vincent Paternoster says:

    Awesome – I struggled through that myself for days.
    I removed the calculated columns and voila, i can now publish the form updates again.

    The only challenge can be around the situation of having a need for the calculated column in the form.

    Thank you so much for explaining!

    • beanyjon says:

      Glad I could help, it becomes a pain when you just need to make small changes to a large list with multiple calculated columns but until Microsoft make a fix its the best work around I have found.

    • Brian says:

      Vincent , when you say ‘remove the calculated columns’, do you mean that you just delete them from the Field List task pane. I guess this does not remove them from the actual sharepoint list, right?

      • Brian says:

        Vincent, sorry, what I meant was, how do you remove the calculated columns, but still keep them in the SharePoint list. I do not need to see the calculated columns in my form

  3. beanyjon says:

    Brian, litterally delete the calculated columns (obviously making a copy of the forumular and column name before hand) then make your infopath changes, then create the column(s) again. Although it doesnt seem the most practical way, as calculated columns calculate on the fly as you create them again they will re-calculate and your data set will be back to how it was.
    If you have a big data set it may take some time after clicking “ok” on creating the calculated column before it goes through, this is because it is re calculating every row, just leave it to do it. If you press back or refresh you may cause issues. I did this on a list with over 100000 items and it took about 10 mins before the page refreshed.

  4. sk says:

    I am getting same error when I try to publish InfoPath form. In my case I had to change the column names for the list and add few new columns. When I updated the column changes in the InfoPath form and clicked to publish it waits for longtime and throws error msg “SOAP message could not be parsed”. I have around 23 calculated fields in the list. Do you think if I remove them from InfoPath form it should get published. Right now I see all the calculated fields in InfoPath form when I open SP list customize form in InfoPath designer.


    • Vincent Paternoster says:

      The problem is not with the form. As GC mentions, it is the deletion of the calculated fields from the list that will allow the publishing of the form.
      Perhaps you can reproduce some formula inside the form as a replacement of the calculated field.
      23 calculated field is quite abit to recreate each time you need to publish the form!

      Good luck,

  5. GC says:

    i can confirm deleting the calculated columns resolved the issue…thanks for the post

  6. Masha says:

    Thank you! Help me a lot!

  7. Kannan says:

    Awesome dude. I have found this page lately, otherwise could’ve fixed the issue much earlier.
    BTW, in my case, there is no custom feature. However just a calculated field was the culprit. Deleted it and all is fine.

    Thanks for sharing the info.

  8. Neha says:

    Thanks for sharing this information
    “My Problem was resolved”

  9. 355781aa says:

    You are really savior! I was struggling to solve the issue and now it is working again

  10. Mr. Great-full says:

    Savior Indeed!

  11. giuseppe says:

    Very Great Solution !!!!
    you are the biggest one

  12. LK Wollett says:

    Thank you a thousand times for researching and posting this. When I removed the calculated fields from the InfoPath form connected to a SharePoint list, the form published easily.

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 )

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