This could be a software licensing or a communication problem. Solutions for both scenarios are:

• Licensing problems

  • Verify that SAS/IntrNet software and other required SAS software (such as SAS/CONNECT software) are licensed.

    If the applet submits a SAS startup command, you might want to add the -altlog option to the command. You can then check the SAS log for additional information.

• Communication problems

  • If you are using the SAS spawner, verify that you are using the correct version of the spawner (described in the requirements page for each Java tool).

  • Telnet to the SAS server.

    Note: For an example of how to start a remote SAS session using telnet, see the telnet example.

    If you cannot connect to the SAS server and you are using the correct version of the spawner, verify that you do not have another telnet daemon running on port 23. If you do, use the -telnet parameter to indicate another port when starting the spawner.

    If you can connect to the SAS server, try to initialize SAS by using the SAS startup command used by the applet. If you cannot initialize SAS using this command, verify that the command is correct.

    If you can initialize SAS through your telnet connection, the problem might be:

    • Your Web server strips the backslashes from the SAS startup command as it is transferred to the SAS server. Change the backslashes in your SAS command to double backslashes. If you are using the tunnel feature, create an alias for the SAS command in your tunnel configuration file.

    • Your timeout values are not set to allow for the speed and traffic on your network.

    • Your connection parameter values are not specified correctly. For more information, see usage note #24077.

Operating System and Release Information