FwpmEngineOpen error 1753, "no more endpoints available"

[GoogleCodeExporter]

Recently saw a thread on the PG2 forums regarding this error from base PG2.
 Looks as though we depend upon the "Base Filtering Engine" service, and
possibly some others.

Once we transition over to a Service (instead of just a regular app), we
should make sure to set the proper service dependencies.  In the meantime
we can check that these services are running, and start them if not.  At
the very least we should trap this error and let the user know what the
problem is in a more user-friendly manner.

More info:

- PG2 Forum Thread discussing "Base Filtering Engine" service (along with
some others): 
http://forums.phoenixlabs.org/showthread.php?t=16113&highlight=endpoints

- Another thread discussing this problem: 
http://forums.phoenixlabs.org/showthread.php?t=16282

Original issue reported on code.google.com by peerbloc...@gmail.com on 27 Jul 2009 at 3:00

[GoogleCodeExporter]

Original comment by peerbloc...@gmail.com on 1 Aug 2009 at 4:37

• Changed state: Started

[GoogleCodeExporter]

To provide at least some relief from this issue, commit r89 adds to trunk a more
user-friendly error message that will popup if your machine his this condition. 
 This
message will explain this problem to the user, and direct them to go to
http://www.peerblock.com/required-services if they want more information.

With this in place, I have no problem letting a "real" fix for this issue - 
checking
the services ourself, and offering to fix them if necessary - slip to the 
post-1.0
timeframe.

Original comment by peerbloc...@gmail.com on 7 Aug 2009 at 2:15

• Changed state: Accepted
• Added labels: Milestone-After1.0, Priority-Low
• Removed labels: Milestone-Release1.0, Priority-Medium

[GoogleCodeExporter]

Original comment by peerbloc...@gmail.com on 7 Aug 2009 at 2:39

[GoogleCodeExporter]

Removing 'After1.0' release-targetting.

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

• Removed labels: Milestone-After1.0