search

warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

Unable to load packet filtering device: CreateFile, 2, "The system cannot find the file specified" #80

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Just installed latest Interim Release r131
2. Installed it
3. Still get same error before at startup of the program.

What is the expected output? What do you see instead?

I expect Peerblock to start running... but instead I get an error message.

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?

Windows XP 32-bit SP3

Here is the error I get: [Error]

Peerblock is unable to load the packet filtering device.
This could happen if peerblock crashed (Nope) and didn't have a chance to
unload the driver (nope), or the pbfilter.sys can't be found (maybe).

Class Win32_Error
Create file.
2
The system cannot find the file specified. [Error]

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

Attached Screen-Shot of the error.

Hope you get this problem fixed =)

Original issue reported on code.google.com by Thefirst...@gmail.com on 2 Sep 2009 at 1:18

Attachments:

GoogleCodeExporter commented 9 years ago 
Here is the log file I forgot to attach.
Won't do much good though. Same thing.

Original comment by Thefirst...@gmail.com on 2 Sep 2009 at 1:21

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks for the problem report!  Could you also attach peerblock.log and 
peerblock.dmp
(if one was created) please?  That should have some more info in it, hopefully
helping us pinpoint what file it was looking for...

Original comment by peerbloc...@gmail.com on 2 Sep 2009 at 1:22

GoogleCodeExporter commented 9 years ago 
Thank you for the fast response.

I did attach the log, if you notice above your post.

Mark contacted me with a special interim release, I installed it, and sent him 
the log.

But here it is anyways so you have it on here just in case.

Thank you =)

Original comment by Thefirst...@gmail.com on 2 Sep 2009 at 8:30

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi...I am having the exact same error. It happens right after peerblock is 
closed and
then started again. The only way to get it running is a reboot.

I am using PeerBlock-Setup_v1.0.0.r181 as of today and had the same problem 
using
PeerBlock-Setup_v0.9.2.r86. I am using XP Pro SP3 (32bit)

Attached is the screenshot, and peerblock.log.

Original comment by scottmsa...@gmail.com on 28 Sep 2009 at 11:18

Attachments:

GoogleCodeExporter commented 9 years ago 
PeerBlock seems to work fine only when "minimize to tray on close" is checked. 
If
this is unchecked, and PeerBlock is closed...and then started...it crashes with 
the
error at the the start of this thread.

Original comment by scottmsa...@gmail.com on 29 Sep 2009 at 3:08

GoogleCodeExporter commented 9 years ago 
Very strange.  So far the only reports I've seen on this one (the two of you 
here,
and one just now reported on our forums) were all running XP.  Thanks for the
additional repro notes, I'll see if I can reproduce the problem on my 
daughter's XP
machine.

Original comment by peerbloc...@gmail.com on 29 Sep 2009 at 3:54

GoogleCodeExporter commented 9 years ago 
Updating summary description to more-specifically identify the bug.

Original comment by peerbloc...@gmail.com on 29 Sep 2009 at 3:55

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 30 Sep 2009 at 4:20

GoogleCodeExporter commented 9 years ago 
(I am signed as JRF in the Forums , and am very reluctantly allowing all these
cookies and java-scripts , to be able to report here , as asked by MarkSide)

What steps will reproduce the problem?
1. install r181 and start PB , or exit and then restart PB .

What is the expected output? What do you see instead?
1. expected : the normal PB run .
2. what I see : the same error popup reported above : Class Win32_Error - 
Create file - 2

What version of PeerBlock are you using? What OS? 32- or 64-bit?
1. r181 , problem has been verified since r086 .
2. Windows XP Pro SP2 32-bit

Please provide any additional information below.  Make sure to attach the log 
and/or
any screenshots that would help explain your problem.
1. problem is very similar to those reported above , the error popup is the 
same .
2. PB always crashes when *not started with Windows* (independently if launched 
from
the Installer , or from a shortcut , or directly run in the Program Directory).
3. in my case PB crashes even if PB option "Minimize to tray on close" is set 
(as
commented above).
4. please observe that the popup just suggests the error is related to 
pbfilter.sys .
5. in my case the error seems to happen because PB is unable to start 
ipFltDrv.sys
*as Service* .
6. the module C:\Windows\System32\ipFltDrv.sys is correctly located , was last
modified in 2001 , and it is set to run on Autorun .
7. at the moment of the PB crash , ipFltDrv.sys was not active .
8. the peerblock.log bellow shows :
-- when PB crashes after being installed , and
-- a subsequent PB successful startup during PC boot .
9. the ipFltDrv.txt bellow shows just the lines related to that module when PB
crashes , and on PC boot . 
10.the file peerblock.dmp is not generated .

Original comment by JRF...@gmail.com on 30 Sep 2009 at 12:34

Attachments:

GoogleCodeExporter commented 9 years ago 
Bumping up the priority on this one, due to the number of people having reported
running into it nowadays.

As far as the "starting the driver as a service" stuff goes, this is standard
operating procedure - from the OS's perspective, drivers act as services as far 
as
starting/stopping them.  (At least they do for most of the drivers I've 
encountered
in the past...)

What is happening in the failed case, is that first off when we check to see 
whether
or not the Microsoft IpFilterDriver (ipfltdrv.sys) is running, it's reporting 
its
status as "stop pending" meaning it's in the process of stopping.  In the 
working
case, the driver is reporting its status as "started".  We then try to start
ipfltdrv.sys, and as part of that process attempt to get a handle to it; we do 
NOT
attempt to get a handle to it if it's already started.  Attempting to acquire 
this
handle is what's causing the "file not found" error, which is causing us to 
throw an
exception and crash.

I think I may have fixed the issue, though it's tough to say for sure since I 
can't
reproduce it.  Please try the attached test-version of PeerBlock and let me 
know if
it works.

Original comment by peerbloc...@gmail.com on 1 Oct 2009 at 4:17

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks for your explanations and the 183-test release .
These are the actions and results :

1- PC was started (from hibernation) , I made an update (OK) on PB.181 and exit 
it .
2- Installed PB.183 : at the last install page accepted to run it .
3- PB.183 started OK (NO CRASH) , the initial update started requesting 
connection to
verify PB-version only (as all other updates were "not-needed") , but the 
Internet
was not available :
4- After the Close-update-window timeout the PB.183 window opened .
5- I reconnect the Internet , and tested GE and my ISP , none detected by PB 
(so PB
SCAN WAS NOT WORKING), I exit PB.183 .

6- Restarted manually PB.183(NO CRASH): 
7- the initial update proposed a connection for a new PB , replied NO :
8- The PB.183 window opened , I tested GE and my ISP , none detected by PB (so 
PB
SCAN WAS NOT WORKING), I exit PB.183 , and RE-BOOT PC .

9- On PC reboot , PB.183 started OK but NO ICON ON SYSTRAY (had to start other
instance to have PB window open) , tested OK (GE and my ISP), so PB SCAN IS 
WORKING
after PC reboot .

Summary for PB.183 tests :
A- the crash on the PB manual restart seems to have been fixed .
B- on PB manual restart the PB scan does not work .
C- on PC boot the PB scan does work OK .
D- on PC boot the PB icon does not appear on systray (even starting 'other' PB).

OBS1 : the log I am going to attach shows the actual situation .
OBS2 : I will keep PB.183 installed , waiting for your kind instructions .

Original comment by JRF...@gmail.com on 2 Oct 2009 at 10:34

Attachments:

GoogleCodeExporter commented 9 years ago 
Thank you for the detailed test report, I'll analyze the data and come up with 
some
next steps.  Since PeerBlock doesn't appear to be working even though it's not
crashing, you may want switch back to an Interim (or Public) Release instead - 
that
way you'll at least know from the beginning whether PeerBlock is in fact 
working for
you or not.

Original comment by peerbloc...@gmail.com on 3 Oct 2009 at 6:31

GoogleCodeExporter commented 9 years ago 
Assigning myself to this bug, as I've been actively pursuing it these past few 
days.

If you have some time to attempt a repro for me, please stop by our IRC channel,
#peerblock at irc.freenode.net (http://webchat.freenode.net/).  (If you're 
using that
web-client, put "#peerblock" into the "Channel" field...)  I have a test driver 
that
should hopefully give out a bit more debug information, though you'll need to
download DebugView 
(http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx) in
order to capture it for me.  Please visit our IRC channel since I will likely 
need to
rebuild the driver based on what you tell me, adding additional debug info to
(hopefully) help narrow-down the failure location.

Original comment by peerbloc...@gmail.com on 9 Oct 2009 at 5:42

GoogleCodeExporter commented 9 years ago 
Looks like we got this bug mostly fixed last night.  It turns out that a Visual
Studio patch had required a newer version of one of the core system DLLs, which 
isn't
installed on some peoples' XP machines.  To workaround this I found some code 
to help
us lock the program-requirement down to a certain rev of that system DLL, which
hopefully will work across the board for XP users - I'll only plan on setting 
this
for XP builds though.

Need to clean up that fix a bit and get it checked-in, but I'm fairly confident 
that
we've ironed this one out.  If you're currently experiencing this problem, 
please try
running with the test-version of peerblock.exe attached.  (Just copy it over 
top of
your currently installed version...)

There are however still a few issues that need to be resolved on the 
test-machine
we'd seen the problem on.  The Microsoft IpFilterDriver driver/service 
sometimes gets
stuck in a "Stop Pending" state (Issue #159), and sometimes PeerBlock start up 
in a
state such that it doesn't actually do anything until you disable & re-enable
blocking (Issue #160).  These issues have been around for awhile now, just 
looks like
no bugs were added to track them.  Working on resolving them now.

Original comment by peerbloc...@gmail.com on 12 Oct 2009 at 1:22

GoogleCodeExporter commented 9 years ago 
To peerblockproject

1- Sorry I could not help on your post from Oct09 , some holidays here and 
visit from
abroad (I am also a bit 'allergic' to any chats , except Skype when 
over-monitored) .
2- I did however installed DebugView 4.76 , and had a look on its options , 
seems if
I just turn-on all scan-types it would catch any driver-tracker-output when/if 
you
have it ready .
3- I have also Inspector IIXII 3.2 
(http://www.opera.com/support/search/view/432/) it
is very simple and has helped on some crashes and freezes , you say when/if you 
want it .
4- I may have misunderstood , but you planned to attach a zip test-pack for me ?
I have now r.187 , no boot-startup problems , just the restart crash .
5- As a sub-product of these tests I have earlier prepared a material with some
characteristics of (Issue 159) , I will attach there in about 30 min max , if 
it may
be of any help .

Original comment by JRF...@gmail.com on 12 Oct 2009 at 6:02

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r194.

Original comment by peerbloc...@gmail.com on 13 Oct 2009 at 3:50

GoogleCodeExporter commented 9 years ago 
Issue 315 has been merged into this issue.

Original comment by peerbloc...@gmail.com on 17 May 2010 at 4:33