Posted by jim guerber on April 29, 2015 at 09:35:14:
In Reply to: Re: XAP question...> posted by Tom Fulton on April 28, 2015 at 08:55:39:
You are not the only one that has reported this or similar problem. This has happened very rarely in the past. We never could reproduce it or even understand how it happened.
What it looks like is that Comet thinks the file has been closed, but Windows thinks the handle is still active and the file is still open. (At least that's my best guess).
Here are some questions that may lead us to an understanding and possible fix:
1. Is this Comet32?
2. What version of windows is this?
3. If you execute a snapshot of the file server, do we list the file?
If you are on Windows 2012 server, there is an enhanced task manager, that can lead you to "Resource Monitor". Resource monitor can list all of the handles that windows thinks a process has open. Check that against the snapshot.
As you can tell from the above, I think it is the file server that has the file open although it does not know it. If that is the case, the only way I know to close the file is to restart comet services.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.