I'm troubleshooting an odd problem.
I'm using KGen to assemble the script from a .TXT file and a couple of .UDF files from my library. The script is a network listener using KixForms Sockets. I'm using the latest version of KF with enhanced socket support.
I have a client that runs as a system service on servers, and a stripped-down command-line client that just connects, queries, displays the results and then exits.
KGen creates a .GEN file with my .TXT and all .UDF files in source form. It then tokenizes the .GEN file and renames the output to .KIX.
Logged in at the server, with either the service account or an admin account, I get the same results.
If I start the service script by calling "kix32.exe service.gen", both the client service and command-line test tools work. If I call the tokenized version - "kix32.exe service.kix" - the connection hangs forever. Both the workstation where I run KGEN and the server have the same copy of Kix32, version 4.62.
When I run the tokenized copy, the service initialization messages are logged, but then it appears that nothing else executes, and the client reports the connection but nothing further.
Does anyone have any ideas why the same code and Kix32 would have such different results just by tokenizing?
Thanks!
Glenn
_________________________
Actually I
am a Rocket Scientist!
