Receiving an Unspecified Error when submitting to SQL Server from SharePoint (2010) but only after Form is reopened - InfoPath Dev
in

InfoPath Dev

Receiving an Unspecified Error when submitting to SQL Server from SharePoint (2010) but only after Form is reopened

Last post 11-28-2011 08:52 AM by DanDeHaven. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 11-28-2011 08:52 AM

    Receiving an Unspecified Error when submitting to SQL Server from SharePoint (2010) but only after Form is reopened

    I created a Form Template library that holds forms that submit to SQL Server (2008 R2). I'm using InfoPath 2010 and SharePoint 2010. The forms submit fine with no errors when they are initially created via the "New" button/process. But when any of the saved forms are reopened and a value changed, the Submit produces an Error:

    InfoPath cannot submit the form.The OnSubmitRequest event handler did not work.InfoPath cannot submit the form.An error occurred while the form was being submitted.InfoPath cannot connect to the data source.

    Unspecified error

       at Microsoft.Office.InfoPath.Internal.MomExceptionHelper.ExecuteDataConnectionAction(XmlFormHost formHost, OMCall d)
       at Microsoft.Office.InfoPath.Internal.AdoSubmitConnectionHost.Execute()
       at My_Form.FormCode.FormEvents_Submit(Object sender, SubmitEventArgs e)
       at Microsoft.Office.InfoPath.Internal.FormEventsHost.OnSubmit(DocReturnEvent pEvent)
       at Microsoft.Office.Interop.InfoPath.SemiTrust._XDocumentEventSink2_SinkHelper.OnSubmitRequest(DocReturnEvent pEvent)

    The forms are using Data Connections that are saved to a Data Connection Library in the same SharePoint Site, they have been converted to udcx files and have been approved. 

    The same forms will submit (Update) after being initially saved, if they are not saved to SharePoint, so I know it's not the forms or Data Connections.

    I'm sure this was working without error in the past and I'm not sure if there has been an update from Microsoft that would have caused this or if some other setting in SharePoint Admin would be the problem? I'm not our SharePoint Admin so I'm kinda at a loss.

    Any thoughts?

    Thanks!!!

Page 1 of 1 (1 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.