TT32Test64.exe reports CreateProcess(FWPCUtil) failed; rc=14001

View: New views
3 Messages — Rating Filter:   Alert me  

TT32Test64.exe reports CreateProcess(FWPCUtil) failed; rc=14001

by baumundberg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I am trying to get the virtual TCP/IP adapter running on a Windows Server 2008 64-bit system. Every WinPcap-installation from 4.0 to 4.1.1 seems to work fine as the net group packet filter is running after starting TT32Test64.exe.
This is the TT32Test64.exe output:

16:26:44.948 ** CFishPackApp::FishPackGetWinPCapInfo: CreateProcess(FWPCUtil) failed; rc=14001 (0x000036B1):
16:26:44.948 Begin TT32Test64.exe, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
16:26:44.948 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
16:26:44.948
16:26:44.948 Running on Windows 2000 (MP=4), version 6.0.6002 Service Pack 2
16:26:44.948
16:26:44.948 ERROR:  **************************************************************
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **                   ***  ERROR  ***                        **
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **   CTCI-W32 was unable to load the WinPCap 'packet.dll'   **
16:26:44.948 ERROR:  **   support module indicating that WinPCap is either not   **
16:26:44.948 ERROR:  **   installed at all or improperly installed. CTCI-W32     **
16:26:44.948 ERROR:  **   is unable to function without a proper installation    **
16:26:44.948 ERROR:  **   of WinPCap.                                            **
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **   Please either install WinPCap first before continuing  **
16:26:44.948 ERROR:  **   or uninstall and then reinstall it again if you have   **
16:26:44.948 ERROR:  **   reason to suspect it might not be properly installed.  **
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **************************************************************
16:26:44.948
16:26:44.948 Using FishPack64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
16:26:44.948 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
16:26:44.948
16:26:44.948 Using TunTap64.dll, version: "3.2.1.160" (3.2.1.160): "64-bit Release version" ...
16:26:44.948 Copyright (C) 2002-2007, Software Development Laboratories (aka 'Fish' (David B. Trout)).
16:26:44.948
16:26:44.948 ---------  The following relevant DosDevices are defined ---------
16:26:44.948
16:26:44.948 NPF_NdisWanBh
16:26:44.948 NPF_NdisWanIp
16:26:44.948 NPF_NdisWanIpv6
16:26:44.948 NPF_{1E7ADD49-8A46-4E54-9BEC-034938C6A5A8}
16:26:44.948 NPF_{26B3A979-9D29-46C7-A2BF-ED49D03898E1}
16:26:44.948 NPF_{57B78A29-B37D-4C4E-BB9F-7CA4341A3D5E}
16:26:44.948 NPF_{9C7E9359-5E4D-4116-A49D-51DA1DB18E4C}
16:26:44.948 NPF_{D3AB7F4F-E50D-4DC3-B1A1-50E968725272}
16:26:44.948 NPF_{D6D34145-B91A-41F3-81AE-F9C2103FAE90}
16:26:44.948 NPF_{E5977465-57F2-490E-988F-2CEFD5776D84}
16:26:44.948 {1E7ADD49-8A46-4E54-9BEC-034938C6A5A8}
16:26:44.948 {26B3A979-9D29-46C7-A2BF-ED49D03898E1}
16:26:44.948 {57B78A29-B37D-4C4E-BB9F-7CA4341A3D5E}
16:26:44.948 {9C7E9359-5E4D-4116-A49D-51DA1DB18E4C}
16:26:44.948 {D3AB7F4F-E50D-4DC3-B1A1-50E968725272}
16:26:44.948 {D6D34145-B91A-41F3-81AE-F9C2103FAE90}
16:26:44.948 {E5977465-57F2-490E-988F-2CEFD5776D84}
16:26:44.948
16:26:44.948 -------------------------  Network Information  -------------------------
16:26:44.948
16:26:44.948   Host Name . . . . . . . . . : MYCOMP
16:26:44.948   Node Type . . . . . . . . . : Hybrid
16:26:44.948   DNS Servers . . . . . . . . : 192.168.11.201
16:26:44.948                                 192.168.11.237
16:26:44.948   IP Routing Enabled. . . . . : no
16:26:44.948
16:26:44.948   Network Address          Netmask  Gateway Address        Interface  Metric
16:26:44.948           0.0.0.0          0.0.0.0     192.168.11.5   192.168.11.231     266
16:26:44.948         127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1     306
16:26:44.948         127.0.0.1  255.255.255.255        127.0.0.1        127.0.0.1     306
16:26:44.948   127.255.255.255  255.255.255.255        127.0.0.1        127.0.0.1     306
16:26:44.948      192.168.11.0    255.255.255.0   192.168.11.231   192.168.11.231     266
16:26:44.948    192.168.11.231  255.255.255.255   192.168.11.231   192.168.11.231     266
16:26:44.948    192.168.11.255  255.255.255.255   192.168.11.231   192.168.11.231     266
16:26:44.948         224.0.0.0        240.0.0.0        127.0.0.1        127.0.0.1     306
16:26:44.948         224.0.0.0        240.0.0.0   192.168.11.231   192.168.11.231     266
16:26:44.948   255.255.255.255  255.255.255.255        127.0.0.1        127.0.0.1     306
16:26:44.948   255.255.255.255  255.255.255.255   192.168.11.231   192.168.11.231     266
16:26:44.948
16:26:44.948   Default gateway:  192.168.11.5
16:26:44.948
16:26:44.948 --------------------------  Detected Adapters  --------------------------
16:26:44.948
16:26:44.948 ERROR:  **************************************************************
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **                   ***  ERROR  ***                        **
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **   CTCI-W32 could not find any usable FishPack adapters.  **
16:26:44.948 ERROR:  **   At least one usable networking adapter is required to  **
16:26:44.948 ERROR:  **   use CTCI-W32 for Hercules networking.                  **
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **   If you do not have a real physical networking adapter  **
16:26:44.948 ERROR:  **   to install on this system, you may still be able to    **
16:26:44.948 ERROR:  **   use CTCI-W32 by installing the 'Microsoft Loopback     **
16:26:44.948 ERROR:  **   Adapter' device.                                       **
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **   For information on how to install Microsoft's built-   **
16:26:44.948 ERROR:  **   in Loopback Adapter device please refer to KB article  **
16:26:44.948 ERROR:  **   839013 'How to install the Microsoft Loopback adapter  **
16:26:44.948 ERROR:  **   in Windows XP' http://support.microsoft.com/kb/839013  **
16:26:44.948 ERROR:  **                                                          **
16:26:44.948 ERROR:  **************************************************************
16:26:44.948


My CTC device statement is:
0E20.2  CTCI    192.168.11.198 192.168.11.231

The Hercules console shows:
Hercules Version 3.06
(c)Copyright 1999-2007 by Roger Bowler, Jan Jaeger, and others
Built on Jan 10 2009 at 01:56:22
Build information:
  Win32 (MSVC) build
  Modes: S/370 ESA/390 z/Arch
  Max CPU Engines: 8
  Using fthreads instead of pthreads
  Dynamic loading support
  Loadable module default base directory is .
  Using shared libraries
  HTTP Server support
  No SIGABEND handler
  Regular Expressions support
  Automatic Operator support
  Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8 fetch_dw store_dw
Running on MYCOMP Windows_NT-6.0 i686 MP=4
Crypto module loaded (c) Copyright Bernard van der Helm, 2003-2008
  Active: Message Security Assist
          Message Security Assist Extension 1
          Message Security Assist Extension 2
HHCCF065I Hercules: tid=00000A14, pid=4280, pgid=4280, priority=0
HHCTE001I Console connection thread started: tid=00000548, pid=4280
HHCDA020I C:/DASD/AUN21 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCTE003I Waiting for console connection on port 23
HHCDA020I C:/DASD/AUN22 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN23 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN24 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN25 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN26 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN27 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN28 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN29 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN30 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN31 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN32 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN33 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN34 cyls=3339 heads=15 tracks=50085 trklen=56832
HHCDA020I C:/DASD/AUN35 cyls=3339 heads=15 tracks=50085 trklen=56832
** tt32_loaddll: LoadLibraryEx("TunTap32.dll") failed; rc=126: The specified module could not be found.
** tt32_loaddll: LoadLibraryEx("TunTap32.dll") failed; rc=126: The specified module could not be found.
HHCTU002E Error opening TUN/TAP device: 00-00-5E-80-00-00: No error
HHCCF044E Initialization failed for device 0E21
HHCCF069I Run-options enabled for this run:
          NUMCPU:           2
          ASN-and-LX-reuse: ENabled
          DIAG8CMD:         DISabled

I also installed "Microsoft Visual C++ 2005 Redistributable (x64)" and "Microsoft Visual C++ 2005 ATL Update kb973923 - x64 8.0.50727.4053".

By the way, executing "TT32Test64.exe" generates the following event log entry:
"Activation context generation failed for "C:\Windows\System32\FWPCUtil.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis."

I copied all the DLLs (FishLib64.dll, FishPack64.dll, TunTap64.dll into Windows\System32 folder.

When executing the "FWPCUtil.exe" in the Windows\System32 folder the following message appears:
"The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail"
The application event log comes up with this:
"Activation context generation failed for "C:\Windows\System32\FWPCUtil.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis."

Please have a look at my information. Please tell me what do you think about these error messages? Do you have any idea what is missing or wrong? Thank you very much.


RE: TT32Test64.exe reports CreateProcess(FWPCUtil) failed; rc=14001

by fish-8 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

baumundberg wrote:

> Hi,
>
> I am trying to get the virtual TCP/IP adapter running
> on a Windows Server 2008 64-bit system. [...]

[...]

> This is the TT32Test64.exe output:
>
> 16:26:44.948 ** CFishPackApp::FishPackGetWinPCapInfo:
> CreateProcess(FWPCUtil) failed; rc=14001 (0x000036B1):

[...]

> The Hercules console shows:
> Hercules Version 3.06
> (c)Copyright 1999-2007 by Roger Bowler, Jan Jaeger, and others
> Built on Jan 10 2009 at 01:56:22
           ^^^^^^^^^^^
           ^^^^^^^^^^^
> Build information:
>   Win32 (MSVC) build
    ^^^^^^^^^^^^^^^^^^
    ^^^^^
[...]
> ** tt32_loaddll: LoadLibraryEx("TunTap32.dll") failed;
                                  ^^^^^^^^^^^^
                                  ^^^^^^^^^^^^
> rc=126: The specified module could not be found.
[...]

> I also installed "Microsoft Visual C++ 2005 Redistributable (x64)"
> and "Microsoft Visual C++ 2005 ATL Update kb973923 - x64 8.0.50727.4053".
[...]
> I copied all the DLLs (FishLib64.dll, FishPack64.dll, TunTap64.dll into
> Windows\System32 folder.

Please don't do that.

Instead, create a private 'bin' directory somewhere (or perhaps a private
'ctciw32' or 'softdevlabs' directory, etc) and place your files in there.
Then add that directory to your Windows search PATH environment variable.

That way you can easily remove that directory from your PATH whenever you
need to (which you WILL need to do once my new software is released).

Otherwise you will have to manually find all of the individual components
(FishLib64.dll, FishPack64.dll, TunTap64.dll, etc) in your Windows system32
directory and remove them from there.

Besides, the Windows system32 is a SYSTEM directory that should technically
only contain Microsoft components that come with the operating system. My
software doesn't qualify.

But that's NOT your problem.  :)



> When executing the "FWPCUtil.exe" in the Windows\System32 folder
> the following message appears:
>
>    "The application has failed to start because
>     its side-by-side configuration is incorrect.
>     Please see the application event log for more
>     detail"
>
> The application event log comes up with this:
>
>     "Activation context generation failed for
>     "C:\Windows\System32\FWPCUtil.exe". Dependent Assembly
>     Microsoft.VC80.MFC,processorArchitecture="x86",
>     [... blah blah blah...] could not be found. Please use
>     sxstrace.exe for detailed diagnosis."
>
> Please have a look at my information. Please tell me what do you
> think about these error messages? Do you have any idea what is missing
> or wrong? Thank you very much.


The official 3.06 release of Hercules you are running:

   "Built on Jan 10 2009"
   "Win32 (MSVC) build"

is only a 32-bit version.

You are trying to run a 32-bit version of Hercules on 64-bit Windows.

While this is entirely possible it is NOT recommended. Instead, we recommend
that you run a 64-bit version of Hercules instead.

64-bit versions of Hercules (which are NOT official releases per se (yet))
can be downloaded from our "daily" development snapshot web site at:

  http://www.ivansoftware.com/snapshots/snapshots/


But wait! There's more! :)

Even if you run one of the above 64-bit versions of Hercules, things STILL
aren't going to work right because you'll still be missing the needed
Microsoft redistributables.

You see, here's the thing: on 64-bit Windows you CAN (if you want) still run
32-bit software, but that 32-bit software is STILL going to need all of the
compnents it would normally need. Such as, say, the 32-bit version of
Microsoft's redistributable DLLs.

You installed the 64-bit version of Microsoft's redistributables:

  "Microsoft Visual C++ 2005 ATL Update kb973923 - x64 8.0.50727.4053"

but did you install the 32-bit x86 version as well? No. You did not.

THAT is why you're getting your errors: you're trying to run 32-bit software
without the needed 32-bit redistributables.

Download and install the 32-bit (x86) version of that same "Microsoft Visual
C++ 2005 ATL Update" redistributable.


NOW....


After installing the above mentioned 32-bit Microsoft redistributable you
SHOULD, as I said, be able to then run any 32-bit software. But the question
remains, why?

I recommend running the 64-bit version of Windows and the 64-bit version of
all of my software.

HOWEVER...

You need to be aware of one VERY IMPORTANT THING about the current version
of my CTCI-W32 Hercules networking package: it also requires the 32-bit
Microsoft redistributables too!

SO....

The rule is: on 64-bit Windows you should ALWAYS install BOTH the 64-bit
*AND* the 32-bit version of Microsoft's redistributables package too! You
need to always install BOTH of them. The 64-bit redistributables *AND* the
32-bit redistributables.

My "FWPCUtil" program -- which my CTCI-WIN package calls to communicate with
WinPCap -- is a 32-bit program not a 64-bit program (the technical reasons
for which I won't get into right now), and thus requires the 32-bit
Microsoft redistributables to be installed.

And since you didn't have the 32-bit Microsoft redistributables installed,
that's why it was failing.


  ------------------------------
  SUMMARY OF RECOMMENDED ACTIONS
  ------------------------------

1. Download and install the "x86" (32-bit) version of Microsoft's
redistributables:

  http://tinyurl.com/yepzp49


2. Download and install a 64-bit version of Hercules:

  http://www.ivansoftware.com/snapshots/snapshots/W64/


3. Try again. :)




These types of problem should hopefully go away as soon as we have a proper
Windows installer in place (which we unfortunately don't yet).

- --
"Fish" (David B. Trout) - fish@...
Fight Spam! Join CAUCE! <http://www.cauce.org/>
7 reasons why HTML email is a bad thing
http://www.georgedillon.com/web/html_email_is_evil.shtml
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52





-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.0 (Build 2158)
Charset: us-ascii

wj8DBQFK5kyESPXX9MTuPioRAhffAJ93qYCog7OZ+AWXV2ywOrOvKQTkcACgsefc
n2EEWEwIojd0qDaka2E2mFE=
=AfT7
-----END PGP SIGNATURE-----

Re: TT32Test64.exe reports CreateProcess(FWPCUtil) failed; rc=14001

by baumundberg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

> The official 3.06 release of Hercules you are running:
>
>    "Built on Jan 10 2009"
>    "Win32 (MSVC) build"
>
> is only a 32-bit version.
>
> You are trying to run a 32-bit version of Hercules on 64-bit Windows.
>
> While this is entirely possible it is NOT recommended. Instead, we recommend
> that you run a 64-bit version of Hercules instead.
>
> 64-bit versions of Hercules (which are NOT official releases per se (yet))
> can be downloaded from our "daily" development snapshot web site at:
>
>   http://www.ivansoftware.com/snapshots/snapshots/
>
>
> But wait! There's more! :)
>
> Even if you run one of the above 64-bit versions of Hercules, things STILL
> aren't going to work right because you'll still be missing the needed
> Microsoft redistributables.
>
> You see, here's the thing: on 64-bit Windows you CAN (if you want) still run
> 32-bit software, but that 32-bit software is STILL going to need all of the
> compnents it would normally need. Such as, say, the 32-bit version of
> Microsoft's redistributable DLLs.
>
> You installed the 64-bit version of Microsoft's redistributables:
>
>   "Microsoft Visual C++ 2005 ATL Update kb973923 - x64 8.0.50727.4053"
>
> but did you install the 32-bit x86 version as well? No. You did not.
>
> THAT is why you're getting your errors: you're trying to run 32-bit software
> without the needed 32-bit redistributables.
>
> Download and install the 32-bit (x86) version of that same "Microsoft Visual
> C++ 2005 ATL Update" redistributable.
>

Hey yeaahh, that's it. I installed x86 Version of MFC dlls and suddenly everything works fine. Thank you very much.