title: Error 5337 submitting InfoPath form to SharePoint
body: <p>I have some InfoPath 2010 forms with custom code that submits information to SharePoint 2010 form-enabled libraries. One of the forms has a date field, chosen by a picker and stored in a Date/Time column in the library. The form had been working fine for months, but one day it just started failing with the following error:</p>
  
  <pre><code>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. 
  </code></pre>
  
  <p>When I click "show error details", it shows error code 5337 and gives a correlation ID.</p>
  
  <p>When I look up the error in the event log, the details are as follows:</p>
  
  <pre><code>Business logic failed due to an exception. (User: XXX\frank, Form 
  Name: Miscellaneous Form, IP: , Request:
  http://intranet//apps/_layouts/FormServer.aspx
  XsnLocation=/FormServerTemplates/Miscellaneous  
  Form.xsn&amp;Source=/apps/SitePages/expenses.aspx&amp;DefaultItemOpen=1, 
  Form ID: urn:schemas-microsoft-com:office:infopath:
  Miscellaneous-Form:-myXSD-2012-05-14T12-19-23, 
  Type: FormatException, 
  Exception Message: String was not recognized as a valid DateTime.)
  </code></pre>
  
  <p>I am at a complete loss to understand how this problem can have arisen. No aspect of the solution was touched between when it was working and when it stopped. The date format on the InfoPath form is the same as the date format in the SharePoint list column. The system locale and regional settings are consistent everywhere and have not been changed. The problem arose after a slew of Windows updates on the 20th of January, so I'm wondering if one of those might have caused the problem. </p>
  
  <p>The next steps I plan to take are to rebuild and redeploy the form to see if that fixes the problems. However this is code I inherited and it's part of a larger solution, so I'm nervous about redeployment in case I break other things. That's why I wanted to ask here if anyone has come across this or a similar problem before and can to point out something obvious that I might have overlooked.</p>
  
  <p>Thanks for taking the trouble to read this. Any advice would be very much appreciated.</p>