Welcome to KORG!

This could be just about anything, so to narrow it down, here's a little overview:
Kixtart began life as an advanced login script processor and has evolved into a powerful administrative scripting tool.
WKIX32 is the "windowing" version of Kixtart - it is used to run Kix scripts that don't output to a console device/window. It's most commonly used to create system services, background automation, and GUI-based tools.

The standard Kixtart file extensions are .KIX and .KX, the latter being the default for tokenized scripts (semi-compiled, non-readable).

I'd start by searching your server for all the .KIX files. If you've ever programmed in BASIC or VB, it should be quite understandable. You can post the scripts here and we can help you figure out what they are doing, and hopefully, what's going wrong. The most common issue with admin scripts is an app upgrade that causes paths or app names to change.

Review any of the scripts you find and obfuscate any potentially proprietary info (credentials, public server names, etc.) before posting. Put the scripts between CODE tags (a "[", the word "code" and a "]" - the end tag is "/code") and it will retain the format/indent and even colorize the script.

Hope that gets you started!

Glenn
_________________________
Actually I am a Rocket Scientist! \:D