I have the following problem: I have a application that, from time to time, opens a file, writes some date and closes it again. I get no errors when opening (with CreateFile) or closing the file (CloseHandle) - everything seems to be OK. My process is the only active user of this file. So far so good.
However, if this file is located on a network shared folder, I get the error ERROR_SHARING_VIOLATION. This error does not recover, even after hours of retrying. On the client PC, no file handle is open (when searching with process explorer). When looking on the server, the client PC still seems to have a handle to the file.
The file gets accessible again, when the network connection is interrupted and reestablished. My client here is Windows XP with the server being Windows Server 2003.
Is this a general problem with SMB? What can I do to get access to my file again?
Any help is warmly appreciated.
Frank