Click here to return to the KiXtart HelpDesk main page...

Troubleshooting KiXtart

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, they are logged in a text file named KiXtart.log, which is stored in the Temp or Windows directory.

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 you are running a NetBIOS interface on one of the bindings.

The macro @FULLNAME returns an empty string ("").

KiXtart cannot retrieve the network information.

On Windows NT, make sure you are running the Workstation service.

On Windows 9x, make sure that the supportDLLs are available.

Also check the event log or kixtart.log for anyerrors.

KiXtart seems to hang when you start it.

KiXtart cannot connect to your logon server to retrieve your user information.

Determine the name of the logon server (using @LSERVER) and try to connect to it manually.

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.

Check that your script does not contain a logical error, such as a net use * /d or use z: /d command. Also, these faults can be caused by antivirus software. If you use antivirus software, make sure you are using the latest version.

Note

Because KiXtart 95 is a true 32-bit application, it writes to the screen using the Win32 Console API. For this reason, screen output may seem slower than the direct screen output used by MS-DOS – based versions of the program.


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."      String with a quote (‘) in it.