InfoPath Dev

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.

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."

heres' the result of the query while the file is in the 'in use' state... DocID LockedBy LockExpires 131                     NULL

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?

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

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?

also, there are no sharepoint errors.

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.

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 ...

first link is dead? :-(