NWNServer crashing does not cause NWNX to restart it

[Zephyrys]

Hello,

I'm running Windows XP on my dedicated server and I'm having an issue with the Watchdog function of NWNX. Occasionally, NWNServer crashes with the message "NWNServer.exe has encountered a problem and needs to close". This window stays up until someone clears it. Unfortunately, NWNX seems to regard this as NWNServer still running and does not restart the server with its Watchdog function. Is there any method of getting around this?

[Baaleos]

Does it popup asking about debugging?

I had the similar issue.
For me, the Just in Time debugger from visual studio was keeping nwnserver open, which had the consequence of preventing nwnx from creating a new instance, and binding it successfully to the nwnserver port designated.

Result was that the server would start up bound to port -1.

Disabled just in time debugger via regedit.
Change

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger to be something like

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger_disabled

You wont even need a restart.
This will only fix the issue, if the issue was indeed caused by the debugger.

[Zephyrys]

The issue was actually caused by Microsoft's own error-reporting dialogue. I found there was a way to turn said dialogue off. It has not crashed yet, so I have yet to fully test it, but I don't see any reason why it wouldn't have done the trick.