KiXtart provides extensive logging of system errors, such as failure to locate support DLLs, failure to connect to the RPC service, and so on. On computers running Windows NT, these errors are logged in the system event log. On computers running Windows 9x, the errors are logged in a text file named Kixtart.log, which is stored in the Temp or Windows directory.
|
Note |
KiXtart supports the new automatic DrWatson functionality of Windows XP. If you encounter an exception error with KiXtart, and the DrWatson dialog is displayed, please do select the ‘Send Report’ option. Doing so will greatly help with the research and resolution of any issues in KiXtart.
The following table describes the most common problems encountered by KiXtart.
|
Error |
Meaning |
Solution |
|
|
||
|
The macro @ADDRESS returns an empty string (""). |
KiXtart failed to find a NetBIOS interface on any of the network bindings. |
Make sure a NetBIOS interface is available on one of the bindings. |
|
The macro @FULLNAME returns an empty string (""). |
KiXtart cannot retrieve the network information. |
On Windows NT, make sure the Workstation service is running. On Windows 9x, make sure that the support DLLs are available. Also check the event log or kixtart.log for any errors. |
|
KiXtart does not recognize certain commands. |
Although KiXtart is a free-format language, some literals, such server names that contain a hyphen (-), can cause errors. |
Enclose literals in quotation marks. |
|
Errors such as "Label not found" or "Unknown command" appear in an otherwise faultless script. |
There is probably an unmatched quotation mark or similar error somewhere in the script. |
Proofread your script. |
|
Failed to initialize RASMAN.DLL. |
Caused by a ‘half-installation’ of the RAS client software. Installation either wasn’t completed, or the uninstallation left RASAPI32.DLL on the system. |
Remove RASAPI32.DLL from the system, or complete the installation of the RAS client. |
|
Application error c0000006H / ‘IN_PAGE_ERROR’ / ‘SWAP_ERROR’ or an Invalid Page Fault is generated intermittently. |
The operating system has failed to read code from executable file(s) because the KiXtart startup drive has become unavailable. |
Make sure that you do not, in any way, disconnect or re-redirect the drive from which KIX32.EXE was started. Also, these faults can be caused by antivirus software. If you use antivirus software, make sure you are using the latest version and if the problem persists, test if disabling the antivirus software solves the problem. Lastly, if you are using the Windows version of KiXtart (WKIX32.EXE) in a batchfile, please make sure to run it using the START command with the /W and /B options. |
|
Tip |
To include quotation marks in a string, either use the CHR function, or enclose the entire string in quotation marks. For example,
"String with a quote (‘) in it."
or:
"String with a double quote
" + Chr(34) + " in it."
KiXtart provides a basic debug facility. In debug mode, a script can be executed statement by statement, the value of variables or macros can be displayed, and you can execute arbitrary script commands. To run a script in debug mode, specify ‘/d’ on the command line. Alternatively, you can enter and leave debug mode anywhere in a script using the DEBUG ON and DEBUG OFF commands.
Note: debug mode can be completely disabled from within a script using SetOption( "DisableDebugging", "On").
In debug mode, the top line of the screen is used to display the current line in the script starting at the current statement. Optionally, the second line of the screen is used to display the value of a specific variable or macro.
In debug mode, the following keys are available to control script execution:
F5 Run (deactivates debug mode, runs rest of script to the end or until a DEBUG ON command is encountered).
F8, <Space>, <Enter> Step into (run a single statement, follow thread into subroutines, UDF’s, and secondary scripts).
F10 Step over (run a single statement, executes, but skips over subroutines, UDF’s, and secondary scripts as far as the debugger is concerned).
\ (Backslash) Enables you to query the value of a variable, array element or macro simply by typing the name and pressing <Enter>. Similarly, you can execute an arbitrary piece of KiXtart code simply by typing it in and pressing <Enter>.