Qdabra Database Accelerator

Re: problem overwriting sharepoint document?

mattmoose — Fri, 18 Sep 2009 08:34:06 GMT

Right, well that error might not be relevant I had just noticed it tends to appear round about the same time I see this issue.

My form is querying the Qdabra AD info webservice on load but thats all, its not doing anything sharepoint related.

Re: problem overwriting sharepoint document?

Jim Cantwell — Thu, 17 Sep 2009 16:23:11 GMT

That error is likely more associated with a save operation. Opening a document should not be doing a SharePoint operation, unless the dbxl submit data connection is set for execute on load.

Re: problem overwriting sharepoint document?

mattmoose — Thu, 17 Sep 2009 15:29:02 GMT

It is infopath which gives the in use error when opening the form.

There is a qdabra error in the eventlog which seems to appear after attempting to open the file when locked, which you should be able to see in the eventlog i sent to you...

"System.Net.WebException: The remote server returned an error: (409) Conflict."

Re: problem overwriting sharepoint document?

mattmoose — Thu, 17 Sep 2009 15:25:58 GMT

heres' the result of the query while the file is in the 'in use' state...

DocID LockedBy LockExpires
131 NULL

Re: problem overwriting sharepoint document?

Jim Cantwell — Thu, 17 Sep 2009 15:13:02 GMT

Is DBXL indicating the file is in use or is it SharePoint? DBXL maintains its own locking mechanism separate from SharePoint. The InfoPath client will lock the form in DBXL and update the lock periodically while the form is open. There is a potential that the form is not getting unlocked by the InfoPath client.

Run the following query on the QdabraDBXL database to see the status of the docid in question:

USE QdabraDBXL

SELECT DocID, LockedBy, LockExpires FROM Document WHERE DocID = youdocidhere

Re: problem overwriting sharepoint document?

mattmoose — Tue, 15 Sep 2009 10:48:21 GMT

I've done an experiment to see if the same issue occurs when simply just saving files to the form libary, and it seems it does not. This problem only seems to occur when submitting via the DBXL webservice :-( does DBXL keep the file open for a while after it is submitted?

Are you able to reproduce this issue at all?

Re: problem overwriting sharepoint document?

mattmoose — Mon, 14 Sep 2009 09:20:27 GMT

ok some more information...

Oddly, this only seems to occur after the form has been submitted twice...

So i can open a new form, submit it, open and edit it and submit it again, but then the next time i open it i am presented with the file in use error. Hope this helps!

Matt

Re: problem overwriting sharepoint document?

mattmoose — Mon, 14 Sep 2009 08:46:18 GMT

Any advance on why i might be seeing this issue with the file being in use? also any idea when a hotfix might be available to cure the initial issue?

Re: problem overwriting sharepoint document?

mattmoose — Thu, 10 Sep 2009 14:58:38 GMT

also, there are no sharepoint errors.

Re: problem overwriting sharepoint document?

mattmoose — Thu, 10 Sep 2009 14:46:51 GMT

Hi Jim,Just emailed through the eventlog to support.I’m not trying to do anything funky, just open and edit the document from within the sharepoint form library, not from a link in DBXL. Everything works ok providing I wait around 15 to 20 minutes after editing the file, but if I try during this time it seems although the file is in use.

Re: problem overwriting sharepoint document?

Jim Cantwell — Thu, 10 Sep 2009 14:23:42 GMT

The checkout feature is normally left off, but it should work either way. Are there any SharePoint errors in the Application eventlog? When you open the file, are you opening from SharePoint or from a link to the file in DBXL?

Can you email the Qdabra eventlog to the Qdabra Support alias ?

Re: problem overwriting sharepoint document?

mattmoose — Thu, 10 Sep 2009 14:00:47 GMT

ok,

I think that making the users a member of the local admins of the machine has fixed the issue with overwriting the files, at least until a fix is released by qdabra (i dont like the idea of all the users being local admins of the server permanently)!

the only issue now is that after the file has been edited, you have to wait a considerable time (15 - 20 minutes) before the file can be edited again, i assume that dbxl has not properly closed the file or it is using it?

the exact error from infopath when trying to open the form in sharepoint is...

"the form cannot be filled out because you do not have adequate permission, another user has the form open, or the form is open in another program. Do you want to open a read only copy for the form?"

Re: problem overwriting sharepoint document?

mattmoose — Thu, 10 Sep 2009 10:52:50 GMT

might be worth noting that sometimes when i try to open the form to edit it, i get a message saying that the form is open by another user or another program...

I assume dbxl has this file open when this message appears? eventually after leaving it a considerable amount of time this mssage will go away, and i can then edit and resubmit the form.

Re: problem overwriting sharepoint document?

mattmoose — Thu, 10 Sep 2009 10:00:35 GMT

i presume by 'if the column is set' you mean visible in the library view? i've made it visible but this seems to be always blank. i then enabled the check out feature of the library assuming i'd miss read something and this needs to be enabled, but still made no difference this column is always blank. Should the check out feature be turned on in the library?

I am getting this error still... and also one new error!... see below..

Caught exception saving document to SharePoint collection https://www.domain.com/formlib. (DocType = 'doctype', DocId = 123) encountered a critical error and needs attention:

System.Net.WebException: The remote server returned an error: (409) Conflict.

at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)

at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)

at System.Net.WebClient.UploadData(String address, String method, Byte[] data)

at Qdabra.Dbxl.Domain.SharePointWebServices.Save(SharePointListItemMapping mapping, SharePointDocumentData doc)

at Qdabra.Dbxl.Domain.Document.SaveDocumentToSharePointLists(XmlDocument xmlDoc, XmlNamespaceManager nsMgr)

The stack trace was: at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)

at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)

at System.Net.WebClient.UploadData(String address, String method, Byte[] data)

at Qdabra.Dbxl.Domain.SharePointWebServices.Save(SharePointListItemMapping mapping, SharePointDocumentData doc)

at Qdabra.Dbxl.Domain.Document.SaveDocumentToSharePointLists(XmlDocument xmlDoc, XmlNamespaceManager nsMgr).

Event Type: Error
Event Source: Database Accelerator
Event Category: None
Event ID: 0
Date:  10/09/2009
Time:  10:27:32
User:  N/A
Computer: <servername>
Description:
Error updating list item metadata in SharePoint collection https://www.domain.com/formlib: 0x81020016 Item does not exist

The page you selected contains an item that does not exist. It may have been deleted by another user. (DocType = 'doctype', DocId = 123) encountered a critical error and needs attention.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Re: problem overwriting sharepoint document?

Jim Cantwell — Wed, 09 Sep 2009 17:15:30 GMT

reread your post. it is an existing document. If the Checked Out To column is set, that will help narrow down the problem.