Qdabra Database Accelerator

Re: Problems with multiple saves within an existing DBXL document

RandyCandy — Mon, 08 Oct 2012 07:58:58 GMT

I'm also using version 2.6, and I don't have any problems with it.

Re: Problems with multiple saves within an existing DBXL document

Jimmy — Mon, 23 Jul 2012 17:58:37 GMT

Hello Jeff,

It sounds like you have a relatively old version of 2.6. How long ago did you download it?

There was a change in 2.6 that probably would cause this issue, but we identified it as problematic and remedied the issue on Jan. 25 of this year. It sounds like your build is a bit older than that.

If it will not be too much trouble for you, I would suggest getting the latest 2.6 installer and upgrading your system to that. Aside from that, the only sensible workaround I can think of is to have the form close after every submit.

Re: Problems with multiple saves within an existing DBXL document

Hilary Stoupa — Mon, 23 Jul 2012 15:54:36 GMT

DC-jeff:
I've tested with and without SharePoint mapping depending if I'm using filler or forms service. Problem occurs when editing existing forms where a user saves multiple times.

So, in browser, you don't have a SharePoint mapping, but the failure still occurs - and are their errors in the Qdabra Event Log when the form fails in the browser?

What I'm trying to do is find the most straightforward way I can reproduce this, as it did not reproduce for me with a filler form without a SharePoint mapping.

Re: Problems with multiple saves within an existing DBXL document

DC-jeff — Mon, 23 Jul 2012 15:46:43 GMT

Quick summmary:

InfoPath 2010. Have tested in both filler & rendered as web form

Button 1 - submit directly to DBXL via data connection 1. I've tested with and without SharePoint mapping depending if I'm using filler or forms service. Problem occurs when editing existing forms where a user saves multiple times. IE - open form, update any field, save (but do not close form), update any field, save again. Filler and browser both throw errors posted earlier in the thread.

Button 2 - sutmit directly to SP forms library via data connection 2. DBXL not involved. Able to perform the update -> save -> update -> save test above without issue.

Yes to your question "Failed submits are only occurring if the form is open, submitted, left open and resubmitted? "

thanks

Jeff

Re: Problems with multiple saves within an existing DBXL document

Hilary Stoupa — Mon, 23 Jul 2012 15:05:12 GMT

Okay - so just so I can be sure I understand your precise setup, so I can try to reproduce, your form has a SharePoint mapping, and you are having the issue of failed submits in both filler and browser? Failed submits are only occurring if the form is open, submitted, left open and resubmitted? Does this describe the base issue correctly?

Re: Problems with multiple saves within an existing DBXL document

DC-jeff — Mon, 23 Jul 2012 14:27:47 GMT

Hillary -

I also modified the form to have 2 submit buttons. The first is the existing one that submits to the DBXLSubmitDocument method. The second submits straight to the SharePoint forms library. I only get the errors in the previous thread when submitting to DBXL. I can do multiple saves without issue using the submit to SharePoint button. Any ideas on further testing?

Thanks

Jeff

Re: Problems with multiple saves within an existing DBXL document

DC-jeff — Mon, 23 Jul 2012 13:49:58 GMT

Hillary -

I tried both of your suggestions. In filler, I'm able to save a new form. I open the new form, update, & save and it works fine. Without closing, I update again and save get a "some rules not applied error". Detail below from the event viewer: InfoPath cannot submit the form.
An error occurred while the form was being submitted.
The SOAP response indicates that an error occurred on the server:

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Exception Code: I0016
Exception Message: Update failed. Document updated by another user (OURDOMAIN\user.name)

Also updated the submit button to always postback and tested in the browser. I open the new form, update, & save and it works fine. Without closing, I update again and save get a "an error has occured while connecting to a web service". Detail below: (I XXX'd out some detail for security reasons)

- System

  - Provider
     [ Name] Microsoft-SharePoint Products-InfoPath Forms Services
     [ Guid] {A3499A35-DB34-421A-94FC-4D76522BEAB3}

EventID 5567

Version 14

Level 3

Task 5

Opcode 0

Keywords 0x2000000000000000

  - TimeCreated
     [ SystemTime] 2012-07-23T13:31:15.488568000Z

EventRecordID 5870

  - Correlation
     [ ActivityID] {DE6F40AB-06A3-4A6E-A00E-D01E4941001A}

  - Execution
     [ ProcessID] 7864
     [ ThreadID] 3004

Channel Microsoft-SharePoint Products-Shared/Operational

Computer XXXXXXXXXX.XXX.XXX

  - Security
     [ UserID] S-1-5-21-266690176-277487647-1704157037-80181

- EventData

string0 OURDOMAIN\user.name

string1 test form

string2

string3 http://XXXXXXXXXXXXX/_layouts/FormServer.aspx?XmlLocation=/sites/era/RepeatingSectionTest/1682.xml&ClientInstalled=true&Source=http://XXXXXXXX/RepeatingSectionTest/Forms/AllItems.aspx&DefaultItemOpen=1#

string4 urn:schemas-microsoft-com:office:infopath:RepeatingSectionTest-http-ocpo-sp-dhs-gov-sites-erav20120723130709a8502765cea14df8808401eb1a02ec94:-myXSD-2012-07-20T16-22-31

string5 DataAdapterException

string6 The remote server returned an error: (500) Internal Server Error. System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Exception Code: I0016 Exception Message: Update failed. Document updated by another user (OURDOMAIN\user.name) at Qdabra.Dbxl.DbxlDocumentServiceEx.CheckAndThrowException(StatusInfo info) at Qdabra.Dbxl.DbxlDocumentServiceEx.Qdabra.Dbxl.Services.IDbxlDocumentServiceEx.SubmitDocument(String docTypeName, String xml, String name, String author, String description, Int32& docId, String& refId) --- End of inner exception stack trace --- The remote server returned an error: (500) Internal Server Error.

Re: Problems with multiple saves within an existing DBXL document

DC-jeff — Fri, 20 Jul 2012 22:00:19 GMT

I'll try in filler. Good idea on the post back settings. I'm betting that's it. I'll post results once I test. thanks Jeff

Re: Problems with multiple saves within an existing DBXL document

Hilary Stoupa — Fri, 20 Jul 2012 21:52:03 GMT

Hmmm. I hadn't realized till your last 2 updates that you were talking about a browser form. Do you have the same results in Filler?

Have you tried changing the postback settings on your submit button? Under the button properties, under Browser, set postback to always?

Re: Problems with multiple saves within an existing DBXL document

DC-jeff — Fri, 20 Jul 2012 19:47:25 GMT

Also, the additional saves work fine if the form is refreshed in the browser.

Re: Problems with multiple saves within an existing DBXL document

DC-jeff — Fri, 20 Jul 2012 19:44:33 GMT

No worries about the spam - happy to have the assistance.

DBXL version 2.6.2011.1211

Nothing in the event viewer.

Also, noticed that the problem isn't specific to repeating tables/sections. I the same problem when updating the "name" field in the form I sent you. Open form, change name, save (button), change name again and save (button) & exit. Only the data from the first save is captured and version never increments.

I'm not doing any type of refresh to the browser based form between saves.

Re: Problems with multiple saves within an existing DBXL document

Hilary Stoupa — Fri, 20 Jul 2012 19:26:49 GMT

Now I'm being nit-picky and spamming you - such fun!

I tried this exact form in a 2.6 install in our environment, and after each submit (no matter which repeating section I filled out) my changes were saved - I could refresh the documents list in the Documents tab in DAT and see the version incrementing - when I closed and re-opened after taking the steps where for you "Changes after the 1st save are never saved" the changes were saved for me - what version of 2.6 do you have? If you look at the bottom of DAT, you'll see the DBXL Version.....

Re: Problems with multiple saves within an existing DBXL document

Hilary Stoupa — Fri, 20 Jul 2012 19:23:36 GMT

Also, sorry, not to sound nit-picky - but are you refreshing your view of the documents tab between saves?

Re: Problems with multiple saves within an existing DBXL document

Hilary Stoupa — Fri, 20 Jul 2012 19:10:11 GMT

Are there any errors in the Qdabra Event Log with your additional submits?

Re: Problems with multiple saves within an existing DBXL document

DC-jeff — Fri, 20 Jul 2012 17:12:25 GMT

Hillary -

I created a new test form (attached to thread) and am able to consistently reproduce. Basic schema with a repeating section and a button bound to the DBXLDocumentSubmit method.

Here's what I'm doing in the test form:

Create a new form and add data for a 3 or 4 repeating sections. Save & Close. I verified in DBXL that the document was submitted and I see it is version 1

Open the existing form and update repeating section 1. Save & Close. I verified in DBXL that the document was updated and it is now version 2

Open the existing form and update repeating section 1. Save. The document is saved to DBXL and the version is 3. Without closing, update repeating section 2. Save. On this save and any after, the DBXL version is never incremented. Changes after the 1st save are never saved.

We recently upgraded to 2.6 and I don't recall having this issue in 2.5.

thanks

Jeff