|
My users use a logon script that launches KiXtart, but before KiXtart is started a VBScript is executed to check installed network printers. When attempting to test the entire logon script with VBScript included Windows gave me a "There is no script engine for file extension ".vbs" message. I updated the Windows Script host to 5.6 after which the entire logon script ran successfully. After making a few changes to the VBScript I tried to run it again and received the error again. Re-running the Windows Script 5.6 install EXE fixed the problem temporarily, but if I try to run the logon script a second time I get the "There is no engine..." message again. It appears as though something in the running of KiXtart is disabling Windows Script 5.6 from being recognized as the engine for running VBScript scripts. After running the Windows Script 5.6 EXE I can run just the VBScript script I created as many times as I want. Once I run the full logon script that launches Kixtart, it runs successfully 1 time but each subsequent time gives me the "There is no engine..." message. At that point I can't run the full logon script or the VBScript until I run the Windows Script 5.6 install EXE again.
We're using KiXtart 3.63 on a Win XP machine and pulling the script from Win 2000 Server.Any suggestions would be greatly appreciated. Thanks in advance.
Bryant
| 
