Troubleshooting Hello, World!
If the Hello, World! application does not load correctly, you can check several things according to the following errors:
Web browser cannot connect with the Web server
If your Web browser cannot connect with the Web server, there is something wrong with your TCP/IP or Web server setup. Make sure you can ping the server, and check the configuration of your server software.
Web server cannot find the WSI program.
If your Web server cannot find the WSI program, make sure you have installed the executable file in your CGI directory. Also confirm that you are specifying the correct file name in the URL (abtwsac.exe, unless you have renamed the file).
Executable file fails
If the executable file fails, make sure the shared library files required by WSI are in a directory that can be found by your server's operating system.
WSI error reading Unable to connect to host
If you see a WSI error reading Unable to connect to host, this means that the WSI program was unable to contact the host where VA Smalltalk is running. Make sure all of the following are true:
The WSI configuration file specifies the correct TCP/IP host name.
TCP/IP is running on the specified host. Try pinging the host from the Web server machine.
A WSI server is running in the VA Smalltalk image. You should see it listed in the Web Server Interface Monitor window.
The WSI server is monitoring the correct port. Compare the port specified in the WSI configuration file to the port number you specified when you started the WSI server.
WSI error reading No class responded to this request
If you see a WSI error reading No class responded to this request, this means that the class name you specified in the URL does not exist. Make sure you are typing the class name exactly as it appears in VA Smalltalk, including the correct capitalization.
WSI error reading An exception occurred during the processing of this request
If you see a WSI error reading An exception occurred during the processing of this request, this means that something caused the VA Smalltalk application to fail. Check for errors in the application.
WSI error reading Configuration file abtwsi.cnf not found or unreadable
If you see a WSI error reading Configuration file abtwsi.cnf not found or unreadable, this means that the WSI program was unable to find the configuration file, or that the file was not in the correct format. Make sure the following are true:
You have placed the configuration file in the directory where abtwsac.exe runs, or in the directory pointed to by the ABTWSI_BASENAME environment variable. To find out the correct directory, check the current directory entry on the WSI error page that appears in your browser. (This information only appears in verbose mode, so make sure your configuration file includes a verbose on statement.)
If you are using the CGI interface, make sure you have enabled the CGI directory for web sharing and that you have used the alias to this directory in your browser URL.
The configuration file is a readable ASCII file and conforms to the correct format. (See Customizing the WSI configuration file for more information on the configuration file format.)
Last modified date: 01/29/2015