G
Guest
Hi there,
Sorry for the cryptic subject header. But that about summarizes my problem
Environment - Windows 2000 Server. Used as WebServer. Running a Document
management system. SQL Server 2000, Index Server being used. Documents are
primarily Compound documents. Have a custom Index Filter. The documents on
the server are opened both by the Index Server Filter (for read) and by an
application DLL running in the web context that opens the document both for
reads and for writes. The application DLL primarily reads and writes custom
and document properties to the file.
The Problem - Every once in a while, some file gets locked out - the Error
corresponds to A lock violation has occurred. (0x80030021). Using Filemon,
the error is what is in the subject header. The problem is that it is not
consistent.
I have seen a sorta related bug report for XP SP2 and a fix, but it is not
the same thing
(http://support.microsoft.com/default.aspx?scid=kb;en-us;830903). It shows
the same Locking problem though...
One pattern that I have observed is that the file might have been opened by
another process (cidaemon.exe) or the same one(inetinfo.exe) a few minutes
prior to this lockup. When things are working fine, the filemon shows the
following sequence of activity
IRP_MJ_CREATE SUCCESS Options: Open Access: All
FASTIO_QUERY_STANDARD_INFO SUCCESS Length: 5344256
FASTIO_QUERY_STANDARD_INFO SUCCESS Length: 5344256
FASTIO_QUERY_STANDARD_INFO SUCCESS Length: 5344256
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483538 Length: 1
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483539 Length: 20
FASTIO_UNLOCK SUCCESS Offset: 2147483539 Length: 20
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483559 Length: 20
FASTIO_UNLOCK SUCCESS Offset: 2147483559 Length: 20
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483579 Length: 20
FASTIO_UNLOCK SUCCESS Offset: 2147483579 Length: 20
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483599 Length: 20
FASTIO_UNLOCK SUCCESS Offset: 2147483599 Length: 20
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483539 Length: 1
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483559 Length: 1
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483579 Length: 1
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483599 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483538 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483539 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483559 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483579 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483599 Length: 1
IRP_MJ_SET_INFORMATION SUCCESS Length: 5344256
IRP_MJ_SET_INFORMATION SUCCESS Length: 5344256
IRP_MJ_CLEANUP SUCCESS
IRP_MJ_CLOSE SUCCESS
But when the Not Granted situation happens, the FASTIO_UNLOCK for the Offset
2147483539 had not occured (even though the file was closed).
The files are opened using StgOpenStorage....
Any help is appreciated! This problem is so unpredictable that I am at a
loss... If you would like I can post the filemon log.
Thanks!
Win2KOed
Sorry for the cryptic subject header. But that about summarizes my problem
Environment - Windows 2000 Server. Used as WebServer. Running a Document
management system. SQL Server 2000, Index Server being used. Documents are
primarily Compound documents. Have a custom Index Filter. The documents on
the server are opened both by the Index Server Filter (for read) and by an
application DLL running in the web context that opens the document both for
reads and for writes. The application DLL primarily reads and writes custom
and document properties to the file.
The Problem - Every once in a while, some file gets locked out - the Error
corresponds to A lock violation has occurred. (0x80030021). Using Filemon,
the error is what is in the subject header. The problem is that it is not
consistent.
I have seen a sorta related bug report for XP SP2 and a fix, but it is not
the same thing
(http://support.microsoft.com/default.aspx?scid=kb;en-us;830903). It shows
the same Locking problem though...
One pattern that I have observed is that the file might have been opened by
another process (cidaemon.exe) or the same one(inetinfo.exe) a few minutes
prior to this lockup. When things are working fine, the filemon shows the
following sequence of activity
IRP_MJ_CREATE SUCCESS Options: Open Access: All
FASTIO_QUERY_STANDARD_INFO SUCCESS Length: 5344256
FASTIO_QUERY_STANDARD_INFO SUCCESS Length: 5344256
FASTIO_QUERY_STANDARD_INFO SUCCESS Length: 5344256
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483538 Length: 1
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483539 Length: 20
FASTIO_UNLOCK SUCCESS Offset: 2147483539 Length: 20
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483559 Length: 20
FASTIO_UNLOCK SUCCESS Offset: 2147483559 Length: 20
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483579 Length: 20
FASTIO_UNLOCK SUCCESS Offset: 2147483579 Length: 20
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483599 Length: 20
FASTIO_UNLOCK SUCCESS Offset: 2147483599 Length: 20
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483539 Length: 1
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483559 Length: 1
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483579 Length: 1
FASTIO_LOCK SUCCESS Excl: Yes Offset: 2147483599 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483538 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483539 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483559 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483579 Length: 1
FASTIO_UNLOCK SUCCESS Offset: 2147483599 Length: 1
IRP_MJ_SET_INFORMATION SUCCESS Length: 5344256
IRP_MJ_SET_INFORMATION SUCCESS Length: 5344256
IRP_MJ_CLEANUP SUCCESS
IRP_MJ_CLOSE SUCCESS
But when the Not Granted situation happens, the FASTIO_UNLOCK for the Offset
2147483539 had not occured (even though the file was closed).
The files are opened using StgOpenStorage....
Any help is appreciated! This problem is so unpredictable that I am at a
loss... If you would like I can post the filemon log.
Thanks!
Win2KOed