InfoPath Dev

I have a InfoPath template that submits it's forms to a SharePoint server.  If the user improperly closes InfoPath the write lock for the form he has open is not removed on the server.  When the form is re-opened the user gets an error stating that someone has the form open.  This is all standard stuff and the lock usually clears itself after 10 minutes.

But sometimes the error message never clears on the original users computer.  The write lock on the server clears normally, anyone else can access the file just fine.  But the original computer never allows write access to the file again.  We can wait days and it still doesn't clear.  Looks like that computer keeps the write lock in it's cache somewhere and never bothers to check the server again.  Is there any method I can use to clear this cache or force the computer out of this state?

 Thanks,

-Dan

Dan,

Try to log off of the original user's computer.  If that does not work, try rebooting the original user's computer. 

Where I work, we have experienced this problem; and the reboot seems to work every time. 

I have not figured out how the lock works, but I think it is related to the session state.  So, I have been researching these links:
Configure session state for InfoPath Forms Services (Office SharePoint Server)
   (http://technet.microsoft.com/en-us/library/cc262299.aspx)
Configure the primary Shared Services Provider
   (http://technet.microsoft.com/en-us/library/cc262649.aspx)
Manage session state (Office SharePoint Server)
   (http://technet.microsoft.com/en-us/library/cc263527.aspx)

We are not using Form Services, however.  Our users are using the InfoPath client to edit the form, but since the InfoPath client seems to use Internet Explorer, I am suspicious about whether or not the Forms Services State Session has an effect on how the client behaves. 

We have also had cases where, when the user tries to save a form, they get this lock error.  This may be a case where user1 opens the form, edits for a while, then user2 comes along after the session timeout is exceeded and opens the same xml file that user1 has, then user1 tries to save the form.  When user1 does this, they get an error saying that they cannot save the form.  I have not seen what the actual error message is, so do not rely on my description of the error.

My objective is to understand how the InfoPath form is locked (xml file is locked in SharePoint) and determine where I can control the timeout.  It appears that the timeout might be set to 60, 10, or 3 minutes.  My Colleague have seen these values (i.e., 60, 10, & 3) being quoted on the Internet. This may be configurable at SharePoint Central Administration-->Application Management-->Configure Session State.  Note: we do not have the document library (where the forms are stored) setup to require document checkouts/checkin.  This is by design since most new SharePoint users do not find the Checkout/Checkin process intuitive.

Still trying to figure this one out ...

Rob