FilterSendMessage return 0x80070005

NTFSD
1

Hi all,

our user application (32bit) is communicating with our filter (minifilter, 64bit) via a communication port (on a W2k3 64bit system), the port is initialized at the beginning and is used then the whole time.
But time by time (maybe once/twice per day) we get the return code 0x80070005 from FilterSendMessage. We send the packages synchronous to our filter and always the same size. The next packages we can send then without a problem to the filter (via the same port).
We did not encounter this problem when we run both filter and our application on a 32bit system.

a) Our ntstatus.h does not list this return code, what does it mean?
b) Any idea how to prevent this, or maybe also to recover it?

Norbert

2

> a) Our ntstatus.h does not list this return code, what does it mean?
For future reference [6001 may be replaced by 6000]:

C:\WinDDK\6001\tools\other\i386>winerror.exe 0x80070005
-2147024891 E_ACCESSDENIED <–> No NTSTATUS matched

-------------- Original message --------------
From: Joseph Vossen

E_ACCESSDENIED

xxxxx@lists.osr.com wrote on 10/10/2007 09:29:16 AM:

> Hi all,
>
> our user application (32bit) is communicating with our filter
> (minifilter, 64bit) via a communication port (on a W2k3 64bit
> system), the port is initialized at the beginning and is used then
> the whole time.
> But time by time (maybe once/twice per day) we get the return code
> 0x80070005 from FilterSendMessage. We send the packages synchronous
> to our filter and always the same size. The next packages we can
> send then without a problem to the filter (via the same port).
> We did not encounter this problem when we run both filter and our
> application on a 32bit system.
>
> a) Our ntstatus.h does not list this return code, what does it mean?
> b) Any idea how to prevent this, or maybe also to recover it?
>
> Norbert
—
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

thanks so far (sorry but this was really easy, don’t know why I didn’t found it :frowning: ),

but what could be the reason that a application which was allowed to to send messages currently can’t send it, or more, just for this one call, because with the next call it works again?
I assume that wrong handles would return something like E_HANDLE…

I will handle this error code now and will retry the same function call (2-3 times),
let’s see how it will behave.
I assume that getting this return code, nothing was send to the filter, otherwise it would be hard to synchronize what the filter got so far and what not.

Norbert

4

Alex,

thanks for the hint to this winerror tool, seems to be very usefull

Norbert

5

> thanks for the hint to this winerror tool, seems to be very usefull
You can get one more treasure, Err.exe from

http://www.microsoft.com/downloads/details.aspx?familyid=be596899-7bb8-4208-b7fc-09e02a13696c&displaylang=en

Ignore the title “Microsoft Exchange Server Error Code Look-up”,
actually it’s good enough for anything windows, for example:

C:!Setups\Err\Err>Err.exe 0xc0000005

for hex 0xc0000005 / decimal -1073741819 :

STATUS_ACCESS_VIOLATION ntstatus.h

The instruction at “0x%08lx” referenced memory at

“0x%08lx”. The memory could not be “%s”.

USBD_STATUS_DEV_NOT_RESPONDING usb.h

2 matches found for “0xc0000005”

C:!Setups\Err\Err>

Cool…

-------------- Original message --------------
From: xxxxx@graudatastorage.de

Alex,

thanks for the hint to this winerror tool, seems to be very usefull

Norbert

NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com