NWN2 Server Log says "No NWNX4"

[Katy]

I think I'd mixed up a successful run and an unsuccessful one.

Failed run looks like this --

Output to nwnx_controllerd window

[Papillon]

This is getting a bit complicated, hope you are still with me .

Next, I would like to see what DDESpy shows. It's a debugging tool that shows what is going on between programs using DDE for communication (i.e., nwnx controller and server process in this case). You can enable all kinds of information logging with it - maybe an error shows up somewhere.

If you do not have it already (it was part of the Visual Studio 6.0 release), you can get the source code here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcsample98/html/vcsmppviewer.asp

I do not know if there are binaries somewhere on the net... but building it should be straightforward.
_________________
Papillon

[Gryphyn]

I've had something similar when developing my ODBC plugin.

The problem was that the plugins Init() call was returning false.
This should have been easy to diagnose, however the 'logging' that would normally be put to the log file doesn't get flushed from the buffer when Init() returns false.

. Something in the .INI file is broken (I had quotes around my path) or
. your Connection fails - causing Init() to return false;

Cheers
Gryphyn

[Papillon]

Hold on, the DDE connection needs to be established before Init() is even called. This does not seem to be the case here.
_________________
Papillon

[Papillon]

While discussing with Gryphyn, I got some more ideas. I'd like to know what the output of the debugging version of the hooking DLL looks like.

- I am assuming that you are still creating the nwnx.txt logfile in startIPCServer() in a fixed place (like c:\nwnw.txt).
- Now please compile the NWNX4 Hook project in debug mode, which will get you a NWNX4_Hookd.dll.
- Delete NWNX4_Controller.exe and NWNX4_Hook.dll and make sure that you have only the "d" versions of both left.
- Start NWNX4_Controllerd.exe -interactive.
- In c:\nwnx.txt you should get something like this on a successful connect: