During Captools/net installation, and whenever the Captools/net "Server Control Panel" program is run, several Windows "scripts" are run to ensure that MS-Windows is properly configured with respect to setting Captools/net program, folders and file permissions needed to allow Captools/net to operate.  We have occasionally encountered computers whose ability to run Windows scripts have been impaired.

 

Symptoms: The following symptoms indicate that your MS-Windows scripting requires repair:

 

1.) You will see "Windows Scripting Host" error messages either while installation or when you launch the Captools/net Server Control Panel.

 

2.) Windows Firewall may not have been configured resulting in "Server Not found (404)" errors when you try to login into the Captools/net Desktop program.

 

3.) For Windows Server, IIS may not have been configured resulting in "Server Not found (404)" errors when you try to login into the Captools/net Desktop program.

 

4.) When you run the Captools/net Reporting program you may get to the Report Selection page but do not see any reports listed there. Alternatively, you do not see any reports listed under the "Reports" menu in the Captools/net Desktop program.

 

5.) When you run the Captools/net Custodian Imports program, you may see no interfaces listed.

 

6.) You will be unable to view any scheduled tasks in the Scheduled Tasks configuration page.

 

8.) You will be unable to upload any files (Report logos, Import Data Files) into Captools/net.

 

Cause: The cause for the above problems is that the Windows Scripting Host software installed on the target machine is either corrupted or not latest. To read more information about Windows Scripting, please visit:

 

https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/wsh_overview.mspx?mfr=true

 

Resolution: Download the latest Windows Scripting Host Engine from Microsoft website (use following link) and install it.

 

 

After you have repaired Windows Scripting, reinstall Captools/net, including launching the Captools/net Server Control Panel.

 

 

VBS Scripts Opening in Notepad (instead of executing)

 

If VBS Scripts open in Windows Note Pad when installing or when re-running from the Server Control Panel, then find a ".Vbs" file in the Captools/net install folder in Windows Explorer, right-click on it, go to "Properties" and then change the "Open With" property to point to the Windows Script Host "wscript.exe" in \Windows\System32.  This will cause the script to be executed instead of simply being displayed in Notepad.  Please see topic VB Scripts Opening In Notepad for more detail.